Cisco Bug: CSCul04778 - CTC allows TP link config with different subnet as next hop
Last Modified
Jan 31, 2017
Products (1)
- Cisco Carrier Packet Transport (CPT) System
Known Affected Releases
9.53 9.531 9.535
Description (partial)
Symptom: CTC allows TP link config with different subnet as next hop Conditions: . Configure IP address in an interface say 10.10.10.1 2. Create MPLS TP link configuration with the next hop IP address as 20.20.20.1 3. It will be created in CTC. But in IOS, it wont be available. 4. Create TP tunnel using that port and it will be created. 5. The TP tunnel will remain in DOWN since it is not aware of the TP link config created. 6. The output of "sh mp tp tu ls" will be as follows, 10.64.107.103#sh mp tp tu ls MPLS-TP Tunnels: Tunnel Peer Active Local Out Out Oper Number global-id::node-id::tun LSP Label Label Interface State ------ ----------------------- ------ ----- ----- --------- ----- 6 0::108.108.108.108::6 work working-lsp:num 0, actv 20 19 unknown down
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