Configure Lan Monitor: HP APA Provides The Following

Configure Lan Monitor
What is APA ? HP Auto Port Aggregation (APA) is a software product that creates link aggregates, often called trunks, which provide a logical grouping of two or more physical ports into a single fat pipe. HP APA provides the following Automatic link failure detection and recovery Support for load balancing of network traffic across all of the links in the aggregation. Support for the creation of failover groups, providing a failover capability for links. In the event of a link failure, LAN Monitor automatically migrates traffic to a standby link. Support for the TCP Segmentation Offload (Large Send) feature, if an aggregate is created with all Ethernet cards capable of TCP Segmentation Offload (TSO). Support for Virtual VLANs (VLANs) over APA link aggregates and failover groups. Support for 64-bit MIB (RFC 2863) statistics, if all the interfaces within a link aggregate or failover group support 64-bit statistics. Support for IPv6 addresses on a link aggregate or failover group. Verify APA is installed on your system? # nwmgr # linkloop -i 1 mac-address 1. Verify that the product was installed by issuing the following command: # swlist -l product | grep -i HP-APA Output similar to the following displays: HP-APA-FMT B.11.31.20 HP Auto-Port Aggregation APA formatter product. HP-APA-KRN B.11.31.20 HP Auto-Port Aggregation kernel products. HP-APA-LM B.11.31.20 HP Auto-Port Aggregation LM commands. HP-APA-NETMOD B.11.31.20 HP Auto-Port Aggregation nwmgr/NCweb libraries. HP-APA-RUN B.11.31.20 HP Auto-Port Aggregation APA command products.
Page 1

2. Verify that the software is configured in the kernel by issuing the following command: # what /stand/vmunix | egrep -i hp_apa Output similar to the following displays: $Revision: hp_apa: HP Auto-Port Aggregation (APA): B.11.31.20 Aug 20 2008 11:30 If nothing is displayed, rebuild the kernel. Configure APA using nwmgr : Check first if any APA is already configured # nwmgr -S apa
Suppose you want to configure a simple, two-port LAN Monitor failover group on a Kclass system. You enter the netstat and ioscan commands as follows:
# netstat in
Name Mtu Network Address Ipkts Opkts lan1 1500 192.1.1.0 192.1.1.153 9504123 12437048 lan0 1500 191.1.1.0 191.1.1.1 11202 257458 lo0 4136 127.0.0.0 127.0.0.1 417 417
# ioscan -fkC lan

Class I H/W Path Driver S/W State H/W Type Description ======================================================================== lan 1 8/8/1/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Core lan 2 8/8/2/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Core lan 3 8/12/1/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Core lan 4 8/12/2/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Core lan 0 10/12/6 lan2 CLAIMED INTERFACE Built-in LAN #
The netstat output shows that lan1 is currently configured with IP address 192.1.1.153. The ioscan output shows spare 1000Base-T devices lan2, lan3, and lan4. You decide that lan2 will be the standby link for the failover group, with lan1 as the active device. To configure the failover group, do the following:
100 Configuring HP APA by editing files
1. Connect lan1 and lan2 to the same switch or to different switches or hubs on the same subnet. NOTE: Be sure that trunking is not enabled on the switch ports and also all
Page 2

2. Obtain the station address for lan2 by issuing the nwmgr command, as follows:
# nwmgr Name/ Interface Station Sub- Interface Related ClassInstance State Address system Type Interface ============== ========= ============== ====== ============= ========= lan0 UP 0x080009D43696 iether 1000Base-SX lan1 UP 0x0060B04B7B82 iether 1000Base-SX lan2 UP 0x0060B04B7B83 iether 1000Base-SX lan3 UP 0x001083953C1C iether 1000Base-SX lan4 UP 0x001083953C1D iether 1000Base-SX 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
The station address is 0x0060B04B7B83. 3. Verify that there is link connectivity between lan1 and lan2, as follows:
# nwmgr --diag -A dest=0x0060B04B7B83 -S iether -I 1 #
If there is no link connectivity, resolve the connectivity issue between the devices. 4. Verify that an entry exists in the /etc/rc.config.d/hp_apaportconf file for the active and standby interfaces that sets the interfaces' port configuration mode to LAN_MONITOR.
HP_APAPORT_INTERFACE_NAME[0]=lan1 HP_APAPORT_CONFIG_MODE[0]=LAN_MONITOR HP_APAPORT_INTERFACE_NAME[1]=lan2 HP_APAPORT_CONFIG_MODE[1]=LAN_MONITOR
5. Activate the configuration by entering:

# # # # /sbin/init.d/hplm stop /sbin/init.d/hpapa stop /sbin/init.d/hpapa start /sbin/init.d/hplm start
6. If the device to be the active link does not have the desired IP address, enter ifconfig to assign the IP address. Also add an entry to the /etc/rc.config.d/netconf file to assign the IP address permanently (or use SAM to do it).
# ifconfig lan1 192.1.1.153
7. Enter the lanqueryconf -s command to query the system for possible failover groups.
# lanqueryconf -s
Page 3

ASCII output is in the /etc/lanmon/lanconfig.ascii file. a. Verify that the content of the ASCII file is valid. Enter lancheckconf:
# lancheckconf
b. View the contents of the /etc/lanmon/lanconfig.ascii file and verify that it contains the configuration information you want.
# cat /etc/lanmon/lanconfig.ascii
See lanconfig.ascii file (page 92) for an example of this file. c. Verify that /etc/lanmon/lanconfig.ascii has the failover group configured, as planned.
# cat /etc/lanmon/lanconfig.ascii
d. Edit the file, if needed, and enter lancheckconf again.

Editing configuration files for link aggregates 101
8. Use the lanapplyconf command to build the failover group, and check it with the nwmgr -S apa and netstat -in commands:
# lanapplyconf Reading ASCII file /etc/lanmon/lanconfig.ascii Creating Fail-Over Group lan900 # nwmgr -S apa Class Mode Load Speed- Members Instance Balancing Duplex ======== =========== ========= ==================== ======= lan900 LAN_MONITOR LB_HS 100 Mbps Full Duplex 1,2 lan901 Not_Enabled LB_MAC 0 Mbps lan902 Not_Enabled LB_MAC 0 Mbps lan903 Not_Enabled LB_MAC 0 Mbps lan904 Not_Enabled LB_MAC 0 Mbps # netstat -in Name Mtu Network Address Ipkts Opkts lan0 1500 191.1.1.0 191.1.1.1 1794 1173 lo0 4136 127.0.0.0 127.0.0.1 390 390 lan900 1500 192.1.1.0 192.1.1.153 0 0
NOTE: If lanapplyconf encounters an invalid failover group, it stops reading the /etc/ lanmon/lanconfig.ascii file. Any failover groups created prior to this error are unaffected. 9. The failover group is now operational. A reboot will restart the failover group as long as the /etc/lanmon/lanconfig.ascii file is intact and the port or link aggregation has an IP address in /etc/rc.config.d/netconf that matches the failover group's Stationary IP entry in /etc/lanmon/lanconfig.ascii. If lan1 fails, lan2 becomes the active port. Similarly, if the failover group consists of two link aggregates, failover from the active link aggregate to the standby link aggregate occurs only
Page 4

when all ports in the link aggregate failed. However, the examples in the next section show how proactive failover gives you greater control of the failover.
Example :#-> nwmgr
Name/
Interface Station Address
Sub- Interface system Type
Related Interface
ClassInstance State
============== ========= ============== ======== ============== ========= lan0 lan1 lan2 lan15 lan16 lan17 . lan29 lan30 lan31 lan32 lan33 lan34 lan35 lan36 DOWN DOWN DOWN UP DOWN DOWN DOWN DOWN 0x2C768A65330A iexgbe 10GBASE-KR 0x2C768A653307 iexgbe 10GBASE-KR 0x2C768A65330B iexgbe 10GBASE-KR 0x2C768A652882 iexgbe 10GBASE-KR 0x2C768A652886 iexgbe 10GBASE-KR 0x2C768A652883 iexgbe 10GBASE-KR 0x2C768A652887 iexgbe 10GBASE-KR 0x2C768A652884 iexgbe 10GBASE-KR UP DOWN DOWN DOWN UP DOWN 0x2C768A6553AE iexgbe 10GBASE-KR 0x2C768A6553B2 iexgbe 10GBASE-KR 0x2C768A6553AF iexgbe 10GBASE-KR 0x2C768A6553BD iexgbe 10GBASE-KR 0x2C768A6532FC iexgbe 10GBASE-KR
0x2C768A653300 iexgbe 10GBASE-KR
Page 5

