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

[Peter Gutierrez]

tstevens at cisco.com wrote:
> Yes, I think you need to check the other side as well - are PIM hellos
>  sent, and is the boundary ACL applied correctly.

> Tim
> 
> At 04:24 PM 2/17/2005, Peter Gutierrez commented:
> >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


I did a monitor session and the capture shows my end (xxx.x.xx.102) 
receiving the Hello from the remote end (xxx.x.xx.101)

FID             Elapsed Size    Destination     Source  Summary
 000000      40.797.778.240  72  PIM_Router  000C31C86C00  IP Time To 
Live Expiring - TTL=1 SA=[xxx.x.xx.102] DA=[224.0.0.13]
 000001      49.758.620.720  72  PIM_Router  000DEDAC9340  IP Time To 
Live Expiring - TTL=1 SA=[xxx.x.xx.101] DA=[224.0.0.13]
 000002      79.278.620.960  72  PIM_Router  000DEDAC9340  IP Time To 
Live Expiring - TTL=1 SA=[xxx.x.xx.101] DA=[224.0.0.13]
 000003     100.700.945.120  72  PIM_Router  000C31C86C00  IP Time To 
Live Expiring - TTL=1 SA=[xxx.x.xx.102] DA=[224.0.0.13]
 000004     109.022.541.320  72  PIM_Router  000DEDAC9340  IP Time To 
Live Expiring - TTL=1 SA=[xxx.x.xx.101] DA=[224.0.0.13]
 000005     130.188.442.560  72  PIM_Router  000C31C86C00  IP Time To 
Live Expiring - TTL=1 SA=[xxx.x.xx.102] DA=[224.0.0.13]
 000006     138.438.556.000  72  PIM_Router  000DEDAC9340  IP Time To 
Live Expiring - TTL=1 SA=[xxx.x.xx.101] DA=[224.0.0.13]
 000007     189.203.665.480  72  PIM_Router  000C31C86C00  IP Time To 
Live Expiring - TTL=1 SA=[xxx.x.xx.102] DA=[224.0.0.13]

Still no neighbor established on my end:

GE-WAN7/3 is up, line protocol is up
  Internet address is GE-WAN7/3 is up, line protocol is up
  Internet address is xxx.x.xx.102/30
  Multicast switching: fast
  Multicast packets in/out: 2093795/0
  Multicast boundary: 40
  Multicast TTL threshold: 0
  PIM: enabled
    PIM version: 2, mode: sparse
    PIM DR: xxx.x.xx.102 (this system)
    PIM neighbor count: 0
    PIM Hello/Query interval: 30 seconds
    PIM State-Refresh processing: enabled
    PIM State-Refresh origination: disabled
    PIM NBMA mode: disabled
    PIM ATM multipoint signalling: disabled
    PIM domain border: enabled
  Multicast Tagswitching: disabled

I have a TAC case open on this, so maybe that will actually resolve 
something if this mailing list doesn't.

PeterG