lan drivers

[Beth Weller]

I loaded patch J2780BA onto my UNIX 11 box. My lan card was working fine with driver btlan0. Then I enlarged /var and rebooted and the system wants to use driver lan.

Tried Sam, network & commo, card config, modify

and it will not let me change the driver!!!!!!!!!

How do I get the card to use the driver btlan0?

[Pete Randall]

J2780BA is "EISA 10/100Base-TX/9000 LAN software". Why were you loading it?

Pete

[Ajit Natarajan]

I have a few questions:

1. Which OS version? 11.0 or 11.11?

2. Not sure what you mean by ``patch J2780BA''. Were you installing a patch for J2780BA? What was the patch number?

3. You say that the system now wants to use lan as the driver. How did you determine that? What led you to the conclusion that the system wants to use the driver lan? Do you mean that the lanscan output changed?

Answers to these questions may help us figure out what is going on.

Thanks.

Ajit
HP Gigabit Ethernet

[Beth Weller]

I upgraded from HP UNIX 10.20 to HP UNIX 11.0. I have 2 lan cards one built in (I was told that one was incompatable by a coworker). The Eisa card worked after the I loaded the software J2780BA that loaded the EISA 100 Base T card and as I said the card was working fine. The lanscan and the ioscan both listed the driver as btlan0 so I want on to bigger and better things (ie enlarging /var so I could load more software and patches). logical vol man scares me so I use SAM. I create a slice and copy /var ( said couldn't copy 6 "sockets" but since this was temp sol I continued. I edited the fstab and the mntab and rebooted. SAM enlarged the real /var then I removed the changes to fstab and mntab and rebooted again.

ioscan and lanscan now report the card is using lan instead of btlan0. (it was pinging the 2 routers but nothing else).

reloaded the J2780BA and today the card is "using" SNAP1 and cant ping anything.

Sorry sooooooo wordy. I REALLY hope this clarification will help somebody on a white horse. Boss wants this operational tues may have to ignite and start from scratch.

thanks in advance

[rick jones · Accepted solution]

Given that you have a system with EISA, that implies that the built-in Ethernet interface is a 10 Mbit/s interface that would be driven by the "lan2" driver.

(I'm guessing this is either a D or an R Class system :)

A word about 11.X and EISA - 63-bit HP-UX kernels contain no support for EISA peripherals. Only 32-bit kernels contain support for EISA peripherals. It doesn't sound quite like this is at issue, but it is worth mentioning.

It would be good if you could provide the output of ioscan -fk on the system. It should show both the core and the EISA interface.

As others have alluded, "J2780BA" does not describe a patch, but a product. Patches have names like PHNE_NNNNN.

There is no way that the driver for a NIC would/should switch from one name to another in a given release. It might change from one release to another - for example, the HSC/PCI/Core 10/100BT drivers btlan[3456] get merged in 11i and are just driven by a driver called "btlan"

SNAP is an encapsulation method that is different from regular Ethernet. If someone has ifconfig'd snap1 there is no way that that interface will talk directly with other systems using basic Ethernet encapsulation. Undo whatever was done to have SNAP1 used as an interface name in ifconfig and the /etc/rc.config.d/netconf file and try a manual ifconfig of (probably) lan1 instead.

Also, don't forget that any resemblance between driver names and interface names (lan0 interface, lan2 driver) is purely coincidence. An interface name does not imply the driver - the driver is (as you probalby already know) shown in the ioscan output.

[Ron Kinner]

When you get it back to where it can ping the routers but nothing else do:

netstat -r

and look for the default route. It probably got lost. You can add it temporarily with route add but you really need to add it to /etc/rc.config.d/netconf or it will go away at the next boot. Also check that
nslookup
is able to talk to the DNS server (assuming you have one).

Since you say you can ping the routers I guess you won't have to turn off dead gateway detection but be aware that it is on automatically in 11.0 and will remove any gateway from the routing table which does not respond to pings after about 3 minutes.

Another interesting gotcha on 11.0 is that the default TTL on a UDP broadcast drops to 1 so that it can't leave the local LAN. You can change that in NDD too.

Ron

[Ajit Natarajan]

It is my opinion that you've run into problems because the EISA 100BT product changed interface naming conventions.

Based on a little bit of digging, here's what I found:

1. Beginning with the 10.20.03 release of EISA 100BT, the interface naming conventions were changed from btlan0x to lanx (where x is the NMID for 10.20 and the PPA for 11.0 and beyond).

2. If a release prior to 10.20.03 is installed and patch PHNE_19199 is installed, the patch changes the naming convention and alters /etc/rc.config.d/netconf.

3. Patch PHNE_21373 and later patches will use the convention currently in use by the product (btlan0x for 10.20.02 and earlier, lanx for 10.20.03 and later). In other words, the patch will not cause a change in naming convention.

My guess is that an upgrade to 11.0 caused a naming convention change.

I find it unlikely that increasing /var causes a problem.

My recommendation is:

1. Determine the version of EISA 100BT you had when you were using 10.20. You will need to consult any offline notes you maintained. You may not be able to determine this easily from the system itself.

2. Check the lanscan output on your 11.0 system to see if the interface is being reported as lanx.

3. Check netconf to see if the entry for this interface shows the interface name as lanx (where x is the instance number displayed by lanscan). If not, adjust it and then either reboot or run /sbin/rc2.d/S340net stop followed by /sbin/rc2.d/S340net start. You will need to all of this as root and you should expect a glitch in network traffic from/to your system.

If none of this helps, you may need to log a call with your HP support representative to examine this further.

Thanks.

Ajit
HP Gigabit Ethernet

[Beth Weller]

PROBLEM SOLVED!

I would like to thank everybody for all the time and effort they put into resolving my problem!!!

Yes I have an HP9000 D class.

Rick Jones advised an ioscan -fk. Those are great options!
lan 0 8/16/6 lan2 CLAIMED interface built-in lan
lan 1 8/20/5/8 btlan0 CLAIMED interface EISA Card INP0500

So the card was using the correct driver.

The lanscan showed both cards up.

I decided to check the built-in card so I plugged the lan cable into the internal card and noticed a TINY white pin switch that said transfer. So I put the lan back into the EISA card and pushed the button and the card could ping itself. The next morning I am working and can telnet everywhere! Patience is a virtue and you have to give the routers time to do there majic.

The ioscan -fk showed me a video card I thought wasn't working so that is a huge step toward one of my next mission.

Ajit thanks for the info, now I am going to start my patches with my enlarged /var.

Again thanks SOOOOOOOO very much!!!!!!!