Physically slot place of NIC and FC

[Torsten.]

Example:

http://h20000.www2.hp.com/bc/docs/support/SupportDocument/c01170674/c01170683.jpg

[itrc55]

Hi,

i follow the instructions on this topic and i successfully disable the two port of lan2 on procurve switch 1
Note: (I have 2 procurve switch, Lan2 on bay4 port4 and port12)
and when i check the lan card status i found it's still alive

#lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
3/0/0/2/0/0/0 0x3C4A923C4326 2 UP lan2 snap2 3 ETHER Yes 119
5/0/0/2/0/0/1 0x3C4A923C48B6 5 UP lan5 snap5 6 ETHER Yes 119
40/0/2/0/0/0/0/2/0/0/0 0xF4CE46F4782A 6 UP lan6 snap6 7 ETHER Yes 119
41/0/2/0/0/0/0/2/0/0/0 0xF4CE46F468F2 7 UP lan7 snap7 8 ETHER Yes 119
LinkAgg0 0x3C4A923C4CD6 900 UP lan900 snap900 10 ETHER Yes 119
LinkAgg1 0x3C4A923C4CDA 901 UP lan901 snap901 11 ETHER Yes 119
LinkAgg2 0x000000000000 902 DOWN lan902 snap902 12 ETHER Yes 119
LinkAgg3 0x000000000000 903 DOWN lan903 snap903 13 ETHER Yes 119
LinkAgg4 0x000000000000 904 DOWN lan904 snap904 14 ETHER Yes 119

#netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lo0 32808 127.0.0.0 127.0.0.1 4788910 0 4788910 0 0
lan2* 1500 172.168.10.0 172.168.10.16 348909 0 346695 0 0
lan901 1500 10.64.238.0 10.64.239.7 203690 0 94723 0 0
lan5 1500 172.168.20.0 172.168.20.16 335367 0 332226 0 0
lan900 1500 10.64.48.0 10.64.49.96 4965601 0 3372915 0 0
lan5:801 1500 169.254.0.0 169.254.170.166 456 0 281 0 0
lan901:8 1500 10.64.238.0 10.64.239.8 4046 0 4036 0 0
Warning: The above name 'lan901:801' is truncated, use -w to show the output in wide format
lan901:8 1500 10.64.238.0 10.64.239.10 5409 0 4042 0 0
Warning: The above name 'lan901:802' is truncated, use -w to show the output in wide format

#ping 172.168.10.16
PING 172.168.10.16: 64 byte packets
64 bytes from 172.168.10.16: icmp_seq=0. time=0. ms
64 bytes from 172.168.10.16: icmp_seq=1. time=0. ms
64 bytes from 172.168.10.16: icmp_seq=2. time=0. ms
64 bytes from 172.168.10.16: icmp_seq=3. time=0. ms

What i can doing now

Thanks

[Duncan Edmonstone]

Some points:

1. You shouldn't be using "lanscan" on 11.31 - it is deprecated - you should be using nwmgr.

2. lanscan reports the "administration status" (i.e. can it be configured) of a NIC, rather than the "operational status" (i.e. does it have link-beat from a cable connection)... here's some examples:

On my SD2, I have a LAN port - lan4 that I know is not cabled up (this isn't a LOM NIC, but the argument is the same), and another LAN port - lan8, that I know is live and in use. Look at the output of the following commands

#netstat -in | grep lan[48]
lan8 1500 16.26.112.0 16.26.112.162 565680 0 84206 0 0
#nwmgr | grep lan[48]
lan4 DOWN 0x1CC1DE4D2000 iether 1000Base-T
lan8 UP 0x1CC1DE4D1044 iether 1000Base-T
#lanscan | grep lan[48]
41/0/0/0/0/0/0/2/0/0/0 0x1CC1DE4D2000 4 UP lan4 snap4 5 ETHER Yes 119
41/0/2/0/0/0/0/2/0/0/0 0x1CC1DE4D1044 8 UP lan8 snap8 9 ETHER Yes 119
#lanadmin -g 4 | grep Status
Administration Status (value) = up(1)
Operation Status (value) = down(2)
#lanadmin -g 8 | grep Status
Administration Status (value) = up(1)
Operation Status (value) = up(1)

As you can see, lanscan is not telling me that the card is operational, it's telling me that it is available to be configured (a different thing entirely).

Secondly, if I bind an IP address to a NIC which is not operational, I can still ping that IP address from the host. I just won't be able to ping anything else on that network. So using my example again, where I know lan4 is not cabled:

#ifconfig lan4 10.10.10.10 up
#netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lo0 32808 127.0.0.0 127.0.0.1 76826 0 76826 0 0
lan4 1500 10.0.0.0 10.10.10.10 0 0 0 0 0
lan8 1500 16.26.112.0 16.26.112.162 562880 0 83964 0 0
#ping 10.10.10.10
PING 10.10.10.10: 64 byte packets
64 bytes from 10.10.10.10: icmp_seq=0. time=3. ms
64 bytes from 10.10.10.10: icmp_seq=1. time=0. ms
64 bytes from 10.10.10.10: icmp_seq=2. time=0. ms

----10.10.10.10 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/1/3

So the lesson is, use nwmgr, not lanscan, and when checking if a NIC is up using ping, don't use the IP address of the local interface, it will still respons even if the NIC is down.

HTH

Duncan

[itrc55]

Hi,

Thanks so much Duncan, You've given me very useful information.

but when i use all you everything you said, and the card is still alive this means i need to disable the ports in the second procurve switch. because the presence of a redundancy (auto port aggregation).

Thanks Again

[Duncan Edmonstone]

Hi,

> but when i use all you everything you
> said, and the card is still alive this
> means i need to disable the ports in the
> second procurve switch. because the
> presence of a redundancy (auto port
> aggregation).

Sorry, was that a question or a statement? I can't really help with questions on APA, it's one thing I know very little about I'm afraid...

Duncan

[Torsten.]

Try

# lanadmin -x -i 900

or "901" to get a status.
Each APA related changed should be written into syslog too.

[Torsten.]

Or even better use nwmgr:

# nwmgr -S apa -I 900 -v

or

# nwmgr -S apa -I 900 -A all


See

HP Auto Port Aggregation Administrator's
Guide
HP-UX 11i v3

HP Part Number: J4240-90049
Published: January 2010
Edition: January 2010, E1001


c02141675.pdf

for more information.

[itrc55]

Hi,

Thanks for All.