- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Procurve DEFAULT_VLAN and tagging
Switches, Hubs, and Modems
1748256
Members
3720
Online
108760
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
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-28-2009 10:32 AM
тАО02-28-2009 10:32 AM
Procurve DEFAULT_VLAN and tagging
Hi,
One of our customer is having 3 switches :
2 x Procurve 2824 , SWA & SWB, interconnected by a trunk trk1.
1 x Procurve 2824 SWC.
There is a link between port 20 of SWA and SWC. SWB is there to achieve redundancy.
Currently customer has no VLAN, only DEFAULT_VLAN = 1 is configured, all ports of SWA/SWB untagged to this VLAN.
This is causing issues since SWA & SWB are polluted with broadcasts from servers behind SWC.
I would like to implement VLANs, so that :
Traffic internal to servers behind SWA/SWC is in a VLAN 10.
Management traffic remains in VLAN 1.
But to achieve this I will need to implement VLAN on customer servers because of lack of free network interfaces on these servers.
So on customer servers there will be bond0 ip address for MGT LAN, and bond0.10 for internal VLAN 10.
On the switch, corresponding ports will be untagged for VLAN 1, tagged for VLAN 10.
trk1 will be tagged for 1 & 10.
I have no problem to create VLANS. My query is now regarding the port 20 of SWA that connects to SWC.
Should I leave port 20 untagged in DEFAULT_VLAN, or should I tag explicitely port 20 for VLAN 1 ? If I do this I guess it is needed to tag port on both sides ?
Thanks
One of our customer is having 3 switches :
2 x Procurve 2824 , SWA & SWB, interconnected by a trunk trk1.
1 x Procurve 2824 SWC.
There is a link between port 20 of SWA and SWC. SWB is there to achieve redundancy.
Currently customer has no VLAN, only DEFAULT_VLAN = 1 is configured, all ports of SWA/SWB untagged to this VLAN.
This is causing issues since SWA & SWB are polluted with broadcasts from servers behind SWC.
I would like to implement VLANs, so that :
Traffic internal to servers behind SWA/SWC is in a VLAN 10.
Management traffic remains in VLAN 1.
But to achieve this I will need to implement VLAN on customer servers because of lack of free network interfaces on these servers.
So on customer servers there will be bond0 ip address for MGT LAN, and bond0.10 for internal VLAN 10.
On the switch, corresponding ports will be untagged for VLAN 1, tagged for VLAN 10.
trk1 will be tagged for 1 & 10.
I have no problem to create VLANS. My query is now regarding the port 20 of SWA that connects to SWC.
Should I leave port 20 untagged in DEFAULT_VLAN, or should I tag explicitely port 20 for VLAN 1 ? If I do this I guess it is needed to tag port on both sides ?
Thanks
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2009 12:20 AM
тАО03-01-2009 12:20 AM
Re: Procurve DEFAULT_VLAN and tagging
To answer your question, you can leave port 20 untagged in VLAN1, but you could also tag it. As long as it's the same on both ends it'll be fine.
Personally I always leave VLAN1 untagged. I tag the rest of my VLANs.
One last thing though, it sounds like this network is rather small - I would be very surprised if any issues they were having is due to excessive broadcast traffic. Do you have more detail on the exact issue they are seeing?
With the 2800 series, a common complain is poort Gigabit to 100Mbit performance. If this is the case, try 'qos-passthrough-mode'
Personally I always leave VLAN1 untagged. I tag the rest of my VLANs.
One last thing though, it sounds like this network is rather small - I would be very surprised if any issues they were having is due to excessive broadcast traffic. Do you have more detail on the exact issue they are seeing?
With the 2800 series, a common complain is poort Gigabit to 100Mbit performance. If this is the case, try 'qos-passthrough-mode'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2009 12:58 AM
тАО03-02-2009 12:58 AM
Re: Procurve DEFAULT_VLAN and tagging
Thanks for your answer Matt Hobbs.
Indeed beyond the SWC switch there is the default gateway. Port 20 is configured to 100 Mbps, other ports are configured to 1Gbps.
The problems on this platform resides in the isolation of LAN. Sometimes there was some delay induced in the communication causing software issue. Broadcast was indeed the main evidence of the bad network configuration (missing VLAN).
I will setup VLAN there on this platform, and I hope I can get a safe network configuration.
Thanks
Indeed beyond the SWC switch there is the default gateway. Port 20 is configured to 100 Mbps, other ports are configured to 1Gbps.
The problems on this platform resides in the isolation of LAN. Sometimes there was some delay induced in the communication causing software issue. Broadcast was indeed the main evidence of the bad network configuration (missing VLAN).
I will setup VLAN there on this platform, and I hope I can get a safe network configuration.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2009 12:59 AM
тАО03-02-2009 12:59 AM
Re: Procurve DEFAULT_VLAN and tagging
answered.
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