Guest

Preview Tool

Cisco Bug: CSCuw44058 - N3500: UTC offset not reused by BC when utc_offet_valid is FALSE from GM

Last Modified

Feb 14, 2018

Products (1)

  • Cisco Nexus 3000 Series Switches

Known Affected Releases

6.0(2)A6(4.124)

Description (partial)

Symptom:
GM ---------- BC1 ------------ BC2 ---------- client
In the above topology when Grand Master [GM] sends utc_offset_valid as FALSE, Boundary Clock node [BC1] propagates 36 as utc offset irrespective of the once received from GM.
In our case, GM sends UTC offset 35 with UTC_offset_valid as FALSE. However BC1 sends to BC2 with UTC offset as 36 and UTC_offset_valid as TRUE.
BC1 *must* always reuse the information received from GM.

Conditions:
NA
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.