10/100BaseT card issues

[OldSchool]

I'm attempting to install / configure a 10/100BaseT HP-PB card (product A3495) on a K-580 running HP-UX 11.0.

To date, the following has occurred:

Installed driver depot base fileset provided by HP. System built kernel and reboot proceeded w/o incident.

Shutdown system and installed card. Power up and reboot again ran ok. IOSCAN shows the card CLAIMED w/ driver BTLAN1 attached. Run SAM -> Network -> NIC, and the card is there and unconfigured, which I expected.

Yesterday, I attempted to use SAM to configure the IP address and thats when the problems began. I assigned the IP as specified by out networking group, and when I hit "OK", SAM took a long time to close. It popped-up an error msg, noting the "OLD" station address and the "NEW" station address, which were the same.

I clicked on the message box, and waited...and waited... and waited...(about 10 minutes total) for SAM to complete saving the new information.

When the save completed, SAM showed the new NIC as enabled and had the correct IP associated with it, however;

I could no longer open new terminals in X-windows
Could not establish telnet session to box
Could not restart SAM (no errors, no messages, no response)

Rebooted, and the new card reported a cable error. The cable was indeed wrong and was replaced. Link light on the hub comes on, no link light / activity on card.

Reboot. rc.log shows that the new card (lan3) had an error when it attempted to configure it. Problems w/ x and telnet continued.

I eventually shutdown, popped the card and rebooted, and the problems are gone, but the network guys still want the card installed.

It looks like SAM partially configured the card, but didn't get all of the information in the correct files.

Attached are files w/ SAMs output after the card was installed along w/ ioscan. Portion of the rc.log is also attached as well as copy of files netconf and hpbasetconf from /etc/rc.config.d.

Can the card be configured by editing the above, and skipping SAM.

Two other points:
the box also has the 10BaseT interface in the core io board, and also contains a FDDI and Token Ring interface.

I also have another 10/100 card available, but my first inclination is that its all a configuration issue.

Anyone care to shed some light on the above?

Thx...Scott

[Steven E. Protter]

Shalom Scott,

Check the server slot diagram at http://docs.hp.com on your K580.

Only certain cards and types of cards will work in certain slots, regardless of whether they fit.

You gave a lot of information, but omitted the OS version and bits. In all but the latest 11i releases many older cards were not configurable in a 64 bit installation.

What Core Os is installed, and what is the patch state of the OS? Later is better in both scenarios.

SEP

[Rita C Workman · Accepted solution]

Greetings System Administrator,

I'm not a fan for SAM for networking tasks, generally when I need to quickly set up a lancard I just do it from the command line.

I like to run lanscan & netstat -rn to check what's out there first (just me..)

to assign the IP to the new card:
ifconfig lan<#> netmask 255.255.255.0
(or whatever your netmask needs to be..)

Then I go in and edit the /etc/rc.config.d/netconf and make sure the entries are there...and that the lan speed is set up right, in your case the hpbtlanconf file.

Some of the other things were 'interesting' to me...like that NODENAME.
But I'm no networking guru...I'm strictly vanilla and keep it simple. So I'll leave that alone.

Kindest regards,
Rita

[OldSchool]

Hi Steve and Rita,

Its HP-UX 11.0 / 32 bit.

Checked the link you gave Steve, and the slot I used was a single-height HP-PB slot w/ a HP-PB card (slot id 10/4/8). Couldn't find anything more specific, so I (ahem) *assume* it should work...

Did find the install manual for the card however, and I do possibly need additional patches for lanadmin and sam. I'll have to wait until later in the week or weekend to try anything else w/ this.

Thanks for the responses, and I'll let you know what the progress is.

[rick jones]

Unless you feel compelled to alther link-level settings, it should suffice to mimic what you see in /etc/rc.config.d/netconf for your other interfaces.

There are other "issues" if you wish to assign mulitple physical NICs to the same IP subnet.

[OldSchool]

ok...the patches are up to date.

Keeping in mind that this is 32bit 11.0, to manually configure this card, I need to:

put the ip address info and interface name in the "netconf" file, and the configuration info (name, speed) in hpbasetconf.

it appears that the hpbtlanconf noted previously is specific to 11i.

Is this correct, or am I barking up the wrong tree?

[rick jones]

Unless you are hardcoding speed and duplex settings, netconf should suffice. You may need/want to update /etc/hosts as well.

[Victor Fridyev]

Hi,

Could you please provide with an output of lanscan and netstat -rn and ifconfig lan1, ifconfig lan2 and ifconfig lan3.

HTH

[OldSchool]

finally was able to get back to this after being out on the disabled list for the last 3 weeks.

problem was finally isolated as being a bad cable connection between the card and the router.

network guys "built" 2 cables, both of which caused problems. third cable, used w/ second card worked like a champ. re-installed first card and it functions properly as well.

the interesting thing is, the cable failure message didn't appear during boot, but at config time. and once the message was received, you can't telnet into the box on the other lan card either and sam wont start in xwindows......

thanks to all who replied.