Cisco Bug: CSCus80369 - Sup reload or Switchover may occur due to Leap second update
Jan 28, 2017
- Cisco Nexus 1000V Switch for VMware vSphere
- Cisco Nexus 1000V Switch
Known Affected Releases
Symptom: There are periodic leap second events which can add or delete a second to global time. When the leap second update occurs the following could be observed; 1. Nexus 1000 active VSM resets. Standby VSM switches over and becomes active. The previous active now comes up as Standby. All the VEM`s will be in same state and will not have any traffic disruption. 2. If the standby VSM is not present, the single active VSM will reset and comes up as active and the VEM`s will flap. During this time there will not be any traffic disruption. 3. No core files for the failed VSM. Conditions: The leap second update will be propagated via Network Time Protocol (NTP) or via manually setting the clock. The Nexus 1000 VSM may hit a Kernel livelock under the following 2 conditions: 1. When the NTP server pushes the update to the N1K NTPd client, which in turn schedules the update to the Kernel. This push should have happened 24 hours before June 30th 2015, by most NTP servers. 2. When the NTP server actually updates the clock 1 minute before the UTC time.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases