topic Re: NIC card not recognized in Operating System - HP-UX

NIC card not recognized

Janet Sanberg — Thu, 23 Oct 2008 12:18:01 GMT

I have a NIC card on a rp7400 which is not working (unable to ping host). The rp7400 is vpar'd 5 ways. When I vparreset -p (hostname) -h, the entire box crashes and I get the following error on the console for this host:

The system is ready.

GenericSysName [HP Release B.11.11] (see /etc/issue)
Console Login:
**************************100 Mb/s LAN/9000 Networking**********************@#%
Wed Oct 23 PDT 2008 05:51:12.751706 DISASTER Subsys:BTLAN Loc:00000
<6004> 10/100BASE-T driver detected a command timeout for
the adapter in slot(Crd In#) 0.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

**************************100 Mb/s LAN/9000 Networking**********************@#%
Wed Oct 23 PDT 2008 05:51:12.758157 DISASTER Subsys:BTLAN Loc:00000
<6003> 10/100BASE-T driver failed to send the first setup frame
to the adapter in slot(Crd In#) 0. Driver is defunct (BTLAN_DOWN).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I brought this vpar up in single user mode to trouble shoot and found that a lanscan and lanadmin shows the card as "up" but when I go into SAM to look at the card it says there is no Network Interface Card installed on the system but and ioscan shows that it is there.

Re: NIC card not recognized

RAC_1 — Thu, 23 Oct 2008 12:27:58 GMT

Have not worked much on npar/vpar. First thing i will do is patches!! then card specific things.

Re: NIC card not recognized

Torsten. — Thu, 23 Oct 2008 12:46:41 GMT

Many BTLAN patches talk about fixes regarding timeout, hang and even panics.

Is it lan0?

Re: NIC card not recognized

Janet Sanberg — Thu, 23 Oct 2008 12:50:19 GMT

Yes, lan0.

Re: NIC card not recognized

Torsten. — Thu, 23 Oct 2008 12:57:24 GMT

Does the ioscan looks like this:

lan 0 0/0/0/0 btlan CLAIMED INTERFACE HP PCI 10/100Ba
se-TX Core

This is on the core I/O card.

I would first check if the system is patched up-to-date, then consider to ask hp support for help regarding suspect hardware.

BTW, I never received any points from you in many of your other threads.

Re: NIC card not recognized

Janet Sanberg — Thu, 23 Oct 2008 13:00:39 GMT

The LAN card in in slot 0/5. I promise I will assign points once this is resloved!

Re: NIC card not recognized

Torsten. — Thu, 23 Oct 2008 13:04:49 GMT

OK, this is PCI slot 1.

Do you have a similar card in another slot or spare?

Anyway, check the patches too.

Re: NIC card not recognized

Janet Sanberg — Thu, 23 Oct 2008 17:25:53 GMT

Do you think the card needs to be erplaced? I hestitate to think it is patches, this host is an exact clone of about 70 others, all with the same patches, who are not having this issue.

Re: NIC card not recognized

Torsten. — Thu, 23 Oct 2008 17:27:06 GMT

Let's see what you have - please post

# swlist

Re: NIC card not recognized

Janet Sanberg — Thu, 23 Oct 2008 17:55:16 GMT

# swlist
# Initializing...
# Contacting target "payub079"...
ERROR: Could not contact host "payub079" because of an invalid
protocol sequence. Protocol sequences are specified with the
"-x rpc_binding_info" option. Make sure this option is
specified correctly.
ERROR: More information may be found in the daemon logfile on this
target (default location is
payub079:/var/adm/sw/swagentd.log).
#

Re: NIC card not recognized

Torsten. — Thu, 23 Oct 2008 18:20:56 GMT

A single problem is not enough ...

Anything in var/adm/sw/swagentd.log ?

Try a restart

# swagentd -r

Re: NIC card not recognized

Janet Sanberg — Thu, 23 Oct 2008 18:33:49 GMT

Still no good news...

# swagentd -r
ERROR: swagentd exiting due to initialization error in background
process. Check the logfile "/var/adm/sw/swagentd.log" for
more information.

======= 10/23/08 12:28:11 PDT BEGIN swagentd (pid = 584).

ERROR: Invalid protocol sequence specified as part of the
"rpc_binding_info=" configuration option.
ERROR: Terminating prematurely - cannot serve Remote Procedure Call
requests.

======= 10/23/08 12:32:19 PDT END swagentd (pid = 589, startup
error).

Re: NIC card not recognized

Torsten. — Thu, 23 Oct 2008 18:37:06 GMT

Check this:

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1262587

Re: NIC card not recognized

Janet Sanberg — Thu, 23 Oct 2008 18:56:15 GMT

Some of the suggestions in the thread require host to be on the network, but I tried those which don't (checking nsswitch and putting entry in /var/adm/sw/defaults) with no luck. I'm wondering if I should just rebuild this thing, I have a bunch of images from clones.

Re: NIC card not recognized

rick jones — Thu, 23 Oct 2008 22:37:28 GMT

Have you tried replacing the NIC yet with one that is known to be good or a spare?

When lanadmin shows "up" is that the *administrative* (aka desired) state or the *operational* (aka actual) state?

What exactly does ioscan show for the card?

Have you tried any of the online diagnostics?

Re: NIC card not recognized

Janet Sanberg — Fri, 24 Oct 2008 12:18:26 GMT

Have not tried to replace NIC although HP CE has looked at it and Networking group has checked connections and all hardware looks healthy. This is a vpar'd host with some of the other vpars being 27/7, replacement would entail downtime, so that will be a last resort. Ioscan looks like this:

# ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
lan 0 0/5/0/0 btlan CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/1
00Base-TX Addon
/dev/diag/lan0 /dev/ether0 /dev/lan0

Both admisitrative and operational status are up. STM is not working, but no HW errors were generated before it stopped working (I have an audit script that would have caught them prior to it going off net)

Re: NIC card not recognized

Torsten. — Fri, 24 Oct 2008 12:21:40 GMT

What else is wrong with this box?

- LAN now working
- sw tools not working
- stm not working

Is actually something working?

Re: NIC card not recognized

Torsten. — Fri, 24 Oct 2008 12:25:46 GMT

If this system is setup to resolve names via DNS first and LAN is not working, you will have problems with all network dependent tools.

If needed, switch to search in /etc/hosts first.

Re: NIC card not recognized

Janet Sanberg — Fri, 24 Oct 2008 12:45:20 GMT

When I do an nslookup it is defaulting to "files" (as it is set up to do) and is working, using a vaild /etc/hosts.

Is sw and stm dependent on network?

Re: NIC card not recognized

Torsten. — Fri, 24 Oct 2008 12:46:51 GMT

More or less. Both are following the client server model.

If the client is trying to resolve the name via DNS but DNS is not working, it will not work even.