[Xorp-users] mfea4 issues
Nicholas Schmidt
nschmidt at mediamath.com
Fri Feb 25 08:46:03 PST 2011
I have provided the configuration and error in my original email. Here it is again for those who have missed it. I have read through and configured per the Getting Started documentation.
-Nick
Log:
[ 2011/02/24 16:26:54 INFO xorp_rtrmgr:3981 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea)
[ 2011/02/24 16:26:58 INFO xorp_rtrmgr:3981 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea)
[ 2011/02/24 16:27:05 INFO xorp_rtrmgr:3981 RTRMGR +101 module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea)
[ 2011/02/24 16:27:05 INFO xorp_fea MFEA ] Interface added: Vif[eth0.33] pif_index: 4 vif_index: 0 addr: 74.121.138.180 subnet: 74.121.138.0/24 broadcast: 74.121.138.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2011/02/24 16:27:05 INFO xorp_fea MFEA ] Interface added: Vif[eth0.512] pif_index: 5 vif_index: 1 addr: 10.3.3.1 subnet: 10.3.3.0/24 broadcast: 10.3.3.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2011/02/24 16:27:05 ERROR xorp_fea:3982 MFEA +709 mfea_mrouter.cc start_mrt ] setsockopt(MRT_INIT, 1) failed: Address already in use
[ 2011/02/24 16:27:05 INFO xorp_fea MFEA ] MFEA started
[ 2011/02/24 16:27:05 INFO xorp_fea MFEA ] Interface enabled Vif[eth0.33] pif_index: 4 vif_index: 0 addr: 74.121.138.180 subnet: 74.121.138.0/24 broadcast: 74.121.138.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2011/02/24 16:27:05 ERROR xorp_fea:3982 MFEA +1113 mfea_mrouter.cc add_multicast_vif ] setsockopt(MRT_ADD_VIF, vif eth0.33) failed: Address already in use
[ 2011/02/24 16:27:05 ERROR xorp_fea:3982 MFEA +1191 mfea_node.cc start_vif ] Cannot start vif eth0.33: cannot add the multicast vif to the kernel
[ 2011/02/24 16:27:05 WARNING xorp_fea XrlMfeaTarget ] Handling method for mfea/0.1/start_vif failed: XrlCmdError 102 Command failed Cannot start vif eth0.33: cannot add the multicast vif to the kernel
[ 2011/02/24 16:27:05 ERROR xorp_rtrmgr:3981 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Cannot start vif eth0.33: cannot add the multicast vif to the kernel
[ 2011/02/24 16:27:05 ERROR xorp_rtrmgr:3981 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Cannot start vif eth0.33: cannot add the multicast vif to the kernel
[ 2011/02/24 16:27:05 INFO xorp_rtrmgr:3981 RTRMGR +2233 task.cc run_task ] No more tasks to run
[ 2011/02/24 16:27:05 INFO xorp_rtrmgr:3981 RTRMGR +176 module_manager.cc terminate ] Terminating module: fea
[ 2011/02/24 16:27:05 INFO xorp_rtrmgr:3981 RTRMGR +176 module_manager.cc terminate ] Terminating module: firewall
[ 2011/02/24 16:27:05 INFO xorp_rtrmgr:3981 RTRMGR +176 module_manager.cc terminate ] Terminating module: interfaces
[ 2011/02/24 16:27:05 INFO xorp_rtrmgr:3981 RTRMGR +176 module_manager.cc terminate ] Terminating module: mfea4
[ 2011/02/24 16:27:05 INFO xorp_rtrmgr:3981 RTRMGR +199 module_manager.cc terminate ] Killing module: mfea4
[ 2011/02/24 16:27:05 ERROR xorp_rtrmgr:3981 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/fea/xorp_fea": terminated with signal 15.
[ 2011/02/24 16:27:05 INFO xorp_rtrmgr:3981 RTRMGR +287 module_manager.cc module_exited ] Module killed during shutdown: mfea4
Configuration:
interfaces {
restore-original-config-on-shutdown: false
interface eth0.33 {
description: "data interface"
disable: false
/* default-system-config */
vif eth0.33 {
disable: false
address 2.2.2.2 {
prefix-length: 24
broadcast: 2.2.2.255
disable: false
}
}
}
interface eth0.512 {
description: "data interface"
disable: false
/* default-system-config */
vif eth0.512 {
disable: false
address 1.1.1.1 {
prefix-length: 24
broadcast: 1.1.1.255
disable: false
}
}
}
}
fea {
unicast-forwarding4 {
disable: false
}
}
protocols {
static {
route 1.1.0.0/22 {
next-hop: 10.3.3.2
metric: 1
}
route 1.1.3.0/24 {
next-hop: 74.121.138.1
metric: 1
}
}
}
plumbing {
mfea4 {
disable: false
interface eth0.33 {
vif eth0.33 {
disable: false
}
}
interface eth0.512 {
vif eth0.512 {
disable: true
}
}
interface register_vif {
vif register_vif {
/* Note: this vif should be always enabled */
disable: false
}
}
traceoptions {
flag all {
disable: false
}
}
}
}
protocols {
pimsm4 {
disable: false
interface eth0.33 {
vif eth0.33 {
disable: false
/* enable-ip-router-alert-option-check: false */
/* dr-priority: 1 */
/* hello-period: 30 */
/* hello-triggered-delay: 5 */
}
}
interface eth0.512 {
vif eth0.512 {
disable: false
/* enable-ip-router-alert-option-check: false */
/* dr-priority: 1 */
/* hello-period: 30 */
/* hello-triggered-delay: 5 */
}
}
interface register_vif {
vif register_vif {
/* Note: this vif should be always enabled */
disable: false
}
}
static-rps {
rp 6.6.6.6 {
group-prefix 224.0.0.0/4 {
/* rp-priority: 192 */
/* hash-mask-len: 30 */
}
}
}
switch-to-spt-threshold {
/* approx. 1K bytes/s (10Kbps) threshold */
disable: false
interval: 100
bytes: 102400
}
traceoptions {
flag all {
disable: false
}
}
}
}
protocols {
igmp {
disable: false
interface eth0.33 {
vif eth0.33 {
disable: false
/* version: 2 */
/* enable-ip-router-alert-option-check: false */
/* query-interval: 125 */
/* query-last-member-interval: 1 */
/* query-response-interval: 10 */
/* robust-count: 2 */
}
}
interface eth0.512 {
vif eth0.512 {
disable: false
/* version: 2 */
/* 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
}
}
}
}
On 2/25/11 11:41 AM, "Ray Soucy" <rps at maine.edu> wrote:
Hi Nicholas,
We have a pretty large XORP deployment for multicast. In our
experience 90% of problems people run into are configuration issues.
Can you provide us with your XORP configuration? Also be sure to
check that you don't have iptables blocking the traffic.
On Fri, Feb 25, 2011 at 11:32 AM, Nicholas Schmidt
<nschmidt at mediamath.com> wrote:
> This is a clean installation of Debian with no routing processes in the
> background running Kernel 2.6.26-2-amd64 and xorp version 1.6
>
> -Nick
>
>
> On 2/24/11 7:23 PM, "Ben Greear" <greearb at candelatech.com> wrote:
>
> On 02/24/2011 01:30 PM, Nicholas Schmidt wrote:
>> Greetings list,
>> I am attempting to run xorp for the first time to satisfy some multicast
>> routing needs that is not currently supported by our hardware vendor. I have
>> attempted
>> to write the simplist possible configuration for my needs based on the
>> guides provided by I receive an MFEA4 error when attempting to launch the
>> application.
>> Any help would be appreciated.
>
> Are you running any other routing daemons, or maybe some xorp processes
> running in the background?
>
> What xorp version?
>
> What kernel version?
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
>
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>
--
Ray Soucy
Epic Communications Specialist
Phone: +1 (207) 561-3526
Networkmaine, a Unit of the University of Maine System
http://www.networkmaine.net/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110225/1bb8753e/attachment-0001.html
More information about the Xorp-users
mailing list