[c-nsp] 6500-MSFC2(c6sup22) - MPLS

[Boštjan Fele]

I am not expert for EoMPLS but it looks a completely valid output. You are dealing with penultimut hop behaviour in MPLS. Last router signals label 3 (implicit null) that is instructing neighbor to remove transit label and send only "VPN" label on that link. Add on another MPLS box (P router( in between and you will get transport/tunnels labels.

Regards,
Bosjan

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Graham Wooden
Sent: Tuesday, March 21, 2006 8:45 PM
To: cisco-nsp
Subject: [c-nsp] 6500-MSFC2(c6sup22) - MPLS

Hello all,

While I had LDP up, it appears that I can't establish EoMPLS with another identical switch.  I am getting " implc-null " where I should be seeing tags.  Both are running 12.1.8b, which is the only sw I have seen so far that offers the mpls ip command on the interfaces.

Is this problem existing because of the lack of OSM interfaces?  If so, what can be done so that I can enter MPLS domains as well as provide EoMPLS on the rj45 card - ws-x6248?  I have no need for any OSM stuff. Do I need the 720 Sup?  Or do I need to run the big c6sup222 12.2 images opposed to the
c6sup22 12.1 images?

Any suggestions would be grand - don't have a lot of cash for this project, so I am trying to get by on what we do have and possibly get used or Refurbished if we need to get anything in addition  Again, wanting to "backhaul" if you will the LDP labels and provide EoMPLS ports - either via vlan or port based.

Regards,

-graham


RouterA - Loopback0: 192.168.2.1, vlan2 IP: 192.168.1.1 RouterB - Loopback0: 192.168.2.2, vlan2 IP: 192.168.1.2
Vlan3 is the EoMPLS (id being 101).  OSPF is the IRP.
VLAN2 and 3 are EtherSVI.


RouterA#show mpls ldp neighbor
Peer LDP Ident: 192.168.2.2:0; Local LDP Ident 192.168.2.1:0
        TCP connection: 192.168.2.2.11013 - 192.168.2.1.646
        State: Oper; Msgs sent/rcvd: 30/31; Downstream
        Up time: 00:18:40
        LDP discovery sources:
          Vlan2
          Targeted Hello 192.168.2.1 -> 192.168.2.2, active, passive
        Addresses bound to peer LDP Ident:
          127.0.0.12      192.168.2.2     192.168.1.4

  

RouterA#show mpls l2transport vc 101 detail

vcid: 101, local groupid: 67, remote groupid: 66 (vc is up)
client: Vl3 is up, destination: 192.168.2.2, Peer LDP Ident: 192.168.2.2:0 local label: 17, remote label: 18, tunnel label: implc-null outgoing interface: Vl2, next hop: 192.168.1.4 Local MTU: 1500, Remote MTU: 1500
imposition: LC Programmed
current imposition/last disposition slot: 0/32 Packet totals(in/out): 0/0 byte totals(in/out): 0/0RouterA#show mpls ldp neighbor Peer LDP Ident: 192.168.2.2:0; Local LDP Ident 192.168.2.1:0
        TCP connection: 192.168.2.2.11013 - 192.168.2.1.646
        State: Oper; Msgs sent/rcvd: 30/31; Downstream
        Up time: 00:18:40
        LDP discovery sources:
          Vlan2
          Targeted Hello 192.168.2.1 -> 192.168.2.2, active, passive
        Addresses bound to peer LDP Ident:
          127.0.0.12      192.168.2.2     192.168.1.4


RouterA#show mpls ldp bindings
  127.0.0.0/8, rev 2
        local binding:  label: imp-null
        remote binding: lsr: 192.168.2.2:0, label: imp-null
  192.168.1.0/24, rev 6
        local binding:  label: imp-null
        remote binding: lsr: 192.168.2.2:0, label: imp-null
  192.168.2.1/32, rev 4
        local binding:  label: imp-null
        remote binding: lsr: 192.168.2.2:0, label: 16
  192.168.2.2/32, rev 8
        local binding:  label: 16
        remote binding: lsr: 192.168.2.2:0, label: imp-null



_______________________________________________
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/