Guest

Preview Tool

Cisco Bug: CSCur86727 - VLAN list truncated/lost on upgrade to 5.2(1) code for 1000v

Last Modified

Jan 29, 2017

Products (3)

  • Cisco Nexus 1000V Switch for VMware vSphere
  • Cisco Nexus 1000V Switch
  • Cisco Application Virtual Switch

Known Affected Releases

5.2(1)SV3(1.2)

Description (partial)

The port profile service continually crashes when ever you try to view or modify the configs of a port profile. An example can be seen below:N1Kv# show port-profile name Prod_uplink
2014 Dec  8 17:33:09 D1AASPRHQA0 sysmgr[1307]: %SYSMGR-2-SERVICE_CRASHED: Service "port-profile" (PID 27301) hasn't caught signal 11 (core will be saved).
2014 Dec  8 17:33:09 D1AASPRHQA0 %USER-3-SYSTEM_MSG: ERROR, mts_send failed, ERROR = -1, ERRNO = 9  - ppm
2014 Dec  8 17:33:13 D1AASPRHQA0 last message repeated 283 times
2014 Dec  8 17:33:13 D1AASPRHQA0 sysmgr[1307]: %SYSMGR-2-SERVICE_CRASHED: Service "port-profile" (PID 27888) hasn't caught signal 11 (core will be saved).
2014 Dec  8 17:33:13 D1AASPRHQA0 sysmgr[1307]: %SYSMGR-2-SYSMGR_AUTOCOLLECT_TECH_SUPPORT_LOG: This supervisor will temporarily remain online in order to collect show tech-support. This behavior is configurable via 'system [no] auto-collect tech-support'.

-The VSM will then crash and a switchover will occur.
-A core will be generated as a result of the crash

When you look at the running config of the port profile you will see something similar to the following output:

version 5.2(1)SV3(1.2)
port-profile type ethernet Prod_uplink
  switchport mode trunk
  2129-2175,2620-2622,2626,3912  <<<<<-------Notice that several of the configs are actually missing 
  service-policy type queuing output uplink-queue
  mtu 9000
  channel-group auto mode on mac-pinning
  no shutdown
  system vlan 151,212,216,218
  state enabled
  vmware port-group

-The following is what the port profile should actually look like:

port-profile type ethernet Prod_uplink
  vmware port-group
  switchport mode trunk
  switchport trunk allowed vlan 14,151,204,208-212,216,218,251-252,254-255
  switchport trunk allowed vlan add 257-258,260-261,263-264,266-267,269-270
  switchport trunk allowed vlan add 272-273,275-276,278-279,281-282,284-285
  switchport trunk allowed vlan add 287-288,290-291,293-294,296-297,306
  switchport trunk allowed vlan add 350-356,359-360,371-374,379-380,385-386
  switchport trunk allowed vlan add 391-399,450-452,600-602,705,748,818
  switchport trunk allowed vlan add 910,912-920,922,930-936,999,1255-1256
  switchport trunk allowed vlan add 1288-1289,1578,2006,2100-2102,2112
  switchport trunk allowed vlan add 2129-2175,2620-2622,2626,3912
  service-policy type queuing output uplink-queue
  mtu 9000
  channel-group auto mode on mac-pinning
  no shutdown
  system vlan 151,212,216,218
  max-ports 128

-Make note that the bug has cut quite a bit of configs form the port profile
-This does not seem to affect the VEMs directly as they are still operating on correct instructions received from the VSM somehow

Symptom:The port profile service continually crashes when ever you try to view or modify the configs of a port profile. An example can be seen below:


N1Kv# show port-profile name Prod_uplink
2014 Dec  8 17:33:09 D1AASPRHQA0 sysmgr[1307]: %SYSMGR-2-SERVICE_CRASHED: Service "port-profile" (PID 27301) hasn't caught signal 11 (core will be saved).
2014 Dec  8 17:33:09 D1AASPRHQA0 %USER-3-SYSTEM_MSG: ERROR, mts_send failed, ERROR = -1, ERRNO = 9  - ppm
2014 Dec  8 17:33:13 D1AASPRHQA0 last message repeated 283 times
2014 Dec  8 17:33:13 D1AASPRHQA0 sysmgr[1307]: %SYSMGR-2-SERVICE_CRASHED: Service "port-profile" (PID 27888) hasn't caught signal 11 (core will be saved).
2014 Dec  8 17:33:13 D1AASPRHQA0 sysmgr[1307]: %SYSMGR-2-SYSMGR_AUTOCOLLECT_TECH_SUPPORT_LOG: This supervisor will temporarily remain online in order to collect show tech-support. This behavior is configurable via 'system [no] auto-collect tech-support'.

-The VSM will then crash and a switchover will occur.
-A core will be generated as a result of the crash

When you look at the running config of the port profile you will see something similar to the following output:

version 5.2(1)SV3(1.2)
port-profile type ethernet Prod_uplink
  switchport mode trunk
  2129-2175,2620-2622,2626,3912  <<<<<-------Notice that several of the configs are actually missing 
  service-policy type queuing output uplink-queue
  mtu 9000
  channel-group auto mode on mac-pinning
  no shutdown
  system vlan 151,212,216,218
  state enabled
  vmware port-group

-The following is what the port profile should actually look like:

port-profile type ethernet Prod_uplink
  vmware port-group
  switchport mode trunk
  switchport trunk allowed vlan 14,151,204,208-212,216,218,251-252,254-255
  switchport trunk allowed vlan add 257-258,260-261,263-264,266-267,269-270
  switchport trunk allowed vlan add 272-273,275-276,278-279,281-282,284-285
  switchport trunk allowed vlan add 287-288,290-291,293-294,296-297,306
  switchport trunk allowed vlan add 350-356,359-360,371-374,379-380,385-386
  switchport trunk allowed vlan add 391-399,450-452,600-602,705,748,818
  switchport trunk allowed vlan add 910,912-920,922,930-936,999,1255-1256
  switchport trunk allowed vlan add 1288-1289,1578,2006,2100-2102,2112
  switchport trunk allowed vlan add 2129-2175,2620-2622,2626,3912
  service-policy type queuing output uplink-queue
  mtu 9000
  channel-group auto mode on mac-pinning
  no shutdown
  system vlan 151,212,216,218
  max-ports 128

-Make note that the bug has cut quite a bit of configs form the port profile
-This does not seem to affect the VEMs directly as they are still operating on correct instructions received from the VSM somehow

Conditions:-When customer is upgrading from 4.2(1) code to 5.2(1) code
-During the upgrade process, the migration of the config between versions has some kind of disconnect and the configs are corrupted
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.