Cisco Bug: CSCum37793 - Callhome timestamp uses ISO 8601 standard for year
Feb 22, 2014
- Cisco 1000 Series Connected Grid Routers
Known Affected Releases
Symptom: Callhome code uses the ISO 8601 standard when reporting year. Sometimes the year reported is not the same as the calendar year. Conditions: Callhome uses the ISO 8601 convention described in 'man strftime()' as follows: ISO 8601 week dates %G, %g, and %V yield values calculated from the week-based year defined by the ISO 8601 standard. In this system, weeks start on a Monday, and are numbered from 01, for the first week, up to 52 or 53, for the last week. Week 1 is the first week where four or more days fall within the new year (or, synonymously, week 01 is: the first week of the year that contains a Thursday; or, the week that has 4 January in it). When three of fewer days of the first calendar week of the new year fall within that year, then the ISO 8601 week-based system counts those days as part of week 53 of the preceding year. For example, 1 January 2010 is a Friday, meaning that just three days of that calendar week fall in 2010. Thus, the ISO 8601 week-based system considers these days to be part of week 53 (%V) of the year 2009 (%G) ; week 01 of ISO 8601 year 2010 starts on Monday, 4 January 2010. and Dec 29 2013 happens to fall on the "first Monday" of 2014, so according to ISO 8601 Callhome using unix function strftime (fmt, STR_BUFFER_SIZE, "%G-%m-%d %H:%M:%S.%%s %Z%z", tm); should return timestamp "2014-12-30 ..." This has been the convention NX-OS Callhome software has used since the earliest days of CG-OS.
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