Using HP Auto Port Aggregation APA

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.

2

Legal NoticesThe information in this document is subject to change without notice.

Hewlett-Packard makes no warranty of any kind with regard to thismanual, including, but not limited to, the implied warranties ofmerchantability and fitness for a particular purpose. Hewlett-Packardshall not be held liable for errors contained herein or direct, indirect,special, incidental or consequential damages in connection with thefurnishing, performance, or use of this material.

Warranty. A copy of the specific warranty terms applicable to yourHewlett-Packard product and replacement parts can be obtained fromyour local Sales and Service Office.

Use of this manual and flexible disk(s) or tape cartridge(s) supplied forthis pack is restricted to this product only. Additional copies of theprograms may be made for security and back-up purposes only. Resale ofthe programs in their present form or with alterations, is expresslyprohibited.

Copyright Notices. ©copyright 1999-2002, Hewlett-Packard Company,all rights reserved.

Reproduction, adaptation, or translation of this document without priorwritten permission is prohibited, except as allowed under the copyrightlaws.

Trademark Notices Cisco, Catalyst, and Fast EtherChannel areregistered trademarks of Cisco Systems Incorporated.

Contents

3

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

2. Overview of Installation and ConfigurationPrepare to install the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Install the HP APA software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Planning Your HP APA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Choose Configuration Method: SAM or Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Setting Port Aggregation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Modifying Default Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

APA Parms for Link Aggregates — hp_apaconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49APA and LAN Monitor Parms for Physical Ports — hp_apaportconf . . . . . . . . . . . . 53

3. Configuring APA Using SAMConfiguring HP APA Using SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Setting Port Aggregation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Configuring an FEC_AUTO Mode Link Aggregate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Using SAM to Configure a MANUAL Mode Link Aggregate . . . . . . . . . . . . . . . . . . . . 67

4. Configuring APA by Editing FilesEditing Configuration Files for All APA Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Edit Files for MANUAL, FEC, or LACP Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

MANUAL port configuration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Contents

4

FEC_AUTO port configuration mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80LACP port configuration mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Use of /sbin/init.d/hpapa stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Verify Status of the Link Aggregates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Verify Status of a Physical Port (HP-UX 11.0 and 11i Only). . . . . . . . . . . . . . . . . . . . . 85

5. What is LAN Monitor?LAN Monitor Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

LAN Monitor Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Configuring LAN Monitor Failover Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Binary File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

LAN Monitor Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97lanqueryconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97lanapplyconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98lancheckconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98landeleteconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

6. Using ServiceGuard with HP APARequirements for Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

7. Troubleshooting HP Auto Port Aggregation (APA) SoftwareTroubleshooting Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104What Happens during Start Up? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

MAC Addresses for Link Aggregates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Diagnostic Flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Flowchart 1: Network Level Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Flowchart 2: Network Physical Port Connections/LED Test . . . . . . . . . . . . . . . . . . 113Flowchart 3: Network Physical Port Configuration Test . . . . . . . . . . . . . . . . . . . . . 117Flowchart 4: Network Physical Port Configuration Test . . . . . . . . . . . . . . . . . . . . . 124Flowchart 4A: Network Physical Port Configuration Test . . . . . . . . . . . . . . . . . . . 127Flowchart 5: Link Aggregate Configuration Test . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Flowchart 5A: Manual Configuration Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Flowchart 5B: PAgP Configurations Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Flowchart 5C: LAN Monitor Configuration Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Flowchart 5D: LACP Configuration Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Contents

5

Flowchart 6: Network Configuration Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Flowchart 7: ARP Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Flowchart 8: Link Level Loopback Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Flowchart 9: Transport Level Loopback Test (using ARPA) . . . . . . . . . . . . . . . . . . 161Flowchart 10: Bridge/Gateway Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Known Problems and Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165HP 9000 T-600 (T-class server). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Known Installation Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Known Problems with Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Using the lanadmin Command for Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Tasks You Can Perform with the lanadmin Command . . . . . . . . . . . . . . . . . . . . . . 167lanadmin Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Using lanadmin from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Using lanadmin Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

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

lanscan Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

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

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

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

Contents

6

Tables

7

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

Tables

8

Figures

9

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

Figures

10

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

Chapter 1 11

1 What is HP Auto PortAggregation?

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

Chapter 112

HP Auto Port Aggregation FeaturesLink Aggregates, often called “trunks,” provide a logical grouping of 2 ormore physical ports into a single “Fat-Pipe” with a single IP address. Twoprimary features are automatic link failure detection and recovery aswell as optional support for load balancing of network traffic across all ofthe links in the aggregation. This allows you to build large bandwidth“logical” links into the server that are highly available and completelytransparent to the client and server applications.

APA on HP-UX 11.0 and 11i supports Fast and Gigabit Ethernet withautomatic fault detection and recovery as well as load balancing ofnetwork traffic, while APA on HP-UX 10.20 only supports the automaticlink failure detection and recovery feature.

HP-UX 11.0 and 11i-based HP APA link aggregates will interoperatewith switches and routers using:

• Cisco’s proprietary Fast EtherChannel (FEC/PAgP) technology.

• IEEE 802.3ad link aggregation control protocol (LACP).

• Manually configured port trunks.

FDDI and Token Ring links, as well as Fast and Gigabit Ethernet, canalso be configured as LAN Monitor failover groups on both HP-UX 10.20and 11.0, but with no load balancing of network traffic. This enables youto use APA throughout their environment to provide Single System HighAvailability for all networking components.

To summarize, APA offers you a comprehensive solution to createlightning fast and highly available network server connections withminimal IT support costs. APA enables this with four key benefits:

• Automatic link failure detection and recovery in case of networkfailures. A link aggregate will continue to operate as long as there isat least one port operating.

• Scalable high performance link aggregates using Fast or GigabitEthernet and APA's efficient Load Balancing Algorithms. Supportedload balancing algorithms include:

— IP-based — Server-to-Router.

— Port-based — Server-to-Server.

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

Chapter 1 13

— MAC-based — Server-to-Switch.

• Fault Management and Isolation with HP's MIB Monitor and Nettllogging facilities.

• Lower IT costs with automated configuration and management toolsusing the IEEE 802.3ad standard and HP's System AdministrationGUI (SAM)

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

Chapter 114

Summary of APA and LAN MonitorCapabilitiesThe following table summarizes the capabilities of APA and LANMonitor.

Table 1-1 APA and LAN Monitor Features

HP APA(on HP-UX 11.x)

inFEC_AUTO,

LACP_AUTO,MANUAL1 Modes


inLAN_MONITOR

Mode

LANMonitor(HP-UX10.20)

Integrationwith MC/SG inMANUAL1 and

FEC_AUTOModes Only

Min# of Ports/ LinkAgg

FEC_AUTO (2)LACP_AUTO (2)MANUAL (1)

2 2 2

Max# of Ports/ LinkAgg

FEC_AUTO (4)MANUAL (4)LACP_AUTO(32)

32 32 4

PrimaryPorts /LinkAgg

N/A 1 1 Min(2) Max(4)

StandbyPorts /LinkAgg

N/A 31 31 Min(1) Max(3)

Max# ofLinkAggs /System

50 50 5 50

LoadBalancing(LB) or HotStandby (HS)

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

LB2

(Ethernet only)and HS

HS only(no LB)

LB2

(Ethernet only)and HS

MIB MonitorSupport

Yes Yes Yes Yes


Chapter 1 15

BUSES PCI, HSC, HP-PB3,core100/1000BT

PCI, HSC,HP-PB3,Core100BT PCI,HSC, HP-PB,Core10/100/1000BT

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

LINKS4 100BT, Gigabit 100BT, Gigabit,FDDI, TokenRing5

100BT,Gigabit,FDDI,HP-PBTokenRing5

100BT, Gigabit(also Token Ring& FDDI whenMC/SG willcoexist withLAN Monitor;Future Feature)

WorkstationSupport

Yes Yes No Yes

Switches/Hubs

HP, Cisco, 3COM All Types All Types HP, Cisco,3COM (HotStandby Modeworks with alltypes ofswitches/hubs)

Start PPA# 100 (11.0), 900 (11i) 100 (11.0), 900(11i)

90 100 (11.0), 900(11i)

MC/SGVersion

A.11.09 Future Feature No support A.11.09

SAM / Edit SAM/Edit files lan*confcommands

lan*confcommands

Edit files

Table 1-1 APA and LAN Monitor Features (Continued)


inFEC_AUTO,



inLAN_MONITOR

Mode



FEC_AUTOModes Only


Chapter 116

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 linkaggregates.

2. Load Balancing is configurable on Ethernet links only. Hot Standbyis the only choice for FDDI and Token Ring. Load Balancing is foroutbound traffic only.

3. HP-PB 100BT adapters can’t be mixed with other non-HP-PB 100BTadapters.

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 linkaggregate.

InstantIgnition

Yes Yes No N/A

Full andHalf-Duplex6

Yes Yes Yes Yes

Table 1-1 APA and LAN Monitor Features (Continued)


inFEC_AUTO,



inLAN_MONITOR

Mode



FEC_AUTOModes Only

What is HP Auto Port Aggregation?Required Software

Chapter 1 17

Required SoftwareThe 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 patchesrelating to HP-UX 11i-based systems.

Table 1-2 Minimum Patches

Driver 10.20 11.0

10/100BT

PCI 1-port 100BT (RJ45), (btlan5) PHNE_20892 PHNE_24006

PCI 1-port 100BT (AUI,BND,RJ45)(btlan6)

N/A PHNE_22245

PCI 4-port 100BT (btlan) PHNE_20422 PHNE_214007

PCI 100BT/SCSI Combo Card(btlan3)

PHNE_23195 (800)PHNE_22405 (700)

HP-UX 11.0Additional CoreEnhancement relof January 2000

Core PCI 10/100BT (btlan3) PHNE_23195 (800)PHNE_22405 (700)

HP-UX 11.0Additional CoreEnhancement relof January 2000

EHSC/HSC 1-port, 2-port 100BT(btlan4)

PHNE_22216 *PHNE_22461

HP-PB 10/100BT (btlan1) PHNE_23921 PHNE_23982

Gigabit

PCI 1000SX (gelan) March 2000 release March 2000release

PCI 1000BT (gelan) N/A N/A

EHSC/HSC 1000SX (gelan) March 2000 release March 2000release

What is HP Auto Port Aggregation?Required Software

Chapter 118

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. Onlythen will the product initialize and become usable.

FDDI

PCI FDDI (fddi4) June 2000 release June 2000 release

EHSC/HSC FDDI (fddi3) PHNE_20010 March 2000release

HP-PB FDDI (fddi) PHNE_24024 March 2000release

Token Ring

PCI Token Ring June 2000 release June 2000 release

HP-PB Token Ring June 2000 release June 2000 release

DLPI/LANC

DLPI/LANC (lan_dlpi.c, lanc*) *PHNE_23862(800)*PHNE_23863(700)

*PHNE_24413

*Required patch.

Table 1-2 Minimum Patches (Continued)

Driver 10.20 11.0

What is HP Auto Port Aggregation?Supported Switches

Chapter 1 19

Supported SwitchesThe following switches have been certified to work with HP Auto PortAggregation software. Other switches that support manual trunkingmay 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 allswitches.

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

Chapter 120

Supported LAN Cards and Functions: HP-UX11.xHP-UX 11.x-based HP APA supports the following network adaptercards:

• All Hewlett-Packard HP-PB, HSC, and PCI 10/100Base cards (bothFX and TX).

• All Hewlett-Packard HSC and PCI 1000Base cards (both Base-T andSX).

• 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 ofports per LinkAgg;

— PAgP and Manual mode – 4.

— LACP and LAN Monitor mode – 32.

• System Administration Manager (SAM) is supported on HP-UX 11.xonly.

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

Chapter 1 21

Supported LAN Cards and Functions: HP-UX10.20 OnlyHP-UX 10.20 based HP APA supports the following network adaptercards:

• 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 serverand 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.

What is HP Auto Port Aggregation?HP APA Configuration Examples

Chapter 122

HP APA Configuration ExamplesHere are some points to remember when configuring HP APA:

• HP APA combines two to four physical link ports into one logicalaggregation of links when using FEC_AUTO or MANUAL linkaggregation. This gives the link aggregation a theoretical bandwidthof four times that of a single physical link. When using anLACP_AUTO link aggregation, as many as 32 physical links may beused 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 aggregationmust be configured for the same speed and duplex. (Note: EISA100BT devices are not supported.)

• The link aggregation has one or more IP addresses assigned to it inthe /etc/rc.config.d/netconf file.

• The physical ports in the link aggregation will use the same MACaddress.

• HP APA distributes the outbound network traffic across the physicallinks in the link aggregation using a load balancing algorithm.

Effective APA load balancing requires many simultaneous, activeclient connections. See Figure 1-1 for a good example. It is theconnections that are distributed across the physical links. One clientconnection will have its traffic sent on one physical link. Theconnection is defined by the load balancing algorithm.

• The link partners (switches, routers, or remote servers) completelycontrol inbound load balancing.

• There are three load balancing algorithms from which to choose:MAC-address-based-, IP-address-based-, andTCP/UDP-port-address-based load balancing algorithms. SeeAppendix B: “Load Balancing and Data Flow Algorithms” for moreinformation.

• HP APA link aggregations provide for migrating the network trafficon a failed physical link in the aggregation to the remainingoperational links in the aggregation.

What is HP Auto Port Aggregation?HP APA Configuration Examples

Chapter 1 23

• The link partner (the switch, router, server) connected to the linkaggregation may inhibit the usefulness of HP APA in someenvironments. See the following examples.

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

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

Chapter 124

Enterprise Intranet Client/ServerEnvironmentEnterprise client/server environments are good candidates for HP APAlink aggregations.

Figure 1-1 Enterprise Intranet Client/Server Environment

Points for Figure 1-1:

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

Chapter 1 25

• Requires a switch capable of trunking/load balancing.

• Many clients produce many connections. This makes effective use ofthe HP APA outbound network traffic distribution algorithms. HPAPA's MAC address based load balancing algorithm would be a goodchoice. The IP address and TCP/UDP port address load balancingalgorithm would also work effectively in this configuration.

• The switch typically provides good inbound traffic distribution. Mostswitches use the data packet's source MAC address, or a combinationof the packet's source and destination MAC addresses, to provideinbound load balancing.

• Depending on the network traffic bandwidth requirements, two tofour 100BT interfaces or two to four Gigabit interfaces can be used inan FEC link aggregation. With LACP, up to 32 interfaces can beused in the link aggregation. This allows for bandwidth scalability asnetwork loads increase as the organization grows.

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

Chapter 126

Internet or Large Enterprise EnvironmentsUsing RoutersHP APA link aggregation can be successfully used in certainenvironments employing routers. Care must be taken because aparticular router may not have a load balancing capability. Additionally,switches employed between the server employing HP APA and the


Chapter 1 27

router inject another level of complexity that should be analyzed beforedetermining the environment is a candidate for HP APA linkaggregations.

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 serverprovides trunking/load balancing using an IP address based loadbalancing algorithm.


Chapter 128

• Assumes there will be many TCP/UDP client connections. The HPAPA IP address based load balancing algorithm would provideeffective outbound network traffic load balancing. So would theTCP/UDP port address based algorithm. The MAC address basedalgorithm should NOT be used since all packets arriving at theserver would contain the same source and destination MACaddresses.

Figure 1-3 Switch between Router and Server

Points for Figure 1-3: (Switch between router and server)

• The switch in the configuration shown in Figure 1-3 may presentproblems. Switches typically use a MAC address based loadbalancing algorithm. This may make the switch a bottleneck pointsince the packets from the router and from the server will contain


Chapter 1 29

the same source and destination MAC addresses, thus defeating theload balancing algorithm for both inbound and outbound data at theserver.

• This may be acceptable if the load balancing of inbound traffic to theserver is not a concern and the link between the switch and therouter has greater bandwidth capacity that the server's linkaggregation. Example: the server's link aggregation is composed of100BT links and the link between the switch and the router is aGigabit link.

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

Chapter 130

Server to Server (Back to Back)Server to server aggregations can be accomplished by directly connectingthe physical ports in one server's link aggregation to the physical ports inthe other server's link aggregation.

Figure 1-4 Server to Server (Back to Back)


• This configuration requires that there be many TCP/UDP clientconnections between the servers for load balancing to be effective.HP APA's TCP/UDP port based load balancing algorithm should beused.

• Depending on the network traffic bandwidth requirements, two tofour 100BT interfaces or two to four Gigabit interfaces can be used inan FEC link aggregation. With LACP, up to 32 interfaces can beused in the link aggregation. This allows for bandwidth scalability asnetwork loads increase as the organization grows.

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

Chapter 1 31

Hot Standby - High AvailabilityHP APA Hot Standby mode link aggregations provide high availabilitynetwork access via a primary link and standby link.

Figure 1-5 Hot Standby - High Availability


• The Hot Standby primary link carries network traffic until it or itslink partner fails. In that event the standby link takes over theresponsibility for delivering network traffic. If the primary isconfigured with a higher port priority than the standby, then when itrecovers it will resume being the active link delivering the networktraffic. If the port priorities are the same, the standby link willcontinue 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 orhub.

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

Chapter 132

• Dual switches/hubs as used in Figure 1-5 are not required. But dualswitches/hubs provide a more reliable network environment byremoving single points of failure. Both switches/hubs must be on thesame subnet.

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

