topic Re: why lano is different status between lancan and cmviewcl? in Operating System - HP-UX

why lano is different status between lancan and cmviewcl?

study unix — Tue, 20 Jul 2010 05:42:12 GMT

cmviewcl -v
CLUSTER STATUS
clsmp up
NODE STATUS STATE
msmp1 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY down 10/4/8 lan0
PRIMARY up 10/12/6 lan1
STANDBY up 10/16/8 lan2

lanscan
Hardware Station Crd Hardware Net-Interface NM MAC HP DLPI Mjr
Path Address In# State NameUnit State ID Type Support Num
10/16/8 0x0010839660C0 2 UP lan2 UP 4 ETHER Yes 173
10/4/8 0x0010839660C1 0 UP lan0 DOWN 5 ETHER Yes 173
10/12/6 0x001083B95091 1 UP lan1 UP 6 ETHER Yes 52

Re: why lano is different status between lancan and cmviewcl?

Asif Sharif — Tue, 20 Jul 2010 06:06:27 GMT

Hi,

Both are showing Down status.

PRIMARY down 10/4/8 lan0
lan0 DOWN 5 ETHER Yes 173

Regards,
Asif Sharif

Re: why lano is different status between lancan and cmviewcl?

study unix — Tue, 20 Jul 2010 06:23:07 GMT

Hi ,
the correct lan output as below,
Hardware Station Crd Hardware Net-Interface NM MAC HP DLPI Mjr
Path Address In# State State ID Type Support Num
10/16/8 0x0010839660C0 2 UP lan2 4 ETHER Yes 173
10/4/8 0x0010839660C1 0 UP lan0 5 ETHER Yes 173
10/12/6 0x001083B95091 1 UP lan1 6 ETHER Yes 52

Re: why lano is different status between lancan and cmviewcl?

S.N.S — Tue, 20 Jul 2010 06:36:47 GMT

Hi Eye,

Pls give us the cmscancl and cmviewcl outputs

SNS

Re: why lano is different status between lancan and cmviewcl?

Torsten. — Tue, 20 Jul 2010 06:38:48 GMT

Both were DOWN, now you (somehow) toggled it to be "UP" - did you check the cluster after this?

Re: why lano is different status between lancan and cmviewcl?

melvyn burnard — Tue, 20 Jul 2010 07:42:51 GMT

cmviewcl output shows the state of the link, so it is telling you there is a link issue.
lanscan shows the state of the hardaware (NIC) and then the link state, hence the card is ok, bit again th elink is DOWN.

If you are on HP-UX 11.31, use nwmgr, as this will show each NIC and whether the LINK is up or down.

Re: why lano is different status between lancan and cmviewcl?

study unix — Tue, 20 Jul 2010 07:47:22 GMT

Hi Melvyn,
If I use command linkoop the same to nwmgr ?

Re: why lano is different status between lancan and cmviewcl?

study unix — Tue, 20 Jul 2010 07:52:33 GMT

Hi Melven,
I login one server, and impletment the command " nwmgr and lanscan", as a reslut, lan1 is diffrent status, as below, thanks!
#nwmgr
Name/ Interface Station Sub- Interface Related
ClassInstance State Address system Type Interface
============== ========= ============== ======== ============== =========
lan0 UP 0x001A4B070772 iether 1000Base-T
lan1 DOWN 0x001A4B070773 iether 1000Base-T
lan900 DOWN 0x000000000000 hp_apa hp_apa
lan901 DOWN 0x000000000000 hp_apa hp_apa
lan902 DOWN 0x000000000000 hp_apa hp_apa
lan903 DOWN 0x000000000000 hp_apa hp_apa
lan904 DOWN 0x000000000000
hp_apa hp_apa

#lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/4/2/0 0x001A4B070772 0 UP lan0 snap0 1 ETHER Yes 119
0/4/2/1 0x001A4B070773 1 UP lan1 snap1 2 ETHER Yes 119
LinkAgg0 0x000000000000 900 DOWN lan900 snap900 4 ETHER Yes 119
LinkAgg1 0x000000000000 901 DOWN lan901 snap901 5 ETHER Yes 119
LinkAgg2 0x000000000000 902 DOWN lan902 snap902 6 ETHER Yes 119
LinkAgg3 0x000000000000 903 DOWN lan903 snap903 7 ETHER Yes 119
LinkAgg4 0x000000000000 904 DOWN lan904 snap904 8 ETHER Yes 119

Re: why lano is different status between lancan and cmviewcl?

melvyn burnard — Tue, 20 Jul 2010 08:08:42 GMT

Well these are different to your origional query, but here goes:
#nwmgr

lan0 UP 0x001A4B070772 iether 1000Base-T
lan1 DOWN 0x001A4B070773 iether 1000Base-T

This shows that lan1 has no working LINK

#lanscan

0/4/2/0 0x001A4B070772 0 UP lan0 snap0 1
0/4/2/1 0x001A4B070773 1 UP lan1 snap1 2
This shows that the lan1 HARDWARE appears ok.

