The MPLS-OPS Archive

[Roger Clark Williams <rogerw@nordlink.com>]

Doug, you didn't mention switches but I thought I might add that MTU issues 
can sometimes screw up VPNs. Switches that are not MPLS-aware can drop 
frames considered giants or the like.

Roger Williams


>X-MindSpring-Loop: rogerw@nordlink.com
>Resent-Date: Tue, 30 Sep 2003 07:51:36 -0400
>X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to 
>mpls-ops-request@mplsrc.com using -f
>From: "Philip Gill" <philip.gill@telefonica.de>
>To: "Doug Legge" <Doug.Legge@BerkeleyGroup.co.uk>
>Cc: <mpls-ops@mplsrc.com>
>Subject:  [MPLS-OPS]: Ping vrf <vrfname>
>Date: Tue, 30 Sep 2003 13:43:52 +0200
>X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
>Importance: Normal
>Resent-From: mpls-ops@mplsrc.com
>X-Mailing-List: <mpls-ops@mplsrc.com> archive/latest/6377
>X-Loop: mpls-ops@mplsrc.com
>Resent-Sender: mpls-ops-request@mplsrc.com
>Resent-Bcc:
>
>
>hi Doug
>
>looks like you are getting the VPN label but not the next hop label
>
>on PE1, try doing
>sh mpls forwarding-table | include 192.168.254.254
>
>on PE2, try
>sh mpls forwarding-table | include (loopback address PE1)
>
>under the 2nd column, you should see outgoing label(s)
>Local  Outgoing    Prefix            Bytes tag  Outgoing   Next Hop
>tag    tag or VC   or Tunnel Id      switched   interface
>
>if either or both loopbacks have no label value, there is an outer label
>problem,
>- ensure you are running MPLS on the interfaces, LDP adjacencies are up
>(show mpls ldp neighbor) and that loopbacks and interfaces connecting PE1, P
>and PE2 are in the routing process.
>
>regards
>Phil
>
>-----Ursprüngliche Nachricht-----
>Von: Doug Legge [mailto:Doug.Legge@BerkeleyGroup.co.uk]
>Gesendet: Dienstag, 30. September 2003 13:11
>An: mpls-ops@mplsrc.com
>Betreff: [MPLS-OPS]: Ping vrf <vrfname>
>
>
>I have an issue with our IP VPN test lab.
>
>CE1 running rip v2 (eth0/0 - 10.223.0.1) in vrf berkeleyHomes, which can see
>all connected serials and it's neighbour within the vrf 10.212.0.1. It can
>ping PE1 its connected neighbour but not CE3 (10.212.0.1).
>
>PE I can ping vrf berkeleyHomes 10.223.0.1 but not 10.212.0.1 yet it appears
>to see all routes - sh ip route vrf berkeleyHomes and learns about
>10.212.0.1 via BGP on PE2 (loop0 192.168.254.254)
>
> >From PE1 you can telnet across the two P nodes to PE2 (192.168.254.254).
>Once on PE2 you find the opposite, all routes are visible but whereas PE2
>can ping 10.212.0.1 it can't ping 10.223.0.1
>
>I had this up and running last week and then the next morning came in to
>find that I had this problem. I've run all the sh tag commands I can think
>of and everything seems to be in order. This is actually starting to hurt
>now, so any help greatly appreciated from anyone who may have experienced
>this before.
>
>Thanks
>
>
>Doug
>
>-------
>The MPLS-OPS Mailing List
>Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>
>-------
>The MPLS-OPS Mailing List
>Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml


-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml