Netgear XCM8806 - 8800 SERIES 6-SLOT CHASSIS SWITCH 사용자 설명서
130
|
Chapter 5. Configuring Slots and Ports on a Switch
NETGEAR 8800 User Manual
A LAG port moves into a defaulted state after the timeout value expires with no LACPDUs
received for the other side of the link. You can configure whether you want this defaulted LAG
port removed from the aggregator or added back into the aggregator. If you configure the
LAG to remove ports that move into the default state, those ports are removed from the
aggregator and the port state is set to unselected. The default configuration for defaulted
ports is to be removed, or deleted, from the aggregator.
received for the other side of the link. You can configure whether you want this defaulted LAG
port removed from the aggregator or added back into the aggregator. If you configure the
LAG to remove ports that move into the default state, those ports are removed from the
aggregator and the port state is set to unselected. The default configuration for defaulted
ports is to be removed, or deleted, from the aggregator.
Note:
To force the LACP trunk to behave like a static sharing trunk, use the
configure sharing lacp defaulted-state-action
command to add
ports to the aggregator.
If you configure the LAG to add the defaulted port into the aggregator, the system takes
inventory of the number of ports currently in the aggregator. If there are fewer ports in the
aggregator than the maximum number allowed, the system adds the defaulted port to the
aggregator (port set to selected and collecting-distributing). If the aggregator has the
maximum ports, the system adds the defaulted port to the standby list (port set to standby).
Use the
inventory of the number of ports currently in the aggregator. If there are fewer ports in the
aggregator than the maximum number allowed, the system adds the defaulted port to the
aggregator (port set to selected and collecting-distributing). If the aggregator has the
maximum ports, the system adds the defaulted port to the standby list (port set to standby).
Use the
show lacp lag <group-id> {detail}
command to display the defaulted action set for
the LAG.
Note:
If the defaulted port is assigned to standby, that port automatically
has a lower priority than any other port in the LAG (including those
already in standby).
already in standby).
Health Check Link Aggregation
The Health Check LAG application allows you to create a link aggregation group where
individual member links can monitor a particular TCP/IP address and TCP port. When
connectivity to the TCP/IP address and TCP port fails, the member link is removed from the
link aggregation group.
individual member links can monitor a particular TCP/IP address and TCP port. When
connectivity to the TCP/IP address and TCP port fails, the member link is removed from the
link aggregation group.
Establishing the status of a TCP connectivity is based on standard TCP socket connections.
As long as the switch can establish a TCP connection to the target switch and TCP port, the
connection is considered up. The TCP connection will retry based on the configured
frequency and miss settings.
As long as the switch can establish a TCP connection to the target switch and TCP port, the
connection is considered up. The TCP connection will retry based on the configured
frequency and miss settings.
A typical use case for this application is when a user wishes to connect each member link to
a Security Server to validate traffic. Each member link of the Health Check LAG is connected
to an individual Security Server. The LAG is added to a VLAN on the same subnet as the
Security Server IP addresses they wish to monitor. Each member port is configured to
monitor a particular IP address and TCP port. The Health Check LAG application attempts to
do a TCP connect to each IP/TCP port through each member port. The Health Check LAG,
by virtue of the sharing algorithm, will load balance traffic across the member links. If a TCP
connection cannot be established through the member link, the port is removed from the
a Security Server to validate traffic. Each member link of the Health Check LAG is connected
to an individual Security Server. The LAG is added to a VLAN on the same subnet as the
Security Server IP addresses they wish to monitor. Each member port is configured to
monitor a particular IP address and TCP port. The Health Check LAG application attempts to
do a TCP connect to each IP/TCP port through each member port. The Health Check LAG,
by virtue of the sharing algorithm, will load balance traffic across the member links. If a TCP
connection cannot be established through the member link, the port is removed from the