17.1.4 Precautions when using L2 loop detection
- <Structure of this section>
(1) Operation in Protocol VLAN and MAC VLAN
An L2 loop detection frame is an untagged frame with its own format. Because the L2 loop detection frame is transferred as a native VLAN on a protocol port or a MAC port, a loop failure across switches might not be detected if the following conditions are met:
-
A port on the core network side is specified as an uplink port.
-
No native VLANs are specified on the core network side.
In such cases, if a port on the core network side specified as an uplink port is specified as the detecting and sending port, loop failures can be detected. The following are specific configuration examples.
(a) Example Configuration for Loop Detection Limits
In the configuration shown in the figure below, if the connection between hubs under the Switch is incorrect, a loop across switches occurs.
In the figure, Switch A sends an L2 loop detection frame from the detecting and blocking port on the hub side, but the frame is not sent from the uplink port on the core switch side. Because Switch B tries to transfer the L2 loop detection frame received on the MAC port as a native LAN, the L2 loop detection frame is not forwarded to the core switch side. In such cases, loop failures cannot be detected because the L2 loop detection frame is not returned to Switch A.
|
(b) Loop-Detectable Configuration Example
If a port on the core switch side of Switch A is specified as a detecting and sending port, Switch A can detect loop failures because Switch B forwards the L2 loop detection frame received from the port on the core switch side to the MAC port.
|
(2) Operations when Tag translation is used
Loop failure is detected in the following cases:
-
When a Tag converted L2 loop-detection frame sent from Tag converter port of the local device wraps in thenetwork and is received by the local device
-
When a Tag converted L2 loop-detection frame is received by another device
If you intend to configure the network to return to the local device, set the target port to a port that is not to be detected to avoid a loop failure.
(3) System Requirements for L2 Loop-Detect Function
When the L2 loop detection functionality is used, if AX6700S and AX6300S series switches (before version 10.7), which do not support the functionality, are installed on the same network and either receives a loop detection frame, it discards the frame. Therefore, if a loop failure occurs on the path containing these switches, the failure is not detected.
(4) Functions for automatically turning active the ports in inactive status (automatic recovery function)
Note the following if you use the automatic-restoration functionality in static link aggregation:
-
To change the line speed (which changes the network configuration), specify mixed-speed mode for the applicable channel group. If a loop is detected while changing the line speed when the mixed-speed mode is not specified, the automatic-restoration functionality might not operate properly in the applicable channel group.
-
If you use the auto-negotiation functionality for connection, specify a line speed. If you do not specify a line speed, the line speed might temporarily vary due to degradation of the line quality, in which case the low-speed line might be withdrawn from the applicable channel group. If a loop is detected in this state, the automatic-restoration functionality might not operate in the applicable channel group.
If the automatic-restoration functionality does not operate, correct the cause of the loop, and then use the activate operation command to activate the port.
(5) Understanding Automatic Recovery Features in a Stacked Configuration
In a stack configuration where the automatic recovery functionality is set and which automatically changes the port status from inactive to active, if a loop failure is detected and thus the master switch is changed when the port is inactive, the port for a new master switch remains inactive. In this case, use the activate operation command to activate the port.
(6) About Using Stacked with Ring Protocol or Spanning Tree
When Ring Protocol or Spanning Tree Protocols are enabled in a stacked configuration, ports that are in Blocking should not be subject to L2 loop-detection.