Request Time Out after configuring APA

[Aji Thomas]

Hi,

We have configured APA for LAN0 and LAN1 by manually editing files:
* hp_apaconf
* hp_apaportconf

Added within hp_apaconf:
HP_APA_START_LA_PPA=900
HP_APA_DEFAULT_PORT_MODE=MANUAL
HP_APA_USE_SYSLOG=1
HP_APA_MAX_LINKAGGS=50
HP_APA_LACP_SYSTEM_ID_MODE=FIRST_APA_PORT
HP_APA_LACP_TIMEOUT=0

HP_APA_INTERFACE_NAME[0]=lan900
HP_APA_LOAD_BALANCE_MODE[0]=LB_MAC
HP_APA_GROUP_CAPABILITY[0]=5
HP_APA_KEY[0]=0
HP_APA_HOT_STANDBY[0]=off
HP_APA_MANUAL_LA[0]=0,1

And added within hp_apaportconf:
HP_APAPORT_INTERFACE_NAME[0]=lan0
HP_APAPORT_GROUP_CAPABILITY[0]=5
HP_APAPORT_KEY[0]=0
HP_APAPORT_PRIORITY[0]=0
HP_APAPORT_CONFIG_MODE[0]=MANUAL
HP_APAPORT_SYSTEM_PRIORITY[0]=0

HP_APAPORT_INTERFACE_NAME[1]=lan1
HP_APAPORT_GROUP_CAPABILITY[1]=5
HP_APAPORT_KEY[1]=0
HP_APAPORT_PRIORITY[1]=0
HP_APAPORT_CONFIG_MODE[1]=MANUAL
HP_APAPORT_SYSTEM_PRIORITY[1]=0

After this we restarted service and assinged IP for this APA.

But now we notice that request timeout happens when we do a continous ping to this IP.

Please advice if we have missed out something, or some additional configuration needs to be done.

Thanks,
Aji

[Richard Hepworth]

Hi,

It will help to know the output of:

lanadmin -x 0
lanadmin -x 1
lanadmin -x -i 900
netstat -ni

regards,

Richard

[Aji Thomas]

Hi,

Thanks for the update,

root@kddrac3-ia64/$>lanadmin -x 0
Speed = 1000 Full-Duplex.
Autonegotiation = On.

root@kddrac3-ia64/$>lanadmin -x 1
Speed = 1000 Full-Duplex.
Autonegotiation = On.

root@kddrac3-ia64/$>lanadmin -x -i 900
Link Aggregate PPA # : 900
Link Aggregation Mode : MANUAL
Load Balance Mode : MAC Address based (LB_MAC)
Active Ports PPA # : 0 1
Port(s) not ready : NONE

root@kddrac3-ia64/$>netstat -ni
Name Mtu Network Address Ipkts Ierrs Opkts
Oerrs Coll
lo0 32808 127.0.0.0 127.0.0.1 300389 0 300389
0 0
lan900 1500 1.11.0.0 1.11.100.133 44502106 0 50109920
0 0
root@kddrac3-ia64/$>

Thanks,
Aji

[Aji Thomas]

HI,

Can anyone advice is there is any configuration on switch side and is it has to be connected on same switch?

Please advice,
Aji

[Sharma Sanjeev]

Hi

Please check if your swith supports 1000 Ful duplex and is enabled, othewise do it auto

Regards
Sanjeev

[Aji Thomas]

yes, its set AUTO

[Sharma Sanjeev]

Hi

Please try to set lan card speed to Auto also

Rehards
Sanjeev

[Aji Thomas]

Please find my previous update:
root@kddrac3-ia64/$>lanadmin -x 0
Speed = 1000 Full-Duplex.
Autonegotiation = On.

root@kddrac3-ia64/$>lanadmin -x 1
Speed = 1000 Full-Duplex.
Autonegotiation = On.

[Richard Hepworth]

Aji,

Can you confirm that both lan0 and lan1 are connected to same subnet?

If you stop apa and configure the address onto both lan0 and then lan1 seperately do both of them respond ok on the network?

[Aji Thomas]

Yes, Before APA, IP was configured on LAN0. It was working fine.

Now also after configuration of APA, if we remove one connection, it goes well without any network request timeout.

Please advice,
Aji

[Richard Hepworth]

what about lan1? does this work ok on the network with that address?

[Aji Thomas]

Yes,

We can find following within syslog as well.
Is there anything to be enabled by using ndd commands

Mar 10 22:08:24 kddrac3 vmunix: Dead gateway detection can't ping the last remaining default gateway at 0x10b64fa .See ndd -h ip_ire_gw_probe for more info

Please advice,
Aji

[rick jones]

What did ndd -h ip_ire_gw_probe tell you?

Also, I think there is an outstanding question about the connectivity of lan1 vs lan0 - in other words is the lan1 interface connected to the same switch as lan0?

[Aji Thomas]

I have set using
ndd -set ip_ire_gw_probe 0

LAN0 and LAN1 are not connected to same switch. They are on two different switches

Please advice,
Aji

[rick jones]

If lan0 and lan1 are on two different switches, I believe you cannot have an "active-active" configuration. You should peruse the APA manuals on docs.hp.com and go with (iirc) LAN Monitor mode.

[Aji Thomas]

HI Rick,

Thanks for the update. We will connect both lan0 and lan1 to same switch.

Please advice if there is any further configurations to be made within the config files.

Thanks,
Aji

[rick jones]

I don't use APA all that much. You really need to read the APA manuals in their entirety.

[HP-UX User_1]

The whole idea of APA is to provide redundancy; if you place both NICs on same switch and that switch fails then connection to the system is lost. When using 2 switches for redundancy the switches must be able to linkloop to each other.

if the switches support LACP then the apa_portconf file can look like this:

HP_APAPORT_INTERFACE_NAME[0]=lan0
HP_APAPORT_GROUP_CAPABILITY[0]=5
HP_APAPORT_KEY[0]=900
HP_APAPORT_PRIORITY[0]=0
HP_APAPORT_CONFIG_MODE[0]=LACP_AUTO
HP_APAPORT_SYSTEM_PRIORITY[0]=0

HP_APAPORT_INTERFACE_NAME[1]=lan1
HP_APAPORT_GROUP_CAPABILITY[1]=5
HP_APAPORT_KEY[1]=900
HP_APAPORT_PRIORITY[1]=0
HP_APAPORT_CONFIG_MODE[1]=LACP_AUTO
HP_APAPORT_SYSTEM_PRIORITY[1]=0

[Bill Hassell]

As mentioned, you split the APA connection between switches for reliability, or place both links on the same switch for enhanced throughput. But in both cases, the switches must be configured for APA -- that is, two links with the same IP address. When the links are split over two switches, the two switches must be interconnected and configured for redundancy. For a single switch, the switch then load balances the same IPaddress traffic between the ports. If the switch cannot be configured for APA, then many switches detect the duplicate IP address and shutdown one or both ports.