Network information

[iman_1]

when I enter netstat -in command, I get below

lan100:1 1500 none none
lan18 1500 192.XXX.Z.0 192.YYY.Z.XXX
lan100:3 1500 10.YY.XXX.0 10.YY.XXX.ZZ
lan100:2 1500 none none
lo0 4136 127.0.0.0 127.0.0.1
lan100:4 1500 10.YY.XXX.0 10.YY.XXX.ZZ
lan100 1500 10.YY.XXX.0 10.YY.XXX.ZZ

some information based on this...

1) How can I find network speed of lan100:2 ?
Tried using lanadmin -x 100:2 or 012 but doesn't work.

2) what is this lan100:4 ? does it mean there is some etherchanneling done ont he network card ?

3) Last part of lanscan shows below

LinkAgg0 0x00306E04DF83 100 UP lan100 snap100 16 ETHER
LinkAgg1 0x000000000000 101 DOWN lan101 snap101 17 ETHER
LinkAgg2 0x000000000000 102 DOWN lan102 snap102 18 ETHER
LinkAgg3 0x000000000000 103 DOWN lan103 snap103 19 ETHER
LinkAgg4 0x000000000000 104 DOWN lan104 snap104 20 ETHER

4) I also want to tell the hardware guy the port at the back of physical server where to remove the network cable from. How can I relate the software information to the hardware on the physical box.

I mean If tell the hardware path of the card is 1/0/10/0/0/5/0 it wouldn't make any sense to him.

I have a guess that Crd In in lanscan could be of use.

I think he requires port location.Is there somethng at the back of Server written which I/he could correlate ?

5) How does the lanscan output compare with netstat -in as there are many ports not assigned any ip address . Assume they are empty.
Help me please

Ciao

[iman_1]

Another One,

Is lan103 same as lan100:3 ?

Still a bit confused in numbering

[Court Campbell]

a lan interface with a ":number" after it is a vlan (according to hpux dics I have read). I usually call them sub-interfaces. It's when you assign multiple ip's to the same interface. lan100 is a port aggregate and you will not be able to get speed info fir it. You will need to run:

lanscan -q

This will show you which lan devices are a aprt of that aggregate. Then you can use lanadmin -x on those interfaces.

Ex.

$lanscan -q
5
901 1 900(0 4)
902
903
904

lan901 is made of lan1 and lan900. and lan900 is made up of lan0 and lan4. So ican look at 1, 0, and 4.

$lanadmin -x 1
Speed = 1000 Full-Duplex.
Autonegotiation = On.

[sujit kumar singh]

Hi


this seems that your system is having the APA that is AUto Port Aggregation ans also that The APA is having some IP multiplexing.

To add clarity,

lan099:1 --- means that an additional IP Address is assigned to the LAN I/F lan 900 and so on.

You can see this happening in the case of a cluster scenario where SG chooses according the LAN Configs in the Cluster and in the packages to assign the Relocatable package IP address to one of the Interfaces.

Say that lan0 you have given an IP address of 192.168.10.1/255.255.255.0 as a Fixed IP.

When the Package starts if this fonds this LAN card as suitable as per config that this only shall host the Rlocatable PAckage IP , then the Packake IP is assigned to this I/F like lan0:1 -- IP address


Regards
Sujit

[iman_1]

All,

Some more questions regaridng the same.

When I do lanscan -q it gives me below

Milano:/ # lanscan -q
9
10
11
12
14
15
16
1
2
3
4
0
900 13 17
901
902
903
904

I suppose this means lan900 is the port aggregation of lan13 and lan17. Where can I get more information about lan13 and lan17 ? They do not seem to be the part of lanscan nor netstat -in.

Help appreciated.

[Heironimus]

Minor correction: the "lan#:#" naming is not a vlan, it is an alias. One important difference between HP-UX and most other UNIX systems is that lan0:0 is actually the same as lan0.