[Xorp-users] Well - I'm half working....

[Dave Price]

Dear All,

	After help received so far (thanks Mark for new LiveCD),
I'm now half working.

	Following a local suggestion (Thanks Hefin), I've
set up a multicast beacon client reporting to the JANET
beacon monitoring system from my Sun (193.60.11.36).

  As far as I can tell, the monitoring
system, and other sites are reporting seeing my multicast
beacon packets being sent to 233.3.18.1

	However, my beacon sees no incoming multicasts
from other beacons, seems to report no reception on the monitoring
software and indeed, using tcpdump/snoop on various interfaces
I can see my outgoing packets but none coming back.

[Aside, why does the XORP machine ask www.icir.org to do pointer
DNS lookups every now and then...  That machine replies NX.
The enquiries are for addresses that would exist in our
number space but are unused. I suspect there is some low volume
of port scanning goping on perhaps - but why
does it ask www.icir.org to do DNS?]

I'm not quite sure what to expect as the output of the various
xorp "show" commands, but there are a view cases where it
says "UNKNOWN" for values of things and I wondered what the
significance of that was.  For instance  if I issue

"show pim join all"

then I get lots of output, selecting just a bit, the output
sections for the group 233.3.18.1 being used by the beacon
are ...

=================================================
233.3.18.1      0.0.0.0         146.97.34.8     WC   
    Upstream interface (RP):   rl3
    Upstream MRIB next hop (RP): UNKNOWN
    Upstream RPF'(*,G):        UNKNOWN
    Upstream state:            Joined 
    Join timer:                58
    Local receiver include WC: ...O..
    Joins RP:                  ......
    Joins WC:                  ......
    Join state:                ......
    Prune state:               ......
    Prune pending state:       ......
    I am assert winner state:  ......
    I am assert loser state:   ......
    Assert winner WC:          ......
    Assert lost WC:            ......
    Assert tracking WC:        ...OO.
    Could assert WC:           ...O..
    I am DR:                   .OOO.O
    Immediate olist RP:        ......
    Immediate olist WC:        ...O..
    Inherited olist SG:        ...O..
    Inherited olist SG_RPT:    ...O..
    PIM include WC:            ...O..
===================================================

and also...

==============================
233.3.18.1      193.60.11.36    146.97.34.8     SG SPT DirectlyConnectedS 
    Upstream interface (S):    rl2
    Upstream interface (RP):   rl3
    Upstream MRIB next hop (RP): UNKNOWN
    Upstream MRIB next hop (S):  UNKNOWN
    Upstream RPF'(S,G):        UNKNOWN
    Upstream state:            Joined 
    Register state:            RegisterPrune RegisterCouldRegister 
    Join timer:                57
    Local receiver include WC: ...O..
    Local receiver include SG: ......
    Local receiver exclude SG: ......
    Joins RP:                  ......
    Joins WC:                  ......
    Joins SG:                  ....O.
    Join state:                ....O.
    Prune state:               ......
    Prune pending state:       ......
    I am assert winner state:  ......
    Assert winner WC:          ......
    Assert winner SG:          ......
    Assert lost WC:            ......
    Assert lost SG:            ......
    Assert lost SG_RPT:        ......
    Assert tracking SG:        ...OO.
    Could assert WC:           ...O..
    Could assert SG:           ....O.
    I am DR:                   .OOO.O
    Immediate olist RP:        ......
    Immediate olist WC:        ...O..
    Immediate olist SG:        ....O.
    Inherited olist SG:        ...OO.
    Inherited olist SG_RPT:    ...O..
    PIM include WC:            ...O..
    PIM include SG:            ......
    PIM exclude SG:            ......
==================================================

is this the correct sort of thing?  Are those "UNKNOWN"
entries anything to worry about??


What other output should I look at to try to debug this??  Any suggestions?

Xorp> show pim mrib  
DestPrefix         NextHopRouter   VifName VifIndex MetricPref Metric
0.0.0.0/0          144.124.35.254  rl3     4                 1      1
144.124.32.0/22    144.124.34.30   rl3     4                 0      0
193.60.10.0/24     193.60.10.90    rl1     2                 0      0
193.60.11.0/24     193.60.11.33    rl2     3                 0      0
193.60.15.0/24     193.60.15.40    rl0     1                 0      0
Xorp> 

Xorp> show pim neighbors  
Interface    DRpriority NeighborAddr    V Mode   Holdtime Timeout
rl3                none 144.124.35.252  2 Sparse      105      79
rl3                none 144.124.35.253  2 Sparse      105      79
Xorp> 

Note: there are actually two router engines in our
upstream Cisco box.  As I understand it, they watch each other and
one adopts 144.124.35.254  but they both have there own
IP addresses too, hence perhaps the oddities above. Live
failover is the plan I understand.

Xorp> show pim mfc
Group           Source          RP             
233.3.18.1      193.60.11.36    146.97.34.8    
    Incoming interface :      rl2
    Outgoing interfaces:      ....O.
Xorp> 

so that looks o.k. I guess? yes?  I presume the dots
match to interfaces in which case I reckon the O
matches to rl3 which is my route upstream.

Any bright ideas anyone??

Thanks,

Dave Price