[c-nsp] IOS-XR 5.2 NG-MVPN

Mihai mihaigabriel at gmail.com
Sat Feb 28 11:25:20 EST 2015


Hello,

Could someone enlighten me why an ASR9k doesn't generate an I-PMSI in 
the below configuration? I am trying to configure a NG-MVPN between 
Cisco ASR9K and Juniper MX using RSVP-TE.

multicast-routing
  address-family ipv4
   mdt source Loopback10
   !
  !
  vrf mihai
   address-family ipv4
    mdt source Loopback10
    core-tree-protocol rsvp-te
    export-rt 200:200
    import-rt 200:200
    interface all enable
    bgp auto-discovery p2mp-te
     receiver-site
    !
    mdt default p2mp-te attribute-set p2mp-te-default-set
   !
  !
!
vrf mihai
  vpn id 200:200
  address-family ipv4 unicast
   import route-target
    200:200
   !
   export route-target
    200:200
   !
  !
!
router bgp 65100
  mvpn
  bgp router-id 2.2.2.2
  address-family vpnv4 unicast
  !
  address-family ipv4 mvpn
   global-table-multicast
  !
  neighbor 1.1.1.1
   remote-as 65100
   update-source Loopback10
   address-family vpnv4 unicast
   !
   address-family ipv4 mvpn
   !
  !
  vrf mihai
   rd 200:200
   address-family ipv4 unicast
    network 10.10.10.1/24
   !
   address-family ipv4 mvpn


RP/0/RSP0/CPU0:asr9k1(config)#do sh bgp ipv4 mvpn neighbors 1.1.1.1 
advertised-routes
Sat Feb 28 18:15:28.205 EETDST
RP/0/RSP0/CPU0:asr9k1(config)#


Juniper is advertising the I-PMSI:

RP/0/RSP0/CPU0:asr9k1(config)#do sh bgp ipv4 mvpn  | begin Distinguisher:
Sat Feb 28 18:14:24.500 EETDST
Route Distinguisher: 200:200 (default for vrf mihai)
*>i[1][1.1.1.1]/40
                       1.1.1.1               100      0 i
Route Distinguisher: 200:201
*>i[1][1.1.1.1]/40
                       1.1.1.1               100      0 i

Processed 2 prefixes, 2 paths

Thanks,
Mihai


More information about the cisco-nsp mailing list