lan37 lan38 lan900 lan901 lan902 lan903 lan904 DOWN DOWN DOWN DOWN DOWN DOWN DOWN 0x2C768A652888 iexgbe 10GBASE-KR 0x2C768A652885 iexgbe 10GBASE-KR 0x000000000000 hp_apa hp_apa 0x000000000000 hp_apa hp_apa 0x000000000000 hp_apa hp_apa 0x000000000000 hp_apa hp_apa 0x000000000000 hp_apa hp_apa
[root@ituspq09:/]# #-> nwmgr -A all -c lan16 lan16 current values: Link State = Up Speed = 1000 Mbps Full Duplex MTU = 1500 MAC Address = 0x2c768a6532fc Transmit Checksum Offload = On Receive Checksum Offload = On Virtual MTU = 32160 TCP Segmentation Offload is now enabled. TX Interrupt Timer = 48 RX Interrupt Timer = 24 Number of Queues = 4 TCP Packet Reassembly in Driver = Off [root@ituspq09:/]# #-> nwmgr -A all -c lan32
Page 6

lan32 current values: Link State = Up Speed = 1000 Mbps Full Duplex MTU = 1500 MAC Address = 0x2c768a652882 Transmit Checksum Offload = On Receive Checksum Offload = On Virtual MTU = 32160 TCP Segmentation Offload is now enabled. TX Interrupt Timer = 48 RX Interrupt Timer = 24 Number of Queues = 4 TCP Packet Reassembly in Driver = Off [root@ituspq09:/]# #-> linkloop -i 16 0x2C768A652882 Link connectivity to LAN station: 0x2C768A652882 -- OK [root@ituspq09:/]# #-> linkloop -i 32 0x2C768A6532FC Link connectivity to LAN station: 0x2C768A6532FC -- OK [root@ituspq09:/]# #-> linkloop -i 16 0x2C768A6532FC Link connectivity to LAN station: 0x2C768A6532FC
Page 7

-- OK [root@ituspq09:/]# #-> swlist -l product | grep -i HP-APA HP-APA-FMT product. HP-APA-KRN products. HP-APA-LM HP-APA-NETMOD libraries. HP-APA-RUN products. [root@ituspq09:/]# #-> what /stand/vmunix | egrep -i hp_apa $Revision: hp_apa: [root@ituspq09:/]# #-> nwmgr -S apa Class Mode Load SpeedMembership B.11.31.1103_LR B.11.31.50 B.11.31.50 B.11.31.50 HP Auto-Port Aggregation APA formatter HP Auto-Port Aggregation APA kernel HP Auto-Port Aggregation APA LM commands. HP Auto-Port Aggregation nwmgr/NCweb HP Auto-Port Aggregation APA command
B.11.31.50 B.11.31.50
Instance
Balancing Duplex
======== =========== ========= ==================== =========================== lan900 Not_Enabled LB_MAC lan901 Not_Enabled LB_MAC lan902 Not_Enabled LB_MAC lan903 Not_Enabled LB_MAC lan904 Not_Enabled LB_MAC 0 Mbps 0 Mbps 0 Mbps 0 Mbps 0 Mbps -
Page 8