depending upon your supposed connectivity, you could try using linkloop to test, but it looks like you have a connectivity issue on lan1

Re: why lano is different status between lancan and cmviewcl?

study unix — Tue, 20 Jul 2010 08:17:27 GMT

Hi All,
Thanks for your reply,
I found the root reason is from syslog,lan card ever happened fail so that cmviewcl output shows one lan card statsu is down, so I use command commodnet -e lancard to enable it,now it is ok, thanks!

Hi Melvyn,
I use linkloop to check the connective between lan 0 and lan1, pls kindly provide some solution how to resolve it,thanks!
linkloop -i 1 0x001A4B070772
Link connectivity to LAN station: 0x001A4B070772
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message

Re: why lano is different status between lancan and cmviewcl?

melvyn burnard — Tue, 20 Jul 2010 08:28:52 GMT

well, is there SUPPOSED to be physical connectivity between lan0 and lan1?
If so, you need to verify your cables, switch ports etc.

Re: why lano is different status between lancan and cmviewcl?

Torsten. — Tue, 20 Jul 2010 08:34:26 GMT

Try this for both - example:

# nwmgr -g -v -c lan22
lan2:
Interface State =DOWN
Probable Cause for State = Cable disconnect
MAC Address = 0x001A41234567
Subsystem = iether
Interface Type = 1000Base-T
Hardware Path = 0/3/1/0
NMID = 33
Feature Capabilities = Physical Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Tag Offload
64Bit MIB Support
IPV4 TCP Segmentation Offload
UDP Multifrag CKO
Feature Settings = Physical Interface
VLAN Tag Offload
64Bit MIB Support
MTU = 1500
Speed = Autonegotiation : On
The link is down. Speed and other link state information are undefined.
Only the configured speed is shown.

Re: why lano is different status between lancan and cmviewcl?

study unix — Tue, 20 Jul 2010 08:46:39 GMT

Hi Torsten,
# ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/4/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
lan 1 0/4/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
root@bandao:/ #
root@bandao:/ # nwmgr -g -v -c lan1
lan1:
Interface State =DOWN
Probable Cause for State = Cable disconnect
MAC Address = 0x001A4B070773
Subsystem = iether
Interface Type = 1000Base-T
Hardware Path = 0/4/2/1
NMID = 2
Feature Capabilities = Physical Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Tag Offload
64Bit MIB Support
IPV4 TCP Segmentation Offload
UDP Multifrag CKO
Feature Settings = Physical Interface
VLAN Tag Offload
64Bit MIB Support
MTU = 1500
Speed = Autonegotiation : On
The link is down. Speed and other link state information are undefined.
Only the configured speed is shown.

# ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/4/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
lan 1 0/4/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
root@bandao:/ #
root@bandao:/ # nwmgr -g -v -c lan1
lan1:
Interface State =DOWN
Probable Cause for State = Cable disconnect
MAC Address = 0x001A4B070773
Subsystem = iether
Interface Type = 1000Base-T
Hardware Path = 0/4/2/1
NMID = 2
Feature Capabilities = Physical Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Tag Offload
64Bit MIB Support
IPV4 TCP Segmentation Offload
UDP Multifrag CKO
Feature Settings = Physical Interface
VLAN Tag Offload
64Bit MIB Support
MTU = 1500
Speed = Autonegotiation : On
The link is down. Speed and other link state information are undefined.
Only the configured speed is shown.

now, if I could check port and cable ?but I only access to it via net,thanks!

Re: why lano is different status between lancan and cmviewcl?

Torsten. — Tue, 20 Jul 2010 08:50:55 GMT

Could be a bad card (port); bad cable or bad switch (port) - check them all. Of course you cannot check the cable from remote ... ;-)

Re: why lano is different status between lancan and cmviewcl?

study unix — Tue, 20 Jul 2010 08:59:12 GMT

Hi Torsten,
I think lan can should run well due to ioscan output show the status is claim,
as for switch port , how to know lan card connect to which switch port? thanks!

Re: why lano is different status between lancan and cmviewcl?

Torsten. — Tue, 20 Jul 2010 09:02:02 GMT

ioscan only says the card is alive, it says nothing about the ports of the NIC.

Consider to logon to the switch and check the ports. Normally the MAC will be shown, but without a connection you need to refer to your own documentation of cabling.

Re: why lano is different status between lancan and cmviewcl?

melvyn burnard — Tue, 20 Jul 2010 09:07:06 GMT

you will need to get your networking team to help here, as this could be a number of items. As Torsten says, the NIC card is ok, but a PORT on the card may be faulty, more likely a cable or networking device like a switch.
Get the switch checked out

Re: why lano is different status between lancan and cmviewcl?

study unix — Tue, 20 Jul 2010 09:07:23 GMT

Hi Torsten,
Thanks for you so nice support,
but I really do not know how to check the ports of NIC ?

Re: why lano is different status between lancan and cmviewcl?

Torsten. — Tue, 20 Jul 2010 09:31:17 GMT

Well, to check a port you must connect "something" there, even a cable (connect the other end "somewhere") or a loopback connector.

If you get "link up", cable and port are ok.