Loopback Detection - Cisco SF220-24 Administration Manual

220 series
Hide thumbs Also See for SF220-24:
Table of Contents

Advertisement

Port Management

Loopback Detection

STEP 3
STEP 4
Loopback Detection
Cisco 220 Series Smart Switches Administration Guide Release 1.1.0.x
DHCP Rate Limit
-
DHCP rate limit causes.
Loopback Detection
-
the Loopback Detection causes.
PoE
-
—(Only applicable for PoE models) Check Enable to enable the timer
to recover from the Power over Ethernet (PoE) causes.
Port Security
-
security causes.
Self Loop
-
—Check Enable to enable the timer to recover from the
selfloop cause.
Unicast Flood
-
Unicast flood causes.
Unknown Multicast Flood
-
from the unknown Multicast flood causes.
Click Apply. The error recovery settings are modified, and the Running
Configuration is updated.
The Suspended (errDisabled) Interface Table displays a list of suspended ports.
To manually reactivate a suspended port, select the desired port, and click
Reactivate.
Loopback Detection (LBD) provides protection against loops by transmitting loop
protocol packets out of ports on which loop protection has been enabled. When
the switch sends out a loop protocol packet, and then receives the same packet, it
shuts down the port that received the packet.
Loopback Detection operates independently of STP. After a loop is discovered,
the port that received the loops is placed in the Shut Down state. A trap is sent
and the event is logged. Network managers can define a Detection Interval that
sets the time interval between LBD packets.
The following loop cases can be detected by the Loopback Detection protocol:
Shorted wire—Port that loop backs all receiving traffic.
—Check Enable to enable the timer to recover from the
—Check Enable to enable the timer to recover from
—Check Enable to enable the timer to recover from the port
—Check Enable to enable the timer to recover from the
—Check Enable to enable the timer to recover
9
111

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents