[c-nsp] PIM neighbor only established on one side of 2 6509s connected by GigE

[Peter Gutierrez]

Tim Stevenson wrote:
> Does it work with the boundary config removed? Could be a misprogramming 
> of the ACL TCAM. You can try removing, or let's see a sh tcam int 
> ge-wan7/3 acl in ip. Have you tried turning on PIM debugs to see if you 
> are receiving hellos from the far end?

I did try PIM debug, and it does show my sending the hello on GE-WAN7/3, 
but not receiving them.

Feb 17 15:05:53.293: PIM(0): Send periodic v2 Hello on GE-WAN7/3
Feb 17 15:05:57.225: PIM(0): Send periodic v2 Hello on GigabitEthernet1/1
Feb 17 15:06:02.445: PIM(0): Send periodic v2 Hello on GigabitEthernet7/2
Feb 17 15:06:04.541: PIM(0): Received v2 hello on GigabitEthernet7/2 from
Feb 17 15:06:06.593: PIM(0): Received v2 hello on GigabitEthernet7/1 from
Feb 17 15:06:08.945: PIM(0): Send periodic v2 Hello on Loopback1
Feb 17 15:06:08.945: PIM(0): Received v2 hello on Loopback1 from
Feb 17 15:06:09.733: PIM(0): Send periodic v2 Hello on GigabitEthernet7/1
Feb 17 15:06:19.217: PIM(0): Received v2 hello on GigabitEthernet1/1 from
Feb 17 15:06:22.593: PIM(0): Send periodic v2 Hello on GE-WAN7/3
Feb 17 15:06:26.661: PIM(0): Send periodic v2 Hello on GigabitEthernet1/1
Feb 17 15:06:31.649: PIM(0): Send periodic v2 Hello on GigabitEthernet7/2
Feb 17 15:06:34.393: PIM(0): Received v2 hello on GigabitEthernet7/2 from
Feb 17 15:06:36.533: PIM(0): Received v2 hello on GigabitEthernet7/1 from


I also removed the multicast boundary statement from the config, on this 
end, without any effect. I can try and have the remote end remove it, 
probably tomorrow. Of course, the multicast boundary acl doesn't have 
neither a permit nor deny for 224.0.0.13, the PIM Hello group.

#show tcam int ge7/3  acl out ip
     deny         ip any 239.0.0.0 0.255.255.255
     deny         ip any host 224.0.1.39
     deny         ip any host 224.0.1.40
     permit       ip any any
     deny         ip any any
     deny         ip any any


PeterG