- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Re: ProCurve 2610 not showing any tags for Avaya p...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
03-21-2016 03:48 PM
03-21-2016 03:48 PM
SolutionYes, 802.1p is not useful for this issue.
Just to clarify: 802.1p tells the *switch* which switch buffer to put each *frame* in when it is *switching* them.
As long as you don't have any switch interfaces running at 80%+, and consequently dropping frames, then .1p isn't doing anything for you.
Your concern is Layer3 QoS, which is how the *packets* are *routed*. And this is only important on the contended infrastructure belonging to the WAN provider.
Your packet captures seem to be indicating you have everything tagged correctly. Sound like something somewhere is (correctly) not agreeing with your DSCP marking "46" being applied to signalling packets.
Ultimately, the cause of your issues is the failure of your WAN provider to offer the standard class-of-service split for traffic that I would expect them to.
- « Previous
-
- 1
- 2
- Next »