HP Auto Port Aggregation Administrator's Guide HP-UX 11i v3 HP Part Number: 766140-001 Published: March 2014 Edition: 1
© Copyright 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents HP secure development lifecycle......................................................................6 1 Introduction...............................................................................................7 Conceptual overview.................................................................................................................7 Link aggregate....................................................................................................................8 Load balancing.........
Displaying the current APA configuration...................................................................................34 Displaying the link aggregate details........................................................................................34 Modifying HP APA global parameters.......................................................................................35 Performing Critical Resource Analysis........................................................................................
D VLANs over APA using HP Procurve switches...............................................92 Configuring VLANs over link aggregates...................................................................................92 Configuring VLANs over failover groups....................................................................................93 E Switch configuration information.................................................................97 Cisco 3120X switches...............................................
HP secure development lifecycle Starting with HP-UX 11i v3 March 2013 update release, HP secure development lifecycle provides the ability to authenticate HP-UX software. Software delivered through this release has been digitally signed using HP's private key. You can now verify the authenticity of the software before installing the products, delivered through this release. To verify the software signatures in signed depot, the following products must be installed on your system: • B.11.31.
1 Introduction 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. This port arrangement provides more data bandwidth than would otherwise be available and enables you to build large bandwidth logical links into the server that are highly available and completely transparent to the client and server applications.
• Interoperability with HP Serviceguard • Administrative methods Link aggregate HP APA enables you to combine multiple physical link ports into one. This gives the link aggregation a theoretical bandwidth of 8 times that of a single physical link (32 times for LACP mode). For maximum number of links for each link aggregate, see the APA Support Matrix A link aggregate has the following characteristics: • The physical ports in the link aggregation use the same MAC address.
Therefore, HP prefers you use the algorithm that is recommended for each supported configuration. See “Preparing for configuration” (page 23) for more information. The load balancing algorithm consists of the following steps: 1. Data Flow Lookup — The load distribution algorithm determines an index into a hash table that includes the physical port through which the outbound data flow is forwarded. 2.
With proactive failover, the port that is the most efficient at carrying traffic is the active port. Efficiency is determined by assigning a cost to each port in a failover group. This cost is divided by the port's current link speed to yield a normalized port cost; link speed is the number of links in a link aggregate multiplied by the speed of a member link, or in the case of a single link, only the link speed. The lower the normalized port cost, the higher the link's efficiency.
VLAN support VLANs over link aggregates and failover groups have the same advantages of VLANs over physical links, but with the following additional features: • VLANs over link aggregates offer higher bandwidth than VLANs over a single physical link. • VLANs over failover groups offer improved reliability. The VLANs continue to carry traffic in case the active link failed. • You can use VLANs over one link aggregate to serve multiple workgroups.
1. From a character-cell terminal or terminal window, enter: # smh If the DISPLAY environment variable is set, HP SMH opens in the default web browser. If the environment variable is not set, HP SMH opens in the TUI. Figure 1 shows the SMH Main page. Figure 1 SMH Main Page 2. 3. Click Tools. The Tools page displays. Scroll down and click Auto Port Aggregation in the Network Interfaces Configuration tool. The APA main page displays as shown in Figure 2.
to save the entire configuration. For more information about the nwmgr command and using it to administer APA, see Chapter 5 (page 41), nwmgr(1M), and nwmgr_apa(1M), respectively. NOTE: The lanadmin, lanscan, and linkloop commands are deprecated. These will be removed in a future HP-UX release. HP recommends the nwmgr command to perform all network interface-related tasks.
2 Installing the APA software This chapter describes the information required in order to install APA on your system. Installation requirements 1. 2. 3. Log in to the HP-UX server as superuser. Confirm that the /usr/bin, /usr/sbin, and /sbin directories are in your PATH by using the echo $PATH command. Use the uname -a command to determine the HP-UX version of your system. Product dependencies See the HP-UX Auto Port Aggregation (APA) Release Notes for required patches and known problems and workarounds.
6. 7. 8. 9. Choose Mark for Install from the Actions menu. Choose Install from the Actions menu to begin product installation and to display the Install Analysis window. Click OK in the Install Analysis window when the Status field displays a Ready message. Click YES at the Confirmation window to confirm that you want to install the software. The swinstall command loads the fileset, runs the control scripts for the filesets, and builds the kernel.
6. Click YES at the Confirmation window to confirm that you want to remove the software. The swremove command unloads the fileset, runs the control scripts for the filesets, and builds the kernel. The estimated time for processing is 3 to 5 minutes depending on the complexity of your system. When the status field indicates Ready, a Note window opens. Click OK on the Note window to reboot the system. NOTE: kernel.
3 Configuring APA This chapter describes how to configure HP APA on your system. This includes: • Reviewing sample HP APA configurations • Preparing for the configuration by gathering information • Configuring systems in sample configurations • Configuring a link aggregate • Configuring a failover group • Configuring the link partner • Performing post-configuration tasks HP APA configuration examples This section shows some sample HP APA configurations.
Figure 3 Sample Router and Server Configuration (No Switch) HP APA 2-4 Port Link Aggregation Router or Switching Router Intranet Intranet Internet or large enterprise environments using routers You can use HP APA link aggregation successfully in certain environments employing routers. You must be careful because a particular router might not have a load balancing capability.
server's link aggregation. For example: The server's link aggregation is composed of 100BT links and the link between the switch and the router is a Gigabit link. Figure 4 Sample Router and Server Configuration (Switch) HP APA 2-4 Port Link Aggregation Switch Router or Switching Router Intranet Intranet Server-to-Server (Back-to-Back) Figure 5 (page 20) shows a sample server-to-server configuration.
Figure 5 Sample Server-to-Server Configuration (Back-to-Back) HP APA 2-4 Port Link Aggregation LAN Monitor for high availability Figure 6 (page 21) shows a sample LAN Monitor mode configuration. These link aggregations provide high availability network access with an active link and a standby link.This configuration has the following characteristics: 20 • The failover group active link carries network traffic until it or its link partner fails.
Figure 6 Sample LAN Monitor Configuration for High Availability HP APA 2-Port LAN Monitor (failover group) Primary Standby Switch Switch LAN Failover group Figure 7 (page 22) shows a sample failover group (LAN_MONITOR mode) configuration. This configuration provides high availability network access with an active link and a standby link, and has the following characteristics: • Dual switches are not required.
Figure 7 Sample Failover Group (LAN_MONITOR) Configuration LAN Monitor 3-Port Failover Group LAN Monitor 2-Port Failover Group Active Standby Switch Switch LAN Active 2 Standby Links Switch Switch LAN Failover group using link aggregates Figure 8 (page 23) shows a failover group that uses link aggregates as the active and standby devices to increase the network bandwidth through load balancing across the physical links.
Figure 8 Sample Failover Group Using Link Aggregates Configuration Active Link Agg Standby Link Agg Intranet Active Link Agg Standby Intranet NOTE: The left part of the image denotes the LAN monitor failover group using HP APA link aggregations. The right part of the image denotes LAN monitor failover group using an HP APA link aggregation as the active link and one physical link as a standby link.
Figure 9 HP APA Configuration Worksheet HP APA Configuration Worksheet Aggregate Instance Number Mode FEC_AUTO LACP_AUTO LAN_MONITOR Not_Enabled Failover Priority Based Cost Based Instance Number: Hardware Path: Interface Type: Priority: Cost: Advanced Parameters (Link Aggregates) Load Distribution Algorithm LB_MAC LB_IP HOT_STANDBY Group Capability (FEC_AUTO only) Key (LACP_AUTO only) Advanced Parameters (Failover Groups) Dead Count Polling Interval Rapid ARP Rapid ARP Interval Rapid A
Aggregate Instance Number The PPA number of the link aggregate or failover group. Enter a value. For example, use 900 for lan900. Mode The configuration mode of the link aggregate or failover group. Your choice will be determined by the capabilities of the link partner (for example, switch, router, or server) to which the link aggregate physical interfaces will be connected. See your link partner's documentation to determine which modes it supports. Check the mode you want to use.
Priority The port priority in a failover group (LAN_MONITOR mode) using priority-based failover or cost-based failover. If you assign a priority value to one link, you must assign a priority value to all links in the failover group. Leave this blank if you do not want to assign a priority value; HP APA will assign it. Cost The port cost in a failover group (LAN_MONITOR mode) using cost-based failover.
Failover group advanced parameters Dead Count The number of polling packets that are missed before LAN Monitor sends a nettl log message to the user that indicates the link might have problems and the network must be checked. The default is 3. Polling Interval The number of microseconds between polling messages. Polling messages are sent between links in the specified interval for monitoring the health of all the links in the link aggregate. Default is 10,000,000 (10 seconds).
1. Click Create Link Aggregate on the APA main page to open the Create Link Aggregate page as shown in Figure 10. Figure 10 Create Link Aggregate Page 2. 3. 4. 5. Select a Link Aggregate Instance, or accept the default. If you select a different value, the display refreshes. Select an APA Mode. If you change the mode, the display refreshes. Select the links to include in the link aggregate. Click Advanced Parameters to display additional link aggregate parameters.
Configuring a failover group Use the Network Interfaces Configuration tool of SMH to create a failover group. To invoke SMH, follow the instructions in “Administrative methods” (page 11). See the same section for alternatives to using SMH. Complete the following steps: 1. Click Create Failover Group on the APA main page to open the Create Failover Group page as shown in Figure 12. Figure 12 Create Failover Group Page 2. 3. 4. Select a Link Aggregate Instance, or accept the default.
Configuring an IP address After you configure HP APA, you must configure an IP address on the interface. To configure an IP address for a link aggregate or failover group, do the following: 1. Select a link aggregate or failover group in the list pane on the APA main page. The interface details are displayed in the details pane. 2. Click View/Modify IP Attributes. The View/Modify Attributes page is displayed. 3. Modify the needed IPv4 attributes. 4. Modify the needed IPv6 attributes. 5.
Verifying the configuration The APA main page displays all configured link aggregates and failover groups, and any available ports on the system. Alternatively, you can view all configured link aggregates by issuing the following command: # nwmgr -S apa What happens during start up? During the system boot-up, the following events occur: 1. HP APA software initializes All the internal housekeeping initialization (for example, allocation of memory) for the software is done.
4 Administering HP APA Administering HP APA consists of performing the following tasks: • “Modifying a link aggregate” (page 32) • “Modifying a failover group” (page 32) • “Deleting a link aggregate” (page 32) • “Deleting a failover group” (page 34) • “Displaying the current APA configuration” (page 34) • “Displaying the link aggregate details” (page 34) • “Modifying HP APA global parameters” (page 35) • “Performing Critical Resource Analysis” (page 36) • “Stopping FEC or LACP protocol” (pa
Figure 13 Delete Link Aggregate Page 3. 4. Select the Configuration Options you want, if different from the default. Click OK to delete the link aggregate. An Operation Successful page appears (Figure 14), confirming the deletion of the link aggregate and the updating of the APA configuration.
Figure 14 Operation Successful Page (Delete) 5. Click OK. The APA main page displays. Deleting a failover group To delete a failover group, do the following: 1. Select a failover group (a link aggregate with LAN_MONITOR mode) in the SMH APA main page to display the detailed view of the failover group. 2. Click Delete Failover Group in the details pane to display the Delete Failover Group page. 3. Select the Configuration Options you want, if different from the default. 4.
3. Click OK to display the APA main page when you are finished viewing the information. Modifying HP APA global parameters The following HP APA global parameters are stored in the /etc/rc.config.d/hp_apaconf file: Default Port Mode The default configuration mode for link aggregates. The supported values are as follows: MANUAL Disables FEC and IEEE 802.3ad LACP on all ports that support HP APA. You must manually add or remove them from the specific link aggregate. This is the default.
hp_apaportconf, and /etc/lanmon/lanconfig.ascii files, which maintains the modified APA global parameter changes across reboots. Performing Critical Resource Analysis Critical Resource Analysis (CRA) provides usage analysis for interfaces (ports and link aggregates). This includes applications that are using the interfaces. To perform CRA, do the following: 1. Select a link aggregate in the APA main page to display the detailed view of the link aggregate. 2.
Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar . . . Mar Mar Mar 1 2 3 4 5 3 3 3 3 3 3 3 3 3 3 08:49:54 08:49:54 08:50:20 08:50:20 08:50:20 08:50:20 08:51:34 08:50:26 08:52:05 08:52:05 hpserver1 hpserver1 hpserver1 hpserver1 hpserver1 hpserver1 hpserver1 hpserver1 hpserver1 hpserver1 vmunix: vmunix: vmunix: vmunix: vmunix: vmunix: vmunix: vmunix: vmunix: vmunix: APA/LM: APA/LM: APA/LM: APA/LM: APA/LM: APA/LM: APA/LM: APA/LM: APA/LM: APA/LM: Product is now running. 1 Product is now stopped.
NOTE: Cisco's Fast EtherChannel (FEC) packets are not counted in the link aggregate statistics. This is required because the FEC packets never traverse the link aggregate, they only traverse the port. Link aggregates support 64-bit statistics based on the following rules: • Aggregates support the 64-bit MIB (Management Information Base) if all the member links are capable of 64-bit statistics when the aggregate is created.
Example 2 Sample Link Aggregate 64-Bit Statistics # nwmgr --st -I 901 -S apa *** lan901 64 bit MIB statistics: Interface Name = lan901 PPA Number = 901 Description = lan901 Hewlett-Packard LinkAggregate Interface MTU Size = 1500 Speed = 3 Gbps Station Address = 0x0012794371B4 Administration Status = UP Operation Status = UP Last Change = Thu Sep 28 18:35:11 2006 Inbound Octets = 1353732 Inbound Unicast Packets = 0 Inbound Multicast Packets = 0 Inbound Broadcast Packets = 0 Inbound Discards = 0 Inbound Error
--iteration count By default, the monitor action continues until you enter Ctrl+c. Minimum value is 1. For more information, see nwmgr_apa(1M). Example 3 shows the 32-bit statistics monitoring.
5 Using the nwmgr command In addition to the preferred SMH GUI and TUI interfaces for configuring and managing HP APA, HP-UX provides the nwmgr command for managing all LAN-based and IB-based network interfaces. The nwmgr command serves as a single tool for performing all network interface-related tasks, offering the functionality provided by the lanscan, lanadmin, linkloop, lanapplyconf, and landeleteconf commands. NOTE: The lanadmin, lanscan, and linkloop commands are deprecated.
• Remove ports from a link aggregate or failover group (--delete option) • Set APA attributes on a port or link aggregate interface (--set option) • Set global attributes to the HP APA configuration files (--set option) • Save the current HP APA configuration to the HP APA configuration files (--saved option) • View all APA interfaces (--get option, the default) • View all or specified attributes of an APA or physical LAN interface • View all or specified APA global attributes (-q global or -A
Example 4 nwmgr Output (No Options) # nwmgr Name/ ClassInstance ============== lan0 lan1 lan2 lan3 lan4 lan5 lan6 lan7 lan8 lan9 lan900 lan901 lan902 lan903 lan904 Interface State ========= UP UP UP UP UP UP UP UP UP UP DOWN DOWN DOWN DOWN DOWN Station Address ============== 0xD4C9EF06945E 0xD4C9EF069462 0xD4C9EF069466 0xD4C9EF06946A 0x001B78789378 0x001B78789379 0x001B7878937A 0x001B7878937B 0x001B78293AA0 0x001B78293AA1 0x000000000000 0x000000000000 0x000000000000 0x000000000000 0x000000000000 Subsyste
Example 5 nwmgr Command Verbose Output (Failover Group) # nwmgr -S apa -I 900 -v lan900 current values: Speed = 1 Gbps Full Duplex MTU = 1500 Virtual Maximum Transmission Unit = 0 MAC Address = 0x00306EF2BADE Network Management ID = 26 Features = Linkagg Interface 1 IPV4 Recv CKO IPV4 Send CKO VLAN Support VLAN Tag Offload 64Bit MIB Support Load Distribution Algorithm = LB_HS Mode = LAN_MONITOR Parent PPA = - 2 APA State = Up 3 Membership = 9,21,22,14,13* 4 Active Port(s) = 9 5 Ready Port(s) = 21,22,14 6 No
8 9 A list of the ports connected to the active port. This indicates that polling packets are being sent successfully between the active port and the connected port(s). This field is displayed only when the Mode is LAN_MONITOR. The failover policy for the failover group. For a description of failover policy, see “Failover group” (page 9) and “Preparing for configuration” (page 23). The policy tells how active port is selected.
Example 6 nwmgr Verbose Output (Link Aggregate) # nwmgr -S apa -I 920 -v lan920 current values: Speed = 2 Gbps Full Duplex MTU = 1500 Virtual Maximum Transmission Unit = 0 MAC Address = 0x00127942FC38 Network Management ID = 46 Features = Linkagg Interface IPV4 Recv CKO IPV4 Send CKO VLAN Support VLAN Tag Offload 64Bit MIB Support Load Distribution Algorithm = LB_MAC Mode = LACP_AUTO Parent PPA = APA State = Up Membership = 13,14 Active Port(s) = 13,14 Not Ready Port(s) = Key = 920 Operational Key = 920 Ex
Key = 900 # nwmgr -s -A key=900,mode=LACP_AUTO -I 2 -S apa lan2 new values: Mode = LACP_AUTO Key = 900 Deleting an HP APA interface Before attempting to delete an HP APA interface, ensure that there are no applications or upper layer protocols active on the interface. Perform a critical resource analysis operation on the interface, by entering: # nwmgr --cra -c lanaggregate_instance The --cra operation displays all applications and commands currently assigned to the interface.
Table 1 Legacy Commands and Corresponding nwmgr Commands Task Legacy Command nwmgr Command Display command help lanadmin -X -H 900 nwmgr --help -S apa View link aggregate status lanadmin -x -v 900 nwmgr -c lan900 Create a failover group lanapplyconf nwmgr -a -A links=1,2 -A mode=LAN_MONITOR -I 900 -S apa Remove all ports from a link aggregate lanadmin -X -c 900 nwmgr -d -A links=all -I 900 -S apa Remove all ports from a failover group landeleteconf -g lan900 nwmgr -d -A links=all -c lan900
Table 1 Legacy Commands and Corresponding nwmgr Commands (continued) Task Legacy Command nwmgr Command Display current port priority lanadmin -x -t 5 900 nwmgr -A port_pri -I 5 -S apa Display aggregate status lanadmin -x -v 900 nwmgr -v -c lan900 Check network connectivity linkloop -i 900 0xaabbccddeeff nwmgr --diag -A dest=0xaabbccddeeff -c lan900 Get statistics lanadmin -g 900 nwmgr --st -c lan900 Monitoring statistics apa-monitor -p 5 nwmgr --st monitor -S apa -I 900 Reset an APA interfa
6 Troubleshooting HP APA This chapter contains a diagnostic map to help you solve problems that might occur when you use HP APA. Use this chapter with the appropriate HP and third-party switch documentation to solve as many problems as possible at your level. Operation Network problems can occur for a number of reasons. The diagnostic map in this chapter help you to isolate the problem.
If you see error messages about link aggregate attributes, do the following: 1. Stop HP APA with the following commands: # /sbin/init.d/hplm stop # /sbin/init.d/hpapa stop 2. 3. Correct the attribute in the appropriate configuration file. Restart HP APA with the following commands: # /sbin/init.d/hpapa start # /sbin/init.d/hplm start Search for the string hplm in the /etc/rc.log file. If there are failover groups configured on your system, the preceding message indicates an error.
3. mode and enable autonegotiating, if necessary. Then, reset the NIC with the nwmgr command Verify that your interface state is UP by issuing the nwmgr command with no arguments. If it is not up, perform the steps for NIC claimed?. Verify that the network daemon (inetd) is running. Enter the following command: # ps -e | grep inetd If no inetd daemon is running, start it using the following command: # /sbin/init.
Verify that the link aggregate is enabled by issuing the following command: # nwmgr -v -c lanxxx where xxx is the link aggregate instance number (for example, 900). If the aggregate is enabled, the APA State is Up. This also indicates that any LACP automatic protocol negotiation was successful. If the APA State is Down, do the following: 1.
1. Verify the type, speed, duplex mode, MTU size, and checksum offload capability of each port you want with the following command: # nwmgr -v -c lanxxx where xxx is the instance number for the port. All ports must have the same values. NOTE: All the links in the aggregate should be having same capability. For example, you cannot aggregate a port that has no CKO capability with a port that has CKO capability, even if its CKO capability is currently disabled. To change an attribute, do the following: a.
3. Verify that the port's key value matches the value of the link aggregate. If it does not, do the following: a. Set the port mode to MANUAL with the following command: # nwmgr -s -A mode=MANUAL -I port-number -S apa b. Set the key value and mode with the following command: # nwmgr -s -A key=value, mode=LACP_AUTO -I port-number -S apa c. d. The ports then negotiate with the link partner (approximately 10 seconds) and join the link aggregate. Repeat this step for each port you want in the aggregate.
4. 5. add it. Also, verify that the DNS service has information about the remote host. If your site uses the NIS name service for name-to-address translation, look in the /etc/nsswitch.conf file to see if nis is specified as a service for the hosts database entry. If it is not, add it. Also, verify if the NIS service has information about the remote host. If your /etc/nsswitch.
4. 5. Verify that the directory and file protection on the files to be copied or the .rhosts file on the remote system are correct. If you are using NFS, see the appropriate NFS documentation. If the telnet command is not successful, there is a problem with the Transport Layer (OSI Layer 4). Do the following: 1. Verify whether you have a problem with a pseudoterminal driver (pty) on your system by issuing the ftp command to the remote host.
Problem still exists? Report your problem to HP. See “Reporting problems ” (page 71). If you suspect or know that you are experiencing packet loss over your connection, do the following: 1. LACP mode link aggregates require time to negotiate with the switch. You might drop some packets during this time. 2. Check the trunk is configured correctly on the switch. Make sure that ports connected to the ports on the server are assigned to the LACP trunk.
2. Verify that the link partner is configured to run the Cisco Fast EtherChannel protocol. Make any changes, if necessary, and wait 10 seconds. Then, verify that the link aggregate is enabled. Verify the ports in the link aggregate by issuing the following command: # nwmgr -A all -c lanxxx -S apa where xxx is the link aggregate instance number. The Membership column shows the ports that compose the link aggregate.
# nwmgr --st -c lanxxx where xxx is the port number (for example, 1, 4, or 10). If the Operation Status is UP, see the steps for Link partner configured?. If the status is down, check the cabling from the NIC to the switch and see the steps for NIC operating?. If a remote host's network is not reachable, the following message is displayed in response to the ping command: network is unreachable Complete the following steps: 1.
4. Verify that an entry exists for the remote host in your system's ARP cache by entering the following command: # arp hostname If the entry is wrong or incomplete, enter the correct station address by using the arp command. See arp(1M) for more information. 5. 6. 7. 8. Make sure the network devices are configured properly on the local host, using the netstat -i command. Verify that the routing tables on the local host are correct, using the netstat -r command.
Problem still exists? Report your problem to HP. See “Reporting problems ” (page 71). If the connection terminates abnormally or a network application appears to hang, complete the following steps: 1. Test the network to determine whether the problem is on the local host, remote host, or a host on the path between the two. 2. After you identify the host with the problem, do the following: a. Confirm that the NIC is properly configured.
Verify the ports in the failover group by issuing the following command: # nwmgr -S apa where xxx is the failover group instance number. The Membership column shows the ports that compose the failover group. If the failover group contains ports that you do not want, delete the ports by issuing the following command: # nwmgr -d -A links=port-number -c lanxxx where port-number can be a list of multiple ports numbers separated by commas and xxx is the instance number of the failover group (for example, 900).
Verify the active ports in the failover group by issuing the following command: # nwmgr -v -c lanxxx where xxx is the failover group instance number. The Active Port(s) field lists the active ports. If there are ports in the Not Ready Port(s) field, verify the port's operation status by issuing the following command: # nwmgr --st -c lanxxx where xxx is the interface number. If the Operation Status is UP, wait 30 seconds to see if the port becomes ready or active.
If the active port priority is greater than the intended port priority, modify the priority value for the intended port (making it greater than the current active port) with the following command: # nwmgr -s -A port_pri=value -c lanxxx -S apa Wait 30 seconds for the change to take effect. Verify the active port again.
1. 2. Ensure that the network devices are configured properly on the local host, using the netstat -i command. Verify that the routing tables on the local host are correct, using the netstat -r command. If a host is not known, the following message is displayed: unknown host Complete the following steps: 1. Verify that the user is trying to reach the remote host using a valid host name. 2. Verify that the remote host is in another name domain and that the user specified the full domain name. 3.
7. 8. Verify that the local host's address-to-name translation for the remote host is correct by using the nslookup command. Inspect the routers along the path to the remote host to determine whether they have security features enabled that prevent you from reaching the remote host. If a file cannot be accessed using the rcp or rsh command, the following message is displayed: permission denied Complete the following steps: 1. Verify that the user is intended to have access to the remote host.
Problem still exists? Report your problem to HP. See “Reporting problems ” (page 71). 2. After you identify the host with the problem, do the following: a. Confirm that the NIC is properly configured. Verify that the broadcast address and address mask for the local host are correct. b. Make sure the local host's /etc/hosts file has the correct IP address for the local host. c. Make sure the cabling from the local host to the network is intact and properly connected. d.
See ping(1M) for more information on the command and its options. Scanning the system hardware Use the ioscan command to scan the system hardware and list the results.
You can access the logging and tracing utility using either the graphical user interface (GUI) version or the command line interface. The GUI version does the following: • Guides you through logging and tracing tasks. • Enables you to create and format reports. • Collects logging and tracing information specific to a subsystem. • Displays report screens that are updated instantaneously with current logging and tracing information by the subsystem. • Provides context-sensitive on-line help.
Whenever the TSO status of a link aggregate or failover group changes, a warning message is logged in the nettl.LOG000 file. For example, when the TSO capability is disabled on an aggregate, a WARNING message similar to the following is logged: ----------------------Auto-Port Aggregation/9000 Networking--------------@#% Timestamp : Wed Aug 18 PDT 2004 09:37:56.
2. Obtain the version, update, and fix information for all software. To check the HP APA version number, enter the following command: # what /stand/vmunix | grep -i -e hp_apa -e pagp -e lacp To check the version of your kernel, enter uname -r. This information enables HP to determine if the problem is already known and if the correct software is installed at your site. 3. 4. 5. 6. 7. 8. Prepare copies of the following files: • /etc/rc.config.d/netconf • /etc/rc.config.d/hp_apaconf • /etc/rc.config.
7 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • See the Contact HP worldwide website • Use the GET HELP FRO
Computer output Text displayed by the computer. Ctrl+x A key sequence. A sequence such as Ctrl+x indicates that you must hold down the key labeled Ctrl while you press another key or mouse button. ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH. ERROR NAME The name of an error, usually returned in the errno variable. Key The name of a keyboard key. Return and Enter both refer to the same key. Term The defined use of an important word or phrase.
8 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
A Product specifications For product specifications and supported configurations, see APA Support Matrix.
B HP APA configuration files HP APA uses the following configuration files: • /etc/rc.config.d/hp_apaconf • /etc/rc.config.d/hp_apaportconf • /etc/lanmon/lanconfig.ascii The following sections describe each file and its parameters. For configuration examples that describe editing these files, see Appendix C (page 85). hp_apaconf file The /etc/rc.config.d/hp_apaconf file contains the following general HP APA configuration parameters for link aggregates.
HP_APA_GROUP_CAPABILITY HP_APA_INTERFACE_NAME HP_APA_KEY HP_APA_LACP_SYSTEM_ID_MODE HP_APA_LACP_TIMEOUT HP_APA_LOAD_BALANCE_MODE For FEC_AUTO only. An integer value used to determine which network physical ports can be aggregated into a common FEC link aggregate. Set the group capability to be the same for all network physical ports in the same link aggregate. Ports going to different link aggregates must have different group capabilities.
HP_APA_USE_SYSLOG of the HP_APA_FIXED_MAC parameter; the link aggregate is assigned the specified MAC address. Enables (1) or disables (0) the logging of status messages to the syslog.log file (for example, when a link aggregate or port fails or comes up). The default value is 0. See Section for sample syslog.log messages and their meaning.
HP_APAPORT_INTERFACE_NAME HP_APAPORT_KEY Name of physical interface. For example, lan0 and lan1. For LACP_AUTO only. An integer value that determines which network physical ports can be aggregated into a common LACP link aggregate. Set the key to be the same for all network physical ports. The key must match the key of the desired aggregate that the user wants the port to join. This value is set in the /etc/rc.config.d/hp_apaconf file.
Example 10 Sample lanconfig.ascii Configuration File #*********************************************** #******* 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 values are microseconds; they are rounded up #*** or down appropriately.
FAILOVER_GROUP STATIONARY_IP STATIONARY_MAC STANDBY PRIMARY lan900 193.33.33.33 0x021122334455 lan9 7 lan6 5 FAILOVER_GROUP STATIONARY_IP PRIMARY STANDBY STANDBY STANDBY lan901 195.55.55.55 lan4 5 lan1 3 lan2 3 lan3 3 FAILOVER_GROUP STATIONARY_IP PRIMARY STANDBY lan902 fe80::2 lan11 5 lan10 3 The lanconfig.ascii configuration file contains the following fields: FAILOVER_GROUP The name for a single LAN Monitor failover group. You must specify a name for each LAN Monitor failover group on the system.
In previous versions of HP APA, the port must have IP address configured and must be the highest priority or lowest cost. In the HP-UX 11i v3 version of HP APA, you can assign the port any priority or cost values. You also need not configure an IP address on it. HP recommends that you always assign the port the highest priority or the lowest cost in a failover group. Specifies a standby port for the FAILOVER_GROUP.
If you specify the POLLING_INTERVAL, DEAD_COUNT, LM_RAPID_ARP_INTERVAL, and LM_RAPID_ARP_COUNT fields once in the lanconfig.ascii file before all failover, the values apply to all failover groups. If you specify them multiple times in the file, the values apply only to those failover groups that follow these fields; you can set different values for failover groups.
C Configuring HP APA by editing files This appendix provides information about editing the different configuration files to configure the following: • Link aggregates • Failover groups Editing configuration files for link aggregates This section shows how to configure the three modes associated with port aggregation. For release-specific information, see the release notes on your system in the /opt/networkdocs directory or on the web at: HP Support Centre.
3. Activate the new configuration by entering: # # # # /sbin/init.d/hplm stop 1 /sbin/init.d/hpapa stop 2 /sbin/init.d/hpapa start /sbin/init.d/hplm start 3 1 2 3 If failover groups are also configured. This can interrupt traffic on existing link aggregates. For configuring failover groups. FEC_AUTO port configuration mode To configure load balancing and group capability for link aggregate 901 with MAC-based load balancing, do the following: 1. Edit the /etc/rc.config.
HP_APAPORT_INTERFACE_NAME[1]=lan2 HP_APAPORT_CONFIG_MODE[1]=LAN_MONITOR 4. 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 5. If the device to be the link does not have the desired IP address, add the IP address for the active port or link aggregation to /etc/rc.config.d/netconf. Editing that file or using SMH will preserve the IP address permanently (across reboots).
Example: Configuring a failover group Suppose you want to configure a simple, two-port LAN Monitor failover group on a K-class system. You enter the netstat and ioscan commands as follows: # netstat Name Mtu lan1 1500 lan0 1500 lo0 4136 -in Network 192.1.1.0 191.1.1.0 127.0.0.0 Address 192.1.1.153 191.1.1.1 127.0.0.
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 SMH 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 ASCII output is in the /etc/lanmon/lanconfig.ascii file. a. Verify that the content of the ASCII file is valid.
Proactive failover examples Proactive failover relies on measuring and calculating efficiency. The efficiency of a link aggregate or individual port in a failover group is affected by the following: • The number of ports in each member of the failover group • The effective throughput of the switch or router to which the failover group members are connected The following examples show how each affects the proactive failover operation.
Example 2 You want to configure a failover group (lan902) for proactive failover. You decide that the failover group consists of two link aggregates: lan900 and lan901. The lan900 aggregate consists of ports 2 and 3; the lan901 aggregate consists of ports 4 and 5. Ports 2, 3, 4, and 5 have speeds of 100 Mb/s. In addition, the link aggregates are connected to different routers using different speeds to connect to the network. To configure the failover group for proactive failover, do the following: 1.
D VLANs over APA using HP Procurve switches This appendix describes how to create VLANs over trunks and ports on an HP Procurve switch. For more information about creating VLANs on HP Procurve switches, see Procurve, Series 6400cl Switches, Series 5300xl Switches, Series 3400cl Switches, Advanced Traffic Management Guide at: ftp://ftp.hp.com/pub/networking/software/ 6400-5300-3400-AdvTrafficMgmt-Oct2005-59906051.
4. Verify that the VLAN with ID 333 is tagged to Trk3. Enter: HP ProCurve Switch 3500yl-24G# show vlan 333 Status and Counters - VLAN Information - Ports - VLAN 333 802.1Q VLAN ID : 333 Name : vlan_333 Status : Port-based Voice : No Port Information Mode Unknown VLAN Status ---------------- -------- ------------ ---------Trk3 Tagged Learn Up VLAN 333 has been successfully tagged to Trk3. On the server side, complete the following steps: 1. Create link aggregate lan900 using ports lan3 and lan4.
Figure 16 VLAN over a Failover Group Run lan901 Atn. Fault Remote Power lan6 lan5 Failover Group lan902: lan901 (Primary), lan5, 6 (Standby) Switch1 Switch2 Trk4 Vlan 333 Vlan 334 F17 F18 Vlan 333 Vlan 334 As the first step in creating the failover group, associate the ports in link aggregate lan901 to Trk4 on Switch 1; set the trunk type to LACP. Connect ports lan5 and lan6 to ports F17 and F18, respectively, on Switch 2. To create the VLANs on Switch 1, complete the following steps: 1.
3. Verify that the VLANs with IDs 333 and 334 are tagged correctly. Enter: Switch 1# show vlan 333 Status and Counters - VLAN Information - Ports - VLAN 333 802.1Q VLAN ID : 333 Name : vlan_333 Status : Port-based Voice : No Port Information Mode ---------------- -------Trk4 Tagged Switch 1# show vlan 334 Status and Counters - VLAN Unknown VLAN Status ------------ ---------Learn Up Information - Ports - VLAN 334 802.
On the server side, complete the following steps: 1. Create link aggregate lan900 using ports lan and lan2. Enter: # nwmgr -s -A key=900,mode=LACP_AUTO -I 1 -S apa lan1 new values: Mode = LACP_AUTO Key = 900 # nwmgr -s -A key=900,mode=LACP_AUTO -I 2 -S apa lan2 new values: Mode = LACP_AUTO Key = 900 2. Create VLANs 333 and 334 over lan902. Enter: # nwmgr -a -S vlan -A vlanid=333, ppa=902 VLAN interface lan5000 successfully configured.
E Switch configuration information This appendix provides some information on how to configure the following switches for use with HP APA: • Cisco • HP Procurve See your switch documentation for complete information.
Last input 00:00:23, output 00:00:01, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/0 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 9273 packets input, 1459338 bytes, 0 no buffer Received 8908 broadcasts (8908 multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 8908
Ctrl+z Switch1(config)#interface port-channel 7 Switch1(config-if)#no shutdown Switch1(config-if)#end 1 Enter configuration commands, one per line. End with Ctrl+z or end.
Displaying more LACP information cisco2#show Flags: S F A - lacp 1 Device Device Device neighbor is requesting Slow LACPDUs is requesting Fast LACPDUs is in Active mode P - Device is in Passive mode Channel group 1 neighbors Partner's information: Port Gi1/0/5 Gi1/0/13 Flags SA SA LACP port Priority Dev ID 0 d4c9.ef06.945e 0 d4c9.ef06.
Port | Name Type | Group Type ---+---------------------------------+-------14 SFP+SR | Trk2 LACP 15 SFP+SR | Trk2 LACP Displaying a Port in a link aggregation HP-E6600ml-24XG(config)# show interface brief 14 Status and Counters - Port Status | Intrusion MDI Flow Bcast Port Type | Alert Enabled Status Mode Mode Ctrl Limit ------- --------- + --------- ------- ------ ---------- ---- ---- ----14-Trk2 SFP+SR | No Yes Up 10GigFD NA off 0 HP-E6600ml-24XG(config)# show interface 14 Status and Counters - Port Coun
Port | Name Type | Group Type ---- + -------------------------------- --------- + ------ -------- 102 Switch configuration information
Glossary A administrative key An integer value that determines which network physical ports can be aggregated into a common LACP link aggregate. The key must match the key of the desired aggregate that the user wants the port to join aggregate A group. For APA, a group of up to eight ports (32 ports for LACP aggregates) makes one link aggregate. There can be 50 link aggregates per computer. aggregation See aggregate. APA Auto Port Aggregation ARP Address Resolution Protocol.
MANUAL The default mode of port configuration. Can be performed by using SMH (preferred) or by editing two configuration files. MIB Management Information Base N network adapter A network device which has one or more network physical ports. network physical port The communications channel formed when you attach a network cable between a specific network port (adapter card) and a LAN device. P PAgP See Port Aggregation Protocol.
Index aggregate instance number, 25 algorithm LB_IP, 26 LB_MAC, 26 LB_PORT, 26 load balancing, 9 APA Main page, 12 application hang (failover group), 67 hang (FEC_AUTO mode), 62 hang (LACP_AUTO mode), 57 resetting with nwmgr command, 47 dead count specifying in lanconfig.
editing for APA configuration, 85–86 hp_apaconf, 31, 77–79 hp_apaportconf, 31, 79–80 netconf, 87 file access verifying (failover group), 67 verifying (FEC_AUTO mode), 61 verifying (LACP_AUTO mode), 56 FIRST_APA_PORT, 35 FIRST_LACP_PORT, 35 G global parameter changing, 35 default port mode, 35 LACP SYSID mode, 35 LACP timeout, 35 maximum link aggregates, 35 Use syslog, 35 group see failover group group capability, 78 and multiple link aggregates, 26 specifying in hp_apaconf file, 78 specifying in hp_apaport
specifying in hp_apaconf file, 78 LB_PORT algorithm, 26 link aggregate and TSO, 10 and VLAN, 92 configuring, 27 configuring by editing files, 85–86 configuring FEC_AUTO mode by editing files, 85–86 configuring IP address, 30 configuring LACP_AUTO mode by editing files, 85–86 configuring MANUAL mode by editing files, 85–86 creating, 27 creating with nwmgr command, 46 deleting, 32 description, 8 displaying details, 34 in failover groups, 22 including in failover group, 9 maximum number of, 35 modifying, 32 no
verifying ready in failover group, 65 verifying UP in failover group, 64 port aggregation statistics, 37 port cost, 26 port mode, 35 port priority, 26 PRIMARY, 82 priority-based failover comparison with proactive failover, 9 proactive failover, 25 configuration example, 90 description, 9 problem gathering information, 71 reporting to HP, 71 R rapid ARP specifying in lanconfig.ascii file, 83 specifying on configuration worksheet, 27 rapid ARP count specifying in lanconfig.
