2. You seem to be right. When you set a port to trust DSCP, you are getting the switch to not reset the DSCP to 0 for incoming packets. The switch will use whatever DSCP the packet came with. On egress, the switch will use the DSCP to CoS map to select the egress queue. Finally, when sending the frame out, the switch will set the CoS value to whatever CoS value the DSCP was mapped to. However, the DSCP value will not be overwritten, since that is supposed to be trusted. Therefore, the 'no mls qos rewrite ip dscp' appears to be redundant in this case. However, the difference is that this command is a global command and will result in ToS-preservation for packets received on all interfaces and not just those set to trust DSCP
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...