Chapter 1 33

Server to Server with Switch (notrecommended)A server to server HP APA link aggregation configuration with a switchbetween the servers will not work as intended.

Figure 1-6 Server to Server with Switch (not recommended)


• The switch will nullify any load balancing of network traffic providedby HP APA.

• The switch will use a MAC address based load balancing algorithm.Since the servers' link aggregations will have fixed MAC addresses,the switch will not load balance, and thus will only transmit data onone physical link.

What is HP Auto Port Aggregation?LAN Monitor Configuration Examples

Chapter 134

LAN Monitor Configuration ExamplesPoints to remember:

• LAN Monitor failover groups are the same as HP APA Hot Standbylink aggregates except for some additional features:

— LAN Monitor periodically exchanges APA packets between thelinks making up the failover group. This allows for betterdetection of non-operational links in the failover group.Therefore a successful linkloop between the devices is arequirement for configuration.

— LAN Monitor is configured with LAN Monitor configurationcommands. See the chapter “What is LAN Monitor?” for details.SAM is not used to configure 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. Oneport will be the primary port, and the others will be standby ports.Network traffic will be sent and received on the primary port (theport with the highest HP APA port priority). In the case where it orits link partner fails, the traffic will be migrated to one of the standbyports. When the primary port link recovers, the network traffic willbe migrated back to the primary port. Sometimes, it is desirable tohave the network traffic remain on the standby after the failure andrecovery of the primary. To achieve this, set the HP APA portpriorities 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 failovergroup. However, all the devices in the failover group must be of onetype, 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 commonMAC address.

• LAN Monitor supports the use of an HP APA link aggregation as adevice in the failover group. This allows for increased bandwidthand load balancing in a failover group.

What is HP Auto Port Aggregation?LAN Monitor Configuration Examples

Chapter 1 35

The following examples show some uses for LAN Monitor failover groupsbased on the points above.

What is HP Auto Port Aggregation?LAN Monitor Failover Group

Chapter 136

LAN Monitor Failover GroupLAN Monitor failover groups provide high availability network accessvia a primary link and standby link.

Figure 1-7 LAN Monitor Failover Group


• Dual switches/hubs as used in Figure 1-7 are not required. But dualswitches/hubs provide a more reliable network environment byremoving single points of failure. If two switches/hubs are used, thenthere must be a data path between them allowing them to be on thesame subnet.

• A linkloop between the devices in the failover group is required forsuccessful configuration and operation of the failover group.

• LAN Monitor failover groups can be connected to any switch or hub.

What is HP Auto Port Aggregation?LAN Monitor Failover Group

Chapter 1 37

• The failover group primary link carries network traffic until it or itslink partner fails. In that event the standby link takes over theresponsibility for delivering network traffic. When the primary linkrecovers it will resume being the active link delivering the networktraffic.

• The primary and standby links must both be the same type of device,100BT, Gigabit, FDDI, or Token Ring.

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

Chapter 138

LAN Monitor Failover Group Using LinkAggregations to Increase BandwidthTo increase the network bandwidth of a LAN Monitor failover group onecan use link aggregations as the primary and standby devices.

Figure 1-8 LM Failover Group Using Link Agg to Increase Bandwidth


• Any HP APA link aggregation, except Hot Standby, can be used as adevice in the LAN Monitor failover group. This allows for increasingthe bandwidth of the group device through load balancing across thephysical links making up the aggregation.

• The standby link does not have to be a link aggregation. It can be asingle physical link of the same type as used in the link aggregation.

• Dual switches as used in Figure 1-8 are not required. But dualswitches provide a more reliable network environment by removingsingle points of failure. If two switches are used, then there must bea data path between them.

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

Chapter 1 39


• LAN Monitor failover groups using link aggregates are restricted toswitches supported by HP APA link aggregates.


• The primary and standby links must both be the same type of device,100BT or Gigabit.

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

Chapter 140

LAN Monitor with FDDI or Token RingLAN Monitor supports FDDI and Token Ring devices.

Figure 1-9 LAN Monitor with FDDI or Token Ring




• The primary and standby links must both be the same type of device,FDDI or Token Ring.

Chapter 2 41

2 Overview of Installation andConfiguration

Overview of Installation and ConfigurationPrepare to install the software

Chapter 242

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 yourPATH 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 stepsfor patch installation as you do for product installation shown next.

Overview of Installation and ConfigurationInstall the HP APA software

Chapter 2 43

Install the HP APA softwareSkip this section if you ordered product option 0D1--preinstallation.

1. To install the software from the installation media, run the swinstallprogram 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 canclick the Source Depot Path button and a list of valid choices will bedisplayed.

5. Highlight the HP APA software: J4240AA (HP-UX 11.0 or 11i) orJ5080AA (HP-UX 10.20).

6. Choose Mark for Install from the “Actions” menu to choose theproduct to be installed.

7. Choose Install from the “Actions” menu to begin product installationand display the Install Analysis Window.

8. Activate the OK button in the Install Analysis Window when theStatus field displays a “Ready” message.

9. Activate the YES button at the Confirmation Window to confirm thatyou want to install the software. swinstall loads the fileset, runs thecontrol scripts for the filesets, and builds the kernel. Estimated timefor processing: 3 to 5 minutes. When the status field indicates“Ready,” a Note Window opens. Activate the OK button on the NoteWindow to reboot the system.

Overview of Installation and ConfigurationPlanning Your HP APA Configuration

Chapter 244

Planning Your HP APA ConfigurationBefore configuring HP APA the following information should bedetermined and gathered:

• Determine which network physical interfaces installed in the HP9000 server can be used for the HP APA link aggregation. Onlythose interfaces supported by HP APA can be used. All 100BTinterfaces except the EISA 100BT interfaces are supported. AllGigabit interfaces are supported. Note that the interfaces in a linkaggregation must be of the same type: all 100BT devices or all1000BASE-x devices. All the devices in the link aggregation must beconfigured for the same speed and duplex.

• Determine the number of physical interfaces required in the linkaggregation. Use present and future bandwidth requirements todetermine this number.

• Determine the mode of the link aggregate, FEC_AUTO,LACP_AUTO, or MANUAL. This is determined by the capabilities ofthe switch or link partner to which the link aggregate physicalinterfaces will be connected. The switch or link partnerdocumentation will need to be consulted to verify which modes itsupports. If both an automatic and a manual mode are available, itis recommended that the automatic mode be used.

• Determine the load balancing algorithm to use. LB_MAC, thedefault, works well in most configurations.

Then for each link aggregation to be configured make a listcontaining:

— The PPA number of the linkagg (100 will be lan100).

— The configuration mode of the aggregation (FEC_AUTO,LACP_AUTO, MANUAL).

— The PPA numbers of the ports that will be in the linkaggregation. And for each port:

Overview of Installation and ConfigurationPlanning Your HP APA Configuration

Chapter 2 45

— The group capability of the port if the link aggregation willuse FEC_AUTO mode. This should match the value specifiedfor the group capability of the link aggregate. The easiestway to choose this is to take the ppa number of the linkaggand use it as the group capability.

— The key of the port if the link aggregation will useLACP_AUTO mode. This should match the value specifiedfor the key of the link aggregate. The easiest way to choosethis is to take the ppa number of the link aggregate and useit as the port key.

— The port's priority if the link aggregation mode will beMANUAL and will use Hot Standby. The port with thehighest priority will be the primary port.

• The load balancing algorithm to use, unless it is a MANUAL linkaggregation that is to use Hot Standby.

• The group capability if the link aggregate will use FEC_AUTOmode. The easiest way to choose this is to take the ppa number of thelinkagg and use it as the group capability.

• The key if the link aggregate will use LACP_AUTO mode. Theeasiest way to choose this is to take the ppa number of the linkaggand use it as the key.

• The IP address and subnet mask of the aggregate.

Overview of Installation and ConfigurationChoose Configuration Method: SAM or Editing

Chapter 246

Choose Configuration Method: SAM or EditingUsing the GUI-based system admin manager (SAM) is the recommendedmethod for configuring HP APA. Using SAM produces less errors andsaves your data permanently.

Configuration doesn’t require a reboot to take effect.

1. To permanently save your configurations, you can either:

• use the GUI-based system admin manager (SAM). To use SAM,refer to the instructions in “Configuring APA Using SAM” in thisdocument for details, and then do the steps for verifying linkaggregates;

or

• edit the configuration files using an editor such as “vi.” Refer to“Configuring APA by Editing Files” in this document forinstructions on editing the two configuration files for APA andtwo additional files for LAN Monitor:

— APA and LAN MONITOR:/etc/rc.config.d/hp_apaconf and/etc/rc.config.d/hp_apaportconf

— LAN Monitor on HP-UX 11.0 and 11i requires thehp_apaportconf plus:/etc/rc.config.d/netconf and/etc/lanmon/lanconfig.ascii.

2. If you are configuring more than one of the four, port-configurationmodes described here, minimize the number of stops (which caninterrupt traffic on existing link aggregates) by editing allconfiguration files first. You will then only need to run one series ofhplm stop (optional); hpapa stop; hpapa start; hplm start(optional) to activate the link aggregates and (optionally) failovergroups.

Overview of Installation and ConfigurationChoose Configuration Method: SAM or Editing

Chapter 2 47

CAUTION You can also use the lanadmin command from the HP-UX command lineprompt to make temporary changes to APA. However, if you change somevariables using the lanadmin command, those changes are not preservedacross reboots. See “Using the lanadmin Command for Testing” fordetails on the lanadmin command.

Overview of Installation and ConfigurationSetting Port Aggregation Modes

Chapter 248

Setting Port Aggregation ModesPorts can be aggregated by setting HP APA to any of the following portaggregation modes:

• Manual Mode — Use this mode to configure HP 9000 LinkAggregates if the server connects to a switch that only supportsmanual configuration. This mode requires the switch to support LinkAggregation. In the event of a link failure, APA automaticallymigrates the data flow(s) from the failed link to another link in theaggregation

• Auto w/ PAgP — Use this mode when configuring Link Aggregateson the HP 9000 when connected to a switch that supports Cisco’sFast EtherChannel protocol (PAgP). This mode requires the switch tosupport the PAgP (FEC) protocol. In the event of a link failure, PAgPautomatically migrates the data flow(s) from the failed link toanother link in the aggregation.

• Auto w/ LACP — Use this mode to automatically aggregate HP9000 links connected to IEEE 802.3ad (LACP) supported switches.This mode requires the switch to support the LACP protocol. In theevent of a link failure, LACP automatically migrates the data flow(s)from the failed link to another link in the aggregation.

• LAN Monitor — Use this mode when configuring fail-over groupson the HP 9000. In the event of a link failure, the LAN Monitorsoftware automatically migrates the data flow from the primary linkto one of the standby links in the “Link Aggregate.” Fail-over groupsdo not support MC/SG. The mode does not strictly require the switchto support Link Aggregation, although some configurations mayrequire the switch to support Link Aggregation.

After you have installed HP APA, it will be in MANUALport-configuration mode until you configure it to aggregate eligible ports.Auto aggregation also requires that you configure your switch to enableCisco’s Fast EtherChannel (FEC) or IEEE 802.3ad Link AggregationControl Protocol (LACP). If your switch only supports manual portconfiguration, you must also set the server ports to MANUAL mode (thedefault configuration). Then edit the server’s configuration files asexplained in this document.

Overview of Installation and ConfigurationModifying Default Configuration Parameters

Chapter 2 49

Modifying Default Configuration ParametersBeginning with the December 2001 release the HP APA defaultport-configuration mode is set to MANUAL mode; it does notautomatically aggregate ports. If you do not modify the defaultconfiguration, nothing will happen-- you have to modify and save theconfiguration by either using SAM or editing the files that are listedhere. Refer to “Configuring APA Using SAM” or “Configuring APA byEditing Files” to set up or modify these files. SAM does not configureLAN Monitor.

HP Auto Port Aggregation uses two configuration files as follows.

• /etc/rc.config.d/hp_apaconf — This file contains configurationvalues for link aggregates.

• /etc/rc.config.d/hp_apaportconf — This file containsconfiguration values for specific physical ports that are supported byHP APA.

LAN Monitor uses the hp_apaportconf file plus the following files:

• /etc/rc.config.d/netconf

• /etc/lanmon/lanconfig.ascii

The following subsections describe the configurable parameters in eachof these files.

APA Parms for Link Aggregates — hp_apaconf

Following are the descriptions of the parameters within the/etc/rc.config.d/hp_apaconf file.

NOTE Each of the supported parameters must be set on a specific linkaggregate prior to aggregating any physical ports.

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


Chapter 250

• HP_APA_DEFAULT_PORT_MODE—The default way to configure linkaggregates is now through MANUALport-configuration mode--formerlyit was automatic (FEC_AUTO). Ensure that switch ports and serverports are set to the same trunking mode (MANUAL or AUTO),duplexity, and speed. Disable PAgP or LACP on any switch ports notintended to be used with APA.

There are two variables governing the mode of ports:

— HP_APA_DEFAULT_PORT_MODE in the/etc/rc.config.d/hp_apaconf file. Sets the default APAconfiguration mode for all ports. The recommended mode isMANUAL. The APA product is shipped with the entry in thehp_apaconf file set to: HP_APA_DEFAULT_PORT_MODE=MANUAL.

— HP_APAPORT_CONFIG_MODE in the/etc/rc.config.d/hp_apaportconf file. Sets the APAconfiguration mode for a single port. This variable takesprecedence.

A port's mode will be set to the value ofHP_APA_DEFAULT_PORT_MODE, unless its mode is specified usingvariable HP_APAPORT_CONFIG_MODE. HP_APA_DEFAULT_PORT_MODEsets the mode for all ports but HP_APAPORT_CONFIG_MODE canoverride it.

• Example 1: Suppose the configuration mode of a port is not set withHP_APAPORT_CONFIG_MODE and HP_APA_DEFAULT_PORT_MODE is notset. This results in the port's configuration mode being FEC_AUTO.

Example 2: Suppose the configuration mode of a port is not set withHP_APAPORT_CONFIG_MODE and HP_APA_DEFAULT_PORT_MODEis setto MANUAL. This results in the port's configuration mode beingMANUAL.

Example 3: Suppose the configuration mode of a port is set toFEC_AUTO via HP_APAPORT_CONFIG_MODE andHP_APA_DEFAULT_PORT_MODE is set to MANUAL. This results in theport's configuration mode being FEC_AUTO.

• HP_APA_INTERFACE_NAME— Name of link aggregate (lan100, lan101,and so on).

• HP_APA_LOAD_BALANCE_MODE — Defines the Load Balancing modefor the specified link aggregate (HP_APA_INTERFACE_NAME). Thesupported values are as follows:


Chapter 2 51

— LB_MAC

This algorithm uses a portion of the destination MAC address todetermine how data flows are distributed across physical ports ina link aggregate. This option is recommended forServer-to-Switch configurations.

— LB_IP

This algorithm uses a portion of the source and destination IPaddress to determine how data flows are distributed acrossphysical ports in a link aggregate. This option is recommendedfor Server-to-Router configurations.

— LB_PORT

This algorithm uses the TCP/UDP source and destination portnumbers to distribute traffic across the ports in a LinkAggregate. This algorithm is recommended for use whenconnecting two HP 9000 servers in a back-to-back configuration.

It is now the recommended option for this purpose instead ofLB_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 networkphysical ports can be aggregated into a common PAgP linkaggregate. Set the group capability to be the same for all networkphysical ports in the same Link Aggregate. Ports going to differentlink aggregates should have different group capabilities. Must matchthe value of HP_APAPORT_GROUP_CAPABILITY in the/etc/rc.config.d/hp_apaportconf file.

• HP_APA_KEY

LACP_AUTO only. An integer value that determines which networkphysical ports can be aggregated into a common LACP linkaggregate. Set the key to be the same for all network physical portsin the same Link Aggregate. Ports going to different link aggregatesshould have different keys. Must match the value ofHP_APAPORT_KEY in the /etc/rc.config.d/hp_apaportconf file.

• HP_APA_HOT_STANDBY


Chapter 252

Configure a Link Aggregate for Hot Standby Mode. This parameteris mutually exclusive with the HP_APA_LOAD_BALANCE parameter. Inaddition HP_APA_HOT_STANDBY takes precedence over theHP_APA_LOAD_BALANCE parameter. The permissible values are onand off. The Default Is off .

For HP APA releases prior to March 2002:

CAUTION Only use lowercase when specifying on/off forHP_APA_HOT_STANDBY in /etc/rc.config.d/hp_apaconf. Uppercasewill cause errors.

• HP_APA_MANUAL_LA

Manually set ports for the specified link aggregate. The ports shouldbe specified with PPA numbers. Each port should be separated by acomma (,).

• Reserved values

The HP_APA_INIT_ARGS are reserved by HP; they are not customerchangeable:

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 PPAs2, 3, and 4:

NOTE Ensure that the server and switch are set to the samemode--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”


Chapter 2 53

APA and LAN Monitor Parms for Physical Ports —hp_apaportconf

Following are the descriptions of the parameters within the/etc/rc.config.d/hp_apaportconf file.

• HP_APAPORT_CONFIG_MODE

Set the configuration mode for a physical port. The supported valuesare listed below:

— LACP_AUTO — IEEE 802.3ad Link Aggregation Control Protocol(LACP) will be started on the port.

— FEC_AUTO — Cisco’s Fast EtherChannel (FEC) will be started onthe port.

— MANUAL— Cisco’s FEC or IEEE 802.3ad LACP will be disabled onthe port, and it must therefore be manually added or removedfrom a specific link aggregate. This is the default configurationmode for all ports which support the HP APA product.

— LAN_MONITOR — Cisco’s FEC or IEEE 802.3ad LACP will bedisabled 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 whichnetwork physical ports can be aggregated into a common PAgP linkaggregate. Set the group capability to be the same for all networkphysical ports in the same Link Aggregate. Ports going to differentlink 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.config.d/hp_apaconf file.

• HP_APAPORT_PRIORITY

Set the port priority for the port. The port priority determines whichport in a link aggregate will be the primary interface when the linkaggregate is set to hot standby mode (HP_APA_HOT_STANDBY=on).

The default port priority is 0.


Chapter 254

• HP_APAPORT_KEY

For LACP_AUTO only. An integer value that determines whichnetwork physical ports can be aggregated into a common LACP linkaggregate. Set the key to be the same for all network physical portsin the same Link Aggregate. Ports going to different link aggregatesshould have different keys. Must match the value of HP_APA_KEY inthe /etc/rc.config.d/hp_apaconf file.

The default administrative key is 0.

• HP_APAPORT_SYSTEM_PRIORITY

For LACP_AUTO only. Set the port system priority for the portspecified by HP_APAPORT_INTERFACE_NAME. The system priority givescontrol to the system to resolve waiting ports to be added in alinkagg.

The default system priority is 0.

• Reserved values

The HP_APAPORT_INIT_ARGS are reserved by HP; they are notcustomer 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”

Chapter 3 55

3 Configuring APA Using SAM

Configuring APA Using SAMConfiguring HP APA Using SAM

Chapter 356

Configuring HP APA Using SAMUsing the GUI-based system admin manager (SAM) is the recommendedmethod for configuring HP APA. Using SAM produces less errors andsaves your configuration data permanently. Configuration doesn’trequire a reboot to take effect.

SAM permanently saves HP APA configuration values in two files:

• /etc/rc.config.d/hp_apaconf and

• /etc/rc.config.d/hp_apaportconf

Setting Port Aggregation Modes

You can use the System Administration Manager (SAM) to configure HPAPA so that it will aggregate ports in any of the following portaggregation modes:

• FEC or LACP Port Aggregation Modes

• Manual Port Aggregation Mode

After you have installed HP APA, it will be in MANUALport-aggregation mode unless you configure it to automatically aggregateeligible ports.

NOTE HP APA also requires that you configure your switches’ trunking mode(AUTO or MANUAL) to match the mode being used on the server: Cisco’sFast EtherChannel (FEC), IEEE 802.3ad Link Aggregation ControlProtocol (LACP), or MANUAL mode.

NOTE SAM cannot be used to configure LAN Monitor. Refer to the chapter on“Configuring APA by Editing” for editing configuration files for all APAmodes and the chapter “What is LAN Monitor?” for configuring LANMonitor mode.

Configuring APA Using SAMConfiguring an FEC_AUTO Mode Link Aggregate

Chapter 3 57

Configuring an FEC_AUTO Mode LinkAggregateWhen configuring an automatic link aggregate (FEC_AUTO orLACP_AUTO) with SAM, the link aggregation characteristics areconfigured first, followed by the port's modes and characteristics.

The following example configures an FEC_AUTO link aggregate. Thesame process can be used to configure an LACP_AUTO link aggregate bysubstituting 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 PortAggregation. A window like the one in Figure 3-1 appears. TheNetworking and Communications screen List pulldown menu(Figure 3-1) displays either:

• Link Aggregates supported by HP APA. This is the list of allavailable Link Aggregates in the system.


Chapter 358

• Network Physical Ports that Support HP APA. This is the list ofall physical ports in the system that support HP APA.

Figure 3-1 Displaying Link Aggregates


Chapter 3 59

3. Click on the linkagg to be configured. Then from the Actionspulldown menu select the Configure Link Aggregate option. Awindow similar to Figure 3-2 will appear.

Figure 3-2 Configuring Link Aggregates


Chapter 360

4. Click on the Advanced Options button to get a window similar toFigure 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 thegroup capability for the linkagg. The group capability should be anon-zero number that differs from the group capability of any otherlinkagg. It should also match the group capability that will beassigned later to the ports belonging in the linkagg. Then click theOK button. Click the OK button in the Configure Link Aggregatewindow.

7. Select the Network Physical Ports that Support HP APA option fromthe List pulldown menu. The displayed port configuration mode(column 7 in Figure 3-4) determines the mode for the linkaggregation. Note: in Figure 3-4 the configuration mode for the ports


Chapter 3 61

that support APA is, by default, set to MANUAL mode. Also note:you may need to adjust the horizontal scroll bar to see all thewindow's fields.

Figure 3-4 Network Physical Ports Supporting APA

8. For each port to be configured in the automatic link aggregation,verify that the port's configuration mode is set to the desired mode,FEC_AUTO. Check that the port's group capability matches thegroup capability that was previously assigned to the linkaggregation. If changes are needed proceed to the next step.

9. Highlight the port to configure by clicking on the port designated byits PPA.


Chapter 362

10. In the Actions pull down menu, select the Modify Network PhysicalPort Attributes option. You will see a window like the one inFigure 3-5.

Figure 3-5 Modify Network Physical Port Attributes

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


Chapter 3 63

12. Continue with steps 8 through 11 to configure the remaining ports tobe in the aggregate. Figure 3-6 shows a sample FEC_AUTOconfiguration using ports 1 and 2 with group capability of 7.

Figure 3-6 Example of Configured Link Aggregates

13. From the List pulldown menu, select the Link Aggregates Supportedby HP APA option. A window similar to Figure 3-7 will appear. Notethat the linkagg may not have a status of UP since APA and theswitch or link partner may not have completed the negotiationrequired for forming the link aggregation. Continue with the nextstep in either case.


Chapter 364

Figure 3-7 Status of Configured Link Aggregate is UP


Chapter 3 65

14. Click once again on the link aggregate being configured. Then fromthe Actions pulldown menu, , select the Configure Link Aggregateoption. A window like that in Figure 3-8 will appear.



Chapter 366

15. Fill in the desired IP address and subnet mask to be used for thelinkagg. Then click on the OK button. A window like that inFigure 3-9 will appear.

Figure 3-9 Link Aggregate with Configured IP Address

16. If the linkagg has a status of UP, then configuration is complete.Exit SAM. Verify that the proper ports are configured in the properlink aggregation with the lanscan -q command.

17. If the linkagg is DOWN: If the switch has not been configured, thenexit SAM and configure the switch. The APA configuration will havebeen permanently saved and can be modified later if needed. If theswitch has been configured, verify the switch and APA configurationand make the required changes to bring them into agreement. If thelink aggregate still does not form correctly, proceed to thetroubleshooting section of this guide.

Configuring APA Using SAMUsing SAM to Configure a MANUAL Mode Link Aggregate

Chapter 3 67

Using SAM to Configure a MANUAL ModeLink AggregateWhen configuring a manual link aggregate with SAM, the first step isconfiguring the port’s modes and characteristics, followed by the linkaggregate characteristics.

Log in as root. At the HP-UX system prompt:

1. Type sam

2. Double-click Networking and Communications, and then Auto PortAggregation. A window like the one in Figure 3-10 appears. TheNetworking and Communications screen List pulldown menu(Figure 3-10) displays either:

• Link Aggregates supported by HP APA. This is the list of allavailable Link Aggregates in the system.


Chapter 368

• Network Physical Ports that Support HP APA. This is the list ofall physical ports in the system that support HP APA.

Figure 3-10 Choices in List Pulldown are Link Aggregates and NetworkPhysical Ports

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


Chapter 3 69

support APA is, by default, set to MANUAL mode. Also note: youmay need to adjust the horizontal scroll bar to see all the window'sfields.

Figure 3-11 Network Physical Ports Supporting APA

4. For each port to be configured in the manual link aggregate, verifythat the port's configuration mode is set to the desired mode,MANUAL. Check that the port's group capability matches the groupcapability that was previously assigned to the link aggregation. Ifchanges are needed proceed to the next step.

5. Highlight the port to configure by clicking on the port designated byits PPA.


Chapter 370

6. In the Actions pulldown menu, select the Modify Network PhysicalPort Attributes option. You will see a window like the one inFigure 3-12.

Figure 3-12 Modify Network Physical Port Attributes

7. In this window make the necessary changes and click on the OKbutton.

8. Continue with steps 4 through 7 to configure the remaining ports tobe in the aggregate.


Chapter 3 71

9. To configure the link aggregate characteristics, select the LinkAggregates supported by HP APA option from the List pulldownmenu. A window like Figure 3-13 will appear.

Figure 3-13 Display Link Aggregates to Configure

10. Click on the link aggregate being configured. Then, from the Actionspulldown menu, select the Configure Link Aggregate option. Awindow similar to Figure 3-14 will appear.


Chapter 372


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


Chapter 3 73

12. Click on the Advanced Options button to get a window similar toFigure 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 windowsimilar to Figure 3-16 will appear.

Figure 3-16 Adding Ports to or Deleting Ports from Link Aggregate


Chapter 374

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 thelinkagg, lan100.

Figure 3-17 Adding Ports to or Deleting Ports from Link Aggregate


Chapter 3 75

17. Click the OK button to see the Configure Link Aggregates window(Figure 3-18) with all the linkagg information filled in.

Figure 3-18 Configured Link Aggregates Display


Chapter 376

18. Clicking the OK button brings us back to the original window(Figure 3-19. It now shows the link aggregate lan100 configured as aMANUAL mode linkagg.

Figure 3-19 Link Aggregate Displays with Status UP

19. The link aggregate is configured. Configure the next MANUAL modelinkagg, or if none, exit by choosing the Exit option from the Filepulldown menu.

Chapter 4 77

4 Configuring APA by EditingFiles

Configuring APA by Editing FilesEditing Configuration Files for All APA Modes

Chapter 478

Editing Configuration Files for All APA ModesThis chapter is for configuring the three modes associated with portaggregation. To configure LAN Monitor mode, refer to the chapter “Whatis LAN Monitor?” in this guide.

Beginning with the December 2001 release, HP Auto Port Aggregation(HP APA) is shipped with the default port-configuration mode set toMANUAL. The value in the /etc/rc.config.d/hp_apaconf file isHP_APA_DEFAULT_PORT_MODE=MANUAL. This allows you to then specifyany of the four port-configuration modes before activating the product.

For release-specific information, refer to the release notes on your systemin /opt/networkdocs or on the worldwide web at:http://www.docs.hp.com .

If you are configuring more than one of the four, port-configurationmodes described here and in the next chapter, minimize the number oftimes you have to run hpapa stop (which can interrupt traffic onexisting link aggregates) by editing all configuration files first. You willthen 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.

Configuring APA by Editing FilesEdit Files for MANUAL, FEC, or LACP Modes

Chapter 4 79

Edit Files for MANUAL, FEC, or LACP Modes

1. Ensure that the switch ports and the HP LAN card ports are set tothe same APA (or “trunking”) mode (MANUAL or AUTO), speed, andduplexity.

2. Run lanadmin interactively if you need to verify that all HP LANcard ports intended for aggregation are connected to the LAN.

3. When numbering the PPAs of your link aggregations, use thefollowing 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 configuration mode

Edit the following values in the /etc/rc.config.d/hp_apaconf file.Example: to put lan1 and lan2 into link aggregate 900 with MAC-basedload-balancing:

HP_APA_INTERFACE_NAME[0]=lan900HP_APA_LOAD_BALANCE_MODE[0]=LB_MACHP_APA_MANUAL_LA[0]=”1,2”

Edit the following values in the /etc/rc.config.d/hp_apaportconf file.If this is the first-time configuration, the CONFIG_MODE is already set tothe default of MANUAL:

HP_APAPORT_INTERFACE_NAME[0]=lan1HP_APAPORT_CONFIG_MODE[0]=MANUALHP_APAPORT_INTERFACE_NAME[1]=lan2HP_APAPORT_CONFIG_MODE[1]=MANUAL


Chapter 480

If you are done editing all configuration modes, activate theconfiguration 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 configuration mode

Optional--set load balancing and group capability in the/etc/rc.config.d/hp_apaconf file. Example: to configure link aggregate900 with MAC-based load-balancing and a group capability of 10, enter:

HP_APA_INTERFACE_NAME[0]=lan900HP_APA_LOAD_BALANCE_MODE[0]=LB_MACHP_APA_GROUP_CAPABILITY[0]=10 {*see Note 1}

Edit the following values in the /etc/rc.config.d/hp_apaportconf file.Example: to put lan1 and lan2 into link aggregate 900:

HP_APAPORT_INTERFACE_NAME[0]=lan1HP_APAPORT_GROUP_CAPABILITY[0]=10 {*see Note 1}HP_APAPORT_CONFIG_MODE[0]=FEC_AUTOHP_APAPORT_INTERFACE_NAME[1]=lan2HP_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 linkaggregate to which it belongs. Ports going to different link aggregatesshould have different group capabilities.}

If you are done editing all configuration modes, activate theconfiguration 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

LACP port configuration mode

Optional--set load balancing and apaport key in the/etc/rc.config.d/hp_apaconf file. Example: to configure link aggregate900 with MAC-based load-balancing and a key of 10, enter:

HP_APA_INTERFACE_NAME[0]=lan900HP_APA_LOAD_BALANCE_MODE[0]=LB_MACHP_APAPORT_KEY[0]=10 {*see Note 2}

Edit the link aggregate, the apaport key, and the configuration mode inthe /etc/rc.config.d/hp_apaportconf file. Example: to put lan1 andlan2 into link aggregate 900:

HP_APAPORT_INTERFACE_NAME[0]=lan1HP_APAPORT_KEY[0]=10 {*see Note 2}HP_APAPORT_CONFIG_MODE[0]=LACP_AUTOHP_APAPORT_INTERFACE_NAME[1]=lan2HP_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 towhich it belongs. Ports going to different link aggregates should havedifferent keys.}

If you are done editing all configuration modes, activate theconfiguration 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}

Configuring APA by Editing FilesUse of /sbin/init.d/hpapa stop

Chapter 482

Use of /sbin/init.d/hpapa stopThe /sbin/init.d/hpapa stop command does not remove the protocolsrunning on the link aggregate. The hpapa stop command:

1. Clears all link aggregates.

2. Clears LAN_MONITOR fail-over groups but does not remove thebinary file.

3. Stops AUTO protocol negotiation on single ports.

4. Does not remove the upper-layer protocols (for example, IP) runningover the link aggregate.

Configuring APA by Editing FilesVerify Status of the Link Aggregates

Chapter 4 83

Verify Status of the Link AggregatesConfiguration doesn’t require a reboot to take effect. HP APAconfiguration is complete when you can verify which link aggregateshave been formed. Depending on your configuration, there may be 0 ormore link aggregates configured.

To verify which link aggregates have been configured, type:

lanscan orlanscan -v for a long listing

The column heading titled Hardware Path will contain the valueLinkAgg for logical link aggregates. The column heading Hdw State willshow the state of the link aggregates. The state should be UP or DOWN.UP indicates that the link aggregation is operational. DOWN indicatesthat the link aggregate has been initialized by the product but notconfigured.

(HP-UX 11.0 and 11i only) To verify that a link aggregate was formedcorrectly, find the linkaggPPA by doing a lanscan and using one of thevalues in the column titled Crd In# which corresponds to a linkaggregate. 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 toshow status, while those used with upper case -X are used to setconfiguration parameters or modes.

For example, to verify the physical ports associated with linkaggPPA101, type:

lanadmin -x -v 101

To verify all the physical ports in all configured link aggregates, type:

lanscan -q

This will list the Card Instance number for each physical port as well asthe link aggregates. Data similar to the following output will bedisplayed (the example following is for HP-UX 11.0):

Configuring APA by Editing FilesVerify Status of the Link Aggregates

Chapter 484

100 5 6 8 7101102103

This output says that there are 4 ports in link aggregate 100. The 4ports are lan5, lan6, lan8, and lan7.

If no link aggregates are formed, refer to the Troubleshooting section.

Configuring APA by Editing FilesVerify Status of a Physical Port (HP-UX 11.0 and 11i Only)

Chapter 4 85

Verify Status of a Physical Port (HP-UX 11.0and 11i Only)To verify the status of a specific physical port, type:

lanadmin -x -p PortPPA linkaggPPA

Where PortPPA can be found by doing a lanscan and using one of thevalues in the column titled Crd In# which corresponds to a physical port(physical ports are denoted by a value similar to, but not necessarily thesame as, 8/0/1/0 in the Hardware Path field).

For example, to verify that the port with PPA number 2 has successfullycompleted FEC negotiation, type:

lanadmin -x -p 2 100

The output from this command should show a field called Port State. Thevalue of the field should be UP. If not then you may have a configurationproblem and you need to refer to the HP Auto-Port Aggregation ReleaseNotes.

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 weresuccessfully added to link aggregate with PPA number 101 type:

lanadmin -x -v 101

CAUTION If you change some link aggregate variables using the lanadmincommand, those changes are not preserved after reboots. If you uselanadmin , you also need to edit the 2 config files: hp_apaconf andhp_apaportconf

Configuring APA by Editing FilesVerify Status of a Physical Port (HP-UX 11.0 and 11i Only)

Chapter 486

Chapter 5 87

5 What is LAN Monitor?

What is LAN Monitor?LAN Monitor Overview

Chapter 588

LAN Monitor OverviewFor details on configuring the FEC_AUTO, MANUAL, or LACP modes,see “Configuring APA by Editing Files” or “Configuring APA Using SAM”in this document.

The LAN Monitor mode of HP APA provides a failover group capabilitywith MC/ServiceGuard-like configuration tools. LAN Monitor does notsupport MC/ServiceGuard. In the event of link failure, LAN Monitor willautomatically migrate the data flow from the primary link to one of thestandby links in the failover group.

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

LAN Monitor Features

• High availability and fast failover of network interfaces. Linkaggregates can be part of the failover group.

• Supports all LAN technologies: 100BT, Gigabit, FDDI, and TokenRing.

• Automatic link aggregate discovery and configuration 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

Configuring LAN Monitor Failover Groups

To configure a LAN Monitor failover group, proceed as follows:

1. Connect the physical devices that are to be in the failover group tothe same switch, or different switches/hubs on the same subnet ifswitch/hub redundancy is desired.


Chapter 5 89

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 IPaddress, add the IP address for the primary port to/etc/rc.config.d/netconf. Editing that file or using SAM willpreserve the IP address permanently (across reboots).

You can also temporarily assign an IP address to the primary link bytyping, for example:ifconfig lan1 192.5.5.138

4. (HP-UX 11.0 and 11i only) In the/etc/rc.config.d/hp_apaportconf file, create a failover groupconsisting of primary and standby interfaces, and assign theconfiguration mode (LAN_MONITOR).

Example, to put lan1 and lan2 into a failover group:

HP_APAPORT_INTERFACE_NAME[0]=lan1HP_APAPORT_CONFIG_MODE[0]=LAN_MONITORHP_APAPORT_INTERFACE_NAME[1]=lan2HP_APAPORT_CONFIG_MODE[1]=LAN_MONITOR

You can also set the LAN_MONITOR mode with:lanadmin -X -p PortPPA AnyLinkAggregatePPA

5. Activate the configuration 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/lanconfig.ascii.

This command will query the system and network for all possiblefailover groups. The results of the query will be placed in theconfiguration file /etc/lanmon/lanconfig.ascii. This file shouldcontain data similar to:


Chapter 590

NODE_NAME hpxyz6ePOLLING_INTERVAL 10000000DEAD_COUNT 3FAILOVER_GROUP lan900 STATIONARY_IP 192.5.5.138 PRIMARY lan1 5 STANDBY lan2 3

You can manually edit this file and change the number of ports in thefailover groups, the dead count, or the poll interval.

7. Verify that the configuration in /etc/lanmon/lanconfig.ascii is stillvalid by typing:

lancheckconf

8. Create the failover groups specified in the configuration file bytyping:

lanapplyconf

This command will create the specified failover groups in the binaryconfiguration file /etc/lanmon/lanconfig.

Check the failover group by using lanscan -q and netstat -in

Note: if you later want to delete all the failover groups specified inthe /etc/lanmon/lanconfig.ascii configuration file, type:

landeleteconf

9. The failover group is now operational. A reboot will restart thefailover group as long as the /etc/lanmon/lanconfig.ascii file isintact.

Example: Configuring a LAN Monitor Failover Group

Intent: Configure a two port LAN Monitor failover group.

K-class system with lan1 currently configured with IP address192.1.1.153. We have spare HSC 100BT devices: lan2, lan3, lan4 asshown by netstat and ioscan

# netstat -in


Chapter 5 91

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

# ioscan -fkC lan

Class I H/W Path Driver S/W State H/W TypeDescription========================================================================lan 1 8/8/1/0 btlan4 CLAIMED INTERFACE HPHSC 100Base-TXlan 2 8/8/2/0 btlan4 CLAIMED INTERFACE HPHSC 100Base-TXlan 3 8/12/1/0 btlan4 CLAIMED INTERFACE HPHSC 100Base-TXlan 4 8/12/2/0 btlan4 CLAIMED INTERFACE HPHSC 100Base-TXlan 0 10/12/6 lan2 CLAIMED INTERFACEBuilt-in LAN

#

It is decided that lan2 will be the standby link for the failover group,with lan1 as the primary device.

To configure the failover group:

1. Connect lan1 and lan2 to the same switch, or different switches/hubson 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 Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPIPath Address In# State NamePPA ID Type Support Mjr#8/8/2/0 0x0060B04B7B83 2 UP lan2 snap2 3 ETHER Yes 1198/12/2/0 0x001083953C1D 4 UP lan4 snap4 4 ETHER Yes 1198/8/1/0 0x0060B04B7B82 1 UP lan1 snap1 5 ETHER Yes 11910/12/6 0x080009D43696 0 UP lan0 snap0 6 ETHER Yes 1198/12/1/0 0x001083953C1C 3 UP lan3 snap3 7 ETHER Yes 119LinkAgg0 0x000000000000 100 DOWN lan100 snap100 9 ETHER Yes 119LinkAgg1 0x000000000000 101 DOWN lan101 snap101 10 ETHER Yes 119LinkAgg2 0x000000000000 102 DOWN lan102 snap102 11 ETHER Yes 119LinkAgg3 0x000000000000 103 DOWN lan103 snap103 12 ETHER Yes 119


Chapter 592

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

3. In the /etc/rc.config.d/hp_apaportconf file, verify that an entryexists for the primary and standby interfaces that sets the interfaces'port configuration mode to LAN_MONITOR.

HP_APAPORT_INTERFACE_NAME[0]=lan1HP_APAPORT_CONFIG_MODE[0]=LAN_MONITOR

HP_APAPORT_INTERFACE_NAME[1]=lan2HP_APAPORT_CONFIG_MODE[1]=LAN_MONITOR

Also set the mode with the lanadmin command:

lanadmin -X -p 1 LAN_MONITOR 100lanadmin -X -p 2 LAN_MONITOR 100

4. If the device to be the primary link does not have the desired IPaddress, use the ifconfig command to assign the IP address. Also addan entry to the /etc/rc.config.d/netconf file to assign the IP addresspermanently (or use SAM to do it).

# ifconfig lan1 192.1.1.153#

5. Use the lanqueryconf -s command to query the system forpossible failover groups.

# lanqueryconf -s

ASCII output is in file /etc/lanmon/lanconfig.ascii#

6. Verify that the contents of the /etc/lanmon/lanconfig.ascii havethe failover group configured 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**


Chapter 5 93

# *** or your manual.**# ********************************************************NODE_NAME hpnmcbar

POLLING_INTERVAL 10000000DEAD_COUNT 3

FAILOVER_GROUP lan100STATIONARY_IP 192.1.1.153STANDBY lan2 3PRIMARY lan1 5

#

7. Use the lanapplyconf command to build the failover group, andcheck it with lanscan -q and netstat -in

# lanapplyconf

Reading ASCII file /etc/lanmon/lanconfig.asciiCreating Fail-Over Group lan100Updated binary file /etc/lanmon/lanconfig

# lanscan -q

0100 1 2101102103104

# netstat -in

Name Mtu Network Address IpktsOpktslan0 1500 15.13.120.0 15.13.120.153 17941173lo0 4136 127.0.0.0 127.0.0.1 390

390lan100 1500 192.1.1.0 192.1.1.153 0

0


Chapter 594

#

8. The failover group is now operational. A reboot will restart thefailover group as long as /etc/lanmon/lanconfig.ascii file is intact.

Configuration Files

ASCII file

The ascii configuration file is /etc/lanmon/lanconfig.ascii.

Sample lanconfig.ascii Configuration 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 hpntcyj

POLLING_INTERVAL 1000000

DEAD_COUNT 3

FAILOVER_GROUP lan92

STATIONARY_IP 194.12.14.55

PRIMARY lan2 5

STANDBY lan3 3



PRIMARY lan6 5

STANDBY lan7 3


Chapter 5 95

The ASCII config file contains the following fields:

• NODE_NAME:The name of the node. This is the name of the system asobtained by gethostname() and should be the first line in the file.

• FAILOVER_GROUP: The aggregate name which will form a singlefail-over group. This may be specified repeatedly for all of the linkaggregates in the system. If the link aggregate has multiple links,then it will be of the form lan100, lan101, …, that is, an aggregate isallocated to it. However, if it is a single link aggregate, then it will belanX, where X is the PPA of the link.

• PRIMARY/STANDBY:The LAN interface (for example, lan0, lan1). Thismay be specified repeatedly for all applicable lan interfaces in thefail-over group. They can be specified only for fail-over groups whichhave more than one link. These interfaces belong to the lastFAILOVER_GROUPthat was mentioned. The last parameter is the portpriority that will be assigned to the port. The port with an IP addressassigned is taken to be primary. The default port priorities have beenselected so that fail-over and fail-back works correctly.

• STATIONARY_IP This is the IP address dedicated to the linkaggregate. This is a required field and must be set for the primarylink before running lanapplyconf.

• POLLING_INTERVAL The number of microseconds between pollingmessages. Polling messages are sent between links in the specifiedinterval for monitoring the health of all the links in the linkaggregate. Default is 10,000,000 (10 seconds). May occur more thanonce in the config file. An aggregate’s polling interval is set to themost recent that is read.

• DEAD_COUNT The number of polling packets that are missed beforedeciding to send a nettl log message to the user that the link may behaving problems and the network should be checked for problems.Default is 3.

STANDBY lan9 3

STANDBY lan8 3


Chapter 596

Binary File

The binary file /etc/lanmon/lanconfig stores the current snapshot ofthe aggregates. Since the aggregates cannot be modified using thelanadmin command, and this file is non-editable, it will correctlyrepresent the current configuration.

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

What is LAN Monitor?LAN Monitor Configuration Commands

Chapter 5 97

LAN Monitor Configuration Commands

lanqueryconf