[root@ituspq09:/]# #-> netstat -in Name lo0 lan0 lan16 0 Mtu Network 32808 127.0.0.0 1500 10.36.114.0 1500 10.36.112.0 Address 127.0.0.1 Ipkts 2090 15332 1845438 Ierrs Opkts 0 2090 0 0 0 1752771 Oerrs Coll 0 0 0 0 0
10.36.114.56 10.36.112.80
[root@ituspq09:/]# #-> ioscan -fkC lan Class I H/W Path Driver S/W State H/W Type Description
=================================================== ===================== lan lan lan lan .. lan lan lan lan . lan lan lan 31 1/0/0/4/0/0/7 iexgbe CLAIMED 32 2/0/0/3/0/0/0 iexgbe CLAIMED 33 2/0/0/3/0/0/1 iexgbe CLAIMED INTERFACE INTERFACE INTERFACE HP PCIe 2-p 10GbE Built-in HP PCIe 2-p 10GbE Built-in HP PCIe 2-p 10GbE Built-in 14 0/0/0/4/0/0/6 iexgbe CLAIMED 15 0/0/0/4/0/0/7 iexgbe CLAIMED 16 1/0/0/3/0/0/0 iexgbe CLAIMED 17 1/0/0/3/0/0/1 iexgbe CLAIMED INTERFACE INTERFACE INTERFACE INTERFACE HP PCIe 2-p 10GbE Built-in HP PCIe 2-p 10GbE Built-in HP PCIe 2-p 10GbE Built-in HP PCIe 2-p 10GbE Built-in 0 0/0/0/3/0/0/0 iexgbe CLAIMED 1 0/0/0/3/0/0/1 iexgbe CLAIMED 2 0/0/0/3/0/0/2 iexgbe CLAIMED 3 0/0/0/3/0/0/3 iexgbe CLAIMED INTERFACE INTERFACE INTERFACE INTERFACE HP PCIe 2-p 10GbE Built-in HP PCIe 2-p 10GbE Built-in HP PCIe 2-p 10GbE Built-in HP PCIe 2-p 10GbE Built-in
Page 9

lan lan 34 2/0/0/3/0/0/2 iexgbe CLAIMED 35 2/0/0/3/0/0/3 iexgbe CLAIMED INTERFACE INTERFACE HP PCIe 2-p 10GbE Built-in HP PCIe 2-p 10GbE Built-in
[root@ituspq09:/]# #-> cat /etc/rc.config.d/hp_apaportconf ################################################### ################## # (c) Copyright 1997-2006 Hewlett-Packard Development Company, L.P. # @(#)B.11.31.1103_LR hp_apaportconf $Revision: 1.8 $ $Date: 2000/05/15 16:21:10 $ ################################################### ################## # # hp_apaportconf : contains configuration values for Physical Ports for # # # HP_APAPORT_INTERFACE_NAME Name of physical interface (lan0, lan1...) # # HP_APAPORT_GROUP_CAPABILITY Set the group capability for the port specified # # # # # # # HP_APAPORT_KEY # Set the administrative key for the port specified The default group capability is 5. by HP_APAPORT_INTERFACE_NAME. The group capability controls which link aggregations the specified port can be grouped with. HP Auto-Port Aggregation interfaces
by HP_APAPORT_INTERFACE_NAME. The key controls
Page 10

# # # # # # HP_APAPORT_PRIORITY # # # # # # # # # HP_APAPORT_CONFIG_MODE # # # # # # # # # This is the default configuration mode for all ports which support FEC_AUTO The Cisco Fast EtherChannel (FEC) Port Aggregation Protocol (PAgP) should be started on the port. Set the configuration mode for physical port The default port priority is 0. Set the port priority for the port specified by The default administrative key is 0. which link aggregations the specified port can be grouped with.
HP_APAPORT_INTERFACE_NAME. The port priority determines which port in a link aggregation will be the primary interface when the link aggregation is set to hot standby mode (HP_APA_HOT_STANDBY="on").
specified by HP_APAPORT_INTERFACE_NAME. The supported values are listed below:
Page 11

# # # # # # # # # # # # # # # # # # # # # # HP_APAPORT_SYSTEM_PRIORITY Set the port system priority for the port # # specified by HP_APAPORT_INTERFACE_NAME. The system priority gives control to the system The default config mode is the same as the value of HP_APA_DEFAULT_CONFIG_MODE whose default is MANUAL. LAN_MONITOR Both PAgP and LACP will be disabled on the port and it must therefore be manually added or removed from a specific link aggregation using lanapplyconf landeleteconf commands. LACP_AUTO The IEEE 802.3ad Link Aggregation Control Protocol (LACP) should be started on the port. MANUAL Both PAgP and LACP will be disabled on the port and it must therefore be manually added or removed from a specific link aggregation. the HP APA product.
Page 12

# # # # # # The parameters listed above can be obtained or set directly via the # lanadmin(1m) command. # # The following examples illustrate how to use the parameters defined # above. # # HP_APAPORT_INTERFACE_NAME[0]=lan0 # HP_APAPORT_GROUP_CAPABILITY[0]=3 # HP_APAPORT_CONFIG_MODE[0]=FEC_AUTO # # HP_APAPORT_INTERFACE_NAME[1]=lan1 # HP_APAPORT_KEY[1]=5 # HP_APAPORT_CONFIG_MODE[1]=LACP_AUTO # # HP_APAPORT_INTERFACE_NAME[2]=lan2 # HP_APAPORT_CONFIG_MODE[2]=LAN_MONITOR # # ################################################### ################## The default system priority is 0. to resolve waiting ports to be added in a linkagg
Page 13
HP_APAPORT_INTERFACE_NAME[1]=lan16 HP_APAPORT_GROUP_CAPABILITY[1]=5 HP_APAPORT_CONFIG_MODE[1]=LAN_MONITOR HP_APAPORT_PRIORITY[1]=0 # HP_APAPORT_INTERFACE_NAME[2]=lan32 HP_APAPORT_GROUP_CAPABILITY[2]=5 HP_APAPORT_CONFIG_MODE[2]=LAN_MONITOR HP_APAPORT_PRIORITY[2]=0
################################################### ######################## # 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"
[root@ituspq09:/]# #-> vi /etc/rc.config.d/hp_apaportconf "/etc/rc.config.d/hp_apaportconf" [Read only] 109 lines, 3963 characters ################################################### ################## # (c) Copyright 1997-2006 Hewlett-Packard Development Company, L.P.
Page 14

# @(#)B.11.31.1103_LR hp_apaportconf $Revision: 1.8 $ $Date: 2000/05/15 16:21:10 $ ################################################### ################## # # hp_apaportconf : contains configuration values for Physical Ports for # # # HP_APAPORT_INTERFACE_NAME Name of physical interface (lan0, lan1...) # # HP_APAPORT_GROUP_CAPABILITY Set the group capability for the port specified # # # # # # # HP_APAPORT_KEY # # # # # # # HP_APAPORT_PRIORITY Set the port priority for the port specified by The default administrative key is 0. Set the administrative key for the port specified The default group capability is 5. by HP_APAPORT_INTERFACE_NAME. The group capability controls which link aggregations the specified port can be grouped with. HP Auto-Port Aggregation interfaces
by HP_APAPORT_INTERFACE_NAME. The key controls which link aggregations the specified port can be grouped with.
Page 15

# # # # # # # # # HP_APAPORT_CONFIG_MODE # # # # # # # # # # # # # # # MANUAL Both PAgP and LACP will be disabled on the port and it must therefore be manually added or removed from a specific link aggregation. This is the default configuration mode for all ports which support the HP APA product. FEC_AUTO The Cisco Fast EtherChannel (FEC) Port Aggregation Protocol (PAgP) should be started on the port. Set the configuration mode for physical port The default port priority is 0. HP_APAPORT_INTERFACE_NAME. The port priority determines which port in a link aggregation will be the primary interface when the link aggregation is set to hot standby mode (HP_APA_HOT_STANDBY="on").
specified by HP_APAPORT_INTERFACE_NAME. The supported values are listed below:
Page 16

# # # # # # # # # # # # # # # # HP_APAPORT_SYSTEM_PRIORITY Set the port system priority for the port # # # # # # # # The parameters listed above can be obtained or set directly via the The default system priority is 0. specified by HP_APAPORT_INTERFACE_NAME. The system priority gives control to the system to resolve waiting ports to be added in a linkagg The default config mode is the same as the value of HP_APA_DEFAULT_CONFIG_MODE whose default is MANUAL. LAN_MONITOR Both PAgP and LACP will be disabled on the port and it must therefore be manually added or removed from a specific link aggregation using lanapplyconf landeleteconf commands. LACP_AUTO The IEEE 802.3ad Link Aggregation Control Protocol (LACP) should be started on the port.
Page 17

