topic Re: APA Configuration Question in Operating System - HP-UX

APA Configuration Question

cam9269 — Thu, 06 Aug 2009 05:55:12 GMT

Hi Guys,

Can you shed light on how this APA setup has been done, I'm a bit confused:

/etc/rc.config.d/hp_apaportconf contains:
HP_APAPORT_INTERFACE_NAME[0]=lan7
HP_APAPORT_CONFIG_MODE[0]=LAN_MONITOR

HP_APAPORT_INTERFACE_NAME[1]=lan8
HP_APAPORT_CONFIG_MODE[1]=LAN_MONITOR

When I do:
# lanadmin -x -v 900
Link Aggregate PPA # : 900
Number of Ports : 1
Ports PPA : 8
Link Aggregation State : LINKAGG MANUAL
Group Capability : 5
Load Balance Mode : Hot Standby (LB_HOT_STANDBY)

-- Does this mean LAN8 is the only member for LAN900?

Also # lanscan -q has the ff. outputs:
0
2
1
7
900 8
901
902
903
904

Saying to me that LAN8 is the only member of LAN900 - correct?

And I have this error during bootup:
Auto-Port Aggregation/9000 Networking*****************@#%
Tue Aug 04 EST 2009 16:41:06.958424 DISASTER Subsys:HP_APA Loc:00000
<1006> HP Auto-Port Aggregation product found that ports in failover
group lan900 are no longer connected to each other. Port 8 did
not receive any poll packets.

Please help. TIA!

Re: APA Configuration Question

Michal Kapalka (mikap) — Thu, 06 Aug 2009 06:03:37 GMT

hi,

check with linkloop and lanadmin if if your lan7/8 are connected to the switch.

in lanadmin the PPA number of lan should be UP - operational status.

mikap

Re: APA Configuration Question

Ganesan R — Thu, 06 Aug 2009 06:05:13 GMT

Hi,

You have configured APA in "LAN MONITOR" mode with lan7 and lan8. But it looks there is no cable connectivity from lan 7. That's why it says "Port 8 did
not receive any poll packets" during startup.

For LAN MONITOR to work, all the ports to be connected to same subnet. You can check the connectivity using linkloop command.

Re: APA Configuration Question

cam9269 — Thu, 06 Aug 2009 22:29:44 GMT

Hi Guys,

Here are lanscan outputs:

-------------------------------------------------------------------------------
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/0/0 0x0010837CC215 0 UP lan0 snap0 1 ETHER Yes 119

Extended Station LLC Encapsulation
Address Methods
0x0010837CC215 IEEE HPEXTIEEE SNAP ETHER NOVELL

Driver Specific Information
btlan
-------------------------------------------------------------------------------
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/10/0/0 0x001083FC93A4 7 UP lan7 snap7 5 ETHER Yes 119

Extended Station LLC Encapsulation
Address Methods
0x001083FC93A4 IEEE HPEXTIEEE SNAP ETHER NOVELL

Driver Specific Information
gelan
-------------------------------------------------------------------------------
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
LinkAgg0 0x00306E04012B 900 UP lan900 snap900 7 ETHER Yes 119

Extended Station LLC Encapsulation
Address Methods
0x00306E04012B

Driver Specific Information
hp_apa
...............................................................................
Hardware Crd Hdw Net-Interface NM MAC HP-DLPI DLPI Driver
Path In# State NamePPA ID Type Support Mjr# Name
1/8/0/0 8 UP lan8 snap8 2 ETHER Yes 119 gelan
-------------------------------------------------------------------------------

Here are linkloop outputs:
-------------------------------------------------------------------------------
LAN900
linkloop -v 0x00306E04012B

Link connectivity to LAN station: 0x00306E04012B
error: get_msg2 getmsg failed, errno = 4
-- FAILED
frames sent : 1
frames received correctly : 0
reads that timed out : 1
-------------------------------------------------------------------------------
LAN7
linkloop -v 0x001083FC93A4

Link connectivity to LAN station: 0x001083FC93A4
error: get_msg2 getmsg failed, errno = 4
-- FAILED
frames sent : 1
frames received correctly : 0
reads that timed out : 1
-------------------------------------------------------------------------------

