Will the device management be affected if an interface with loop detected is blocked

1

The blocked interface does not affect device management because the ping and Telnet functions are not affected. Blocking the interface only affect Layer 2 forwarding on the interface because the blocked interface does not learn MAC addresses.

Other related questions:
Can protocol packets be sent if an interface with a loop detected is blocked on an S series switches
Can protocol packets be sent if an interface with a loop detected is blocked on an S series (except the S1700) or E series switch? For S series switches (except the S1700), the destination MAC address of LDT packets and tagged LBDT packets is all Fs. These packets cannot be sent through an interface if it is blocked. The destination MAC address of untagged LBDT packets is a BPDU MAC address. These packets can still be sent through an interface even if it is blocked. For E series switches, the destination MAC address of tagged LBDT packets is all Fs. These packets cannot be sent through an interface if it is blocked. The destination MAC address of untagged LBDT packets is a BPDU MAC address. These packets can still be sent through an interface even if it is blocked.

Whether loop detection can be configured on the firewall interface
The USG2000&5000&6000 do not support configuring the loop detection command at the interface. Loop detection usually applies to detection at the lower-layer switches. On the firewall: 1. You can make a comparison by viewing interface traffic information. If the traffic volumes of certain interfaces are large and similar, a loop may occur. 2. If a loop occurs, the following alarm information is displayed. Alarm information: PPP/4/TRAP: [oid] Interface (IfIndex:[interface-index]) LoopBack is detected

Can a box switch record logs and alarms after a loop detection-enabled interface detects a loop
A fixed switch can record alarms but not logs after a loop detection-enabled interface detects a loop. The configurations are as follows: In V100R005 and V100R006, you can run the snmp-agent trap enable feature-name ldttrap command to enable the alarm function for loop detection. If snmp-agent trap enable has been configured globally, the alarm function has been enabled. Loop detection and loopback detection have been available since V200R001. You can run the snmp-agent trap enable feature-name ldttrap command to enable the alarm function for loop detection and run the snmp-agent trap enable feature-name lbdt command to enable the alarm function for loopback detection. You can run the display trapbuffer command to view alarms.

Loop prevention and breaking on S series switch
For S series switches except S1700 switches, use any of the following methods to remove loops: 1. Configure features such as STP, RSTP, MSTP, VBST,RRPP, and SEP to prevent loops. 2. Bundle dual physical links into a single logical link to prevent loops while implementing redundancy and increasing bandwidth. 3. Configure the switch to transparently transmit packets of different VLANs along different paths. 4. Enable loop detection and loopback detection to detect loops on the switch or downstream network connected to the switch, and configure the switch to take the preconfigured action to remove loops. Fixed switches only support loopback detection.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top