Still missing relevant informations, but I guess you miss the backup-path TE configuration on your protecting core interfaces.
On 20.12.2012, at 19:38, M K <[email protected]> wrote: > > R2 > router isis 1 > net 49.0001.0000.0000.0002.00 > is-type level-2-only > metric-style wide > passive-interface Loopback0 > mpls traffic-eng router-id Loopback0 > mpls traffic-eng level-2 > > R2#sh run | sec router bgp > router bgp 100 > bgp log-neighbor-changes > no bgp default ipv4-unicast > neighbor 4.4.4.4 remote-as 100 > neighbor 4.4.4.4 update-source Loopback0 > ! > address-family ipv4 > exit-address-family > ! > address-family vpnv4 > neighbor 4.4.4.4 activate > neighbor 4.4.4.4 send-community both > exit-address-family > ! > address-family ipv4 vrf MSSK > network 1.1.1.1 mask 255.255.255.255 > network 192.1.12.0 > exit-address-family > > R4 > router isis 1 > net 49.0001.0000.0000.0004.00 > is-type level-2-only > metric-style wide > passive-interface Loopback0 > mpls traffic-eng router-id Loopback0 > mpls traffic-eng level-2 > > R4#sh run | sec router bgp > router bgp 100 > bgp log-neighbor-changes > no bgp default ipv4-unicast > neighbor 2.2.2.2 remote-as 100 > neighbor 2.2.2.2 update-source Loopback0 > ! > address-family ipv4 > exit-address-family > ! > address-family vpnv4 > neighbor 2.2.2.2 activate > neighbor 2.2.2.2 send-community both > exit-address-family > ! > address-family ipv4 vrf MSSK > network 6.6.6.6 mask 255.255.255.255 > network 192.1.46.0 > exit-address-family > > R2#sh mpls traffic-eng tunnels summary > Signalling Summary: > LSP Tunnels Process: running > Passive LSP Listener: running > RSVP Process: running > Forwarding: enabled > Periodic reoptimization: every 3600 seconds, next in 2998 seconds > Periodic FRR Promotion: Not Running > Periodic auto-bw collection: every 300 seconds, next in 298 seconds > P2P: > Head: 1 interfaces, 1 active signalling attempts, 1 established > 5 activations, 4 deactivations > 4703 failed activations > 0 SSO recovery attempts, 0 SSO recovered > Midpoints: 0, Tails: 1 > P2MP: > Head: 0 interfaces, 0 active signalling attempts, 0 established > 0 sub-LSP activations, 0 sub-LSP deactivations > 0 LSP successful activations, 0 LSP deactivations > 0 SSO recovery attempts, LSP recovered: 0 full, 0 partial, 0 fail > Midpoints: 0, Tails: 0 > > R4#sh mpls traffic-eng tunnels sum > Signalling Summary: > LSP Tunnels Process: running > Passive LSP Listener: running > RSVP Process: running > Forwarding: enabled > Periodic reoptimization: every 3600 seconds, next in 2995 seconds > Periodic FRR Promotion: Not Running > Periodic auto-bw collection: every 300 seconds, next in 295 seconds > P2P: > Head: 1 interfaces, 1 active signalling attempts, 1 established > 5 activations, 4 deactivations > 4695 failed activations > 0 SSO recovery attempts, 0 SSO recovered > Midpoints: 0, Tails: 1 > P2MP: > Head: 0 interfaces, 0 active signalling attempts, 0 established > 0 sub-LSP activations, 0 sub-LSP deactivations > 0 LSP successful activations, 0 LSP deactivations > 0 SSO recovery attempts, LSP recovered: 0 full, 0 partial, 0 fail > Midpoints: 0, Tails: 0 > > Now , shutting down R3 connection to R5 inside the MPLS backbone > > R3(config)#int f2/0 > R3(config-if)#shut > > R2# > *Dec 20 14:33:26.952: %LINEPROTO-5-UPDOWN: Line protocol on Interface > Tunnel0, changed state to down > > R2#sh mpls traffic-eng tunnels summary > Signalling Summary: > LSP Tunnels Process: running > Passive LSP Listener: running > RSVP Process: running > Forwarding: enabled > Periodic reoptimization: every 3600 seconds, next in 2904 seconds > Periodic FRR Promotion: Not Running > Periodic auto-bw collection: every 300 seconds, next in 204 seconds > P2P: > Head: 1 interfaces, 0 active signalling attempts, 0 established > 6 activations, 6 deactivations > 4709 failed activations > 0 SSO recovery attempts, 0 SSO recovered > Midpoints: 0, Tails: 1 > P2MP: > Head: 0 interfaces, 0 active signalling attempts, 0 established > 0 sub-LSP activations, 0 sub-LSP deactivations > 0 LSP successful activations, 0 LSP deactivations > 0 SSO recovery attempts, LSP recovered: 0 full, 0 partial, 0 fail > Midpoints: 0, Tails: 0 > > BR, > > >> CC: [email protected] >> From: [email protected] >> Subject: Re: [c-nsp] MPLS TE >> Date: Thu, 20 Dec 2012 21:22:18 +1100 >> To: [email protected] >> >> Hi, >> >> Please post all of your configurations and not just the Tunnels, plus the >> usual TE verification show commands such as "show mpls traffic-eng tunnels", >> "show mpls traffic-eng topology" >> >> Cheers, >> Joe >> >> Sent from my iPhone >> >> On 20/12/2012, at 21:05, M K <[email protected]> wrote: >> >>> >>> Hi all >>> I have configured MPLS TE with RSVP using ISIS inside the MPLS core >>> R2 and R4 are my PE routers >>> >>> R2#sh run int tun0 >>> Building configuration... >>> Current configuration : 259 bytes >>> ! >>> interface Tunnel0 >>> ip unnumbered Loopback0 >>> tunnel mode mpls traffic-eng >>> tunnel destination 4.4.4.4 >>> tunnel mpls traffic-eng autoroute announce >>> tunnel mpls traffic-eng path-option 1 explicit name PATH >>> tunnel mpls traffic-eng path-option 2 dynamic >>> end >>> >>> R4#sh run int tun 0 >>> Building configuration... >>> Current configuration : 259 bytes >>> ! >>> interface Tunnel0 >>> ip unnumbered Loopback0 >>> tunnel mode mpls traffic-eng >>> tunnel destination 2.2.2.2 >>> tunnel mpls traffic-eng autoroute announce >>> tunnel mpls traffic-eng path-option 1 explicit name PATH >>> tunnel mpls traffic-eng path-option 2 dynamic >>> end >>> >>> Now , the explicit path is working fine , when I shutdown one of the links >>> across the MPLS backbone , the tunnel interfaces become up again due to the >>> dynamic path configured under the tunnel interface >>> Now , when I remove the dynamic and configure FRR instead , the tunnel >>> interface keep in the down state (it's line protocol) >>> tunnel mpls traffic-eng fast-reroute bw-protect >>> >>> Am i missing something ? >>> >>> BR, >>> >>> _______________________________________________ >>> cisco-nsp mailing list [email protected] >>> https://puck.nether.net/mailman/listinfo/cisco-nsp >>> archive at http://puck.nether.net/pipermail/cisco-nsp/ > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
