Unidirectional links occur when one end of a link can receive packets from the other end, but the other end cannot receive packets sent by the first end. Unidirectional links result in problems such as loops in an STP-enabled network.

For example, the link between two switches, Switch A and Switch B, is a bidirectional link when they are connected via a fiber pair, with one fiber used for sending packets from A to B and the other for sending packets from B to A. This link is a two-way link. If one of the fibers gets broken, the link becomes a unidirectional link (one-way link).

There are two types of unidirectional fiber links. One occurs when fibers are cross-connected. The other occurs when a fiber is not connected at one end, or when one fiber of a fiber pair gets broken. Figure 1 shows a correct fiber connection and the two types of unidirectional fiber connection.

Figure 1 Correct and incorrect fiber connections

The Device link detection protocol (DLDP) detects unidirectional links (fiber links or twisted-pair links) and can be configured to shut down the related port automatically or prompt users to take actions to avoid network problems.

As a data link layer protocol, DLDP cooperates with physical layer protocols to monitor link status. When the auto-negotiation mechanism provided by the physical layer detects physical signals and faults, DLDP performs operations such as identifying peer devices, detecting unidirectional links, and shutting down unreachable ports. The auto-negotiation mechanism and DLDP work together to ensure that physical/logical unidirectional links can be detected and shut down, and to prevent failure of other protocols such as STP. If both ends of a link are operating normally at the physical layer, DLDP detects whether the link is correctly connected at the link layer and whether the two ends can exchange packets properly. This is beyond the capability of the auto-negotiation mechanism at the physical layer.

How DLDP works

DLDP link states

A device is in one of these DLDP link states: Initial, Inactive, Active, Advertisement, Probe, Disable, and DelayDown, as described in Table 1.

Table 1 DLDP link states

State	Indicates…
Initial	DLDP is disabled.
Inactive	DLDP is enabled, and the link is down.
Active	DLDP is enabled and the link is up, or the neighbor entries have been cleared.
Advertisement	All neighbors are bi-directionally reachable or DLDP has been in active state for more than five seconds. This is a relatively stable state where no unidirectional link has been detected.
Probe	DLDP enters this state if it receives a packet from an unknown neighbor. In this state, DLDP sends packets to check whether the link is unidirectional. As soon as DLDP transits to this state, a probe timer starts and an echo timeout timer starts for each neighbor to be probed.
Disable	A port enters this state when: · A unidirectional link is detected. · The contact with the neighbor in enhanced mode gets lost. · In this state, the port does not receive or send packets other than DLDPDUs.
DelayDown	A port in the Active, Advertisement, or Probe DLDP link state transits to this state rather than removes the corresponding neighbor entry and transits to the Inactive state when it detects a port-down event. When a port transits to this state, the DelayDown timer is triggered.

DLDP timers

Table 2 DLDP timers

DLDP timer	Description
Active timer	Determines the interval for sending Advertisement packets with RSY tags, which defaults to 1 second. By default, a device in the active DLDP link state sends two Advertisement packet with RSY tags every second. The maximum number of advertisement packets with RSY tags that can be sent successively is 5.
Advertisement timer	Determines the interval for sending common advertisement packets, which defaults to 5 seconds.
Probe timer	Determines the interval for sending Probe packets, which defaults to 1 second. By default, a device in the probe state sends one Probe packet every second. The maximum number of Probe packets that can be sent successively is 10.
Echo timer	This timer is set to 10 seconds. It is triggered when a device transits to the Probe state or when an enhanced detect is launched. When the Echo timer expires and no Echo packet has been received from a neighbor device, the state of the link is set to unidirectional and the device transits to the Disable state. In this case, the device does the following: Sends Disable packets. Either prompts the user to shut down the port or shuts down the port automatically (depending on the DLDP down mode configured). Removes the corresponding neighbor entries.
Entry timer	When a new neighbor joins, a neighbor entry is created and the corresponding entry timer is triggered. When a DLDP packet is received, the device updates the corresponding neighbor entry and the entry timer. In normal mode, if no packet is received from a neighbor when the corresponding entry timer expires, DLDP sends advertisement packets with RSY tags and removes the neighbor entry. In enhanced mode, if no packet is received from a neighbor when the Entry timer expires, DLDP triggers the enhanced timer. The setting of an Entry timer is three times that of the Advertisement timer.
Enhanced timer	In enhanced mode, this timer is triggered if no packet is received from a neighbor when the entry timer expires. Enhanced timer is set to 1 second. After the Enhanced timer is triggered, the device sends up to eight probe packets to the neighbor at a frequency of one packet per second.
DelayDown timer	A device in Active, Advertisement, or Probe DLDP link state transits to DelayDown state rather than removes the corresponding neighbor entry and transits to the Inactive state when it detects a port-down event. When a device transits to this state, the DelayDown timer is triggered. A device in DelayDown state only responds to port-up events. If a device in the DelayDown state detects a port-up event before the DelayDown timer expires, it resumes its original DLDP state. If not, when the DelayDown timer expires, the device removes the corresponding DLDP neighbor information and transits to the Inactive state.
RecoverProbe timer	This timer is set to 2 seconds. A port in the Disable state sends one RecoverProbe packet every two seconds to detect whether a unidirectional link has restored.