I can't do a linkloop on on LAN8 because it's not present in the lanscan outputs I sent earlier.

The question is, in the lanscan -v output above, under LAN900, it says LAN8 is UP. Does this mean that LAN8 is the only member of LAN900? Is there something wrong with my setup?

Regards.

Re: APA Configuration Question

cam9269 — Fri, 07 Aug 2009 03:13:31 GMT

Hello again guys,

I just got the lanadmin outputs, seems LAN7 is dead.

lanadmin -g mibstats 7

LAN INTERFACE STATUS DISPLAY
Fri, Aug 7,2009 12:34:15

PPA Number = 7
Description = lan7 HP PCI 1000Base-SX Release B.11.11.25
Type (value) = ethernet(6)
MTU Size = 1500
Speed = 1000000000
Station Address = 0x1083fc93a4
Administration Status (value) = up(1)
Operation Status (value) = down(2)
Last Change = 0
Inbound Octets = 0
Inbound Unicast Packets = 0
Inbound Non-Unicast Packets = 0
Inbound Discards = 0
Inbound Errors = 0
Inbound Unknown Protocols = 0
Outbound Octets = 0
Outbound Unicast Packets = 0
Outbound Non-Unicast Packets = 0
Outbound Discards = 237700
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367

Ethernet-like Statistics Group

Index = 5
Alignment Errors = 0
FCS Errors = 0
Single Collision Frames = 0
Multiple Collision Frames = 0
Deferred Transmissions = 0
Late Collisions = 0
Excessive Collisions = 0
Internal MAC Transmit Errors = 0
Carrier Sense Errors = 0
Frames Too Long = 0
Internal MAC Receive Errors = 0

lanadmin -g mibstats 8

LAN INTERFACE STATUS DISPLAY
Fri, Aug 7,2009 12:34:23

PPA Number = 8
Description = lan8 HP PCI 1000Base-SX Release B.11.11.25
Type (value) = ethernet(6)
MTU Size = 1500
Speed = 1000000000
Station Address = 0x306e04012b
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 22511392
Inbound Octets = 1570840395
Inbound Unicast Packets = 222105806
Inbound Non-Unicast Packets = 3803
Inbound Discards = 0
Inbound Errors = 0
Inbound Unknown Protocols = 5
Outbound Octets = 378671099
Outbound Unicast Packets = 84396828
Outbound Non-Unicast Packets = 2540
Outbound Discards = 47
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367

Ethernet-like Statistics Group

Index = 2
Alignment Errors = 0
FCS Errors = 0
Single Collision Frames = 0
Multiple Collision Frames = 0
Deferred Transmissions = 0
Late Collisions = 0
Excessive Collisions = 0
Internal MAC Transmit Errors = 0
Carrier Sense Errors = 0
Frames Too Long = 0
Internal MAC Receive Errors = 0

lanadmin -g mibstats 900

LAN INTERFACE STATUS DISPLAY
Fri, Aug 7,2009 12:34:34

PPA Number = 900
Description = lan900 Hewlett-Packard LinkAggregate Interface
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 1000000000
Station Address = 0x306e04012b
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 22511392
Inbound Octets = 1544990521
Inbound Unicast Packets = 222088551
Inbound Non-Unicast Packets = 3799
Inbound Discards = 0
Inbound Errors = 0
Inbound Unknown Protocols = 4
Outbound Octets = 378346737
Outbound Unicast Packets = 84390838
Outbound Non-Unicast Packets = 2543
Outbound Discards = 31
Outbound Errors = 0
Outbound Unknown Protocols = 0
Specific = 0

---------------------------------------

So I guess we need to replace LAN7?

Re: APA Configuration Question

Alzhy — Fri, 07 Aug 2009 13:57:05 GMT

Definitely. If your server is OLRADable -- meaning PCI/PCI-X are hot swappable -- then you need not shut down the system.

Re: APA Configuration Question

rick jones — Fri, 07 Aug 2009 15:36:25 GMT

I'm quite a bit rusty on interpreting lanadmin -g mibstats output, but if the only indication is the operational state being down, while it could be dead, it could simply be sleeping, or perhaps pining for the fjords... Checking the cable *and* the switch port to which lan7 is connected would be goodness as might running some online diagnostics against lan7.