[j-nsp] Juniper MX + Cisco RSVP-TE/LSP
Jeffrey Nikoletich
jeffn at xfernet.com
Sat May 28 23:09:08 EDT 2016
Hello all,
We recently got in to juniper (and my first post here helped solve a
problem we were having, so I am loving this list). I have been trying to
figure out a design issue and hoping this list can help.
The design is this
CORE01.LAX01 (1.1.1.1)
|
|
CORE02.LAX01 (1.1.1.2)----------CORE01.ORD01 (2.2.2.1)
What we have is 2 cores in LAX01 (both MX960) and 1 core in ORD01 (Cisco
6500 Sup720-3BXL.
The issue I am having is getting all the LSP and RSVP-TE correct. I get the
LSP between CORE02.LAX01 and CORE01.ORD01 and see it online:
show mpls lsp
Ingress LSP: 2 sessions
To From State Rt P ActivePath LSPname
1.1.1.1 1.1.1.2 Up 0 * core01.lax01
2.1.1.1 1.1.1.2 Up 0 * core01.ord01
Total 2 displayed, Up 2, Down 0
Egress LSP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
1.1.1.2 2.2.2.1 Up 0 1 SE 3 - core1.ord01_t2
1.1.1.2 1.1.1.1.1 Up 0 1 FF 3 - core02.lax01
Total 2 displayed, Up 2, Down 0
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
But the LSP between CORE01.LAX01 and CORE01.ORD01 is not showing up:
show mpls lsp
Ingress LSP: 2 sessions
To From State Rt P ActivePath LSPname
1.1.1.2 1.1.1.1 Up 0 * core02.lax01
2.2.2.1 1.1.1.1 Dn 0 - core01.ord01
Total 2 displayed, Up 1, Down 1
Egress LSP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
1.1.1.1 1.1.1.2 Up 0 1 FF 3 - core01.lax01
Total 1 displayed, Up 1, Down 0
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
Here is my configs. I have been doing some testing and feel like I have
made the configs worse.
jeffn at core02.lax01> show configuration protocols mpls
label-switched-path core01.ord01 {
to 2.2.2.1;
}
label-switched-path core01.lax01 {
to 1.1.1.1;
}
interface all;
jeffn at core02.lax01> show configuration protocols rsvp
interface all;
jeffn at core01.lax01> show configuration protocols mpls
label-switched-path core01.ord01 {
to 2.2.2.1;
}
label-switched-path core02.lax01 {
to 1.1.1.2;
}
interface all;
jeffn at core01.lax01> show configuration protocols rsvp
interface all;
Sites are all interconnected via a /30.
Here is the config for CORE01.ORD01:
interface Tunnel1
ip unnumbered Loopback0
tunnel destination 1.1.1.1
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 dynamic
!
interface Tunnel2
ip unnumbered Loopback0
ip mtu 9100
tunnel destination 1.1.1.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 dynamic
router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 1
router-id 2.2.2.1
core1.ord01#sh mpls traffic-eng tunnels brief
Signalling Summary:
LSP Tunnels Process: running
Passive LSP Listener: running
RSVP Process: running
Forwarding: enabled
Periodic reoptimization: every 3600 seconds, next in 2549 seconds
Periodic FRR Promotion: Not Running
Periodic auto-bw collection: every 300 seconds, next in 166 seconds
TUNNEL NAME DESTINATION UP IF DOWN IF
STATE/PROT
core1.ord01_t1 1.1.1.1 - - up/down
core1.ord01_t2 1.1.1.2 - Vl200 up/up
core01.ord01 2.2.2.1 Vl200 - up/up
Displayed 2 (of 2) heads, 0 (of 0) midpoints, 1 (of 1) tails
Name: core1.ord01_t1 (Tunnel1) Destination: 1.1.1.1
Status:
Admin: up Oper: down Path: valid Signalling: RSVP
signalling proceeding
path option 10, type dynamic (Basis for Setup, path weight 2)
Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 0 bw-based
auto-bw: disabled
RSVP Signalling Info:
Src 2.2.2.1, Dst 1.1.1.1, Tun_Id 1, Tun_Instance 4845
History:
Tunnel:
Time since created: 17 days, 1 hours, 24 minutes
Time since path change: 2 minutes, 49 seconds
Current LSP:
Setup Time: 2 minutes, 20 seconds remaining
Prior LSP:
ID: path option 10 [4844]
Removal Trigger: setup timed out
Name: core1.ord01_t2 (Tunnel2) Destination: 1.1.1.2
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 10, type dynamic (Basis for Setup, path weight 1)
Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 0 bw-based
auto-bw: disabled
InLabel : -
OutLabel : Vlan200, implicit-null
RSVP Signalling Info:
Src 2.2.2.1, Dst 1.1.1.2, Tun_Id 2, Tun_Instance 469
RSVP Path Info:
My Address: 1.1.1.230
Explicit Route: 1.1.1.229 1.1.1.2
Record Route: NONE
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
RSVP Resv Info:
Record Route: NONE
Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
History:
Tunnel:
Time since created: 17 days, 1 hours, 47 minutes
Time since path change: 7 days, 7 hours, 25 minutes
Current LSP:
Uptime: 7 days, 7 hours, 25 minutes
Prior LSP:
ID: path option 10 [463]
Removal Trigger: path error
LSP Tunnel core01.ord01 is signalled, connection is up
InLabel : Vlan200, implicit-null
OutLabel : -
RSVP Signalling Info:
Src 1.1.1.2, Dst 2.2.2.1, Tun_Id 50597, Tun_Instance 3
RSVP Path Info:
My Address: 0.0.0.0
Explicit Route: NONE
Record Route: 1.1.1.229
Tspec: ave rate=0 kbits, burst=0 bytes, peak rate=17179869 kbits
RSVP Resv Info:
Record Route: NONE
Fspec: ave rate=0 kbits, burst=0 bytes, peak rate=0 kbits
Pinging over the LSP from CORE02.LAX01 works fine to CORE01.ORD01
jeffn at core02.lax01 > ping mpls rsvp core01.ord01 sweep
100! 5052! 7528! 8768! 9388. 9080! 9392. 9236. 9160. 9120. 9100! 9112!
9124. 9120. 9116!
--- lsp ping sweep result---
Maximum Transmission Unit (MTU) is 9116 bytes
Pinging back fails its seems:
core1.ord01#ping mpls traffic-eng tunnel 2
Sending 5, 100-byte MPLS Echos to Tunnel2,
timeout is 2 seconds, send interval is 0 msec:
Codes: '!' - success, 'Q' - request not transmitted,
'.' - timeout, 'U' - unreachable,
'R' - downstream router but not target,
'M' - malformed request
Type escape sequence to abort.
.....
Success rate is 0 percent (0/5)
core1.ord01#
Also CORE01.LAX01 and CORE02.LAX01 cant ping each other as well:
jeffn at core01.lax01> ping mpls rsvp core02.lax01 detail
Request for seq 1, to interface 196616, no label stack., packet size 92
Request for seq 2, to interface 196616, no label stack., packet size 92
Request for seq 3, to interface 196616, no label stack., packet size 92
Timeout for seq 1
Request for seq 4, to interface 196616, no label stack., packet size 92
Timeout for seq 2
Request for seq 5, to interface 196616, no label stack., packet size 92
Timeout for seq 3
Timeout for seq 4
Timeout for seq 5
--- lsping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
So any help is appreciated.
Regards,
Jeffrey Nikoletich - Chief Information Officer | 213-201-6080
Xfernet
| 3250 Wilshire BlvdPh 213-201-6080 | http://www.xfernet.net
More information about the juniper-nsp
mailing list