cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Using BGP-LS/PCE-P with XR and ODL

8700
Views
2
Helpful
15
Comments
Cisco Employee

First off ensure you have a "new" XRv or ASR9K load (XR 6.0 or later) and a "new" ODL (Beryllium or later).


Then ensure ODL is running the BGP and PCEP features (by doing "feature:install odl-bgpcep-bgp-all" and "feature:install odl-bgpcep-pcep-all").

Configure BGP on ODL.  You have two options here:

  • modify ~/etc/opendaylight/karaf/41-bgp-example.xml.
    • change the local BGP RIB info.  Search for "example-bgp-rib" and change the "local-as" and "bgp-rib-id" values to be your local AS and ODL's IP address.
    • add the peer for XRv (one of your XRv nodes needs to be the BGP speaker).  Look for the "example-bgp-peer" module, remove the comments around it, and edit the IP address.
    • (optionally).  If you want XR to be in a different ASN to ODL then add "<peer-role>ebgp</peer-role>" and "<remote-as>XXX</remote-as>" (replacing "XXX" with XR's ASN).
    • (optionally).  If you want ODL to listen on port 179 (so it can accept inbound connections from XR) then search for "binding-port" and modify the port to be 179 instead of 1790.  Note that you'll need to run ODL as root for this to work.
    • do an rm -rf on ODL's ~/data and ~/etc/opendaylight/current directories and restart ODL for the changes to take effect.
  • PUTting the config from e.g. postman.


1) PUT the RIB:  So e.g. PUT to http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules/module/odl-bgp-rib-impl-cfg:rib-impl/example-bgp-rib with:

{ "module" : [

        {

            "type": "odl-bgp-rib-impl-cfg:rib-impl",

            "name": "example-bgp-rib",

            "odl-bgp-rib-impl-cfg:bgp-rib-id": "10.0.0.1",

            "odl-bgp-rib-impl-cfg:bgp-dispatcher": {

                "type": "odl-bgp-rib-impl-cfg:bgp-dispatcher",

                "name": "global-bgp-dispatcher"

            },

            "odl-bgp-rib-impl-cfg:extensions": {

                "type": "odl-bgp-rib-spi-cfg:extensions",

                "name": "global-rib-extensions"

            },

            "odl-bgp-rib-impl-cfg:tcp-reconnect-strategy": {

                "type": "protocol-framework:reconnect-strategy-factory",

                "name": "example-reconnect-strategy-factory"

            },

            "odl-bgp-rib-impl-cfg:rib-id": "example-bgp-rib",

            "odl-bgp-rib-impl-cfg:session-reconnect-strategy": {

                "type": "protocol-framework:reconnect-strategy-factory",

                "name": "example-reconnect-strategy-factory"

            },

            "odl-bgp-rib-impl-cfg:local-table": [

                {

                    "type": "odl-bgp-rib-impl-cfg:bgp-table-type",

                    "name": "ipv4-unicast"

                },

                {

                    "type": "odl-bgp-rib-impl-cfg:bgp-table-type",

                    "name": "ipv6-unicast"

                },

                {

                    "type": "odl-bgp-rib-impl-cfg:bgp-table-type",

                    "name": "linkstate"

                },

                {

                    "type": "odl-bgp-rib-impl-cfg:bgp-table-type",

                    "name": "ipv4-flowspec"

                },

                {

                    "type": "odl-bgp-rib-impl-cfg:bgp-table-type",

                    "name": "ipv6-flowspec"

                },

                {

                    "type": "odl-bgp-rib-impl-cfg:bgp-table-type",

                    "name": "labeled-unicast"

                }

            ],

            "odl-bgp-rib-impl-cfg:data-provider": {

                "type": "opendaylight-md-sal-binding:binding-async-data-broker",

                "name": "pingpong-binding-data-broker"

            },

            "odl-bgp-rib-impl-cfg:dom-data-provider": {

                "type": "opendaylight-md-sal-dom:dom-async-data-broker",

                "name": "pingpong-broker"

            },

            "odl-bgp-rib-impl-cfg:codec-tree-factory": {

                "type": "opendaylight-md-sal-binding:binding-codec-tree-factory",

                "name": "runtime-mapping-singleton"

            },

            "odl-bgp-rib-impl-cfg:local-as": 64496

        }

    ]

}

