[Xorp-users] Help with errors when starting up Xorp

[Chris Robson NRL]

Hi Pavlin

still plugging away here trying to get XORP PIM working on a Fedora Core 4 
Kernel 2.6.14-1.1637 working.  I had to make some manual modifications to 
Hoerdt modified files which I will relay later to you.  But should I be 
concerned about these warnings?  By-the-by, which Hoerdt patch are you 
using 1a, 1b, 1c or 1d?  And just an FYI, we'll be testing this once we get 
a working PIM over a 6VPE (IPv6-Over-IPv4-MPLS) backbone.  thanks for the help

./configure output ........
configure: WARNING: linux/rtnetlink.h: present but cannot be compiled
configure: WARNING: linux/rtnetlink.h: check for missing prerequisite headers?
configure: WARNING: linux/rtnetlink.h: proceeding with the preprocessor's 
result
checking for linux/rtnetlink.h... yes
checking linux/types.h usability... yes
checking linux/types.h presence... yes
checking for linux/types.h... yes
checking linux/sockios.h usability... yes
checking linux/sockios.h presence... yes
checking for linux/sockios.h... yes
checking linux/mroute6.h usability... no
checking linux/mroute6.h presence... yes
configure: WARNING: linux/mroute6.h: present but cannot be compiled
configure: WARNING: linux/mroute6.h: check for missing prerequisite headers?
configure: WARNING: linux/mroute6.h: proceeding with the preprocessor's result
checking for linux/mroute6.h... yes


At 08:18 PM 11/22/2005, Pavlin Radoslavov wrote:
> > Everything runs but these 2 errors dump when I start XORP.  Any idea what
> > this is?
> >
> > [ 2005/11/22 11:56:53  WARNING xorp_rtrmgr:4296 XrlFinderTarget +406
> > ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> > method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
> > Target "PIMSM_4" does not exist or is not enabled
> >
> > [ 2005/11/22 11:56:51  WARNING xorp_rtrmgr:4296 XrlFinderTarget +406
> > ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> > method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
> > Target "IGMP" does not exist or is not enabled
>
>This is normal if there are 1-2 such errors (per module). Those are
>transient errors during startup only (and eventually during
>shutdown).
>
>Only if you see many periodic errors like those above, then this
>could be an issue.
>
>Pavlin

Christopher L. Robson
GS-1550-NP-IV
(V/C) 202-404-3138
EMAIL: Chris.Robson@nrl.navy.mil
GIG-EF SIP: Chris.Robson@nrl.gigef.net
DoN, NRL, Code 5590
4555 Overlook Ave
Washington, D.C. 20375