- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- VLAN configuration question
Switches, Hubs, and Modems
1753394
Members
7431
Online
108792
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2010 02:01 PM
тАО02-03-2010 02:01 PM
I am wondering if it is possible to use VLANs to configure my network to resolve this issue.
I want to allow the traffic on the secondary network to talk to Port 43 on the primary network; but that is the only traffic I want to allow between the two networks. It is a time server with a single NIC and I currently have it dual-homed.
I attempted to add the ports listed below to their own VLAN. However, when I do that I am unable to ping from the 10.1.105.0 network to 10.1.105.199.
So, my question is do I need to get a router or can I use VLANs?
Procurve 2848 - Primary network -172.20.20.0
Port 43 - 172.20.20.199/10.1.105.199 - Time Server
Port 20 - Connected 2610
Procurve 2610 - Secondary network - 10.1.105.0
Port 7 - Connected to 2848
I want to allow the traffic on the secondary network to talk to Port 43 on the primary network; but that is the only traffic I want to allow between the two networks. It is a time server with a single NIC and I currently have it dual-homed.
I attempted to add the ports listed below to their own VLAN. However, when I do that I am unable to ping from the 10.1.105.0 network to 10.1.105.199.
So, my question is do I need to get a router or can I use VLANs?
Procurve 2848 - Primary network -172.20.20.0
Port 43 - 172.20.20.199/10.1.105.199 - Time Server
Port 20 - Connected 2610
Procurve 2610 - Secondary network - 10.1.105.0
Port 7 - Connected to 2848
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2010 12:28 AM
тАО02-04-2010 12:28 AM
Solution
Hello,
all ports on both switches are in the DEFAULT_VLAN (VLAN ID 1). You have to create new VLANs for each ip subnet you use. For example:
DEFAULT_VLAN - VLAN ID 1
Subnet 172.20.20.0 - VLAN ID 20
Subnet 10.1.105.0 - VLAN ID 105
A short configuration:
On the 2848
conf t
ip routing
vlan 20
name "Subnet 172.20.20.0"
ip address 172.20.20.254 255.255.255.0
tagged 20
untagged 1-19,21-48
exit
vlan 105
name "subnet 10.1.105.0"
ip address 172.1.105.254
tagged 20
no untagged 1-19,21-48
exit
On the 2610
conf t
vlan 20
name "Subnet 172.20.20.0"
tagged 7
no untagged 1-6,8-24
exit
vlan 105
name "Subet 10.1.150.0"
tagged 7
untagged 1-6,8-24
exit
You have to set the 10.1.150.254 as default gateway for all clients in this subnet, the same for all clients in the subnet 172.20.20.0 - all clients in this subnet must have the 172.20.20.254 as default gateway. Now you can remove the 10.1.150.199 from the timeserver. It's just a question of routing. :)
Regards,
Patrick
all ports on both switches are in the DEFAULT_VLAN (VLAN ID 1). You have to create new VLANs for each ip subnet you use. For example:
DEFAULT_VLAN - VLAN ID 1
Subnet 172.20.20.0 - VLAN ID 20
Subnet 10.1.105.0 - VLAN ID 105
A short configuration:
On the 2848
conf t
ip routing
vlan 20
name "Subnet 172.20.20.0"
ip address 172.20.20.254 255.255.255.0
tagged 20
untagged 1-19,21-48
exit
vlan 105
name "subnet 10.1.105.0"
ip address 172.1.105.254
tagged 20
no untagged 1-19,21-48
exit
On the 2610
conf t
vlan 20
name "Subnet 172.20.20.0"
tagged 7
no untagged 1-6,8-24
exit
vlan 105
name "Subet 10.1.150.0"
tagged 7
untagged 1-6,8-24
exit
You have to set the 10.1.150.254 as default gateway for all clients in this subnet, the same for all clients in the subnet 172.20.20.0 - all clients in this subnet must have the 172.20.20.254 as default gateway. Now you can remove the 10.1.150.199 from the timeserver. It's just a question of routing. :)
Regards,
Patrick
Best regards,
Patrick
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2010 06:28 AM
тАО02-04-2010 06:28 AM
Re: VLAN configuration question
Patrick,
Thank you for the excellent response. That is exactly what I was looking for.
Thank you for the excellent response. That is exactly what I was looking for.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2010 07:22 AM
тАО02-04-2010 07:22 AM
Re: VLAN configuration question
Hello,
I hope it works for you. The config was freehand. :)
Regards,
Patrick
I hope it works for you. The config was freehand. :)
Regards,
Patrick
Best regards,
Patrick
Patrick
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP