Operating System - HP-UX
1827593 Members
2790 Online
109965 Solutions
New Discussion

SCSI drive and NIC difficulty

 
Melissa Murphy
Advisor

SCSI drive and NIC difficulty

Hello, everyone.

I have two mostly independent problems today. Firstly, I have a few HP K460s that had a built-in 10Mbit NIC in them, then an additional 100Mb expansion NIC. I am not quite sure how to make it so that SAM sees the unused 100baseT card so I can switch the IP from the 10 to it. Does it have anything to do with btlan1 and installing this driver? I am pretty unfamiliar with installing new hardware on these systems.

Second, some of these K460s have external SCSI hard drives that I would like to mount. They are plugged in to the SCSI port on the machine, they are receiving power, and are turned on. I believe it must be a somewhat similar process to my first problem, because I'm not sure how to just get the hardware to be recognized. In an ioscan I believe I can see these:


ext_bus 1 10/4/12 scsi3 CLAIMED INTERFACE HP 28696A - Wide SCSI ID=7
unknown -1 10/4/12.1 UNCLAIMED UNKNOWN SEAGATE ST19171W
unknown -1 10/4/12.1.0 UNCLAIMED UNKNOWN SEAGATE ST19171W
lan 0 10/4/16 btlan1 UNCLAIMED UNKNOWN HP HP-PB 100 Base TX card


In SAM I can go to Kernel Config => Drivers and their current and pending states are 'in'. Should they be 'out'? Any help at all would be appreciated. Thank you very much.

Melissa
5 REPLIES 5
Babak
Valued Contributor

Re: SCSI drive and NIC difficulty


For the Hard drive, in configurable kernel parameters look for disc1 disc2 disc3 drivers, you may need one of these drivers to allow you access to the drives. Also if you are running HP-UX 10.20 you may need to install a newer ACE bundle to provide you with some of the newer drivers.

For the NIC card, run "ioscan -fnC lan". If the output lists all of your network connections (ignore loopback), the drivers are installed. If the ioscan does not list everything and a simple "ioscan" output shows the lan card as unknown, then you will probabely need to install the software/driver for the NIC card(you should be able to find the software for the driver in one of the HP-UX application CDs).
Once the driver issues are resolved, you will need to disable the card with ip address "A" before you can assign the same IP address to another NIC card. Also, be aware that with a multi host HP-UX box, each assigned IP address will need to be in a separate subnet.

Hope this helps.

B.

p.s. Be carefull with the drives, if you are using them in a cluster/shared environment.

Robert_Jewell
Honored Contributor

Re: SCSI drive and NIC difficulty

I may be able to give you a little help with the drives. UNCLAIMED means that the system cannot find a driver for the device. However you are booting from something so I assume that the sdisk driver is there. You can verify what drivers are loaded by using SAM ('In' refers to a loaded driver, or a driver that will be loaded if marked under Pending) or the command lsdev. The sdisk has a major number of 31. You could also try running the command insf -e to try and re-install the device files, but I am not sure that will work without the system recognizing it as a disk first.

-Bob
----------------
Was this helpful? Like this post by giving me a thumbs up below!
Babak
Valued Contributor

Re: SCSI drive and NIC difficulty

Let me correct myself. Look for the disc(x) drivers in SAM->Drivers and not in the configurable kernel parameters.

Rgds,
B.
Mike Shilladay
Esteemed Contributor

Re: SCSI drive and NIC difficulty

Hi Melissa,

To solve the problem with the network cards you will need to load the drivers. If the cards are located in the HP-PB slots (to the left of the Multifunction IO Card when looking from the rear) then you will need the software driver J2759BA. As your listing suggests you are using the HP-PB network Card. Please note that any drivers that you add to the kernel will require a reboot.

As for the disks, another item that you may wish to check for is the PDC. Old versions of the PDC do not support later disks and memory modules, so if you find that the extra disk drivers as explained in previous replies do not solve the problem, you may need to look at this. If the PDC does need upgrading, this will require downtime as well as taking the precation of taking a full backup before you attempt it.

Hope this helps,

Mike.

Melissa Murphy
Advisor

Re: SCSI drive and NIC difficulty

Alright guys, sorry it's taken me a bit to get back to you. Seems all the SCSI drives are working out for me - thanks for your help. Now I'm only suffering with half of my HPs with NIC problems. The systems that are working use the driver btlan1 for the NIC, so that's what I've loaded up on the others. In SAM I go to the kernel and rebuild it, reboot. (I've had a problem where the driver won't show up in SAM, so I've just edited /stand/build/system, added btlan1, and did mk_kernel, then rebooted. Is this okay?) When I 'ioscan -fnC lan' I can see the card with the driver assigned to it, but after a reboot it is still UNCLAIMED, UKNOWN. SAM sees both the NICs now, but if I go to configure the 100baseT I get an "error: lan0 interface | PPA 0: Old station Address = 'blah blah blah' New station Address = 'blah blah blah'" The new and the old are the same. I also get that there is already an entry for the hostname and IP address. I have disabled the 10baseT card that used the IP address that I want to use. How can I fix this so that I can configure the new card without running into hardware address problems? I hear there is a way to change or spoof the hardware address. Is this discouraged? What can I do to get these faster NICs up and running? Thanks a ton!

Later,
Melissa