cancel
Showing results for 
Search instead for 
Did you mean: 

rx 6600 APA problem

wayne_104
Regular Advisor

rx 6600 APA problem

Hi

I have a rx 6600 server on which installed HPUX 11.31 september 2010 base on.

It came up fine and lan0 was fine.

I then setup the apa on the system. I can ping the lan900 from the server 10.192.100.120.

however i cannot ping outside of my server at all.

here are copies of my config files what have i missed?
/etc/hosts
10.192.100.120 alsop1.ialch.co.za alsop1
127.0.0.1 localhost loopback

# more /etc/rc.config.d/netconf
# netconf: configuration values for core networking subsystems
#
# @(#) netconf $Date: 2007/10/05 20:09:28 $Revision: r11.31/1 PATCH_11.31 (PHNE_
36281)
#
# HOSTNAME: Name of your system for uname -S and hostname
#
# OPERATING_SYSTEM: Name of operating system returned by uname -s
# ---- DO NOT CHANGE THIS VALUE ----
#
# LOOPBACK_ADDRESS: Loopback address
# ---- DO NOT CHANGE THIS VALUE ----
#

HOSTNAME="alsop1"
OPERATING_SYSTEM=HP-UX
LOOPBACK_ADDRESS=127.0.0.1

# Internet configuration parameters. See ifconfig(1m), autopush(1m)
#
# INTERFACE_NAME: Network interface name (see lanscan(1m))
#
# IP_ADDRESS: IP address in decimal-dot notation (e.g., 192.1.2.3),
# or hostname (in /etc/hosts).
#
# SUBNET_MASK: Subnetwork mask in decimal-dot notation, if different
# from default
#
# BROADCAST_ADDRESS: Broadcast address in decimal-dot notation, if
# different from default
#
# INTERFACE_STATE: Desired interface state at boot time.
# either up or down, default is up.
#
# DHCP_ENABLE Determines whether or not DHCP client functionality
# will be enabled on the network interface (see
# auto_parms(1M), dhcpclient(1M)). DHCP clients get
# their IP address assignments from DHCP servers.
# 1 enables DHCP client functionality; 0 disables it.
#
# INTERFACE_MODULES: A list of modules to be pushed on a stream
# associated with an interface. For example,
# INTERFACE_MODULES[0]="mod1 mod2 ... modN-1 modN"
# pushes modN on top of modN-1.
#
# For each additional network interfaces, add a set of variable assignments
# like the ones below, changing the index to "[1]", "[2]" et cetera.
#

#INTERFACE_NAME[0]="lan0"
#IP_ADDRESS[0]="10.192.100.17"
#SUBNET_MASK[0]="255.255.255.0"
#BROADCAST_ADDRESS[0]=""
#INTERFACE_STATE[0]=""
#DHCP_ENABLE[0]="0"
#INTERFACE_MODULES[0]=""


# Internet routing configuration. See route(1m), routing(7)
#
# ROUTE_DESTINATION: Destination host or network IP address in decimal-dot
# notation, or hostname (in /etc/hosts) or network name
# (in /etc/networks), preceded by the word "host" or "net";
# or simply the word "default".
#
# ROUTE_MASK: Subnetwork mask in decimal-dot notation, or C language
# hexadecimal notation. This is an optional field.
# An IP address/subnet mask pair uniquely identifies
# a subnet to be reached. If a subnet mask is not given,
# then the system will assign the longest subnet mask
# of the configured network interfaces to this route.
# If there is no matching subnet mask, then the system
# will assign the default network mask as the route's
# subnet mask.
#
# ROUTE_GATEWAY: Gateway IP address in decimal-dot notation, or hostname
# (in /etc/hosts). If local interface, must use the
# same form as used for IP_ADDRESS above (hostname or
# decimal-dot notation). If loopback interface, i.e.,
# 127.0.0.1, the ROUTE_COUNT must be set to zero.
#
# ROUTE_COUNT: An integer that indicates whether the gateway is a
# remote interface (one) or the local interface (zero)
# or loopback interface (e.g., 127.*).
#
# ROUTE_ARGS: Route command arguments and options. This variable
# may contain a combination of the following arguments:
# "-f", "-n" and "-p pmtu".
#
# ROUTE_SOURCE: Local system IP address in decimal-dot notation, or the
# equivalent hostname or alias (in /etc/hosts).
# This field is optional. If specified, it must match
# one of the configured IP addresses or names of the
# local system.
#
# For each additional route, add a set of variable assignments like the ones
# below, changing the index to "[1]", "[2]" et cetera.
#
# IMPORTANT: If host or network names are used instead of IP addresses for
# fields that support both, make sure the system name resolution
# policy is configured so that a hang during system boot (or slow
# boot behavior) is avoided. See nsswitch.conf(4).

ROUTE_DESTINATION[0]="default"
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]="10.192.100.1"
ROUTE_COUNT[0]="1"
ROUTE_ARGS[0]=""
ROUTE_SOURCE[0]=""

# Dynamic routing daemon configuration. See gated(1m)
#
# GATED: Set to 1 to start gated daemon.
# GATED_ARGS: Arguments to the gated daemon.

GATED=0
GATED_ARGS=""

#
# Router Discover Protocol daemon configuration. See rdpd(1m)
#
# RDPD: Set to 1 to start rdpd daemon
#

RDPD=0

#
# Reverse ARP daemon configuration. See rarpd(1m)
#
# RARP: Set to 1 to start rarpd daemon
#

RARPD=0