# lanadmin(1m) command. # # The following examples illustrate how to use the parameters defined # above. # # HP_APAPORT_INTERFACE_NAME[0]=lan0 # HP_APAPORT_GROUP_CAPABILITY[0]=3 # HP_APAPORT_CONFIG_MODE[0]=FEC_AUTO # # HP_APAPORT_INTERFACE_NAME[1]=lan1 # HP_APAPORT_KEY[1]=5 # HP_APAPORT_CONFIG_MODE[1]=LACP_AUTO # # HP_APAPORT_INTERFACE_NAME[2]=lan2 # HP_APAPORT_CONFIG_MODE[2]=LAN_MONITOR # # ################################################### ##################
Page 18
"/etc/rc.config.d/hp_apaportconf" 104 lines, 3845 characters [root@ituspq09:/]# #-> cat /etc/rc.config.d/hp_apaportconf ################################################### ################## # (c) Copyright 1997-2006 Hewlett-Packard Development Company, L.P. # @(#)B.11.31.1103_LR hp_apaportconf $Revision: 1.8 $ $Date: 2000/05/15 16:21:10 $ ################################################### ################## # # hp_apaportconf : contains configuration values for Physical Ports for # # # HP_APAPORT_INTERFACE_NAME Name of physical interface (lan0, lan1...) # # HP_APAPORT_GROUP_CAPABILITY Set the group capability for the port specified HP Auto-Port Aggregation interfaces
Page 19

# # # # # # # HP_APAPORT_KEY # # # # # # # HP_APAPORT_PRIORITY # # # # # # # # # HP_APAPORT_CONFIG_MODE # Set the configuration mode for physical port The default port priority is 0. Set the port priority for the port specified by The default administrative key is 0. Set the administrative key for the port specified The default group capability is 5. by HP_APAPORT_INTERFACE_NAME. The group capability controls which link aggregations the specified port can be grouped with.
by HP_APAPORT_INTERFACE_NAME. The key controls which link aggregations the specified port can be grouped with.
HP_APAPORT_INTERFACE_NAME. The port priority determines which port in a link aggregation will be the primary interface when the link aggregation is set to hot standby mode (HP_APA_HOT_STANDBY="on").
specified by HP_APAPORT_INTERFACE_NAME. The
Page 20

# # # # # # # # # # # # # # # # # # # # # # # # LAN_MONITOR Both PAgP and LACP will be disabled on the port and it must therefore be manually added or removed from a specific link aggregation using lanapplyconf landeleteconf commands. LACP_AUTO The IEEE 802.3ad Link Aggregation Control Protocol (LACP) should be started on the port. MANUAL Both PAgP and LACP will be disabled on the port and it must therefore be manually added or removed from a specific link aggregation. This is the default configuration mode for all ports which support the HP APA product. FEC_AUTO The Cisco Fast EtherChannel (FEC) Port Aggregation Protocol (PAgP) should be started on the port. supported values are listed below:
Page 21

# # # # # # HP_APAPORT_SYSTEM_PRIORITY Set the port system priority for the port # # # # # # # # The parameters listed above can be obtained or set directly via the # lanadmin(1m) command. # # The following examples illustrate how to use the parameters defined # above. # # HP_APAPORT_INTERFACE_NAME[0]=lan0 # HP_APAPORT_GROUP_CAPABILITY[0]=3 # HP_APAPORT_CONFIG_MODE[0]=FEC_AUTO # # HP_APAPORT_INTERFACE_NAME[1]=lan1 The default system priority is 0. specified by HP_APAPORT_INTERFACE_NAME. The system priority gives control to the system to resolve waiting ports to be added in a linkagg The default config mode is the same as the value of HP_APA_DEFAULT_CONFIG_MODE whose default is MANUAL.
Page 22

# HP_APAPORT_KEY[1]=5 # HP_APAPORT_CONFIG_MODE[1]=LACP_AUTO # # HP_APAPORT_INTERFACE_NAME[2]=lan2 # HP_APAPORT_CONFIG_MODE[2]=LAN_MONITOR # # ################################################### ##################
[root@ituspq09:/]# #-> /sbin/init.d/hplm stop
Page 23

/sbin/init.d/hplm stopped. [root@ituspq09:/]# #-> /sbin/init.d/hpapa stop /sbin/init.d/hpapa stopped. [root@ituspq09:/]# #-> /sbin/init.d/hpapa start /sbin/init.d/hpapa started. Please be patient. This may take about 40 seconds. HP_APA_DEFAULT_PORT_MODE = MANUAL /usr/sbin/hp_apa_util -S 16 LAN_MONITOR /usr/sbin/hp_apa_util -S 32 LAN_MONITOR /sbin/init.d/hpapa Completed successfully. [root@ituspq09:/]# #-> /sbin/init.d/hplm start /sbin/init.d/hplm started. /etc/lanmon/lanconfig.ascii not present on the system. lanapplyconf will not be executed [root@ituspq09:/]# #-> lanqueryconf -s ASCII output is in file /etc/lanmon/lanconfig.ascii [root@ituspq09:/]# #-> cat /etc/lanmon/lanconfig.ascii # ******************************************************** # *********** LAN MONITOR CONFIGURATION FILE *************
Page 24

