[Xorp-users] Module not foudn problem

Pavlin Radoslavov pavlin at icir.org
Sun Sep 2 12:35:25 PDT 2007


> According to the "ip addr" command as shown below, there is a link local 
> address.
> I wonder if there is an issue with xorp and linux kernel 2.6.22.  Every 
> since 2.6.18 a lot of IP stack things have broken.  Could yo save me 
> some time, where does xorp test for this?  Then I can poke around and 
> see what is happening.
> 
> 
> 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
> qlen 100
>     link/ether 00:1a:6b:69:a8:75 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.109/24 brd 192.168.1.255 scope global eth0
>     inet 192.168.1.106/24 brd 192.168.1.255 scope global secondary eth0
>     inet6 2001:480:f022:3:400:8000:0:196/84 scope global
>        valid_lft forever preferred_lft forever
>     inet6 fe80::21a:6bff:fe69:a875/64 scope link
>        valid_lft forever preferred_lft forever

Yes, the IPv6 link-local address is configured in the kernel, but
that configuration needs to be propagated to XORP as well. This can
be done by either:

a) Explicitly configure the IP addresses inside the XORP
"interfaces" section, including the link-local address.

b) Implicitly configure all IP addresses by using configuration
like:

interfaces {
    interface eth0 {
         default-system-config
    }
}

Option (b) is probably simpler in your case, so this is what I'd
recommend you do for now.
If you still get the same MLD error, then please configure only the
"interfaces" and "mfea6" sections, and send the output of
the following xorpsh commands:
  show interfaces
  show mfea6 interface

Regards,
Pavlin