DLDP mode

DLDP can operate in normal or enhanced mode.

· In normal DLDP mode, when an entry timer expires, the device removes the corresponding neighbor entry and sends an Advertisement packet with the RSY tag.

· In enhanced DLDP mode, when an entry timer expires, the Enhanced timer is triggered and the device tests the neighbor by sending up to eight Probe packets at the frequency of one packet per second. If no Echo packet has been received from the neighbor when the Echo timer expires, the device transits to the Disable state.

Table 3 shows the relationship between the DLDP modes and neighbor entry aging.

Table 3 DLDP mode and neighbor entry aging

DLDP mode	Detecting a neighbor after the corresponding neighbor entry ages out	Removing the neighbor entry immediately after the Entry timer expires	Triggering the Enhanced timer after an Entry timer expires
Normal DLDP mode	No	Yes	No
Enhanced DLDP mode	Yes	No	Yes

Enhanced DLDP mode is designed for addressing black holes. It prevents situations where one end of a link is up and the other is down.

If you configure forced speed and full duplex mode on a port, the situation shown in Figure 2 may occur (take the fiber link for example). Without DLDP enabled, the port on Device B is actually down but its state cannot be detected by common data link protocols, so the port on Device A is still up. However, in enhanced DLDP mode, the following occurs:

The port on Device B is in Inactive DLDP state because it is physically down.

The port on Device A tests the peer port on Device B after the Entry timer for the port on Device B expires.

The port on Device A transits to the Disable state if it does not receive an Echo packet from the port on Device B when the Echo timer expires.

Figure 2 A scenario for the enhanced DLDP mode

NOTE:

· When DLDP works in normal mode, the device can identify only the unidirectional link of cross-connected fibers.

· When DLDP works in enhanced mode, the device can identify the unidirectional link of cross-connected fibers and of that one fiber of a fiber pair is not connected or broken. In the latter link, ports that have signals are in the Disable state and that do not have signals are in the Inactive state on the RX line.

DLDP authentication mode

You can use DLDP authentication to prevent network attacks and illegal detecting. There are three DLDP authentication modes.

· Non-authentication:

The sending side sets the Authentication field and the Authentication type field of DLDP packets to 0.

The receiving side checks the values of the two fields of received DLDP packets and drops the packets where the two fields conflict with the corresponding local configuration.

· Plain text authentication:

Before sending a DLDP packet, the sending side sets the Authentication field to the password configured in plain text and sets the Authentication type field to 1.

The receiving side checks the values of the two fields in received DLDP packets and drops any packets where the two fields conflict with the corresponding local configuration.

· MD5 authentication:

Before sending a packet, the sending side encrypts the user configured password using MD5 algorithm, assigns the digest to the Authentication field, and sets the Authentication type field to 2.

The receiving side checks the values of the two fields in received DLDP packets and drops any packets where the two fields conflicting with the corresponding local configuration.

DLDP processes

1. On a DLDP-enabled link that is in up state, DLDP sends DLDP packets to the peer device and processes the DLDP packets received from the peer device. DLDP packets sent vary with DLDP states. Table 4 lists DLDP states and their packet types.

Table 4 DLDP packet types and DLDP states

DLDP state	Type of DLDP packets sent
Active	Advertisement packet with RSY tag
Advertisement	Normal Advertisement packet
Probe	Probe packet
Disable	Disable packet and then RecoverProbe packet

NOTE:

A device sends Flush packets when it transits to Initial state from Active, Advertisement, Probe, or DelayDown state but does not send them when it transits to the Initial state from Inactive or Disable state.

2. A received DLDP packet is processed with the following methods.

· In any of the three authentication modes, the packet is dropped if it fails to pass the authentication.

· The packet is dropped if the setting of the interval to send Advertisement packets it carries conflicts with the corresponding local setting.

· Other processes are as shown in Table 5.

