Changing a LAN card Driver

[rick jones]

A couple tings about linkloop - first, the remote system, which you specify by MAC address, must know how to interpret the frame linkloop sends (it is either an XID or TEST frame IIRC). Another HP-UX system will know how to interpret the frame, as would a Linux system running a linkloop server from sourceforge.

The first linkloop failure with the Unix errno of 57 suggests there is no link up - either no cable, bad cable, or nothing live at the other end of the cable:

$ grep 57 /usr/include/sys/errno.h
#define ENOLINK 57 /* the link has been severed */
#define ECONFIG 157 /* Configured kernel resource exhausted */

The second failure looks a bit more obscure:

$ grep 4 /usr/include/sys/errno.h
# if defined(_REENTRANT) && !defined(_PTHREADS_DRAFT4)
# else /* ! _REENTRANT || _PTHREADS_DRAFT4 */
# endif /* ! _REENTRANT || _PTHREADS_DRAFT4 */
# define ERANGE 34 /* Math result not representable */
#define EINTR 4 /* interrupted system call */
#define EFAULT 14 /* Bad address */

I'm guessing that is a timer popping when there was no reply from the remote MAC, which brings us back to the bit about the remote needing to grok the frame sent by linkloop.

[Torsten.]

A very basic step in troubleshooting is to observe the LED status.

At least the build in NICs will indicate the connection as 10/100/1000.

How about this?
(just for the case of a bad cable)

This is similar for the A7012A NIC.
There is an activity/link LED and the other will indicate the speed.

http://docs.hp.com/en/5971-4261/ch01s02.html#d0e710

[rick jones]

and if you cannot be physically present to see the blinking lights, careful examination of both the administrative and operational state of the interface as shown with say lanadmin -g mibstats may be helpful.

[V.Manoharan]

Hi andrew,
you can probly check the following
1. check physically whether link led glow properly.
2. connect an cross cable and check the ping status.
3. you can check the nettl log output for any cable issues/harware issues.
4. check whether local ping and telnet works well.
5. check the parameters of ip_send_source_quench and ip_ire_gw_probe using ndd get command.

ndd -get /dev/ip ip_send_source_quench
ndd -get /dev/ip ip_ire_gw_probe
if above return stauts 1 try change to 0 by.

ndd -set /dev/ip ip_send_source_quench 0
ndd -set /dev/ip ip_ire_gw_probe 0

[Andrew Pollard]

Hi,

I had to open a call with HP support. They are still working on the problem.

Thanks for all your suggestions.

Andrew