#
# Network interface configuration. See ifconfig(1m)
#
# DEFAULT_INTERFACE_MODULES contains a default list of modules to be
# pushed on a stream associated with an interface. For example,
# INTERFACE_MODULES[0]="mod1 mod2 ... modN-1 modN" pushes modN on top
# of modN-1.
#
# Precedence rules:
# 1) The module names specified in INTERFACE_MODULES[] for the specified
# interface overrides the modules in DEFAULT_INTERFACE_MODULES. For
# example, INTERFACE_MODULES[0]="foo" and
# DEFAULT_INTERFACE_MODULES="m1 m2", then the module list applied
# will be "foo".
#
# 2) If INTERFACE_MODULES[] is set to null string, then the module
# names specified in DEFAULT_INTERFACE_MODULES will be used for the
# specified interface. For example, INTERFACE_MODULES[0]="" ( or
# INTERFACE_MODULES[0]= ) and DEFAULT_INTERFACE_MODULES="m1 m2",
# then the applied module list will be "m1,m2".
#
# 3) If INTERFACE_MODULES[] is explicitly set to "NONE", then no module
# list will be applied for the specified interface. For example, if
# INTERFACE_MODULES[0]="NONE" and DEFAULT_INTERFACE_MODULES="m1 m2",
# then there will be no -m option applied to the interface.
# Restriction: The module name can't be "NONE", and "NONE" is not
# case sensitive.




more /etc/rc.config.d/hp_apaportconf




INTERFACE_NAME[1]="lan900"
IP_ADDRESS[1]="10.192.100.120"
SUBNET_MASK[1]="255.255.255.0"
BROADCAST_ADDRESS[1]="10.192.100.255"
INTERFACE_STATE[1]="up"
DHCP_ENABLE[1]="0"
INTERFACE_MODULES[1]=""
DEFAULT_INTERFACE_MODULES=""
INTERFACE_NAME[2]="lan1"
IP_ADDRESS[2]="10.0.0.120"
SUBNET_MASK[2]="255.255.255.0"
BROADCAST_ADDRESS[2]="10.0.0.255"
INTERFACE_STATE[2]="up"
DHCP_ENABLE[2]="0"
INTERFACE_MODULES[2]=""


# The HP_APAPORT_INIT_ARGS are reserved by HP. They are NOT user changable.

HP_APAPORT_INIT_ARGS="HP_APAPORT_GROUP_CAPABILITY HP_APAPORT_PRIORITY HP_APAPORT
_CONFIG_MODE HP_APAPORT_KEY HP_APAPORT_SYSTEM_PRIORITY"


HP_APAPORT_INTERFACE_NAME[0]=lan2
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]=lan0
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

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

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

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

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



more /etc/rc.config.d/hp_apaconf

HP_APA_DEFAULT_PORT_MODE=LACP_AUTO
HP_APA_MAX_LINKAGGS=50
HP_APA_LACP_SYSTEM_ID_MODE=FIRST_APA_PORT
HP_APA_LACP_TIMEOUT=0
HP_APA_USE_SYSLOG=1

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

7 REPLIES
Michael Leu
Honored Contributor

Re: rx 6600 APA problem

Seems like the gateway did not get configured.

Put this part:

INTERFACE_NAME[1]="lan900"
IP_ADDRESS[1]="10.192.100.120"
SUBNET_MASK[1]="255.255.255.0"
BROADCAST_ADDRESS[1]="10.192.100.255"
INTERFACE_STATE[1]="up"
DHCP_ENABLE[1]="0"
INTERFACE_MODULES[1]=""
DEFAULT_INTERFACE_MODULES=""
INTERFACE_NAME[2]="lan1"
IP_ADDRESS[2]="10.0.0.120"
SUBNET_MASK[2]="255.255.255.0"
BROADCAST_ADDRESS[2]="10.0.0.255"
INTERFACE_STATE[2]="up"
DHCP_ENABLE[2]="0"
INTERFACE_MODULES[2]=""

back into /etc/rc.config.d/netconf and do a '/sbin/init.d/net start'.
Steven E. Protter
Exalted Contributor

Re: rx 6600 APA problem

Shalom,

Did you have your Cisco switch port configuration changed to support your configuration?

To get benefits from APA, you need to reach out to the Cisco/Networking people.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
wayne_104
Regular Advisor

Re: rx 6600 APA problem

Yea cisco side is all fine. we got two other systems here running fine. just seems to be this one.
wayne_104
Regular Advisor

Re: rx 6600 APA problem

netconf did not work
wayne_104
Regular Advisor

Re: rx 6600 APA problem

These are my nics. How do i get the latest firmware for them?

iether2: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hard
ware path 0/4/2/0
iether0: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at h
ardware path 0/2/1/0
iether1: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at h
ardware path 0/2/1/1
iether3: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hard
ware path 0/4/2/1
iether4: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at h
ardware path 0/6/1/0
iether5: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at h
Kenan Erdey
Honored Contributor

Re: rx 6600 APA problem

Hi,

before forming a link aggregate check out if four lans are in the same vlan.

linkloop -i 0 lan2_mac_adress

then make sure you gave lan names in HP_APA_MANUAL_LA[0] line.

if on the cisco side, ports are configured to etherchannel, try manuel mode.

form the link aggregate. and check it's ok

lanscan -q

assing ip and check. i met sometimes which i can't ping without reboot.
Computers have lots of memory but no imagination
wayne_104
Regular Advisor

Re: rx 6600 APA problem

I have solved the problem i did a firware update of the base system. problem solved.