Configuring Basic DCN Functions

This chapter describes how to enable DCN globally, enable DCN on an interface, enable the automatic NE report function on a GNE, and configure NE IDs and NE IP addresses.

Usage Scenario

The construction of a large network requires significant human and material resources if software commissioning engineers have to configure devices on site, causing high operational expenditure (OPEX). DCN can reduce the OPEX by allowing GNEs to manage NEs. DCN enables NMSs to rapidly detect new NEs and remotely manage the NEs.

The DCN technique offers a mechanism to implement plug-and-play. After each NE is initialized, it generates an NE IP address based on its NE ID, creates a mapping entry for the NE ID and NE IP address, adds the mapping entry to its DCN core routing table, and uses OSPF to advertise the mapping entry to all other NEs on the DCN. Therefore, all the NEs on the DCN can communicate with each other.

The DCN feature allows NMSs to use GNEs to manage NEs. A GNE supports the automatic NE report function, enabling the GNE to automatically report a new NE's information to NMSs immediately after the GNE detects the new NE. Then the NMSs can manage the new NE in time. In addition, a GNE can send a trap to its interworking NMSs when the number of NEs connected to the GNE reaches the alarm threshold. Then the NMSs will generate alarms to inform users of this information.

Pre-configuration Tasks

Before configuring basic DCN functions, complete the following tasks:

Configure reachable routes between the GNE and NMSs.
Configure reachable routes between the GNE and NEs.

When the GNE is connected to an NE for the first time, the SSH default user account is used for login.

Procedure

Enable DCN Globally.
1. Run system-view
  The system view is displayed.
2. Run dcn
  The DCN function is enabled globally.
3. Run commit
  The configuration is committed.

Enable DCN on an interface and specify a DCN VLAN.

By default, DCN is enabled on some interfaces. For details, see .

After an interface is switched to a FLEX interface, the DCN status does not change.

The default DCN enabling rule of a subcard with adjustable interface bandwidth is the same as that of a subcard with only one type of interface bandwidth and is not affected by the adjustable bandwidth.

**Table 1** Rules for enabling DCN on interfaces by default
Interfaces on Fixed Boards	Ethernet Interfaces on Flexible Cards
DCN is enabled on all interfaces by default.	DCN is enabled on all interfaces by default.

In router mode:

Run system-view
The system view is displayed.
Run interface interface-type interface-number
The interface view is displayed.
Run dcn (interface view)
DCN is enabled on the interface.
Run dcn vlan vlan-id or dcn vlan { beginvlan-id [ to endvlan-id ] } &<1–4094>
A DCN VLAN is specified.
Run commit
The configuration is committed.

In router mode, a DCN VLAN can be a service VLAN.

In transport mode:

Run system-view
The system view is displayed.
Run interface interface-type interface-number
The interface view is displayed.
Run dcn
DCN is enabled on the interface.
Run dcn vlan vlan-id
A DCN VLAN is specified.
Run commit
The configuration is committed.

In transport mode, only one DCN VLAN can be configured. And it is conflicted with service VLAN.

Configure the automatic NE report function on a GNE.
1. Run system-view
  The system view is displayed.
2. Run dcn
  The DCN view is displayed.
3. Run auto-report
  The automatic NE report function is enabled.
4. Run commit
  The configuration is committed.
Configure an NE ID and NE IP address.
1. Run system-view
  The system view is displayed.
2. Run set neid ne-id
  An NE ID is set.
3. Run dcn
  The DCN view is displayed.
4. Run ne-ip ip-address { ip-mask | mask-length }
  An NE IP address is set.
5. Run commit
  The configuration is committed.
(Optional) Configure the bandwidth for DCN interfaces to send packets.
1. Run system-view
  The system view is displayed.
2. Run dcn
  The DCN view is displayed.
3. Run bandwidth { ethernet bandwidth }
4. Run commit
  The configuration is committed.

Verifying the Configuration

Perform the following operations to check the configurations:

Run the display neid command to check the NE ID.
Run the display dcn brief command to check configurations of the GNE.
Run the display dcn ne-info command to check information about the DCN core routing table.
Run the display dcn global command to check whether DCN is enabled globally.
Run the display dcn default-port command to check the interface on which DCN is enabled by default.
Run the display dcn interface [ interface-type interface-number ] command to check DCN configurations and traffic statistics of an interface.
Run the display dcn warning command to check DCN trap information.

Run the display neid command to check the NE ID.

<HUAWEI> display neid
NEID: 0x280FC

Run the display dcn brief command to check GNE configuration information.

<HUAWEI> display dcn brief
------------------------------------------------
 NE-ID:               0x10008
 NE-IP:               192.168.0.8
 Mask:                255.255.0.0
 DCN-Interface:       LoopBack2047
 Auto-Report:         Enable
------------------------------------------------

Follow-up Procedure

An NMS's IP address is a public IP address, and a GNE's NE IP address is a Layer 3 VPN address. To implement address conversion, specify the interface that connects a GNE to an NMS, bind the interface to a DCN VPN instance, and set an IP address for the interface. After DCN is enabled globally on the GNE, it automatically generates a DCN VPN instance named __dcn_vpn__. Detailed operations are as follows:

Run the interface interface-type interface-number command to display the interface view.
Run the ip binding vpn-instance vpn-instance-name command to bind a DCN VPN instance.
Run the ip address { mask | mask-length } command to set an interface IP address.