HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Switch Config best practices
Switches, Hubs, and Modems
1832433
Members
3381
Online
110042
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
Forums
Discussions
Discussions
Discussions
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
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
11-02-2006 07:41 AM
11-02-2006 07:41 AM
Switch Config best practices
I have a question about the best practices for several Switch options... but generally, I assume it is ideal to use the same options on all switches ie:
1) QOS- if you have a statment such as qos dscp 101110 for a high priority vlan, I would assume for the traffic to be properly queued on all the switches, the statement should be on all the swiches that have that vlan, not just on a core switch
2) dhcp-relay and ip helper- I assume if you are using a central (off subnet) dhcp server it is ideal to ensure both statements exist on all switches, not just a core switch
3) ip route- I assume if you are using routing on a core switch, it is the only one that requires the ip route statements, and for performance the fewer the number of routes the better the switch performance (particularly on lower end switches ie 2600's)
Are all these assumptions correct?
Thanks
1) QOS- if you have a statment such as qos dscp 101110 for a high priority vlan, I would assume for the traffic to be properly queued on all the switches, the statement should be on all the swiches that have that vlan, not just on a core switch
2) dhcp-relay and ip helper- I assume if you are using a central (off subnet) dhcp server it is ideal to ensure both statements exist on all switches, not just a core switch
3) ip route- I assume if you are using routing on a core switch, it is the only one that requires the ip route statements, and for performance the fewer the number of routes the better the switch performance (particularly on lower end switches ie 2600's)
Are all these assumptions correct?
Thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2006 08:55 PM
11-02-2006 08:55 PM
Re: Switch Config best practices
Hi RobB !
1. The command:
qos dscp-map < codepoint > priority < 0 - 7 > [name < ascii-string >]
configures an 802.1p priority for the specified codepoint
and, optionally, an identifying (policy) name.
In your case the specified DSCP Policy 101110
implies 802.1p Priority 7 by default.
It means that IP packet coming into the switch, having the value 101110 within its header TOS field is assigned the priority 7 within priority field of the 802.1Q tag of the encapsulating frame coming out of the switch, if the out port is tagged.
In other word the incoming frame will be assigned to Class 7 of service using Level 3 marking, serviced via high priority queue and marked at Level 2 with priority 7.
The other switches should be aware of 802.1p priority using tagged ports for forwarding the frame.
If the out port is untagged the frame goes out of the switch unmarked, thus killing the prioritization.
2. dhcp-relay works only on routing switches, receves DHCP broadcast request and translates them into unicast or subnet directed broadcasts (depending on configuration), addressed to the specified DHCP servers or subnet.
3. Theoretically you're right practically it depends on segmentation of your network and traffic flows.
Good luck,
Dmitry
1. The command:
qos dscp-map < codepoint > priority < 0 - 7 > [name < ascii-string >]
configures an 802.1p priority for the specified codepoint
and, optionally, an identifying (policy) name.
In your case the specified DSCP Policy 101110
implies 802.1p Priority 7 by default.
It means that IP packet coming into the switch, having the value 101110 within its header TOS field is assigned the priority 7 within priority field of the 802.1Q tag of the encapsulating frame coming out of the switch, if the out port is tagged.
In other word the incoming frame will be assigned to Class 7 of service using Level 3 marking, serviced via high priority queue and marked at Level 2 with priority 7.
The other switches should be aware of 802.1p priority using tagged ports for forwarding the frame.
If the out port is untagged the frame goes out of the switch unmarked, thus killing the prioritization.
2. dhcp-relay works only on routing switches, receves DHCP broadcast request and translates them into unicast or subnet directed broadcasts (depending on configuration), addressed to the specified DHCP servers or subnet.
3. Theoretically you're right practically it depends on segmentation of your network and traffic flows.
Good luck,
Dmitry
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP