Cisco Bug: CSCuo45578 - Daox - clock set is not persistent across vsm reload
Last Modified
Dec 25, 2014
Products (1)
- Cisco Nexus 1000V Switch for VMware vSphere
Known Affected Releases
5.2(1)SV3(1.0.51)
Description (partial)
Symptom: Following are different symptoms seen under this issue: Whenever VSM clock is changed using clock set command, the time is not persistent after the reload. When NTP is configured on the VSM and during reload, some of logs shows a skewed clock before the VSM gets correct time from NTP server. Conditions: This problem is seen only when the VSM is hosted on a 1010/1110 CPPA Box.
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