05-11-2012 11:29 AM
Customer running Nexus 7000 6.03a. Core and Distribution VDCs. With the static RP configuration shown below,
a source in VLAN 300 attached to a L2 Catalyst 6500, and a receiver on eth 1/14 on the core, multicast traffic
in groups 234.5.6.7-234.5.6.11 is delivered successfully from source to receiver. When we try to use anycast-rp,
replacing the staic rp config in the distribution VDC with the 2 lines below, all traffic fails.
ip pim anycast-rp 10.129.26.146 10.129.26.133 <==== Other distribution VDC loopback 100 IP
ip pim anycast-rp 10.129.26.146 10.129.26.134 <==== Local distribution VDC loopback 100 IP
Loopback 99 is the anycast RP 'virtual' address, loopback 100 is the local RP used for anycast rp-to-rp communication.
Debugging pim joins generates a message 'no rp found for group x.x.x.x' for all five groups on
the distribution VDC. The core pim debug shows no errors.
Unicast routing (BGP and static) IP addressing is working correctly. IGMP/IGMP snooping also appears correct,
and we are seeing the groups joined on the core VDC.
I am at a loss to explain why the distribution VDC cannot recognize itself as an RP. Does anyone have an idea?
Some additional config notes:
There are two Nexus chassis, each split into core and distributtion VDCs. There is a VPC between the distribution VDCs,
with member vlans trunked to a pair of 6509s, operating at layer 2 only. Vlan 300, the source vlan, is a vpc member.
The source is attached to a 6509 port in Vlan 300.
Each distribution VDC has a pairof layer 3 ports, each connected to one of the core VDCs. The core VDCs have a layer 3
link between them, and the distribution VDCs have a layer 3 link outside the vpc. Basically, the L3 is a bow-tie,
with horizotal cross links as well. PIM is running on all L3 links, as well on vlan 300, and the loopbacks used for RP.
======================================================================
Distribution VDC
ip pim rp-address 10.129.26.146 group-list 224.0.0.0/4
ip pim log-neighbor-changes
ip pim ssm range 232.0.0.0/8
interface Vlan300
ip address 10.129.26.67/28
ip pim sparse-mode
ip pim dr-priority 200
hsrp 200
preempt
priority 150
ip 10.129.26.65
ip dhcp relay address 10.129.26.84
description Dist Server VLAN 300
no shutdown
interface loopback99
ip address 10.129.26.146/32
ip pim sparse-mode
interface loopback100
ip address 10.129.26.134/32
ip pim sparse-mode
interface Ethernet5/1
description cidcnxsw2-DIST to cidcnxsw2-CORE
no switchport
ip address 10.129.26.246/30
ip pim sparse-mode
no shutdown
=======================================================================
Core VDC
ip pim rp-address 10.129.26.146 group-list 224.0.0.0/4
ip pim ssm range 232.0.0.0/8
interface Vlan111
description Multicast Anycast Test VLAN
no shutdown
ip address 10.129.27.35/27
ip pim sparse-mode
interface Ethernet1/14
description Test PC
switchport
switchport access vlan 111
no shutdown
interface Ethernet2/1
description cidcnxsw2-CORE to cidcnxsw2-DIST
ip address 10.129.26.245/30
ip pim sparse-mode
no shutdown
============================================================================
Solved! Go to Solution.
05-18-2012 03:41 AM
Hi
If you configure anycast-RP you still need the config-line for the static-rp. So you need these 3 lines on your anycast-rp-routers:
ip pim anycast-rp 10.129.26.146 10.129.26.133
ip pim anycast-rp 10.129.26.146 10.129.26.134
ip pim rp-address 10.129.26.146 group-list 224.0.0.0/4
Line 1 & 2 providing the anycast RP (you configure a redundant RP) - but you still need the third line to tell your routers where they find the RP.
HTH
Marcel
05-18-2012 03:41 AM
Hi
If you configure anycast-RP you still need the config-line for the static-rp. So you need these 3 lines on your anycast-rp-routers:
ip pim anycast-rp 10.129.26.146 10.129.26.133
ip pim anycast-rp 10.129.26.146 10.129.26.134
ip pim rp-address 10.129.26.146 group-list 224.0.0.0/4
Line 1 & 2 providing the anycast RP (you configure a redundant RP) - but you still need the third line to tell your routers where they find the RP.
HTH
Marcel
05-20-2012 03:45 PM
Marcel,
Thanks - that makes sense. We still need to do full testing, but I think this will addressw the issue.
05-20-2012 10:56 PM
Glad I could help. Have a nice day
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide