Using HP Auto Port Aggregation (APA)

HP Systems Networking
for HP APA versions B.11.11.07, B.11.00.16, and B.10.20.05

Manufacturing Part Number : J4240-90016 E0302

U.S.A. Copyright 1999 - 2002 Hewlett-Packard Company.

Legal Notices
The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and tness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty. A copy of the specic warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Ofce. Use of this manual and exible disk(s) or tape cartridge(s) supplied for this pack is restricted to this product only. Additional copies of the programs may be made for security and back-up purposes only. Resale of the programs in their present form or with alterations, is expressly prohibited. Copyright Notices. copyright 1999-2002, Hewlett-Packard Company, all rights reserved. Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws. Trademark Notices Cisco, Catalyst, and Fast EtherChannel are registered trademarks of Cisco Systems Incorporated.

Contents
1. What is HP Auto Port Aggregation?
HP Auto Port Aggregation Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of APA and LAN Monitor Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported LAN Cards and Functions: HP-UX 11.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported LAN Cards and Functions: HP-UX 10.20 Only . . . . . . . . . . . . . . . . . . . . . . HP APA Conguration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enterprise Intranet Client/Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet or Large Enterprise Environments Using Routers . . . . . . . . . . . . . . . . . . . . . Server to Server (Back to Back) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hot Standby - High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server to Server with Switch (not recommended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Monitor Conguration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Monitor Failover Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Monitor Failover Group Using Link Aggregations to Increase Bandwidth . . . . . LAN Monitor with FDDI or Token Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 14 17 19 20 21 22 24 26 30 31 33 34 36 38 40

2. Overview of Installation and Conguration

Prepare to install the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the HP APA software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Your HP APA Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Choose Conguration Method: SAM or Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Port Aggregation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Default Conguration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APA Parms for Link Aggregates hp_apaconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APA and LAN Monitor Parms for Physical Ports hp_apaportconf . . . . . . . . . . . . 42 43 44 46 48 49 49 53

3. Conguring APA Using SAM

Conguring HP APA Using SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Port Aggregation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conguring an FEC_AUTO Mode Link Aggregate . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using SAM to Congure a MANUAL Mode Link Aggregate . . . . . . . . . . . . . . . . . . . . 56 56 57 67

4. Conguring APA by Editing Files

Editing Conguration Files for All APA Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Edit Files for MANUAL, FEC, or LACP Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 MANUAL port conguration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 3

Contents
FEC_AUTO port conguration mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LACP port conguration mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use of /sbin/init.d/hpapa stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify Status of the Link Aggregates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify Status of a Physical Port (HP-UX 11.0 and 11i Only). . . . . . . . . . . . . . . . . . . . . 80 81 82 83 85

5. What is LAN Monitor?

LAN Monitor Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Monitor Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conguring LAN Monitor Failover Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conguration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Binary File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Monitor Conguration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lanqueryconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lanapplyconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lancheckconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . landeleteconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 88 88 94 96 97 97 98 98 98

6. Using ServiceGuard with HP APA

Requirements for Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

7. Troubleshooting HP Auto Port Aggregation (APA) Software

Troubleshooting Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What Happens during Start Up? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAC Addresses for Link Aggregates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic Flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 1: Network Level Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 2: Network Physical Port Connections/LED Test . . . . . . . . . . . . . . . . . . Flowchart 3: Network Physical Port Conguration Test . . . . . . . . . . . . . . . . . . . . . Flowchart 4: Network Physical Port Conguration Test . . . . . . . . . . . . . . . . . . . . . Flowchart 4A: Network Physical Port Conguration Test . . . . . . . . . . . . . . . . . . . Flowchart 5: Link Aggregate Conguration Test . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 5A: Manual Conguration Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 5B: PAgP Congurations Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 5C: LAN Monitor Conguration Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 5D: LACP Conguration Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 104 105 106 107 110 113 117 124 127 130 136 138 143 148

Contents
Flowchart 6: Network Conguration Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 7: ARP Verication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 8: Link Level Loopback Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 9: Transport Level Loopback Test (using ARPA) . . . . . . . . . . . . . . . . . . Flowchart 10: Bridge/Gateway Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Known Problems and Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP 9000 T-600 (T-class server). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Known Installation Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Known Problems with Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the lanadmin Command for Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks You Can Perform with the lanadmin Command . . . . . . . . . . . . . . . . . . . . . . lanadmin Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using lanadmin from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using lanadmin Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 156 158 161 163 165 165 165 165 167 167 168 171 173

A. HP Auto Port Aggregation (APA) Statistics

HP Auto Port Aggregation Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Interface Status Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RFC 1213 MIB II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Link Aggregate Characteristics Using lanscan. . . . . . . . . . . . . . . . . . . . . . . . . . lanscan Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 181 182 185 185

B. Load Balancing and Data Flow Algorithms

Supported Load Balancing and Data Flow Algorithms . . . . . . . . . . . . . . . . . . . . . . . . Packet Ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Balancing Algorithm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Flow Distribution Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 191 192 193

C. HP Auto Port Aggregation (APA) Resources

HP-UX Manual Reference Pages (man pages) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contacting Your HP Representative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What Manuals are Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Product Numbers and Filesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 198 199 201 203 204

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Contents

Tables
Table 1-1. APA and LAN Monitor Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Table 1-2. Minimum Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Table 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Table 7-2. Flowchart Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Table 7-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Table 7-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Table 7-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Table A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Table A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Table A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Table A-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Table A-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Tables

Figures
Figure 1-1. Enterprise Intranet Client/Server Environment . . . . . . . . . . . . . . . . . . 24 Figure 1-2. No Switch between Router and Server . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figure 1-3. Switch between Router and Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Figure 1-4. Server to Server (Back to Back) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Figure 1-5. Hot Standby - High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Figure 1-6. Server to Server with Switch (not recommended). . . . . . . . . . . . . . . . . . 33 Figure 1-7. LAN Monitor Failover Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Figure 1-8. LM Failover Group Using Link Agg to Increase Bandwidth . . . . . . . . . 38 Figure 1-9. LAN Monitor with FDDI or Token Ring . . . . . . . . . . . . . . . . . . . . . . . . . 40 Figure 3-1. Displaying Link Aggregates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Figure 3-2. Conguring Link Aggregates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Figure 3-3. Link Aggregate Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Figure 3-4. Network Physical Ports Supporting APA . . . . . . . . . . . . . . . . . . . . . . . . 61 Figure 3-5. Modify Network Physical Port Attributes . . . . . . . . . . . . . . . . . . . . . . . . 62 Figure 3-6. Example of Congured Link Aggregates . . . . . . . . . . . . . . . . . . . . . . . . . 63 Figure 3-7. Status of Congured Link Aggregate is UP . . . . . . . . . . . . . . . . . . . . . . 64 Figure 3-8. Conguring Link Aggregates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Figure 3-9. Link Aggregate with Congured IP Address. . . . . . . . . . . . . . . . . . . . . . 66 Figure 3-10. Choices in List Pulldown are Link Aggregates and Network Physical Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Figure 3-11. Network Physical Ports Supporting APA . . . . . . . . . . . . . . . . . . . . . . . 69 Figure 3-12. Modify Network Physical Port Attributes . . . . . . . . . . . . . . . . . . . . . . . 70 Figure 3-13. Display Link Aggregates to Congure . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Figure 3-14. Conguring Link Aggregates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Figure 3-15. Link Aggregate Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Figure 3-16. Adding Ports to or Deleting Ports from Link Aggregate. . . . . . . . . . . . 73 Figure 3-17. Adding Ports to or Deleting Ports from Link Aggregate. . . . . . . . . . . . 74 Figure 3-18. Congured Link Aggregates Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Figure 3-19. Link Aggregate Displays with Status UP . . . . . . . . . . . . . . . . . . . . . . . 76 Figure 7-1. Flowchart 1: Network Level Loopback Test . . . . . . . . . . . . . . . . . . . . . 111 Figure 7-2. Flowchart 2: Network Physical Port Connections/LED Test . . . . . . . . 115 Figure 7-3. Flowchart 3: Network Physical Port Conguration Test . . . . . . . . . . . 118 Figure 7-4. Flowchart 4: Network Physical Port Conguration Test . . . . . . . . . . . 125 Figure 7-5. Flowchart 4A: Network Physical Port Conguration Test . . . . . . . . . . 127 Figure 7-6. Flowchart 5: Link Aggregate Conguration Test . . . . . . . . . . . . . . . . . 131

Figures
Figure 7-7. Flowchart 5A: Manual Conguration Test . . . . . . . . . . . . . . . . . . . . . . Figure 7-8. Flowchart 5B: PAgP Conguration Test . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-9. Flowchart 5C: LAN Monitor Conguration Test. . . . . . . . . . . . . . . . . . Figure 7-10. Flowchart 5D: LACP Conguration Test. . . . . . . . . . . . . . . . . . . . . . . Figure 7-11. Flowchart 6: Network Conguration Test . . . . . . . . . . . . . . . . . . . . . . Figure 7-12. Flowchart 7: ARP Verication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-13. Flowchart 8: Link Level Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-14. Flowchart 9: Transport Level Loopback Test (using ARPA). . . . . . . . Figure 7-15. Flowchart 10: Bridge and Gateway Loopback Test . . . . . . . . . . . . . . . 136 139 143 149 153 156 158 161 163

10

What is HP Auto Port Aggregation?

Chapter 1

11

What is HP Auto Port Aggregation? HP Auto Port Aggregation Features

HP Auto Port Aggregation Features

Link Aggregates, often called trunks, provide a logical grouping of 2 or more physical ports into a single Fat-Pipe with a single IP address. Two primary features are automatic link failure detection and recovery as well as optional support for load balancing of network trafc across all of the links in the aggregation. This allows you to build large bandwidth logical links into the server that are highly available and completely transparent to the client and server applications. APA on HP-UX 11.0 and 11i supports Fast and Gigabit Ethernet with automatic fault detection and recovery as well as load balancing of network trafc, while APA on HP-UX 10.20 only supports the automatic link failure detection and recovery feature. HP-UX 11.0 and 11i-based HP APA link aggregates will interoperate with switches and routers using: Ciscos proprietary Fast EtherChannel (FEC/PAgP) technology. IEEE 802.3ad link aggregation control protocol (LACP). Manually congured port trunks.

FDDI and Token Ring links, as well as Fast and Gigabit Ethernet, can also be congured as LAN Monitor failover groups on both HP-UX 10.20 and 11.0, but with no load balancing of network trafc. This enables you to use APA throughout their environment to provide Single System High Availability for all networking components. To summarize, APA offers you a comprehensive solution to create lightning fast and highly available network server connections with minimal IT support costs. APA enables this with four key benets: Automatic link failure detection and recovery in case of network failures. A link aggregate will continue to operate as long as there is at least one port operating. Scalable high performance link aggregates using Fast or Gigabit Ethernet and APA's efcient Load Balancing Algorithms. Supported load balancing algorithms include: IP-based Server-to-Router. Port-based Server-to-Server.

12

Chapter 1

What is HP Auto Port Aggregation? HP Auto Port Aggregation Features MAC-based Server-to-Switch. Fault Management and Isolation with HP's MIB Monitor and Nettl logging facilities. Lower IT costs with automated conguration and management tools using the IEEE 802.3ad standard and HP's System Administration GUI (SAM)

Chapter 1

13

What is HP Auto Port Aggregation? Summary of APA and LAN Monitor Capabilities

Summary of APA and LAN Monitor Capabilities

The following table summarizes the capabilities of APA and LAN Monitor. Table 1-1 APA and LAN Monitor Features HP APA (on HP-UX 11.x) in FEC_AUTO, LACP_AUTO, MANUAL1 Modes Min# of Ports / LinkAgg Max# of Ports / LinkAgg Primary Ports / LinkAgg Standby Ports / LinkAgg Max# of LinkAggs / System Load Balancing (LB) or Hot Standby (HS) MIB Monitor Support FEC_AUTO (2) LACP_AUTO (2) MANUAL (1) FEC_AUTO (4) MANUAL (4) LACP_AUTO(32) N/A HP APA (on HP-UX 11.x) in LAN_MONITOR Mode 2

LAN Monitor (HP-UX 10.20)

Integration with MC/SG in MANUAL1 and FEC_AUTO Modes Only 2

32

32

Min(2) Max(4)

N/A

31

31

Min(1) Max(3)

50

50

50

FEC_AUTO (LB) LACP_AUTO(LB) MANUAL (Either) Yes

LB2 (Ethernet only) and HS Yes

HS only (no LB)

LB2 (Ethernet only) and HS Yes

Yes

14

Chapter 1

What is HP Auto Port Aggregation? Summary of APA and LAN Monitor Capabilities Table 1-1 APA and LAN Monitor Features (Continued) HP APA (on HP-UX 11.x) in FEC_AUTO, LACP_AUTO, MANUAL1 Modes BUSES PCI, HSC, HP-PB3, core100/1000BT HP APA (on HP-UX 11.x) in LAN_MONITOR Mode PCI, HSC, HP-PB3, Core100BT PCI, HSC, HP-PB, Core10/100/1000 BT 100BT, Gigabit, FDDI, Token Ring5

LAN Monitor (HP-UX 10.20)

Integration with MC/SG in MANUAL1 and FEC_AUTO Modes Only

PCI, HSC, HP-PB3, Core100/ 1000BT

LINKS4

100BT, Gigabit

100BT, Gigabit, FDDI, HP-PB Token Ring5 No All Types

100BT, Gigabit (also Token Ring & FDDI when MC/SG will coexist with LAN Monitor; Future Feature) Yes HP, Cisco, 3COM (Hot Standby Mode works with all types of switches/hubs) 100 (11.0), 900 (11i) A.11.09 Edit les

Workstation Support Switches/ Hubs

Yes HP, Cisco, 3COM

Yes All Types

Start PPA# MC/SG Version SAM / Edit

100 (11.0), 900 (11i) A.11.09 SAM/Edit les

100 (11.0), 900 (11i) Future Feature lan*conf commands

90 No support lan*conf commands

Chapter 1

15

What is HP Auto Port Aggregation? Summary of APA and LAN Monitor Capabilities Table 1-1 APA and LAN Monitor Features (Continued) HP APA (on HP-UX 11.x) in FEC_AUTO, LACP_AUTO, MANUAL1 Modes Instant Ignition Full and Half-Duplex6 Yes Yes HP APA (on HP-UX 11.x) in LAN_MONITOR Mode Yes Yes

LAN Monitor (HP-UX 10.20)

Integration with MC/SG in MANUAL1 and FEC_AUTO Modes Only N/A Yes

No Yes

1. MANUAL mode: can be Load Balancing or Non-Load Balancing Load Balancing: MAC, IP, or LB_PORT algorithm . Non-Load Balancing: Hot Standby mode.

MC/ServiceGuard does not support LACP_AUTO mode link aggregates. 2. Load Balancing is congurable on Ethernet links only. Hot Standby is the only choice for FDDI and Token Ring. Load Balancing is for outbound trafc only. 3. HP-PB 100BT adapters cant be mixed with other non-HP-PB 100BT adapters. 4. Links must be of the same speed and type (100Base-T, 1000Base-T, Token Ring, or FDDI). 5. There is no PCI Token Ring on HP-UX 10.20 6. You cannot reset the speed, duplexity, or MTU size over a link aggregate.

16

Chapter 1

What is HP Auto Port Aggregation? Required Software

Required Software
The HP 9000 can be running either HP-UX 10.20, HP-UX 11.0 or 11i. Please refer to Known Problems and Workarounds for any patches relating to HP-UX 11i-based systems. Table 1-2 Minimum Patches Driver 10/100BT PCI 1-port 100BT (RJ45), (btlan5) PCI 1-port 100BT (AUI,BND,RJ45) (btlan6) PCI 4-port 100BT (btlan) PCI 100BT/SCSI Combo Card (btlan3) PHNE_20892 N/A PHNE_20422 PHNE_23195 (800) PHNE_22405 (700) PHNE_24006 PHNE_22245 PHNE_214007 HP-UX 11.0 Additional Core Enhancement rel of January 2000 HP-UX 11.0 Additional Core Enhancement rel of January 2000 *PHNE_22461 PHNE_23982 10.20 11.0

Core PCI 10/100BT (btlan3)

PHNE_23195 (800) PHNE_22405 (700)

EHSC/HSC 1-port, 2-port 100BT (btlan4) HP-PB 10/100BT (btlan1) Gigabit PCI 1000SX (gelan) PCI 1000BT (gelan) EHSC/HSC 1000SX (gelan)

PHNE_22216 PHNE_23921

March 2000 release N/A March 2000 release

March 2000 release N/A March 2000 release

Chapter 1

17

What is HP Auto Port Aggregation? Required Software Table 1-2 Minimum Patches (Continued) Driver FDDI PCI FDDI (fddi4) EHSC/HSC FDDI (fddi3) HP-PB FDDI (fddi) Token Ring PCI Token Ring HP-PB Token Ring DLPI/LANC DLPI/LANC (lan_dlpi.c, lanc*) *PHNE_23862 (800) *PHNE_23863 (700) *PHNE_24413 June 2000 release June 2000 release June 2000 release June 2000 release June 2000 release PHNE_20010 PHNE_24024 June 2000 release March 2000 release March 2000 release 10.20 11.0

*Required patch.

IMPORTANT

The patches must be in place before installing the HP APA software. Absence of the latest core LAN patch can cause the following behavior: Release of April 1999: Installation of the product will fail. Release of June 1999 and after: Installation of the product will succeed, but it will not initialize. When the patch is installed, it will cause the system to reboot. Only then will the product initialize and become usable.

18

Chapter 1

What is HP Auto Port Aggregation? Supported Switches

Supported Switches
The following switches have been certied to work with HP Auto Port Aggregation software. Other switches that support manual trunking may also work with HP APA. 3Com Corebuilder and SuperStack All Cisco Catalyst series HP ProCurve Foundry Alteon

NOTE

Hot Standby mode and LAN Monitor mode are supported with all switches.

Chapter 1

19

What is HP Auto Port Aggregation? Supported LAN Cards and Functions: HP-UX 11.x

Supported LAN Cards and Functions: HP-UX 11.x

HP-UX 11.x-based HP APA supports the following network adapter cards: All Hewlett-Packard HP-PB, HSC, and PCI 10/100Base cards (both FX and TX). All Hewlett-Packard HSC and PCI 1000Base cards (both Base-T and SX). HP-PB and PCI Token Ring (LAN Monitor only). HP-PB, HSC, and PCI FDDI (LAN Monitor only).

HP-UX 11.x-based HP APA supports the following functions: HP APA on HP-UX 11.x supports a total of 50 LinkAggs per server. HP APA on HP-UX 11.x supports the following maximum number of ports per LinkAgg; PAgP and Manual mode 4. LACP and LAN Monitor mode 32. System Administration Manager (SAM) is supported on HP-UX 11.x only.

20

Chapter 1

What is HP Auto Port Aggregation? Supported LAN Cards and Functions: HP-UX 10.20 Only

Supported LAN Cards and Functions: HP-UX 10.20 Only

HP-UX 10.20 based HP APA supports the following network adapter cards: HSC 10/100Base-TX or FX and HP-PB 10/100Base-TX. PCI 1000Base-T HSC 1000Base-SX. HSC and HP-PB FDDI. HP-PB Token Ring (there is no HP-UX 10.20-based PCI Token Ring).

HP-UX 10.20-based HP APA supports the following functions: HP APA on HP-UX 10.20 supports a total of 5 LinkAggs per server and up to 32 ports per LinkAgg. HP APA on HP-UX 10.20 only supports the LAN Monitor mode. PAgP and Manual mode are not supported on HP-UX 10.20.

Chapter 1

21

What is HP Auto Port Aggregation? HP APA Conguration Examples

HP APA Conguration Examples

Here are some points to remember when conguring HP APA: HP APA combines two to four physical link ports into one logical aggregation of links when using FEC_AUTO or MANUAL link aggregation. This gives the link aggregation a theoretical bandwidth of four times that of a single physical link. When using an LACP_AUTO link aggregation, as many as 32 physical links may be used in a link aggregation. 100BT or Gigabit devices may be used in the link aggregation. However, all the devices in the link aggregation must be of one type, 100BT or Gigabit. And the physical devices in the link aggregation must be congured for the same speed and duplex. (Note: EISA 100BT devices are not supported.) The link aggregation has one or more IP addresses assigned to it in the /etc/rc.cong.d/netconf le. The physical ports in the link aggregation will use the same MAC address. HP APA distributes the outbound network trafc across the physical links in the link aggregation using a load balancing algorithm. Effective APA load balancing requires many simultaneous, active client connections. See Figure 1-1 for a good example. It is the connections that are distributed across the physical links. One client connection will have its trafc sent on one physical link. The connection is dened by the load balancing algorithm. The link partners (switches, routers, or remote servers) completely control inbound load balancing. There are three load balancing algorithms from which to choose: MAC-address-based-, IP-address-based-, and TCP/UDP-port-address-based load balancing algorithms. See Appendix B: Load Balancing and Data Flow Algorithms for more information. HP APA link aggregations provide for migrating the network trafc on a failed physical link in the aggregation to the remaining operational links in the aggregation.

22

Chapter 1

What is HP Auto Port Aggregation? HP APA Conguration Examples The link partner (the switch, router, server) connected to the link aggregation may inhibit the usefulness of HP APA in some environments. See the following examples.

The following examples show some supported and unsupported uses for HP APA based on the points above.

Chapter 1

23

What is HP Auto Port Aggregation? Enterprise Intranet Client/Server Environment

Enterprise Intranet Client/Server Environment

Enterprise client/server environments are good candidates for HP APA link aggregations. Figure 1-1 Enterprise Intranet Client/Server Environment

Points for Figure 1-1: 24 Chapter 1

What is HP Auto Port Aggregation? Enterprise Intranet Client/Server Environment Requires a switch capable of trunking/load balancing. Many clients produce many connections. This makes effective use of the HP APA outbound network trafc distribution algorithms. HP APA's MAC address based load balancing algorithm would be a good choice. The IP address and TCP/UDP port address load balancing algorithm would also work effectively in this conguration. The switch typically provides good inbound trafc distribution. Most switches use the data packet's source MAC address, or a combination of the packet's source and destination MAC addresses, to provide inbound load balancing. Depending on the network trafc bandwidth requirements, two to four 100BT interfaces or two to four Gigabit interfaces can be used in an FEC link aggregation. With LACP, up to 32 interfaces can be used in the link aggregation. This allows for bandwidth scalability as network loads increase as the organization grows.

Chapter 1

25

What is HP Auto Port Aggregation? Internet or Large Enterprise Environments Using Routers

Internet or Large Enterprise Environments Using Routers

HP APA link aggregation can be successfully used in certain environments employing routers. Care must be taken because a particular router may not have a load balancing capability. Additionally, switches employed between the server employing HP APA and the

26

Chapter 1

What is HP Auto Port Aggregation? Internet or Large Enterprise Environments Using Routers router inject another level of complexity that should be analyzed before determining the environment is a candidate for HP APA link aggregations. Figure 1-2 No Switch between Router and Server

Points for Figure 1-2: (No switch between router and server) Assumes the router or switching router connected to the server provides trunking/load balancing using an IP address based load balancing algorithm.

Chapter 1

27

What is HP Auto Port Aggregation? Internet or Large Enterprise Environments Using Routers Assumes there will be many TCP/UDP client connections. The HP APA IP address based load balancing algorithm would provide effective outbound network trafc load balancing. So would the TCP/UDP port address based algorithm. The MAC address based algorithm should NOT be used since all packets arriving at the server would contain the same source and destination MAC addresses.

Figure 1-3

Switch between Router and Server

Points for Figure 1-3: (Switch between router and server) The switch in the conguration shown in Figure 1-3 may present problems. Switches typically use a MAC address based load balancing algorithm. This may make the switch a bottleneck point since the packets from the router and from the server will contain

28

Chapter 1

What is HP Auto Port Aggregation? Internet or Large Enterprise Environments Using Routers the same source and destination MAC addresses, thus defeating the load balancing algorithm for both inbound and outbound data at the server. This may be acceptable if the load balancing of inbound trafc to the server is not a concern and the link between the switch and the router has greater bandwidth capacity that the server's link aggregation. Example: the server's link aggregation is composed of 100BT links and the link between the switch and the router is a Gigabit link.

Chapter 1

29

What is HP Auto Port Aggregation? Server to Server (Back to Back)

Server to Server (Back to Back)

Server to server aggregations can be accomplished by directly connecting the physical ports in one server's link aggregation to the physical ports in the other server's link aggregation. Figure 1-4 Server to Server (Back to Back)

Points for Figure 1-4: This conguration requires that there be many TCP/UDP client connections between the servers for load balancing to be effective. HP APA's TCP/UDP port based load balancing algorithm should be used. Depending on the network trafc bandwidth requirements, two to four 100BT interfaces or two to four Gigabit interfaces can be used in an FEC link aggregation. With LACP, up to 32 interfaces can be used in the link aggregation. This allows for bandwidth scalability as network loads increase as the organization grows.

30

Chapter 1

What is HP Auto Port Aggregation? Hot Standby - High Availability

Hot Standby - High Availability

HP APA Hot Standby mode link aggregations provide high availability network access via a primary link and standby link. Figure 1-5 Hot Standby - High Availability

Points for Figure 1-5: The Hot Standby primary link carries network trafc until it or its link partner fails. In that event the standby link takes over the responsibility for delivering network trafc. If the primary is congured with a higher port priority than the standby, then when it recovers it will resume being the active link delivering the network trafc. If the port priorities are the same, the standby link will continue as the active link. The primary and standby links must both be the same type of device, 100Base-T or Gigabit. Hot Standby link aggregations can be connected to any switch or hub.

Chapter 1

31

What is HP Auto Port Aggregation? Hot Standby - High Availability Dual switches/hubs as used in Figure 1-5 are not required. But dual switches/hubs provide a more reliable network environment by removing single points of failure. Both switches/hubs must be on the same subnet.

32

Chapter 1

What is HP Auto Port Aggregation? Server to Server with Switch (not recommended)

Server to Server with Switch (not recommended)

A server to server HP APA link aggregation conguration with a switch between the servers will not work as intended. Figure 1-6 Server to Server with Switch (not recommended)

Points for Figure 1-6: The switch will nullify any load balancing of network trafc provided by HP APA. The switch will use a MAC address based load balancing algorithm. Since the servers' link aggregations will have xed MAC addresses, the switch will not load balance, and thus will only transmit data on one physical link.

Chapter 1

33

What is HP Auto Port Aggregation? LAN Monitor Conguration Examples

LAN Monitor Conguration Examples

Points to remember: LAN Monitor failover groups are the same as HP APA Hot Standby link aggregates except for some additional features: LAN Monitor periodically exchanges APA packets between the links making up the failover group. This allows for better detection of non-operational links in the failover group. Therefore a successful linkloop between the devices is a requirement for conguration. LAN Monitor is congured with LAN Monitor conguration commands. See the chapter What is LAN Monitor? for details. SAM is not used to congure LAN Monitor failover groups. FDDI or Token Ring devices may be used in the failover group. Combines 2 to 32 physical link ports into one failover group. One port will be the primary port, and the others will be standby ports. Network trafc will be sent and received on the primary port (the port with the highest HP APA port priority). In the case where it or its link partner fails, the trafc will be migrated to one of the standby ports. When the primary port link recovers, the network trafc will be migrated back to the primary port. Sometimes, it is desirable to have the network trafc remain on the standby after the failure and recovery of the primary. To achieve this, set the HP APA port priorities the same for all ports in the failover group. 100BT or Gigabit devices may be used in the failover group. Additionally, FDDI or Token Ring devices may be used in the failover group. However, all the devices in the failover group must be of one type, 100BT, Gigabit, FDDI, or Token Ring. The failover group has one or more IP addresses assigned to it. The physical ports in the link aggregation do not share a common MAC address. LAN Monitor supports the use of an HP APA link aggregation as a device in the failover group. This allows for increased bandwidth and load balancing in a failover group.

34

Chapter 1

What is HP Auto Port Aggregation? LAN Monitor Conguration Examples The following examples show some uses for LAN Monitor failover groups based on the points above.

Chapter 1

35

What is HP Auto Port Aggregation? LAN Monitor Failover Group

LAN Monitor Failover Group

LAN Monitor failover groups provide high availability network access via a primary link and standby link. Figure 1-7 LAN Monitor Failover Group

Points for Figure 1-7: Dual switches/hubs as used in Figure 1-7 are not required. But dual switches/hubs provide a more reliable network environment by removing single points of failure. If two switches/hubs are used, then there must be a data path between them allowing them to be on the same subnet. A linkloop between the devices in the failover group is required for successful conguration and operation of the failover group. LAN Monitor failover groups can be connected to any switch or hub.

36

Chapter 1

What is HP Auto Port Aggregation? LAN Monitor Failover Group The failover group primary link carries network trafc until it or its link partner fails. In that event the standby link takes over the responsibility for delivering network trafc. When the primary link recovers it will resume being the active link delivering the network trafc. The primary and standby links must both be the same type of device, 100BT, Gigabit, FDDI, or Token Ring.

Chapter 1

37

What is HP Auto Port Aggregation? LAN Monitor Failover Group Using Link Aggregations to Increase Bandwidth

LAN Monitor Failover Group Using Link Aggregations to Increase Bandwidth

To increase the network bandwidth of a LAN Monitor failover group one can use link aggregations as the primary and standby devices. Figure 1-8 LM Failover Group Using Link Agg to Increase Bandwidth

Points for Figure 1-8: Any HP APA link aggregation, except Hot Standby, can be used as a device in the LAN Monitor failover group. This allows for increasing the bandwidth of the group device through load balancing across the physical links making up the aggregation. The standby link does not have to be a link aggregation. It can be a single physical link of the same type as used in the link aggregation. Dual switches as used in Figure 1-8 are not required. But dual switches provide a more reliable network environment by removing single points of failure. If two switches are used, then there must be a data path between them.

38

Chapter 1

What is HP Auto Port Aggregation? LAN Monitor Failover Group Using Link Aggregations to Increase Bandwidth A linkloop between the devices in the failover group is required for successful conguration and operation of the failover group. LAN Monitor failover groups using link aggregates are restricted to switches supported by HP APA link aggregates. The failover group primary link carries network trafc until it or its link partner fails. In that event the standby link takes over the responsibility for delivering network trafc. When the primary link recovers it will resume being the active link delivering the network trafc. The primary and standby links must both be the same type of device, 100BT or Gigabit.

Chapter 1

39

What is HP Auto Port Aggregation? LAN Monitor with FDDI or Token Ring

LAN Monitor with FDDI or Token Ring

LAN Monitor supports FDDI and Token Ring devices. Figure 1-9 LAN Monitor with FDDI or Token Ring

Points for Figure 1-9: A linkloop between the devices in the failover group is required for successful conguration and operation of the failover group. The failover group primary link carries network trafc until it or its link partner fails. In that event the standby link takes over the responsibility for delivering network trafc. When the primary link recovers it will resume being the active link delivering the network trafc. The primary and standby links must both be the same type of device, FDDI or Token Ring.

40

Chapter 1

Overview of Installation and Conguration

Chapter 2

41

Overview of Installation and Conguration Prepare to install the software

Prepare to install the software

1. Log in to HP-UX server as root. 2. Verify that the /usr/bin, /usr/sbin and /sbin directories are in your PATH using the command: echo $PATH 3. Use the swlist command to verify the HP-UX version. 4. Install any required patches for your system as described in the Required Patches section of the release notes. Use the same steps for patch installation as you do for product installation shown next.

42

Chapter 2

Overview of Installation and Conguration Install the HP APA software

Install the HP APA software

Skip this section if you ordered product option 0D1--preinstallation. 1. To install the software from the installation media, run the swinstall program using the command: swinstall. 2. Select the appropriate Source Depot Type (for example, Local CD, Local tape, Local Directory, Network Directory/CDROM). 3. Select Source Host Name. 4. Select Source Depot Path. If you do not know the exact path you can click the Source Depot Path button and a list of valid choices will be displayed. 5. Highlight the HP APA software: J4240AA (HP-UX 11.0 or 11i) or J5080AA (HP-UX 10.20). 6. Choose Mark for Install from the Actions menu to choose the product to be installed. 7. Choose Install from the Actions menu to begin product installation and display the Install Analysis Window. 8. Activate the OK button in the Install Analysis Window when the Status eld displays a Ready message. 9. Activate the YES button at the Conrmation Window to conrm that you want to install the software. swinstall loads the leset, runs the control scripts for the lesets, and builds the kernel. Estimated time for processing: 3 to 5 minutes. When the status eld indicates Ready, a Note Window opens. Activate the OK button on the Note Window to reboot the system.

Chapter 2

43

Overview of Installation and Conguration Planning Your HP APA Conguration

Planning Your HP APA Conguration

Before conguring HP APA the following information should be determined and gathered: Determine which network physical interfaces installed in the HP 9000 server can be used for the HP APA link aggregation. Only those interfaces supported by HP APA can be used. All 100BT interfaces except the EISA 100BT interfaces are supported. All Gigabit interfaces are supported. Note that the interfaces in a link aggregation must be of the same type: all 100BT devices or all 1000BASE-x devices. All the devices in the link aggregation must be congured for the same speed and duplex. Determine the number of physical interfaces required in the link aggregation. Use present and future bandwidth requirements to determine this number. Determine the mode of the link aggregate, FEC_AUTO, LACP_AUTO, or MANUAL. This is determined by the capabilities of the switch or link partner to which the link aggregate physical interfaces will be connected. The switch or link partner documentation will need to be consulted to verify which modes it supports. If both an automatic and a manual mode are available, it is recommended that the automatic mode be used. Determine the load balancing algorithm to use. LB_MAC, the default, works well in most congurations. Then for each link aggregation to be congured make a list containing: The PPA number of the linkagg (100 will be lan100). The conguration mode of the aggregation (FEC_AUTO, LACP_AUTO, MANUAL). The PPA numbers of the ports that will be in the link aggregation. And for each port:

44

Chapter 2

Overview of Installation and Conguration Planning Your HP APA Conguration The group capability of the port if the link aggregation will use FEC_AUTO mode. This should match the value specied for the group capability of the link aggregate. The easiest way to choose this is to take the ppa number of the linkagg and use it as the group capability. The key of the port if the link aggregation will use LACP_AUTO mode. This should match the value specied for the key of the link aggregate. The easiest way to choose this is to take the ppa number of the link aggregate and use it as the port key. The port's priority if the link aggregation mode will be MANUAL and will use Hot Standby. The port with the highest priority will be the primary port. The load balancing algorithm to use, unless it is a MANUAL link aggregation that is to use Hot Standby. The group capability if the link aggregate will use FEC_AUTO mode. The easiest way to choose this is to take the ppa number of the linkagg and use it as the group capability. The key if the link aggregate will use LACP_AUTO mode. The easiest way to choose this is to take the ppa number of the linkagg and use it as the key. The IP address and subnet mask of the aggregate.

Chapter 2

45

Overview of Installation and Conguration Choose Conguration Method: SAM or Editing

Choose Conguration Method: SAM or Editing

Using the GUI-based system admin manager (SAM) is the recommended method for conguring HP APA. Using SAM produces less errors and saves your data permanently. Conguration doesnt require a reboot to take effect. 1. To permanently save your congurations, you can either: use the GUI-based system admin manager (SAM). To use SAM, refer to the instructions in Conguring APA Using SAM in this document for details, and then do the steps for verifying link aggregates; or edit the conguration les using an editor such as vi. Refer to Conguring APA by Editing Files in this document for instructions on editing the two conguration les for APA and two additional les for LAN Monitor: APA and LAN MONITOR: /etc/rc.cong.d/hp_apaconf and /etc/rc.cong.d/hp_apaportconf LAN Monitor on HP-UX 11.0 and 11i requires the hp_apaportconf plus: /etc/rc.cong.d/netconf and /etc/lanmon/lancong.ascii. 2. If you are conguring more than one of the four, port-conguration modes described here, minimize the number of stops (which can interrupt trafc on existing link aggregates) by editing all conguration les rst. You will then only need to run one series of hplm stop (optional); hpapa stop; hpapa start; hplm start (optional) to activate the link aggregates and (optionally) failover groups.

46

Chapter 2

Overview of Installation and Conguration Choose Conguration Method: SAM or Editing

CAUTION

You can also use the lanadmin command from the HP-UX command line prompt to make temporary changes to APA. However, if you change some variables using the lanadmin command, those changes are not preserved across reboots. See Using the lanadmin Command for Testing for details on the lanadmin command.

Chapter 2

47

Overview of Installation and Conguration Setting Port Aggregation Modes

Setting Port Aggregation Modes

Ports can be aggregated by setting HP APA to any of the following port aggregation modes: Manual Mode Use this mode to congure HP 9000 Link Aggregates if the server connects to a switch that only supports manual conguration. This mode requires the switch to support Link Aggregation. In the event of a link failure, APA automatically migrates the data ow(s) from the failed link to another link in the aggregation Auto w/ PAgP Use this mode when conguring Link Aggregates on the HP 9000 when connected to a switch that supports Ciscos Fast EtherChannel protocol (PAgP). This mode requires the switch to support the PAgP (FEC) protocol. In the event of a link failure, PAgP automatically migrates the data ow(s) from the failed link to another link in the aggregation. Auto w/ LACP Use this mode to automatically aggregate HP 9000 links connected to IEEE 802.3ad (LACP) supported switches. This mode requires the switch to support the LACP protocol. In the event of a link failure, LACP automatically migrates the data ow(s) from the failed link to another link in the aggregation. LAN Monitor Use this mode when conguring fail-over groups on the HP 9000. In the event of a link failure, the LAN Monitor software automatically migrates the data ow from the primary link to one of the standby links in the Link Aggregate. Fail-over groups do not support MC/SG. The mode does not strictly require the switch to support Link Aggregation, although some congurations may require the switch to support Link Aggregation.

After you have installed HP APA, it will be in MANUAL port-conguration mode until you congure it to aggregate eligible ports. Auto aggregation also requires that you congure your switch to enable Ciscos Fast EtherChannel (FEC) or IEEE 802.3ad Link Aggregation Control Protocol (LACP). If your switch only supports manual port conguration, you must also set the server ports to MANUAL mode (the default conguration). Then edit the servers conguration les as explained in this document.

48

Chapter 2

Overview of Installation and Conguration Modifying Default Conguration Parameters

Modifying Default Conguration Parameters

Beginning with the December 2001 release the HP APA default port-conguration mode is set to MANUAL mode; it does not automatically aggregate ports. If you do not modify the default conguration, nothing will happen-- you have to modify and save the conguration by either using SAM or editing the les that are listed here. Refer to Conguring APA Using SAM or Conguring APA by Editing Files to set up or modify these les. SAM does not congure LAN Monitor. HP Auto Port Aggregation uses two conguration les as follows. /etc/rc.cong.d/hp_apaconf This le contains conguration values for link aggregates. /etc/rc.cong.d/hp_apaportconf This le contains conguration values for specic physical ports that are supported by HP APA.

LAN Monitor uses the hp_apaportconf le plus the following les: /etc/rc.cong.d/netconf /etc/lanmon/lancong.ascii

The following subsections describe the congurable parameters in each of these les.

APA Parms for Link Aggregates hp_apaconf

Following are the descriptions of the parameters within the /etc/rc.cong.d/hp_apaconf le.

NOTE

Each of the supported parameters must be set on a specic link aggregate prior to aggregating any physical ports.

HP_APA_MAX_LINKAGGS Sets the maximum number of LinkAggs for the server. The valid range is from 5 to 50. The default value is 50. This value only takes effect after a reboot.

Chapter 2

49

Overview of Installation and Conguration Modifying Default Conguration Parameters HP_APA_DEFAULT_PORT_MODEThe default way to congure link aggregates is now through MANUAL port-conguration mode--formerly it was automatic (FEC_AUTO). Ensure that switch ports and server ports are set to the same trunking mode (MANUAL or AUTO), duplexity, and speed. Disable PAgP or LACP on any switch ports not intended to be used with APA. There are two variables governing the mode of ports: HP_APA_DEFAULT_PORT_MODE in the /etc/rc.cong.d/hp_apaconf le. Sets the default APA conguration mode for all ports. The recommended mode is MANUAL. The APA product is shipped with the entry in the hp_apaconf le set to: HP_APA_DEFAULT_PORT_MODE=MANUAL. HP_APAPORT_CONFIG_MODE in the /etc/rc.cong.d/hp_apaportconf le. Sets the APA conguration mode for a single port. This variable takes precedence. A port's mode will be set to the value of HP_APA_DEFAULT_PORT_MODE, unless its mode is specied using variable HP_APAPORT_CONFIG_MODE. HP_APA_DEFAULT_PORT_MODE sets the mode for all ports but HP_APAPORT_CONFIG_MODE can override it. Example 1: Suppose the conguration mode of a port is not set with HP_APAPORT_CONFIG_MODE and HP_APA_DEFAULT_PORT_MODE is not set. This results in the port's conguration mode being FEC_AUTO. Example 2: Suppose the conguration mode of a port is not set with HP_APAPORT_CONFIG_MODE and HP_APA_DEFAULT_PORT_MODE is set to MANUAL. This results in the port's conguration mode being MANUAL. Example 3: Suppose the conguration mode of a port is set to FEC_AUTO via HP_APAPORT_CONFIG_MODE and HP_APA_DEFAULT_PORT_MODE is set to MANUAL. This results in the port's conguration mode being FEC_AUTO. HP_APA_INTERFACE_NAME Name of link aggregate (lan100, lan101, and so on). HP_APA_LOAD_BALANCE_MODE Denes the Load Balancing mode for the specied link aggregate (HP_APA_INTERFACE_NAME). The supported values are as follows:

50

Chapter 2

Overview of Installation and Conguration Modifying Default Conguration Parameters LB_MAC This algorithm uses a portion of the destination MAC address to determine how data ows are distributed across physical ports in a link aggregate. This option is recommended for Server-to-Switch congurations. LB_IP This algorithm uses a portion of the source and destination IP address to determine how data ows are distributed across physical ports in a link aggregate. This option is recommended for Server-to-Router congurations. LB_PORT This algorithm uses the TCP/UDP source and destination port numbers to distribute trafc across the ports in a Link Aggregate. This algorithm is recommended for use when connecting two HP 9000 servers in a back-to-back conguration. It is now the recommended option for this purpose instead of LB_CPU. The default for HP_APA_LOAD_BALANCE is LB_MAC. HP_APA_GROUP_CAPABILITY FEC_AUTO only. An integer value used to determine which network physical ports can be aggregated into a common PAgP 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 should have different group capabilities. Must match the value of HP_APAPORT_GROUP_CAPABILITY in the /etc/rc.cong.d/hp_apaportconf le. HP_APA_KEY 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 in the same Link Aggregate. Ports going to different link aggregates should have different keys. Must match the value of HP_APAPORT_KEY in the /etc/rc.cong.d/hp_apaportconf le. HP_APA_HOT_STANDBY

Chapter 2

51

Overview of Installation and Conguration Modifying Default Conguration Parameters Congure a Link Aggregate for Hot Standby Mode. This parameter is mutually exclusive with the HP_APA_LOAD_BALANCE parameter. In addition HP_APA_HOT_STANDBY takes precedence over the HP_APA_LOAD_BALANCE parameter. The permissible values are on and off. The Default Is off. For HP APA releases prior to March 2002:

CAUTION

Only use lowercase when specifying on/off for HP_APA_HOT_STANDBY in /etc/rc.cong.d/hp_apaconf. Uppercase will cause errors.

HP_APA_MANUAL_LA Manually set ports for the specied link aggregate. The ports should be specied with PPA numbers. Each port should be separated by a comma (,).

Reserved values The HP_APA_INIT_ARGS are reserved by HP; they are not customer changeable:

Examples: To set the load balancing mode to port based (LB_PORT) on lan100:
HP_APA_INTERFACE_NAME[0]=lan100 HP_APA_LOAD_BALANCE_MODE[0]=LB_PORT HP_APA_HOT_STANDBY[0]=off

To create a manually formed link aggregate having ports with PPAs 2, 3, and 4:

NOTE

Ensure that the server and switch are set to the same mode--MANUAL.

HP_APA_INTERFACE_NAME[1]=lan100 HP_APA_LOAD_BALANCE_MODE[1]=LB_PORT HP_APA_HOT_STANDBY[1]=off HP_APA_MANUAL_LA[1]=2,3,4

52

Chapter 2

Overview of Installation and Conguration Modifying Default Conguration Parameters

APA and LAN Monitor Parms for Physical Ports hp_apaportconf

Following are the descriptions of the parameters within the /etc/rc.cong.d/hp_apaportconf le. HP_APAPORT_CONFIG_MODE Set the conguration mode for a physical port. The supported values are listed below: LACP_AUTO IEEE 802.3ad Link Aggregation Control Protocol (LACP) will be started on the port. FEC_AUTO Ciscos Fast EtherChannel (FEC) will be started on the port. MANUAL Ciscos FEC or IEEE 802.3ad LACP will be disabled on the port, and it must therefore be manually added or removed from a specic link aggregate. This is the default conguration mode for all ports which support the HP APA product. LAN_MONITOR Ciscos FEC or IEEE 802.3ad LACP will be disabled and the port will be used for LAN Monitor aggregates. HP_APAPORT_INTERFACE_NAME Name of physical interface (lan0, lan1, and so on). HP_APAPORT_GROUP_CAPABILITY For FEC_AUTO only. An integer value used to determine which network physical ports can be aggregated into a common PAgP 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 should have different group capabilities. The default group capability is 5. Must match the value of HP_APA_GROUP_CAPABILITY in the /etc/rc.cong.d/hp_apaconf le. HP_APAPORT_PRIORITY Set the port priority for the port. The port priority determines which port in a link aggregate will be the primary interface when the link aggregate is set to hot standby mode (HP_APA_HOT_STANDBY=on). The default port priority is 0.

Chapter 2

53

Overview of Installation and Conguration Modifying Default Conguration Parameters HP_APAPORT_KEY 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 in the same Link Aggregate. Ports going to different link aggregates should have different keys. Must match the value of HP_APA_KEY in the /etc/rc.cong.d/hp_apaconf le. The default administrative key is 0. HP_APAPORT_SYSTEM_PRIORITY For LACP_AUTO only. Set the port system priority for the port specied 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 system priority is 0. Reserved values The HP_APAPORT_INIT_ARGS are reserved by HP; they are not customer changeable: Example: Use the default Group Capability, but set the other values as listed:
HP_APAPORT_INTERFACE_NAME[0]=lan1 HP_APAPORT_CONFIG_MODE[0]=FEC_AUTO

54

Chapter 2

Conguring APA Using SAM

Chapter 3

55

Conguring APA Using SAM Conguring HP APA Using SAM

Conguring HP APA Using SAM

Using the GUI-based system admin manager (SAM) is the recommended method for conguring HP APA. Using SAM produces less errors and saves your conguration data permanently. Conguration doesnt require a reboot to take effect. SAM permanently saves HP APA conguration values in two les: /etc/rc.cong.d/hp_apaconf and /etc/rc.cong.d/hp_apaportconf

Setting Port Aggregation Modes

You can use the System Administration Manager (SAM) to congure HP APA so that it will aggregate ports in any of the following port aggregation modes: FEC or LACP Port Aggregation Modes Manual Port Aggregation Mode

After you have installed HP APA, it will be in MANUAL port-aggregation mode unless you congure it to automatically aggregate eligible ports.

NOTE

HP APA also requires that you congure your switches trunking mode (AUTO or MANUAL) to match the mode being used on the server: Ciscos Fast EtherChannel (FEC), IEEE 802.3ad Link Aggregation Control Protocol (LACP), or MANUAL mode.

NOTE

SAM cannot be used to congure LAN Monitor. Refer to the chapter on Conguring APA by Editing for editing conguration les for all APA modes and the chapter What is LAN Monitor? for conguring LAN Monitor mode.

56

Chapter 3

Conguring APA Using SAM Conguring an FEC_AUTO Mode Link Aggregate

Conguring an FEC_AUTO Mode Link Aggregate

When conguring an automatic link aggregate (FEC_AUTO or LACP_AUTO) with SAM, the link aggregation characteristics are congured rst, followed by the port's modes and characteristics. The following example congures an FEC_AUTO link aggregate. The same process can be used to congure an LACP_AUTO link aggregate by substituting LACP_AUTO for FEC_AUTO, and key for group capability. Log in as root. At the HP-UX system prompt: 1. Type sam 2. Double-click Networking and Communications, and then Auto Port Aggregation. A window like the one in Figure 3-1 appears. The Networking and Communications screen List pulldown menu (Figure 3-1) displays either: Link Aggregates supported by HP APA. This is the list of all available Link Aggregates in the system.

Chapter 3

57

Conguring APA Using SAM Conguring an FEC_AUTO Mode Link Aggregate Network Physical Ports that Support HP APA. This is the list of all physical ports in the system that support HP APA.

Figure 3-1

Displaying Link Aggregates

58

Chapter 3

Conguring APA Using SAM Conguring an FEC_AUTO Mode Link Aggregate 3. Click on the linkagg to be congured. Then from the Actions pulldown menu select the Congure Link Aggregate option. A window similar to Figure 3-2 will appear. Figure 3-2 Conguring Link Aggregates

Chapter 3

59

Conguring APA Using SAM Conguring an FEC_AUTO Mode Link Aggregate 4. Click on the Advanced Options button to get a window similar to Figure 3-3. Figure 3-3 Link Aggregate Advanced Options

5. Verify the correct settings for the load balancing (distribution) algorithm. If required make the necessary changes. 6. If the link aggregation will use the FEC_AUTO mode, then set the group capability for the linkagg. The group capability should be a non-zero number that differs from the group capability of any other linkagg. It should also match the group capability that will be assigned later to the ports belonging in the linkagg. Then click the OK button. Click the OK button in the Congure Link Aggregate window. 7. Select the Network Physical Ports that Support HP APA option from the List pulldown menu. The displayed port conguration mode (column 7 in Figure 3-4) determines the mode for the link aggregation. Note: in Figure 3-4 the conguration mode for the ports

60

Chapter 3

Conguring APA Using SAM Conguring an FEC_AUTO Mode Link Aggregate that support APA is, by default, set to MANUAL mode. Also note: you may need to adjust the horizontal scroll bar to see all the window's elds. Figure 3-4 Network Physical Ports Supporting APA

8. For each port to be congured in the automatic link aggregation, verify that the port's conguration mode is set to the desired mode, FEC_AUTO. Check that the port's group capability matches the group capability that was previously assigned to the link aggregation. If changes are needed proceed to the next step. 9. Highlight the port to congure by clicking on the port designated by its PPA.

Chapter 3

61

Conguring APA Using SAM Conguring an FEC_AUTO Mode Link Aggregate 10. In the Actions pull down menu, select the Modify Network Physical Port Attributes option. You will see a window like the one in Figure 3-5. Figure 3-5 Modify Network Physical Port Attributes

11. In this window, make the necessary changes and click on the OK button.

62

Chapter 3

Conguring APA Using SAM Conguring an FEC_AUTO Mode Link Aggregate 12. Continue with steps 8 through 11 to congure the remaining ports to be in the aggregate. Figure 3-6 shows a sample FEC_AUTO conguration using ports 1 and 2 with group capability of 7. Figure 3-6 Example of Congured Link Aggregates

13. From the List pulldown menu, select the Link Aggregates Supported by HP APA option. A window similar to Figure 3-7 will appear. Note that the linkagg may not have a status of UP since APA and the switch or link partner may not have completed the negotiation required for forming the link aggregation. Continue with the next step in either case.

Chapter 3

63

Conguring APA Using SAM Conguring an FEC_AUTO Mode Link Aggregate

Figure 3-7

Status of Congured Link Aggregate is UP

64

Chapter 3

Conguring APA Using SAM Conguring an FEC_AUTO Mode Link Aggregate 14. Click once again on the link aggregate being congured. Then from the Actions pulldown menu, , select the Congure Link Aggregate option. A window like that in Figure 3-8 will appear. Figure 3-8 Conguring Link Aggregates

Chapter 3

65

Conguring APA Using SAM Conguring an FEC_AUTO Mode Link Aggregate 15. Fill in the desired IP address and subnet mask to be used for the linkagg. Then click on the OK button. A window like that in Figure 3-9 will appear. Figure 3-9 Link Aggregate with Congured IP Address

16. If the linkagg has a status of UP, then conguration is complete. Exit SAM. Verify that the proper ports are congured in the proper link aggregation with the lanscan -q command. 17. If the linkagg is DOWN: If the switch has not been congured, then exit SAM and congure the switch. The APA conguration will have been permanently saved and can be modied later if needed. If the switch has been congured, verify the switch and APA conguration and make the required changes to bring them into agreement. If the link aggregate still does not form correctly, proceed to the troubleshooting section of this guide.

66

Chapter 3

Conguring APA Using SAM Using SAM to Congure a MANUAL Mode Link Aggregate

Using SAM to Congure a MANUAL Mode Link Aggregate

When conguring a manual link aggregate with SAM, the rst step is conguring the ports modes and characteristics, followed by the link aggregate characteristics. Log in as root. At the HP-UX system prompt: 1. Type sam 2. Double-click Networking and Communications, and then Auto Port Aggregation. A window like the one in Figure 3-10 appears. The Networking and Communications screen List pulldown menu (Figure 3-10) displays either: Link Aggregates supported by HP APA. This is the list of all available Link Aggregates in the system.

Chapter 3

67

Conguring APA Using SAM Using SAM to Congure a MANUAL Mode Link Aggregate Network Physical Ports that Support HP APA. This is the list of all physical ports in the system that support HP APA.

Figure 3-10

Choices in List Pulldown are Link Aggregates and Network Physical Ports

3. Select the Network Physical Ports that Support HP APA option from the List pulldown menu. The port conguration mode (shown in column 7 in Figure 3-11) determines the mode for the link aggregate. Note: in Figure 3-11, the conguration mode for the ports that

68

Chapter 3

Conguring APA Using SAM Using SAM to Congure a MANUAL Mode Link Aggregate support APA is, by default, set to MANUAL mode. Also note: you may need to adjust the horizontal scroll bar to see all the window's elds. Figure 3-11 Network Physical Ports Supporting APA

4. For each port to be congured in the manual link aggregate, verify that the port's conguration mode is set to the desired mode, MANUAL. Check that the port's group capability matches the group capability that was previously assigned to the link aggregation. If changes are needed proceed to the next step. 5. Highlight the port to congure by clicking on the port designated by its PPA.

Chapter 3

69

Conguring APA Using SAM Using SAM to Congure a MANUAL Mode Link Aggregate 6. In the Actions pulldown menu, select the Modify Network Physical Port Attributes option. You will see a window like the one in Figure 3-12. Figure 3-12 Modify Network Physical Port Attributes

7. In this window make the necessary changes and click on the OK button. 8. Continue with steps 4 through 7 to congure the remaining ports to be in the aggregate.

70

Chapter 3

Conguring APA Using SAM Using SAM to Congure a MANUAL Mode Link Aggregate 9. To congure the link aggregate characteristics, select the Link Aggregates supported by HP APA option from the List pulldown menu. A window like Figure 3-13 will appear. Figure 3-13 Display Link Aggregates to Congure

10. Click on the link aggregate being congured. Then, from the Actions pulldown menu, select the Congure Link Aggregate option. A window similar to Figure 3-14 will appear.

Chapter 3

71

Conguring APA Using SAM Using SAM to Congure a MANUAL Mode Link Aggregate

Figure 3-14

Conguring Link Aggregates

11. Fill in the desired IP address and subnet mask to be used for the linkagg.

72

Chapter 3

Conguring APA Using SAM Using SAM to Congure a MANUAL Mode Link Aggregate 12. Click on the Advanced Options button to get a window similar to Figure 3-15. Figure 3-15 Link Aggregate Advanced Options

13. Verify the correct settings for Hot Standby and the load balancing (distribution) algorithm. If required make the necessary changes. Then press the OK button. 14. Press the Add or Delete Network Physical Ports button. A window similar to Figure 3-16 will appear.

Figure 3-16

Adding Ports to or Deleting Ports from Link Aggregate

Chapter 3

73

Conguring APA Using SAM Using SAM to Congure a MANUAL Mode Link Aggregate 15. Highlight a port to be included in the link aggregate. Then use the < button to move it into the linkagg. 16. Figure 3-17 shows the result of moving lan1 and lan2 into the linkagg, lan100. Figure 3-17 Adding Ports to or Deleting Ports from Link Aggregate

74

Chapter 3

Conguring APA Using SAM Using SAM to Congure a MANUAL Mode Link Aggregate 17. Click the OK button to see the Congure Link Aggregates window (Figure 3-18) with all the linkagg information lled in. Figure 3-18 Congured Link Aggregates Display

Chapter 3

75

Conguring APA Using SAM Using SAM to Congure a MANUAL Mode Link Aggregate 18. Clicking the OK button brings us back to the original window (Figure 3-19. It now shows the link aggregate lan100 congured as a MANUAL mode linkagg. Figure 3-19 Link Aggregate Displays with Status UP

19. The link aggregate is congured. Congure the next MANUAL mode linkagg, or if none, exit by choosing the Exit option from the File pulldown menu.

76

Chapter 3

Conguring APA by Editing Files

Chapter 4

77

Conguring APA by Editing Files Editing Conguration Files for All APA Modes

Editing Conguration Files for All APA Modes

This chapter is for conguring the three modes associated with port aggregation. To congure LAN Monitor mode, refer to the chapter What is LAN Monitor? in this guide. Beginning with the December 2001 release, HP Auto Port Aggregation (HP APA) is shipped with the default port-conguration mode set to MANUAL. The value in the /etc/rc.cong.d/hp_apaconf le is HP_APA_DEFAULT_PORT_MODE=MANUAL. This allows you to then specify any of the four port-conguration modes before activating the product. For release-specic information, refer to the release notes on your system in /opt/networkdocs or on the worldwide web at: http://www.docs.hp.com. If you are conguring more than one of the four, port-conguration modes described here and in the next chapter, minimize the number of times you have to run hpapa stop (which can interrupt trafc on existing link aggregates) by editing all conguration les rst. You will then only need to run one series of hplm stop (optional); hpapa stop; hpapa start; hplm start (optional) to activate the link aggregates and (optionally) failover groups.

78

Chapter 4

Conguring APA by Editing Files Edit Files for MANUAL, FEC, or LACP Modes

Edit Files for MANUAL, FEC, or LACP Modes

1. Ensure that the switch ports and the HP LAN card ports are set to the same APA (or trunking) mode (MANUAL or AUTO), speed, and duplexity. 2. Run lanadmin interactively if you need to verify that all HP LAN card ports intended for aggregation are connected to the LAN. 3. When numbering the PPAs of your link aggregations, use the following numbers as the starting point: for HP-UX 11i, it is 900; for HP-UX 11.0, it is 100; and for HP-UX 10.20, it is 90.

NOTE

The following examples are for HP-UX 11i only.

MANUAL port conguration mode

Edit the following values in the /etc/rc.cong.d/hp_apaconf le. Example: to put lan1 and lan2 into link aggregate 900 with MAC-based load-balancing: HP_APA_INTERFACE_NAME[0]=lan900 HP_APA_LOAD_BALANCE_MODE[0]=LB_MAC HP_APA_MANUAL_LA[0]=1,2 Edit the following values in the /etc/rc.cong.d/hp_apaportconf le. If this is the rst-time conguration, the CONFIG_MODE is already set to the default of MANUAL: HP_APAPORT_INTERFACE_NAME[0]=lan1 HP_APAPORT_CONFIG_MODE[0]=MANUAL HP_APAPORT_INTERFACE_NAME[1]=lan2 HP_APAPORT_CONFIG_MODE[1]=MANUAL

Chapter 4

79

Conguring APA by Editing Files Edit Files for MANUAL, FEC, or LACP Modes If you are done editing all conguration modes, activate the conguration by typing: /sbin/init.d/hplm stop {optional--for failover groups} /sbin/init.d/hpapa stop and then /sbin/init.d/hpapa start /sbin/init.d/hplm start {optional--for failover groups}

FEC_AUTO port conguration mode

Optional--set load balancing and group capability in the /etc/rc.cong.d/hp_apaconf le. Example: to congure link aggregate 900 with MAC-based load-balancing and a group capability of 10, enter: HP_APA_INTERFACE_NAME[0]=lan900 HP_APA_LOAD_BALANCE_MODE[0]=LB_MAC HP_APA_GROUP_CAPABILITY[0]=10 {*see Note 1} Edit the following values in the /etc/rc.cong.d/hp_apaportconf le. Example: to put lan1 and lan2 into link aggregate 900: HP_APAPORT_INTERFACE_NAME[0]=lan1 HP_APAPORT_GROUP_CAPABILITY[0]=10 {*see Note 1} HP_APAPORT_CONFIG_MODE[0]=FEC_AUTO HP_APAPORT_INTERFACE_NAME[1]=lan2 HP_APAPORT_GROUP_CAPABILITY[1]=10 {*see Note 1} HP_APAPORT_CONFIG_MODE[1]=FEC_AUTO {Note 1: Set the group capability to be the same as that of the link aggregate to which it belongs. Ports going to different link aggregates should have different group capabilities.} If you are done editing all conguration modes, activate the conguration by typing: /sbin/init.d/hplm stop {optional--for failover groups} /sbin/init.d/hpapa stop and then /sbin/init.d/hpapa start /sbin/init.d/hplm start {optional--for failover groups}

80

Chapter 4

Conguring APA by Editing Files Edit Files for MANUAL, FEC, or LACP Modes

LACP port conguration mode

Optional--set load balancing and apaport key in the /etc/rc.cong.d/hp_apaconf le. Example: to congure link aggregate 900 with MAC-based load-balancing and a key of 10, enter: HP_APA_INTERFACE_NAME[0]=lan900 HP_APA_LOAD_BALANCE_MODE[0]=LB_MAC HP_APAPORT_KEY[0]=10 {*see Note 2} Edit the link aggregate, the apaport key, and the conguration mode in the /etc/rc.cong.d/hp_apaportconf le. Example: to put lan1 and lan2 into link aggregate 900: HP_APAPORT_INTERFACE_NAME[0]=lan1 HP_APAPORT_KEY[0]=10 {*see Note 2} HP_APAPORT_CONFIG_MODE[0]=LACP_AUTO HP_APAPORT_INTERFACE_NAME[1]=lan2 HP_APAPORT_KEY[1]=10 {*see Note 2} HP_APAPORT_CONFIG_MODE[1]=LACP_AUTO {Note 2: Set the LACP key to be the same as that of the link aggregate to which it belongs. Ports going to different link aggregates should have different keys.} If you are done editing all conguration modes, activate the conguration by typing: /sbin/init.d/hplm stop {optional--for failover groups} /sbin/init.d/hpapa stop and then /sbin/init.d/hpapa start /sbin/init.d/hplm start {optional--for failover groups}

Chapter 4

81

Conguring APA by Editing Files Use of /sbin/init.d/hpapa stop

Use of /sbin/init.d/hpapa stop

The /sbin/init.d/hpapa stop command does not remove the protocols running on the link aggregate. The hpapa stop command: 1. Clears all link aggregates. 2. Clears LAN_MONITOR fail-over groups but does not remove the binary le. 3. Stops AUTO protocol negotiation on single ports. 4. Does not remove the upper-layer protocols (for example, IP) running over the link aggregate.

82

Chapter 4

Conguring APA by Editing Files Verify Status of the Link Aggregates

Verify Status of the Link Aggregates

Conguration doesnt require a reboot to take effect. HP APA conguration is complete when you can verify which link aggregates have been formed. Depending on your conguration, there may be 0 or more link aggregates congured. To verify which link aggregates have been congured, type: lanscan or lanscan -v for a long listing The column heading titled Hardware Path will contain the value LinkAgg for logical link aggregates. The column heading Hdw State will show the state of the link aggregates. The state should be UP or DOWN. UP indicates that the link aggregation is operational. DOWN indicates that the link aggregate has been initialized by the product but not congured. (HP-UX 11.0 and 11i only) To verify that a link aggregate was formed correctly, nd the linkaggPPA by doing a lanscan and using one of the values in the column titled Crd In# which corresponds to a link aggregate. Then, type: lanadmin -x -v linkaggPPA NOTE: When using the lanadmin commands, please be aware that the -x and -X are case sensitive. Options used with lower case -x are used to show status, while those used with upper case -X are used to set conguration parameters or modes. For example, to verify the physical ports associated with linkaggPPA 101, type: lanadmin -x -v 101 To verify all the physical ports in all congured link aggregates, type: lanscan -q This will list the Card Instance number for each physical port as well as the link aggregates. Data similar to the following output will be displayed (the example following is for HP-UX 11.0):

Chapter 4

83

Conguring APA by Editing Files Verify Status of the Link Aggregates 100 101 102 103 5 6 8 7

This output says that there are 4 ports in link aggregate 100. The 4 ports are lan5, lan6, lan8, and lan7. If no link aggregates are formed, refer to the Troubleshooting section.

84

Chapter 4

Conguring APA by Editing Files Verify Status of a Physical Port (HP-UX 11.0 and 11i Only)

Verify Status of a Physical Port (HP-UX 11.0 and 11i Only)

To verify the status of a specic physical port, type: lanadmin -x -p PortPPA linkaggPPA Where PortPPA can be found by doing a lanscan and using one of the values in the column titled Crd In# which corresponds to a physical port (physical ports are denoted by a value similar to, but not necessarily the same as, 8/0/1/0 in the Hardware Path eld). For example, to verify that the port with PPA number 2 has successfully completed FEC negotiation, type: lanadmin -x -p 2 100 The output from this command should show a eld called Port State. The value of the eld should be UP. If not then you may have a conguration problem and you need to refer to the HP Auto-Port Aggregation Release Notes. To verify that a link aggregate was formed correctly, type: lanadmin -x -v linkaggPPA For example, to verify that ports with PPA numbers 2, 3, 8, and 9 were successfully added to link aggregate with PPA number 101 type: lanadmin -x -v 101

CAUTION

If you change some link aggregate variables using the lanadmin command, those changes are not preserved after reboots. If you use lanadmin, you also need to edit the 2 cong les: hp_apaconf and hp_apaportconf

Chapter 4

85

Conguring APA by Editing Files Verify Status of a Physical Port (HP-UX 11.0 and 11i Only)

86

Chapter 4

What is LAN Monitor?

Chapter 5

87

What is LAN Monitor? LAN Monitor Overview

LAN Monitor Overview

For details on conguring the FEC_AUTO, MANUAL, or LACP modes, see Conguring APA by Editing Files or Conguring APA Using SAM in this document. The LAN Monitor mode of HP APA provides a failover group capability with MC/ServiceGuard-like conguration tools. LAN Monitor does not support MC/ServiceGuard. In the event of link failure, LAN Monitor will automatically migrate the data ow from the primary link to one of the standby links in the failover group.

NOTE

In HP-UX 10.20, the term card instance is used to indicate the port instance. Some le outputs will use the term PPA for this parameter.

LAN Monitor Features

High availability and fast failover of network interfaces. Link aggregates can be part of the failover group. Supports all LAN technologies: 100BT, Gigabit, FDDI, and Token Ring. Automatic link aggregate discovery and conguration commands (lanqueryconf, lanapplyconf, lancheckconf, landeleteconf). Supports SNMP (interface MIB only). Supports the following platforms: HP-UX 10.20: A, D, K, R HP-UX 11.0 and 11i: All except T-class

Conguring LAN Monitor Failover Groups

To congure a LAN Monitor failover group, proceed as follows: 1. Connect the physical devices that are to be in the failover group to the same switch, or different switches/hubs on the same subnet if switch/hub redundancy is desired.

88

Chapter 5

What is LAN Monitor? LAN Monitor Overview 2. Check that a linkloop between the devices succeeds. If it fails, resolve the physical connection between the devices. 3. If the device to be the primary link does not have the desired IP address, add the IP address for the primary port to /etc/rc.cong.d/netconf. Editing that le or using SAM will preserve the IP address permanently (across reboots). You can also temporarily assign an IP address to the primary link by typing, for example: ifcong lan1 192.5.5.138 4. (HP-UX 11.0 and 11i only) In the /etc/rc.cong.d/hp_apaportconf le, create a failover group consisting of primary and standby interfaces, and assign the conguration mode (LAN_MONITOR). Example, to put lan1 and lan2 into a failover group: 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 You can also set the LAN_MONITOR mode with: lanadmin -X -p PortPPA AnyLinkAggregatePPA 5. Activate the conguration by typing: /sbin/init.d/hplm stop /sbin/init.d/hpapa stop and then /sbin/init.d/hpapa start /sbin/init.d/hplm start 6. Query the system for possible link failover groups by typing: lanqueryconf -s

CAUTION

Running lanqueryconf -s will overwrite the original /etc/lanmon/lancong.ascii.

This command will query the system and network for all possible failover groups. The results of the query will be placed in the conguration le /etc/lanmon/lancong.ascii. This le should contain data similar to:

Chapter 5

89

What is LAN Monitor? LAN Monitor Overview NODE_NAME POLLING_INTERVAL DEAD_COUNT FAILOVER_GROUP STATIONARY_IP PRIMARY STANDBY hpxyz6e 10000000 3 lan900 192.5.5.138 lan1 5 lan2 3

You can manually edit this le and change the number of ports in the failover groups, the dead count, or the poll interval. 7. Verify that the conguration in /etc/lanmon/lancong.ascii is still valid by typing: lancheckconf 8. Create the failover groups specied in the conguration le by typing: lanapplyconf This command will create the specied failover groups in the binary conguration le /etc/lanmon/lancong. Check the failover group by using lanscan -q and netstat -in Note: if you later want to delete all the failover groups specied in the /etc/lanmon/lancong.ascii conguration le, type: landeleteconf 9. The failover group is now operational. A reboot will restart the failover group as long as the /etc/lanmon/lancong.ascii le is intact. Example: Conguring a LAN Monitor Failover Group Intent: Congure a two port LAN Monitor failover group. K-class system with lan1 currently congured with IP address 192.1.1.153. We have spare HSC 100BT devices: lan2, lan3, lan4 as shown by netstat and ioscan # netstat -in

90

Chapter 5

What is LAN Monitor? LAN Monitor Overview

Name lan1 lan0 lo0 Mtu 1500 1500 4136 Network Address 192.1.1.0 192.1.1.153 15.13.120.0 15.13.120.153 127.0.0.0 127.0.0.1 Ipkts 9504123 11202 417 Opkts 12437048 257458 417

# ioscan -fkC lan

Class I H/W Path Driver S/W State H/W Type Description ============================================================== ========== lan 1 8/8/1/0 btlan4 CLAIMED INTERFACE HP HSC 100Base-TX lan 2 8/8/2/0 btlan4 CLAIMED INTERFACE HP HSC 100Base-TX lan 3 8/12/1/0 btlan4 CLAIMED INTERFACE HP HSC 100Base-TX lan 4 8/12/2/0 btlan4 CLAIMED INTERFACE HP HSC 100Base-TX lan 0 10/12/6 lan2 CLAIMED INTERFACE Built-in LAN #

It is decided that lan2 will be the standby link for the failover group, with lan1 as the primary device. To congure the failover group: 1. Connect lan1 and lan2 to the same switch, or different switches/hubs on the same subnet. 2. Check that a linkloop between the two devices succeeds. If it fails, resolve the connectivity issue between the devices. # lanscan
Hardware Path 8/8/2/0 8/12/2/0 8/8/1/0 10/12/6 8/12/1/0 LinkAgg0 LinkAgg1 LinkAgg2 LinkAgg3 Station Crd Hdw Address In# State 0x0060B04B7B83 2 UP 0x001083953C1D 4 UP 0x0060B04B7B82 1 UP 0x080009D43696 0 UP 0x001083953C1C 3 UP 0x000000000000 100 DOWN 0x000000000000 101 DOWN 0x000000000000 102 DOWN 0x000000000000 103 DOWN Net-Interface NamePPA lan2 snap2 lan4 snap4 lan1 snap1 lan0 snap0 lan3 snap3 lan100 snap100 lan101 snap101 lan102 snap102 lan103 snap103 NM ID 3 4 5 6 7 9 10 11 12 MAC Type ETHER ETHER ETHER ETHER ETHER ETHER ETHER ETHER ETHER HP-DLPI DLPI Support Mjr# Yes 119 Yes 119 Yes 119 Yes 119 Yes 119 Yes 119 Yes 119 Yes 119 Yes 119

Chapter 5

91

What is LAN Monitor? LAN Monitor Overview

LinkAgg4 0x000000000000 104 DOWN lan104 snap104 13 # # linkloop -i 1 0x0060B04B7B83 Link connectivity to LAN station: 0x0060B04B7B83 -- OK # ETHER Yes 119

3. In the /etc/rc.cong.d/hp_apaportconf le, verify that an entry exists for the primary and standby interfaces that sets the interfaces' port conguration 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

Also set the mode with the lanadmin command: lanadmin -X -p 1 LAN_MONITOR 100 lanadmin -X -p 2 LAN_MONITOR 100 4. If the device to be the primary link does not have the desired IP address, use the ifcong command to assign the IP address. Also add an entry to the /etc/rc.cong.d/netconf le to assign the IP address permanently (or use SAM to do it). # ifconfig lan1 192.1.1.153 # 5. Use the lanqueryconf -s command to query the system for possible failover groups. # lanqueryconf -s ASCII output is in le /etc/lanmon/lancong.ascii # 6. Verify that the contents of the /etc/lanmon/lancong.ascii have the failover group congured as planned.
# cat /etc/lanmon/lanconfig.ascii # ******************************************************** # *********** LAN MONITOR CONFIGURATION FILE ******** # *** For complete details about the parameters and how ** # *** to set them, consult the lanqueryconf(1m) manpage **

92

Chapter 5

What is LAN Monitor? LAN Monitor Overview

# *** or your manual. ** # ******************************************************** NODE_NAME hpnmcbar POLLING_INTERVAL DEAD_COUNT FAILOVER_GROUP STATIONARY_IP STANDBY PRIMARY # 10000000 3 lan100 192.1.1.153 lan2 3 lan1 5

7. Use the lanapplyconf command to build the failover group, and check it with lanscan -q and netstat -in # lanapplyconf
Reading ASCII file /etc/lanmon/lanconfig.ascii Creating Fail-Over Group lan100 Updated binary file /etc/lanmon/lanconfig

# lanscan -q
0 100 101 102 103 104 1 2

# netstat -in
Name Opkts lan0 1173 lo0 390 lan100 0 1500 192.1.1.0 192.1.1.153 0 Mtu Network 1500 15.13.120.0 4136 127.0.0.0 Address 15.13.120.153 127.0.0.1 Ipkts 1794 390

Chapter 5

93

What is LAN Monitor? LAN Monitor Overview

# 8. The failover group is now operational. A reboot will restart the failover group as long as /etc/lanmon/lancong.ascii le is intact.

Conguration Files
ASCII le The ascii conguration le is /etc/lanmon/lancong.ascii. Sample lancong.ascii Conguration File #*********************************************** #******* LAN MONITOR ASCII CONFIGURATION FILE #*** For complete details about the parameters and how #*** to set them, consult the lanqueryconf(1m) manpage #*** or your manual. #********************************************** NODE_NAME POLLING_INTERVAL DEAD_COUNT hpntcyj 1000000 3

FAILOVER_GROUP STATIONARY_IP PRIMARY STANDBY

lan92 194.12.14.55 lan2 lan3 5 3

FAILOVER_GROUP STATIONARY_IP PRIMARY STANDBY

lan91 192.12.14.55 lan6 lan7 5 3

94

Chapter 5

What is LAN Monitor? LAN Monitor Overview

STANDBY STANDBY

lan9 lan8

3 3

The ASCII cong le contains the following elds: NODE_NAME: The name of the node. This is the name of the system as obtained by gethostname() and should be the rst line in the le. FAILOVER_GROUP: The aggregate name which will form a single fail-over group. This may be specied repeatedly for all of the link aggregates in the system. If the link aggregate has multiple links, then it will be of the form lan100, lan101, , that is, an aggregate is allocated to it. However, if it is a single link aggregate, then it will be lanX, where X is the PPA of the link. PRIMARY/STANDBY: The LAN interface (for example, lan0, lan1). This may be specied repeatedly for all applicable lan interfaces in the fail-over group. They can be specied only for fail-over groups which have more than one link. These interfaces belong to the last FAILOVER_GROUP that was mentioned. The last parameter is the port priority that will be assigned to the port. The port with an IP address assigned is taken to be primary. The default port priorities have been selected so that fail-over and fail-back works correctly. STATIONARY_IP This is the IP address dedicated to the link aggregate. This is a required eld and must be set for the primary link before running lanapplyconf. POLLING_INTERVAL The number of microseconds between polling messages. Polling messages are sent between links in the specied interval for monitoring the health of all the links in the link aggregate. Default is 10,000,000 (10 seconds). May occur more than once in the cong le. An aggregates polling interval is set to the most recent that is read. DEAD_COUNT The number of polling packets that are missed before deciding to send a nettl log message to the user that the link may be having problems and the network should be checked for problems. Default is 3.

Chapter 5

95

What is LAN Monitor? LAN Monitor Overview

Binary File
The binary le /etc/lanmon/lancong stores the current snapshot of the aggregates. Since the aggregates cannot be modied using the lanadmin command, and this le is non-editable, it will correctly represent the current conguration.

CAUTION

DO NOT manually edit the binary le as you can corrupt the data.

96

Chapter 5

What is LAN Monitor? LAN Monitor Conguration Commands

LAN Monitor Conguration Commands

lanqueryconf
The basic function of this command is to discover the set of LAN interfaces that can form a single link aggregate and then map that information to an ASCII conguration le (/etc/lanmon/lancong.ascii). Usage: lanqueryconf [-s] [-b] [-v] [-c ascii_file] (At least one of the -s or -b options must be used.) The options are: -s queries the system for what can be found -b queries the binary le -v species verbose output -c ascii_le species the ascii le to be output the default is lanconfig.ascii

Query the system and create an ascii conguration le lanqueryconf -s This will create an ascii le that represents the valid LAN Monitor aggregations that can be formed. This le can be edited and then used with the lanapplyconf command to form the aggregations. The output will be similar to the sample le shown on page 94. Query the system for the binary le The lanqueryconf -b command reads the binary bile /etc/lanmon/lanconfig and creates an ascii output le that can show the LAN Monitor aggregations congured in the system. lanqueryconf -b Reading binary file /etc/lanmon/lanconfig ASCII output is in file /etc/lanmon/laconfig.ascii

Chapter 5

97

What is LAN Monitor? LAN Monitor Conguration Commands

lanapplyconf
This command implements the conguration in the ASCII le /etc/lanmon/lancong.ascii and creates a binary le with the information. Usage: lanapplyconf [-v] [-c ascii_file] The options are: -v species verbose output -c ascii_le species the ascii le to be used for the conguration. The default is /etc/lanmon/lanconfig.ascii.

lancheckconf
This command validates the content of the ASCII conguration le. Usage: lancheckconf [-v] [-c ascii_file] The options are: -v species verbose output -c ascii_le species the ascii le to be checked. The default is /etc/lanmon/lanconfig.ascii.

landeleteconf
This command clears the aggregate(s) that have been created in LAN_MONITOR mode. Usage: landeleteconf [-v][-g PPA number of fail-over group to be deleted] The options are: -v species verbose output -g PPA# species which link aggregate to delete

98

Chapter 5

What is LAN Monitor? LAN Monitor Conguration Commands For example, to delete a FAILOVER_GROUP with a PPA of 104, enter: landeleteconf -g lan104

Chapter 5

99

What is LAN Monitor? LAN Monitor Conguration Commands

100

Chapter 5

Using ServiceGuard with HP APA

Following are the instructions for using MC/ServiceGuard with HP APA.

Chapter 6

101

Using ServiceGuard with HP APA Requirements for Use

Requirements for Use

To use MC/ServiceGuard with HP APA, the following MC/SG and APA requirements must be met: Required MC/ServiceGuard versions A.11.09, A.11.12, or A.11.13 on HP-UX 11.0 and 11.i. MC/ServiceGuard only supports FEC_AUTO and MANUAL link aggregates. MC/ServiceGuard does not support LACP_AUTO mode link aggregates.

NOTE

Congure APA before conguring MC/SG. Only link aggregates should be used in the MC/SG conguration.

APA Conguration Requirement - Follow the general rules for conguring APAs FEC_AUTO or MANUAL link aggregates. If more than one FEC_AUTO aggregation is used on the system (including those that are NOT used with MC/SG), each FEC_AUTO aggregation must have a different group capability.

Refer to chapter 2, Modifying Default Conguration Parameters for details on conguring link aggregates and for setting the FEC group capability or LACP key.

102

Chapter 6

Troubleshooting HP Auto Port Aggregation (APA) Software

This chapter contains an overview on troubleshooting and detailed troubleshooting owcharts and instructions.

Chapter 7

103

Troubleshooting HP Auto Port Aggregation (APA) Software Troubleshooting Overview

Troubleshooting Overview
HP Auto-Port Aggregation problems can be caused by a variety of hardware and software components. The problem impacting your system may originate in a required hardware component (that is. networking adapter), the switch which the networking adapter connects to, or the HP Auto-Port Aggregation software. As with any troubleshooting, a systematic approach is helpful. The following table and owcharts provide a logical sequence of steps to follow when troubleshooting the HP Auto-Port Aggregation software. Using the diagnostic owcharts provided in this chapter, identify whether the problem is with the HP Auto-Port Aggregation software, conguration of the switch, physical connections to the switch, or whether it is in some other part of the network. Once the problem is isolated, execute the recommended corrective action. If you cannot solve the problem on your own, contact your HP representative. Use the guidelines in Contacting Your HP Representative, to help you effectively communicate what is wrong.

104

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software What Happens during Start Up?

What Happens during Start Up?

Following is the sequence of actions that occur after you have installed the HP APA software. During the system boot-up, the following sequence of events occur: 1. Initialize HP APA software All the internal housekeeping initialization (such as allocation of memory, etc.) for the software is done. During this step, the default values are assigned for all the properties on each port and link aggregate. 2. hp_apaportconf processing Contains customization variables for each physical port. The features that can be set on each port are Group Capability, Port Priority, and Cong Mode. If no value is specied for a given feature for a given port, the software assumes a default value for the same. The ports mode is set at this stage. 3. hp_apaconf processing /etc/rc.cong.d/hp_apaconf contains customization variables for each link aggregate. The features that can be set on each link aggregate are Load Balancing Mode, Hot Standby Mode, and ports in a Manual Link Aggregate. The last feature allows manual conguration of a link aggregate with the port(s) specied. 4. Start the HP APA software Cisco's FEC or IEEE 802.3ad LACP protocol is started on the ports that have been marked as such. No action is taken for the ports that have Ciscos FEC or IEEE 802.3ad LACP turned off. 5. Process LAN Monitor ASCII le Process /etc/lanmon/lanconfig.ascii to create fail-over groups. If this le has not been created then no action is taken. Once the system is up and running, you can distinguish a link aggregate from a normal (unaggregated) port by running lanscan(1M) at the HP-UX prompt as follows:

Chapter 7

105

Troubleshooting HP Auto Port Aggregation (APA) Software What Happens during Start Up?

lanscan Table 7-1

Hardware Path 10/12/6 LinkAgg0 LinkAgg1 LinkAgg2 LinkAgg3 LinkAgg4 Station Address 0x080009B19B60 0x0010830497D5 0x0060B0770028 0x000000000000 0x000000000000 0x000000000000 Crd In# 12 100 101 102 103 104 Hdw State UP UP UP DOWN DOWN DOWN Net-Interface NamePPA lan0 snap0 lan100 snap100 lan101 snap101 lan102 snap102 lan103 snap103 lan104 snap104 NM ID 11 14 15 16 17 18 MAC Type ETHER ETHER ETHER ETHER ETHER ETHER HP-DLPI Support Yes Yes Yes Yes Yes Yes DLPI Mjr# 119 119 119 119 119 119

The hardware path of a LinkAggregate has LinkAggx (with x indicating the LinkAggregate number) instead of a slash (/) separated hardware path.

MAC Addresses for Link Aggregates

This section describes the process used to select unique MAC addresses for link aggregates. The unique MAC address for a specic link aggregate is determined by using the permanent MAC address of the rst physical port assigned to the link aggregate. If the rst port is removed, the link aggregates MAC address is updated with the permanent MAC address of the last port in the link aggregate. When a physical port is removed from a link aggregate, its local MAC address is reset to the physical ports permanent MAC address. Unsupported Way of Changing MAC Address HP-UX 11.x and 10.20 versions of APA do not support the following function: Changing the local MAC address on logical link aggregations via DL_SET_PHYS_ADDR_REQ.

106

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Diagnostic Flowcharts
Below is a summary of the types of network tests in the diagnostic owcharts. Follow the owcharts in sequence beginning with Flowchart 1. Continue sequentially through owcharts 2, 3, 4, 5, 6, 7, 8, 9, and 10 referring back to Flowchart 1 (ping), as indicated at the end of each owchart, until you have corrected the problem. The following owcharts are described in general terms and can be executed on any network physical port supported by the HP Auto-Port Aggregation software. See Summary of APA and LAN Monitor Capabilities on page 14 for a list of supported network physical ports (adapter cards). Table 7-2 Flowchart Descriptions Flowchart 1 2 3 and 4 5 5A 5B 5C 5D 6 7 8 9 10 Description Network Level Loopback Test Network Physical Port Connections/LED Test Network Physical Port Conguration Test Link Aggregation Conguration Test Manual Conguration Test PAgP Conguration Test LAN Monitor Conguration Test LACP Conguration Test Network Conguration Test Arp Verication Link Level Loopback Test Transport Level Loopback Test (using ARPA) Bridge/Gateway Loopback Test

Chapter 7

107

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Network Level Loopback Test: Checks roundtrip communication between Network Layers on the source and target host using the ping(1M) command. Network Physical Port Connections/LED Test: Checks that all the hardware connections between your system and the network are connected and operational. Network Physical Port Configuration Test: Veries the conguration of the network physical port(s) on a host using the lanscan(1M), netfmt -vf, lanadmin(1M), and ifcong(1M) commands. In addition, the switch conguration should be veried using the appropriate switch commands. Link Aggregation Configuration Test: Veries the conguration of the link aggregate on the server. The switch conguration should be veried using the appropriate switch commands. The appropriate patches should also be veried. Arp Verification: Checks arp entries using the arp(1M) command.
Link Level Loopback Test: Checks roundtrip communication between Link Levels on the source and target host using the linkloop(1M) diagnostic.

Transport Level Loopback Test: Checks roundtrip communication between Transport Layers on the source and target host using ARPA services telnet and ftp commands. Bridge/Gateway Loopback Test: Checks general network connections through a gateway.

108

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

This page intentionally left blank

Chapter 7

109

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 1: Network Level Loopback Test

The following tests should be executed on the specic link aggregate which is experiencing problems.

110

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Figure 7-1 Flowchart 1: Network Level Loopback Test 1
A Execute: ping to remote host

ping successful ? No

Yes

Stop

Network unreachable ? No

Yes

3, 5

Command hangs ? No Unknown host ? No

Yes

2,3,4,5 6,7 & 8

F
Yes Correct BIND, YP or /etc/hosts conguration 1

H
G No route to host ? No Call HP Yes Add route table entry

Chapter 7

111

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 1 Procedures A.

Execute: ping to remove host. Using ping(1M), send a message to the remote host to which you are having problems connecting. For example:
ping spiff

B.

ping successful? A message is printed to stdout for each ping packet returned by the remote host. If packets are being returned, your system has network level connectivity to the remote host. Note what percentage of the total packets are lost, if any. Losing ten percent or more may indicate the network or remote host is extremely busy. You may also nd it useful to note the round-trip transmission times. Periodically high transmission times may indicate that the network or remote host is extremely busy. Consistently high transmission times may indicate the local host is extremely busy. If a message is not returned after executing ping, ping is not successful. Do Cntrl C to stop the ping output. Network unreachable? If YES, go to Flowchart 3 to display connection status using the lanscan(1M) command. If this is OK, then proceed to Flowchart 5 and verify that the link aggregate is congured correctly. Command hangs. If a message is not returned after executing ping, go to Flowcharts 2 through 7, referring back to Flowchart 1 (ping) until you have corrected the problem. Unknown host? If you receive this message, go to Step F. Correct BIND, YP or hosts configuration. Add the missing host name and start again with Flowchart 1. No route to host? If Error= Sendto: No route to host, go to Step H. Otherwise, call your HP representative for help.

C.

D.

E. F.

G.

112

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts H.

Add route table entry. Using route, add a route table entry for that host. Refer to the route(1M) online man page for more details. Start again with Flowchart 1.

Flowchart 2: Network Physical Port Connections/LED Test

The following owchart should be used for each of the network physical ports which have been congured in a specic link aggregate. These tests can be executed at any time to verify proper physical connection between the network physical port and the switch.

Chapter 7

113

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Refer to Modifying Default Conguration Parameters on page 49, or Using the lanadmin Command for Testing on page 167 for a detailed description of how to determine which network physical ports are associated with a specic link aggregate.

114

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Figure 7-2 2 A
Check: Power outlet

Flowchart 2: Network Physical Port Connections/LED Test

LED Display:
Test Error Message 100 Mbit port LED=ON on Mbit (dmesg ouput) 10 Screenport LED=OFF Yes

? D
No

Check network physical Port Installation. Reset the network physical port.

1
Check status of Link LED

F E Link LED = OFF ?

No Yes Check connection to switch. Ensure switch is autonegotiating. Ensure switch is congured in the correct mode. Reset the network physical port.

1 H G
Do Mbit port LED=ON 100link speed and duplex 10 mode matchLED=OFF Mbit port switch No Set attached switch to correct speed, duplex mode, and autonegotiation mode.

?
Yes

1 3 Reset network physical port.

Chapter 7

115

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 2 Procedures A. B.

Check power outlet. Ensure the power cord is plugged in to a live outlet. Test error message on screen? At the HP-UX prompt, type the dmesg command, and look for an error message. Does the dmesg output show an error message from networking port(s) you are using? If not, go to Step D.
Note: even if the Test LED is OFF, a card problem is still possible.

C.

Check card installation.If dmesg reported an error message for the networking port(s), reset the port according to Steps D through G in Flowchart 4. If problem persists, call HP. Go back to Flowchart 1.
Check status of Link LED.

D. E.

Link LED = OFF? Go to Step F. Link LED = ON? Go to Step G.

F.

If Link LED = OFF, check connection to switch. Ensure switch is not autonegotiating. Ensure switch is congured in the correct mode. Reset card according to Steps D through G in Flowchart 4. Go back to Flowchart 1.

G. H.

Do link speed and duplex mode match switch? If they do, proceed to Flowchart 3.
If Link speed and duplex mode do not match what you expect, set attached switch to the correct link speed and duplex mode, and if necessary enable autonegotiation. Reset the network physical port according to Steps D through G in Flowchart 4 and go back to Flowchart 1.

116

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 3: Network Physical Port Conguration Test

The following owchart should be used for each of the network physical ports which are being congured in a specic link aggregate. These tests can be executed at any time to verify that the software for the network physical port is correctly installed on the HP 9000 server.

Chapter 7

117

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Figure 7-3 Flowchart 3: Network Physical Port Conguration Test 3 A
Execute: lanscan -v

Is your interface displayed ? No Run ioscan -f

Yes

Hardware up ? No

Yes 5

Is driver in kernel ? Yes

No F

Install driver. Verify or edit /stand/system to add driver keyword Regen kernel.

G
Check hardware

H
Reboot the system

Problem xed ?
Yes Stop

No

118

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 3 Procedures

NOTE

Check that your network physical port connectors between the card and switch (or wall plug) are fully connected before beginning this owchart.

A.

Execute: lanscan. Enter the lanscan -v command to display information about network physical ports and the link aggregates that are successfully installed on the system. Some network physical ports may show up as part of a specic link aggregate and not as standalone ports. See Using the lanadmin Command for Testing on page 167 for a detailed description of how to determine which link aggregate a specic network physical port belongs to.
See the lanscan online man page for more detailed information.

B.

Is your interface displayed? lanscan shows information about every LAN card in the system backplane. The Hardware Path of one of the entries should correspond to the network physical port slot multiplied times four. For example, a hardware path of 32 corresponds to a network physical port in slot 8.

C.

Hardware up? The hardware state is operational if up is displayed for the network physical port under the Hardware State heading. If it is, continue to Flowchart 5. If not, go to Step D.

Chapter 7

119

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts D.

Run ioscan. ioscan will scan the system hardware and list the results. If you execute ioscan -f, output similar to the following will be displayed:

120

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Table 7-3

Chapter 7

Class I H/W Path Driver S/W State H/W Type Description ============================================================================= bc 0 root CLAIMED BUS_NEXUS bc 1 8 ccio CLAIMED BUS_NEXUS I/O Adapter ba 0 8/4 GSCtoPCI CLAIMED BUS_NEXUS PCI Bus Bridg - GSCtoPCI lan 4 8/4/1/0 btlan4 CLAIMED INTERFACE PCI(10110009) - Built-in #1 lan 5 8/4/2/0 btlan4 CLAIMED INTERFACE PCI(10110009) - Built-in #2 ba 1 8/8 GSCtoPCI CLAIMED BUS_NEXUS PCI Bus Bridg - GSCtoPCI lan 6 8/8/1/0 btlan4 CLAIMED INTERFACE PCI(10110009) - Built-in #1 lan 7 8/8/2/0 btlan4 CLAIMED INTERFACE PCI(10110009) - Built-in #2 ba 2 8/12 GSCtoPCI CLAIMED BUS_NEXUS PCI Bus Bridg - GSCtoPCI lan 8 8/12/1/0 btlan4 CLAIMED INTERFACE PCI(10110009) - Built-in #1 lan 9 8/12/2/0 btlan4 CLAIMED INTERFACE PCI(10110009) - Built-in #2 bc 2 10 ccio CLAIMED BUS_NEXUS I/O Adapter ext_bus 0 10/0 c720 CLAIMED INTERFACE GSC built-in st/Wide SCSI Interface target 0 10/0.6 tgt CLAIMED DEVICE disk 0 10/0.6.0 sdisk CLAIMED DEVICE HP C2490 target 1 10/0.7 tgt CLAIMED DEVICE ctl 0 10/0.7.0 sctl CLAIMED DEVICE Initiator bc 3 10/4 bc CLAIMED BUS_NEXUS Bus Converter tty 0 10/4/0 mux2 CLAIMED INTERFACE MUX lanmux 0 10/4/4 lanmux0 CLAIMED INTERFACE HP J2146A - 8 .3 LAN lan 1 10/4/4.1 lan3 CLAIMED INTERFACE ba 3 10/8 GSCtoPCI CLAIMED BUS_NEXUS PCI Bus Bridg - GSCtoPCI lan 2 10/8/1/0 btlan4 CLAIMED INTERFACE PCI(10110009) - Built-in #1 lan 3 10/8/2/0 btlan4 CLAIMED INTERFACE PCI(10110009) - Built-in #2 ba 4 10/12 bus_adapter CLAIMED BUS_NEXUS Core I/O Adap r ext_bus 1 10/12/5 c720 CLAIMED INTERFACE Built-in SCSI target 2 10/12/5.2 tgt CLAIMED DEVICE target 3 10/12/5.7 tgt CLAIMED DEVICE ctl 1 10/12/5.7.0 sctl CLAIMED DEVICE Initiator lan 0 10/12/6 lan2 CLAIMED INTERFACE Built-in LAN 121 ps2 0 10/12/7 ps2 CLAIMED INTERFACE Built-in Keyb rd/Mouse processor 0 32 processor CLAIMED PROCESSOR Processor processor 1 34 processor CLAIMED PROCESSOR Processor memory 0 49 memory CLAIMED MEMORY Memory

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Table 7-4
ba 0 GSCtoPCI lan 4 Built-in #1 lan 5 Built-in #2 8/4 8/4/1/0 8/4/2/0 GSCtoPCI btlan4 btlan4 CLAIMED CLAIMED CLAIMED BUS_NEXUS INTERFACE INTERFACE

PCI Bus Bridg

PCI(10110009)

PCI(10110009)

If there are multiple network physical ports installed in the system then the output above will be duplicated with only the H/W Path column changing to reect the correct hardware path information. The example above shows multiple HSC 100BT cards installed. E.

Is driver in kernel? If the driver has not been generated into the kernel, ioscan output will be similar to (but not necessarily the same as):

Table 7-5
ioscan -f Class I H/W Path Driver S/W State H/W Type Description ======================================================================= ======= unknown -1 10/4/4 UNKNOWN UNCLAIMED INTERFACE

The class and driver elds alone will indicate unknown status if the kernel has not been generated. If the driver has not been generated, continue to Step F. If the driver is in the kernel, go to Step G. F.

Verify or edit /stand/system and regen kernel. Verify/edit that /stand/system contains the appropriate keyword for the networking adapter you are using. For example, if you are using the HSC 100BT network adpater, the keyword btlan4 should appear. Or, if using a V-class PCI 100BT network adapter, the keyword btlan6 should appear. If not, see Creating a New Kernel in Chapter 3 of the Installing and Administering LAN/9000 Software manual for instructions on how to edit /stand/system to create a new kernel.
Chapter 7

122

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Verify that the required patch is installed for the network physical port which is being used. Refer to Chapter 1 for a list of required patches. G H. I.

Check Hardware. Verify that the network card is seated correctly and that it is operational. Reboot the system. Problem fixed? If you have found the appropriate network physical port problem, stop. If not, start again with Flowchart 1.

Chapter 7

123

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 4: Network Physical Port Conguration Test

The following owchart should be used for each of the network physical ports which are being congured in a specic link aggregate. These tests can be executed at any time to verify if there are any nettl log messages associated with the network physical ports that are being congured in a link aggregate.

124

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Figure 7-4 Flowchart 4: Network Physical Port Conguration Test
4

A
Execute: netfmt

B
Check causes and actions on display in the formatted log output

C
Problem solved ? No Execute: lanadmin

Yes 1

E
Select LAN from Menu

F
Select PPA command and enter Network Physical port nmid

G
Reset Port

Reset successful

Yes

?
No 4A

Chapter 7

125

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 4 Procedures A.

Execute: netfmt. Use the netfmt command to view log data (error and disaster messages). An example command is shown below.
netfmt -v -f /var/adm/nettl.LOG00|more

B.

Check causes and actions on display in the formatted log output. Use the time stamp to nd the proper logs. Ensure that you are looking at the appropriate network physical port information. Problem solved? If YES, go to Flowchart 1. If not, continue with Step D. Execute lanadmin. Run lanadmin(1M). For a complete description of this command, refer to the lanadmin(1M) online man page. Select LAN from Menu. Select lan to enter the LAN Interface diagnostic. Select the PPA command and enter the Network Physical Port PPA. You can use the lanscan command to nd the current PPA for the network physical port. The PPA you enter becomes the current device to be tested. Reset the network physical port according to Steps D through G in Flowchart 4. The reset command in lanadmin re-executes the LAN network physical port self-test. Reset successful? The reset is successful if no errors are displayed as a result of the reset command. If the self-test was successful, the problem may be that you are not connected to the network properly. Correct the problem and verify the resolution by continuing with Flowchart 1. Otherwise, go to Flowchart 4A.

C. D.

E. F.

G.

H.

126

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 4A: Network Physical Port Conguration Test

Figure 7-5 Flowchart 4A: Network Physical Port Conguration Test

4A A
Execute: netfmt

B
Check causes and actions on display in the formatted log output

Problem solved

Yes

?
No Call HP

Flowchart 4A Procedures A.

Execute: netfmt. Use the netfmt command to view log data (error and disaster messages). An example netfmt command is shown below:
netfmt -v -f /var/adm/nettl.LOG00|more Extend the search to LOG01 as information may have rolled (overowed) into this le from LOG00.

Chapter 7

127

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts B.

Check causes and actions on display in the formatted log output. Use the time stamp to nd the proper logs. Ensure that you are looking at the appropriate network physical port information. Problem solved? If YES, go to Flowchart 1. If not, contact your HP representative.

C.

128

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

This page intentionally left blank

Chapter 7

129

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 5: Link Aggregate Conguration Test

The following tests should be executed on the specic link aggregate which is not working correctly.

130

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Figure 7-6 Flowchart 5: Link Aggregate Conguration Test 5

11.0

HP-UX release is

10.20

A
Execute lanadmin -x -v <agg>

F Execute lanscan -q

B
Ports in the aggregate ? no yes

Ports in the aggregate ? no Execute lanqueryconf -b

yes

H yes

C
Is the aggregate enabled ? no

D
Manual PAgP Mode = =

5A

5B

Is the aggregate enabled ?

yes

no
no

E
LM LACP Mode = =

5C 5D

5C

Chapter 7

131

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 5 Procedures Depending on whether you are on HP-UX 11.0 or 10.20, the tools you use are different. lanadmin has no LAN Monitor functionality in 10.20. You must use other tools lanqueryconf(1M), lanapplyconf(1M), or landeleteconf(1M). Also note that in10.20, which supports only link aggregates, instance numbers start at 90; 11.0 instance numbers start at 100, 11i at 900. HP-UX 11.0 A.

Execute lanadmin -x -v LinkAggPPA. A sample output for three scenarios using linkagg 100 is shown below. Case 1 shows that a linkagg is enabled and there are ports in the aggregate. Case 2 shows that there were ports in the aggregate, but they are currently down. In case 3, the linkagg is not enabled and either you need to add ports to enable it (Lan Monitor or Manual mode) or turn on LACP/PAgP aggregation protocols, so ports could be added to the aggregate automatically.

Case 1: lanadmin -x -v 100 Linkaggregate PPA # Number of Ports Ports PPA Link Aggregation State Group Capability Load Balance Mode Case 2: lanadmin -x -v 100 Linkaggregate PPA # Number of Ports : 100 : 0 : 100 : 2 : 5 6 : LINKAGG MANUAL : 0 : MAC Address Based (LB_MAC)

132

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Ports PPA Link Aggregation State Group Capability Load Balance Mode Case 3: lanadmin -x -v 101 Linkaggregate PPA # Number of Ports Ports PPA Link Aggregation State Group Capability Load Balance Mode

: NONE : LINKAGG HAS NO PORTS : 0 : MAC Address Based (LB_MAC)

: 101 : 0 : NONE : LINKAGG IS NOT ENABLED : 0 : MAC Address Based (LB_MAC)

See Using the lanadmin Command for Testing on page 167 for a detailed list of supported commands and their usage. B. If there are ports in the aggregate, as shown by the Ports PPA line above, go to Flowchart 6. Otherwise continue to the Step C. If the aggregate is enabled, go to Flowchart 4. Otherwise continue to Step D. Depending on the mode (MANUAL, FEC_AUTO, LAN_MONITOR, or LACP_AUTO) in which you want to enable the aggregate, follow Flowchart 5A, 5B, 5C, OR 5D as appropriate. FEC_AUTO is the same as PAgP and LAN_MONITOR is also being referred to as LM.

C. D & E.

HP-UX 10.20 F. Execute lanscan -q If link aggregates are congured and ports are UP, it can be seen in the lanscan output.

Chapter 7

133

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Example 1: Shows that link aggregates are either not congured or went down. lanscan -q 0 1 2 3 4 5 90 91 92 93 94 Example 2: Shows that link aggregates with ports in them went down. lanscan -q 0 5 90 91 92 93 94 G. H. Ports in the aggregate? If YES, go to Flowchart 6. If No, go to Step H. Execute lanqueryconf -b This shows the present conguration that is effective in the system. The output of this command tells if a link aggregate is now congured, but if ports went down. In the following example, link aggregate 92 is congured and all of its ports went down.

lanqueryconf -b

134

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Reading binary file /etc/lanmon/lanconfig ASCII output is in file /etc/lanmon/lanconfig.ascii

NODE_NAME POLLING_INTERVAL DEAD_COUNT

hpntcyj 10000000 3

FAILOVER_GROUP STATIONARY_IP STANDBY PRIMARY

lan90 193.33.33.33 lan9 lan6 3 5

FAILOVER_GROUP STATIONARY_IP PRIMARY STANDBY STANDBY STANDBY FAILOVER_GROUP STATIONARY_IP I.

lan91 195.55.55.55 lan0 lan1 lan2 lan3 5 3 3 3 lan92 194.44.44.44

Is the aggregate enabled? If Yes, go to Flowchart 4. If No go to Flowchart 5C.

Chapter 7

135

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 5A: Manual Conguration Test

Figure 7-7 Flowchart 5A: Manual Conguration Test 5A A
Execute lanadmin -x -p <port_num> 100 for each port

Is port mode Manual?

No

C
Execute lanadmin -X -p <port> MANUAL 100 for each port

Yes

D
Add port to aggregate lanadmin -X -a <port_list> 100

E
Success? No Fix error according to message received

Yes

5A

136

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 5A Procedures A. Execute lanadmin -x -p <portppa> 100 to determine the mode for each of the ports that you want to be a part of the aggregate in MANUAL mode. For example, to determine the status of port PPA 4, enter: lanadmin -x -p 4 100 For more examples of the lanadmin command, see Using the lanadmin Command for Testing on page 167. B. Examine the output and look at the mode. If the port mode is not MANUAL go to Step C. Otherwise go to Step D. Execute lanadmin -X -p <portppa> MANUAL 100 to change the state to MANUAL for all the ports which were not in MANUAL mode. Add the ports to the aggregate using the following command syntax: lanadmin -X -a PortPPAs LinkAggPPA This command will add the network physical ports with portPPA numbers to the link aggregate with LinkAggPPA. For example, to add network physical ports with PortPPAs 1,2,3, and 4 to aggregate 100 the following command should be used: lanadmin -X -a 1 2 3 4 100 E. Did the above command complete successfully? If YES go to Flowchart 1. If NO x the error according to the error message and go back to the beginning of this owchart.

C.

D.

NOTE

The link aggregate can be congured, but there can still be misconguration problems on the switch. Its imperative that both the switch and the server links aggregates are consistent in order for successful network communication to occur.

Chapter 7

137

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 5B: PAgP Congurations Test

138

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Figure 7-8 Flowchart 5B: PAgP Conguration Test A 5B
Execute lanadmin -x -p <port_num> 100 for each port

Is port mode FEC_AUTO or LACP_AUTO?

No

C
Execute lanadmin -X -p <port> FEC_AUTO 100 for each port

Yes

D
Run lanscan -q to see if ports are aggregated

E
Ports aggregated? No

Yes

Execute lanadmin -x -p <port> 100 for each port

H 1. Check Cisco FEC protocol on each port 2. Check switch conguration 3. Verify that required patches are installed

Is port mode FEC_AUTO? No

Yes

Call HP

No

Stop LACP?
Yes J

1. Execute lanadmin -X -p <port> MANUAL 100 2. Check switch conguration

Chapter 7

139

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 5B Procedures A. Execute lanadmin -x -p <portppa> 100 to determine the mode for each of the ports that you want to be a part of the aggregate in PAgP mode. For example, to determine the status of port ppa 4, enter: lanadmin -x -p 4 100 For more examples of the lanadmin command, see Using the lanadmin Command for Testing on page 167. B. Examine the output and look at the mode. If the port mode is neither FEC_AUTO nor LACP_AUTO go to Step C. Otherwise go to Step D. Execute: lanadmin -X -p <portppa> FEC_AUTO 100 to change the state to FEC_AUTO for all the ports which were in MANUAL mode. Wait 30 seconds for the aggregation protocol to establish the connection. Execute lanscan -q to see if ports are aggregated. If YES go to Step G. If NO go to Step F.

C.

D & E. F.

Ports aggregated? If the are not aggregated, then the following should be veried for correctness. 1. Auto Add: If you are attempting to enable a link aggregate via the Cisco Fast EtherChannel protocol check the network physical port status with the following command:
lanadmin -x -p PortPPA LinkAggPPA This command should display the following output: Port FEC Mode Port State Port Group Capability Port Priority The Port State eld should show UP if the Cisco FastEtherChannel Protocol has negotiated successfully. If the Port State is not UP then go to Step 3, below.

140

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

2. Switch Configuration: Verify that the switch is congured correctly. Refer to the appropriate switch documentation to determine if the switch ports connected to the HP 9000 Server are congured correctly for link aggregation. 3. Required Patches: Verify that required patches are properly installed on your server. See Required Software on page 17 to determine which patches are required for the HP Auto-Port Aggregation Product.
If all of the checks above are OK then call your HP Representative. If any step is not OK, then correct the problem and go back to Step A. G. Execute the following command again: Lanadmin -x -p <portppa> LinkAggPPA H. I. Is port mode FEC_AUTO? If YES go to Flowchart 1. If NO, go to Step I. Stop LACP? The port mode must be LACP_AUTO. If you DO NOT want to stop LACP on the ports, go to Flowchart 1. If you DO want to use the ports for PAgP go to Step J. 1. Execute lanadmin -X -p <port> MANUAL 100 to stop the LACP protocol. 2. Check switch conguration. Check the conguration to ensure the port should not run IEEE 802.3ad LACP protocol, but Cisco Fast EtherChannel protocol. Wait 30 seconds for the port to settle down and then start this owcharts procedure again.

J.

Chapter 7

141

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

This page intentionally left blank

142

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 5C: LAN Monitor Conguration Test

Figure 7-9 Flowchart 5C: LAN Monitor Conguration Test 5C A
Execute lanqueryconf -s and gure out possible fail-over (FOV) groups

No

Port in FOV group needs IP assigned?

Yes Pick a port in FOV group and assign an IP address to it

E D F
Make an entry in /etc/rc.cong.d/netconf No Success? Correct problem according to error message received

5C

G
Run lanapplyconf -s again and edit /etc/lanmon/lancong.ascii if necessary

H
Yes

Run lanapplyconf

5C J
No

I
Success?

Correct problem according to error message received

Chapter 7

143

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 5C Procedures A. lanqueryconf gures out which set of ports are on the same subnet, and which on e of them is congured with an IP address and writes valid congurations to the default le /etc/lanmon/lanconfig.ascii. It also prints a warning message if none of the ports on a subnet have an IP address assigned. For more details, see the lanqueryconf(1M) man page. Execute lanqueryconf -s to do a system-wide search for ports/links that can form fail-over groups. Example 1:lanqueryconf -s fails to ne ports that can form a fail-over group.

lanqueryconf -s WARNING: None of the ports in subnet (lan2) have an IP address assigned WARNING: None of the ports in subnet (lan4) have an IP address assigned WARNING: None of the ports in subnet (lan12) have an IP address assigned

WARNING: None of the ports in subnet (lan6 lan7) have an IP address assigne No Fail-Over groups found. ASCII file not created. Example 2: lanquery -s successfully nds ports that can form a fail-over group. lanqueryconf -s ASCII output is in file /etc/lanmon/lanconfig.ascii The le /etc/lanmon/lanconfig.ascii looks like: NODE_NAME POLLING_INTERVAL DEAD_COUNT hpntc6s 10000000 3

144

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

FAILOVER_GROUP STATIONARY_IP PRIMARY STANDBY B.

lan101 194.12.14.56 lan0 lan2 5 3

If none of the ports in a fail-over group has an IP address assigned, lanqueryconf prints a warning message. The port that you choose to assign an IP address to carries all the trafc to and from the fail-over group. This port is called the primary port, and in the event of failure of this port, the next highest priority port among the standby ports takes over. Use the following syntax for the ifcong command: ifcong <interface> <ip address> up Example: ifconfig lan3 192.12.14.56 up For more details see the ifconfig(1M) man page.

C.

D.

Run ifcong <interface> to check if the command in Step C was successful.

ifcong lan3 lan3: flags=843<UP, BROADCAST RUNNING MUTICAST> inet 192.12.14.56 netmask ffffff00 broadcast 192.12.14.255 E. Correct any problem with the ifcong ags or other error indications and repeat from Step A. If necessary use the ifcong(1M) man page to gure out the errors. An entry in /etc/rc.config.d/netconf helps in conguring IP addresses automatically by using the rc scripts on boot up. Run lanqueryconf -s again so it can determine which ports can form fail-over groups.

F.

G.

Chapter 7

145

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts H. Run lanapplyconf. This takes the information in a conguration le, forms fail-over groups with them as described in the conguration le, and switches the IP address from the primary port to the fail-over group. The default conguration le is /etc/lanmon/lanconfig.ascii. If lanapplyconf is successful, go to Flowchart 1. Otherwise go to Step J. Correct any problems by using the error messages and then begin again at Step A of this owchart.

I. J.

146

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

This page intentionally left blank

Chapter 7

147

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 5D: LACP Conguration Test

148

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Figure 7-10 Flowchart 5D: LACP Conguration Test 5D A
Execute lanadmin -x -p <port_num> 100 for each port

Is port mode FEC_AUTO or LACP_AUTO?

No

C
Execute lanadmin -X -p <port> LACP_AUTO 100 for each port

Yes

D
Run lanscan -q to see if ports are aggregated

E
Ports aggregated? No

Yes

Execute lanadmin -x -p <port> 100 for each port

H 1. Check LACP protocol on each port 2. Check switch conguration 3. Verify that required patches are installed

Is port mode LACP_AUTO? No

Yes

Call HP

No

Stop PAgP?
Yes J

Chapter 7

149

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 5D Procedures A. Execute lanadmin -x -p <portppa> 100 to determine the mode for each of the ports that you want to be a part of the aggregate in PAgP mode. For example, to determine the status of port ppa 4, enter: lanadmin -x -p 4 100 For more examples of the lanadmin command, see Using the lanadmin Command for Testing on page 167. B. Examine the output and look at the mode. If the port mode is not FEC_AUTO or LACP_AUTO go to Step C. Otherwise go to Step D. Execute: lanadmin -X -p <portppa> LACP_AUTO 100 to change the state to LACP_AUTO for all the ports which were in MANUAL mode. Wait 30 seconds for the aggregation protocol to establish the connection. Execute lanscan -q to see if ports are aggregated. If YES go to Step G. If NO go to Step F. Ports aggregated? If the ports are not aggregated, then the following should be veried for correctness.

C.

D & E. F.

1. Auto Add: If you are attempting to enable a link aggregate via the IEEE 802.3ad LACP Protocol. Check the network physical port status with the following command:
lanadmin -x -p PortPPA LinkAggPPA This command should display the following output: Port LACP Mode Port State Port Group Capability Port Priority The Port State eld should be UP if the IEEE 802.3ad LACP Protocol has negotiated successfully. If the Port State is not UP then go to Step 3, below.

150

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

2. Switch Configuration: Verify that the switch is congured correctly. Refer to the appropriate switch documentation to determine if the switch ports connected to the HP 9000 Server are congured correctly for link aggregation. 3. Required Patches: Verify that required patches are properly installed on your server. See Required Software on page 17 to determine which patches are required for the HP Auto-Port Aggregation Product.
If all of the checks above are OK then call your HP Representative. If any step is not OK, correct the problem and go back to Step A. G. Execute the following command again: Lanadmin -x -p <portppa> LinkAggPPA H. I. Is port mode LACP_AUTO? If YES go to Flowchart 1. If NO, go to Step I. Stop PAgP? The port mode must be FEC_AUTO. If you DO NOT want to stop FEC (PAgP) on the ports, go to Flowchart 1. If you DO want to stop PAgP and use the ports for LACP go to Step J. 1. Execute lanadmin -X -p <port> MANUAL 100 to stop the FEC (PAgP) protocol. 2. Check switch conguration. Check the conguration to ensure the port should not run Ciscos FEC protocol, but IEEE 802.3ad LACP protocol. Wait 30 seconds for the port to settle down and then start this owcharts procedure again.

J.

Chapter 7

151

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

This page intentionally left blank

152

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 6: Network Conguration Test

Figure 7-11 6 A
Execute ifcong <interface> ...<IP address> up

Flowchart 6: Network Conguration Test

B
Execute: ifcong <interface>

E C
ifcong successful ? Yes No

Are ags correct ? Yes

No

Correct ifcong ag settings

ifcong entry in /etc/rc.cong.d/netconf : ? No Modify /etc/rc.cong.d/netconf

Yes

Any error messages returned ? Yes Correct problem according to the message received

No

Call HP

Chapter 7

153

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 6 Procedures A. Execute ifcong <interface> <IP address> up on the link aggregate you want to congure in order to ensure that the link aggregate is enabled. For example, to congure an IP address for the link aggregate lan100, enter: ifconfig lan100 192.6.1.17 up For more examples of the ifcong command, refer to the ifcong(1M) online man page. B. Execute ifcong <interface> without the up parameter again, to check the ag setting on the link aggregate you want to test for the UP parameter. For example, to check the link aggregate lan100, enter: ifconfig lan100 C.

ifconfig successful? ifconfig is successful if the output shows the correct Internet address and the ags: <UP, BROADCAST, NOTRAILERS, RUNNING>.
Note: Make sure the UP ag is displayed.

D.

Are flags correct? If ags are not correct, use the ifconfig command to correct them. If they are correct, go to Step F. Correct ifconfig flag settings. If ifcong returns an incorrect ag setting, re-execute the command with the proper setting. For more information, refer to the ifcong(1M) online man page. Start again with Flowchart 5, as necessary. Any error message returned? If ifcong is not successful, and an error message appears, go to Step G. If no error messages appear, contact your HP representative. Correct problem according to the message received. If you received an error message, make the appropriate corrections stated in the message and then begin this procedure again.

E.

F.

G.

154

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts H.

ifconfig entry in /etc/rc.config.d/netconf? Check that there is an entry in the /etc/rc.config.d/netconf le for your 10/100Base-TX card. Modify the /etc/rc.config.d/netconf file according the IP address you want assigned to the link aggregate. Then run the following command:
/sbin/init.d/net start For more information, refer to the ifcong(1M) online man page. Go back to Flowchart 1 to verify that the problem has been solved.

I.

Chapter 7

155

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 7: ARP Verication

Figure 7-12 Flowchart 7: ARP Verication

Host entry in ARP cache ? Yes

No

Remote host up ? No

Yes

C
Bring up remote host

E D
Entry complete ? Yes No Use arp/ifcong to arp complete entry

F
ping local host

156

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 7: Procedures A.

Host entry in ARP cache? Using arp, check that an entry exists for the remote host in your system's ARP cache. For example:
arp spiff

B.

Remote host up? If there is no ARP cache entry for the remote host, rst check that the remote host is up. If not, the remote host has not broadcast an ARP message, and that probably is why there is no entry in the ARP cache Bring-up remote host. Have the node manager of the remote host bring that system up and start again with Flowchart 1. Entry complete? Perhaps there is an ARP cache entry, but it is wrong or not complete. If the entry is complete, go to Step F. Use arp to complete entry. Using arp, enter the correct Station Address. For more information, refer to the arp(1M) online man page. Also, try running the following commands on the link aggregate which is not working properly. For example, if link aggregate 100 is not working properly execute the following commands:
ifconfig lan100 down ifconfig lan100 up Start again with Flowchart 1.

C.

D.

E.

F.

ping local host. Using ping, do an internal loopback on your own system. In other words, ping your own system.
If the internal loopback is successful, your system is operating properly to the Network Layer (OSI Layer 3). In addition, you know an ARP cache entry for the remote host exists on your system. Start again with Flowchart 1.

Chapter 7

157

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 8: Link Level Loopback Test

Figure 7-13 Flowchart 8: Link Level Loopback Test

8 A
Execute: linkloop to remote host

linkloop successful ? No

Yes

C
Loopback FAILED: Address has bad format

D
Loopback FAILED: Not an individual address

E
Loopback FAILED

F
Correct the link address parameter

G
Choose a different remote host re-execute linkloop.

8 H 7
No linkloop successful ? Yes

I
Check remote hosts connectivity to link aggregate

158

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 8 Procedures A.

Execute: linkloop to remote host. Enter the PPA of your link aggregate and link level address (station address) of the remote host in hexadecimal form (preceded by 0x). Execute lanscan (1M) on the local system to nd the PPA and obtain the link level address (station address) of the remote host. For more information on linkloop, refer to the linkloop(1M) online man page. linkloop successful? If the test was successful, go to Flowchart 1 to verify that the problem is solved. Network connectivity is OK through the Link Layer (OSI Layer 2). If not successful, note which error was returned and continue with this owchart. Loopback failed: Address has bad format. The link level address is not correct. Go to Step F. Loopback failed: Not an individual address. The link level address is not correct. The rst hexadecimal digit has its high order bit set (if the value is equal to or greater than 8, it is set). This means it is a multicast or broadcast address, which is not allowed. The address must be unique to one remote host. Go to Step F. Loopback failed. The remote host did not respond. Go to Step G. Correct the link address parameter. Change the link level address to an allowed value and start again with Flowchart 8. Choose a different remote host; re-execute linkloop. Restart Flowchart 7 using a different remote host. If this does not work, then check the switch conguration to verify the link aggregate on the switch is congured correctly. linkloop successful? If the test was successful, go to Step I. Network connectivity is OK through the Link Layer (OSI Layer 2). If not successful, the problem may be with the remote system. Go to Flowchart 7.

B.

C. D.

E. F.

G.

H.

Chapter 7

159

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts I.

Check remote host's connectivity to link aggregate. Contact the node manager of the remote host. Check that the host is congured correctly and that its network interface is up. If necessary, use Flowchart 1 to verify conguration of the remote host.

160

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 9: Transport Level Loopback Test (using ARPA)

Figure 7-14 Flowchart 9: Transport Level Loopback Test (using ARPA) 9 A
Execute: telnet to remote host

B
Successful ? No

Yes

Stop

C
Execute: ftp to remote host

Successful ? No

Yes Call HP

TCP not congured on local or remote host ? No

G
Yes Congure TCP

Network congested ? No Call HP

Yes Call HP

Chapter 7

161

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 9 Procedures A. B.

Execute: telnet to remote host. Try to establish a telnet connection to the remote host. Successful? If your telnet attempt was successful, stop. The connection is OK through the Transport Layer (OSI Layer 4). Execute: ftp to remote host. Unlike telnet, ftp does not go through a pseudoterminal driver (pty) on your system. This step tests to see if the pty is why telnet failed. Successful? If ftp is successful, you likely have a problem with a pty on your system. Contact your HP representative. TCP not configured on local or remote host? Neither telnet nor ftp will work if TCP is not congured on either side of the connection. Check the /etc/protocols le on both hosts to be sure TCP is installed and congured. Network congested? If TCP is installed on both hosts, do a le transfer to another remote host on the network. Use netstat(1) to check for lost packets.
If network congestion is not the cause, more detailed diagnostics are required. Again, contact your HP representative.

C.

D.

E.

F.

G.

Configure TCP. If necessary, install TCP on either or both hosts. Start again with this owchart.

162

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts

Flowchart 10: Bridge/Gateway Loopback Test

Figure 7-15 Flowchart 10: Bridge and Gateway Loopback Test

10 A
Execute: ping from known good host through gateway to known good host

C B
Successful ? Yes Check route table on problem host and all hosts between

No

E
Examine gateway Correct route tables

1 F
Non-HP 9000 or other vendors. Refer to networking documentation

G
If HP 9000 execute: ifcong on gateway host

Network interface up ?

yes

no I
Congure interface up

Chapter 7

163

Troubleshooting HP Auto Port Aggregation (APA) Software Diagnostic Flowcharts Flowchart 10 Procedures A.

Execute: ping from known good host through gateway to known good remote host. This will test gateway connectivity to the remote network. Successful? If the executing ping returned successfully, the problem may exist in the routing table for the problem host. Go to Step C. Check route table on problem host and all hosts in between. Execute netstat -r to examine a route table. Examine gateway. If the gateway is an HP 9000, go to Step G. If it is not, go to Step F. Correct route tables. Ensure that the proper IP/Internet addresses are assigned in the Destination and Gateway elds. If you are using subnetting, make sure that the destination is what you expect: a network or a host. Go back to Flowchart 1 to verify that the problem is solved. Non-HP 9000 or other vendors. Refer to networking documentation. Refer to the documentation that came with the gateway for additional diagnostics. If HP 9000, execute ifconfig on gateway host. Execute ifcong for all network interfaces on the gateway. Network interface up? If the output from ifcong does not include the UP parameter, the network interface is down. Execute netstat -i to check the status of the network interfaces. An asterisk (*) indicates that the interface is DOWN. If the network interface is DOWN, go to Step I.
If the network interfaces are UP, start again with Flowchart 3. Using Flowchart 3, test all network interfaces on the gateway.

B.

C.

D. E.

F.

G.

H.

I.

Configure interface up. Execute ifcong on each interface to bring it up. Start again with Flowchart 1. Use Flowchart 1 to test all network interfaces on the gateway.

164

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Known Problems and Workarounds

Known Problems and Workarounds

HP 9000 T-600 (T-class server)
HP APA is not supported on the HP 9000 T-600 server.

Known Installation Problems

Installing APA on HP-UX 11.0 without the latest core LAN patch may cause installation failures, and HP APA may not function correctly. See the note (labelled Important) after the Required Patches section for details.

Known Problems with Switches

HP ProCurve Switches When disabling Ciscos Fast EtherChannel protocol on the HP 9000 server, the HP ProCurve switches will block that particular port from further usage. Corrective Action: In order to use the network physical port on the HP 9000 server after disabling Ciscos Fast EtherChannel, you must physically move the connection from the server to the switch to another non-Cisco Fast EtherChannel port on the switch. Cisco Catalyst 5000 Switches Turning off Ciscos Fast EtherChannel on one network physical port on the HP 9000 server may cause the entire link aggregate (the port it is associated with) to be decongured. Corrective Action: This problem can only be corrected by reconguring the switch to not include the port in the link aggregate being congured. Refer to the appropriate switch documentation for details on how to recongure link aggregates. The Catalyst 5000 switch only allows two- or four-port link aggregates. Refer to the Cisco Catalyst 5000 Conguration Guide for more details on these limitations.

Chapter 7

165

Troubleshooting HP Auto Port Aggregation (APA) Software Known Problems and Workarounds A known problem has been xed for HSC 100Base-TX, and PCI 4-port 100Base-TX when interfacing to a Cisco Catalyst 5000 switch [with rmware version 4.5(4)] with ports in Desirable Mode connected to an HP server with ports running HP APA. Sometimes the link aggregations went up and down repeatedly. Corrective Action: For HP-UX 11.0, the HSC 100Base-TX x requires patch PHNE_20420, and the PCI 4-port x is in patch PHNE_20423. You also need the core LAN patch PHNE_20657 (or later). For HP-UX 11i, the 100Base-T x is in patch PHNE_23465. 3Com SuperStack II Switches To interoperate with the switch, disable the Trunk Control Message Protocol (TCMP) on all of the ports that are being used with HP 9000 servers.

166

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing

Using the lanadmin Command for Testing

You can use the lanadmin -X command (uppercase X) with options to make temporary changes to APA.

CAUTION

The lanadmin command does not preserve your changes across reboots. To permanently save your conguration, use SAM or edit the conguration les.

Tasks You Can Perform with the lanadmin Command

You can perform the following tasks using the lanadmin command: Link aggregate specic commands (lanadmin options are in parentheses): Manually congure a link aggregate: Add physical ports to a link aggregate (-X -a portPPA [portPPA...] linkaggregatePPA). Delete physical ports from a link aggregate (-X -d portPPA [portPPA...] linkaggregatePPA). De-congure (clear) a link aggregate (-X -c linkaggregatePPA). Specify load-distribution algorithm (-X -l loaddistalgorithm linkaggregatePPA). Specify hot-standby mode (-X -y on|off linkaggregatePPA). View status of a link aggregate (-x -v linkaggregatePPA). Automatically congure a link aggregate: Enable LACP or FEC on all physical ports. See Port specic commands, below. De-congure a link aggregate.

Chapter 7

167

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing Specify load-distribution algorithm. Specify hot-standby mode. View status of a link aggregate. Port specic commands:

NOTE

Remember that the starting PPA number for link aggregates varies with the operating system you have installed: for HP-UX 10.20, it is 90; for 11.x, it is 100; and 11i, it is 900. The following example uses HP-UX 11.x

Enable/disable LACP on a port (-X -p portPPA LACP_AUTO|MANUAL AnyLinkAggregatePPA). Enable/disable FEC on a port (-X -p portPPA FEC_AUTO|MANUAL AnyLinkAggregatePPA). Specify port priority (-X -t portPPA port_priority AnyLinkAggregatePPA). Specify group capability (-X -g portPPA group_capability AnyLinkAggregatePPA). View status of a port (-x -p portPPA AnyLinkAggregatePPA). Specify port key (-X -k portPPA key AnyLinkAggregatePPA)

lanadmin Syntax
You use the lanadmin command to manage link aggregates and the addition of ports to a link aggregate. The following options are for use along with the -X option: lanadmin [-X -a PortPPA [PortPPA ...] LinkAggregatePPA] [-X -c LinkAggregatePPA] [-X -d PortPPA [PortPPA ...] LinkAggregatePPA] [-X -g PortPPA group_capability AnyLinkAggregatePPA] [-X [-h|-H] AnyLinkAggregatePPA] [-X -k PortPPA admin_key AnyLinkAggregatePPA] [-X -l load_distribution_algorithm LinkAggregatePPA] [-X -o LinkAggregatePPA] [-X -p PortPPA config_mode AnyLinkAggregatePPA]

168

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing [-X -s PortPPA system_priority AnyLinkAggregatePPA [-X -t PortPPA port_priority AnyLinkAggregatePPA] [-X -y on|off LinkAggregatePPA] -a Add ports with the specied portPPAs, to the link aggregate with the specied linkaggregatePPA number. Clear (remove all) ports from a link aggregate with the specied linkaggregatePPA number. Delete ports with the specied PPAs from the link aggregate with the specied linkaggregatePPA number. Set group capability for a port with the specied portPPA. The valid values for group_capability are integral numbers starting at 0. Print out the help screen. Print out the extended help screen. Set Administrative key for an LACP port. Set the load distribution algorithm for a link aggregate with the specied linkaggregatePPA number. The following values are valid for load_distribution_algorithm: LB_CPU Based on the process specic CPU. Appropriate for server-server conguration. LB_MAC Based on the MAC Address of the outgoing packet. Appropriate for server-to-switch conguration. LB_IP Based on the IP Address of the outgoing packet. Appropriate for server-to-router conguration. -o -p Clear Data Flows for a LinkAggregate Set Mode for a port with the specied portPPA number. The following values are valid: LACP_AUTO Turn on IEEE 802.3ad (LACP) FEC_AUTO Turn on Fast EtherChannel (FEC) on the port for automatic port aggregation.

-c -d

-g

-h -H -k -l

Chapter 7

169

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing -s -t MANUAL Turn off Fast EtherChannel (FEC) or IEEE 802.3ad (LACP) on the port. LAN_MONITOR Provides Hot Standby capability.

Set System Priority for an LACP port. Set port priority for the port with the specied PPA Number. You can specify any valid link aggregate PPA number with this option. The valid values for port_priority are integral numbers starting at 0.

-y

Turn on/off hot standby for the link aggregate with the specied linkaggregatePPA number.

The following options will be passed along with the -x option: lanadmin[-x -g PortPPA AnyLinkAggregatePPA [-x [-h|-H] AnyLinkAggregatePPA] [-x -k PortPPA AnyLinkAggregatePPA] [-x -l LinkAggregatePPA] [-x -m AnyLinkAggregatePPA] [-x -n AnyLinkAggregatePPA] [-x -p PortPPA AnyLinkAggregatePPA] [-x -q PortPPA AnyLinkAggregatePPA] [-x -s PortPPA AnyLinkAggregatePPA] [-x -t portPPA AnyLinkAggregatePPA] [-x -v LinkAggregatePPA] [-x -y LinkAggregatePPA -g Display the current group capability for the link aggregate with the specied linkaggregatePPA number. Print out the help screen. Print out the extended help screen. Get administrative and operational key for an LACP port. Display the current load distribution algorithm for the link aggregate with the specied linkaggregatePPA number. View status for all LinkAggregates.

-h -H -k -l

-m

170

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing -n -p -q -s -t -v -y View status for all APA capable ports. Display the present status of a port with the specied portPPA number. Display the present status of a port with the specied portPPA in the extended format. Get system priority for an LACP port. Display the current port priority for the port with the specied portPPA number. View status for a given link aggregate with the specied linkaggregatePPA number. Display Hot Standby value for the link aggregate with the specied linkaggregatePPA number.

lanadmin [-a linkaggregatePPA The following existing option is supported though with a different meaning: -a Display current station address of link aggregate with the specied linkaggregatePPA number.

Using lanadmin from the Command Line

NOTE The examples in this section are for HP-UX 11.0 only.

To obtain additional information on options for the lanadmin command, type: lanadmin -X -H linkaggPPA where linkaggPPA can be any valid link aggregate PPA value. To form a link aggregate of ports automatically, turn on Ciscos Fast EtherChannel protocol on that port. Suppose port #2 needed to be congured automatically: lanadmin -X -p 2 FEC_AUTO 100

Chapter 7

171

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing where 100 is the PPA of the rst link aggregate. When the protocol completes successfully, HP_APA will determine which link aggregate port #2 will best t and add the port there. To congure ports with PPAs 6, 7, 8 and 9 manually into a link aggregate, for example, lan101, use the following command: lanadmin -X -a 6 7 8 9 101

CAUTION

Be careful while using the -a sub-option. This may lead to an invalid link aggregate. This command gives you full control over forming any link aggregate that you want. You can congure ports with PPAs 6, 7, 8, and 9 into a single link aggregate even if they are connected to different switches, which is an invalid conguration, and could lead to problems.

NOTE

If you are using MANUAL mode conguration, ensure that the switch conguration is set for the manual conguration.

Before you can remove a port from an automatically formed link aggregate, you must turn off Ciscos Fast EtherChannel protocol on that port. If a port with a PPA number of 2 belongs to link aggregate lan100 (which has a PPA number of 100), then use one of the following two commands: lanadmin -X -d 2 100 or lanadmin -X -p 2 MANUAL 100

To de-congure a link aggregate, say 103, which has ports with PPAs 6, 7, 8, and 9, use the following commands in succession: lanadmin lanadmin lanadmin lanadmin -X -X -X -X -p -p -p -p 6 7 8 9 MANUAL MANUAL MANUAL MANUAL 103 103 103 103

Or, the following single command will achieve the same result: lanadmin -X -d 6 7 8 9 103 To fully decongure a link aggregate, use the following command:

172

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing lanadmin -X -c 103

CAUTION

Failure to fully decongure a link aggregate may result in some properties being retained in the link aggregate, and subsequently, when a new set of ports are added onto the link aggregate they will inherit old properties of the link aggregate. Thus the new link aggregate formed will no longer be new.

To delete a single port, say 8, from link aggregate 101 the following can be done: lanadmin -X -d 8 101 To also delete 6 and 9: lanadmin -X -d 6 9 101

To decongure the link aggregate 101 completely: lanadmin -X -c 101 This will delete the remaining port, 7, from link aggregate 101, and then clear all the properties from the link aggregate, so that it becomes completely clean.

CAUTION

After all the ports have been deleted from link aggregate 101, (after using, for example, lanadmin -X -d 7 100), failure to use the -c sub-option may result in some properties being retained in link aggregate 101, and subsequently, when a new set of ports is added to link aggregate 101, they will inherit old properties of the link aggregate. Thus the new link aggregate formed will not be new.

Using lanadmin Interactively

If you type the command lanadmin by itself, or with the -t option, the command becomes interactive. The following example illustrates the interactive use of lanadmin:
lanadmin LAN ONLINE ADMINISTRATION, Version 1.1

Chapter 7

173

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing
Tue. May 26, 1998 15:33:05

Copyright 1994 Hewlett Packard Company All rights are reserved. Test Selection mode. lan= LAN Administration menu= Display this menu quit= Terminate the Administration terse= Do not display command menu verbose= Display command menu Enter Command: lan LAN Interface test mode. LAN INterface PPA=6 clear= Clear statistics registers display= display LAN Interface status and statistics registers end = End LAN Interface Administration, return to Test Selection menu= Display this menu ppa= PPA Number of the LAN Interface quit= Terminate the Administration, return to shell reset= Reset LAN Interface to execute its selftest special= Special menu (driver specific menu)

Enter command: ppa Enter PPA Number. currently 6: 100 LAN Interface test mode. LAN Interface PPA=100 clear= Clear statistics registers display= display LAN Interface status and statistics registers end = End LAN Interface Administration, return to Test Selection menu= Display this menu ppa= PPA Number of the LAN Interface

174

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing
quit= Terminate the Administration, return to shell reset= Reset LAN Interface to execute its selftest special= Special menu (driver specific menu) Enter command: display PPA Number=100 Description=lan100 Hewlett-Packard Linkaggregate Interface Type (value)=ethernet-csmacd(6) LinkAggregate Station Address=0x80009e72894 Administration Status (value)=up(1) Operation Status (value)=up(1) LinkAggregate Status (value)=enabled(1) Group Capability=5 LinkAggregate Mode (value)=auto(1) Distribution algorithm (value)=DA based(1) Load Balancing (value)=off(0) Physical Ports=2, 3 and 5 Last Change=100

For link-aggregate MIB statistics, press <Return> to continue

Inbound Octets=0 Inbound Unicast Packets=0 Inbound Non-Unicast Packets=0 Inbound Discards=0 Inbound Errors=0 Inbound Unknown Protocols=0 Outbound Octets=0 Outbound Unicast Packets=0

Chapter 7

175

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing
Outbound Non-Unicast Packets=0 Outbound Discards=0 Outbound Errors=0 Outbound queue Length=0 Specific=0

LAN Interface test mode. LAN Interface PPA=100 clear= Clear statistics registers display= Display LinkAggregate status and statistics registers end= End LAN Interface test mode, return to Test selection mode. menu= Display this menu ppa= PPA Number of the LinkAggregate quit= Terminate the Administration, return to shell reset= Reset LAN Interface to execute its selftest special= Special menu (driver specific menu) Enter command: special Valid LAN Interface PPAs: 4 2 5 3. Driver specific test mode. linkagg= Link Aggregate status port= Port's HP_APA status end= End Driver Specific Test Mode, return to Lan Interface test menu= Display this menu quit= Terminate the Administration, return to shell Enter command: linkagg Number of ports: 4 Ports PPA: 4 2 5 3 Link Aggregation Mod: Automatic Aggregation Group Capability: 51 mode.

176

Chapter 7

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing
Load Balance Mode MAC Address based (LB_MAC) Hot Standby Mode: ON Valid LAN Interface PPAs: 4 2 5 3 Driver specific test mode linkagg= Link Aggregate status port= Port's HP_APA status end= End Driver Specific Test Mode, return to Lan Interface test menu= Display this menu ppa= PPA Number of the LAN Interface quit= Terminate the Administration, return to shell mode.

Enter command: port Port Number: 4 pagp EnabledENABLED ppMyData.deviceId: 0x0060B04BAB84 ppMyData.distReq: LEARNCAP_AGPORT ppMyData.portPriority: 2 ppMyData.sentPortIfIndex: 8 ppMyData.groupCapability: 51 ppMyData.groupIfIndex: 13 ppNoPagpTimerI : 0 ppNoTransTimerQ: 0 ppTHToTATimerS: 0 ppSlowHelloTimerA: 18 ppPartnerCount: 1 ++++++++++++++++++++++++++++++Partner Data++++++++++++++++ PARTNER 0 ppPartnerData.deviceId: 00e01e51dad8 ppPartnerData.distReq: LEARNCAP_AGPORT

Chapter 7

177

Troubleshooting HP Auto Port Aggregation (APA) Software Using the lanadmin Command for Testing
ppPartnerData.portPriority: 128 ppPartnerData.sentPortIfIndex: 19 ppPartnerData.groupCapability: 1 ppPartnerData.groupIfIndex: 0 ppTimerP: 104 ppSlowHelloRequestP: 1 ++++++++++++++++++++++++++++++Partner Data++++++++++++++++ ppAutoMode.myAutoMode: 0 ppAutoMode.yourRequest: 0 ppMySlowHello: 1 portState: PAGP_STATE_UPPAGP portNextState: PAGP_STATE_UPPAGP portNextEvent: PAGP_EVENT_NULL portXmitState: PAGP_XMIT_STATE_SLOW_U6 portXmitNextState: PAGP_XMIT_STATE_SLOW_U6 portXmitNextEvent: PAGP_XMIT_EVENT_NULL Valid LAN Interface PPAs: 4 2 5 3.

Driver specific test mode. linkagg= Link Aggregate status port= Port's HP_APA status end= End Driver Specific Test Mode, return to Lan menuDisplay this menu ppaPPA Number of the LAN Interface quitTerminate the Administration, return to shell Enter command: quit Interface test mode

178

Chapter 7

HP Auto Port Aggregation (APA) Statistics

Appendix A

179

HP Auto Port Aggregation (APA) Statistics HP Auto Port Aggregation Statistics

HP Auto Port Aggregation Statistics

This section describes how link aggregate level statistics are collected and reported. The link aggregate software keeps a counter for each statistic dened in RFC 1213 MIB II. Each counter is set to the negative of the sum of all the physical ports in the link aggregate when it is created. When reporting the value of a statistic, the sum of all the physical ports corresponding statistic counter is added to the link aggregates counter. When a physical port is removed from a link aggregate, each of its statistics is added to the corresponding link aggregate statistic. When a physical port is added to a link aggregate, its current statistics are subtracted from the link aggregates statistics.

NOTE

Ciscos 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. Therefore, they should not be included in the link aggregation level statistics.

180

Appendix A

HP Auto Port Aggregation (APA) Statistics LAN Interface Status Display

LAN Interface Status Display

This section contains a description of the RFC 1213 MIB II statistics elds for LAN interface cards which are displayed on the screen with the display command in lanadmin LAN interface Test Mode. This same command is also used to examine RFC 1213 MIB II statistics for logical link aggregate interfaces. Refer to View Link Aggregate Statistics for a sample output.

Appendix A

181

HP Auto Port Aggregation (APA) Statistics RFC 1213 MIB II

RFC 1213 MIB II

For additional information about the elds described below, refer to RFC 1213. Field Description

Network Management ID A unique ID assigned by the system for the network management of each network interface. Description Type (value) A textual string containing information about the interface. The type of interface, distinguished according to the physical/link protocols, immediately below the network layer in the protocol stack. 10/100Base-TX can have one of the following values: ethernet-csmacd(6), or iso88023-csmacd(7). The following values are for other networking products. MTU Size The size of the largest datagram which can be sent/received on the interface specied in octets. This value is 1500. The speed of the link in bits per second.

Speed in bits per second

Station Address The interface address at the protocol layer immediately below the network layer in the protocol stack. For interfaces which do not have such an address, such as serial line, this object contains an octet string of zero length. Administration Status The desired state of the interface. This parameter is set to up(1) and is not congurable. It will have one of the following values:

Table A-1 up(1) down(2) Ready to pass packets Not operative

182

Appendix A

HP Auto Port Aggregation (APA) Statistics RFC 1213 MIB II Table A-1 (Continued) testing(3) Operation Status In test mode

The current operational state of the interface. This value is the same as the hardware status displayed by lanscan(1M). It will have one of the following values.

Table A-2 up(1) down(2) testing(3) Last Change Ready to pass packets Not operative (card is down) In test mode

The value of SysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last reinitialization of the local network management subsystem, then this object contains a zero value.

Inbound Octets The total number of octets received on the interface, including framing characters. Inbound Unicast Packets The number of subnetwork-unicast packets delivered to a high-layer protocol. Inbound Non-Unicast Packets The number of non-unicast (subnetwork-broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol. Inbound Discards The number of inbound packets that were discarded even though no errors had been detected, to prevent their being delivered to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space.

Inbound Errors The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.

Appendix A

183

HP Auto Port Aggregation (APA) Statistics RFC 1213 MIB II Inbound Unknown Protocols

The number of packets received via the interface which were discarded because of an unknown or unsupported protocol. The total number of octets transmitted out of the interface, including framing characters.

Outbound Octets Outbound Unicast Packets

The total number of packets that higher-level protocols requested be transmitted to a subnetwork-unicast address, including those that were discarded or not sent.

Outbound Non-Unicast Packets

The total number of packets that higher-level protocols requested be transmitted to a non-unicast (a subnetwork-broadcast or subnetwork-multicast) address, including those that were discarded or not sent. The number of outbound packets that were discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. The number of outbound packets that could not be transmitted because of errors. The length of the output packet queue (in packets).

Outbound Discards

Outbound Errors Outbound Queue Length

184

Appendix A

HP Auto Port Aggregation (APA) Statistics View Link Aggregate Characteristics Using lanscan

View Link Aggregate Characteristics Using lanscan

The lanscan command now includes the ports in a link aggregate. Use lanscan -q to list the physical ports attached to all the link aggregates in the system.

lanscan Output
Following are examples of the various outputs from the lanscan command. lanscan on systems without HP APA installed remains the same. # lanscan Table A-3
Hardware Path 10/4/8.1 8/0/1/0 8/0/2/0 8/4/2/0 8/8/2/0 8/4/1/0 8/8/1/0 10/12/6 Station Address 0x080009B7C158 0x0060B0220001 0x0060B0220002 0x0060B04B2B43 0x0060B04BAB85 0x0060B04B2B42 0x0060B04BAB84 0x080009F0165D Crd In# 6 0 1 3 5 2 4 7 Hdw State UP UP UP UP UP UP UP UP Net-Interface NamePPA lan6 snap6 lan0 snap0 lan1 snap1 lan3 snap3 lan5 snap5 lan2 snap2 lan4 snap4 lan7 snap7 NM ID 1 2 3 4 5 6 7 8 MAC Type ETHER ETHER ETHER ETHER ETHER ETHER ETHER ETHER HP-DLPI Support Yes Yes Yes Yes Yes Yes Yes Yes DLPI Mjr# 119 119 119 119 119 119 119 119

lanscan on the same machine, with link aggregation enabled. In this example, the link aggregate lan100 is formed of ports lan2, lan3, lan4 and lan5. The output suppresses the information on lan2, lan3, lan4 and lan5, since these ports cannot be used by themselves any longer. You can only see lan100.

Appendix A

185

HP Auto Port Aggregation (APA) Statistics View Link Aggregate Characteristics Using lanscan # lanscan Table A-4
Hardware Path 10/4/8.1 8/0/1/0 8/0/2/0 10/12/6 LinkAgg0 LinkAgg1 LinkAgg2 LinkAgg3 LinkAgg4 Station Address 0x080009B7C158 0x0060B0220001 0x0060B0220002 0x080009F0165D 0x0060B04BAB84 0x000000000000 0x000000000000 0x000000000000 0x000000000000 Crd In# 6 0 1 7 100 101 102 103 104 Hdw State UP UP UP UP UP DOWN DOWN DOWN DOWN Net-Interface NamePPA lan6 snap6 lan0 snap0 lan1 snap1 lan7 snap7 lan100 snap100 lan101 snap101 lan102 snap102 lan103 snap103 lan104 snap104 NM ID 1 2 3 8 10 11 12 13 14 MAC Type ETHER ETHER ETHER ETHER ETHER ETHER ETHER ETHER ETHER HP-DLPI Support Yes Yes Yes Yes Yes Yes Yes Yes Yes DLPI Mjr# 119 119 119 119 119 119 119 119 119

lanscan with verbose option. This will print some port-aggregate specic information. Below, only a section of lanscan output is shown. In this example, lanscan prints out information for lan100. The information includes the list of ports belonging to the link aggregate (lan2, lan3, lan4, and lan5). lanscan -v

Table A-5
-----------------------------------------------------------------Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI Path Address In# State NamePPA ID Type Support Mjr# Link Agg 0x0060B04BAB84 100 UP lan100 snap100 10 ETHER Yes 119 Extended Station Address 0x0060B04BAB84 LLC Encapsulation Methods IEEE HPEXTIEEE SNAP ETHER NOVELL

Driver Specific Information hp_apa ........................................................................... Hardware Crd Hdw Net-Interface NM MAC HP-DLPI DLPI Driver Path In# State NamePPA ID Type Support Mjr# Name 8/8/1/0 4 UP lan4 snap4 7 ETHER Yes 119 btlan4 8/4/1/0 2 UP lan2 snap2 6 ETHER Yes 119 btlan4 8/8/2/0 5 UP lan5 snap5 5 ETHER Yes 119 btlan4 8/4/2/0 3 UP lan3 snap3 4 ETHER Yes 119 btlan4

186

Appendix A

HP Auto Port Aggregation (APA) Statistics View Link Aggregate Characteristics Using lanscan lanscan with the option -q (extended print-ppa). lanscan -q
6 0 1 7 100 101 102 103 104

4 2 5 3

Appendix A

187

HP Auto Port Aggregation (APA) Statistics View Link Aggregate Characteristics Using lanscan

188

Appendix A

Load Balancing and Data Flow Algorithms

Appendix B

189

Load Balancing and Data Flow Algorithms Supported Load Balancing and Data Flow Algorithms

Supported Load Balancing and Data Flow Algorithms

The algorithms described below only apply to outbound data transfer. Inbound Load Balancing and Data Flow Distribution are strictly determined by the link partner and have no affect on the outbound algorithms. In addition, although each of these algorithms can be used in all supported congurations, they may not all provide the same load on each of the physical ports in the link aggregate. Therefore, HP prefers you use the algorithm that's recommended for each supported conguration.

190

Appendix B

Load Balancing and Data Flow Algorithms Packet Ordering

Packet Ordering
Each of the algorithms below guarantees that they will not introduce any severe ordering problems within a specic data ow. This is required to make sure that the performance is not degraded signicantly as a result of turning on one of the algorithms. Further, all packets for a specic data ow will always ow out through the same physical port (the only exception is CPU based distribution) until the data ow is aged out of the distribution table (see below). This means that in order to generate simultaneous load on each of the physical ports in a link aggregate, multiple data ows must be started over the link aggregate.

Appendix B

191

Load Balancing and Data Flow Algorithms Load Balancing Algorithm

Load Balancing Algorithm

The Load Balancing algorithm is described as a simple three step process. 1. Data Flow Lookup The Data Flow Distribution algorithm (next section) determines an index into a hash table which includes the physical port the data ow should be forwarded out of. 2. Data Flow Physical Port Assignment If the hash index for the data ow has not been assigned a physical port (the entry is NULL), then a physical port in the link aggregate is assigned to that specic hash index. The physical port is selected on a Round Robin basis. 3. Aging Data Flows Over time each data ow is checked to determine if it is still active. If the data ow has not been active in the last 30 seconds, it's specic hash index is cleared (aged out). If the data ow restarts after being cleared from the hash table it will be re-assigned a new physical port on a Round Robin basis.

192

Appendix B

Load Balancing and Data Flow Algorithms Data Flow Distribution Algorithms

Data Flow Distribution Algorithms

Listed below are the three supported Data Flow Distribution algorithms, plus the Hot Standby mode. Each algorithm is briey explained and the recommended conguration for the specic algorithm is also listed. For examples on conguring the algorithms, please refer to the earlier chapters on conguration in this guide.

NOTE

Each of the supported Data Flow Distribution algorithms must be set on the specic link aggregate prior to adding any physical ports.

Destination MAC address The Destination MAC address based algorithm uses the least signicant byte of the link level destination MAC address, of the data ow, as an index into a table of 256 possible entries. If the entry is NULL, then a physical port is selected from the link aggregate on a Round Robin basis and assigned to the index. The physical port selected will be used to send packets for the duration of the specic data ow. This is the default algorithm for all link aggregates. Recommended Conguration: Server-to-Switch.

IP address The IP address based algorithm uses the least signicant bytes of the source and destination IP address, of the data ow, as an index into a table of 256 possible entries. The same processing that occurs for destination MAC distribution is used if the entry is NULL. Recommended Conguration: Server-to-Router.

LB_PORT TCP/UDP Port-based Algorithm The TCP/UDP Port-based algorithm uses the TCP/UDP source and destination port numbers to distribute trafc across the ports in a Link Aggregate. This algorithm is recommended for use when connecting two HP 9000 servers in a back-to-back conguration. Recommended conguration: Server-to-Server

Appendix B

193

Load Balancing and Data Flow Algorithms Data Flow Distribution Algorithms Hot Standby Hot Standby ON mode uses one primary link in the link aggregate to send all outbound trafc on. Therefore, when this mode is enabled there is no load balancing across the network physical ports in the link aggregate. If the primary link goes down (for example, cable disconnect) then all the trafc on the primary link is automatically switched to a secondary link in the same link aggregate. The primary and secondary links are determined by the Port Priority of the network physical ports in the link aggregate. The network physical port with the highest Port Priority is used as the primary link. If there are multiple network physical ports with equal Port Priorities then the APA software will pick one of the ports. This conguration is recommended for servers that need highly available network interfaces. CPU No longer recommended when using Server-to-Server. See LB_PORT The CPU based algorithm uses the processor index that the data ow is being serviced on, as an index into a table of 256 possible entries. Therefore, this algorithm relies on the CPU scheduler to determine how data ows will be distributed across different physical ports. This conguration should not be used on Uni-Processor systems as only one physical port in the link aggregate will be used.

NOTE

Since this algorithm relies on the CPU scheduler to determine where the packets for a specic data ow will be sent, it is possible for a specic data ow to move from one physical port to another during the lifetime of the data ow. This is possible because if one CPU becomes loaded, one or more processes may need to be migrated to another CPU. This can lead to a specic data ow sending data out one interface and then switching to another due to an overloaded CPU. This may cause a temporary ordering problem, but should not result in any signicant or prolonged performance problems.

194

Appendix B

HP Auto Port Aggregation (APA) Resources

Appendix C

195

HP Auto Port Aggregation (APA) Resources

In addition to this manual, use the following resources to maintain and administer HP APA/9000.

196

Appendix C

HP Auto Port Aggregation (APA) Resources HP-UX Manual Reference Pages (man pages)

HP-UX Manual Reference Pages (man pages)

While installing, conguring, or troubleshooting HP APA, you may need to refer to any of the following online manual reference pages (man pages) for useful HP-UX operating system or HP APA commands. To display a man page, type the following at the system prompt: man <command name>. For example, man arp. arp(1M) displays and modies the Internet-to-station address mapping tables used by the Address Resolution Protocol. hosts(4) is a database that contains a single line entry for each host name entry. ifcong(1M) assigns an address to a network interface, and congures and displays network parameters. ioscan(1M) scans system hardware, usable I/O system devices, or kernel I/O system data structures as appropriate, and lists the results. lanadmin(1M) resets or reports the status of the LAN card. lanscan(1M) displays information about LAN cards that are successfully bound to the system. linkloop(1M) veries network connectivity through the Data Link Layer (OSI Layer 2). netfmt(1M) formats common tracing and logging binary les. netstat(1) provides network statistics and information about network connections. nettl(1M) logs network events and traces packets as they enter and exit the 10/100Base-TX driver. ping(1M) veries network connectivity through the Network Layer (OSI Layer 3) and reports the round-trip time of communications between the local and remote hosts. route(1M) adds and deletes entries to the network routing table. sam(1M) congures networking software. swinstall(1M) loads software lesets onto 10.x and later systems. swverify(1M) veries software installation. 197

Appendix C

HP Auto Port Aggregation (APA) Resources Error Messages

Error Messages
HP APA comes with an online message catalog that is used to report networking problems. You must use the nettl logging and tracing utility to display the probable cause and action for a message.

198

Appendix C

HP Auto Port Aggregation (APA) Resources Logging Messages

Logging Messages
The HP network physical port and the HP APA software use the nettl(1M) logging and tracing facility supplied with HP-UX. You may access the logging and tracing utility using either the graphical user interface (GUI) version or the command line interface. Features of the GUI version, which are now a part of your HP 9000 system, include: An interface which guides you through logging and tracing tasks. An interface which allows you to create and format reports. The capability to collect logging and tracing subsystem-specic information. Report screens which are updated instantaneously with current logging and tracing information by the subsystem. Context-sensitive on-line help.

To access the GUI version of the logging and tracing utility, run the command: nettladm See the nettladm(1M) man page for information on using the GUI version, or the nettl(1M) manual (man) page for information on using the command line interface. There are three levels of logging At link aggregate level. At Ciscos FEC level. At IEEE 802.3ad LACP level

Listed below are some examples using the command line interface. To turn on all logging at link aggregate level, use: nettl -log 0xf -e HP_APA To turn on all logging at Ciscos FEC level, use nettl -log 0xf -e HP_APAPORT

Appendix C

199

HP Auto Port Aggregation (APA) Resources Logging Messages To turn on all logging at IEEE 802.3ad level, use nettl -log 0xf -e HP_APALACP To examine the log le with cause and action descriptions: netfmt -v -f /var/adm/nettl.LOG00 | more To examine just the log messages in the log le, use: netfmt -f var/adm/nettl.LOG00 To check network logging and tracing status, use: nettl -status To start Ciscos FEC tracing to the le /tmp/tracele.TRC0, use nettl -traceon all -entity HP_APAPORT -file /tmp/tracefile To stop Ciscos FEC tracing, use nettl -traceoff all -entity HP_APAPORT To start LACP tracing to the le /tmp/tracele.TRC0, use nettl -traceon all -entity HP_APALACP -file /tmp/tracefile To stop LACP tracing, use nettl -traceoff all -entity HP_APALACP To format the tracele into the le /tmp/traceout, use: nettl -f /tmp/tracefile.TRC0 > /tmp/traceout Refer to the netfmt(1M) man page for further information about this card and how to create a lter for trace formatting.

200

Appendix C

HP Auto Port Aggregation (APA) Resources Contacting Your HP Representative

Contacting Your HP Representative

If you have no service contract with HP, you may follow the procedure described below, but you will be billed accordingly for time and materials. If you have a service contract with HP, document the problem as a Service Request (SR) and forward it to your HP representative. Include the following information where applicable: A description of the problem. Describe the events leading up to and including the problem. Attempt to describe the source and symptoms of the problem. Your description should include: HP-UX commands; communication subsystem commands; job streams; result codes and messages; and data that can reproduce the problem. You should also provide a network map with the host name, IP/Internet address, and station address of each system connected with the HP system. Illustrate as clearly as possible the context of any message(s). Prepare copies of information displayed at the system console and user terminal. Obtain the version, update, and x information for all software. To check the HP APA version number, execute what vmunix and look for the keyword, hp_apa. To check the version of your kernel, execute uname -r. This allows HP to determine if the problem is already known and if the correct software is installed at your site. Prepare copies of all the following les: /etc/rc.config.d/netconf /etc/rc.config.d/hp_apaconf /etc/rc.config.d/hp_apaportconf /etc/lanmon/lanconfig.ascii Execute the dmesg command and record messages about the status of the HP APA card. Execute the lanscan -v command and record the output.

Appendix C

201

HP Auto Port Aggregation (APA) Resources Contacting Your HP Representative Execute the display command of the lanadmin diagnostic on the HP APA interface and record the output. Record the troubleshooting owchart number and step number where you are unable to resolve the problem. Record all error messages and numbers that appear at the user terminal and the system console. Save all network log les. Make sure that ERROR and DISASTER log classes are enabled when log les are collected. Prepare the formatted output and a copy of the log le for your HP representative to further analyze. Prepare a listing of the HP-UX I/O conguration you are using for your HP representative to further analyze. Use the ioscan(1M) command to help collect this information. Prepare a list of your switch trunking conguration related to this problem. Try to determine the general area within the software where you think the problem exists. Refer to the appropriate reference manual and follow the guidelines on gathering information for that product. Document your interim, or workaround, solution. The cause of the problem can sometimes be found by comparing the circumstances in which it occurs with the circumstances in which it does not occur. Create copies of any Internet or HP APA/9000 link trace les that were active when the problem occurred for your HP representative to further analyze. In the event of a system failure, a full memory dump must be taken. Use the HP-UX utility savecore(1M) to save a core dump. Send the output to your HP representative.

202

Appendix C

HP Auto Port Aggregation (APA) Resources What Manuals are Available

What Manuals are Available

The following documents are available: HP Auto Port Aggregation Quick Installation Guide This document summarizes the installation, conguration, verication, and troubleshooting of the HP Auto Port Aggregation product. HP Auto Port Aggregation Release Notes This document provides summarized information about the HP Auto Port Aggregation product, and late-breaking information that is not in either the Quick Installation or Users guides. It is an online only le located on your system in /opt/networkdocs or on the worldwide web at http://www.docs.hp.com

Appendix C

203

HP Auto Port Aggregation (APA) Resources Software Product Numbers and Filesets

Software Product Numbers and Filesets

Part numbers for the HP APA product are as follows: Software: J4240AA = HP APA Software Product for HP-UX 11.x J5080AA = LAN Monitor for HP-UX 10.20

The HP Auto Port Aggregation software includes the following products and lesets: Product Filesets: APA-KRN APA-RUN APA-INIT APA-FORMAT SAM-APA APA-LM

204

Appendix C

Glossary
A
aggregate A group. In this product a group of four ports makes one link aggregate. There can be 50 link aggregates per computer. aggregation See aggregate. APA Auto Port Aggregation Auto Port Aggregation (APA) HPs software product that allows grouping up to four ports into an aggregate to boost performance and provide port fail-over.

H
Hot Standby availability A method of providing high

HSC High Speed Connect

L
LACP Link Aggregation Control Protocol

LAN Local Area Network LB_IP Internet Protocol-based algorithm for server-to-router congurations. LB_MAC MAC-based algorithm for server-to-switch congurations (this is the default algorithm). See Load Balancing and Data Flow Distribution Algorithm for details. LB_PORT TCP/UDP port-based algorithm for server-to-server (back-to-back) congurations link aggregate A logical grouping of one or more physical ports into a single fat-pipe. This term is used to describe LACP, Manual, or PAgP (Cisco Fast EtherChannel) created logical ports. link aggregation See link aggregate

F
fail-over group a logical grouping of one or more physical ports formed by LAN Monitor. The failover group is used as an alternative if the primary link fails. Fast EtherChannel (FEC) The proprietary name of Ciscos port aggregation product. When referring to FEC mode, it indicates use of PAgP on a link. FEC See Fast EtherChannel FEC_AUTO The automatic conguration mode of FEC. ow A sequence of MAC frames between a pair of hosts where all of the MAC frames form part of the same conversation between that pair of hosts.

linkaggPPA The PPA or logical card instance number of a specic link aggregate. load balancing A method of distributing trafc across the network physical ports in a link aggregate. Unicast and multicast trafc is distributed across the network physical ports in a link aggregate. Broadcast trafc is always sent out the rst network physical port in a link aggregate

G
group capability An integer value used to determine which network physical ports can be aggregated into a common link aggregate.

Glossary

205

Glossary MANUAL

M
MANUAL The default mode of port conguration. Can be performed by editing two conguration les or by using SAM. MAC MIB Media Access Control Management Information Base

automatically determines a bidirectional connection between two network physical ports. port priority An integer value used to determine which network physical port will be used as the primary port in a link aggregate in hot standby mode. PPA See physical point of attachment

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 specic network port (adapter card) and a LAN device.

S
SAM System Administration Management Server-to-Router Server-to-Server See LB_IP. See LB_PORT.

Server-to-Switch See LB_MAC.

P
PAgP See Port Aggregation Protocol. PCI Peripheral Component Interconnect physical point of attachment A unique integer identier for each network physical port installed on a server. port The communications channel formed when you attach a network cable between a network physical port and a LAN device. port aggregate See link aggregate. port aggregation See link aggregate Port Aggregation Protocol (PAgP) The proprietary port aggregation protocol, developed by Cisco Systems Inc., which

206

Glossary