(remember to change the IP address for the bgp-rib-id, and if needed the local-as)

(also note that for ODL Beryllium and later the "flowspec" stanza is replaced by separate "ipv4-flowspec" and "ipv6-flowspec" stanzas, though of course you only need to include the address families you plan to use.  The same applies to the peer config below).

2) PUT the peer - as above only one of the XR nodes needs to speak BGP.  Note that you only need to enable the address families that you wish to use (they are listed under "advertized-table").


So e.g. PUT to http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules/module/odl-bgp-rib-impl-cfg:bgp-peer/example-bgp-peer with:

{ "module" : [

        {

            "type": "odl-bgp-rib-impl-cfg:bgp-peer",

            "name": "example-bgp-peer",

            "odl-bgp-rib-impl-cfg:host":"10.0.0.2",

            "odl-bgp-rib-impl-cfg:initiate-connection": true,

            "odl-bgp-rib-impl-cfg:rib": {

                "type": "odl-bgp-rib-impl-cfg:rib-instance",

                "name": "example-bgp-rib"

            },

            "odl-bgp-rib-impl-cfg:peer-registry": {

                "type": "odl-bgp-rib-impl-cfg:bgp-peer-registry",

                "name": "global-bgp-peer-registry"

            },

            "odl-bgp-rib-impl-cfg:advertized-table": [

                {

                    "type": "odl-bgp-rib-impl-cfg:bgp-table-type",

                    "name": "ipv4-unicast"

                },

                {

                    "type": "odl-bgp-rib-impl-cfg:bgp-table-type",

                    "name": "linkstate"

                }

            ]

        }

    ]

}

(again remember to change the IP address for the host)

Now configure BGP on XRv.  So e.g.

router bgp 64496

bgp router-id 10.0.0.2

address-family link-state link-state

!

neighbor 10.0.0.1

  remote-as 64496

  address-family link-state link-state

!

Ensure XRv also has ISIS or OSPF routes distributed into BGP-LS using the following command within ISIS or OSPF:

distribute bgp-ls

Now verify that the BGP session comes up.  In ODL you ought to be able to do a GET on e.g.: http://localhost:8181/restconf/operational/network-topology:network-topology/topology/example-linkstate-topology and see BGP-LS topology info.


Now configure PCE-P on all of your XRv instances.  under "mpls traffic-eng" you want something like:


pce

  peer ipv4 10.0.0.1

  !

  stateful-client

  instantiation

  delegation

  !

!

auto-tunnel pcc

  tunnel-id min 101 max 200


Note that for PCE-P to come up your ODL instance will need to be able to route back to the loopback addresses in your XRv network.  If those are e.g. in 192.168.0.0/24 then go to the ODL host and do something like:


sudo route add -net 192.168.0.0/24 gw 10.0.0.2


if you want this to persist after a reboot then edit /etc/network/interfaces (this is assuming Ubuntu) and add:


up route add -net 192.168.0.0/24 gw 10.0.0.2


Alternatively you can configure XR to use a different source interface for PCE-P using "mpls traffic-eng pce peer source ipv4 a.b.c.d" and selecting e.g. the address of the management interface.


Then check PCE-P has come up on ODL by looking at e.g. http://localhost:8181/restconf/operational/network-topology:network-topology/topology/pcep-topology.  You should see a list of PCE-P nodes.  If not then look for ESTABLISHED inbound connections to port 4189 on the ODL host and if they're missing then verify you can ping the router loopbacks and that there are no filters in e.g. iptables blocking inbound connections.


Having done all this you can start adding LSPs etc.

There are two modes for PCE-P LSPs

