HP Auto Port Aggregation (APA) Release Notes HP-UX 11i v1, 11i v2, and 11i v3 (March 2011)

3 HP APA Overview for HP-UX 11i v3
This chapter provides information about the HP-UX 11i v3 (B.11.31.50) March 2011 release of
HP Auto Port Aggregation (APA) and LAN Monitor software.
This release of HP APA is a defect fix only release; there are no new features.
Auto Port Aggregation
HP APA is a software product that creates link aggregates, often called "trunks," which provide a
logical grouping of two or more physical ports into a single "Fat-Pipe." Network traffic is load
balanced across all of the links in the aggregation, which allows you to build large bandwidth
logical links into the server that are highly available and completely transparent to the client and
server applications.
In addition, HP APA provides automatic link failure detection and recovery, and optional support
for load balancing of network traffic across all of the links in the aggregation.
HP APA supports HP Serviceguard. See the HP Auto Port Aggregation (APA) Administrator's Guide
for more information.
Failover Group
HP APA supports the creation of failover groups (link aggregates in LAN_MONITOR mode),
providing a failover capability for links. In the event of a link failure, LAN Monitor automatically
migrates traffic to an available, standby link (port or link aggregate) in the failover group.
Known Problems Fixed in This Version
Table 2.1 lists the known problems and fixes in this release of HP APA B.11.31.50.
Table 3 Fixes in the HP APA B.11.31.50 Release
DescriptionDefect ID
Critical Resource Analysis fails on a LAN Monitor link if the link is down or not in the
connected to active state.
QXCR1001018201
In HP APA B.11.31.40, the /sbin/init.d/hpapa script does not recognize the
HP_APA_STATION_ADDRESS parameter in the /etc/rc.config.d/hp_apaconf
file.
QXCR1001056750
The lancheckconf command returns the Memory fault(coredump) message
when reading the /etc/lanmon/lanconfig.ascii file.
QXCR1001074207
Known Problems and Limitations
This section describes the known problems and limitations as known to HP at time of publication.
If workarounds are available, they are included.
Known Problems
• HP ProCurve Switches
When disabling Cisco's Fast Ether Channel protocol on the HP 9000 server, the HP ProCurve
switches block that particular port from further use.
Severity: Medium
Auto Port Aggregation 15