Service guard found one error

[study unix]

"Failed to switch 10.88.6.225 from lan1 to lan0: Device busy",
how to resolve it ?

[Steven E. Protter]

Shalom,

ssh or otherwise log into the offending server and run:

lanscan

Check the serviceguard logs for other errors.

SEP

[Rita C Workman]

Did you (or someone) assign an IP to lan0? Because if lan0 is the failover lan for your lan1, then lan0 should not have an IP hard assigned to it.
Failover lan's 'inherit' the IP, they do not have an IP assigned.

Interesting, cause generally I set up lan0 (which is generally the lan port on the core)with the hard IP assigned, and then would have lan1 or lan2...etc as my failover lans.

Maybe I just need a cup of coffee,
Rita

[Bhadresh]

The switch is failing with Device busy. It indicates lan0 is in an invalid state. Device busy usually indicates that the lan is already configured.

Regards,
Bhadresh

[study unix]

Hi Rita,
Lan0 is primary lan, and lan 1 is failvoer lan to lan 0, that is, lan 0 is backup lan,
currently, lan 1 is switching to lan 0 the result is error message "Failed to switch 10.88.6.225 from lan1 to lan0: Device busy",
thanks for your support!

[study unix]

Hi Bhadresh ,
as your words,if lan 0 has been configured, then I run below command , can you feel it is worth action?
1.ifconfig lan0 plumb
2.ifconfig lan0 up

[Vijaykumar_1]

what is the status of lan0 interface? whether it is up?

pls post lanscan o/p..

[study unix]

Hi All,
All lan card status is up, so I am confused with it! who ever dealt with similar case!

[Rita C Workman]

Please post what version of O/S and version of MCSG are you running.

Please run and post output of:

netstat -rn

Thanks,
Rita

[Stephen Doud]

Try the following:
1) run landiag and reset it.

# landiag


Enter command: lan


-> at this point, before resetting the NIC, enter 'display' to inspect the NIC stats and look for large errors or a cause for the NIC to fail to respond.

When you are ready to try a reset a NIC, you can either use 'PPA' to point landiag to a new NIC, or accept the default (lan0)

Enter command: reset
Resetting LAN Interface to run selftest.

LAN Interface test mode. LAN Interface PPA Number = 0


2) unplumb and re-plumb the 'busy' NIC.

Examples:
# ifconfig lan0 unplumb
# ifconfig lan0 plumb

(landiag -> reset may be necessary again)
---

Hopefully lan0 will become usable after one of these and Serviceguard will automatically move traffic back to the primary NIC.

[Deeos]

Hi,


lan0 primary
lan1 stand by


#more /etc/rc.config.d/netconf file to check lan0 assigned or not?

#lanadmin -x 0

#ifconfig lan0 unplumb
#ifconfig lan1 unplumb

#/sbin/init.d/net stop
#/sbin/init.d/net start


#netstat -in



Regards
Deeos

[stephen peng]

Eyeshot,
guys were not so clear what problem you encountered, so just please post everything needed!