Table 5 Procedures for processing different types of DLDP packets received

Packet type	Processing procedure
Advertisement packet with RSY tag	Retrieves the neighbor information	If the corresponding neighbor entry does not exist, creates the neighbor entry, triggers the Entry timer, and transits to Probe state.
Advertisement packet with RSY tag	Retrieves the neighbor information	If the corresponding neighbor entry already exists, resets the Entry timer and transits to Probe state.
Normal Advertisement packet	Retrieves the neighbor information	If the corresponding neighbor entry does not exist, creates the neighbor entry, triggers the Entry timer, and transits to Probe state.
Normal Advertisement packet	Retrieves the neighbor information	If the corresponding neighbor entry already exists, resets the Entry timer.
Flush packet	Determines whether or not the local port is in Disable state	If yes, performs no processing.
Flush packet		If not, removes the corresponding neighbor entry (if any).
Probe packet	Retrieves the neighbor information	If the corresponding neighbor entry does not exist, creates the neighbor entry, transits to Probe state, and returns Echo packets.
Probe packet	Retrieves the neighbor information	If the corresponding neighbor entry already exists, resets the Entry timer and returns Echo packets.
Echo packet	Retrieves the neighbor information	If the corresponding neighbor entry does not exist, creates the neighbor entry, triggers the Entry timer, and transits to Probe state.
		The corresponding neighbor entry already exists	If the neighbor information it carries conflicts with the corresponding locally maintained neighbor entry, drops the packet.
		The corresponding neighbor entry already exists	Otherwise, sets the flag of the neighbor as two-way connected. In addition, if the flags of all the neighbors are two-way connected, the device transits from Probe state to Advertisement state and disables the Echo timer.
Disable packet	Checks whether the local port is in Disable state	If yes, performs no processing.
Disable packet	Checks whether the local port is in Disable state	If not, sets the state of the corresponding neighbor to unidirectional, and then checks the state of other neighbors. If all the neighbors are unidirectional, transitions the local port to the Disable state. If the state of some neighbors is unknown, waits until the state of these neighbors is determined. If bidirectional neighbors are present, removes all unidirectional neighbors.
RecoverProbe packet	Checks whether the local port is in Disable or Advertisement state	If not, performs no processing.
RecoverProbe packet		If yes, returns RecoverEcho packets.
RecoverEcho packet	Checks whether the local port is in Disable state	If not, performs no processing.
RecoverEcho packet	Checks whether the local port is in Disable state	If yes, the local port transits to Active state if the neighbor information the packet carries is consistent with the local port information.
LinkDown packet	Checks whether the local port operates in Enhanced mode	If not, performs no processing.
LinkDown packet	Checks whether the local port operates in Enhanced mode	If yes and the local port is not in Disable state, sets the state of the corresponding neighbor to unidirectional, and then checks the state of other neighbors. If all the neighbors are unidirectional, transitions the local port to the Disable state. If the state of some neighbors is unknown, waits until the state of these neighbors is determined. If bidirectional neighbors are present, removes all unidirectional neighbors.

3. If no echo packet is received from the neighbor, DLDP performs the following processing.

Table 6 DLDP process when no echo packet is received from the neighbor

No echo packet received from the neighbor	Processing procedure
In normal mode, no echo packet is received when the Echo timer expires.	DLDP sets the state of the corresponding neighbor to unidirectional, and then checks the state of other neighbors: · If all the neighbors are unidirectional, removes all the neighbors, transitions to the Disable state, outputs log and tracking information, and sends Disable packets. In addition, depending on the user-defined DLDP down mode, shuts down the local port or prompts users to shut down the port. · If the state of some neighbors is unknown, waits until the state of these neighbors is determined. · If bidirectional neighbors are present, removes all unidirectional neighbors.
In enhanced mode, no echo packet is received when the Echo timer expires.

No echo packet received from the neighbor

Processing procedure

In normal mode, no echo packet is received when the Echo timer expires.

DLDP sets the state of the corresponding neighbor to unidirectional, and then checks the state of other neighbors:

· If all the neighbors are unidirectional, removes all the neighbors, transitions to the Disable state, outputs log and tracking information, and sends Disable packets. In addition, depending on the user-defined DLDP down mode, shuts down the local port or prompts users to shut down the port.

· If the state of some neighbors is unknown, waits until the state of these neighbors is determined.

· If bidirectional neighbors are present, removes all unidirectional neighbors.

In enhanced mode, no echo packet is received when the Echo timer expires.

Link auto-recovery mechanism