The basic function of this command is to discover the set of LANinterfaces that can form a single link aggregate and then map thatinformation to an ASCII configuration file(/etc/lanmon/lanconfig.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 file

• -v – specifies verbose output

• -c ascii_file – specifies the ascii file to be output — the default islanconfig.ascii

Query the system and create an ascii configuration file

lanqueryconf -s

This will create an ascii file that represents the valid LAN Monitoraggregations that can be formed. This file can be edited and then usedwith the lanapplyconf command to form the aggregations.

The output will be similar to the sample file shown on page 94.

Query the system for the binary file

The lanqueryconf -b command reads the binary bile/etc/lanmon/lanconfig and creates an ascii output file that can showthe LAN Monitor aggregations configured in the system.

lanqueryconf -b

Reading binary file /etc/lanmon/lanconfig

ASCII output is in file /etc/lanmon/laconfig.ascii


Chapter 598

lanapplyconf

This command implements the configuration in the ASCII file/etc/lanmon/lanconfig.ascii and creates a binary file with theinformation.

Usage:

lanapplyconf [-v] [-c ascii_file]

The options are:


• -c ascii_file – specifies the ascii file to be used for the configuration.The default is /etc/lanmon/lanconfig.ascii .

lancheckconf

This command validates the content of the ASCII configuration file.

Usage:

lancheckconf [-v] [-c ascii_file]

The options are:


• -c ascii_file – specifies the ascii file to be checked. The default is/etc/lanmon/lanconfig.ascii .

landeleteconf

This command clears the aggregate(s) that have been created inLAN_MONITOR mode.

Usage:

landeleteconf [-v][-g PPA number of fail-over group to bedeleted]

The options are:


• -g PPA# – specifies which link aggregate to delete


Chapter 5 99

For example, to delete a FAILOVER_GROUP with a PPA of 104, enter:

landeleteconf -g lan104


Chapter 5100

Chapter 6 101

6 Using ServiceGuard with HPAPA

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

Using ServiceGuard with HP APARequirements for Use

Chapter 6102

Requirements for UseTo use MC/ServiceGuard with HP APA, the following MC/SG and APArequirements 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 linkaggregates. MC/ServiceGuard does not support LACP_AUTO modelink aggregates.

NOTE Configure APA before configuring MC/SG. Only link aggregatesshould be used in the MC/SG configuration.

• APA Configuration Requirement - Follow the general rules forconfiguring APA’s 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_AUTOaggregation must have a different group capability.

Refer to chapter 2, “Modifying Default Configuration Parameters” fordetails on configuring link aggregates and for setting the FEC groupcapability or LACP key.

Chapter 7 103

7 Troubleshooting HP Auto PortAggregation (APA) Software

This chapter contains an overview on troubleshooting and detailedtroubleshooting flowcharts and instructions.

Troubleshooting HP Auto Port Aggregation (APA) SoftwareTroubleshooting Overview

Chapter 7104

Troubleshooting OverviewHP Auto-Port Aggregation problems can be caused by a variety ofhardware and software components. The problem impacting your systemmay originate in a required hardware component (that is. networkingadapter), the switch which the networking adapter connects to, or theHP Auto-Port Aggregation software.

As with any troubleshooting, a systematic approach is helpful. Thefollowing table and flowcharts provide a logical sequence of steps tofollow when troubleshooting the HP Auto-Port Aggregation software.

Using the diagnostic flowcharts provided in this chapter, identifywhether the problem is with the HP Auto-Port Aggregation software,configuration of the switch, physical connections to the switch, orwhether it is in some other part of the network. Once the problem isisolated, execute the recommended corrective action.

If you cannot solve the problem on your own, contact your HPrepresentative. Use the guidelines in “Contacting Your HPRepresentative”, to help you effectively communicate what is wrong.

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

Chapter 7 105

What Happens during Start Up?Following is the sequence of actions that occur after you have installedthe HP APA software. During the system boot-up, the following sequenceof events occur:

1. Initialize HP APA software

All the internal housekeeping initialization (such as allocation ofmemory, etc.) for the software is done. During this step, the defaultvalues are assigned for all the properties on each port and linkaggregate.

2. hp_apaportconf processing

Contains customization variables for each physical port. Thefeatures that can be set on each port are Group Capability, PortPriority, and Config Mode. If no value is specified for a given featurefor a given port, the software assumes a default value for the same.The port’s mode is set at this stage.

3. hp_apaconf processing

/etc/rc.config.d/hp_apaconf contains customization variables foreach link aggregate. The features that can be set on each linkaggregate are Load Balancing Mode, Hot Standby Mode, and ports ina Manual Link Aggregate. The last feature allows manualconfiguration of a link aggregate with the port(s) specified.

4. Start the HP APA software

Cisco's FEC or IEEE 802.3ad LACP protocol is started on the portsthat have been marked as such. No action is taken for the ports thathave Cisco’s FEC or IEEE 802.3ad LACP turned off.

5. Process LAN Monitor ASCII file

Process /etc/lanmon/lanconfig.ascii to create fail-over groups. Ifthis file has not been created then no action is taken.

Once the system is up and running, you can distinguish a link aggregatefrom a normal (unaggregated) port by running lanscan(1M) at theHP-UX prompt as follows:

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

Chapter 7106

lanscan

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

MAC Addresses for Link Aggregates

This section describes the process used to select unique MAC addressesfor link aggregates.

The unique MAC address for a specific link aggregate is determined byusing the permanent MAC address of the first physical port assigned tothe link aggregate. If the first port is removed, the link aggregate’s MACaddress is updated with the permanent MAC address of the last port inthe link aggregate.

When a physical port is removed from a link aggregate, it’s local MACaddress is reset to the physical port’s permanent MAC address.

Unsupported Way of Changing MAC Address

HP-UX 11.x and 10.20 versions of APA do not support the followingfunction:

• Changing the local MAC address on logical link aggregations viaDL_SET_PHYS_ADDR_REQ.

Table 7-1

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

Troubleshooting HP Auto Port Aggregation (APA) SoftwareDiagnostic Flowcharts

Chapter 7 107

Diagnostic FlowchartsBelow is a summary of the types of network tests in the diagnosticflowcharts. Follow the flowcharts in sequence beginning with Flowchart1. Continue sequentially through flowcharts 2, 3, 4, 5, 6, 7, 8, 9, and 10referring back to Flowchart 1 (ping ), as indicated at the end of eachflowchart, until you have corrected the problem.

The following flowcharts are described in general terms and can beexecuted on any network physical port supported by the HP Auto-PortAggregation software. See “Summary of APA and LAN MonitorCapabilities” on page 14 for a list of supported network physical ports(adapter cards).

Table 7-2 Flowchart Descriptions

Flowchart Description

1 Network Level Loopback Test

2 Network Physical Port Connections/LEDTest

3 and 4 Network Physical Port Configuration Test

5 Link Aggregation Configuration Test

5A Manual Configuration Test

5B PAgP Configuration Test

5C LAN Monitor Configuration Test

5D LACP Configuration Test

6 Network Configuration Test

7 Arp Verification

8 Link Level Loopback Test

9 Transport Level Loopback Test (usingARPA)

10 Bridge/Gateway Loopback Test


Chapter 7108

Network Level Loopback Test: Checks roundtrip communicationbetween Network Layers on the source and target host using theping(1M) command.

Network Physical Port Connections/LED Test: Checks that all thehardware connections between your system and the network areconnected and operational.

Network Physical Port Configuration Test: Verifies theconfiguration of the network physical port(s) on a host using thelanscan(1M), netfmt -vf, lanadmin(1M), and ifconfig(1M) commands. Inaddition, the switch configuration should be verified using theappropriate switch commands.

Link Aggregation Configuration Test: Verifies the configuration ofthe link aggregate on the server. The switch configuration should beverified using the appropriate switch commands. The appropriatepatches should also be verified.

Arp Verification: Checks arp entries using the arp(1M) command.

Link Level Loopback Test: Checks roundtrip communication betweenLink Levels on the source and target host using the linkloop(1M)diagnostic.

Transport Level Loopback Test: Checks roundtrip communicationbetween Transport Layers on the source and target host using ARPAservices telnet and ftp commands.

Bridge/Gateway Loopback Test: Checks general network connectionsthrough a gateway.


Chapter 7 109

This page intentionallyleft blank


Chapter 7110

Flowchart 1: Network Level Loopback Test

The following tests should be executed on the specific link aggregatewhich is experiencing problems.


Chapter 7 111

Figure 7-1 Flowchart 1: Network Level Loopback Test

1

A

C

Execute: pingto remote host

Networkunreachable

?

pingsuccessful

?

EUnknown

host?

Yes

G No routeto host

?

Yes

StopYes

Yes

No

No

No

No

Correct BIND, YP or/etc/hosts configuration

Add routetable entry

H

B

3, 5

Call HP

Commandhangs

?

D

1

No

Yes2,3,4,56,7 & 8

F


Chapter 7112

Flowchart 1 Procedures

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

ping spiff

B. ping successful? A message is printed to stdout foreach ping packet returned by the remote host. Ifpackets are being returned, your system has networklevel connectivity to the remote host. Note whatpercentage of the total packets are lost, if any. Losingten percent or more may indicate the network orremote host is extremely busy. You may also find ituseful to note the round-trip transmission times.Periodically high transmission times may indicate thatthe network or remote host is extremely busy.Consistently high transmission times may indicate thelocal host is extremely busy. If a message is notreturned after executing ping, ping is not successful.Do Cntrl C to stop the ping output.

C. Network unreachable? If YES, go to Flowchart 3 todisplay connection status using the lanscan(1M)command. If this is OK, then proceed to Flowchart 5and verify that the link aggregate is configuredcorrectly.

D. Command hangs. If a message is not returned afterexecuting ping, go to Flowcharts 2 through 7, referringback to Flowchart 1 (ping ) until you have corrected theproblem.

E. Unknown host? If you receive this message, go to StepF.

F. Correct BIND, YP or hosts configuration. Addthe missing host name and start again with Flowchart1.

G. No route to host? If Error= Sendto: No route tohost , go to Step H. Otherwise, call your HPrepresentative for help.


Chapter 7 113

H. Add route table entry. Using route , add a routetable entry for that host. Refer to the route(1M) onlineman page for more details. Start again with Flowchart1.

Flowchart 2: Network Physical Port Connections/LEDTest

The following flowchart should be used for each of the network physicalports which have been configured in a specific link aggregate. These testscan be executed at any time to verify proper physical connection betweenthe network physical port and the switch.


Chapter 7114

Refer to “Modifying Default Configuration Parameters” on page 49, or“Using the lanadmin Command for Testing” on page 167 for a detaileddescription of how to determine which network physical ports areassociated with a specific link aggregate.


Chapter 7 115

Figure 7-2 Flowchart 2: Network Physical Port Connections/LED Test

2

Check:Power outlet

100 Mbit port LED=ON10 Mbit port LED=OFF

LED Display:

Test Error Message

?

Link LED = OFF

?

B

E

No

No

on Screen (dmesg ouput)

Yes

Yes

D

F

1

ACheck network physical

100 Mbit port LED=ON10 Mbit port LED=OFFDo link speed and duplex

?

G

Yes

mode match switchSet attached switchto correct speed, duplex mode,and autonegotiation mode.

Reset network physical port.

No

H

3

Port Installation.

Reset the networkphysical port.

1

1

Check connection to switch.

Ensure switch is autonegotiating.

Ensure switch is configured inthe correct mode.

Reset the network physical port.

Check status ofLink LED


Chapter 7116


A. Check power outlet. Ensure the power cord isplugged in to a live outlet.

B. Test error message on screen? At the HP-UXprompt, type the dmesg command, and look for an errormessage. Does the dmesg output show an errormessage from networking port(s) you are using? If not,go to Step D.

Note: even if the Test LED is OFF, a card problem isstill possible.

C. Check card installation .If dmesg reported an errormessage for the networking port(s), reset the portaccording to Steps D through G in Flowchart 4. Ifproblem persists, call HP. Go back to Flowchart 1.

D. Check status of Link LED.

E. Link LED = OFF? Go to Step F.

Link LED = ON? Go to Step G.

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

G. Do link speed and duplex mode match switch? Ifthey do, proceed to Flowchart 3.

H. If Link speed and duplex mode do not match what youexpect, set attached switch to the correct link speedand duplex mode, and if necessary enableautonegotiation. Reset the network physical portaccording to Steps D through G in Flowchart 4 and goback to Flowchart 1.


Chapter 7 117

Flowchart 3: Network Physical Port ConfigurationTest

The following flowchart should be used for each of the network physicalports which are being configured in a specific link aggregate. These testscan be executed at any time to verify that the software for the networkphysical port is correctly installed on the HP 9000 server.


Chapter 7118

Figure 7-3 Flowchart 3: Network Physical Port Configuration Test

3

A

Execute: lanscan -v

Isyour interface

displayed

B

5

Yes

Yes

Verify or edit/stand/system

Regen kernel.

Run ioscan

Is driver inkernel

Reboot thesystem

E

H

No

Yes

-f

?

?

Hardware

?

CD

Checkhardware

Problem

Yes

Stop

No

No

I

G

F

No1

Install driver.

to add driver keyword

up

fixed?


Chapter 7 119


NOTE Check that your network physical port connectors between the card andswitch (or wall plug) are fully connected before beginning this flowchart.

A. Execute: lanscan. Enter the lanscan -v commandto display information about network physical portsand the link aggregates that are successfully installedon the system. Some network physical ports may showup as part of a specific link aggregate and not asstandalone ports. See “Using the lanadmin Commandfor Testing” on page 167 for a detailed description ofhow to determine which link aggregate a specificnetwork physical port belongs to.

See the lanscan online man page for more detailedinformation.

B. Is your interface displayed? lanscan showsinformation about every LAN card in the systembackplane. The Hardware Path of one of the entriesshould correspond to the network physical port slotmultiplied times four. For example, a hardware path of32 corresponds to a network physical port in slot 8.

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


Chapter 7120

D. Run ioscan. ioscan will scan the system hardwareand list the results. If you execute ioscan -f , outputsimilar to the following will be displayed:


Chapter 7 121

Table 7-3

Class I H/W Path Driver S/W State H/W Type Description=============================================================================bc 0 root CLAIMED BUS_NEXUSbc 1 8 ccio CLAIMED BUS_NEXUS I/O Adapterba 0 8/4 GSCtoPCI CLAIMED BUS_NEXUS PCI Bus Brid g- GSCtoPCIlan 4 8/4/1/0 btlan4 CLAIMED INTERFACE PCI(10110009)- Built-in #1lan 5 8/4/2/0 btlan4 CLAIMED INTERFACE PCI(10110009)- Built-in #2ba 1 8/8 GSCtoPCI CLAIMED BUS_NEXUS PCI Bus Brid g- GSCtoPCIlan 6 8/8/1/0 btlan4 CLAIMED INTERFACE PCI(10110009)- Built-in #1lan 7 8/8/2/0 btlan4 CLAIMED INTERFACE PCI(10110009)- Built-in #2ba 2 8/12 GSCtoPCI CLAIMED BUS_NEXUS PCI Bus Brid g- GSCtoPCIlan 8 8/12/1/0 btlan4 CLAIMED INTERFACE PCI(10110009)- Built-in #1lan 9 8/12/2/0 btlan4 CLAIMED INTERFACE PCI(10110009)- Built-in #2bc 2 10 ccio CLAIMED BUS_NEXUS I/O Adapterext_bus 0 10/0 c720 CLAIMED INTERFACE GSC built-in st/Wide SCSI Interfacetarget 0 10/0.6 tgt CLAIMED DEVICEdisk 0 10/0.6.0 sdisk CLAIMED DEVICE HP C249 0target 1 10/0.7 tgt CLAIMED DEVICEctl 0 10/0.7.0 sctl CLAIMED DEVICE Initiatorbc 3 10/4 bc CLAIMED BUS_NEXUS Bus Converte rtty 0 10/4/0 mux2 CLAIMED INTERFACE MUXlanmux 0 10/4/4 lanmux0 CLAIMED INTERFACE HP J2146A - 8.3 LANlan 1 10/4/4.1 lan3 CLAIMED INTERFACEba 3 10/8 GSCtoPCI CLAIMED BUS_NEXUS PCI Bus Brid g- GSCtoPCIlan 2 10/8/1/0 btlan4 CLAIMED INTERFACE PCI(10110009)- Built-in #1lan 3 10/8/2/0 btlan4 CLAIMED INTERFACE PCI(10110009)- Built-in #2ba 4 10/12 bus_adapter CLAIMED BUS_NEXUS Core I/O Ada prext_bus 1 10/12/5 c720 CLAIMED INTERFACE Built-in SCS Itarget 2 10/12/5.2 tgt CLAIMED DEVICEtarget 3 10/12/5.7 tgt CLAIMED DEVICEctl 1 10/12/5.7.0 sctl CLAIMED DEVICE Initiatorlan 0 10/12/6 lan2 CLAIMED INTERFACE Built-in LANps2 0 10/12/7 ps2 CLAIMED INTERFACE Built-in Key brd/Mouseprocessor 0 32 processor CLAIMED PROCESSOR Processorprocessor 1 34 processor CLAIMED PROCESSOR Processormemory 0 49 memory CLAIMED MEMORY Memory


Chapter 7122

If there are multiple network physical ports installedin the system then the output above will be duplicatedwith only the H/W Path column changing to reflect thecorrect hardware path information. The example aboveshows multiple HSC 100BT cards installed.

E. Is driver in kernel? If the driver has not beengenerated into the kernel, ioscan output will besimilar to (but not necessarily the same as):

The class and driver fields alone will indicate“unknown” status if the kernel has not been generated.If the driver has not been generated, continue to StepF. 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 appropriatekeyword for the networking adapter you are using. Forexample, if you are using the HSC 100BT networkadpater, the keyword btlan4 should appear. Or, if usinga V-class PCI 100BT network adapter, the keywordbtlan6 should appear. If not, see “Creating a NewKernel” in Chapter 3 of the Installing andAdministering LAN/9000 Software manual forinstructions on how to edit /stand/system to create anew kernel.

Table 7-4

ba 0 8/4 GSCtoPCI CLAIMED BUS_NEXUS PCI Bus Brid gGSCtoPCIlan 4 8/4/1/0 btlan4 CLAIMED INTERFACE PCI(10110009)Built-in #1lan 5 8/4/2/0 btlan4 CLAIMED INTERFACE PCI(10110009)Built-in #2

Table 7-5

ioscan -f

Class I H/W Path Driver S/W State H/WType Description==============================================================================unknown -1 10/4/4 UNKNOWN UNCLAIMED INTERFACE


Chapter 7 123

Verify that the required patch is installed for thenetwork physical port which is being used. Refer toChapter 1 for a list of required patches.

G Check Hardware. Verify that the network card isseated correctly and that it is operational.

H. Reboot the system.

I. Problem fixed? If you have found the appropriatenetwork physical port problem, stop. If not, start againwith Flowchart 1.


Chapter 7124

Flowchart 4: Network Physical Port ConfigurationTest

The following flowchart should be used for each of the network physicalports which are being configured in a specific link aggregate. These testscan be executed at any time to verify if there are any nettl log messagesassociated with the network physical ports that are being configured in alink aggregate.


Chapter 7 125

Figure 7-4 Flowchart 4: Network Physical Port Configuration Test

No

Execute: netfmt

A

B

C

D

E

Yes

No

4

Execute: lanadmin

Select LAN fromMenu

F

Select PPA command

Check causes andactions on displayin the formatted log

output

1

G

H

Reset Port

Resetsuccessful

?1

Yes

4A

and enter NetworkPhysical port nmid

Problemsolved

?


Chapter 7126


A. Execute: netfmt. Use the netfmt command to viewlog data (error and disaster messages). An examplecommand is shown below.

netfmt -v -f /var/adm/nettl.LOG00|more

B. Check causes and actions on display in theformatted log output. Use the time stamp to findthe proper logs. Ensure that you are looking at theappropriate network physical port information.

C. Problem solved? If YES, go to Flowchart 1. If not,continue with Step D.

D. Execute lanadmin. Run lanadmin(1M) . For acomplete description of this command, refer to thelanadmin(1M) online man page.

E. Select LAN from Menu. Select lan to enter the LANInterface diagnostic.

F. Select the PPA command and enter the NetworkPhysical Port PPA. You can use the lanscancommand to find the current PPA for the networkphysical port. The PPA you enter becomes the currentdevice to be tested.

G. Reset the network physical port according toSteps D through G in Flowchart 4. The resetcommand in lanadmin re-executes the LAN networkphysical port self-test.

H. Reset successful? The reset is successful if no errorsare displayed as a result of the reset command. If theself-test was successful, the problem may be that youare not connected to the network properly. Correct theproblem and verify the resolution by continuing withFlowchart 1. Otherwise, go to Flowchart 4A.


Chapter 7 127

Flowchart 4A: Network Physical Port ConfigurationTest

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

Flowchart 4A Procedures

A. Execute: netfmt. Use the netfmt command to viewlog data (error and disaster messages). An examplenetfmt command is shown below:

netfmt -v -f /var/adm/nettl.LOG00|more

Extend the search to LOG01 as information may haverolled (overflowed) into this file from LOG00.

Execute: netfmt

A

B

4A

Check causes andactions on display

in the formatted logoutput

Problemsolved

?

C Yes

No

Call HP

1


Chapter 7128

B. Check causes and actions on display in theformatted log output. Use the time stamp to findthe proper logs. Ensure that you are looking at theappropriate network physical port information.

C. Problem solved? If YES, go to Flowchart 1. If not,contact your HP representative.


Chapter 7 129



Chapter 7130

Flowchart 5: Link Aggregate Configuration Test

The following tests should be executed on the specific link aggregatewhich is not working correctly.


Chapter 7 131

Figure 7-6 Flowchart 5: Link Aggregate Configuration Test

5

A

B

C

ManualMode = =

Ports inthe aggregate

?

yes

Executelanadmin -x -v

<agg>

Is theaggregate enabled

?

yes

PAgP

LMMode = =

no

no

no

D

E

5A 5B

4

6

5C

HP-UXrelease is

11.0

Executelanscan -q

Ports inthe aggregate

?

Executelanqueryconf -b

Is theaggregate enabled

?

10.20

6yes

F

G

H

I

no

4yes

no

5C

5DLACP


Chapter 7132


Depending on whether you are on HP-UX 11.0 or 10.20, the tools you useare different. lanadmin has no LAN Monitor functionality in 10.20. Youmust use other tools — lanqueryconf(1M), lanapplyconf(1M), orlandeleteconf(1M). Also note that in10.20, which supports only linkaggregates, instance numbers start at 90; 11.0 instance numbers start at100, 11i at 900.

HP-UX 11.0

A. Execute lanadmin -x -v LinkAggPPA. A sampleoutput for three scenarios using linkagg 100 is shownbelow. Case 1 shows that a linkagg is enabled and thereare ports in the aggregate. Case 2 shows that therewere ports in the aggregate, but they are currentlydown. In case 3, the linkagg is not enabled and eitheryou need to add ports to enable it (Lan Monitor orManual mode) or turn on LACP/PAgP aggregationprotocols, so ports could be added to the aggregateautomatically.

Case 1:

lanadmin -x -v 100

Linkaggregate PPA # : 100

Number of Ports : 2

Ports PPA : 5 6

Link Aggregation State : LINKAGG MANUAL

Group Capability : 0

Load Balance Mode : MAC Address Based (LB_MAC)

Case 2:

lanadmin -x -v 100


Number of Ports : 0


Chapter 7 133

See “Using the lanadmin Command for Testing” onpage 167 for a detailed list of supported commands andtheir usage.

B. If there are ports in the aggregate, as shown by thePorts PPA line above, go to Flowchart 6. Otherwisecontinue to the Step C.

C. If the aggregate is enabled, go to Flowchart 4.Otherwise continue to Step D.

D & E. Depending on the mode (MANUAL, FEC_AUTO,LAN_MONITOR, or LACP_AUTO) in which you wantto enable the aggregate, follow Flowchart 5A, 5B, 5C,OR 5D as appropriate. FEC_AUTO is the same asPAgP and LAN_MONITOR is also being referred to asLM.

HP-UX 10.20

F. Execute lanscan -q If link aggregates are configuredand ports are UP, it can be seen in the lanscan output.

Ports PPA : NONE

Link Aggregation State : LINKAGG HAS NO PORTS



Case 3:

lanadmin -x -v 101


Number of Ports : 0

Ports PPA : NONE

Link Aggregation State : LINKAGG IS NOT ENABLED




Chapter 7134

Example 1: Shows that link aggregates are either notconfigured or went down.

lanscan -q

0123459091929394

Example 2: Shows that link aggregates with ports inthem went down.

lanscan -q

059091929394

G. Ports in the aggregate? If YES, go to Flowchart 6. IfNo, go to Step H.

H. Execute lanqueryconf -b This shows the presentconfiguration that is effective in the system. Theoutput of this command tells if a link aggregate is nowconfigured, but if ports went down. In the followingexample, link aggregate 92 is configured and all of itsports went down.

lanqueryconf -b


Chapter 7 135

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

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

NODE_NAME hpntcyj


DEAD_COUNT 3



STANDBY lan9 3

PRIMARY lan6 5



PRIMARY lan0 5

STANDBY lan1 3

STANDBY lan2 3

STANDBY lan3 3




Chapter 7136

Flowchart 5A: Manual Configuration Test

Figure 7-7 Flowchart 5A: Manual Configuration Test

5A

1

A

B

C

D

E

No

Yes

No

F

Yes

5A

Executelanadmin -x -p <port_num> 100

for each port

Isport modeManual?

Executelanadmin -X -p <port> MANUAL 100

for each port

Add port to aggregatelanadmin -X -a <port_list> 100

Success?

Fix error accordingto message received


Chapter 7 137

Flowchart 5A Procedures

A. Execute lanadmin -x -p <portppa> 100 to determinethe mode for each of the ports that you want to be apart 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” onpage 167.

B. Examine the output and look at the mode. If the portmode is not MANUAL go to Step C. Otherwise go toStep D.

C. Execute lanadmin -X -p <portppa> MANUAL 100 tochange the state to MANUAL for all the ports whichwere not in MANUAL mode.

D. Add the ports to the aggregate using the followingcommand syntax:lanadmin -X -a PortPPAs LinkAggPPA

This command will add the network physical portswith portPPA numbers to the link aggregate withLinkAggPPA. For example, to add network physicalports with PortPPAs 1,2,3, and 4 to aggregate 100 thefollowing command should be used:

lanadmin -X -a 1 2 3 4 100

E. Did the above command complete successfully? If YESgo to Flowchart 1. If NO fix the error according to theerror message and go back to the beginning of thisflowchart.

NOTE The link aggregate can be configured, but there can still bemisconfiguration problems on the switch. Its imperative that both theswitch and the server links aggregates are consistent in order forsuccessful network communication to occur.


Chapter 7138

Flowchart 5B: PAgP Configurations Test


Chapter 7 139

Figure 7-8 Flowchart 5B: PAgP Configuration Test

5B

1

A

B

C

D

E

No

Yes

No

F

Yes


for each port

Executelanadmin -X -p <port> FEC_AUTO 100

for each port

Run lanscan -q to seeif ports are aggregated

1. Check Cisco FEC protocol on each port2. Check switch configuration3. Verify that required patches are installed

Call HP

Executelanadmin -x -p <port> 100

for each port

Isport mode

FEC_AUTO?

Yes

No

Stop LACP? 1

Ports aggregated?

1. Execute lanadmin -X -p <port> MANUAL 1002. Check switch configuration

No

Yes

G

H

I

J

Is portmode FEC_AUTOor LACP_AUTO?


Chapter 7140

Flowchart 5B Procedures

A. Execute lanadmin -x -p <portppa> 100 to determinethe mode for each of the ports that you want to be apart of the aggregate in PAgP mode. For example, todetermine the status of port ppa 4, enter:



B. Examine the output and look at the mode. If the portmode is neither FEC_AUTO nor LACP_AUTO go toStep C. Otherwise go to Step D.

C. Execute: lanadmin -X -p <portppa> FEC_AUTO 100 tochange the state to FEC_AUTO for all the ports whichwere in MANUAL mode. Wait 30 seconds for theaggregation protocol to establish the connection.

D & E. Execute lanscan -q to see if ports are aggregated. IfYES go to Step G. If NO go to Step F.

F. Ports aggregated? If the are not aggregated, then thefollowing should be verified for correctness.

1. Auto Add: If you are attempting to enable a linkaggregate via the Cisco Fast EtherChannel protocolcheck the network physical port status with thefollowing 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 field should show UP if the CiscoFastEtherChannel Protocol has negotiatedsuccessfully. If the Port State is not UP then go to Step3, below.


Chapter 7 141

2. Switch Configuration: Verify that the switch isconfigured correctly. Refer to the appropriate switchdocumentation to determine if the switch portsconnected to the HP 9000 Server are configuredcorrectly for link aggregation.

3. Required Patches: Verify that required patchesare properly installed on your server. See “RequiredSoftware” on page 17 to determine which patches arerequired for the HP Auto-Port Aggregation Product.

If all of the checks above are OK then call your HPRepresentative. If any step is not OK, then correct theproblem and go back to Step A.

G. Execute the following command again:

Lanadmin -x -p <portppa> LinkAggPPA

H. Is port mode FEC_AUTO? If YES go to Flowchart 1.If NO, go to Step I.

I. Stop LACP? The port mode must be LACP_AUTO. Ifyou DO NOT want to stop LACP on the ports, go toFlowchart 1. If you DO want to use the ports for PAgPgo to Step J.

J. 1. Execute lanadmin -X -p <port> MANUAL 100 to stopthe LACP protocol.

2. Check switch configuration. Check the configurationto ensure the port should not run IEEE 802.3ad LACPprotocol, but Cisco Fast EtherChannel protocol.

Wait 30 seconds for the port to settle down and thenstart this flowchart’s procedure again.


Chapter 7142



Chapter 7 143

Flowchart 5C: LAN Monitor Configuration Test

Figure 7-9 Flowchart 5C: LAN Monitor Configuration Test

5C

1

A

B

C

D

E

No

Yes

No

F

Execute lanqueryconf -sand figure out possiblefail-over (FOV) groups

Port in FOVgroup needs IP

assigned?

Run lanapplyconf -s again andedit /etc/lanmon/lanconfig.ascii

Pick a port in FOV groupand assign an IP address to it

Success?Correct problem accordingto error message received

No

Make an entry in/etc/rc.config.d/netconf

G

Success?

if necessary

Run lanapplyconfH

IJ

Correct problem accordingto error message received

Yes

5C

5C


Chapter 7144

Flowchart 5C Procedures

A. lanqueryconf figures out which set of ports are on thesame subnet, and which on e of them is configured withan IP address and writes valid configurations to thedefault file /etc/lanmon/lanconfig.ascii . It alsoprints a warning message if none of the ports on asubnet have an IP address assigned. For more details,see the lanqueryconf(1M) man page.

Execute lanqueryconf -s to do a system-wide searchfor ports/links that can form fail-over groups.

Example 1:lanqueryconf -s fails to fine ports that canform a fail-over group.

Example 2: lanquery -s successfully finds ports thatcan form a fail-over group.

The file /etc/lanmon/lanconfig.ascii looks like:

lanqueryconf -s

WARNING: None of the ports in subnet (lan2) have an IP address assigned



WARNING: None of the ports in subnet (lan6 lan7) have an IP address assign e

No Fail-Over groups found. ASCII file not created.

lanqueryconf -s

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

NODE_NAME hpntc6s


DEAD_COUNT 3


Chapter 7 145

B. If none of the ports in a fail-over group has an IPaddress assigned, lanqueryconf prints a warningmessage.

C. The port that you choose to assign an IP address tocarries all the traffic to and from the fail-over group.This port is called the primary port, and in the event offailure of this port, the next highest priority portamong the standby ports takes over. Use the followingsyntax for the ifconfig command:ifconfig <interface> <ip address> up

Example: ifconfig lan3 192.12.14.56 up

For more details see the ifconfig(1M) man page.

D. Run ifconfig <interface> to check if the command inStep C was successful.

E. Correct any problem with the ifconfig flags or othererror indications and repeat from Step A. If necessaryuse the ifconfig(1M) man page to figure out the errors.

F. An entry in /etc/rc.config.d/netconf helps inconfiguring IP addresses automatically by using the rcscripts on boot up.

G. Run lanqueryconf -s again so it can determine whichports can form fail-over groups.



PRIMARY lan0 5

STANDBY lan2 3

ifconfig lan3

lan3: flags=843<UP, BROADCAST RUNNING MUTICAST>inet 192.12.14.56 netmask ffffff00 broadcast 192.12.14.255


Chapter 7146

H. Run lanapplyconf. This takes the information in aconfiguration file, forms fail-over groups with them asdescribed in the configuration file, and switches the IPaddress from the primary port to the fail-over group.The default configuration file is/etc/lanmon/lanconfig.ascii .

I. If lanapplyconf is successful, go to Flowchart 1.Otherwise go to Step J.

J. Correct any problems by using the error messages andthen begin again at Step A of this flowchart.


Chapter 7 147



Chapter 7148

Flowchart 5D: LACP Configuration Test


Chapter 7 149

Figure 7-10 Flowchart 5D: LACP Configuration Test

5D

1

A

B

C

D

E

No

Yes

No

F

Yes


for each port

Executelanadmin -X -p <port> LACP_AUTO 100

for each port

Run lanscan -q to seeif ports are aggregated

1. Check LACP protocol on each port2. Check switch configuration3. Verify that required patches are installed

Call HP

Executelanadmin -x -p <port> 100

for each port

Isport mode

LACP_AUTO?

Yes

No

Stop PAgP? 1

Ports aggregated?

No

Yes

G

H

I

J

Is portmode FEC_AUTOor LACP_AUTO?


Chapter 7150

Flowchart 5D Procedures

A. Execute lanadmin -x -p <portppa> 100 to determinethe mode for each of the ports that you want to be apart of the aggregate in PAgP mode. For example, todetermine the status of port ppa 4, enter:



B. Examine the output and look at the mode. If the portmode is not FEC_AUTO or LACP_AUTO go to Step C.Otherwise go to Step D.

C. Execute: lanadmin -X -p <portppa> LACP_AUTO 100to change the state to LACP_AUTO for all the portswhich were in MANUAL mode. Wait 30 seconds for theaggregation protocol to establish the connection.

D & E. Execute lanscan -q to see if ports are aggregated. IfYES go to Step G. If NO go to Step F.

F. Ports aggregated? If the ports are not aggregated,then the following should be verified for correctness.

1. Auto Add: If you are attempting to enable a linkaggregate via the IEEE 802.3ad LACP Protocol. Checkthe network physical port status with the followingcommand:

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 field should be UP if the IEEE 802.3adLACP Protocol has negotiated successfully. If the PortState is not UP then go to Step 3, below.


Chapter 7 151

2. Switch Configuration: Verify that the switch isconfigured correctly. Refer to the appropriate switchdocumentation to determine if the switch portsconnected to the HP 9000 Server are configuredcorrectly for link aggregation.

3. Required Patches: Verify that required patchesare properly installed on your server. See “RequiredSoftware” on page 17 to determine which patches arerequired for the HP Auto-Port Aggregation Product.

If all of the checks above are OK then call your HPRepresentative. If any step is not OK, correct theproblem and go back to Step A.

G. Execute the following command again:

Lanadmin -x -p <portppa> LinkAggPPA

H. Is port mode LACP_AUTO? If YES go to Flowchart1. If NO, go to Step I.

I. Stop PAgP? The port mode must be FEC_AUTO. Ifyou DO NOT want to stop FEC (PAgP) on the ports, goto Flowchart 1. If you DO want to stop PAgP and usethe ports for LACP go to Step J.

J. 1. Execute lanadmin -X -p <port> MANUAL 100 to stopthe FEC (PAgP) protocol.

2. Check switch configuration. Check the configurationto ensure the port should not run Cisco’s FEC protocol,but IEEE 802.3ad LACP protocol.

Wait 30 seconds for the port to settle down and thenstart this flowchart’s procedure again.


Chapter 7152



Chapter 7 153

Flowchart 6: Network Configuration Test

Figure 7-11 Flowchart 6: Network Configuration Test

:

?

6

ifconfigentry in

/etc/rc.config.d/netconf

Execute:ifconfig <interface>

?

6

Executeifconfig <interface>...<IP address> up

Correct ifconfigflag settings

A

B

C DE

H

I

No

Yes

No

Yes

Yes

No

1

F

G

No

Yes

6

Any error

returned?

messages

Areflags correct

Call HP

ifconfigsuccessful

?

Modify/etc/rc.config.d/netconf

Correct problemaccording to themessage received


Chapter 7154


A. Execute ifconfig <interface> <IP address> up on thelink aggregate you want to configure in order to ensurethat the link aggregate is enabled. For example, toconfigure an IP address for the link aggregate lan100,enter:

ifconfig lan100 192.6.1.17 up

For more examples of the ifconfig command, refer tothe ifconfig(1M) online man page.

B. Execute ifconfig <interface> without the up parameteragain, to check the flag setting on the link aggregateyou want to test for the UP parameter. For example, tocheck the link aggregate lan100, enter:

ifconfig lan100

C. ifconfig successful? ifconfig is successful if theoutput shows the correct Internet address and theflags: <UP, BROADCAST, NOTRAILERS, RUNNING>.

Note: Make sure the UP flag is displayed.

D. Are flags correct? If flags are not correct, use theifconfig command to correct them. If they are correct,go to Step F.

E. Correct ifconfig flag settings. If ifconfigreturns an incorrect flag setting, re-execute thecommand with the proper setting. For moreinformation, refer to the ifconfig(1M) online man page.Start again with Flowchart 5, as necessary.

F. Any error message returned? If ifconfig is notsuccessful, and an error message appears, go to Step G.If no error messages appear, contact your HPrepresentative.

G. Correct problem according to the messagereceived. If you received an error message, make theappropriate corrections stated in the message and thenbegin this procedure again.


Chapter 7 155

H. ifconfig entry in /etc/rc.config.d/netconf?Check that there is an entry in the/etc/rc.config.d/netconf file for your10/100Base-TX card.

I. Modify the /etc/rc.config.d/netconf fileaccording the IP address you want assigned tothe link aggregate. Then run the followingcommand:

/sbin/init.d/net start

For more information, refer to the ifconfig(1M) onlineman page. Go back to Flowchart 1 to verify that theproblem has been solved.


Chapter 7156

Flowchart 7: ARP Verification

Figure 7-12 Flowchart 7: ARP Verification

7

A

D Entrycomplete

?

Yes

Bring upremote host

Yes

No

NoE

BRemotehost up

?

Yes

No

Use arp/ifconfig toarp complete entry

F

ping local host

Host entryin ARP

?cache

C

1

1

1


Chapter 7 157

Flowchart 7: Procedures

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

arp spiff

B. Remote host up? If there is no ARP cache entry forthe remote host, first check that the remote host is up.If not, the remote host has not broadcast an ARPmessage, and that probably is why there is no entry inthe ARP cache

C. Bring-up remote host. Have the node manager ofthe remote host bring that system up and start againwith Flowchart 1.

D. Entry complete? Perhaps there is an ARP cacheentry, but it is wrong or not complete. If the entry iscomplete, go to Step F.

E. Use arp to complete entry. Using arp, enter thecorrect Station Address. For more information, refer tothe arp(1M) online man page. Also, try running thefollowing commands on the link aggregate which is notworking properly. For example, if link aggregate 100 isnot working properly execute the following commands:

ifconfig lan100 down

ifconfig lan100 up

Start again with Flowchart 1.

F. ping local host. Using ping, do an internal loopbackon your own system. In other words, ping your ownsystem.

If the internal loopback is successful, your system isoperating properly to the Network Layer (OSI Layer 3).In addition, you know an ARP cache entry for theremote host exists on your system. Start again withFlowchart 1.


Chapter 7158

Flowchart 8: Link Level Loopback Test

Figure 7-13 Flowchart 8: Link Level Loopback Test

8

C

Loopback FAILED:Address has bad

Loopback FAILED:E

LoopbackFAILEDNot an individual

Correct the link

Hlinkloop

?No

Check remote host’sconnectivity to

successful

D

F

I

GChoose a different

remote host

AExecute: linkloop

to remote host

B linkloopsuccessful

?

Yes

Yes

No

format address

address parameterre-executelinkloop.

link aggregate

8

7

1

1


Chapter 7 159


A. Execute: linkloop to remote host. Enter the PPAof your link aggregate and link level address (stationaddress) of the remote host in hexadecimal form(preceded by “0x”). Execute lanscan (1M) on the localsystem to find the PPA and obtain the link leveladdress (station address) of the remote host. For moreinformation on linkloop, refer to the linkloop(1M)online man page.

B. linkloop successful? If the test was successful, goto 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 wasreturned and continue with this flowchart.

C. Loopback failed: Address has bad format. Thelink level address is not correct. Go to Step F.

D. Loopback failed: Not an individual address.The link level address is not correct. The firsthexadecimal digit has its high order bit set (if the valueis equal to or greater than 8, it is set). This means it isa multicast or broadcast address, which is not allowed.The address must be unique to one remote host. Go toStep F.

E. Loopback failed. The remote host did not respond.Go to Step G.

F. Correct the link address parameter. Change thelink level address to an allowed value and start againwith Flowchart 8.

G. Choose a different remote host; re-executelinkloop. Restart Flowchart 7 using a differentremote host. If this does not work, then check theswitch configuration to verify the link aggregate on theswitch is configured correctly.

H. linkloop successful? If the test was successful, goto Step I. Network connectivity is OK through the LinkLayer (OSI Layer 2). If not successful, the problem maybe with the remote system. Go to Flowchart 7.


Chapter 7160

I. Check remote host's connectivity to linkaggregate. Contact the node manager of the remotehost. Check that the host is configured correctly andthat its network interface is up. If necessary, useFlowchart 1 to verify configuration of the remote host.


Chapter 7 161

Flowchart 9: Transport Level Loopback Test (usingARPA)

Figure 7-14 Flowchart 9: Transport Level Loopback Test (using ARPA)

9

B

DSuccessful

?

Call HP

No

FNetworkcongested

?

No

No

Yes

CExecute: ftp to

Successful?

A

Execute: telnet to

StopYes

Call HP

YesE TCP not

configured on

?

remote host

remote host

local or remotehost

G

Call HPYes

No

Configure TCP 9


Chapter 7162


A. Execute: telnet to remote host. Try to establish atelnet connection to the remote host.

B. Successful? If your telnet attempt was successful,stop. The connection is OK through the TransportLayer (OSI Layer 4).

C. Execute: ftp to remote host. Unlike telnet, ftpdoes not go through a pseudoterminal driver (pty) onyour system. This step tests to see if the pty is whytelnet failed.

D. Successful? If ftp is successful, you likely have aproblem with a pty on your system. Contact your HPrepresentative.

E. TCP not configured on local or remote host?Neither telnet nor ftp will work if TCP is not configuredon either side of the connection. Check the/etc/protocols file on both hosts to be sure TCP isinstalled and configured.

F. Network congested? If TCP is installed on both hosts,do a file transfer to another remote host on thenetwork. Use netstat(1) to check for lost packets.

If network congestion is not the cause, more detaileddiagnostics are required. Again, contact your HPrepresentative.

G. Configure TCP. If necessary, install TCP on either orboth hosts. Start again with this flowchart.


Chapter 7 163

Flowchart 10: Bridge/Gateway Loopback Test

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

10

FNon-HP 9000 or

Configure interface

G

If HP 9000

up

Network

?interface up

I

execute: ifconfigon gateway host

A

Execute: ping fromknown good host B

Successful?

Yes

No

CCheck route table

on problem host andthrough gateway toknown good host all hosts between

DExaminegateway

ECorrect route

tables

other vendors.

1

1

Refer to networkingdocumentation

H3

yes

no


Chapter 7164


A. Execute: ping from known good host throughgateway to known good remote host. This will testgateway connectivity to the remote network.

B. Successful? If the executing ping returnedsuccessfully, the problem may exist in the routing tablefor the problem host. Go to Step C.

C. Check route table on problem host and allhosts in between. Execute netstat -r to examine aroute table.

D. Examine gateway. If the gateway is an HP 9000, go toStep G. If it is not, go to Step F.

E. Correct route tables. Ensure that the properIP/Internet addresses are assigned in the Destinationand Gateway fields. If you are using subnetting, makesure that the destination is what you expect: a networkor a host. Go back to Flowchart 1 to verify that theproblem is solved.

F. Non-HP 9000 or other vendors. Refer to networkingdocumentation. Refer to the documentation that camewith the gateway for additional diagnostics.

G. If HP 9000, execute ifconfig on gateway host.Execute ifconfig for all network interfaces on thegateway.

H. Network interface up? If the output from ifconfigdoes not include the UP parameter, the networkinterface is down. Execute netstat -i to check the statusof the network interfaces. An asterisk (*) indicates thatthe interface is DOWN. If the network interface isDOWN, go to Step I.

If the network interfaces are UP, start again withFlowchart 3. Using Flowchart 3, test all networkinterfaces on the gateway.

I. Configure interface up. Execute ifconfig on eachinterface to bring it up. Start again with Flowchart 1.Use Flowchart 1 to test all network interfaces on thegateway.

Troubleshooting HP Auto Port Aggregation (APA) SoftwareKnown Problems and Workarounds

Chapter 7 165

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 maycause installation failures, and HP APA may not function correctly. Seethe note (labelled Important) after the “Required Patches” section fordetails.

Known Problems with Switches

• HP ProCurve Switches

When disabling Cisco’s Fast EtherChannel protocol on the HP 9000server, the HP ProCurve switches will block that particular port fromfurther usage.

Corrective Action: In order to use the network physical port on theHP 9000 server after disabling Cisco’s Fast EtherChannel, you mustphysically move the connection from the server to the switch toanother non-Cisco Fast EtherChannel port on the switch.

• Cisco Catalyst 5000 Switches

— Turning off Cisco’s Fast EtherChannel on one network physicalport on the HP 9000 server may cause the entire link aggregate(the port it is associated with) to be deconfigured.

Corrective Action: This problem can only be corrected byreconfiguring the switch to not include the port in the linkaggregate being configured. Refer to the appropriate switchdocumentation for details on how to reconfigure link aggregates.

The Catalyst 5000 switch only allows two- or four-port linkaggregates. Refer to the Cisco Catalyst 5000 Configuration Guidefor more details on these limitations.

Troubleshooting HP Auto Port Aggregation (APA) SoftwareKnown Problems and Workarounds

Chapter 7166

A known problem has been fixed for HSC 100Base-TX, and PCI4-port 100Base-TX when interfacing to a Cisco Catalyst 5000switch [with firmware version 4.5(4)] with ports in DesirableMode 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 fixrequires patch PHNE_20420, and the PCI 4-port fix is in patchPHNE_20423. You also need the core LAN patch PHNE_20657(or later). For HP-UX 11i, the 100Base-T fix is in patchPHNE_23465.

• 3Com SuperStack II Switches

To interoperate with the switch, disable the Trunk Control MessageProtocol (TCMP) on all of the ports that are being used with HP 9000servers.

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

Chapter 7 167

Using the lanadmin Command for TestingYou can use the lanadmin -X command (uppercase X) with options tomake temporary changes to APA.

CAUTION The lanadmin command does not preserve your changes across reboots.To permanently save your configuration, use SAM or edit theconfiguration files.

Tasks You Can Perform with the lanadmin Command

You can perform the following tasks using the lanadmin command:

• Link aggregate specific commands (lanadmin options are inparentheses):

— Manually configure 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-configure (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 configure a link aggregate:

— Enable LACP or FEC on all physical ports. See Port specificcommands, below.

— De-configure a link aggregate.


Chapter 7168

— Specify load-distribution algorithm.

— Specify hot-standby mode.

— View status of a link aggregate.

• Port specific commands:

NOTE Remember that the starting PPA number for link aggregates varieswith the operating system you have installed: for HP-UX 10.20, it is90; for 11.x, it is 100; and 11i, it is 900. The following example usesHP-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_priorityAnyLinkAggregatePPA ).

— 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 theaddition of ports to a link aggregate. The following options are for usealong 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 ]