> .....chris
> 
> Pavlin Radoslavov wrote:
> > Chris Robson <Chris.Robson at nrl.navy.mil> wrote:
> >
> >   
> >> Pavlin
> >>
> >> Here is the complete dump, also is the "mld" section of the config file.
> >> There is an error about invalid primary address which I assumed was being
> >> caused because the module was being terminated.
> >>     
> >
> > The "primary address" error is triggered because it appears eth0
> > doesn't have a configured IPv6 link-local address. The link-local
> > address should be assigned by either explicitly configuring it in
> > the "interfaces" section, or by using a configuration like:
> >
> > interfaces {
> >     interface eth0 {
> >         default-system-config
> >     }
> > }
> >
> > The latter solution assumes that all relevant IPv4 and IPv6
> > addresses have been configured in advance.
> >
> > FYI, in the future this should be fixed in XORP such that the IPv6
> > link-local address will be automatically taken from the kernel even
> > if "default-system-config" is not used.
> >
> > Regards,
> > Pavlin
> >
> >   
> >> protocols {
> >>     mld {
> >>     disable: false
> >>     interface eth0 {
> >>         vif eth0 {
> >>         disable: false
> >>         version: 1
> >>         enable-ip-router-alert-option-check: false
> >>         query-interval: 125
> >>         query-last-member-interval: 1
> >>         query-response-interval: 10
> >>         robust-count: 2
> >>         }
> >>     }
> >>     traceoptions {
> >>         flag all {
> >>         disable: false
> >>         }
> >>     }
> >>     }
> >> }
> >>
> >> [ 2007/09/01 17:52:14  INFO xorp_rtrmgr:4757 RTRMGR +239 master_conf_tree.cc
> >> execute ] Changed modules: interfaces, fea, mfea4, mfea6, mld, rib, fib2mrib,
> >> igmp, pimsm4, policy, static_routes, ospf4
> >> [ 2007/09/01 17:52:14  INFO xorp_rtrmgr:4757 RTRMGR +96 module_manager.cc
> >> execute ] Executing module: interfaces (fea/xorp_fea)
> >> [ 2007/09/01 17:52:15 INFO xorp_fea MFEA ] MFEA enabled
> >> [ 2007/09/01 17:52:15 INFO xorp_fea MFEA ] CLI enabled
> >> [ 2007/09/01 17:52:15 INFO xorp_fea MFEA ] CLI started
> >> [ 2007/09/01 17:52:15 INFO xorp_fea MFEA ] MFEA enabled
> >> [ 2007/09/01 17:52:15 INFO xorp_fea MFEA ] CLI enabled
> >> [ 2007/09/01 17:52:15 INFO xorp_fea MFEA ] CLI started
> >> [ 2007/09/01 17:52:16  INFO xorp_rtrmgr:4757 RTRMGR +96 module_manager.cc
> >> execute ] Executing module: fea (fea/xorp_fea)
> >> [ 2007/09/01 17:52:22  INFO xorp_rtrmgr:4757 RTRMGR +96 module_manager.cc
> >> execute ] Executing module: mfea4 (fea/xorp_fea)
> >> [ 2007/09/01 17:52:22 INFO xorp_fea MFEA ] Interface added: Vif[eth0]
> >> pif_index: 3 vif_index: 0 addr: 192.168.1.106 subnet: 192.168.1.0/24
> >> broadcast: 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST
> >> UNDERLYING_VIF_UP MTU: 1500
> >> [ 2007/09/01 17:52:22 INFO xorp_fea MFEA ] MFEA started
> >> [ 2007/09/01 17:52:22 INFO xorp_fea MFEA ] Interface enabled Vif[eth0]
> >> pif_index: 3 vif_index: 0 addr: 192.168.1.106 subnet: 192.168.1.0/24
> >> broadcast: 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST
> >> UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
> >> [ 2007/09/01 17:52:22 INFO xorp_fea MFEA ] Interface started: Vif[eth0]
> >> pif_index: 3 vif_index: 0 addr: 192.168.1.106 subnet: 192.168.1.0/24
> >> broadcast: 192.168.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST
> >> UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
> >> [ 2007/09/01 17:52:22 INFO xorp_fea MFEA ] Interface added: Vif[register_vif]
> >> pif_index: 3 vif_index: 1 addr: 192.168.1.106 subnet: 192.168.1.106/32
> >> broadcast: 192.168.1.106 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP
> >> MTU: 1500
> >> [ 2007/09/01 17:52:22 INFO xorp_fea MFEA ] Interface enabled Vif[register_vif]
> >> pif_index: 3 vif_index: 1 addr: 192.168.1.106 subnet: 192.168.1.106/32
> >> broadcast: 192.168.1.106 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP
> >> MTU: 1500 DOWN IPv4 ENABLED
> >> [ 2007/09/01 17:52:22 INFO xorp_fea MFEA ] Interface started:
> >> Vif[register_vif] pif_index: 3 vif_index: 1 addr: 192.168.1.106 subnet:
> >> 192.168.1.106/32 broadcast: 192.168.1.106 peer: 0.0.0.0 Flags: PIM_REGISTER
> >> UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
> >> [ 2007/09/01 17:52:22  INFO xorp_rtrmgr:4757 RTRMGR +96 module_manager.cc
> >> execute ] Executing module: mfea6 (fea/xorp_fea)
> >> [ 2007/09/01 17:52:22 INFO xorp_fea MFEA ] Interface added: Vif[eth0]
> >> pif_index: 3 vif_index: 0 addr: 2001:480:f022:3:400:8000:0:196 subnet:
> >> 2001:480:f022:3:400:8000::/84 broadcast: :: peer: :: Flags: MULTICAST
> >> BROADCAST UNDERLYING_VIF_UP MTU: 1500
> >> [ 2007/09/01 17:52:22 INFO xorp_fea MFEA ] MFEA started
> >> [ 2007/09/01 17:52:22  INFO xorp_rtrmgr:4757 RTRMGR +96 module_manager.cc
> >> execute ] Executing module: mld (mld6igmp/xorp_mld)
> >> [ 2007/09/01 17:52:22  WARNING xorp_rtrmgr:4757 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 "MLD"
> >> does not exist or is not enabled.
> >> [ 2007/09/01 17:52:22 INFO xorp_mld MLD6IGMP ] Protocol enabled
> >> [ 2007/09/01 17:52:22 INFO xorp_mld MLD6IGMP ] CLI enabled
> >> [ 2007/09/01 17:52:22 INFO xorp_mld MLD6IGMP ] CLI started
> >> [ 2007/09/01 17:52:23 INFO xorp_mld MLD6IGMP ] Protocol started
> >> [ 2007/09/01 17:52:23  ERROR xorp_mld:4763 MLD6IGMP +718 mld6igmp_node.cc
> >> add_vif ] Error updating primary address for vif eth0: invalid primary address
> >> [ 2007/09/01 17:52:24 INFO xorp_mld MLD6IGMP ] Interface enabled: Vif[eth0]
> >> pif_index: 3 vif_index: 0 addr: 2001:480:f022:3:400:8000:0:196 subnet:
> >> 2001:480:f022:3:400:8000::/84 broadcast: :: peer: :: Flags: MULTICAST
> >> BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv6 ENABLED
> >> [ 2007/09/01 17:52:24  ERROR xorp_mld:4763 MLD6IGMP +1083 mld6igmp_node.cc
> >> start_vif ] Cannot start vif eth0: invalid primary address
> >> [ 2007/09/01 17:52:24 WARNING xorp_mld XrlMld6igmpTarget ] Handling method for
> >> mld6igmp/0.1/start_vif failed: XrlCmdError 102 Command failed Cannot start vif
> >> eth0: invalid primary address
> >> [ 2007/09/01 17:52:24  ERROR xorp_rtrmgr:4757 RTRMGR +675 master_conf_tree.cc
> >> commit_pass2_done ] Commit failed: 102 Command failed Cannot start vif eth0:
> >> invalid primary address
> >> [ 2007/09/01 17:52:24  ERROR xorp_rtrmgr:4757 RTRMGR +251 master_conf_tree.cc
> >> config_done ] Configuration failed: 102 Command failed Cannot start vif eth0:
> >> invalid primary address
> >> [ 2007/09/01 17:52:24  INFO xorp_rtrmgr:4757 RTRMGR +2228 task.cc run_task ]
> >> No more tasks to run
> >> [ 2007/09/01 17:52:24  INFO xorp_rtrmgr:4757 RTRMGR +171 module_manager.cc
> >> terminate ] Terminating module: fea
> >> [ 2007/09/01 17:52:24  INFO xorp_rtrmgr:4757 RTRMGR +171 module_manager.cc
> >> terminate ] Terminating module: interfaces
> >> [ 2007/09/01 17:52:24  INFO xorp_rtrmgr:4757 RTRMGR +171 module_manager.cc
> >> terminate ] Terminating module: mfea4
> >> [ 2007/09/01 17:52:24  INFO xorp_rtrmgr:4757 RTRMGR +171 module_manager.cc
> >> terminate ] Terminating module: mfea6
> >> [ 2007/09/01 17:52:24  INFO xorp_rtrmgr:4757 RTRMGR +194 module_manager.cc
> >> terminate ] Killing module: mfea6
> >> [ 2007/09/01 17:52:24  INFO xorp_rtrmgr:4757 RTRMGR +171 module_manager.cc
> >> terminate ] Terminating module: mld
> >> [ 2007/09/01 17:52:24  INFO xorp_rtrmgr:4757 RTRMGR +194 module_manager.cc
> >> terminate ] Killing module: mld
> >> [ 2007/09/01 17:52:24  ERROR xorp_rtrmgr:4757 RTRMGR +747 module_manager.cc
> >> done_cb ] Command "/usr/local/xorp/mld6igmp/xorp_mld": terminated with signal
> >> 15.
> >> [ 2007/09/01 17:52:24  INFO xorp_rtrmgr:4757 RTRMGR +282 module_manager.cc
> >> module_exited ] Module killed during shutdown: mld
> >> [ 2007/09/01 17:52:24  ERROR xorp_rtrmgr:4757 RTRMGR +747 module_manager.cc
> >> done_cb ] Command "/usr/local/xorp/fea/xorp_fea": terminated with signal 15.
> >> [ 2007/09/01 17:52:24  INFO xorp_rtrmgr:4757 RTRMGR +282 module_manager.cc
> >> module_exited ] Module killed during shutdown: mfea6
> >> [root at FEON etc]#
> >>
> >>
> >>
> >> Pavlin Radoslavov wrote:
> >>     
> >>>> Anyone now what is missing to cause this not found error?  /usr/local/sbin
> >>>> has the file xorp_mld.
> >>>>
> >>>> 2007/08/31 16:33:41  INFO xorp_rtrmgr:666 RTRMGR +96 module_manager.cc
> >>>> execute ] Executing module: mld (mld6igmp/xorp_mld)
> >>>> [ 2007/08/31 16:33:41  WARNING xorp_rtrmgr:666 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 "MLD" does not exist or is not enabled.
> >>>>
> >>>>         
> >>> Did the xorp_rtrmgr execution continue after that?
> >>> Typically, this is a transient error during startup/shutdown, so if
> >>> the xorp_rtrmgr execution continued then you can ignore it.
> >>>
> >>> Regards,
> >>> Pavlin
> >>>
> >>>
> >>>       
> >>>> -- 
> >>>> Chris
> >>>>
> >>>> _______________________________________________
> >>>> Xorp-users mailing list
> >>>> Xorp-users at xorp.org
> >>>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >>>>
> >>>>         
> >>> _______________________________________________
> >>> Xorp-users mailing list
> >>> Xorp-users at xorp.org
> >>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >>>
> >>>
> >>>
> >>>       
> >> -- 
> >> Christopher Robson
> >> Senior Computer Scientist, GS-15
> >> Naval Research Laboratory
> >> Center for Computational Science
> >> Networking, Code 5591
> >> 4555 Overlook ave.
> >> Washington, D.C. 20375-5320
> >> (COM) 202-404-3138
> >> (VoIP) 2024043138 at GIGEF
> >> (CHAT) Chris.Robson at GIGEF
> >>     
> >
> >
> >   
> 
> -- 
> Christopher Robson
> Senior Computer Scientist, GS-15
> Naval Research Laboratory
> Center for Computational Science
> Networking, Code 5591
> 4555 Overlook ave.
> Washington, D.C. 20375-5320
> (COM) 202-404-3138
> (VoIP) 2024043138 at GIGEF
> (CHAT) Chris.Robson at GIGEF
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users



More information about the Xorp-users mailing list