From: Ian Blaney (ian.blaney@gmail.com)
Date: Mon Jul 30 2007 - 18:51:15 ART
I managed to get the tunnel to come up but I am not sure why it was not
working before.
A previous IGP OSPF task asks you to change the network type to
non-broadcast and use the neighbor command so that no other devices can
intercept any OSPF traffic between R6 and R2 which are the first 2 devices
in the tunnel path..
I configured on R6 and a similar config on R2
R6
interface Ethernet0/1
ip ospf network non-broadcast
router ospf 1
neighbor 131.1.26.2
R2
interface FastEthernet0/0
ip ospf network non-broadcast
router ospf 1
neighbor 131.1.26.6
With this config the tunnel does not come up but if I remove the ip ospf
network non-broadcast and use the default broadcast the tunnel comes up.
Does RSVP not work over a non-broadcast network or am I misunderstanding
something here???
Ian
On 7/30/07, Ian Blaney <ian.blaney@gmail.com> wrote:
>
> Hello
>
> Could some please tell me what this message means. I am working on lab1
> section 4.4 of the IE SP workbook. I can create a tunnel in one direction
> but somehow not in the other direction.
>
> %MPLS_TE-3-CONSISTENCY: Path lookup returned path that didn't pass
> verification: -Traceback= 0x60402F18 0x611DA574 0x611DAAA4 0x611E3E90
> 0x611E4840
>
> I also see show mpls traffic-eng tunnels tunn0 gives me
>
> Last Error: PCALC:: Can't use link 131.1.26.6 on node 131.1.6.6
>
> This is my config
>
> interface Tunnel0
> ip unnumbered Loopback0
> tunnel destination 131.1.4.4
> tunnel mode mpls traffic-eng
> tunnel mpls traffic-eng autoroute announce
> tunnel mpls traffic-eng priority 7 7
> tunnel mpls traffic-eng bandwidth 10000
> tunnel mpls traffic-eng path-option 2 dynamic
> no routing dynamic
>
> interface Ethernet0/1
> bandwidth 45000
> ip address 131.1.26.6 255.255.255.0
> mpls ip
> mpls traffic-eng tunnels
> ip rsvp bandwidth
> end
>
> Rack1R6#show mpls forwarding-table 131.1.4.4
> Local Outgoing Prefix Bytes tag Outgoing Next Hop
> tag tag or VC or Tunnel Id switched interface
> 20 19 131.1.4.4/32 0 Et0/1 131.1.26.2
>
> Rack1R6#show mpls traffic-eng topology path destination 131.1.4.4
> Query Parameters:
> Destination: 131.1.4.4
> Bandwidth: 0
> Priorities: 0 (setup), 0 (hold)
> Affinity: 0x0 (value), 0xFFFFFFFF (mask)
> Query Results:
> Min Bandwidth Along Path: 33750 (kbps)
> Max Bandwidth Along Path: 33750 (kbps)
> Hop 0: 131.1.26.6 : affinity 00000000, bandwidth 33750 (kbps)
> Hop 1: 131.1.23.2 : affinity 00000000, bandwidth 33750 (kbps)
> Hop 2: 131.1.34.3 : affinity 00000000, bandwidth 33750 (kbps)
> Hop 3: 131.1.34.4 : affinity 00000000, bandwidth 33750 (kbps)
> Hop 4: 131.1.4.4
>
> Rack1R6#trace 131.1.4.4
>
> Type escape sequence to abort.
> Tracing the route to 131.1.4.4
>
> 1 131.1.26.2 [MPLS: Label 19 Exp 0] 516 msec 620 msec 548 msec
> 2 131.1.23.3 [MPLS: Label 16 Exp 0] 260 msec 520 msec 236 msec
> 3 131.1.34.4 324 msec * 384 msec
>
> Rack1R6#
>
> Rack1R6#show mpls traffic-eng tunnels tunn0
>
> Name: Rack1R6_t0 (Tunnel0) Destination: 131.1.3.3
> Status:
> Admin: up Oper: down Path: not valid Signalling: Down
> path option 2, type dynamic
>
> Config Parameters:
> Bandwidth: 10000 kbps (Global) Priority: 7 7 Affinity:
> 0x0/0xFFFF
> Metric Type: TE (default)
> AutoRoute: enabled LockDown: disabled Loadshare: 10000 bw-based
> auto-bw: disabled
>
> Shortest Unconstrained Path Info:
> Path Weight: 4 (TE)
> Explicit Route: 131.1.26.6 131.1.23.3 131.1.3.3
> History:
> Tunnel:
> Time since created: 31 minutes, 14 seconds
> Path Option 2:
> Last Error: PCALC:: Can't use link 131.1.26.6 on node 131.1.6.6
>
> Thanks
> Ian Blaney
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:42 ART