Chapter 7 169

[-X -s PortPPA system_priority AnyLinkAggregatePPA[-X -t PortPPA port_priority AnyLinkAggregatePPA ][-X -y on|off LinkAggregatePPA ]

-a Add ports with the specified portPPA s, to the linkaggregate with the specified linkaggregatePPAnumber.

-c Clear (remove all) ports from a link aggregate with thespecified linkaggregatePPA number.

-d Delete ports with the specified PPAs from the linkaggregate with the specified linkaggregatePPAnumber.

-g Set group capability for a port with the specifiedportPPA . The valid values for group_capability areintegral numbers starting at 0.

-h Print out the help screen.

-H Print out the extended help screen.

-k Set Administrative key for an LACP port.

-l Set the load distribution algorithm for a link aggregatewith the specified linkaggregatePPA number.

The following values are valid forload_distribution_algorithm :

LB_CPU — Based on the process specific CPU.Appropriate for server-server configuration.

LB_MAC — Based on the MAC Address of the outgoingpacket. Appropriate for server-to-switch configuration.

LB_IP — Based on the IP Address of the outgoingpacket. Appropriate for server-to-router configuration.

-o Clear Data Flows for a LinkAggregate

-p Set Mode for a port with the specified portPPA number.The following values are valid:

• LACP_AUTO Turn on IEEE 802.3ad (LACP)

• FEC_AUTOTurn on Fast EtherChannel (FEC) on theport for automatic port aggregation.


Chapter 7170

• MANUALTurn off Fast EtherChannel (FEC) or IEEE802.3ad (LACP) on the port.

• LAN_MONITOR Provides Hot Standby capability.

-s Set System Priority for an LACP port.

-t Set port priority for the port with the specified PPANumber. You can specify any valid link aggregate PPAnumber with this option.

The valid values for port_priority are integralnumbers starting at 0.

-y Turn on/off hot standby for the link aggregate withthe specified 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 linkaggregate with the specified linkaggregatePPAnumber.

-h Print out the help screen.

-H Print out the extended help screen.

-k Get administrative and operational key for an LACPport.

-l Display the current load distribution algorithm for thelink aggregate with the specified linkaggregatePPAnumber.

-m View status for all LinkAggregates.


Chapter 7 171

-n View status for all APA capable ports.

-p Display the present status of a port with the specifiedportPPA number.

-q Display the present status of a port with the specifiedportPPA in the extended format.

-s Get system priority for an LACP port.

-t Display the current port priority for the port with thespecified portPPA number.

-v View status for a given link aggregate with thespecified linkaggregatePPA number.

-y Display Hot Standby value for the link aggregate withthe specified linkaggregatePPA number.

lanadmin [-a linkaggregatePPA

The following existing option is supported though with a differentmeaning:

-a Display current station address of link aggregate withthe specified 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 lanadmincommand, 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 Cisco’s FastEtherChannel protocol on that port. Suppose port #2 needed to beconfigured automatically:

lanadmin -X -p 2 FEC_AUTO 100


Chapter 7172

where 100 is the PPA of the first link aggregate. When the protocolcompletes successfully, HP_APA will determine which link aggregateport #2 will best fit and add the port there.

• To configure ports with PPAs 6, 7, 8 and 9 manually into a linkaggregate, 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 aninvalid link aggregate. This command gives you full control overforming any link aggregate that you want. You can configure portswith PPAs 6, 7, 8, and 9 into a single link aggregate even if they areconnected to different switches, which is an invalid configuration,and could lead to problems.

NOTE If you are using MANUAL mode configuration, ensure that theswitch configuration is set for the manual configuration.

• Before you can remove a port from an automatically formed linkaggregate, you must turn off Cisco’s Fast EtherChannel protocol onthat port. If a port with a PPA number of 2 belongs to link aggregatelan100 (which has a PPA number of 100), then use one of thefollowing two commands:

lanadmin -X -d 2 100 or

lanadmin -X -p 2 MANUAL 100

• To de-configure a link aggregate, say 103, which has ports with PPAs6, 7, 8, and 9, use the following commands in succession:

lanadmin -X -p 6 MANUAL 103lanadmin -X -p 7 MANUAL 103lanadmin -X -p 8 MANUAL 103lanadmin -X -p 9 MANUAL 103

Or, the following single command will achieve the same result:

lanadmin -X -d 6 7 8 9 103

• To fully deconfigure a link aggregate, use the following command:


Chapter 7 173

lanadmin -X -c 103

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

• To delete a single port, say 8, from link aggregate 101 the followingcan be done:

lanadmin -X -d 8 101

To also delete 6 and 9:

lanadmin -X -d 6 9 101

• To deconfigure the link aggregate 101 completely:

lanadmin -X -c 101

This will delete the remaining port, 7, from link aggregate 101, andthen clear all the properties from the link aggregate, so that itbecomes completely clean.

CAUTION After all the ports have been deleted from link aggregate 101, (afterusing, for example, lanadmin -X -d 7 100 ), failure to use the -csub-option may result in some properties being retained in linkaggregate 101, and subsequently, when a new set of ports is added tolink aggregate 101, they will inherit old properties of the linkaggregate. 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, thecommand becomes interactive. The following example illustrates theinteractive use of lanadmin:

lanadmin

LAN ONLINE ADMINISTRATION, Version 1.1


Chapter 7174

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


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


display= display LAN Interface status and statistics registers

end

= End LAN Interface Administration, return to Test Selection




Chapter 7 175




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 7176

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


display= Display LinkAggregate status and statistics registers

end= End LAN Interface test mode, return to Test selection mode.


ppa= PPA Number of the LinkAggregate




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 mode.



Enter command:

linkagg

Number of ports: 4

Ports PPA: 4 2 5 3

Link Aggregation Mod: Automatic Aggregation

Group Capability: 51


Chapter 7 177

Load Balance Mode MAC Address based (LB_MAC)

Hot Standby Mode: ON

Valid LAN Interface PPAs: 4 2 5 3

Driver specific test mode



end= End Driver Specific Test Mode, return to Lan Interface test 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 7178

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.



end= End Driver Specific Test Mode, return to Lan Interface test mode

menuDisplay this menu

ppaPPA Number of the LAN Interface

quitTerminate the Administration, return to shell

Enter command:

quit

Appendix A 179

A HP Auto Port Aggregation (APA)Statistics

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

Appendix A180

HP Auto Port Aggregation StatisticsThis section describes how link aggregate level statistics are collectedand reported. The link aggregate software keeps a counter for eachstatistic defined in RFC 1213 MIB II. Each counter is set to the negativeof the sum of all the physical ports in the link aggregate when it iscreated. When reporting the value of a statistic, the sum of all thephysical ports corresponding statistic counter is added to the linkaggregates counter.

When a physical port is removed from a link aggregate, each of it’sstatistics is added to the corresponding link aggregate statistic. When aphysical port is added to a link aggregate, it’s current statistics aresubtracted from the link aggregates statistics.

NOTE Cisco’s Fast EtherChannel (FEC) packets are not counted in the linkaggregate statistics. This is required because the FEC packets nevertraverse the link aggregate, they only traverse the port. Therefore, theyshould not be included in the link aggregation level statistics.

HP Auto Port Aggregation (APA) StatisticsLAN Interface Status Display

Appendix A 181

LAN Interface Status DisplayThis section contains a description of the RFC 1213 MIB II statisticsfields for LAN interface cards which are displayed on the screen with thedisplay command in lanadmin LAN interface Test Mode. This samecommand is also used to examine RFC 1213 MIB II statistics for logicallink aggregate interfaces. Refer to View Link Aggregate Statistics for asample output.

HP Auto Port Aggregation (APA) StatisticsRFC 1213 MIB II

Appendix A182

RFC 1213 MIB IIFor additional information about the fields described below, refer to RFC1213.

Field Description

NetworkManagement ID A unique ID assigned by the system for the network

management of each network interface.

Description A textual string containing information about theinterface.

Type (value) The type of interface, distinguished according to thephysical/link protocols, immediately below the networklayer 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 besent/received on the interface specified in octets. Thisvalue is 1500.

Speed in bitsper second The speed of the link in bits per second.

Station Address The interface address at the protocol layer immediatelybelow the network layer in the protocol stack. Forinterfaces which do not have such an address, such asserial line, this object contains an octet string of zerolength.

AdministrationStatus The desired state of the interface. This parameter is set

to up(1) and is not configurable. It will have one of thefollowing values:

Table A-1

up(1) Ready to pass packets

down(2) Not operative


Appendix A 183

OperationStatus The current operational state of the interface. This

value is the same as the hardware status displayed bylanscan(1M). It will have one of the following values.

Last Change The value of SysUpTime at the time the interfaceentered its current operational state. If the currentstate was entered prior to the last reinitialization of thelocal network management subsystem, then this objectcontains a zero value.

Inbound Octets The total number of octets received on the interface,including framing characters.

Inbound UnicastPackets 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.

InboundDiscards The number of inbound packets that were discarded

even though no errors had been detected, to preventtheir being delivered to a higher-layer protocol. Onepossible reason for discarding such a packet could be tofree up buffer space.

Inbound Errors The number of inbound packets that contained errorspreventing them from being deliverable to ahigher-layer protocol.

testing(3) In test mode

Table A-2

up(1) Ready to pass packets

down(2) Not operative (card isdown)

testing(3) In test mode

Table A-1 (Continued)


Appendix A184

InboundUnknownProtocols The number of packets received via the interface which

were discarded because of an unknown or unsupportedprotocol.

OutboundOctets The total number of octets transmitted out of the

interface, including framing characters.

OutboundUnicastPackets The total number of packets that higher-level protocols

requested be transmitted to a subnetwork-unicastaddress, including those that were discarded or notsent.

OutboundNon-UnicastPackets The total number of packets that higher-level protocols

requested be transmitted to a non-unicast (asubnetwork-broadcast or subnetwork-multicast)address, including those that were discarded or notsent.

OutboundDiscards The number of outbound packets that were discarded

even though no errors had been detected to preventtheir being transmitted. One possible reason fordiscarding such a packet could be to free up bufferspace.

OutboundErrors The number of outbound packets that could not be

transmitted because of errors.

OutboundQueue Length The length of the output packet queue (in packets).

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

Appendix A 185

View Link Aggregate Characteristics Usinglanscan

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

lanscan Output

Following are examples of the various outputs from the lanscancommand.

• lanscan on systems without HP APA installed remains the same.

# lanscan

• lanscan on the same machine, with link aggregation enabled. In thisexample, 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 anylonger. You can only see lan100.

Table A-3

Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPIPath Address In# State NamePPA ID Type Support Mjr#10/4/8.1 0x080009B7C158 6 UP lan6 snap6 1 ETHER Yes 1198/0/1/0 0x0060B0220001 0 UP lan0 snap0 2 ETHER Yes 1198/0/2/0 0x0060B0220002 1 UP lan1 snap1 3 ETHER Yes 1198/4/2/0 0x0060B04B2B43 3 UP lan3 snap3 4 ETHER Yes 1198/8/2/0 0x0060B04BAB85 5 UP lan5 snap5 5 ETHER Yes 1198/4/1/0 0x0060B04B2B42 2 UP lan2 snap2 6 ETHER Yes 1198/8/1/0 0x0060B04BAB84 4 UP lan4 snap4 7 ETHER Yes 11910/12/6 0x080009F0165D 7 UP lan7 snap7 8 ETHER Yes 119


Appendix A186

# lanscan

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

lanscan -v

Table A-4

Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPIPath Address In# State NamePPA ID Type Support Mjr#10/4/8.1 0x080009B7C158 6 UP lan6 snap6 1 ETHER Yes 1198/0/1/0 0x0060B0220001 0 UP lan0 snap0 2 ETHER Yes 1198/0/2/0 0x0060B0220002 1 UP lan1 snap1 3 ETHER Yes 11910/12/6 0x080009F0165D 7 UP lan7 snap7 8 ETHER Yes 119LinkAgg0 0x0060B04BAB84 100 UP lan100 snap100 10 ETHER Yes 119LinkAgg1 0x000000000000 101 DOWN lan101 snap101 11 ETHER Yes 119LinkAgg2 0x000000000000 102 DOWN lan102 snap102 12 ETHER Yes 119LinkAgg3 0x000000000000 103 DOWN lan103 snap103 13 ETHER Yes 119LinkAgg4 0x000000000000 104 DOWN lan104 snap104 14 ETHER Yes 119

Table A-5

------------------------------------------------------------------Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPIPath Address In# State NamePPA ID Type Support Mjr#Link Agg 0x0060B04BAB84 100 UP lan100 snap100 10 ETHER Yes 119

Extended Station LLC EncapsulationAddress Methods0x0060B04BAB84 IEEE HPEXTIEEE SNAP ETHER NOVELL

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


Appendix A 187

• lanscan with the option -q (extended print-ppa).

lanscan -q

6017100 4 2 5 3101102103104


Appendix A188

Appendix B 189

B Load Balancing and Data FlowAlgorithms

Load Balancing and Data Flow AlgorithmsSupported Load Balancing and Data Flow Algorithms

Appendix B190

Supported Load Balancing and Data FlowAlgorithmsThe algorithms described below only apply to outbound data transfer.Inbound Load Balancing and Data Flow Distribution are strictlydetermined by the link partner and have no affect on the outboundalgorithms. In addition, although each of these algorithms can be used inall supported configurations, they may not all provide the same load oneach of the physical ports in the link aggregate. Therefore, HP prefersyou use the algorithm that's recommended for each supportedconfiguration.

Load Balancing and Data Flow AlgorithmsPacket Ordering

Appendix B 191

Packet OrderingEach of the algorithms below guarantees that they will not introduce anysevere ordering problems within a specific data flow. This is required tomake sure that the performance is not degraded significantly as a resultof turning on one of the algorithms.

Further, all packets for a specific data flow will always flow out throughthe same physical port (the only exception is CPU based distribution)until the data flow is aged out of the distribution table (see below). Thismeans that in order to generate simultaneous load on each of thephysical ports in a link aggregate, multiple data flows must be startedover the link aggregate.

Load Balancing and Data Flow AlgorithmsLoad Balancing Algorithm

Appendix B192

Load Balancing AlgorithmThe Load Balancing algorithm is described as a simple three stepprocess.

1. Data Flow Lookup — The Data Flow Distribution algorithm (nextsection) determines an index into a hash table which includes thephysical port the data flow should be forwarded out of.

2. Data Flow Physical Port Assignment — If the hash index for thedata flow has not been assigned a physical port (the entry is NULL),then a physical port in the link aggregate is assigned to that specifichash index. The physical port is selected on a Round Robin basis.

3. Aging Data Flows — Over time each data flow is checked todetermine if it is still active. If the data flow has not been active inthe last 30 seconds, it's specific hash index is cleared (aged out). Ifthe data flow restarts after being cleared from the hash table it willbe re-assigned a new physical port on a Round Robin basis.

Load Balancing and Data Flow AlgorithmsData Flow Distribution Algorithms

Appendix B 193

Data Flow Distribution AlgorithmsListed below are the three supported Data Flow Distribution algorithms,plus the Hot Standby mode. Each algorithm is briefly explained and therecommended configuration for the specific algorithm is also listed.

For examples on configuring the algorithms, please refer to the earlierchapters on configuration in this guide.

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

• Destination MAC address

The Destination MAC address based algorithm uses the leastsignificant byte of the link level destination MAC address, of the dataflow, as an index into a table of 256 possible entries. If the entry isNULL, then a physical port is selected from the link aggregate on aRound Robin basis and assigned to the index. The physical portselected will be used to send packets for the duration of the specificdata flow.

This is the default algorithm for all link aggregates.

Recommended Configuration: Server-to-Switch.

• IP address

The IP address based algorithm uses the least significant bytes of thesource and destination IP address, of the data flow, as an index into atable of 256 possible entries. The same processing that occurs fordestination MAC distribution is used if the entry is NULL.

Recommended Configuration: Server-to-Router.

• LB_PORT — TCP/UDP Port-based Algorithm

The TCP/UDP Port-based algorithm uses the TCP/UDP source anddestination port numbers to distribute traffic across the ports in aLink Aggregate. This algorithm is recommended for use whenconnecting two HP 9000 servers in a back-to-back configuration.

Recommended configuration: Server-to-Server

Load Balancing and Data Flow AlgorithmsData Flow Distribution Algorithms

Appendix B194

• Hot Standby

Hot Standby ON mode uses one primary link in the link aggregate tosend all outbound traffic on. Therefore, when this mode is enabledthere is no load balancing across the network physical ports in thelink aggregate. If the primary link goes down (for example, cabledisconnect) then all the traffic on the primary link is automaticallyswitched to a secondary link in the same link aggregate.

The primary and secondary links are determined by the Port Priorityof the network physical ports in the link aggregate. The networkphysical port with the highest Port Priority is used as the primarylink. If there are multiple network physical ports with equal PortPriorities then the APA software will pick one of the ports.

This configuration is recommended for servers that needhighly available network interfaces.

• CPU — No longer recommended when usingServer-to-Server. See LB_PORT

The CPU based algorithm uses the processor index that the data flowis being serviced on, as an index into a table of 256 possible entries.Therefore, this algorithm relies on the CPU scheduler to determinehow data flows will be distributed across different physical ports.

This configuration should not be used on Uni-Processor systems asonly one physical port in the link aggregate will be used.

NOTE Since this algorithm relies on the CPU scheduler to determine wherethe packets for a specific data flow will be sent, it is possible for aspecific data flow to move from one physical port to another duringthe lifetime of the data flow. This is possible because if one CPUbecomes loaded, one or more processes may need to be migrated toanother CPU. This can lead to a specific data flow sending data outone interface and then switching to another due to an overloadedCPU. This may cause a temporary ordering problem, but should notresult in any significant or prolonged performance problems.

Appendix C 195

C HP Auto Port Aggregation (APA)Resources

HP Auto Port Aggregation (APA) Resources

Appendix C196

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

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

Appendix C 197

HP-UX Manual Reference Pages (man pages)While installing, configuring, or troubleshooting HP APA, you may needto refer to any of the following online manual reference pages (manpages) for useful HP-UX operating system or HP APA commands. Todisplay a man page, type the following at the system prompt: man<command name>. For example, man arp .

• arp(1M) displays and modifies the Internet-to-station addressmapping tables used by the Address Resolution Protocol.

• hosts(4) is a database that contains a single line entry for each hostname entry.

• ifconfig(1M) assigns an address to a network interface, andconfigures and displays network parameters.

• ioscan(1M) scans system hardware, usable I/O system devices, orkernel I/O system data structures as appropriate, and lists theresults.

• lanadmin(1M) resets or reports the status of the LAN card.

• lanscan(1M) displays information about LAN cards that aresuccessfully bound to the system.

• linkloop(1M) verifies network connectivity through the Data LinkLayer (OSI Layer 2).

• netfmt(1M) formats common tracing and logging binary files.

• netstat(1) provides network statistics and information about networkconnections.

• nettl(1M) logs network events and traces packets as they enter andexit the 10/100Base-TX driver.

• ping(1M) verifies network connectivity through the Network Layer(OSI Layer 3) and reports the round-trip time of communicationsbetween the local and remote hosts.

• route(1M) adds and deletes entries to the network routing table.

• sam(1M) configures networking software.

• swinstall(1M) loads software filesets onto 10.x and later systems.

• swverify(1M) verifies software installation.

HP Auto Port Aggregation (APA) ResourcesError Messages

Appendix C198

Error MessagesHP APA comes with an online message catalog that is used to reportnetworking problems. You must use the nettl logging and tracing utilityto display the probable cause and action for a message.

HP Auto Port Aggregation (APA) ResourcesLogging Messages

Appendix C 199

Logging MessagesThe HP network physical port and the HP APA software use thenettl(1M) logging and tracing facility supplied with HP-UX. You mayaccess the logging and tracing utility using either the graphical userinterface (GUI) version or the command line interface.

Features of the GUI version, which are now a part of your HP 9000system, 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-specificinformation.

• Report screens which are updated instantaneously with currentlogging and tracing information by the subsystem.

• Context-sensitive on-line help.

To access the GUI version of the logging and tracing utility, run thecommand:

nettladm

See the nettladm(1M) man page for information on using the GUIversion, or the nettl(1M) manual (man) page for information on using thecommand line interface.

There are three levels of logging

• At link aggregate level.

• At Cisco’s 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 Cisco’s FEC level, use

nettl -log 0xf -e HP_APAPORT

HP Auto Port Aggregation (APA) ResourcesLogging Messages

Appendix C200

• To turn on all logging at IEEE 802.3ad level, use

nettl -log 0xf -e HP_APALACP

• To examine the log file with cause and action descriptions:

netfmt -v -f /var/adm/nettl.LOG00 | more

• To examine just the log messages in the log file, use:netfmt -f var/adm/nettl.LOG00

• To check network logging and tracing status, use:

nettl -status

• To start Cisco’s FEC tracing to the file /tmp/tracefile.TRC0, use

nettl -traceon all -entity HP_APAPORT -file/tmp/tracefile

• To stop Cisco’s FEC tracing, use

nettl -traceoff all -entity HP_APAPORT

• To start LACP tracing to the file /tmp/tracefile.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 tracefile into the file /tmp/traceout, use:

nettl -f /tmp/tracefile.TRC0 > /tmp/traceout

Refer to the netfmt(1M) man page for further information about this cardand how to create a filter for trace formatting.

HP Auto Port Aggregation (APA) ResourcesContacting Your HP Representative

Appendix C 201

Contacting Your HP RepresentativeIf you have no service contract with HP, you may follow the proceduredescribed below, but you will be billed accordingly for time and materials.

If you have a service contract with HP, document the problem as aService Request (SR) and forward it to your HP representative. Includethe following information where applicable:

• A description of the problem. Describe the events leading up to andincluding the problem. Attempt to describe the source and symptomsof the problem.

Your description should include: HP-UX commands; communicationsubsystem commands; job streams; result codes and messages; anddata that can reproduce the problem. You should also provide anetwork map with the host name, IP/Internet address, and stationaddress 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 anduser terminal.

• Obtain the version, update, and fix information for all software. Tocheck the HP APA version number, execute what vmunix and look forthe 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 ifthe correct software is installed at your site.

• Prepare copies of all the following files:

— /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 statusof the HP APA card.

• Execute the lanscan -v command and record the output.

HP Auto Port Aggregation (APA) ResourcesContacting Your HP Representative

Appendix C202

• Execute the display command of the lanadmin diagnostic on the HPAPA interface and record the output.

• Record the troubleshooting flowchart number and step numberwhere you are unable to resolve the problem.

• Record all error messages and numbers that appear at the userterminal and the system console.

• Save all network log files. Make sure that ERROR and DISASTERlog classes are enabled when log files are collected.

Prepare the formatted output and a copy of the log file for your HPrepresentative to further analyze.

• Prepare a listing of the HP-UX I/O configuration you are using foryour HP representative to further analyze. Use the ioscan(1M)command to help collect this information.

• Prepare a list of your switch trunking configuration related to thisproblem.

• Try to determine the general area within the software where youthink the problem exists. Refer to the appropriate reference manualand follow the guidelines on gathering information for that product.

• Document your interim, or “workaround,” solution. The cause of theproblem can sometimes be found by comparing the circumstances inwhich it occurs with the circumstances in which it does not occur.

• Create copies of any Internet or HP APA/9000 link trace files thatwere active when the problem occurred for your HP representative tofurther analyze.

• In the event of a system failure, a full memory dump must betaken. Use the HP-UX utility savecore(1M) to save a core dump.Send the output to your HP representative.

HP Auto Port Aggregation (APA) ResourcesWhat Manuals are Available

Appendix C 203

What Manuals are AvailableThe following documents are available:

• HP Auto Port Aggregation Quick Installation Guide

This document summarizes the installation, configuration,verification, and troubleshooting of the HP Auto Port Aggregationproduct.

• HP Auto Port Aggregation Release Notes

This document provides summarized information about the HP AutoPort Aggregation product, and late-breaking information that is notin either the Quick Installation or User’s guides. It is an online onlyfile located on your system in /opt/networkdocs or on theworldwide web at http://www.docs.hp.com

HP Auto Port Aggregation (APA) ResourcesSoftware Product Numbers and Filesets

Appendix C204

Software Product Numbers and FilesetsPart 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 productsand filesets:

Product Filesets:

APA-KRN

APA-RUN

APA-INIT

APA-FORMAT

SAM-APA

APA-LM

Glossary 205

Glossary

A

aggregate A group. In this product a groupof four ports makes one link aggregate.There can be 50 link aggregates percomputer.

aggregation See aggregate.

APA Auto Port Aggregation

Auto Port Aggregation (APA) HP’ssoftware product that allows grouping up tofour ports into an aggregate to boostperformance and provide port fail-over.

F

fail-over group a logical grouping of one ormore physical ports formed by LAN Monitor.The failover group is used as an alternativeif the primary link fails.

Fast EtherChannel (FEC) Theproprietary name of Cisco’s port aggregationproduct. When referring to FEC mode, itindicates use of PAgP on a link.

FEC See Fast EtherChannel

FEC_AUTO The automatic configurationmode of FEC.

flow A sequence of MAC frames between apair of hosts where all of the MAC framesform part of the same conversation betweenthat pair of hosts.

G

group capability An integer value used todetermine which network physical ports canbe aggregated into a common link aggregate.

H

Hot Standby A method of providing highavailability

HSC High Speed Connect

L

LACP Link Aggregation Control Protocol

LAN Local Area Network

LB_IP Internet Protocol-based algorithmfor server-to-router configurations.

LB_MAC MAC-based algorithm forserver-to-switch configurations (this is thedefault algorithm). See “Load Balancing andData Flow Distribution Algorithm” fordetails.

LB_PORT TCP/UDP port-based algorithmfor server-to-server (back-to-back)configurations

link aggregate A logical grouping of one ormore physical ports into a single “fat-pipe”.This term is used to describe LACP, Manual,or PAgP (Cisco Fast EtherChannel) createdlogical ports.

link aggregation See link aggregate

linkaggPPA The PPA or logical cardinstance number of a specific link aggregate.

load balancing A method of distributingtraffic across the network physical ports in alink aggregate. Unicast and multicast trafficis distributed across the network physicalports in a link aggregate. Broadcast traffic isalways sent out the first network physicalport in a link aggregate

GlossaryMANUAL

Glossary206

M

MANUAL The default mode of portconfiguration. Can be performed by editingtwo configuration files or by using SAM.

MAC Media Access Control

MIB Management Information Base

N

network adapter A network device whichhas one or more network physical ports.

network physical port Thecommunications channel formed when youattach a network cable between a specificnetwork port (adapter card) and a LANdevice.

P

PAgP See Port Aggregation Protocol.

PCI Peripheral Component Interconnect

physical point of attachment A uniqueinteger identifier for each network physicalport installed on a server.

port The communications channel formedwhen you attach a network cable between anetwork physical port and a LAN device.

port aggregate See link aggregate.

port aggregation See link aggregate

Port Aggregation Protocol (PAgP) Theproprietary port aggregation protocol,developed by Cisco Systems Inc., which

automatically determines a bidirectionalconnection between two network physicalports.

port priority An integer value used todetermine which network physical port willbe used as the primary port in a linkaggregate in hot standby mode.

PPA See physical point of attachment

S

SAM System Administration Management

Server-to-Router See LB_IP.

Server-to-Server See LB_PORT.

Server-to-Switch See LB_MAC.

Date post:	16-Oct-2014
Category:	Documents
Upload:	walter-lopez
View:	929 times
Download:	2 times

Using HP Auto Port Aggregation APA

Documents