Guest

Preview Tool

Cisco Bug: CSCtb32301 - N5K: Some QoS config wiped out when upgrade to version 4.1(3)N1(1)

Last Modified

Jan 31, 2017

Products (3)

  • Cisco Nexus 5000 Series Switches
  • Cisco Nexus 5020 Switch
  • Cisco Nexus 5010 Switch

Known Affected Releases

4.1(3)N1(1)

Description (partial)

Symptom:
The N5K switch is configured with QoS policy-map as follows:
policy-map uplink-qos-egress
  class control-system-class
    bandwidth percent 1
  class enterprise-system-class
    bandwidth percent 80
  class balanced-system-class
    bandwidth percent 8
  class vmotion-system-class
    bandwidth percent 10
  class class-fcoe
    bandwidth percent 0
  class class-default
    bandwidth percent 1
policy-map downlink-qos-egress
  class control-system-class
    bandwidth percent 1
  class enterprise-system-class
    bandwidth percent 34
  class balanced-system-class
    bandwidth percent 4
  class vmotion-system-class
    bandwidth percent 10
  class class-default
    bandwidth percent 1
  class class-fcoe
    bandwidth percent 50
system qos
  service-policy system-level-qos
!
interface port-channel1
  service-policy output uplink-qos-egress
!
interface Ethernet1/1
  service-policy output downlink-qos-egress

After the switch was upgraded from version 4.0(1a)N2(1a) to 4.1(3)N1(1), the following configuration were wiped out:
1) the QoS actions of the policy-map
2) the QoS policy attachments to the interfaces
3) the QoS policy attachment to system service

No error message was displayed on the console to indicate that there is anything wrong with the QoS configuration during the reboot. See attached upgrade.log.

Conditions:
Upgrading software image to 4.1(3)N1(1), with QoS queuing configuration.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.