NOTE: For multichassis link aggregation (MC-LAG) peers in active-active
mode, configuring the interface-mac-limit statement or changing the
interface-mac-limit configuration when traffic is flowing can cause the MAC
entries to be out of synchronization between the two MC-LAG peers, which
might result in flooding. To avoid flooding, you must either halt traffic
forwarding and then configure the interface-mac-limit statement or use the
commit at configuration statement to commit the changes at the same time
in both the peer nodes.
Alternatively, if flooding does occur, you can clear the bridge MAC table on
both the routers or switches by using the clear bridge mac-table command.
Running this command ensures that the MAC entries are re-learned and in
synchronization between both the peers.
Default The default MAC limit varies with the platform.
Options disable—Disables the global interface-mac-limit configuration on an interface and sets
the maximum interface-mac-limit that is permitted on the device.
limit—Sets the maximum number of MAC addresses learned from an interface.
Range: 1 through <default MAC limit> MAC addresses per interface. Range is platform
specific.
If you configure both disable and limit, disable takes precedence and packet-action is
set to none. The remaining statement is explained separately.
Required Privilege
Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Layer 2 Learning and Forwarding for Bridge Domains Overview
• Layer 2 Learning and Forwarding for VLANs Overview
• Layer 2 Learning and Forwarding for Bridge Domains Functioning as Switches with Layer
2 Trunk Ports
• Layer 2 Learning and Forwarding for VLANs Acting as a Switch for a Layer 2 Trunk Port
1571Copyright © 2017, Juniper Networks, Inc.
Chapter 41: Configuration Statements
To Next Page
Loading...
Need help?
General
