R3721-F3210-F3171-HP High-End Firewalls High Availability Configuration Guide-6PW101

164
BAGG -- Bridge-Aggregation, RAGG -- Route-Aggregation
Aggregation Mode: S -- Static, D -- Dynamic
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Actor System ID: 0x8000, 000f-e2ff-0001
AGG AGG Partner ID Select Unselect Share
Interface Mode Ports Ports Type
-------------------------------------------------------------------------------
RAGG1 S none 2 0 Shar
RAGG2 S none 2 0 Shar
The output shows that link aggregation groups 1 and 2 are both load-shared Layer 3 static
aggregation groups and each contains two Selected ports.
# Display all the group-specific load sharing criteria on Device A.
[DeviceA] display link-aggregation load-sharing mode interface
Route-Aggregation1 Load-Sharing Mode:
source-ip address
Route-Aggregation2 Load-Sharing Mode:
destination-ip address
The output shows that the load sharing criterion for link aggregation group 1 is the source IP
address and the load sharing criterion for link aggregation group 2 is the destination IP address.
Configuration guidelines
Follow these guidelines when you configure a link aggregation group:
• In an aggregation group, only member ports that have the same port attributes and class-two
configurations as the reference port can become selected ports. Make sure that all member ports
have the same port attributes and class-two configurations as the reference port. The other settings
only need to be configured on the aggregate interface, not on the member ports.
• In a static aggregation group, make sure that ports at both end of a link have the same
selected/unselected status. Otherwise, the aggregation function cannot work properly.
• You cannot add a port with any of the following functions enabled to a Layer 2 aggregation group:
RRPP, packet filtering, Ethernet frame filtering, and portal-free rule.
• You cannot add an interface with any of the following functions enabled to a Layer 3 aggregation
group: IP address, DHCP client, BOOTP client, VRRP, and Portal.
• HP does not recommend assigning the reflector port of a port mirroring group to an aggregation
group.
• Removing a Layer 2 aggregate interface also removes the corresponding aggregation group.
Meanwhile, the member ports of the aggregation group, if any, leave the aggregation group.
• When a load-sharing aggregation group becomes a non-load-sharing aggregation group because
of insufficient load sharing resources, one of the following problems may have occurred: The
number of Selected ports of the actor is inconsistent with that of the partner, which may result in
incorrect traffic forwarding; the peer port of a Selected port is an Unselected port, which may result
anomalies in upper-layer protocol and traffic forwarding. You should fully consider the situation
when making configuration.