[BGPCEP-490] ipv4-extended-tunnel-id showing backwards when LSP is operational down Created: 01/Jul/16  Updated: 03/Mar/19  Resolved: 02/Jul/16

Status: Resolved
Project: bgpcep
Component/s: PCEP
Affects Version/s: Bugzilla Migration
Fix Version/s: Bugzilla Migration

Type: Bug
Reporter: Kevin Wang Assignee: Claudio David Gasparini
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File ip-extended.down.pcap     File ip-extended.up.pcap    
External issue ID: 6138

 Description   

Bug exists since Beryllium at least.

Reproduce:

1. Create a PCC-inited LSP
2. Observe the network topology, ipv4 under reported-lsp/path/lsp/tlvs/lsp-identifiers is displayed like this:

<ipv4>
<ipv4-tunnel-endpoint-address>192.168.254.3</ipv4-tunnel-endpoint-address>
<ipv4-tunnel-sender-address>192.168.254.1</ipv4-tunnel-sender-address>
<ipv4-extended-tunnel-id>192.168.254.3</ipv4-extended-tunnel-id>
</ipv4>

3. Make the LSP operational down
4. Check the network topology again, now the ipv4 is showing like this

<ipv4>
<ipv4-tunnel-endpoint-address>192.168.254.6</ipv4-tunnel-endpoint-address>
<ipv4-tunnel-sender-address>192.168.254.1</ipv4-tunnel-sender-address>
<ipv4-extended-tunnel-id>6.254.168.192</ipv4-extended-tunnel-id>
</ipv4>

5. The ipv4-extended-tunnel-id is recovered to correct value when operational is back to UP.

  • Tested with Cisco XRV 5.3 as router

Is this behavior expected?

 Comments   
Comment by Claudio David Gasparini [ 01/Jul/16 ]

Hi Kevin, could you please attach logs, and package captures?
Thanks

Comment by Kevin Wang [ 02/Jul/16 ]

Attachment ip-extended.up.pcap has been added with description: pcap when lsp is up

Comment by Kevin Wang [ 02/Jul/16 ]

Attachment ip-extended.down.pcap has been added with description: pcap when the lsp is going down

Comment by Kevin Wang [ 02/Jul/16 ]

Hi Claudio,

I double checked the pcap (uploaded). the extended tunnel id is showing backwards in the PCRpt. I think it is a Cisco XRV bug.

Generated at Wed Feb 07 19:13:13 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.