[c-nsp] Very basic MPLS VPN issue
selamat pagi
ketimun at gmail.com
Tue May 4 03:41:38 EDT 2010
Yes, that was it.
> "mpls ip" was not enabled on an interface.
>
> Now everything works [?]
> (and hopefully my MPLS-troubleshooting skills improved a bit)
>
> Thank you ALL
>
>
>
> On Mon, May 3, 2010 at 11:17 PM, Yuri Bank <yuribank at gmail.com> wrote:
>
>> I agree with the previous comment. If MPLS/LDP is already enabled, check
>> to
>> make sure your LDP sessions are working correctly. Do show mpls ldp
>> neighbor
>>
>> -Yuri
>>
>> On Mon, May 3, 2010 at 12:04 PM, Shimol Shah <shimshah at cisco.com> wrote:
>>
>> > Is MPLS/LDP enabled and up between the two boxes ? Notice the outgoing
>> > "untagged" in the global LFIB on both boxes. I would have expected a
>> > "imp-null" due to PHP
>> >
>> > "sh mpls int <> int" on two boxes may tell you more.
>> >
>> >
>> >
>> >
>> > On 5/3/10 2:14 PM, selamat pagi wrote:
>> >
>> >> Setup
>> >> CE (loopback 3 on R3 vrf BLUE ) - PE1 R3 - MPLS -- PE2 R4 --
>> CE
>> >> (loopback4 on R4 vrf BLUE
>> >>
>> >> *ping between lo 3 and lo 4 does not work. *
>> >> both lo are in vrf BLUE
>> >>
>> >> - vrf routing table show routes / vpnv4 BGP neigbor is up
>> >>
>> >> R3#sh ip route vrf BLUE
>> >> !
>> >> 3.0.0.0/32 is subnetted, 1 subnets
>> >> C 3.3.3.3 is directly connected, Loopback3
>> >> 4.0.0.0/32 is subnetted, 1 subnets
>> >> B 4.4.4.4 [200/0] via 150.1.4.4, 00:07:27
>> >>
>> >>
>> >> R3#sh ip bgp vpnv4 all su
>> >> !
>> >> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
>> >> State/PfxRcd
>> >> 150.1.4.4 4 100 15 16 5 0 0 00:09:52
>> >>
>> >>
>> >>
>> >> Such a simple setup, but I just cannot figure out what's wrong.
>> >> Any feedback is highly welcome :-)
>> >>
>> >> cheers, keti
>> >>
>> >> Configuration / sh outputs
>> >> ------------------------------------
>> >> R3
>> >> ip vrf BLUE
>> >> rd 1:100
>> >> route-target export 1:100
>> >> route-target import 1:100
>> >> !
>> >> interface Loopback3
>> >> ip vrf forwarding BLUE
>> >> ip address 3.3.3.3 255.255.255.255
>> >> router bgp 100
>> >> no synchronization
>> >> bgp log-neighbor-changes
>> >> neighbor 150.1.4.4 remote-as 100
>> >> neighbor 150.1.4.4 update-source Loopback0
>> >> no auto-summary
>> >> !
>> >> address-family vpnv4
>> >> neighbor 150.1.4.4 activate
>> >> neighbor 150.1.4.4 send-community both
>> >> exit-address-family
>> >> !
>> >> address-family ipv4 vrf BLUE
>> >> redistribute connected
>> >> no auto-summary
>> >> no synchronization
>> >> exit-address-family
>> >>
>> >>
>> >> R4
>> >>
>> >> ip vrf BLUE
>> >> rd 1:100
>> >> route-target export 1:100
>> >> route-target import 1:100
>> >>
>> >> interface Loopback4
>> >> ip vrf forwarding BLUE
>> >> ip address 4.4.4.4 255.255.255.255
>> >>
>> >> router bgp 100
>> >> no synchronization
>> >> bgp log-neighbor-changes
>> >> neighbor 150.1.3.3 remote-as 100
>> >> neighbor 150.1.3.3 update-source Loopback0
>> >> no auto-summary
>> >> !
>> >> address-family vpnv4
>> >> neighbor 150.1.3.3 activate
>> >> neighbor 150.1.3.3 send-community both
>> >> exit-address-family
>> >> !
>> >> address-family ipv4 vrf BLUE
>> >> redistribute connected
>> >> no auto-summary
>> >> no synchronization
>> >> exit-address-family
>> >> !
>> >>
>> >>
>> >> R3#sh ip cef vrf BLUE 4.4.4.4 det
>> >> 4.4.4.4/32, version 2, epoch 0, cached adjacency to Serial2/0
>> >> 0 packets, 0 bytes
>> >> tag information set
>> >> local tag: VPN-route-head
>> >> fast tag rewrite with
>> >> Recursive rewrite via 150.1.4.4/32, tags imposed {19}
>> >> via 150.1.4.4, 0 dependencies, recursive
>> >> next hop 150.1.13.1, Serial2/0 via 150.1.4.4/32
>> >> valid cached adjacency
>> >> tag rewrite with
>> >> Recursive rewrite via 150.1.4.4/32, tags imposed {19}
>> >>
>> >>
>> >> R3#sh mpls forwarding-table
>> >> Local Outgoing Prefix Bytes tag Outgoing Next Hop
>> >> tag tag or VC or Tunnel Id switched interface
>> >> 16 Untagged 150.1.24.0/24 0 Se2/0 point2point
>> >> 17 Untagged 150.1.4.4/32 0 Se2/0 point2point
>> >> 18 Untagged 150.1.12.0/24 0 Se2/0 point2point
>> >> 19 Aggregate 3.3.3.3/32[V] <http://3.3.3.3/32%5BV%5D> <
>> http://3.3.3.3/32%5BV%5D> 0
>> >> R3#
>> >> R4#sh mpls forwarding-table
>> >> Local Outgoing Prefix Bytes tag Outgoing Next Hop
>> >> tag tag or VC or Tunnel Id switched interface
>> >> 16 Untagged 150.1.3.3/32 0 Se2/0.1 point2point
>> >> 17 Untagged 150.1.13.0/24 0 Se2/0.1 point2point
>> >> 18 Untagged 150.1.12.0/24 0 Se2/0.1 point2point
>> >> 19 Aggregate 4.4.4.4/32[V] <http://4.4.4.4/32%5BV%5D> <
>> http://4.4.4.4/32%5BV%5D> 0
>> >> R4#
>> >>
>> >> R4#sh ip cef vrf BLUE 3.3.3.3
>> >> 3.3.3.3/32, version 2, epoch 0, cached adjacency to Serial2/0.1
>> >> 0 packets, 0 bytes
>> >> tag information set
>> >> local tag: VPN-route-head
>> >> fast tag rewrite with
>> >> Recursive rewrite via 150.1.3.3/32, tags imposed {19}
>> >> via 150.1.3.3, 0 dependencies, recursive
>> >> next hop 150.1.24.2, Serial2/0.1 via 150.1.3.3/32
>> >> valid cached adjacency
>> >> tag rewrite with
>> >> Recursive rewrite via 150.1.
>> >> _______________________________________________
>> >> cisco-nsp mailing list cisco-nsp at puck.nether.net
>> >> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> >> archive at http://puck.nether.net/pipermail/cisco-nsp/
>> >>
>> > _______________________________________________
>> > cisco-nsp mailing list cisco-nsp at puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/cisco-nsp
>> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>> >
>> _______________________________________________
>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20100504/4a7bbab7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 360.gif
Type: image/gif
Size: 453 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20100504/4a7bbab7/attachment-0001.gif>
More information about the cisco-nsp
mailing list