Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
General
cancel
Showing results for 
Search instead for 
Did you mean: 

Auto-Port Aggragation and netstat -in

SOLVED
Go to solution
MTSU_SAN
Regular Advisor

Auto-Port Aggragation and netstat -in

When I first installed APA software, and configured my lan100 and lan101, the netstat -in command showed the standby, but with an asterisk next to it. Now, netstat -in does NOT show the standby, even though sam shows it. Also, I cannot reset the card with lanadmin. I did get some lan card failure messages, but I've always assumed they were because I have four ports not connected to anything. Any ideas?
13 REPLIES
David Bell_1
Honored Contributor

Re: Auto-Port Aggragation and netstat -in

Jerry,

Please see the following document:

http://support2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000060579504

This document describes the problem you are seeing. It also recommends patches, checnges to configuration, etc.

HTH,

Dave
David Bell_1
Honored Contributor

Re: Auto-Port Aggragation and netstat -in

Jerry,

You may also want to look at this configuration and test document:

http://support2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062139536

You should also verify that you have the latest cumulative APA patch PHNE_26773.

HTH,

Dave
MTSU_SAN
Regular Advisor

Re: Auto-Port Aggragation and netstat -in

I don't think those documents apply, because I've got all of the configuration done, and it worked correctly for a while. I'm trying to figure out why it changed! These are my lanscans:
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
5/1/0 0x001083F7260E 4 UP lan4 snap4 4 ETHER Yes 119
LinkAgg0 0x0060B0B222B5 100 UP lan100 snap100 7 ETHER Yes 119
LinkAgg1 0x001083F706B0 101 UP lan101 snap101 8 ETHER Yes 119

lanscan -q
4
100 0 3
101 1 2

So everything shows up fine, just lan101 no longer appears in netstat -in:
Name Mtu Network Address Ipkts Opkts
lo0 4136 127.0.0.0 127.0.0.1 13261727 13261774
lan4 1500 192.1.1.0 192.1.1.2 8 10
lan100 1500 161.45.193.0 161.45.193.16 55020305 58042231
frank
David Bell_1
Honored Contributor

Re: Auto-Port Aggragation and netstat -in

Jerry,

It appears that the -i and -r options of netstat have changed. Here's the document:

http://devresource.hp.com/STK/impacts/i211.html

HTH,

Dave
MTSU_SAN
Regular Advisor

Re: Auto-Port Aggragation and netstat -in

Thanks for the info, but this has only changed within the past couple of weeks, with no patching in between, so I don't think it is that, either.
David Bell_1
Honored Contributor

Re: Auto-Port Aggragation and netstat -in

Jerry,

Can you give me some information on your system and lan cards. Also I'm assuming you're running HP-UX 11.00, is this accurate? Lastly, what do you get if you do an ?

Dave
MTSU_SAN
Regular Advisor

Re: Auto-Port Aggragation and netstat -in

I have two boxes--same symptoms (they will be nodes in SG cluster someday).
V-2500 has four HP A3738A PCI 10/100Base-TX Ultimate Combo
cards, two each on lan100 and lan101 as lanscan -q shows.
rp7400 has two HP A5506B PCI 10/100Base-TX 4 port cards with similar set up as V. ifconfig lan101 shows "no such interface" on both boxes. But, lanscan and Sam show they are up. This started just recently, and correct (I think) behavior lasted through several reboots on Nbox.
MTSU_SAN
Regular Advisor

Re: Auto-Port Aggragation and netstat -in

Sorry, yes, 11.0. APA B.11.00.16
David Bell_1
Honored Contributor

Re: Auto-Port Aggragation and netstat -in

Jerry,

Okay, the obvious questions:

1. Do you have a link light on all interfaces?
2. Do you have an occasional activity light on all connected interfaces?
3. Have you performed a linkloop from lan100 to lan100 of the second node (or lan101)?
4. What does the output of dmesg show?
5. Have ANY configuration changes been made to the network (host or switches)?

Dave
MTSU_SAN
Regular Advisor

Re: Auto-Port Aggragation and netstat -in

i have to go take the side of the V box off to check there, but last time I checked N, yes link lights and activity lights on lan100.
I don't know what a linkloop is.
dmesg shows nothing about the lan cards, except for the four ports on the Nclass that are not hooked to anything, and the normal initiation of all of the ports. Here are some messages from OLDsyslog for lan4, which doesn't seem to have any problems (will be SG Heartbeat, one day)
Aug 9 13:04:53 frank vmunix: btlan6: NOTE: MII Link Status Not OK - Switch Conn
ection to AUI at 5/1/0....
Aug 9 13:04:53 frank vmunix: btlan6: Reset looper timeout: DMA timeout occurred
at 5/1/0
Aug 9 13:04:53 frank vmunix: btlan6: reset state is 550 at 5/1/0....
Aug 9 13:04:53 frank vmunix: btlan6: WARNING: AUI Loopback Failed at 5/1/0....
Aug 9 13:04:53 frank vmunix: btlan6: Reset looper timeout: DMA timeout occurred
at 5/1/0
Aug 9 13:04:53 frank vmunix: btlan6: reset state is 575 at 5/1/0....
Aug 9 13:04:53 frank vmunix: btlan6: WARNING: BNC Loopback Failed at 5/1/0....


David Bell_1
Honored Contributor

Re: Auto-Port Aggragation and netstat -in

Jerry,

Make sure you have link and activity on lan100 as well as lan101. Check the "known good" lan (either lan4 or lan100) with the and see if it returns ip information. I would agree that the dmesg and syslog appear normal. The syslog appears to show loopback failure on the AUI and BNC ports so I'll assume you're using the RJ45 port of that interface.

Linkloop does a hardware level check of the interface using the link or MAC address. The syntax is something like:

linkloop [-i PPA] [-n count] [-r rif] [-s size] [-t timeout] [-v] linkaddr ...

see - man 1m linkloop

Dave
David Bell_1
Honored Contributor
Solution

Re: Auto-Port Aggragation and netstat -in

Jerry,

One other thing to look at since this involved reboots. On the V2500, I believe the correct file is /etc/rc.config.d/hpsppci100conf. On the rp7400, it will either be hpbtlanconf or hppci100conf depending on what driver you're using where hpbtlanconf is for the btlan driver and the hppci100conf is for the btlan5 driver. At any rate, look at the file and note the "speed" stateman for the lans. Obviously it depends on what kind of switch, etc. However, make sure they are set for 100FD if supported by your switch. Do not set them to AUTO as this can cause failures.

It should look something like this:

XXX_INTERFACE_NAME[0]: Name of interface (lan0, lan1...)
XXX_STATION_ADDRESS[0]: Station address / MAC address of interface.
XXX_SPEED[0]: Values are : 10HD, 10FD, 100HD, 100FD, 1000FD, auto_on

If you are having a speed mismatch, the aggregate interface cannot be formed properly.

HTH,

Dave
David Bell_1
Honored Contributor

Re: Auto-Port Aggragation and netstat -in

Jerry,

Did the "Speed" fix your problem?

Assign as 0 please...

Dave