aggregation is not working and will try to send the traffic anyway. There is no negotiation
taking place between NetDefendOS and the switch to which the aggregated interfaces are
connected.
This means that on link failure, a connection can be dropped entirely.
•
LACP (Negotiated)
With negotiated aggregation, the switch to which the aggregated interfaces are connected is
configured to use
LACP
(Link Aggregation Control Protocol). This means that should a
physical link become inoperative, NetDefendOS will only try to send traffic over the
remaining operating links.
The advantage over the
Static
setting is that NetDefendOS will try to send a limited number
of packets over the failed connection before it switches to an alternate, working link. This
means that the connection will not be dropped and the connection's external endpoint will
experience only minor packet loss.
Individual Interface References Are Ignored
When an
EthernetInterface
object becomes part of a
LinkAggregation
object, it can no longer be
used as a separate object. If a configuration retains this individual interface usage after
aggregation then any references to it in the NetDefendOS configuration will be ignored during
operation although the underlying configuration is not changed.
For example, the following will be true:
•
Any IP rules that refer to an aggregated interface will be ignored in rule searches.
•
Any routes that refer to an aggregated interface will be ignored in route searches. The
ignored routes will still appear in output from the CLI command
show routes
but will not
appear in the CLI command
routes.
Removing Individual Routing References is Recommended
Whenever configuration changes are committed, NetDefendOS will issue warnings about any
aggregated interface references that will be ignored. For example, such a warning is shown
below for the interface
If1
because it is being used in a
Route
object.
If1 is not a valid routing interface because it's a Link Aggregation member
For configuration clarity, it is recommended that the administrator removes such redundant
interface usage from the NetDefendOS configuration.
Individual Interface Addresses Becomes 0.0.0.0
When an
EthernetInterface
object becomes part of a
LinkAggregation
object, its individual IPv4
address becomes
0.0.0.0
. This will be seen in the output from the CLI command
ifstat
.
However, the underlying NetDefendOS configuration is not changed. For example, the
associated address book objects are not changed so that if an interface is no longer part of of a
LinkAggregation
object, its IP address will revert back to its original address.
Distribution Methods
Chapter 3: Fundamentals
193
Summary of Contents for NetDefendOS
Page 30: ...Figure 1 3 Packet Flow Schematic Part III Chapter 1 NetDefendOS Overview 30 ...
Page 32: ...Chapter 1 NetDefendOS Overview 32 ...
Page 144: ...Chapter 2 Management and Maintenance 144 ...
Page 284: ...Chapter 3 Fundamentals 284 ...
Page 392: ...Chapter 4 Routing 392 ...
Page 419: ... Host 2001 DB8 1 MAC 00 90 12 13 14 15 5 Click OK Chapter 5 DHCP Services 419 ...
Page 420: ...Chapter 5 DHCP Services 420 ...
Page 573: ...Chapter 6 Security Mechanisms 573 ...
Page 607: ...Chapter 7 Address Translation 607 ...
Page 666: ...Chapter 8 User Authentication 666 ...
Page 775: ...Chapter 9 VPN 775 ...
Page 819: ...Chapter 10 Traffic Management 819 ...
Page 842: ...Chapter 11 High Availability 842 ...
Page 866: ...Default Enabled Chapter 13 Advanced Settings 866 ...
Page 879: ...Chapter 13 Advanced Settings 879 ...