If the port shutdown mode upon detection of a unidirectional link is set to auto, DLDP automatically sets the state of the port where a unidirectional link is detected to DLDP down. A DLDP down port cannot forward data traffic or send/receive any PDUs except DLDPDUs.

On a DLDP down port, DLDP monitors the unidirectional link. Once DLDP finds out that the state of the link has restored to bidirectional, it brings up the port. The specific process is:

The DLDP down port sends out a RecoverProbe packet, which carries only information about the local port, every two seconds. Upon receiving the RecoverProbe packet, the remote end returns a RecoverEcho packet. Upon receiving the RecoverEcho packet, the local port checks whether neighbor information in the RecoverEcho packet is the same as the local port information. If they are the same, the link between the local port and the neighbor is considered to have been restored to a bidirectional link, and the port will transit from Disable state to Active state and re-establish relationship with the neighbor.

Only DLDP down ports can send and process Recover packets, including RecoverProbe packets and RecoverEcho packets. If related ports are manually shut down with the shutdown command, the auto-recovery mechanism will not take effect.

DLDP neighbor state

A DLDP neighbor can be in one of the three states described in Table 7.

Table 7 Description on DLDP neighbor states

DLDP neighbor state	Description
Unknown	A neighbor is in this state when it is just detected and is being probed. A neighbor is in this state only when it is being probed. It transits to Two way state or Unidirectional state after the probe operation finishes.
Two way	A neighbor is in this state after it receives response from its peer. This state indicates the link is a two-way link.
Unidirectional	A neighbor is in this state when the link connecting it is detected to be a unidirectional link. After a device transits to this state, the corresponding neighbor entries maintained on other devices are removed.

DLDP configuration task list

Complete the following tasks to configure DLDP:

Task	Remarks
Enabling DLDP	Required
Setting DLDP mode	Optional
Setting the interval to send advertisement packets	Optional
Setting the DelayDown timer	Optional
Setting the port shutdown mode	Optional
Configuring DLDP authentication	Optional
Resetting DLDP state	Optional

CAUTION:

· For DLDP to work properly, configure the full duplex mode and the same forced speed on ports of both sides.

· For DLDP to work properly, enable DLDP on both sides and make sure these settings are consistent: the interval to send Advertisement packets, DLDP authentication mode, and password.

· DLDP does not process any link aggregation control protocol (LACP) events. The links in an aggregation are treated as individual links in DLDP.

· Make sure the DLDP version running on devices on the two ends are the same.

Enabling DLDP

To properly configure DLDP on the device, first enable DLDP globally, and then enable it on each port.

Follow these steps to enable DLDP:

To do…		Use the command…	Remarks
Enter system view		system-view	—
Enable DLDP globally		dldp enable	Required Globally disabled by default
Enter Ethernet interface view or port group view	Enter Ethernet interface view	interface interface-type interface-number	Either of the two is required. Configurations made in Ethernet interface view apply to the current port only. Configurations made in port group view apply to all ports in the port group.
Enter Ethernet interface view or port group view	Enter port group view	port-group manual port-group-name
Enable DLDP		dldp enable	Required Disabled on a port by default

NOTE:

· DLDP takes effect only on Ethernet interfaces (optical or copper).

· DLDP can detect unidirectional links only after all physical links are connected. Therefore, before enabling DLDP, make sure that optical fibers or copper twisted pairs are connected.

Setting DLDP mode

DLDP works in normal or enhanced mode.

In normal mode, DLDP does not actively detect neighbors when the corresponding neighbor entries age out.

In enhanced mode, DLDP actively detects neighbors when the corresponding neighbor entries age out.

Follow these steps to set DLDP mode:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Set DLDP mode	dldp work-mode { enhance \| normal }	Optional Normal by default

To do…

Use the command…

Remarks

Enter system view

system-view

—

Set DLDP mode

dldp work-mode { enhance | normal }

Optional

Normal by default

Setting the interval to send advertisement packets

DLDP detects unidirectional links by sending Advertisement packets. To ensure that DLDP can detect unidirectional links in time without affecting network performance, set the advertisement interval appropriately depending on your network environment. The interval should be set shorter than one third of the STP convergence time. If the interval is too long, STP loops may occur before unidirectional links are detected and shut down. If the interval is too short, the number of advertisement packets will increase. H3C recommends you use the default interval in most cases.

Follow these steps to set the interval to send Advertisement packets:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Set the interval to send Advertisement packets	dldp interval time	Optional 5 seconds by default

To do…

Use the command…

Remarks

Enter system view

system-view

—

Set the interval to send Advertisement packets

dldp interval time

