Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

MPLS Tags not appearing on one side of new MPLS VPN

I have an already existing 6509 that is going to provide the entire MPLS routing table via route reflector to a new 6509.  Here are the relevant configs:

 

EXISTING 6509 (Router A)

 

interface Loopback0

 ip address 10.255.2.2 255.255.255.255

end

 

router bgp 23532
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 10.255.2.3 remote-as 23532
 neighbor 10.255.2.3 update-source Loopback0
 !
 address-family ipv4 mdt
  neighbor 10.255.2.3 activate
  neighbor 10.255.2.3 send-community extended
  neighbor 10.255.2.3 route-reflector-client
  neighbor 10.255.2.3 soft-reconfiguration inbound
 exit-address-family
 !
 address-family vpnv4
  neighbor 10.255.2.3 activate
  neighbor 10.255.2.3 send-community extended
  neighbor 10.255.2.3 route-reflector-client
  neighbor 10.255.2.3 next-hop-self
  bgp redistribute-internal
 exit-address-family

!

 address-family ipv4 vrf CustomerA

  redistribute connected

  redistribute static

  no synchronization

  bgp redistribute-internal

 exit-address-family

 

DAL-COLO-6509-1#show mpls ldp neighbor 10.255.2.3
    Peer LDP Ident: 10.255.2.3:0; Local LDP Ident 10.255.2.2:0
        TCP connection: 10.255.2.3.16271 - 10.255.2.2.646
        State: Oper; Msgs sent/rcvd: 647/646; Downstream
        Up time: 06:07:30
        LDP discovery sources:
          Vlan65, Src IP addr: X.X.X.69
        Addresses bound to peer LDP Ident:
          10.255.2.3      X.X.X.69     X.X.X.254    10.10.1.31 

 

DAL-COLO-6509-1#show mpls forwarding-table 10.255.2.3 detail

Local      Outgoing   Prefix           Bytes Label   Outgoing   Next Hop    

Label      Label      or Tunnel Id     Switched      interface              

257        Pop Label  10.255.2.3/32    22272         Vl65       X.X.X.69 

        MAC/Encaps=14/14, MRU=1584, Label Stack{}

        001CB14458000009B6A4B8008847 

        No output feature configured

 

DAL-COLO-6509-1#show mpls ldp bindings 10.255.2.3 32

  lib entry: 10.255.2.3/32, rev 4933

        local binding:  label: 257

        remote binding: lsr: 10.255.2.1:0, label: 131

        remote binding: lsr: 10.255.2.3:0, label: imp-null

 

DAL-COLO-6509-1#traceroute 10.255.2.3

 

Type escape sequence to abort.

Tracing the route to 10.255.2.3

 

  1 69-69.netblk-66-60-69.yada.net (X.X.X.69) 0 msec *  0 msec

DAL-COLO-6509-1#

 

 

 

 

New 6509 (Router B)

 

router bgp 23532
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 10.255.2.2 remote-as 23532
 neighbor 10.255.2.2 update-source Loopback0
 !
 address-family ipv4 mdt
  neighbor 10.255.2.2 activate
  neighbor 10.255.2.2 send-community both
  neighbor 10.255.2.2 soft-reconfiguration inbound
 exit-address-family
 !
 address-family vpnv4
  neighbor 10.255.2.2 activate
  neighbor 10.255.2.2 send-community both
  neighbor 10.255.2.2 next-hop-self
  bgp redistribute-internal
 exit-address-family
 !
 address-family ipv4 vrf CustomerA
  redistribute connected
  redistribute static
  no synchronization
  bgp redistribute-internal
 exit-address-family

 

Br26-COLO-6509-1#show mpls ldp neighbor 10.255.2.2

    Peer LDP Ident: 10.255.2.2:0; Local LDP Ident 10.255.2.3:0

        TCP connection: 10.255.2.2.646 - 10.255.2.3.16271

        State: Oper; Msgs sent/rcvd: 657/657; Downstream

        Up time: 06:16:40

        LDP discovery sources:

          Vlan65, Src IP addr: X.X.X.70

        Addresses bound to peer LDP Ident:

          10.255.2.2      X.X.X.10     X.X.X.14     X.X.X.5      

          66.60.70.18     66.60.75.252    66.60.72.65     66.60.75.81     

          10.10.1.40      66.60.70.17     X.X.X.17     66.60.73.161    

          X.X.X.70     

 

Br26-COLO-6509-1#show mpls forwarding-table 10.255.2.2 detail

Local      Outgoing   Prefix           Bytes Label   Outgoing   Next Hop    

Label      Label      or Tunnel Id     Switched      interface              

40         Pop Label  10.255.2.2/32    0             Vl65       X.X.X.70 

        MAC/Encaps=14/14, MRU=1584, Label Stack{}

        0009B6A4B800001CB14458008847 

        No output feature configured

 

Br26-COLO-6509-1#show mpls ldp bindings 10.255.2.2 32

  lib entry: 10.255.2.2/32, rev 40

        local binding:  label: 40

        remote binding: lsr: 10.10.1.30:0, label: 29

        remote binding: lsr: 10.255.2.2:0, label: imp-null

 

Br26-COLO-6509-1#traceroute 10.255.2.2

 

Type escape sequence to abort.

Tracing the route to 10.255.2.2

 

  1 70-69.netblk-66-60-69.yada.net (X.X.X.70) 0 msec *  0 msec