Firstly the LSP may be configured in XR and delegated to PCE-P.  So the LSP will be configured something like:

interface tunnel-te1

ipv4 unnumbered Loopback0

signalled-name foo

autoroute announce

!

destination 192.168.0.4

pce

  delegation

!

!

So then the LSP can be brought up by using the update-lsp RPC (http://localhost:8181/restconf/operations/network-topology-pcep/update-lsp):

{

    "input" : {

        "node" : "pcc://192.168.0.1",

        "name" : "foo",

        "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]",

        "arguments": {

            "lsp": {

                "administrative": "true",

                "delegate": "true"

            },

            "ero" : {

                "subobject" : [

                    {

                        "loose" : "false",

                        "ip-prefix" : { "ip-prefix" : "192.168.99.2/32" }

                    },

                    {

                        "loose" : "false",

                        "ip-prefix" : { "ip-prefix" : "192.168.0.4/32" }

                    }

                ]

            }

        }

    }

}

(note that there will be one sub-object per link the LSP traverses - using the address of the far end of the link - plus one for the loopback address of the egress router).

The response to the RPC should be empty (i.e. '{ "output": {} }').

Once you have done this the LSP should be visible under the PCC in the pcep-topology, or by doing a "show mpls traffic-eng tunnels" in XR.

Alternatively the LSP may be created/deleted dynamically by ODL using the add-lsp RPC (http://localhost:8181/restconf/operations/network-topology-pcep/add-lsp):

{

    "input": {

        "node": "pcc://192.168.0.1",

        "name": "bar",

        "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]",

        "arguments": {

            "odl-pcep-ietf-stateful07:lsp" : {

                "delegate" : "true",

                "administrative" : "true"

            },

            "endpoints-obj": {

                "ipv4": {

                    "source-ipv4-address": "192.168.0.1",

                    "destination-ipv4-address": "192.168.0.4"

                }

            },

            "ero" : {

                "subobject" : [

                    {

                        "loose" : "false",

                        "ip-prefix" : {

                            "ip-prefix" : "192.168.99.2/32"

                        }

                    },

                    {

                        "loose" : "false",

                        "ip-prefix" : {

                            "ip-prefix" : "192.168.0.4/32"

                        }

                    }

                ]

            }

        }

    }

}

Again the LSP should then be visible in the pcep-topology and in XR.  In XR the tunnel number will be in the range given in the MPLS-TE config for dynamic tunnels.

you can still update the LSP (e.g. to change path or to add bandwidth) using update-lsp:

{

    "input" : {

        "node" : "pcc://192.168.0.1",

        "name" : "bar",

        "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]",

        "arguments": {

            "lsp": {

                "administrative": "true",

                "delegate": "true"

            },

            "bandwidth": {

                "bandwidth": "QvoAAA=="

            },

            "ero" : {

                "subobject" : [

                    {

                        "loose" : "false",

                        "ip-prefix" : { "ip-prefix" : "192.168.99.2/32" }

                    },

                    {

                        "loose" : "false",

                        "ip-prefix" : { "ip-prefix" : "192.168.0.2/32" }

                    }

                ]

            }

        }

    }

}

(note that a full ERO must still be given even if not changing the path).

you can then delete the LSP if required using the remove-lsp RPC (http://localhost:8181/restconf/operations/network-topology-pcep/remove-lsp):

{

    "input" : {

        "node" : "pcc://192.168.0.1",

        "name" : "bar",

        "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]"

    }

}

Note that one constraint with ODL is that dynamically-generated LSPs don't support autoroute (as autoroute isn't part of the standard).  But there are Cisco-proprietary extensions available (e.g. in Cisco OSC) to enable that.  E.g. include the following within "arguments", "lsp":

                    "tlvs" : {

                        "vs-tlv" : {

                            "enterprise-number" : 9,

                            "pcep-cisco-specific:fcid" : 1

                        }

                    }

(you'll also need to configure "mpls traffic-eng pce stateful-client cisco-extension" on XR)

Enjoy!

15 Comments
Not applicable

Excellent Tutorial Giles! I appreciate putting all together.

Beginner

Thanks Giles. Very useful. 

ps. I think some of the URIs changed.

Cisco Employee

ah - that might have been my mistake in the RPC URIs

Beginner

Hello Giles, thank you for this tutorial! I have a question. Is 192.168.0.1 an address of loopback interface? Is it possible to setup tunnel between non loopback interfaces?

Cisco Employee

yes - it's a loopback.

you can change the PCC to use e.g. the management interface by putting "peer source ipv4 a.b.c.d" under mpls traffic-eng pce.

for the LSPs themselves I think you'd generally want to use loopbacks - but sure you should be able to use any address on either box.

Cisco Employee

Thanks for this Giles. Some questions:

- What is an example of "your local AS"

- From the network at the following link, which should be the peer? opendaylight-setup/xrvr-5 at master · CiscoDevNet/opendaylight-setup · GitHub

- Why might one want ODL to list on port 179 for inbound connections? What might the XR node be saying?

- What significance do the 10.0.0.1 and 10.0.0.2 addresses have in these sections?             "odl-bgp-rib-impl-cfg:bgp-rib-id": "10.0.0.1", and "odl-bgp-rib-impl-cfg:host":"10.0.0.2",

- What assumptions have you made about the VM host networking? For example, does it have static or dynamic addressing? Which interfaces does it have? Where do the 192.168 networks come from?

Regards

Nathan

Cisco Employee

- What is an example of "your local AS"

whatever AS you use for BGP.    By default ODL runs in 64496, but I generally use 65504 so you'll see that in my various scripts/postman collections etc. on github.

- From the network at the following link, which should be the peer? opendaylight-setup/xrvr-5 at master · CiscoDevNet/opendaylight-setup · GitHub

ah - I'll update the git with a new parameters file.  it should be xrvr-a.

- Why might one want ODL to list on port 179 for inbound connections? What might the XR node be saying?

XR (and most other routers) will always connect on port 179.    So if you want ODL to accept inbound connections from XR etc. then you need it to run on port 179.  I generally stick to having ODL connect outbound.

- What significance do the 10.0.0.1 and 10.0.0.2 addresses have in these sections?             "odl-bgp-rib-impl-cfg:bgp-rib-id": "10.0.0.1", and "odl-bgp-rib-impl-cfg:host":"10.0.0.2",

The RIB ID is used for BGP best path selection etc. and is generally set to the IP address of ODL.  The host is the IP address of your BGP peer.

- What assumptions have you made about the VM host networking? For example, does it have static or dynamic addressing? Which interfaces does it have? Where do the 192.168 networks come from?

Well - no assumptions per se, but dynamic IPs would generally be a nightmare (IIRC my setup scripts in github handle that at least for the client VM by checking the IP address of the tunnel interface).  The XR nodes will start up with as many interfaces as you configure in KVM/QEMU (the first is always for management).  Typically I just have ODL BGP peer with the management IP of one of the XR nodes.   The 192.168.100.0/24 addresses are the XR loopbacks.  For PCE-P ODL needs to be able to reach XR's loopback, or you need to tell XR not to use its loopback (e.g. you can tell it to use its management IP instead - all of this is in the text above)

Not applicable

Hi, tried to setup in VIRL and PCEP peer won't comeup here is the post I put on CLN without anyone answering, please help !!!!

I trying to configure PCEP on XRv in VIRL, the session is failed to establish with ODL. Here is the configuration  :

PCC ( XRv) IP : 192.168.2.121/24

PCE (ODL) IP : 192.168.2.61/24

iBGP peer is up between them :

RP/0/0/CPU0:coma01#sh bgp sum

Thu Sep  1 14:51:25.791 UTC

BGP router identifier 192.168.0.1, local AS number 65001

BGP generic scan interval 60 secs

Non-stop routing is enabled

BGP table state: Active

Table ID: 0xe0000000   RD version: 2

BGP main routing table version 2

BGP NSR Initial initsync version 2 (Reached)

BGP NSR/ISSU Sync-Group versions 0/0

BGP scan interval 60 secs

BGP is operating in STANDALONE mode.

Process       RcvTblVer   bRIB/RIB   LabelVer  ImportVer  SendTblVer  StandbyVer

Speaker               2          2          2          2           2           0

Neighbor        Spk    AS MsgRcvd MsgSent   TblVer  InQ OutQ  Up/Down  St/PfxRcd

192.168.2.61      0 65001     160     287        2    0    0 01:14:33          0

PCE configuration on XRv :


pce

  peer source ipv4 192.168.6.121

  peer ipv4 192.168.2.61

  !

  segment-routing

  logging events peer-status

  stateful-client

   instantiation

   delegation

  !

!

auto-tunnel pcc

  tunnel-id min 101 max 200

!

PCE debug msg on XRv :

RP/0/0/CPU0:Sep  1 14:40:30.306 : te_control[1049]: DBG-PCE-SESSION[10]: pce_sock_init:873: Initialize TCP socket

RP/0/0/CPU0:Sep  1 14:40:30.306 : te_control[1049]: ERR-PCE[10]: te_pce_open_active_tcp_con:1185: bind_connect_cisco failed for 192.168.6.121 -->192.168.2.61

There is also a weird license msg on all XRv : ( just purchased 1 year 30 nodes this August )

xrvr_lic_mgr[412]: %LICENSE-IOSXRV_LICENSE-2-ENFORCE_EVAL_EXPIRED : Licensed feature L-XRV-DEMO-LIC is in use beyond the evaluation period.

Cisco Employee

shouldn't your peer source be 192.168.2.121 rather than 192.168.6.121?

Not applicable

HA, typo is your friend too confident when typing. peer is up hoooooooo.

Any idea on the license msg ?

BTW, this is really good stuff, thank you for coming up the procedure, it's what we are looking for.

Cisco Employee
Not applicable

Got that too, and the post on CLN was me   Just can't find VIRL guys, seems like no Cisco VIRL guy ever join/watch community   that's why I asked you here ...  sent email to virl@cisco.com to see any response from there.

Beginner

Hello!

How can bind PCE initiated LSP to L3VPN service if i don't use OCS with cisco-specific autoroute announce attribute? Can apply such configuration in another way ? Maybe through configuration group?

Not applicable

Finally have time to do some tests and troubleshooting. I am having two issues and wondering if  you could help.

1. update-lsp

It seems like without configuring SR in XRv manually, the TE tunnel ( with PCE delegation configured ) won't come up and PCE lsp-database won't be build, meaning there isn't any LSP in ODL PCE topology. When I tried to make restconf call to update-lsp, got error message error-type 19 and error-value 3 = "Attempted LSP Update Request for an LSP  identified by an unknown PLSP-ID".

I can make restconf call to update-lsp to change LSP when I manually configured SR in XRv first though.

2. LSP created by ODL - add-lsp

PCE debug ( development and path ) in XRv showed all operations are normal, LSP built and put into lsp-database, only one weird thing in ODL PCE topology :

<reported-lsp><name>dynamic-te1</name><path><lsp-id>0</lsp-id><lspa><hold-priority>7</hold-priority><exclude-any>0</exclude-any><tlvs/><local-protection-desired>false</local-protection-desired><ignore>false</ignore><processing-rule>false</processing-rule><include-all>0</include-all><setup-priority>7</setup-priority><include-any>0</include-any></lspa><ero><processing-rule>false</processing-rule><ignore>false</ignore></ero><lsp><sync>false</sync><remove>false</remove><operational>down</operational><administrative>true</administrative><processing-rule>false</processing-rule><plsp-id>103</plsp-id><ignore>false</ignore><tlvs><symbolic-path-name><path-name>ZHluYW1pYy10ZTE=</path-name></symbolic-path-name><lsp-identifiers><lsp-id>0</lsp-id><tunnel-id>102</tunnel-id><ipv4><ipv4-tunnel-endpoint-address>192.168.0.6</ipv4-tunnel-endpoint-address><ipv4-tunnel-sender-address>192.168.0.1</ipv4-tunnel-sender-address><ipv4-extended-tunnel-id>6.0.168.192</ipv4-extended-tunnel-id></ipv4></lsp-identifiers><path-binding><binding-type>0</binding-type><binding-value>AAXdcAA=</binding-value></path-binding></tlvs><delegate>false</delegate><create>false</create></lsp><bandwidth><processing-rule>false</processing-rule><ignore>false</ignore><bandwidth>AAAAAA==</bandwidth></bandwidth></path></reported-lsp>

until it try bring up TE tunnel :

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4711: Dump lsp (tunnel): 11989f3c

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4714:     plsp-id=13

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4719:     symbolic path name=tunnel-te12

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4725:     creator: 11989f60

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4727:         addr: 0.0.0.0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4729:         speaker-id: (null)

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4735:     owner: 11989f68

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4737:         addr: 192.168.2.61

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4739:         speaker-id: (null)

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4745:     last owner: 11989f70

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4747:         addr: 0.0.0.0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4749:         speaker-id: (null)

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4753:     delegatable: 1

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4756:     initiated: 0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4770:     srp-id: 0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4773:     waiting request count: 0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4779:     setup type: 1 (Segment-routing)

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4788:     END-POINTS: 118d85f4

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4790:         src addr: 192.168.0.1

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4792:         dest addr: 192.168.0.14

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4798:     LSP: 118d85bc

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4801:         flags: Delegation Remove Administrative

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4810:         Operational: Up

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4815:         ipv4 lsp identifiers: 118d85d8

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4817:             sender addr: 192.168.0.1

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4820:             lsp-id: 2

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4823:             tunnel id: 12

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4826:             extended tunnel id: 3232235534 (14.0.168.192)

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4856:         traffic steering:

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4858:             FCID: 0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4860:             Loadshare: 0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4862:             Autoroute: none

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4914:     path 1/1: 118d740c

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4944:         SR-ERO:

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4946:             Hop count: 2

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4953:             1. SID: 16004

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4959:                 L:0 C: 0 M: 1

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4963:                 NAI: Local Node-ID: 192.168.0.11

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4953:             2. SID: 16007

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4959:                 L:0 C: 0 M: 1

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:4963:                 NAI: Local Node-ID: 192.168.0.14

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:5001:         LSPA: 118d8cf0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:5003:             exclude_any: 0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:5006:             include_any: 0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:5009:             include_all: 0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:5012:             setup priority: 7

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:5015:             hold priority: 7

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:5018:             local protection required bit: 0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:5055:         BW: 118d7dd0

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_dump_lsp:5057:             value: 0 Bps

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_update_tx_stats:3477: Updating statistics: TX Report

RP/0/0/CPU0:Oct  6 20:54:20.648 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_tx_msg:3597: TX msg at 1475787260

RP/0/0/CPU0:Oct  6 20:54:20.658 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_flush_tcp_buffer:1673: Tranmitted 116 bytes, no pending data

RP/0/0/CPU0:Oct  6 20:54:20.658 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_p2p_rw_proc_tunnel_rw_response:200: TE RW RES: Succeed,RC:[0x00000000, No error],TID:12,LID:3

RP/0/0/CPU0:Oct  6 20:54:20.658 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_report_to_all:5557: === Reporting state of lsp 13 to all peers - end ===

RP/0/0/CPU0:Oct  6 20:54:20.658 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_lsp_free:181: pce_lsp_free: freeing lsp 13 (tunnel-te12)

RP/0/0/CPU0:Oct  6 20:54:20.658 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_lsp_request_dequeue:1646: pce_lsp_request_dequeue: queue is empty

RP/0/0/CPU0:Oct  6 20:54:40.096 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_lspmgr_tecomm_pce_process_report:3291: pce_lspmgr_tecomm_pce_process_report: Received report batch from TE (full_report: 0, count: 1)

RP/0/0/CPU0:Oct  6 20:54:40.096 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_lsp_free:181: pce_lsp_free: freeing lsp 102 ((null))

RP/0/0/CPU0:Oct  6 20:54:40.096 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_lsp_request_dequeue:1646: pce_lsp_request_dequeue: queue is empty

RP/0/0/CPU0:Oct  6 20:54:40.096 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_lsp_free:181: pce_lsp_free: freeing lsp 0 (dynamic-te1)

RP/0/0/CPU0:Oct  6 20:54:40.096 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_lsp_request_dequeue:1646: pce_lsp_request_dequeue: queue is empty

RP/0/0/CPU0:Oct  6 20:54:40.096 : te_control[1049]: DBG-PCE-DEVELOP[10]: pce_lspmgr_tecomm_pce_send_error:3774: pce_lspmgr_tecomm_pce_send_error: Sending internal error 3 to TE

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-SIG[1]: mte_vif_reopt_cleanup_timer_expired:13661 (Tunnel ID: 1): cleanup timer expired, for tunnel-te1 cleaning up cleanedLSP 2

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-SIG[1]: mte_vif_reopt_cleanup_timer_expired:13661 (Tunnel ID: 2): cleanup timer expired, for tunnel-te2 cleaning up cleanedLSP 2

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-SIG[1]: mte_vif_reopt_cleanup_timer_expired:13661 (Tunnel ID: 11): cleanup timer expired, for tunnel-te11 cleaning up cleanedLSP 2

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_api_unadmit_resv:371 (T:1,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.6,CT:7,V:1610612736): Segment-Routing S2L admission not supported.

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_api_unadmit_path:243 (T:1,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.6,CT:7,V:1610612736): Segment-Routing S2L admission not supported.

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_s2l_output_rw_delete:1091: Subfam deleted. (tun id 1, lsp id 2, ext_tun_id 192.168.0.1, source 192.168.0.1, p2p dest 192.168.0.6, p2mp id 2147483647, nexthop 0.0.0.0)

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_p2p_rw_lsd_delete_psc_label_rw:1789 (T:1,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.6,CT:7,V:1610612736): DEL Lbl RW: R:[0x00000000, No error],LL:24015,OL:1048577,NH:0.0.0.0

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_api_free_local_label:806: te_lsd_api_free_local_label:806:

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_s2l_get_soft_preempt_bw_to_update:2499 (T:1,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.6,CT:7,V:1610612736): not soft-preempted

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_api_unadmit_resv:371 (T:2,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.14,CT:7,V:1610612736): Segment-Routing S2L admission not supported.

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_api_unadmit_path:243 (T:2,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.14,CT:7,V:1610612736): Segment-Routing S2L admission not supported.

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_s2l_output_rw_delete:1091: Subfam deleted. (tun id 2, lsp id 2, ext_tun_id 192.168.0.1, source 192.168.0.1, p2p dest 192.168.0.14, p2mp id 2147483647, nexthop 0.0.0.0)

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_p2p_rw_lsd_delete_psc_label_rw:1789 (T:2,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.14,CT:7,V:1610612736): DEL Lbl RW: R:[0x00000000, No error],LL:24016,OL:1048577,NH:0.0.0.0

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_api_free_local_label:806: te_lsd_api_free_local_label:806:

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_s2l_get_soft_preempt_bw_to_update:2499 (T:2,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.14,CT:7,V:1610612736): not soft-preempted

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_api_unadmit_resv:371 (T:11,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.6,CT:7,V:1610612736): Segment-Routing S2L admission not supported.

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_api_unadmit_path:243 (T:11,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.6,CT:7,V:1610612736): Segment-Routing S2L admission not supported.

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_s2l_output_rw_delete:1091: Subfam deleted. (tun id 11, lsp id 2, ext_tun_id 192.168.0.1, source 192.168.0.1, p2p dest 192.168.0.6, p2mp id 2147483647, nexthop 0.0.0.0)

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_p2p_rw_lsd_delete_psc_label_rw:1789 (T:11,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.6,CT:7,V:1610612736): DEL Lbl RW: R:[0x00000000, No error],LL:24017,OL:1048577,NH:0.0.0.0

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_api_free_local_label:806: te_lsd_api_free_local_label:806:

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_s2l_get_soft_preempt_bw_to_update:2499 (T:11,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.6,CT:7,V:1610612736): not soft-preempted

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_p2p_rw_proc_rw_del_result:407: Rcv RW del from LSD, status='No error'

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_api_free_lcl_label_result:1216: Freed LL: ctx=0x5dcf, status='No error'

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_p2p_rw_proc_rw_del_result:407: Rcv RW del from LSD, status='No error'

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_api_free_lcl_label_result:1216: Freed LL: ctx=0x5dd0, status='No error'

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_p2p_rw_proc_rw_del_result:407: Rcv RW del from LSD, status='No error'

RP/0/0/CPU0:Oct  6 20:54:40.736 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_api_free_lcl_label_result:1216: Freed LL: ctx=0x5dd1, status='No error'

RP/0/0/CPU0:Oct  6 20:54:40.776 : te_control[1049]: DBG-TUNNEL-SIG[1]: mte_vif_reopt_cleanup_timer_expired:13661 (Tunnel ID: 12): cleanup timer expired, for tunnel-te12 cleaning up cleanedLSP 2

RP/0/0/CPU0:Oct  6 20:54:40.776 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_api_unadmit_resv:371 (T:12,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.14,CT:7,V:1610612736): Segment-Routing S2L admission not supported.

RP/0/0/CPU0:Oct  6 20:54:40.776 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_api_unadmit_path:243 (T:12,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.14,CT:7,V:1610612736): Segment-Routing S2L admission not supported.

RP/0/0/CPU0:Oct  6 20:54:40.776 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_s2l_output_rw_delete:1091: Subfam deleted. (tun id 12, lsp id 2, ext_tun_id 192.168.0.1, source 192.168.0.1, p2p dest 192.168.0.14, p2mp id 2147483647, nexthop 0.0.0.0)

RP/0/0/CPU0:Oct  6 20:54:40.776 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_p2p_rw_lsd_delete_psc_label_rw:1789 (T:12,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.14,CT:7,V:1610612736): DEL Lbl RW: R:[0x00000000, No error],LL:24018,OL:1048577,NH:0.0.0.0

RP/0/0/CPU0:Oct  6 20:54:40.776 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_api_free_local_label:806: te_lsd_api_free_local_label:806:

RP/0/0/CPU0:Oct  6 20:54:40.776 : te_control[1049]: DBG-TUNNEL-ADMIT[1]: te_s2l_get_soft_preempt_bw_to_update:2499 (T:12,L:2,P:2147483647,E:192.168.0.1,SI:0,SO:0.0.0.0,S:192.168.0.1,D:192.168.0.14,CT:7,V:1610612736): not soft-preempted

RP/0/0/CPU0:Oct  6 20:54:40.776 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_p2p_rw_proc_rw_del_result:407: Rcv RW del from LSD, status='No error'

RP/0/0/CPU0:Oct  6 20:54:40.776 : te_control[1049]: DBG-TUNNEL-REWRITE[1]: te_lsd_api_free_lcl_label_result:1216: Freed LL: ctx=0x5dd2, status='No error'

And TE tunnel won't come up, any help will be appreciated.

Thanks !

Cisco Employee

Hello Giles.

How I can modify a TE or SR tunnel's parameters, like bandwidth, autoroute-announce, forward class, forwarding adjacency, etc? Obviously, it should go through update-lsp API call, but how XML body of POST request should looks like?

CreatePlease to create content
This widget could not be displayed.