Let's see if it is a system issue or a XORP issue. What is the output of running the following command as root?
vconfig add eth1 10 If that doesn't return an error it would help to see the whole log file. cheers, robert. Rodney Prescott wrote: > Hi Robert, > > Thanks for the response, please find the tail of the logfile, basically > states interface not recognised > > Help would be most appreciated! > > wthree:/var/log# tail messages > Sep 17 09:17:58 localhost xorp_rtrmgr: [ 2007/09/17 09:17:58 ERROR > xorp_rtrmgr:3935 RTRMGR +701 > /home/autobuild/builds/master/2007-08-23-1113/ofr/xorp/xorp/rtrmgr/master_conf_tree.cc > commit_pass2_done ] Commit failed: 102 Command failed Interface error on > eth1.10: interface not recognized > Sep 17 09:18:17 localhost xorp_fea: [ 2007/09/17 09:18:17 ERROR > xorp_fea:3994 FEA +99 > /home/autobuild/builds/master/2007-08-23-1113/ofr/xorp/xorp/fea/ifconfig_set.cc > push_config ] Interface error on eth1.10: interface not recognized > Sep 17 09:18:17 localhost xorp_fea: [ 2007/09/17 09:18:17 WARNING > xorp_fea XrlFeaTarget ] Handling method for ifmgr/0.1/commit_transaction > failed: XrlCmdError 102 Command failed Interface error on eth1.10: > interface not recognized > Sep 17 09:18:17 localhost xorp_rtrmgr: [ 2007/09/17 09:18:17 ERROR > xorp_rtrmgr:3935 RTRMGR +701 > /home/autobuild/builds/master/2007-08-23-1113/ofr/xorp/xorp/rtrmgr/master_conf_tree.cc > commit_pass2_done ] Commit failed: 102 Command failed Interface error on > eth1.10: interface not recognized > Sep 17 09:19:19 localhost login[12798]: (pam_unix) check pass; user unknown > Sep 17 10:30:23 localhost kernel: bnx2: eth1 NIC Link is Down > Sep 17 11:34:15 localhost kernel: bnx2: eth0 NIC Link is Down > Sep 17 11:40:50 localhost xorp_fea: [ 2007/09/17 11:40:50 ERROR > xorp_fea:3994 FEA +99 > /home/autobuild/builds/master/2007-08-23-1113/ofr/xorp/xorp/fea/ifconfig_set.cc > push_config ] Interface error on eth1.10: interface not recognized > Sep 17 11:40:51 localhost xorp_fea: [ 2007/09/17 11:40:50 WARNING > xorp_fea XrlFeaTarget ] Handling method for ifmgr/0.1/commit_transaction > failed: XrlCmdError 102 Command failed Interface error on eth1.10: > interface not recognized > Sep 17 11:40:51 localhost xorp_rtrmgr: [ 2007/09/17 11:40:50 ERROR > xorp_rtrmgr:3935 RTRMGR +701 > /home/autobuild/builds/master/2007-08-23-1113/ofr/xorp/xorp/rtrmgr/master_conf_tree.cc > commit_pass2_done ] Commit failed: 102 Command failed Interface error on > eth1.10: interface not recognized > > On 18/09/2007, at 11:57 AM, Robert Bays wrote: > >> Hi Guys, >> >> I know this response is *way* overdue... Sorry about that. FWIW, I >> just tried this on a freshly booted livecd and didn't see any errors. >> Maybe there is a clue in the /var/log/messages file? >> >> Cheers, >> Robert. >> >> Nick Davey wrote: >>> Hmm, that's odd. I'm getting the same problem on eth1 on my OFR. >>> >>> set interfaces ethernet eth1 vif 1024 >>> [edit] >>> [EMAIL PROTECTED] commit >>> [edit] >>> Commit Failed >>> 102 Command failed Interface error on eth1.1024 : interface not >>> recognized >>> >>> I attempted to just create the VLAN interface without IPing it to see if >>> there was some sort of race condition, but that doesn't seem to be the >>> case. I also tried with a higher VLAN id in case that was some sort of >>> issue. This also seems to affect the web interface, as I can't create >>> vif's from the web interface. Maybe I'm doing something wrong though. >>> The weird thing is is that I'm already using VLAN interfaces... >>> >>> Nick >>> >>> On 9/6/07, *Rodney Prescott* <[EMAIL PROTECTED] >>> <mailto:[EMAIL PROTECTED]>> wrote: >>> >>> Hi, >>> >>> Trying as per the documentation set up VLANs on the Community >>> version >>> 2.2 >>> >>> So here is the problem >>> >>> [edit] >>> [EMAIL PROTECTED] set interfaces ethernet eth1 vif 40 address >>> 10.10.40.65 <http://10.10.40.65> prefix-length 24 >>> [edit] >>> [EMAIL PROTECTED] commit >>> [edit] >>> Commit Failed >>> [EMAIL PROTECTED] led Interface error on eth1.40: interface not >>> [EMAIL PROTECTED] >>> [edit] >>> >>> Does it on both the WEB interface and as above on the CLI, gets the >>> same error message when Commit is used on the web as well >>> >>> >>> HELP, as I need to have VLANs running for the Wireless Gear I am >>> running, the multi SSIDs need unique VLANS >>> >>> Thanks in anticipation >>> _______________________________________________ >>> Vyatta-users mailing list >>> Vyatta-users@mailman.vyatta.com >>> <mailto:Vyatta-users@mailman.vyatta.com> >>> http://mailman.vyatta.com/mailman/listinfo/vyatta-users >>> <http://mailman.vyatta.com/mailman/listinfo/vyatta-users> >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Vyatta-users mailing list >>> Vyatta-users@mailman.vyatta.com >>> http://mailman.vyatta.com/mailman/listinfo/vyatta-users > _______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