Br26-COLO-6509-1#

 

 

 

 

Im seeing label switching coming from the old switch (which has several MPLS VPN connections already).  Im not seeing anything from the new switch.  OSPF is the routing protocol between the interfaces, and shows to be working fine.  LDP neighbor relationship seems to be good- just tagging isn’t occurring going back toward the old switch.  Any suggestions?

 

Thanks

Greg

Everyone's tags (3)
11 REPLIES
Hall of Fame Super Silver

Hello Greg,because the two

Hello Greg,

because the two devices are directly connected, Penultimate Hop Popping (PHP) applies each device advertise its own loopback in LDP with an implicit null  (should be label 3) and the action is POP label and so the label stack is empty and the packet is sent as a native IP packet as you see also in the traceroute.

What you see is normal behaviour.

You would need three devices connected in a row RA-RB-RC  to see label propagation in action

 

Hope to help

Giuseppe

 

 

 

New Member

I need the MPLS VPN to come

I need the MPLS VPN to come up, trade routes, and pass traffic.  No matter what I do- it doesn't seem to fix this.  That's the ultimate issue here.  The new 6509 is acting as a Route Reflector Client getting it's routing table from the old switch.

 

Thanks

Greg

Hall of Fame Super Silver

Hello Greg,I see your point

Hello Greg,

I see your point.

post from new switch

show ip bgp vpnv4 all summary

only routes matching route targets of locally defined VRFs are actually imported

outside of BGP protocol you need

 

ip vrf CustomerA

route-distinguisher 1000:1

route-target import 1000:1

route-target export 1000:1

 

in both routers to build an MPLS VPN

 

Hope to help

Giuseppe

 

 

 

 

New Member

It's already there:This is

It's already there:

This is off the new switch:

ip vrf CustomerA
 rd 23532:1
 route-target export 23532:1001
 route-target import 23532:1001
 mdt default 239.232.255.0

Br26-COLO-6509-1#sh ip bgp vpnv4 all summary 
BGP router identifier 10.255.2.3, local AS number 23532
BGP table version is 13652, main routing table version 13652
13 network entries using 1781 bytes of memory
13 path entries using 884 bytes of memory
7/4 BGP path/bestpath attribute entries using 1120 bytes of memory
6 BGP rrinfo entries using 144 bytes of memory
3 BGP extended community entries using 72 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 4001 total bytes of memory
BGP activity 3997/3970 prefixes, 9542/9515 paths, scan interval 15 secs

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
10.255.2.2      4       23532    7853    3327    13652    0    0 00:02:16       11

 

Thanks

Greg

 

Here is the show ip route statement for the VRF:

Br26-COLO-6509-1#sh ip route vrf CustomerA

Routing Table: CustomerA
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area 
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C       10.105.46.0/24 is directly connected, Vlan217
C       10.253.0.9/32 is directly connected, Loopback2

 

Hall of Fame Super Silver

Hello Greg,all BGP routes are

Hello Greg,

all BGP routes are missing from vrf IP routing table

Can you post a sh version, sh module from new switch?

 

Only Sup7203B or better supports MPLS services in 6500 platform

 

Hope to help

Giuseppe

 

New Member

Yes- that is the problem we

Yes- that is the problem we are trying to fix.

 

Br26-COLO-6509-1#sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXI13, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Tue 11-Mar-14 04:53 by prod_rel_team

ROM: System Bootstrap, Version 12.2(17r)SX5, RELEASE SOFTWARE (fc1)

 Br26-COLO-6509-1 uptime is 1 day, 49 minutes
Uptime for this control processor is 1 day, 49 minutes
Time since Br26-COLO-6509-1 switched to active is 1 day, 48 minutes
System returned to ROM by reload at 09:20:45 CDT Wed May 7 2014 (SP by reload)
System restarted at 09:24:29 CDT Wed May 7 2014
System image file is "disk0:s72033-adventerprisek9_wan-mz.122-33.SXI13.bin"
Last reload reason: Reload Command

 

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

cisco WS-C6509-E (R7000) processor (revision 1.3) with 458720K/65536K bytes of memory.
Processor board ID SMG1125N74N
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
5 Virtual Ethernet interfaces
154 Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.

65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102

 

 

Yes- we do have a Sup7303B in this switch.

Purple

Hi,Can you do this on the

Hi,

Can you do this on the switch where the prefixes are not installed:

sh ip bgp vpnv4 vrf CustomerA

To see if you receive these via BGP

 

Regards

 

Alain

Don't forget to rate helpful posts.
New Member

We are not receiving any

We are not receiving any routes/MPLS tags from the switch.

New Member

Br26-COLO-6509-1#sh ip bgp

Br26-COLO-6509-1#sh ip bgp vpnv4 vrf CustomerA
BGP table version is 421, local router ID is 10.255.2.3
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 23532:1 (default for vrf CustomerA)
*> 10.105.46.0/24   0.0.0.0                  0         32768 ?
*> 10.253.0.9/32    0.0.0.0                  0         32768 ?
 

Gold

check your import/export

check your import/export policy on both routers

Could u disable default PE router behavior by configuring no bgp route target filter command under BGP to see all routes send through BGP vpnv4 table ,then use sh bgp vpn4 un all command to verify BGP routes.

Regards,

Ashish

New Member

Anyone have any ideas?

Anyone have any ideas?

294
Views
0
Helpful
11
Replies
CreatePlease login to create content