Optional

5 seconds by default

NOTE:

· The interval sending Advertisement packets applies to all DLDP-enabled ports.

· To enable DLDP to operate properly, make sure the intervals to send Advertisement packets on both sides of a link are the same.

Setting the DelayDown timer

On some ports, when the Tx line fails, the port goes down and then comes up again, causing optical signal jitters on the Rx line. When a port goes down due to a Tx failure, the device transits to the DelayDown state instead of the Inactive state to prevent the corresponding neighbor entries from being removed. At the same time, the device triggers the DelayDown timer. If the port goes up before the timer expires, the device restores the original state; if the port remains down when the timer expires, the device transits to the Inactive state.

Follow these steps to set the DelayDown timer

To do…	Use the command…	Remarks
Enter system view	system-view	—
Set the DelayDown timer	dldp delaydown-timer time	Optional 1 second by default

To do…

Use the command…

Remarks

Enter system view

system-view

—

Set the DelayDown timer

dldp delaydown-timer time

Optional

1 second by default

NOTE:

DelayDown timer setting applies to all DLDP-enabled ports.

Setting the port shutdown mode

On detecting a unidirectional link, the ports can be shut down in one of the following two modes.

· Manual mode. This mode applies to low performance networks, where normal links may be treated as unidirectional links. It protects data traffic transmission against false unidirectional links. In this mode, DLDP only detects unidirectional links but does not automatically shut down unidirectional link ports. Instead, the DLDP state machine generates log and traps to prompt you to manually shut down unidirectional link ports with the shutdown command. H3C recommends you do as prompted. Then the DLDP state machine transits to the Disable state.

· Auto mode. In this mode, when a unidirectional link is detected, DLDP transits to Disable state, generates log and traps, and sets the port state to DLDP Down.

Follow these steps to set port shutdown mode:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Set port shutdown mode	dldp unidirectional-shutdown { auto \| manual }	Optional auto by default

To do…

Use the command…

Remarks

Enter system view

system-view

—

Set port shutdown mode

dldp unidirectional-shutdown { auto | manual }

Optional

auto by default

NOTE:

· On a port with both remote OAM loopback and DLDP enabled, if the port shutdown mode is auto mode, the port will be shut down by DLDP when it receives a packet sent by itself, causing remote OAM loopback to operate improperly. To prevent this, set the port shutdown mode to manual mode.

· If the device is busy, or the CPU usage is high, normal links may be treated as unidirectional links. In this case, you can set the port shutdown mode to manual mode to alleviate the impact caused by false unidirectional link report.

Configuring DLDP authentication

You can guard your network against attacks and malicious probes by configuring an appropriate DLDP authentication mode, which can be clear text authentication or MD5 authentication. If your network is safe, you can choose not to authenticate.

Follow these steps to configure DLDP authentication:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Configure DLDP authentication	dldp authentication-mode { md5 md5-password \| none \| simple simple-password }	Required none by default

To do…

Use the command…

Remarks

Enter system view

system-view

—

Configure DLDP authentication

dldp authentication-mode { md5 md5-password | none | simple simple-password }

Required

none by default

NOTE:

To enable DLDP to operate properly, make sure that DLDP authentication modes and passwords on both sides of a link are the same.

Resetting DLDP state

After DLDP detects a unidirectional link on a port, the port enters Disable state. In this case, DLDP prompts you to shut down the port manually or shuts down the port automatically depending on the user-defined port shutdown mode. To enable the port to perform DLDP detect again, you can reset the DLDP state of the port by using one of the following methods:

· If the port is shut down with the shutdown command manually, run the undo shutdown command on the port.

· If DLDP automatically shuts down the port, run the dldp reset command on the port to enable the port to perform DLDP detection again. Alternatively, you can wait for DLDP to automatically enable the port when it detects that the link has been restored to bidirectional. For how to reset the DLDP state by using the dldp reset command, see “Resetting DLDP state in system view” and “Resetting DLDP state in port view/port group view.”

The DLDP state that the port transits to upon the DLDP state reset operation depends on its physical state. If the port is physically down, it transits to Inactive state; if the port is physically up, it transits to Active state.

Resetting DLDP state in system view

Resetting DLDP state in system view applies to all ports of the device.

Follow these steps to reset DLDP in system view:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Reset DLDP state	dldp reset	Required

Resetting DLDP state in port view/port group view

Resetting DLDP state in port view or port group view applies to the current port or all ports in the port group.

Follow these steps to reset DLDP state in port view/port group view:

