will "[no] mls qos" cause network disruption?

Unanswered Question
Apr 23rd, 2009
User Badges:

Hi,


Would like to confim the following:

(1) will enabling qos using "mls qos" cause any network disruption?


(2) will disabling qos using "no mls qos" cause any network disruption? (in case we need to fallback)


My client is concerned about enabling/disabling qos may cause network disruption to existing traffic flow due to the re-allocation of buffer at the interface.


My thoughts is that if the link is not congested, no packets will be in the queue, hence enabling/disabling qos should not impact existing traffic flows.


Any comments/thoughts are welcome.


Thanks

Eng Wee


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Giuseppe Larosa Fri, 04/24/2009 - 11:21
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

Hello Eng,

the immediate effect of enabling mls qos is that of seeing all packets QoS settings (DSCP byte) set to zero because by default all ports are not trusted.


see for example


http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/qos.html#wp1705197


This can be a problem for applications that check the DSCP settings.


This is the aspect to be aware of.


Hope to help

Giuseppe


Edison Ortiz Fri, 04/24/2009 - 12:28
User Badges:
  • Super Bronze, 10000 points or more
  • Hall of Fame,

    Founding Member

You haven't described the type of switches you are planning to QoS on but if those switches are 6500s, you should be aware that each module type employs a different type of QoS queuing.


If you are etherchanneling and the link members belong to different module types, you may experience a disruption in the etherchannel and an error will come up such as "QoS card-type mismatch".


HTH,


__


Edison.

glen.grant Sat, 04/25/2009 - 04:52
User Badges:
  • Purple, 4500 points or more

Yeah 6500 can be a pain as we found out the hard way . We tried to remove some mls qos commands off a single interface and its behavior was to pull it off all the ports in that particular asic which was like 12 ports , broke stuff on those other ports .

Actions

This Discussion