# *** 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. **
# ********************************************************
# **************************************************************** # 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 DEAD_COUNT 3 10000000
# **************************************************************** # By default, LM_RAPID_ARP is off. # If 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 # ****************************************************************
Page 25

LM_RAPID_ARP LM_RAPID_ARP_INTERVAL LM_RAPID_ARP_COUNT on 1000000 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. ** **
Page 26

# ** **
# 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 # PRIMARY # STANDBY # I/f Pri 7 6 Cost :1 :2 ** ** ** ** ** ** ** ** **
lan900 lan901
# 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
lan900
STATIONARY_IP 10.36.112.80 PRIMARY STANDBY [root@ituspq09:/]# #-> cat /etc/hosts # @(#)B.11.31_LRhosts $Revision: 1.9.214.1 $ $Date: 96/10/08 13:20:01 $ # lan16 5 lan32 3
Page 27

# The form for each entry is: # <internet address> # # For example: # 192.1.2.34 # # See the hosts(4) manual page for more information. # Note: The entries cannot be preceded by a space. # # # # The format described in this file is the correct format. The original Berkeley manual page contains an error in the format description. hpfcrm loghost <official hostname> <aliases>
10.36.112.80 127.0.0.1 10.36.114.56
ituspq09 ituspq09.jnj.com localhost loopback
ituspq09bkp ituspq09.backup.jnj.com
[root@ituspq09:/]# #-> lancheckconf Reading ASCII file /etc/lanmon/lanconfig.ascii Verification of input file /etc/lanmon/lanconfig.ascii is complete. [root@ituspq09:/]# #-> cat /etc/lanmon/lanconfig.ascii # ******************************************************** # *********** LAN MONITOR CONFIGURATION FILE *************
Page 28

# *** 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. **
# ********************************************************
# **************************************************************** # 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 DEAD_COUNT 3 10000000
# **************************************************************** # By default, LM_RAPID_ARP is off. # If 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 # ****************************************************************
Page 29

LM_RAPID_ARP LM_RAPID_ARP_INTERVAL LM_RAPID_ARP_COUNT on 1000000 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. ** **
Page 30

# ** **
# 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 # PRIMARY # STANDBY # I/f Pri 7 6 Cost :1 :2 ** ** ** ** ** ** ** ** **
lan900 lan901
# 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
lan900
STATIONARY_IP 10.36.112.80 PRIMARY STANDBY [root@ituspq09:/]# #-> lanapplyconf Reading ASCII file /etc/lanmon/lanconfig.ascii Creating Fail-Over Group lan900 lan16 5 lan32 3
Page 31

[root@ituspq09:/]# #-> nwmgr -S apa Class Mode Load SpeedMembership
Instance
Balancing Duplex
======== =========== ========= ==================== =========================== lan900 LAN_MONITOR LB_HS lan901 Not_Enabled LB_MAC lan902 Not_Enabled LB_MAC lan903 Not_Enabled LB_MAC lan904 Not_Enabled LB_MAC [root@ituspq09:/]# #-> netstat -in Name lo0 lan0 lan900 Mtu Network 32808 127.0.0.0 1500 10.36.114.0 1500 10.36.112.0 Address 127.0.0.1 Ipkts 2109 15347 155 Ierrs Opkts 0 2109 0 0 0 154 Oerrs Coll 0 0 0 0 0 0 1 Gbps Full Duplex 16,32 0 Mbps 0 Mbps 0 Mbps 0 Mbps -
10.36.114.56 10.36.112.80
[root@ituspq09:/]# #->
Page 32

Configure Lan Monitor: HP APA Provides The Following

Uploaded by

Copyright:

Available Formats

Configure Lan Monitor: HP APA Provides The Following

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configure Lan Monitor: HP APA Provides The Following

Uploaded by

Copyright:

Available Formats

Configure Lan Monitor