Cisco Bug: CSCup44917 - Edit PBR identifier not raising Topo mis- config alarm in CTC
Last Modified
Feb 03, 2017
Products (1)
- Cisco Carrier Packet Transport (CPT) System
Known Affected Releases
9.701
Description (partial)
Symptom: Problem Statement / SYMPTOM: ************************** Edit PBR identifier in existing Ring is not triggering Topo mis- config alarm even though there is mis-match between actual topology and provisioned topology. Conditions: Steps followed: ***************** 1. Created a DH with 3 PBR in a ring with identifier as NE1, NE2 and NE3. Ring state was UP and enabled. 2. I disabled ring state. Edit and change PBR identifier from NE3 to NE4. 3. Now I made ring state enable. In Above scenario, PBR is configured with device identifier as NE3 but in CTC I edited and provisioned as NE4.
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