User's Manual
Table Of Contents
- 1. INTRODUCTION
- 2. INSTALLATION
- 3. SWITCH MANAGEMENT
- 4. WEB CONFIGURATION
- 4.1 System Information
- 4.2 Switch Management
- 4.2.1 Jumbo Frame
- 4.2.2 Interface
- 4.2.3 Statistics
- 4.2.4 VLAN
- 4.2.5 MAC Address
- 4.2.6 Port Mirror
- 4.2.7 Static Link Aggregation
- 4.2.8 LACP
- 4.2.9 Trunk Group Load Balance
- 4.2.10 Spanning Tree Protocol
- 4.2.11 IGMP Snooping
- 4.2.12 IGMP Filtering and Throttling
- 4.2.13 MLD Snooping
- 4.2.14 MVR For IPv4
- 4.2.14.1 Configure Global
- 4.2.14.2 Configure Domain
- 4.2.14.3 Show Configure Profile
- 4.2.14.4 Add Configure Profile
- 4.2.14.5 Show Associate Profile
- 4.2.14.6 Add Associate Profile
- 4.2.14.7 Configure Interface
- 4.2.14.8 Show Static Group Member
- 4.2.14.9 Add Static Group Member
- 4.2.14.10 Show Member
- 4.2.14.11 Show Query Statistics
- 4.2.14.12 Show VLAN Statistics
- 4.2.14.13 Show Port Statistics
- 4.2.14.14 Show Group Statistics
- 4.2.15 MVR For IPv6
- 4.2.15.1 Configure Global
- 4.2.15.2 Configure Domain
- 4.2.15.3 Show Configure Profile
- 4.2.15.4 Add Configure Profile
- 4.2.15.5 Show Associate Profile
- 4.2.15.6 Add Associate Profile
- 4.2.15.7 Configure Interface
- 4.2.15.8 Show Static Group Member
- 4.2.15.9 Add Static Group Member
- 4.2.15.10 Show Member
- 4.2.15.11 Show Query Statistics
- 4.2.15.12 Show VLAN Statistics
- 4.2.15.13 Show Port Statistics
- 4.2.15.14 Show Group Statistics
- 4.2.16 LLDP
- 4.2.17 ERPS
- 4.2.18 Loopback Detection
- 4.2.19 UDLD
- 4.2.20 Rate Limit
- 4.2.21 Storm Control
- 4.2.22 Stacking
- 4.2.23 Pepo
- 4.3 Route Management
- 4.4 ACL
- 4.5 CoS
- 4.6 Qu’s
- 4.7 Security
- 4.7.1 AAA
- 4.7.2 Web Authentication
- 4.7.3 802.1X
- 4.7.4 MAC Authentication
- 4.7.5 HTTPS
- 4.7.6 SSH
- 4.7.7 Port Security
- 4.7.8 DAI – Dynamic ARP Inspection
- 4.7.9 Login IP Management
- 4.7.10 DoS Protection
- 4.7.11 IPv4 DHCP Snooping
- 4.7.12 IPv6 DHCP Snooping
- 4.7.13 IPv4 Source Guard
- 4.7.14 IPv6 Source Guard
- 4.7.15 Application Filter
- 4.7.16 CPU Guard
- 4.8 Device Management
- 4.8.1 SNMP
- 4.8.2 RMON
- 4.8.3 Cluster
- 4.8.4 DNS
- 4.8.5 DHCP
- 4.8.6 OAM
- 4.8.7 CFM
- 4.8.7.1 Global Configuration
- 4.8.7.2 Interface Configuration
- 4.8.7.3 MD Management
- 4.8.7.4 MD Details
- 4.8.7.5 MA Management
- 4.8.7.6 MA Details
- 4.8.7.7 MEP Management
- 4.8.7.8 Remote MEP Management
- 4.8.7.9 Transmit Link Trace
- 4.8.7.10 Transmit Loopback
- 4.8.7.11 Transmit Delay Measure
- 4.8.7.12 Show Local MEP
- 4.8.7.13 Show Local MEP Details
- 4.8.7.14 Show Local MIP
- 4.8.7.15 Show Remote MEP
- 4.8.7.16 Show Remote MEP Details
- 4.8.7.17 Show Link Trace Cache
- 4.8.7.18 Show Fault Notification Generator
- 4.8.7.19 Show Continuity Check Error
- 4.8.8 Time Setting
- 4.8.9 Event Log
- 4.8.10 File Management
- 4.8.11 Ping
- 4.8.12 Trace Route
- 4.8.13 System Reboot
- 5. SWITCH OPERATION
- 6. TROUBLESHOOTING
- APPENDIX A: Networking Connection
- APPENDIX B : GLOSSARY
User’s Manual of SGS-5240 Series Managed Switch
174
4.2.19.2 Interface Configuration
Switch Management > UDLD > Interface Configuration page is used to enable UDLD and aggressive mode which reduces the
shut-down delay after loss of bidirectional connectivity is detected.
◆ Port – Port identifier. (Range: 1-28/52)
◆ UDLD – Enables UDLD on a port. (Default: Disabled)
UDLD requires that all the devices connected to the same LAN segment be running the protocol in order for a
potential mis-configuration to be detected and for prompt corrective action to be taken.
Whenever a UDLD device learns about a new neighbor or receives a resynchronization request from an
out-of-synch neighbor, it (re)starts the detection process on its side of the connection and sends N echo messages
in reply. (This mechanism implicitly assumes that N packets are sufficient to get through a link and reach the other
end, even though some of them might get dropped during the transmission.) Since this behavior must be the same
on all the neighbors, the sender of the echoes expects to receive an echo in reply. If the detection process ends
without the proper echo information being received, the link is considered to be unidirectional.
◆ Aggressive Mode – Reduces the shut-down delay after loss of bidirectional connectivity is detected. (Default: Disabled)
UDLD can function in two modes: normal mode and aggressive mode.
In normal mode, determination of link status at the end of the detection process is always based on information
received in UDLD messages: whether that’s information about the exchange of proper neighbor identification or the
absence of such. Hence, albeit bound by a timer, normal mode determinations are always based on gleaned
information, and as such are “event-based.” If no such information can be obtained (e.g., because of a bidirectional
loss of connectivity), UDLD follows a conservative approach to minimize false positives during the detection
process and deems a port to be in “undetermined” state. In other words, normal mode will shut down a port only if it
can explicitly determine that the associated link is faulty for an extended period of time.
In aggressive mode, UDLD will also shut down a port if it loses bidirectional connectivity with the neighbor for the
same extended period of time (as that mentioned above for normal mode) and subsequently fails repeated
last-resort attempts to re-establish communication with the other end of the link. This mode of operation assumes
that loss of communication with the neighbor is a meaningful network event in itself, and a symptom of a serious
connectivity problem. Because this type of detection can be event-less, and lack of information cannot always be
associated to an actual malfunction of the link, this mode is recommended only in certain scenarios (typically only
on point-to-point links where no communication failure between two neighbors is admissible).