Cisco Bug: CSCuo94573 - 9.231:On single node 2nd UPSR revert depend on 1st UPSR revertive mode
Feb 05, 2017
- Cisco ONS 15454 Series Multiservice Provisioning Platforms
Known Affected Releases
9.213 9.23 9.231
Symptom: On a single 15454 node having two UPSR selectors for a circuit, the 2nd UPSR revertive traffic switching depends on the revertive mode provisioned for 1st UPSR selector. The above issue is only on the 2nd UPSR revertive switching. The 1st UPSR revertive switching works fine and is independent of 2nd UPSR revertive mode config. Conditions: Setup: 1. Two different UPSR rings(any rate) with one 15454 as a common node. 2. Create VT1.5 circuit between nodes logically located in different UPSR rings and monitor the same. Steps: 1. Open Edit window for the VT1.5 circuit and go to 'UPSR Selector' tab. 2. Observe two UPSR selectors available for common 15454 node. At initial, the traffic is carried on working path for both UPSR selectors. 3. Provision Revertive time for 1st UPSR selector as non-revertive and 2nd UPSR selector as 0.5 mins. 4. Apply user command on 2nd UPSR selector to switch traffic on protect and observe traffic switches within 50ms. 5. Release the command and observe traffic never switches back to working though the mode is set to Revertive. 6. Change Revertive time for 1st UPSR selector as 0.5 mins and non-revertive for 2nd UPSR selector. 7. Apply user command on 2nd UPSR selector to switch traffic on protect and observe traffic switches to protect port within 50ms. 8. Release the command and observe traffic switches back to working within 50ms though the mode is set to Non-revertive. Also observe WTR alarm reported against this port. 9. Apply user command on 1st UPSR selector to switch traffic on protect and observe traffic switches to protect port within 50ms. Releasing the command switches back the traffic to working. Conclusion: 2nd UPSR revertive switching is dependent on 1st UPSR revertive mode config.
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