Cisco Bug: CSCup23928 - After 4F-BLSR Span Switch; Path TCA's are not reported on protect port
Sep 15, 2014
- Cisco ONS 15454 Series Multiservice Provisioning Platforms
Known Affected Releases
Symptom: After 4F-BLSR span switch and traffic carried on protect port, then following two issues are observed: 1) The path TCA's are not raised on protect port but reported on working port which is incorrect. 2) The Path level alarms are reported on both working and protect port. Conditions: Setup: 1. 4 Node 4F-BLSR ring with OC-192 rate on 15454 MSPP nodes. 2. Provision EC1/STS1/STS3C traffics with 4F-BLSR protection and monitor the same. Steps: 1. Enable IPPM on the trunk ports of 4F-BLSR for the monitored traffic. 2. Initiate Force Span switch on the 4F-BLSR ring for the monitored traffic. Observe traffic hit of <50ms and traffic is switched to protect path. 3. Inject B3 ERRORS from Test set so as to cross the threshold values for Path PM counters CV/ES/SES/UAS. 4. Observe the counters on protect port getting incremented but TCA's are raised against protect port but incorrectly reported on working port. 5. Inject Path alarms like AIS-P, UNEQ-P from test set. 6. Observe AIS-P alarm is reported on both working & protect port of the 4F-BLSR trunk.
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