No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

ME60 V800R010C10SPC500 Feature Description - System Management 01

This is ME60 V800R010C10SPC500 Feature Description - System Management
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
DCN Fundamentals

DCN Fundamentals

Figure 9-2 Basic DCN principles

Huawei NEs can use serial interfaces or sub-interfaces numbered 4049 for DCN communication. Non-Huawei NEs cannot use serial interfaces for DCN communication. Therefore, to implement DCN communication between Huawei NEs and non-Huawei NEs, sub-interfaces numbered 4094 must be configured.

Using Serial Interfaces for DCN Communication

The devices on a data communication network (DCN) communicate with each other using the Point-to-Point Protocol (PPP) through single-hop logical channels. Therefore, packets transmitted on the DCN are encapsulated into PPP frames and forwarded through service ports at the data link layer.

As shown in Figure 9-2, the NMS uses a GNE to manage non-GNEs in the following process:
  1. After the DCN function is enabled, a PPP channel and an OSPF neighbor relationship are established between devices.
  2. OSPF LSAs are sent between OSPF neighbors to learn host routes carrying NEIP addresses to obtain mappings between NEIP addresses and NEIDs.
  3. GNE sends the mappings to NMS, The NMS then accesses non-GNEs.
A core routing table is generated in the following process:
  1. After PPP Network Control Protocol (NCP) negotiation is complete, a point-to-point route is generated without network segment restrictions.
  2. An OSPF neighbor relationship is set up, and an OSPF route is generated for the entire network.
  3. NEIDs are advertised using OSPF LSAs, triggering the generation of a core routing table.

Using Sub-Interfaces Numbered 4094 for DCN Communication

A sub-interface numbered 4094 is configured on a DCN-enabled interface and used for DCN communication between NEs. After the sub-interface numbered 4094 is configured, it is automatically associated with VLAN 4094, and its encapsulation type is dot1q VLAN tag termination. OSPF is enabled on the sub-interface numbered 4094 by default.

As shown in Figure 9-2, the NMS uses a GNE to manage non-GNEs in the following process:
  1. Each neighbor learns host routes to NEIP addresses through OSPF, as well as mapping relationships between NEIP addresses and NEIDs.
  2. The GNE sends the mapping relationships to the NMS, and the NMS can directly access non-GNEs.
A core routing table is generated in the following process:
  1. An OSPF neighbor relationship is set up, and an OSPF route is generated for the entire network.
  2. NEIDs are advertised using OSPF link-state advertisements (LSAs), triggering the generation of a core routing table.
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059466

Views: 10497

Downloads: 7

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next