To do…		Use the command…	Remarks
Enter system view		system-view	—
Enter Ethernet interface view/port group view	Enter Ethernet interface view	interface interface-type interface-number	Either is required. Configurations made in Ethernet interface view apply to the current port only. Configurations made in port group view apply to all the ports in the port group.
Enter Ethernet interface view/port group view	Enter port group view	port-group manual port-group-name
Reset DLDP state		dldp reset	Required

Displaying and maintaining DLDP

To do…	Use the command…	Remarks
Display the DLDP configuration of a port	display dldp [ interface-type interface-number ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display the statistics on DLDP packets passing through a port	display dldp statistics [ interface-type interface-number ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Clear the statistics on DLDP packets passing through a port	reset dldp statistics [ interface-type interface-number ]	Available in user view

DLDP configuration examples

Automatically shutting down unidirectional links

Network requirements

· As shown in Figure 3, Device A and Device B are connected with two fiber pairs.

· Configure DLDP to automatically shut down the faulty port upon detecting a unidirectional link, and automatically bring up the port after you clear the fault.

Figure 3 Network diagram for configuring automatic shutdown of unidirectional links

Configuration procedure

1. Configuration on Device A

# Enable DLDP globally.

<DeviceA> system-view

[DeviceA] dldp enable

# Configure GigabitEthernet 1/0/10 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.

[DeviceA] interface gigabitethernet 1/0/10

[DeviceA-GigabitEthernet1/0/10] duplex full

[DeviceA-GigabitEthernet1/0/10] speed 1000

[DeviceA-GigabitEthernet1/0/10] dldp enable

[DeviceA-GigabitEthernet1/0/10] quit

# Configure GigabitEthernet 1/0/11 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.

[DeviceA] interface gigabitethernet 1/0/11

[DeviceA-GigabitEthernet1/0/11] duplex full

[DeviceA-GigabitEthernet1/0/11] speed 1000

[DeviceA-GigabitEthernet1/0/11] dldp enable

[DeviceA-GigabitEthernet1/0/11] quit

# Set the DLDP mode to enhanced.

[DeviceA] dldp work-mode enhance

# Set the port shutdown mode to auto.

[DeviceA] dldp unidirectional-shutdown auto

2. Configuration on Device B

# Enable DLDP globally.

<DeviceB> system-view

[DeviceB] dldp enable

# Configure GigabitEthernet 1/0/10 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.

[DeviceB] interface gigabitethernet 1/0/10

[DeviceB-GigabitEthernet1/0/10] duplex full

[DeviceB-GigabitEthernet1/0/10] speed 1000

[DeviceB-GigabitEthernet1/0/10] dldp enable

[DeviceB-GigabitEthernet1/0/10] quit

# Configure GigabitEthernet 1/0/11 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.

[DeviceB] interface gigabitethernet 1/0/11

[DeviceB-GigabitEthernet1/0/11] duplex full

[DeviceB-GigabitEthernet1/0/11] speed 1000

[DeviceB-GigabitEthernet1/0/11] dldp enable

[DeviceB-GigabitEthernet1/0/11] quit

# Set the DLDP mode to enhanced.

[DeviceB] dldp work-mode enhance

# Set the port shutdown mode to auto.

[DeviceB] dldp unidirectional-shutdown auto

3. Verifying the configurations

After the configurations are complete, you can use the display dldp command to display the DLDP configuration information on ports.

# Display the DLDP configuration information on all the DLDP-enabled ports of Device A.

[DeviceA] display dldp

DLDP global status : enable

DLDP interval : 5s

DLDP work-mode : enhance

DLDP authentication-mode : none

DLDP unidirectional-shutdown : auto

DLDP delaydown-timer : 1s

The number of enabled ports is 2.

Interface GigabitEthernet1/0/10

DLDP port state : advertisement

DLDP link state : up

The neighbor number of the port is 1.

Neighbor mac address : 0023-8956-3600

Neighbor port index : 59

Neighbor state : two way

Neighbor aged time : 11

Interface GigabitEthernet1/0/11

DLDP port state : advertisement

DLDP link state : up

The neighbor number of the port is 1.

Neighbor mac address : 0023-8956-3600

Neighbor port index : 60

Neighbor state : two way

Neighbor aged time : 12

The output indicates that both GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11 are in Advertisement state, which means both links are bidirectional.

# Enable system information monitoring on Device A, and enable the display of log and trap information.

[DeviceA] quit

<DeviceA> terminal monitor

<DeviceA> terminal logging

<DeviceA> terminal trapping

The following log and trap information is displayed on Device A:

#Jan 18 17:36:18:798 2010 DeviceA DLDP/1/TrapOfUnidirectional: -Slot=2; h3cDLDPUnidirectionalPort : DLDP detects a unidirectional link in port 17825792.

%Jan 18 17:36:18:799 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/10 link status is DOWN.

%Jan 18 17:36:18:799 2010 DeviceA DLDP/3/DLDP_UNIDIRECTION_AUTO: -Slot=2; DLDP detects a unidirectional link on port GigabitEthernet1/0/10. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is AUTO. DLDP shuts down the port.

#Jan 18 17:36:20:189 2010 DeviceA DLDP/1/TrapOfUnidirectional: -Slot=2; h3cDLDPUnidirectionalPort : DLDP detects a unidirectional link in port 17825793.

%Jan 18 17:36:20:189 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/11 link status is DOWN.

%Jan 18 17:36:20:190 2010 DeviceA DLDP/3/DLDP_UNIDIRECTION_AUTO: -Slot=2; DLDP detects a unidirectional link on port GigabitEthernet1/0/11. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is AUTO. DLDP shuts down the port.

%Jan 15 16:54:56:040 2010 DeviceA DLDP/3/DLDP_UNIDIRECTION_AUTO_ENHANCE: -Slot=2; In enhanced DLDP mode, port GigabitEthernet1/0/10 cannot detect its aged-out neighbor. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is AUTO. DLDP shuts down the port.

The output indicates that the link status of both GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11 is down, and DLDP has detected a unidirectional link on both ports and has automatically shut them down.

Assume that in this example, the unidirectional links are caused by cross-connected fibers. Correct the fiber connections on detecting the unidirectional link problem. As a result, the ports shut down by DLDP automatically recover, and Device A displays the following log information:

%Jan 18 17:47:33:869 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/10 link status is UP.

%Jan 18 17:47:35:894 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/11 link status is UP.

The output indicates that the link status of both GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11 is now up.

Manually shutting down unidirectional links

Network requirements

· As shown in Figure 4, Device A and Device B are connected with two fiber pairs.

· Configure DLDP to send information when a unidirectional link is detected, to remind the network administrator to manually shut down the faulty port.

Figure 4 Network diagram for configuring manual shutdown of unidirectional links

Configuration procedure

1. Configuration on Device A

# Enable DLDP globally.

<DeviceA> system-view

[DeviceA] dldp enable

# Configure GigabitEthernet 1/0/10 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.

[DeviceA] interface gigabitethernet 1/0/10

[DeviceA-GigabitEthernet1/0/10] duplex full

[DeviceA-GigabitEthernet1/0/10] speed 1000

[DeviceA-GigabitEthernet1/0/10] dldp enable

[DeviceA-GigabitEthernet1/0/10] quit

# Configure GigabitEthernet 1/0/11 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.

[DeviceA] interface gigabitethernet 1/0/11

[DeviceA-GigabitEthernet1/0/11] duplex full

[DeviceA-GigabitEthernet1/0/11] speed 1000

[DeviceA-GigabitEthernet1/0/11] dldp enable

[DeviceA-GigabitEthernet1/0/11] quit

# Set the DLDP mode to enhanced.

[DeviceA] dldp work-mode enhance

# Set the port shutdown mode to manual.

[DeviceA] dldp unidirectional-shutdown manual

2. Configuration on Device B

# Enable DLDP globally.

<DeviceB> system-view

[DeviceB] dldp enable

# Configure GigabitEthernet 1/0/10 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.

[DeviceB] interface gigabitethernet 1/0/10

[DeviceB-GigabitEthernet1/0/10] duplex full

[DeviceB-GigabitEthernet1/0/10] speed 1000

[DeviceB-GigabitEthernet1/0/10] dldp enable

[DeviceB-GigabitEthernet1/0/10] quit

# Configure GigabitEthernet 1/0/11 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.

[DeviceB] interface gigabitethernet 1/0/11

[DeviceB-GigabitEthernet1/0/11] duplex full

[DeviceB-GigabitEthernet1/0/11] speed 1000

[DeviceB-GigabitEthernet1/0/11] dldp enable

[DeviceB-GigabitEthernet1/0/11] quit

# Set the DLDP mode to enhanced.

[DeviceB] dldp work-mode enhance

# Set the port shutdown mode to manual.

[DeviceB] dldp unidirectional-shutdown manual

3. Verifying the configurations

After the configurations are complete, you can use the display dldp command to display the DLDP configuration information on ports.

# Display the DLDP configuration information on all the DLDP-enabled ports of Device A.

[DeviceA] display dldp

DLDP global status : enable

DLDP interval : 5s

DLDP work-mode : enhance

DLDP authentication-mode : none

DLDP unidirectional-shutdown : manual

DLDP delaydown-timer : 1s

The number of enabled ports is 2.

Interface GigabitEthernet1/0/10

DLDP port state : advertisement

DLDP link state : up

The neighbor number of the port is 1.

Neighbor mac address : 0023-8956-3600

Neighbor port index : 59

Neighbor state : two way

Neighbor aged time : 11

Interface GigabitEthernet1/0/11

DLDP port state : advertisement

DLDP link state : up

The neighbor number of the port is 1.

Neighbor mac address : 0023-8956-3600

Neighbor port index : 60

Neighbor state : two way

Neighbor aged time : 12

The output indicates that both GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11 are in Advertisement state, which means both links are bidirectional.

# Enable system information monitoring on Device A, and enable the display of log and trap information.

[DeviceA] quit

<DeviceA> terminal monitor

<DeviceA> terminal logging

<DeviceA> terminal trapping

The following log and trap information is displayed on Device A:

#Jan 18 18:10:38:481 2010 DeviceA DLDP/1/TrapOfUnidirectional: -Slot=2; h3cDLDPUnidirectionalPort : DLDP detects a unidirectional link in port 17825792.

%Jan 18 18:10:38:481 2010 DeviceA DLDP/3/DLDP_UNIDIRECTION_MANUAL: -Slot=2; DLDP detects a unidirectional link on port GigabitEthernet1/0/10. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is MANUAL. The port needs to be shut down by the user.

#Jan 18 18:10:38:618 2010 DeviceA DLDP/1/TrapOfUnidirectional: -Slot=2; h3cDLDPUnidirectionalPort : DLDP detects a unidirectional link in port 17825793.

%Jan 18 18:10:38:618 2010 DeviceA DLDP/3/DLDP_UNIDIRECTION_MANUAL: -Slot=2; DLDP detects a unidirectional link on port GigabitEthernet1/0/11. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is MANUAL. The port needs to be shut down by the user.

The output indicates that DLDP has detected a unidirectional link on both GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11, and is asking you to shut down the faulty ports manually.

After you shut down GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11, the following log information is displayed:

<DeviceA> system-view

[DeviceA] interface gigabitethernet 1/0/10

[DeviceA-GigabitEthernet1/0/10] shutdown

%Jan 18 18:16:12:044 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/10 link status is DOWN.

[DeviceA-GigabitEthernet1/0/10] quit

[DeviceA] interface gigabitethernet 1/0/11

[DeviceA-GigabitEthernet1/0/11] shutdown

%Jan 18 18:18:03:583 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/11 link status is DOWN.

The output indicates that the link status of both GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11 is down.

Assume that in this example, the unidirectional links are caused by cross-connected fibers. Correct the fiber connections, and then bring up the ports shut down earlier.

# On Device A, bring up GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11:

[DeviceA-GigabitEthernet1/0/11] undo shutdown

[DeviceA-GigabitEthernet1/0/11]

%Jan 18 18:22:11:698 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/11 link status is UP.

[DeviceA-GigabitEthernet1/0/11] quit

[DeviceA] interface gigabitethernet 1/0/10

[DeviceA-GigabitEthernet1/0/10] undo shutdown

[DeviceA-GigabitEthernet1/0/10]

%Jan 18 18:22:46:065 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/10 link status is UP.

The output indicates that the link status of both GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11 is now up.

Troubleshooting DLDP

Symptom

Two DLDP-enabled devices, Device A and Device B, are connected through two fiber pairs, in which two fibers are cross-connected. The unidirectional links cannot be detected; all the four ports involved are in Advertisement state.

Analysis

The problem can be caused by the following.

· The intervals to send Advertisement packets on Device A and Device B are not the same.

· DLDP authentication modes/passwords on Device A and Device B are not the same.

Solution

Make sure the interval to send Advertisement packets, the authentication mode, and the password configured on Device A and Device B are the same.

07-High Availability Configuration Guide

DLDP configuration

How DLDP works

DLDP link states

DLDP timers

DLDP mode

DLDP authentication mode

DLDP processes

Link auto-recovery mechanism

DLDP neighbor state

DLDP configuration task list

Enabling DLDP

Setting DLDP mode

Setting the interval to send advertisement packets

Setting the DelayDown timer

Configuring DLDP authentication

Displaying and maintaining DLDP

DLDP configuration examples

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Troubleshooting DLDP

Symptom

Analysis

Solution

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us