To view the status of an aggregation, navigate to the Link Aggregation
page as shown below:
Using LACP
The serv
er supports the Link Aggregation Control Protocol (LACP) which it
uses to manage an individual link's transmission state (within a Link
Aggregation Group). The server controls the LACP relationship between
multiple switches. The server determines which network interfaces are in use
and can bring up alternative network interfaces during a failure. For example,
if the server does not receive any LACP messages from the primary switch
(the waiting time is determined by the configured LACP timeout), the server
can use the network interfaces connected to the secondary switch instead.
LACP aggregates are not automatically created or populated. The
administrator must first create an aggregate interface, then enable LACP on
that interface.
Note: The serv
er always sends LACPDUs set to ACTIVE.
LACP timeouts
The serv
er supports both short (one second) and long (30 second) LACP
timers. A short timeout is three seconds (three x one second). A long timeout
is 90s (three x 30 seconds). Therefore, the link times out after three missed
messages. Long timeouts are recommended in order to upgrade upstream
network devices without causing path failover on the server. The default
setting is a short timeout.
Typical LACP configurations
Here are three typical configurations when using LACP with NAS servers:
• Split-LAG with Layer-2 redundancy
• Split-LAG with Layer-2 redundancy and increased bandwidth
16 Network interfaces
Hitachi NAS Platform Network Administration Guide
To Next Page
Need help?
General