MPLS TE - IP Explicit Path
Hi all,
Just wonder what is the best for the next-address, shall we point to next hop router interface ip or the router loopback ip ?
ip explicit-path name path1 enable
next-address 172.18.255.46
next-address 172.18.255.42
next-address 172.18.255.2
next-address 172.18.255.1
Both would work. If you have multiple links between 2 routers and want to force the link through a specific link you can probably use the interface ip.
If you want it to be choosen dynamically you can keep specifying the next-hop as the loopbacks of all the directly connected routers in the Tunnel path.
HTH-Cheers,
Swaroop
Similar Messages
-
MPLS TE - Explicit Path Configuration
Hi all
Few questions about explicit path configuration.
1) next-hop IP address , point to next-hop interface ip or router-id(loopback) , which is prefer with? and why.
2) Attached the diagram, 3 example of explicit-path configuration. Like to know it isi possible and valid.
Explicit path <1> & <2> the purpose is the TE path must via either one of the "pink" WAN links. Are both configuration valid ?
<3> have same purpose, but mixed with interface & router-ID as next hop. Does this kind config work ?
<1>TE Tunnel Site-A PE1 to Site-B PE1
ip explicite-path name APE1-BPE1_1 enable
next-address 10.1.1.1
exclude-address 10.1.3.2
next-address 10.1.4.2
<2>TE Tunnel Site-A PE1 to Site-B PE1
ip explicite-path name APE1-BPE1_2 enable
next-address 10.1.1.1
exclude-address 10.1.3.2
<3>TE Tunnel Site-A PE1 to Site-B PE1
ip explicite-path name APE1-BPE1_3 enable
next-address 10.1.1.1
next-address1.1.1.2As Shivlu explained if you use the next hop physical address then that is an strict hop but if you specify a loopback address as your next hop then that is considered as loose hop. Usually a loose hop is more flexible if you have multiple paths to the same destination. On the other hand when you specify the next hop as strict if that next hop goes down then your LSP goes down with it too. Although not very common but you can use a combination of loose and strict hop together.
Have a look at this doc for more info:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_inter_as_te.html
HTH
Reza -
MPLS TE: Loose Path vs Explicit Path
Hi NetPro,
I'm new with MPLS TE. Upon reading, I'm trying to understand the different between the terms of configuring loose path and explicit path.
Can anyone explain in simple term how to differentiate between this two terms?
Thanks in advance.
maherHi Maher,
I'm glad to hear from you. These two terms are not mutually exclusive. In other words, an explicit path can be configured with or without the loose option.
The loose option would rather be the opposite of the strict option.
Here is a brief summary of the difference between the strict and loose option:
Strict means that the next address in the explicit path belongs to an adjacent router to the router in the sequence.
Loose means that the next address can belong to a router that is not necesseraly adjacent.
Regards, -
I have two routers connected in a lab via MPLS TE using RSVP. When i setup the tunnel to use explicit path-option
for example " tunnel mpls traffic-eng path-option 2 explicit identifier 2", the tunnel goes down and doesnt come up until i change it to use" tunnel mpls traffic-eng path-option 2 dynamic". Any ideas why this is not working?
R1
ip cef
mpls traffic-eng tunnels
interface Loopback0
ip address 150.1.1.1 255.255.255.255
interface Loopback1
description MPLS Traffic Eng
ip address 172.25.1.1 255.255.255.0
interface Tunnel0
ip unnumbered Loopback1
load-interval 30
tunnel destination 172.25.2.1
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng bandwidth 100
tunnel mpls traffic-eng path-option 1 dynamic
interface Serial1/0
ip address 192.168.1.1 255.255.255.0
mpls traffic-eng tunnels
serial restart-delay 0
ip rsvp bandwidth 100
router ospf 1
mpls traffic-eng router-id Loopback1
mpls traffic-eng area 0
router-id 150.1.1.1
log-adjacency-changes
network 150.1.1.1 0.0.0.0 area 0
network 172.25.1.0 0.0.0.255 area 0
network 172.25.80.1 0.0.0.0 area 0
network 192.168.1.0 0.0.0.255 area 0
network 192.168.2.0 0.0.0.255 area 0
R2
ip cef
mpls traffic-eng tunnels
interface Loopback0
ip address 150.2.2.2 255.255.255.255
interface Loopback1
description MPLS Traffic Eng
ip address 172.25.2.1 255.255.255.0
interface Tunnel0
ip unnumbered Loopback1
tunnel destination 172.25.1.1
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 2 2
tunnel mpls traffic-eng bandwidth 200
tunnel mpls traffic-eng path-option 2 dynamic
interface Serial1/1
ip address 192.168.1.2 255.255.255.0
ip ospf priority 0
mpls traffic-eng tunnels
serial restart-delay 0
ip rsvp bandwidth 200
router ospf 1
mpls traffic-eng router-id Loopback1
mpls traffic-eng area 0
router-id 150.2.2.2
log-adjacency-changes
network 150.2.2.2 0.0.0.0 area 0
network 172.25.2.0 0.0.0.255 area 0
network 192.168.1.0 0.0.0.255 area 0Hi,
Could you post the "show ip explicit-paths" output. I couldn't locate the explicit path identifier 2 config from your running-config. May be you missed to configure the explicit path?
Sample config for R1:
Router(config)#ip explicit-path identifier 2
Router(cfg-ip-expl-path)#next-address 192.168.1.2
Explicit Path identifier 2:
1: next-address 192.168.1.2
Router(cfg-ip-expl-path)#do show ip exp
PATH 2 (strict source route, path complete, generation 3)
1: next-address 192.168.1.2
Router(cfg-ip-expl-path)#
Thanks,
Vijay -
External files need explicit path
I have a interesting quirk in the Flash app I'm working on.
I'm finding that everything that is loaded externally (movie clips,
XML files, even the skin for FLVPlayer controls) needs a full path
in order to be found, even though the files are all in the same
directory as the player. In other words something like "
http://www.mydomain.com/subdir1/subdir2/file.swf"
versus just "file.swf". The interesting thing is this same
application works fine in other places without a full path. The
difference is that for the other places, the player is in the same
directory as the HTML and for my use it is one level down. So my
HTML is in subdir1, myApp.swf is in subdir1/subdir2 and the HTML
params are src='subdir2/myApp.swf', movie='subdir2/myApp.swf',
id='myApp.swf', name=myApp.swf. Do id and name need to have the
directory path too? If myApp.swf and the files it loads are all in
subdir2 why can't it find them without an explicit path?Hello dubwai,
One thing you might want to check when setting your path is if the directory that you're adding to the path variable has spaces in it, where Microsoft Internet does...
I am writing you from a Solaris box, so can't check how to include spaces in the PATH variable, but I believe you would enclose the directory with " " signs? I know you placed " " signs in your question, but you also did for "iexplore" and "iexplore.exe", so didn't know if you actually enclosed them, or if they were just used to emphasize the strings....
Hope this helps,
Ming
Developer Technical Support
http://www.sun.com/developers/support -
Explicit path need to run iexplore.exe
I am having a wierd problem with windows.
When I run programs using the exec command, I generally can use strings like "java -jar JarFile.jar" as long as java.exe is in the path variable. For some odd reason, this doesn't work for internet explorer. I can run IE if I use the following exec string:
"C:/Program Files/Plus!/Microsoft Internet/iexplore.exe"
but
"iexplore"
and
"iexplore.exe"
don't work even if I specfically add "C:/Program Files/Plus!/Microsoft Internet" to the path variable. Does anyone have any idea why this is so?Hello dubwai,
One thing you might want to check when setting your path is if the directory that you're adding to the path variable has spaces in it, where Microsoft Internet does...
I am writing you from a Solaris box, so can't check how to include spaces in the PATH variable, but I believe you would enclose the directory with " " signs? I know you placed " " signs in your question, but you also did for "iexplore" and "iexplore.exe", so didn't know if you actually enclosed them, or if they were just used to emphasize the strings....
Hope this helps,
Ming
Developer Technical Support
http://www.sun.com/developers/support -
Hi
Can you please clarify my understanding of MPLS-TE path-options and how the head-end fails over to less-preferred paths when using inter-area tunnels? Assuming I have a working inter-area tunnel with multiple explicit paths defined:
The tunnel head-end will switch from path-option 1 to path-option 2 based on RSVP events only, eg. tunnel preemption or lack of bandwidth somewhere along path 1.
A node or link failure along path 1 will not trigger the switch to path-option 2 it will drop the tunnel instead.
Is this the expected behaviour? Is there another way to trigger the failover to the second path?
Thanks in advanceTo clarify when you mention a node failure is the node in the same area as the headend or a remote area?
When you contrast preemption vs node fail you say switch paths vs drop paths. Can you explain exactly what you mean here?
It's logical that you would tear down a tunnel if a node failed and try to signal again. I think you are referring to when preemption occurs the tunnel has some time to signal the new path and switch. Ultimately if the new path is not found eventually the same outcome will be reached.
Actually preemption is tunable between hard and soft which are tear down and reoptimize respectively.
Maybe my answer just introduces new questions..
HTH,
Matt -
Ping Packet Loss across MPLS TE Tunnels
Hello...Please Help,
I have a Single Area OPSF network running across 4 main routers via GigEth Ckts. The OSPF Network is working correctly. I recently implemented MPLS TE creating two Tunnels - One Explicit Path and One Dynamic Path. Two of the Routers also have a T1 Frame Relay Link over which the Explicit path is configured. It is up and woking but I am experiencing 50-60 percent packet loss when pinging between these PE routers. When I force it to the dynamic tunnel it follows the same FR path and experiences the same packet loss. There is no packet loss anywhere else in the network.
This is a Lab environment w/three LAN's Two 7206VXR & Two 3745 routers and Three 3550 Switches - one per LAN
Suggestions?Thank You for your response. The problem may not be an MPLS TE problem.
But would my "path-option" and "priority" being set the same for the Dynamic and Explicit Tunnels cause one tunnel to come up and the other go down and cease to signal. Right now I have one or the other working when viewed w/the "show mpls traffic-eng tunnels" command. If I take one down the other works.
The IPs are 10.1.101.1 & 2/30 respectively for the FR Link. That was a Typo...I have corrected it.
The FR interfaces are not SubInt's as the Serial Interface holds the IP address. These are strictly Point to Point but I have the "IP OSPF Network Broadcast" command set and OSPF going across them.
I have SubInt's set on the Gi0/3 Interface.
Gi0/3.1 & 3.10 for VLAN's 1 & 10
There are not any drops when pinging from Within the routers "Interface to Interface".
But when I ping the LAN Node to Node or from within the Router "if" I do not specify an "interface source" I receive the drops.
The result is the same from either side of the Network on both of the 7206 Routers.
Thanks, Kevin -
Hi,
I have an Explicit Path configured on a tunnel as 1 and a dynamic path as 2.
If a link fails in the core FRR fails over, then after a while the tunnel takes teh dynamic path. However when the link recovers the tunnel stays on the dynamic path.
My question is: how can i force to take the explicit path again?
R1#show mpls traffic-eng tunnels tunnel 1
Name: R1_t1 (Tunnel1) Destination: 2.2.2.2
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 2, type dynamic (Basis for Setup, path weight 3)
path option 1, type explicit 1
Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 0 [0] bw-based
auto-bw: disabled
Active Path Option Parameters:
State: dynamic path option 2 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
InLabel : -
OutLabel : FastEthernet0/1, 28
Next Hop : 10.15.0.5
RSVP Signalling Info:
Src 1.1.1.1, Dst 2.2.2.2, Tun_Id 1, Tun_Instance 32
RSVP Path Info:
My Address: 10.15.0.1
Explicit Route: 10.15.0.5 10.56.0.5 10.56.0.6 10.26.0.6
10.26.0.2 2.2.2.2
Record Route: NONE
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
RSVP Resv Info:
Record Route: 5.5.5.5(28) 6.6.6.6(33)
2.2.2.2(3)
Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
Shortest Unconstrained Path Info:
Path Weight: 3 (TE)
Explicit Route: 10.15.0.1 10.15.0.5 10.56.0.5 10.56.0.6
10.26.0.6 10.26.0.2 2.2.2.2
History:
Tunnel:
Time since created: 1 hours, 48 minutes
Time since path change: 55 seconds
Number of LSP IDs (Tun_Instances) used: 32
Current LSP: [ID: 32]
Uptime: 58 seconds
Selection: reoptimization
Prior LSP: [ID: 30]
ID: path option 1 [30]
Removal Trigger: re-route path error
Last Error: RSVP:: Path Error from 10.13.0.3: Notify: Tunnel locally repaired (flags 0)
Thx!Hi,
By default, the re-optimization is around 1 hour. You can use the below command to speed up the re-optimization,
mpls traffic-eng reoptimize timers frequence <seconds>
With this command, the router after the seconds mentioned will check for better path for existing LSP (to see if primary path option is available) and use it if available.
-Nagendra -
MPLS-TE and use of /31 addressing on backbone uplinks (P2P)
Hi, we're recently renumbered a number of our backbone links from /30 to /31.
Shortly after doing so, we noticed that a number of our MPLS-TE tunnels had gone down within portions of the network that were renumbered and I'm wondering whether or not 1) this is a simple coincidence? or 2), whether any of you have experienced the same thing as the result of a /30 to /31 migration?
The impacted devices are several CSR-3 pairs that are all running IOS-XR 4.2.4 which is fully compliant with RFC3021.
Thanks in advance,
AndrewThe problem and the solution have been identified. MPLS-TE is fully compatible with /31 addressing. For reasons that are beyond the scope of the current post (subject of a case), Cisco IOS / IOS XR maintain in the MPLS-TE dB (SPF) the old IP addresses as phantoms until such time that the "offending" interface is shut/no shut) at which time the MPLS-TE tunnels come back up.
Performing a debug mpls traffic-eng path lookup on either tunnel endpoint help identify the problem.
Oct 18 13:31:26: TE-PCALC-PATH: create_path_hoplist:ip addr A.B.C.D unknown (the old interface IP address)
Once you identify the address, you need to find the device's new IP address (hopefully you saved the before/after addresse are in a migration worksheet or equivalent), connect to the router and do a shut/no shut of the interface that was addressed using the old IP address that appears in your debug as "unknown.". You may need to perform the debug serveral times in order to find all the offending interfaces that still have the phantom IPs in their dBs (they jump from one interface to another when the explicit path is long). Once the entire chain is done, the tunnel will come back up
In researching this problem I was unable to find a single reference either on google or this forum. I'm hopeful that if anyone runs into this problem they'll find my post since it'll save them lots of time. In truth, L2VPN, VRF, L2VPN in VRF in VRF, VRF in VRF, logical-systems, etc all make networking hard enough, but when you add "phantom addresses" that shouldn't even be there to the equation, it makes things even harder
Kind regards,
Andrew -
Hello:
I use IOS code 7200 Software (C7200-SPSERVICESK9-M), Version 12.2(33)SRC3
at default MPLS FRR works fine
when I shutdown pos interface on primary path, FRR works fine, but after I bring back pos interface, I noticed tu1 still use backup path
until I shut and no shut tu1
anyone could shred a light?
thx,
~mikeHi Mike,
Instead of dynamic path option, configure an explicit path with "192.168.3.1" as strict hop and try the scenario.
In this case, when pos interface on primary path goes down the traffic will be rerouted via backup tunnel and the primary path will be retried for every 30 seconds. When the interface is back up, primary path signaling will succeed and tunnel will no longer use the backup path.
When tunnel uses the backup tunnel, "show mpls traffic-eng fast database" will display it's status as "active".
With dynamic path option, the tunnel will calculate a path which will be same as the backup tunnel path and it'll look like it's using the backup tunnel. To use the best path you've to trigger reoptimization (manual/periodic/event-linkUp).
Thanks,
Vijay -
Hi,
Trying to build out an xconnect to follow a specific path (a longer path). I cannot get the tunnel to come up. I dont know what I missed. everything else looks ok. All interfaces are up and working, except the tunnel itself.
I've included the MPLS portion of the config, if I missed something let me know. I did enable the MPLS-TE in OSPF on the routers inbetween. I have connectivity inbetween.
Router 1:
ip cef
mpls label protocol ldp
mpls traffic-eng tunnels
mpls label protocol ldp
mpls traffic-eng tunnels
pseudowire-class 5001
encapsulation mpls
preferred-path interface Tunnel5001
interface Loopback10
ip address 10.201.1.4 255.255.255.255
interface Tunnel5001
ip unnumbered Loopback10
tunnel mode mpls traffic-eng
tunnel destination 10.201.1.2
tunnel mpls traffic-eng path-option 1 explicit name strict
tunnel mpls traffic-eng path-selection metric te
interface FastEthernet2/0
xconnect 10.201.1.2 5001 encapsulation mpls pw-class 5001
router ospf 100
router-id 10.201.1.4
mpls traffic-eng router-id Loopback10
mpls traffic-eng area 0
ip route 10.201.1.2 255.255.255.255 Tunnel5001
ip explicit-path name strict enable
next-address 10.201.1.3
next-address 10.201.1.1
next-address 10.201.1.2
Router 2:
ip cef
mpls label protocol ldp
mpls traffic-eng tunnels
pseudowire-class 5001
encapsulation mpls
preferred-path interface Tunnel5001
interface Loopback10
ip address 10.201.1.2 255.255.255.255
interface Tunnel5001
ip unnumbered Loopback10
tunnel mode mpls traffic-eng
tunnel destination 10.201.1.4
tunnel mpls traffic-eng path-option 1 explicit name strict
tunnel mpls traffic-eng path-selection metric te
interface FastEthernet2/0
xconnect 10.201.1.4 5001 encapsulation mpls pw-class 5001
router ospf 102
router-id 10.201.1.2
mpls traffic-eng router-id Loopback10
mpls traffic-eng area 0
ip route 10.201.1.4 255.255.255.255 Tunnel5001
ip explicit-path name strict enable
next-address 10.201.1.1
next-address 10.201.1.3
next-address 10.201.1.4
From router 1. Both Router 1 and Router 2 show the samething.
show mpls l2transport vc detail
Local interface: Fa2/0 up, line protocol up, Ethernet up
Destination address: 10.201.1.2, VC ID: 5001, VC status: up
Output interface: Fa1/1, imposed label stack {22}
Preferred path: Tunnel5001, no route
Default path: active
Next hop: 192.168.102.13
Create time: 00:10:13, last status change time: 00:10:13
Last label FSM state change time: 00:10:13
Signaling protocol: LDP, peer 10.201.1.2:0 up
Targeted Hello: 10.201.1.4(LDP Id) -> 10.201.1.2, LDP is UP
Status TLV support (local/remote) : enabled/supported
LDP route watch : enabled
Label/status state machine : established, LruRru
Last local dataplane status rcvd: No fault
Last BFD dataplane status rcvd: Not sent
Last BFD peer monitor status rcvd: No fault
Last local AC circuit status rcvd: No fault
Last local AC circuit status sent: No fault
Last local PW i/f circ status rcvd: No fault
Last local LDP TLV status sent: No fault
Last remote LDP TLV status rcvd: No fault
Last remote LDP ADJ status rcvd: No fault
MPLS VC labels: local 22, remote 22
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
Control Word: On (configured: autosense)
Dataplane:
SSM segment/switch IDs: 4101/4100 (used), PWID: 1
VC statistics:
transit packet totals: receive 0, send 0
transit byte totals: receive 0, send 0
transit packet drops: receive 0, seq error 0, send 0
show int tun 5001
Tunnel5001 is up, line protocol is down
Hardware is Tunnel
Interface is unnumbered. Using address of Loopback10 (10.201.1.4)
MTU 17936 bytes, BW 100 Kbit/sec, DLY 50000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source 10.201.1.4, destination 10.201.1.2
Tunnel protocol/transport Label Switching
Tunnel transmit bandwidth 8000 (kbps)
Tunnel receive bandwidth 8000 (kbps)
Last input never, output never, output hang never
Last clearing of "show interface" counters 00:27:10
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped outHi,
One issue what i can see is, you have mentioned loopback ips in the explicit-path not the interface ip addresses. This can not be strict path and you have to mention next-address as loose (which means router will refer IGP to reach the next-hop)
ip explicit-path name strict enable
next-address 10.201.1.1
next-address 10.201.1.3
next-address 10.201.1.4
Correct way
ip explicit-path name strict enable
next-address loose 10.201.1.1
next-address loose 10.201.1.3
next-address loose 10.201.1.4
To troubleshoot TE
- first you can remove the explicit path and try to bring it up with dynamic path, which will help to confirm that configuration is ok on all routers in the path
- i hope you have configured "ip rsvp" on all physical intrfaces.
- If with dynamic path option also link does not come up, please share output of command "show mpls traffic-eng tunnels tunnel5001
--Pls dont forget to rate helpful posts--
Regards,
Akash -
I try to configure CoPP on 7600 sup7203BXL,
when I apply on Control-Plane, then the MPLS TE tunnel goes down.
Can anyone help ?
Cisco RSVP is port 3455 ?
I do not have any packet match port 3455.
Extended IP access list cp-class-default-in
10 permit ip any any (82250 matches)
Extended IP access list cp-critical-in
10 permit ospf any host 224.0.0.5 (53601 matches)
20 permit ospf any host 224.0.0.6
30 permit ospf any any (145 matches)
40 permit tcp any any eq bgp (2 matches)
50 permit tcp any eq bgp any (50725 matches)
60 permit tcp any any eq 646 (4457 matches)
70 permit tcp any eq 646 any (3222 matches)
80 permit udp any any eq 646 (49019 matches)
90 permit udp any eq 646 any
110 permit tcp any any eq 3455
120 permit udp any any eq 3455
130 permit tcp any eq 3455 any
140 permit udp any eq 3455 any
Extended IP access list cp-important-in
10 permit tcp any any eq 22 (238 matches)
20 permit tcp any eq 22 any
30 permit tcp any any eq telnet (7059 matches)
40 permit tcp any eq telnet any
50 permit tcp any any eq tacacs (1 match)
60 permit tcp any eq tacacs any (1219 matches)
70 permit udp any any eq ntp (47 matches)
80 permit udp any eq ntp any
90 permit udp any any eq snmp (89625 matches)
Extended IP access list cp-normal-in
10 permit icmp any any echo (267766 matches)
20 permit icmp any any echo-reply (5394 matches)
30 permit icmp any any parameter-problem (499 matches)
40 permit icmp any any ttl-exceeded (17 matches)
50 permit icmp any any port-unreachable (8 matches)
60 permit icmp any any time-exceeded
Policy Map control-plane-in
Class cp-critical-in
police cir 1000000000 bc 31250000
conform-action transmit
exceed-action transmit
Class cp-important-in
police cir 1000000 bc 312500
conform-action transmit
exceed-action drop
Class cp-normal-in
police cir 100000 bc 31250
conform-action transmit
exceed-action drop
Class cp-class-default-in
police cir 100000 bc 31250
conform-action drop
exceed-action drop
Extended IP access list cp-class-default-in
10 permit ip any any (82250 matches)
Extended IP access list cp-critical-in
10 permit ospf any host 224.0.0.5 (53601 matches)
20 permit ospf any host 224.0.0.6
30 permit ospf any any (145 matches)
40 permit tcp any any eq bgp (2 matches)
50 permit tcp any eq bgp any (50725 matches)
60 permit tcp any any eq 646 (4457 matches)
70 permit tcp any eq 646 any (3222 matches)
80 permit udp any any eq 646 (49019 matches)
90 permit udp any eq 646 any
110 permit tcp any any eq 3455
120 permit udp any any eq 3455
130 permit tcp any eq 3455 any
140 permit udp any eq 3455 any
Extended IP access list cp-important-in
10 permit tcp any any eq 22 (238 matches)
20 permit tcp any eq 22 any
30 permit tcp any any eq telnet (7059 matches)
40 permit tcp any eq telnet any
50 permit tcp any any eq tacacs (1 match)
60 permit tcp any eq tacacs any (1219 matches)
70 permit udp any any eq ntp (47 matches)
80 permit udp any eq ntp any
90 permit udp any any eq snmp (89625 matches)
Extended IP access list cp-normal-in
10 permit icmp any any echo (267766 matches)
20 permit icmp any any echo-reply (5394 matches)
30 permit icmp any any parameter-problem (499 matches)
40 permit icmp any any ttl-exceeded (17 matches)
50 permit icmp any any port-unreachable (8 matches)
60 permit icmp any any time-exceeded
Policy Map control-plane-in
Class cp-critical-in
police cir 1000000000 bc 31250000
conform-action transmit
exceed-action transmit
Class cp-important-in
police cir 1000000 bc 312500
conform-action transmit
exceed-action drop
Class cp-normal-in
police cir 100000 bc 31250
conform-action transmit
exceed-action drop
Class cp-class-default-in
police cir 100000 bc 31250
conform-action drop
exceed-action dropIt seems the RSVP signalling problem.
Router #sho mpls traffic-eng tunnels
Name: vocom_hinet (Tunnel9181) Destination: 203.160.227.98
Status:
Admin: up Oper: down Path: valid Signalling: RSVP signalling proceeding
path option 1, type explicit TP765_TP1243_G1 (Basis for Setup, path weight 2)
path option 2, type explicit TP765_TP1243_G2
path option 3, type explicit TP765_TP1243_G3
Config Parameters:
Bandwidth: 64 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 64 bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
RSVP Signalling Info:
Src 203.160.227.53, Dst 203.160.227.98, Tun_Id 9181, Tun_Instance 2903
History:
Tunnel:
Time since created: 446 days, 9 hours, 52 minutes
Time since path change: 1 minutes, 19 seconds
Number of LSP IDs (Tun_Instances) used: 2903
Current LSP:
Setup Time: 3 minutes, 40 seconds remaining
Selection: reoptimization
Prior LSP:
ID: path option 1 [2902]
Removal Trigger: label reservation removed
Path Option 3:
Last Error: PCALC:: No addresses to connect 203.78.186.225 to 203.160.227.98
Name: vocom_HK (Tunnel9182) Destination: 203.160.227.27
Status:
Admin: up Oper: down Path: valid Signalling: RSVP signalling proceeding
path option 1, type explicit vocom_HK (Basis for Setup, path weight 6)
Config Parameters:
Bandwidth: 64 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 64 bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
RSVP Signalling Info:
Src 203.160.227.53, Dst 203.160.227.27, Tun_Id 9182, Tun_Instance 1471
History:
Tunnel:
Time since created: 446 days, 9 hours, 52 minutes
Time since path change: 1 minutes, 25 seconds
Number of LSP IDs (Tun_Instances) used: 1471
Current LSP:
Setup Time: 3 minutes, 34 seconds remaining
Selection: reoptimization
Prior LSP:
ID: path option 1 [1470]
Removal Trigger: label reservation removed
Name: cmstr-Vocom_CT (Tunnel9184) Destination: 203.160.227.114
Status:
Admin: up Oper: down Path: valid Signalling: RSVP signalling proceeding
path option 1, type explicit vocom_ct (Basis for Setup, path weight 5)
Config Parameters:
Bandwidth: 64 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 64 bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
RSVP Signalling Info:
Src 203.160.227.53, Dst 203.160.227.114, Tun_Id 9184, Tun_Instance 143
History:
Tunnel:
Time since created: 227 days, 45 minutes
Time since path change: 1 minutes, 26 seconds
Number of LSP IDs (Tun_Instances) used: 143
Current LSP:
Setup Time: 3 minutes, 33 seconds remaining
Selection: reoptimization
Prior LSP:
ID: path option 1 [142]
Removal Trigger: label reservation removed
Name: CHTG-Virtela-2M(Burst10M) (Tunnel9185) Destination: 203.160.227.114
Status:
Admin: up Oper: down Path: valid Signalling: RSVP signalling proceeding
path option 1, type explicit CHTG-Virtela (Basis for Setup, path weight 5)
Config Parameters:
Bandwidth: 64 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 64 bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
RSVP Signalling Info:
Src 203.160.227.53, Dst 203.160.227.114, Tun_Id 9185, Tun_Instance 151
History:
Tunnel:
Time since created: 163 days, 7 hours, 6 minutes
Time since path change: 1 minutes, 26 seconds
Number of LSP IDs (Tun_Instances) used: 151
Current LSP:
Setup Time: 3 minutes, 33 seconds remaining
Selection: reoptimization
Prior LSP:
ID: path option 1 [150]
Removal Trigger: label reservation removed
Name: TFN_CT (Tunnel9186) Destination: 203.160.227.98
Status:
Admin: up Oper: down Path: valid Signalling: RSVP signalling proceeding
path option 1, type explicit TFN_CT (Basis for Setup, path weight 101)
Config Parameters:
Bandwidth: 64 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 64 bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
RSVP Signalling Info:
Src 203.160.227.53, Dst 203.160.227.98, Tun_Id 9186, Tun_Instance 63
History:
Tunnel:
Time since created: 85 days, 20 hours, 42 minutes
Time since path change: 1 minutes, 19 seconds
Number of LSP IDs (Tun_Instances) used: 63
Current LSP:
Setup Time: 3 minutes, 40 seconds remaining
Selection: reoptimization
Prior LSP:
ID: path option 1 [62]
Removal Trigger: label reservation removed
Name: TFN_CNC (Tunnel9187) Destination: 203.160.227.98
Status:
Admin: up Oper: down Path: valid Signalling: RSVP signalling proceeding
path option 1, type explicit TFN_CNC (Basis for Setup, path weight 101)
Config Parameters:
Bandwidth: 64 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 64 bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
RSVP Signalling Info:
Src 203.160.227.53, Dst 203.160.227.98, Tun_Id 9187, Tun_Instance 195
History:
Tunnel:
Time since created: 85 days, 20 hours, 43 minutes
Time since path change: 27 seconds
Number of LSP IDs (Tun_Instances) used: 195
Current LSP:
Setup Time: 4 minutes, 32 seconds remaining
Selection: reoptimization
Prior LSP:
ID: path option 1 [194]
Removal Trigger: label reservation removed -
Hi,
I'm studing for MPLS exam and after reading the documentation some aspects about MPLS-TE are still not clear .
I hope you can help me to clarify some concepts:
1)Is RSVP a requirement on every router link of the ISP when we are using dynamic tunnel computation considering that a tunnel could change his path?
2)Is Constrant-based routing(CBR)used when the tunnel is configured using an explicit path?Hello Marco,
MPLS TE are unidirectional and also RSVP reservations are unidirectional.
Said this the answers are:
1) yes an alternate path can be used only if it has enough RSVP resources to satisfy the requests in the RSVP tunnel setup message.
resources are consumed outbound towards destination node
2) yes every possible path dynamic or explicit uses constrained based routing that means takes in account resources and resource current usage.
For this reason an MPLS TE with only a path option describing an explict path will fail if not enough resources are available on one of the specified links on the path
Hope to help
Giuseppe -
MPLS TE tunnels doesn't come up after BGP arrived at the scene
Hi folks,
I was running a little lab where I had an mpls te tunnel running fine from one router located at the border of the network to the other, I was using ISIS as the IGP. Everything was fine untill I added BGP to the lab and suddenly the tunnel turn down. I want to know if I got to add an additional configuration to my PE routers to succesfully bring up my tunnel like before. My tunnel's explicits path were LSR-PE2 and LSR PE1. My topology looks like this.
LSR
eBGP / \ eBGP
ASx ------------ PE1 ----------------- PE2--------------ASy
iBGP
Thanks,
Francis.Here I leave the configurations and I correct myself about the network topology, I added a pic about the exact topology too. The tunnel is built PE1-R1-R3.
PE1 - R0
clns routing
mpls label protocol ldp
mpls traffic-eng tunnels
interface Loopback0
ip address 10.201.0.0 255.255.255.255
ip router isis
interface Tunnel0
ip unnumbered Loopback0
tunnel destination 10.201.0.3
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng priority 5 5
tunnel mpls traffic-eng bandwidth 1000
tunnel mpls traffic-eng path-option 10 explicit name te
no routing dynamic
interface FastEthernet0/0
bandwidth 100000
ip address 10.200.0.1 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
ip rsvp bandwidth 75000
ip rsvp resource-provider none
interface FastEthernet1/0
bandwidth 100000
ip address 10.200.0.5 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
ip rsvp bandwidth 85000
ip rsvp resource-provider none
interface FastEthernet2/0
ip address 190.80.239.1 255.255.255.252
duplex auto
speed auto
router isis
net 49.0123.0000.0000.0000.00
is-type level-1
metric-style wide
mpls traffic-eng router-id Loopback0
mpls traffic-eng level-1
router bgp 6400
no synchronization
bgp log-neighbor-changes
network 190.80.239.0 mask 255.255.255.252
neighbor 10.201.0.4 remote-as 6400
neighbor 10.201.0.4 password cisco
neighbor 10.201.0.4 update-source Loopback0
neighbor 190.80.239.2 remote-as 1630
neighbor 190.80.239.2 password cisco
no auto-summary
ip explicit-path name te enable
next-address 10.201.0.1
next-address 10.201.0.3
mpls ldp router-id Loopback0
LSR- R1
clns routing
mpls label protocol ldp
mpls traffic-eng tunnels
interface Loopback0
ip address 10.201.0.1 255.255.255.255
ip router isis
interface FastEthernet0/0
bandwidth 100000
ip address 10.200.0.6 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls mtu 1508
mpls traffic-eng tunnels
ip rsvp bandwidth 75000
ip rsvp resource-provider none
interface Serial1/0
bandwidth 1500
ip address 10.200.0.9 255.255.255.252
ip router isis
encapsulation ppp
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
serial restart-delay 0
ip rsvp bandwidth 1200
ip rsvp resource-provider none
interface Ethernet2/0
bandwidth 10000
ip address 10.200.0.13 255.255.255.252
ip router isis
full-duplex
mpls label protocol ldp
mpls ip
mpls mtu 1508
mpls traffic-eng tunnels
ip rsvp bandwidth 7500
ip rsvp resource-provider none
router isis
net 49.0123.0000.0000.0001.00
is-type level-1
metric-style wide
mpls traffic-eng router-id Loopback0
mpls traffic-eng level-1
mpls ldp router-id Loopback0
LSR-R3
ip cef
no ip domain lookup
mpls label protocol ldp
mpls traffic-eng tunnels
interface Loopback0
ip address 10.201.0.3 255.255.255.255
ip router isis
interface Tunnel0
ip unnumbered Loopback0
tunnel destination 10.201.0.0
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng priority 5 5
tunnel mpls traffic-eng bandwidth 1000
tunnel mpls traffic-eng path-option 10 explicit name te
no routing dynamic
interface FastEthernet0/0
bandwidth 100000
ip address 10.200.0.2 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
ip rsvp bandwidth 75000
ip rsvp resource-provider none
interface Serial1/0
bandwidth 1500
ip address 10.200.0.10 255.255.255.252
ip router isis
encapsulation ppp
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
serial restart-delay 0
isis metric 1677214
ip rsvp bandwidth 1200
interface Ethernet2/0
bandwidth 10000
ip address 10.200.0.14 255.255.255.252
ip router isis
full-duplex
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
ip rsvp bandwidth 7500
ip rsvp resource-provider none
interface FastEthernet3/0
bandwidth 100000
ip address 10.200.0.17 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
isis metric 1677214
ip rsvp bandwidth 75000
router isis
net 49.0123.0000.0000.0003.00
is-type level-1
metric-style wide
mpls traffic-eng router-id Loopback0
mpls traffic-eng level-1
ip explicit-path name te enable
next-address 10.200.0.13
next-address 10.201.0.0
mpls ldp router-id Loopback0
PE2- R4
ip cef
no ip domain lookup
clns routing
mpls label protocol ldp
mpls traffic-eng tunnels
interface Loopback0
ip address 10.201.0.4 255.255.255.255
ip router isis
interface FastEthernet0/0
bandwidth 10000
ip address 10.200.0.18 255.255.255.252
ip router isis
duplex auto
speed auto
mpls label protocol ldp
mpls ip
mpls traffic-eng tunnels
ip rsvp bandwidth 75000
interface FastEthernet1/0
ip address 190.80.239.5 255.255.255.252
duplex auto
speed auto
router isis
net 49.0123.0000.0000.0004.00
is-type level-1
metric-style wide
mpls traffic-eng router-id Loopback0
mpls traffic-eng level-1
router bgp 6400
no synchronization
bgp log-neighbor-changes
network 190.80.239.4 mask 255.255.255.252
neighbor 10.201.0.0 remote-as 6400
neighbor 10.201.0.0 password cisco
neighbor 10.201.0.0 update-source Loopback0
neighbor 190.80.239.6 remote-as 36256
neighbor 190.80.239.6 password cisco
no auto-summary
mpls ldp router-id Loopback0
Maybe you are looking for
-
Standard idoc type for Vendor invoices
Hi All, Can anyone tell me if any <b>standard idoc type for Vendor invoice(Cleared items)</b> exists and if any standard report is there to populate and distribute that idoc? I want the fields bukrs,belnr,lifnr,bldat,cpudt,zfbdt,zterm,xblnr,wa
-
Web Service Client - SOAP/jms: Specific response queue (not default queue)?
Hi @ll I try to define a specific jms response queue for a web service client that communicates SOAP/jms, running on a WLS 9.2. The web service itself runs also on a WLS 9.2 where also the request and response queues are located. By default the clien
-
What is the use of bluetooth on/off ?
What is the use of bluetooth 0n/off in general settings?
-
New version of itunes won't open on my macbook
I have just downloaded the new version of itunes and now it won't open on my macbook. Any suggestions?
-
Does the iTunes Wish list have limited capacity?
I have a long list of albums, songs and TV shows to buy, and I added most of them to the wish list, however when I checked the list, I found far less items than I know I added...! Does the wish list accept a certain number of items only? Or is there