topic Re: APA Warning in rc.log in Operating System - HP-UX

APA Warning in rc.log

Scott Larocque_1 — Thu, 28 Jan 2010 22:20:15 GMT

I have APA configured, and apears to be running but I get the following error in the rc.log.
WARNING: IP address(es) configured on the lan interface of the primary
port 0 in the failover-group lan900, but the failover-group is
declared without the STATIONARY_IP field.

I want to resolve whatever is wrong.

Any help would appreciated.

Scottl

Re: APA Warning in rc.log

Jupinder Bedi — Fri, 29 Jan 2010 08:11:37 GMT

can you please send me the following outputs

lanscan
ioscan -fnC lan
netstat -in
/etc/rc.config.d/hp_apaconf
/etc/rc.config.d/hp_apaportconf
/etc/lanmon

Re: APA Warning in rc.log

Jupinder Bedi — Fri, 29 Jan 2010 08:13:33 GMT

sorry /etc/lanmon is a directory . The most important file I need is

/etc/lanmon/lanconfig.ascii

Re: APA Warning in rc.log

Scott Larocque_1 — Mon, 01 Feb 2010 17:57:12 GMT

Here are the outputs:

oappv1:root > lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
LinkAgg0 0x001E0B5C2520 900 UP lan900 snap900 6 ETHER Yes 119
LinkAgg1 0x000000000000 901 DOWN lan901 snap901 7 ETHER Yes 119
LinkAgg2 0x000000000000 902 DOWN lan902 snap902 8 ETHER Yes 119
LinkAgg3 0x000000000000 903 DOWN lan903 snap903 9 ETHER Yes 119
LinkAgg4 0x000000000000 904 DOWN lan904 snap904 10 ETHER Yes 119
oappv1:root >
oappv1:root > ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/1/1/0 igelan CLAIMED INTERFACE HP PCI-X 1000Mbps Dual-port Built-in
lan 1 0/1/1/1 igelan CLAIMED INTERFACE HP PCI-X 1000Mbps Dual-port Built-in
lan 2 0/2/2/0 igelan CLAIMED INTERFACE HP PCI-X 1000Mbps Dual-port Built-in
lan 3 0/2/2/1 igelan CLAIMED INTERFACE HP PCI-X 1000Mbps Dual-port Built-in
oappv1:root >
oappv1:root > netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lo0 32808 127.0.0.0 127.0.0.1 709288 0 709291 0 0
lan900 1500 10.96.102.0 10.96.102.182 23828735 0 93970834 0 0
oappv1:root >

Re: APA Warning in rc.log

John Guster — Mon, 01 Feb 2010 20:57:49 GMT

can you post the content of /etc/lanmon/lanconfig.ascii here? caould not open your attachement?

Re: APA Warning in rc.log

Scott Larocque_1 — Mon, 01 Feb 2010 21:04:33 GMT

#####################################################################
# (c) Copyright 1997-2006 Hewlett-Packard Development Company, L.P.
# @(#) lanconfig.ascii.sample $Revision: 1.13 $ $Date: 2006/09/25 11:21:20 $
#####################################################################
#
# ********************************************************
# *********** LAN MONITOR CONFIGURATION FILE *************
# *** For complete details about the parameters and how **
# *** to set them, consult the lanqueryconf(1m) manpage **
# *** or your manual. **
# *** All timeout are microseconds, it will be round up **
# *** or down appropriately. **
# ********************************************************

NODE_NAME oappv1

# ****************************************************************
# The valid range for POLLING_INTERVAL: 500,000-10,000,000 usec **
# Default value for POLLING_INTERVAL: 10,000,000 usec **
# Minimum value for DEAD_COUNT: 2 **
# Default value for DEAD_COUNT: 3 **
# ****************************************************************
POLLING_INTERVAL 10000000
DEAD_COUNT 3

# ****************************************************************
# By default, LM_RAPID_ARP is on. The valid ranges are: **
# LM_RAPID_ARP_INTERVAL: 1000000-4000000 (default:1000000) usec **
# LM_RAPID_ARP_COUNT: 5 - 60 (default is 10) **
# (LM_RAPID_ARP_INTERVAL * LM_RAPID_ARP_COUNT) <= 60s **
# ****************************************************************
LM_RAPID_ARP off
LM_RAPID_ARP_INTERVAL 1000000
LM_RAPID_ARP_COUNT 10

# ****************************************************************
# Note: **
# **
# In Proactive Failover, the active port of a fail-over group **
# is the port with the minimum normalized port cost. This means **
# a fail-over group will change its active port to a ready port **
# having a lower normalized port cost, even when the current **
# active port remains up. You must use cost-based fail-over **
# groups in order to get the Proactive Failover behavior. **
# **
# To define a cost-based fail-over group, all the ports in the **
# fail-over group must have a cost defined. Cost has a valid **
# range of between 1 and 100, inclusive. The value must be **
# preceded by a colon (:) character. **
# **
# If one of the ports in a fail-over group does not have a cost **
# defined, the fail-over group is invalid. **
# **
# If all ports in a fail-over group have no cost defined, the **
# default failover behavior is used. The available port with **
# the highest priority becomes the active port. **
# **
# By default, the lanqueryconf -s command creates only **
# priority-based fail-over groups. **
# **
# Example with cost defined: **
# FAILOVER_GROUP lan903 **
# STATIONARY_IP 195.55.55.55 **
# # Pri/Stdby I/f Pri Cost **
# PRIMARY lan900 7 : 1 **
# STANDBY lan901 6 : 2 **
# **
# For more information on how to use proactive fail-over, refer **
# to HP Auto Port Aggregation Support Guide at **
# http://docs.hp.com. **
# ****************************************************************

#FAILOVER_GROUP lan901
# STATIONARY_IP 193.33.33.33
# STANDBY lan9 3
# PRIMARY lan6 5

FAILOVER_GROUP lan900
STATIONARY_IP 10.96.102.182
PRIMARY lan0 5
STANDBY lan1 3
STANDBY lan2 3
STANDBY lan3 3

Re: APA Warning in rc.log

Jupinder Bedi — Tue, 02 Feb 2010 08:28:25 GMT

1) Verify that the configuration in /etc/lanmon/lanconfig.ascii is still valid by using the lancheckconf command

2) Create the failover groups specified in the configuration file by using the lanapplyconf command.

This command creates the specified failover groups.

Check the failover groups by using the nwmgr -S apa and netstat -in commands.

A reboot will restart the failover group as long as the /etc/lanmon/lanconfig.ascii file is intact.

Good Luck

Re: APA Warning in rc.log

Jupinder Bedi — Tue, 02 Feb 2010 08:33:48 GMT

if you still need any help please see the following link

http://www.docs.hp.com/en/J4240-90041/apcs01.html