Reset Search
 

 

Article

ToS rewrite doesn't apply value on new ports after new blade added on XoS switches

« Go Back

Information

 
TitleToS rewrite doesn't apply value on new ports after new blade added on XoS switches
Symptoms
  • ToS rewrite not working on new ports
  • Show switch config doesn't show that diffserv is enabled on ports in a newly added blade
Environment
  • XoS Summit switches
  • XMC NetSight
  • Policy Manager
  • Diffserv
  • ToS Rewrite
  • CoS
Cause
There is no function to enable diffserv at the port level via command line when adding a new blade to a switch.

Enabling diffserv at the port level requires a policy manager enforce which in turn enables Policy and automatically sets diffserv to enabled for all ports.  If policy is already enabled on the switch, subsequent enforces don't do an enable and therefore the diffserv is not enabled per port.
Resolution
To resolve this and enable diffserv for all ports on the new blade, the following process is required;
  1. In policy manager, right click on the device and select refresh
  2. Right click on the device and select Disable Class of Service
  3. Enforce policy to the switch
  4. Right click on the device and select Enable Class of Service
  5. Enforce Policy

This will resolve this issue.  If you issue a show config command you should now see configuration for all ports in this format;

enable diffserv replacement ports [port:number] qosprofile [QoS value]
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255