Hi, You must also configure a BGP session using the address-family ipv4 mdt
Take a look at http://www.cisco.com/en/US/docs/ios-xml/ios/ipmulti_mvpn/configuration/15-2s/imc_cfg_mc_vpn.html Regards, Fredrik Vöcks Senior IP Network Engineer On 26 April 2013 18:25, Leigh Harrison <[email protected]>wrote: > Hello folks, > > We're going through setting up multicasting in our network between some > core ASR9K's and some edge ME3600's. The underlying multicasting is > implemented and working well, but we're having some trouble in getting the > vrf's working correctly for multicasting. Would someone be able to offer > some sagely advice and some pointers as to what we're doing wrong or not > doing?? > > Leigh > > > Config for one of the 9K's:- > > vrf multicast_test > address-family ipv4 unicast > import route-target > 64900:123456 > ! > export route-target > 64900:123456 > ! > ! > router pim > address-family ipv4 > auto-rp mapping-agent Loopback0 scope 20 interval 60 > auto-rp candidate-rp Loopback0 scope 20 group-list 224-4 interval 60 > interface Loopback0 > enable > ! > interface TenGigE0/3/1/0 > enable > ! > interface TenGigE0/3/1/3 > enable > ! > interface TenGigE0/4/1/3 > enable > ! > interface GigabitEthernet0/3/0/0 > enable > ! > ! > vrf multicast_test > address-family ipv4 > rp-address 200.200.200.11 > interface Loopback239 > enable > ! > ! > ! > ! > router igmp > interface Loopback0 > join-group 239.0.0.239 > ! > vrf multicast_test > interface Loopback239 > join-group 239.0.1.239 > ! > ! > ! > interface Loopback239 > vrf multicast_test > ipv4 address 200.200.200.11 255.255.255.255 > ! > router bgp 64900 > vrf multicast_test > rd 64900:12345611 > address-family ipv4 unicast > redistribute connected > ! > ! > ! > RP/0/RSP0/CPU0:CH-LHC-ASR9010-1#sh pim vrf multicast_test interface > Fri Apr 26 17:19:30.029 BST > > PIM interfaces in VRF multicast_test > Address Interface PIM Nbr Hello DR > DR > Count Intvl Prior > > 200.200.200.11 Loopback239 on 1 30 1 > this system > 10.200.2.9 mdtmulticast/test on 2 30 1 > 10.200.5.1 > RP/0/RSP0/CPU0:CH-LHC-ASR9010-1#sh pim vrf multicast_test neigh > Fri Apr 26 17:19:34.212 BST > > PIM neighbors in VRF multicast_test > > Neighbor Address Interface Uptime Expires DR > pri Flags > > 200.200.200.11* Loopback239 03:03:26 00:01:37 1 > (DR) B P > 10.200.2.9* mdtmulticast/test 01:42:23 00:01:22 1 > 10.200.5.1 mdtmulticast/test 01:42:16 00:01:19 1 > (DR) P > > RP/0/RSP0/CPU0:CH-LHC-ASR9010-1#ping vrf multicast_test 239.0.1.239 > Fri Apr 26 17:22:45.480 BST > Mdef cons get failed for VRF 0x60000003 - No such process > > > Config for the ME3600 (directly connected) > > CG-Peer1-3600ME-1#sh run vrf multicast_test > Building configuration... > > Current configuration : 444 bytes > ip vrf multicast_test > rd 64900:12345615 > mdt default 239.0.0.1 > mdt data 239.0.1.0 0.0.0.255 threshold 1 > route-target export 64900:123456 > route-target import 64900:123456 > ! > ! > interface Loopback239 > ip vrf forwarding multicast_test > ip address 200.200.200.15 255.255.255.255 > ip pim sparse-mode > ip igmp join-group 239.0.1.239 > ! > router bgp 64900 > ! > address-family ipv4 vrf multicast_test > redistribute connected > exit-address-family > ! > end > > CG-Peer1-3600ME-1# > CG-Peer1-3600ME-1#sh ip pim vrf multicast_test int > CG-Peer1-3600ME-1#sh ip pim vrf multicast_test interface > > Address Interface Ver/ Nbr Query DR DR > Mode Count Intvl Prior > 10.200.5.1 Tunnel1 v2/S 1 30 1 > 10.200.5.1 > 200.200.200.15 Loopback239 v2/S 0 30 1 > 200.200.200.15 > CG-Peer1-3600ME-1#sh ip pim vrf multicast_test neigh > PIM Neighbor Table > Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, > P - Proxy Capable, S - State Refresh Capable, G - GenID Capable > Neighbor Interface Uptime/Expires Ver DR > Address > Prio/Mode > 10.200.2.9 Tunnel1 01:43:11/00:01:28 v2 1 / G > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security Cloud System, > Managed and Supported by TekNet Solutions (http://www.teknet.co.uk) > ______________________________________________________________________ > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
