> : Sam won't enable lan0, and lanscan reports DOWN for the
> : hardware state.
> lanscan (and landiag) check the selftest state of the LAN card. The most
> common problem is that a valid LAN connection is not present. For thinlan
> (ie, a BNC connector), two (2) terminators must be present on the LAN
> cable and the CPU must be plugged into the LAN. Otherwise, the LAN card
> fails selftest and produces the DOWN state. Similarly for AUI and twisted
> pair cables.
In most cases, if your machine was booted up without a valid LAN present,
you have to go into 'landiag' to 'reset' the interface, otherwise,
it will remain in DOWN state. Same goes if you took off the LAN cable long
enough for it to go to DOWN state, it will not get back to the UP state
unless you maually do a reset.
Why doesn't HP-UX automatically recognize the new presence of a LAN?
Our software heavily rely on the LAN. There have been cases where the
users kicked the connected off (ya I know, should have secure it better,
but our hardware guys did the job :-8 ) and the software just waits
forever for the LAN to come back. They ended up resetting the LAN interface
everytime they do a retry.
Why is it the way it is? Curious minds like to know...
Angela Bao -- Project Peace Shield | #include <std.disclaimer>
Sys Admin Sector XXX, don't ask me which one...