On 28 August 2016 at 22:28, Chris Boyd <cb...@gizmopartners.com> wrote: > I think I’m missing something, but I can’t find a simple command on a Cisco > ASR router to show me what LSP a TE path is taking. It looks like something > like
Firstly, which kind of ASR are you looking at here? ASR9000s or 900s? I have put output below from ASR900 but ASR9K is similar... Secondly, do you mean you want to see which explicit path you are using, I'm a bit confused by the question? Do you just want to see the end-to-end label values? If you aren't using any explicit paths of contraint based routing then you are probably going to be following the IGP shortest path, in which case you can see in the IGP the LSP path. If are you using explicit paths you can simply view the explicit path(s): abr1-cdpfbo.core#show mpls traffic-eng tunnels Tu1119 Name: core:abr1-omnrgt:Tu1119 cid:MPLS... (Tunnel1119) Destination: 10.0.0.11 Status: Admin: up Oper: up Path: valid Signalling: connected path option 1, type explicit abr1-cdpfbo_to_abr1-omnrgt (Basis for Setup, path weight 110) Config Parameters: Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) .... Active Path Option Parameters: State: explicit path option 1 is active .... InLabel : - OutLabel : TenGigabitEthernet0/0/27, 50375 Next Hop : 10.10.0.65 RSVP Signalling Info: Src 10.0.0.19, Dst 10.0.0.11, Tun_Id 1119, Tun_Instance 9 RSVP Path Info: My Address: 10.10.0.66 Explicit Route: 10.10.0.65 10.10.0.22 10.0.0.11 .... abr1-cdpfbo.core#show ip explicit-paths name abr1-cdpfbo_to_abr1-omnrgt PATH abr1-cdpfbo_to_abr1-omnrgt (strict source route, path complete, generation 6) 1: next-address 10.10.0.66 2: next-address 10.10.0.65 3: next-address 10.10.0.21 4: next-address 10.10.0.22 Cheers, James. _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/