Did you ever find a

Bilal Nawaz · ‎05-02-2013

Hello, I just had a look at the logs on a pair of 6509's with SUP-720-3B. They have a etherchannel between them (just standard basic campus config - with OSPF) and I get these so so frequently, fairly new to multicast arena so I have no idea why this is happening, could someone perhaps explain what is happening. Why would this just drop for 0.0.0.0 (itself, right?):

6509-1

May 2 21:23:46.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:23:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:24:16.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:24:16.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:24:46.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:24:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:25:16.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:25:16.705 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:25:46.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:25:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:26:16.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:26:16.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:26:46.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:26:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:27:16.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:27:16.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:27:46.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:27:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

6509-2

May 2 21:34:16.700 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:34:16.704 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:34:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:34:46.705 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:35:16.713 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:35:16.717 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:35:46.709 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:35:46.713 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:36:16.709 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:36:16.713 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

May 2 21:36:46.709 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24

May 2 21:36:46.713 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR

It seems exactly every 30 seconds this happens. This is the config for vlan 24

6509-1#show run int vlan 24

Building configuration...

Current configuration : 312 bytes

!

interface Vlan24

description *** Server VLAN***

ip address 172.25.24.2 255.255.252.0

ip helper-address 172.25.24.137

ip helper-address 172.25.24.138

ip directed-broadcast 110

ip flow ingress

ip flow egress

ip pim sparse-mode

standby 24 ip 172.25.24.1

standby 24 priority 110

standby 24 preempt

end

6509-2#show run int vlan 24

Building configuration...

Current configuration : 311 bytes

!

interface Vlan24

description *** Server VLAN***

ip address 172.25.24.3 255.255.252.0

ip helper-address 172.25.24.137

ip helper-address 172.25.24.138

ip directed-broadcast 110

ip flow ingress

ip flow egress

ip pim sparse-mode

standby 24 ip 172.25.24.1

standby 24 priority 90

standby 24 preempt

end

6509-1#show ip pim neighbor

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

172.25.18.3 Vlan18 29w4d/00:01:36 v2 1 / DR S P G

172.25.24.3 Vlan24 29w4d/00:01:32 v2 1 / DR S P G

172.25.28.3 Vlan28 29w4d/00:01:26 v2 1 / DR S P G

172.25.32.3 Vlan32 29w4d/00:01:40 v2 1 / DR S P G

172.25.36.3 Vlan36 29w4d/00:01:23 v2 1 / DR S P G

172.25.40.3 Vlan40 29w4d/00:01:43 v2 1 / DR S P G

172.25.44.3 Vlan44 29w4d/00:01:38 v2 1 / DR S P G

172.25.48.3 Vlan48 29w4d/00:01:41 v2 1 / DR S P G

172.25.52.3 Vlan52 29w4d/00:01:27 v2 1 / DR S P G

172.25.56.3 Vlan56 29w4d/00:01:22 v2 1 / DR S P G

172.25.60.3 Vlan60 29w4d/00:01:30 v2 1 / DR S P G

172.25.64.3 Vlan64 29w4d/00:01:21 v2 1 / DR S P G

172.25.68.3 Vlan68 29w4d/00:01:28 v2 1 / DR S P G

172.25.72.3 Vlan72 29w4d/00:01:28 v2 1 / DR S P G

172.25.76.3 Vlan76 29w4d/00:01:16 v2 1 / DR S P G

172.25.84.3 Vlan84 29w4d/00:01:30 v2 1 / DR S P G

192.168.250.3 Vlan590 10w1d/00:01:33 v2 1 / S P G

192.168.250.6 Vlan590 10w1d/00:01:35 v2 1 / DR S P G

192.168.250.5 Vlan590 10w1d/00:01:21 v2 1 / S P G

192.168.240.6 Vlan592 10w1d/00:01:21 v2 1 / DR S P G

192.168.240.5 Vlan592 15w5d/00:01:34 v2 1 / S P G

192.168.240.3 Vlan592 10w1d/00:01:16 v2 1 / S P G

Thank you

B

Please rate useful posts and remember to mark any solved questions as answered. Thank you.

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

paul driver · ‎05-02-2013

Hello
These logs are saying it losing connection with it pim neighbour adjacency- that is the two svi's.

Enabling pim- sparse mode it telling the router you want to pull mc from the m/c RP

Not sure enabling pim-sparse on an svi is necessary( need to validate that) but usually this is enabled on an interface towards the to the RP.

How are you specifying the RP - Static or automatically

Debug ip pim
Debug ip multicast-routing

Res
Paul

Sent from Cisco Technical Support iPad App

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Bilal Nawaz · ‎05-02-2013

Hello Paul. Thanks for your reply.
I may disagree that the neighbourship is dropping. I have assigned the RP statically and it is not one of the 6509s.

All the other SVIs have the same thing as you can see from the neighbourship the PIM neighbours I.e. 6509-2 have been up for weeks including VLAN 24.

Why is it only this VLAN 24 that I am getting these logs for?

When there's a neighbourship change with another router, normally we see the address of the attached interface rather than 0.0.0.0. (This is what I have observed anyway)
When we enable PIM sparse mode on an interface, we get the 0.0.0.0 if nothing is connected to the other side?

I also don't understand why there would be consistency. Every 30 seconds or so?

Thank you

Sent from Cisco Technical Support iPhone App

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

Bilal Nawaz · ‎05-10-2013

Anyone?

Sent from Cisco Technical Support iPhone App

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

Bilal Nawaz · ‎01-22-2014

Anyone? :-/

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

david.wild · ‎12-05-2014

Did you ever find a resolution reason for this ? Have a similar issue at the moment.

Thanks

Why do I get %PIM-5-NBRCHG in the logs - 6509-E?