WO2016019645A1

WO2016019645A1 - Method and system for turning on a data communication network, and storage medium

Info

Publication number: WO2016019645A1
Application number: PCT/CN2014/090462
Authority: WO
Inventors: 陈磊
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-08-07
Filing date: 2014-11-06
Publication date: 2016-02-11
Also published as: CN105337754B; CN105337754A

Abstract

Disclosed in the embodiments of the present invention is a method for turning on a data communication network (DCN), said method comprising: on the basis of preset rules for generating a management address, access network elements and non-access network elements respectively generate a network element management IP address, configuring said network element management IP address to manage a loopback interface, and create an OSPF routing instance of the DCN; when it is determined that the Ethernet interface status meets preset conditions, creating an Ethernet sub-interface, generating an IP address routing table of the DCN, and configuring network element information to an OSPF routing protocol; and an EMS parses every network element information sent by the access network elements, creates a logical network element corresponding to the non-access network elements, and creates a connection between non-access network elements. Also disclosed in the embodiments of the present invention are a system for turning on a DCN, and a storage medium.

Description

Data communication network opening method and system, and storage medium

Technical field

The present invention relates to a related art for a data communication network (DCN) in a Packet Transport Network (DTN), and more particularly to a DCN provisioning method and system, and a storage medium.

Background technique

For a newly opened PTN device network, after all the physical layers of the device are successfully connected, the DCN must be enabled first, so that the maintenance personnel can use the EMS (Element Management System) of the telecom operator to each NE (NE). , Net Element) telecom services for remote centralized deployment and monitoring. As the scale of PTN equipment network deployment continues to increase, the labor costs for opening DCN networks are also increasing.

At present, the industry usually adopts an internal gateway-way protocol (IGP) routing instance, such as: Open Shortest Path First (OSPF) bootstrap method to automatically establish DCN between each network element. Channels, improve the efficiency of DCN opening, but the current DCN network can not achieve true automatic opening. Each network element in the DCN network must have a unique Internet Protocol (IP) address, that is, the DCN management address of the network element, used to communicate with the network management server. However, the DCN management address usually needs to be manually specified or dependent on the special The device is assigned.

The latest device manufacturer's DCN solution has added the function of automatically generating IP addresses. However, the generation rules of IPs of various vendors lack unified planning. The IP addresses of different device vendors may conflict, and a device that mixes different device vendors cannot be satisfied. The need for the automatic opening of the DCN network affects the flexible planning of the operator network. In addition, the network management system is usually deployed on high-performance computers or other visual control systems, and does not participate in IGP routing learning of the device network. The method directly senses the device information in the network, and needs to manually create a logical network element in the network management system.

Summary of the invention

In order to solve the above technical problem, the embodiment of the present invention is expected to provide a DCN opening method and system, which can automatically open a data communication network, and has high efficiency and high reliability.

An embodiment of the present invention provides a method for opening a data communication network DCN, where the method includes:

The access network element and the non-access network element respectively generate an IP address management network protocol IP address according to the preset management address generation rule, configure the network element management IP address to the management loopback interface, and create an open type of the DCN. The shortest path first OSPF routing instance;

After determining the status of the Ethernet interface to meet the preset conditions, create an Ethernet sub-interface, generate an IP address routing table of the DCN, and configure the NE information to the OSPF routing protocol.

The network element management system EMS parses the network element information sent by the access network element, creates a logical network element corresponding to the non-access network element, and establishes a connection with the non-access network element.

In the foregoing solution, before the access network element and the non-access network element respectively generate the network element management IP address according to the preset management address generation rule, the method further includes: creating the access network element and the non-access network element. DCN network management instance and management loopback interface.

In the above solution, the management address generation rule includes: determining whether the network element supports the network element identification NEID mapping into the network element management IP address, and if so, mapping the NEID to the network element management IP address; if not, the network element is not supported. The media access control MAC address is mapped to the network element management IP address.

In the foregoing solution, the creating an Ethernet sub-interface and generating a DCN IP address routing table includes: creating a point-to-point type Ethernet sub-interface, binding the Ethernet sub-interface to a virtual local area network VLAN, and configuring the OSPF routing protocol, And generating an IP address routing table of the DCN according to the OSPF routing protocol, where the IP address of the Ethernet sub-interface is a method of renting a DCN management address.

In the above solution, after the network element information is configured to the OSPF routing protocol, the method further includes: configuring a route between the access network element and the EMS, re-provisioning the route to the OSPF routing protocol, and designating the EMS side. The route to each network element.

In the above solution, before the EMS parses the information about the network element that is sent by the network element, the method further includes: creating a logical network element corresponding to the access network element, and establishing a connection between the EMS and the access network element, where The access network element sends each network element information to the EMS.

The embodiment of the present invention further provides a DCN-enabled system, where the system includes: an access network element, a non-access network element, and an EMS;

The access network element and the non-access network element are respectively configured to generate an network element management IP address according to the preset management address generation rule, configure the network element management IP address to the management loopback interface, and create a DCN. OSPF routing instance;

And determining that the Ethernet interface status meets the preset condition, creating an Ethernet sub-interface, generating a DCN IP address routing table, and configuring the network element information to the OSPF routing protocol;

The EMS is configured to parse each network element information sent by the access network element, create a logical network element corresponding to the non-access network element, and establish a connection with the non-access network element.

In the above solution, the access network element and the non-access network element are respectively configured to create a DCN network management instance and a management loopback interface.

In the above solution, the management address generation rule includes: determining whether the network element supports the NEID mapping into the network element management IP address, and if yes, mapping the NEID to the network element management IP address; if not, mapping the network element MAC address to The NE manages the IP address.

In the above solution, the access network element and the non-access network element respectively create an Ethernet sub-interface, and the IP address routing table for generating the DCN includes: the access network element and the non-access network element respectively create a peer-to-peer type Ethernet The network sub-interface binds the Ethernet sub-interface to the VLAN and configures the OSPF routing protocol to generate an IP address routing table of the DCN according to the OSPF routing protocol. The IP address of the Ethernet sub-interface is leased by the DCN. The way the address is managed.

In the above solution, the access network element is further configured to configure a route between the access network element and the EMS, and re-advertise the route to the OSPF routing protocol;

Correspondingly, the system further comprises a gateway;

The EMS is further configured to specify a route of the EMS to the gateway;

The gateway is configured to specify a route from the gateway to each network element.

In the above solution, the EMS is further configured to create a logical network element corresponding to the access network element, and establish a connection between the EMS and the access network element;

The access network element is further configured to send each network element information to the EMS.

A storage medium having stored therein a computer program configured to perform the aforementioned data communication network DCN activation method.

In the DCN-opening method and system provided by the embodiment of the present invention, the access network element and the non-access network element respectively generate an IP address management IP address according to a preset management address generation rule, and configure the network element management IP address to be managed. On the loopback interface, create an OSPF route instance of the DCN. If the Ethernet interface status meets the preset conditions, create an Ethernet sub-interface, generate a DCN IP address routing table, and configure the NE information to the OSPF routing protocol. The network element information sent by the access network element is parsed, the logical network element corresponding to the non-access network element is created, and a connection with the non-access network element is established. In this way, the data communication network can be automatically opened, which saves a lot of manpower and financial costs, improves user satisfaction, and has high efficiency and high reliability.

DRAWINGS

1 is a schematic flowchart of a DCN opening method according to an embodiment of the present invention;

2 is a network topology diagram of a DCN according to an embodiment of the present invention;

3 is a schematic flowchart of a method for opening a DCN according to Embodiment 2 of the present invention;

FIG. 4 is a schematic structural diagram of a DCN open system according to an embodiment of the present invention.

detailed description

In the embodiment of the present invention, the access network element and the non-access network element respectively generate an IP address management IP address according to the preset management address generation rule, and configure the network element management IP address to the management loopback interface, and Create an OSPF route instance of the DCN. If the Ethernet interface status meets the preset conditions, create an Ethernet sub-interface, generate an IP address routing table of the DCN, and configure the NE information to the OSPF routing protocol. The EMS resolves the access NE. Each of the network element information creates a logical network element corresponding to the non-access network element, and establishes a connection with the non-access network element;

The network element information includes network element information of the access network element and the non-access network element.

1 is a schematic flowchart of a DCN activation method according to an embodiment of the present invention. As shown in FIG. 1 , the DCN activation method in this embodiment includes:

Step 101: The access network element and the non-access network element respectively generate an IP address management IP address according to the preset management address generation rule, configure the network element management IP address to the management loopback interface, and create DCN OSPF. Routing instance

Before the step, the method further includes: the access network element and the non-access network element respectively create a DCN network management instance and a management loopback interface;

Here, the DCN network management instance refers to a dedicated DCN virtual route forwarding (VRF) instance created for the DCN network, which can isolate the management route and service route of the PTN network to avoid mutual interference.

As an implementation manner, the management address generation rule includes: determining whether the network element supports NE ID (Net Elemet Identification) mapping into a network element management IP address, and if supported, mapping the NEID to an network element management IP address. If not supported, the network element access control (MAC) address is mapped to the network element management IP address;

Correspondingly, the access network element and the non-access network element respectively generate the network element management IP address according to the preset management address generation rule: the access network element and the non-access network element respectively determine whether the NEID is supported by the NEID generation network element management. IP address, if supported, directly maps its own NEID to a network element. Management IP address; if not supported, map its own MAC address to the NE management IP address;

The NEID is a unique digitized identifier of the network element, and the length is 4 bytes, which is written by each vendor when the device generates the shipment. The NEID definition rule in the embodiment of the present invention is as follows:

The device NEID is defined as 4 bytes, 32 bit serial number, NEID is currently defined to use 24 bits, where BIT [20 ~ 27] is reserved, the first 4 bytes of the first byte are used to identify the device type, and the remaining bytes are 20 The bits are used to identify the device hardware serial number. NEID supports non-volatile storage. For devices with storage space on the backplane, NEID can be saved in the non-volatile memory of the backplane. For devices with no storage space on the backplane, it is stored in the non-volatile storage of the main control board of the device. In space

The network element management IP address is planned into three segments in bytes from high to low:

The first segment: the device manufacturer number, occupies the first byte of the IPv4 address, and the operator specifies a fixed number for different telecommunication device vendors according to network requirements;

The second segment: the device model, which occupies the upper 4 bits of the second byte of the IPv4 address, and is allocated by the device manufacturer for the PTN devices of different models;

The third sector: the IP address sequence number, which occupies the lower four bits, the third byte, and the fourth byte of the second byte of the IPv4 address. In theory, for the same PTN device of the same manufacturer, the network can support 0xfffff, which is 1048575, which can fully meet the network needs of telecom operators.

As an implementation manner, when the network element supports the NEID to generate the network element management IP address and the NEID is mapped to the network element management IP address, the network element management IP address is generated according to the NEID:

The first segment of the network element management IP address: a fixed value defined by the telecommunication operator for each device manufacturer;

The second section of the network management IP address: the serial number of the device in the NEID;

The third section of the network management IP address: the 20Bit effective device sequence number of the NEID;

When the network element does not support the NEID to generate the network element management IP address and the network element MAC address is mapped to the network element management IP address, the generation rule of the network element management IP address according to the network element MAC address is:

The first section of the network element management IP address: a fixed value defined by the telecommunications carrier for each equipment manufacturer;

The second section of the network management IP address: This section is fixed to 0 to distinguish the NEID generation.

The third section of the network management IP address: the vendor number part of the MAC address is ignored, that is, the first 3 bytes, only the last three bytes of the MAC address are used for mapping, and the last 3 bytes represent the internal hardware number of the vendor number. The number is unique within the manufacturer. Since each device usually needs to occupy multiple MAC addresses in succession, the last three bytes of the MAC address are shifted to the right by N bits, and then the lower 24 bits are copied to the third sector. The bit number of the right shift is N=log2(M), and M is the number of displacements of the MAC address occupied by the device.

As an implementation manner, an OSPF routing instance of the DCN is created, and the management loopback interface can be configured to an OSPF routing protocol to enable route negotiation between the network elements.

The management loopback interface uses a 32-bit mask.

Step 102: After determining that the status of the Ethernet interface meets the preset condition, create an Ethernet sub-interface, generate an IP address routing table of the DCN, and configure the network element information to the OSPF routing protocol.

Here, the preset condition means that the Ethernet interface status is UP;

The method includes: the access network element and the non-access network element periodically detect the state of the Ethernet interface, and when the status of the Ethernet interface is UP, create a point-to-point type Ethernet sub-interface, and bind the Ethernet sub-interface. The interface is connected to a virtual local area network (VLAN) and configured to an OSPF routing protocol, and generates an IP address routing table of the DCN according to the OSPF routing protocol, so that routing between the network elements is available; wherein the Ethernet sub-interface The IP address of the interface adopts the method of renting the DCN management address.

And configuring the network element information to the OSPF routing protocol, so that when the OSPF routing protocol works normally, the extended link state configuration (LSA) including the network element information is flooded in the DCN domain. The access network element can obtain the network element information of each network element in the DCN domain in its own OSPF database.

The network element information includes: an NEID, a network element MAC address, an element management IPv4 address, a network element device vendor identifier, and a network element type.

The OSPF routing protocol uses the special type10 type of Opaque LSA to carry the NE information for flooding. Here, the LSA ID is defined as 200.255.238.0, where 200 is the opaque type and 255.238.0 (ffee00) is the instance information.

The Opaque LSA carries the following NE information in the TLV format:

NE device vendor ID: Type: 0x8000; Length: ID name string length;

NE model: Type: 0x8001; Length: Model name string length;

NE MAC: Type: 0x8002; Length: 6 bytes;

NEID: Type: 0x8003; Length: 4 bytes;

NEIP IPv4: Type: 0x8004; Length: 4 bytes.

As an implementation manner, after the network element information is configured to the OSPF routing protocol, the method further includes: configuring a route between the access network element and the EMS, re-provisioning the route to the OSPF routing protocol, and designating the EMS side. Routing to each network element; thus, clearing the route between the EMS and the entire PTN network element;

The EMS side includes an EMS and a gateway;

The routing of the specified EMS side to each network element includes: specifying a route from the EMS to the gateway, and routing of the gateway to each network element.

Step 103: The EMS parses the network element information sent by the access network element, creates a logical network element corresponding to the non-access network element, and establishes a connection with the non-access network element.

Before the step, the method further includes: creating a logical network element corresponding to the access network element, and establishing a connection between the EMS and the access network element, where the access network element sends each network element information to the EMS;

Here, the establishing the connection between the EMS and the access network element is specifically: establishing a TCP/IP connection between the EMS and the access network element;

The sending, by the access network element, the information of each network element to the EMS includes: the access network element actively sends the whole Each network element information of the DCN network is sent to the EMS; or the access network element receives the network element information request sent by the EMS, and sends the network element information of the entire DCN network to the EMS.

As an implementation manner, the step further includes: the EMS parses the information of each network element sent by the access network element, and obtains the network element management IP address, the network element type, the network element MAC address, or the NEID of each network element, and creates and disconnects The logical network element corresponding to the incoming network element establishes a connection with the non-access network element according to the standard TCP/IP protocol, that is, establishes a TCP/IP connection with the non-access network element; thus, the EMS can implement the Management of all network elements.

2 is a network topology diagram of a DCN according to an embodiment of the present invention. As shown in FIG. 2, the network includes an EMS, a gateway, and five network elements NEA to E. The NE A is an access network element, and the NE B to E are non- The access network element may be one or more access network elements, and the non-access network element may be one or more.

FIG. 3 is a schematic flowchart of a method for opening a DCN according to Embodiment 2 of the present invention. In combination with FIG. 2 and FIG. 3, a method for opening a DCN according to an embodiment of the present invention includes:

Step 301: The access network element and the non-access network element respectively create a DCN network management instance and a management loopback interface.

Here, the DCN network management instance refers to a dedicated DCN VRF instance created for the DCN network, which can isolate the management route and service route of the PTN network to avoid mutual interference;

In this embodiment, after the access network element and the non-access network element are powered on, the DCN VRF instance is automatically created, the management loopback interface loopback 1023 is created, and the management loopback interface is bound to the DCN VPN.

Step 302: Generate an IP address management IP address according to the preset management address generation rule, configure the network element management IP address to the management loopback interface, and create an OSPF routing instance of the DCN.

Here, the management address generation rule includes: determining whether the network element supports the mapping of the NEID to the network element management IP address, and if so, mapping the NEID to the network element management IP address; if not, mapping the network element MAC address to the network element Management IP address;

Correspondingly, the access network element and the non-access network element respectively generate the network element management IP address according to the preset management address generation rule: the access network element and the non-access network element respectively determine whether the NEID is supported by the NEID generation network element management. IP address, if supported, directly maps the NEID to the NE management IP address; if not, maps its own MAC address to the NE management IP address;

In this embodiment, NE A to C support NEID mapping to the network element management IP address, NE D and NEE do not support NEID mapping into the network element management IP address; the operator allocates the network element management IP first byte value to be 131 (decimal The four bits of the identifier assigned by the manufacturer for NE A are 0001 (binary), and the identifier assigned to NE B to E is 0002 (binary), and each network element is continuously allocated 8 MAC addresses. At this time, each network element The generated NE management IP addresses are as follows:

NE A: Generate 131.17.1.1 according to NEID;

NE B: generates 131.33.1.5 according to NEID;

NE C: generates 131.33.1.4 according to NEID;

NE D: generates 131.0.36.32 according to the MAC address of the network element;

NE E: generates 131.0.38.32 according to the MAC address of the network element;

The management loopback interface uses a 32-bit mask.

Step 303: Detecting the status of the Ethernet interface, determining whether the status of the Ethernet interface meets the preset condition, when the preset condition is met, step 304 is performed; when the preset condition is not met, step 303 is performed;

Here, the detecting the status of the Ethernet interface is to periodically detect the status of the Ethernet interface;

The preset condition is that the Ethernet interface status is UP, and the non-compliant preset condition means that the Ethernet interface status is DOWN.

Step 304: Create an Ethernet sub-interface, and generate an IP address routing table of the DCN.

The step specifically includes: the access network element and the non-access network element respectively create a peer-to-peer type Ethernet a network sub-interface, which binds the Ethernet sub-interface to a VLAN and is configured to an OSPF routing protocol, and generates an IP address routing table of the DCN according to the OSPF routing protocol, so that routing between the network elements is available; wherein the Ethernet The IP address of the sub-interface is in the manner of renting the DCN management address.

In this embodiment, when the status of the Ethernet interface is Up, the 4094 point-to-point type Ethernet sub-interface is automatically created and bound to VLAN 4094. The specific creation is as follows:

The Ethernet sub-interface gei_1/1.4094, gei_1/3.4094 is created by default on NE A;

The Ethernet sub-interface gei_1/3.4094, gei_1/2.4094 is created by default on NE B.

The Ethernet sub-interface gei_1/2.4094 is created by default on NE C.

The Ethernet sub-interface gei_1/1.4094, gei_1/2.4094 is created by default on NE D;

The Ethernet sub-interface gei_1/2.4094 is created by default on NE E.

The Ethernet sub-interface created above is bound to the DCNVPN and configured to the OSPF routing protocol. The access NE and the non-access NE perform routing learning according to the OSPF routing protocol to generate an IP address routing table of the DCN. The routes between the network elements can pass.

Step 305: Configure the network element information to the OSPF routing protocol to perform flooding of the entire network of the DCN.

Here, the access network element and the non-access network element respectively configure the network element information to the OSPF routing protocol, so that when the OSPF routing protocol works normally, the extended LSA including the network element information is flooded in the DCN domain. The access network element can obtain the network element information of each network element in the DCN domain in its own OSPF database.

In this embodiment, the NE information configured by each network element to the OSPF routing protocol is as follows:

NE A:

Manufacturer ID: XXX

NE ID: NE A

NE MAC address: 00d0.d001.1101

NEID: 16.1.1.1

NE management IP: 131.17.1.1

NE B:

Manufacturer ID: XXX

NE ID: NE B

NE MAC address: 00d0.d001.5101

NEID: 32.1.1.5

NE management IP: 131.33.1.5

NE C:

Manufacturer ID: XXX

NE ID: NE C

NE MAC address: 00d0.d001.4101

NEID: 0.0.0.0

NE management IP: 131.33.1.4

NE D:

Manufacturer ID: XXX

NE ID: NE D

NE MAC address: 00d0.d001.2101

NEID: 0.0.0.0

NE management IP: 131.0.36.32

NE E:

Manufacturer ID: XXX

NE ID: NE E

NE MAC address: 00d0.d001.3101

NEID: 0.0.0.0

NE management IP: 131.0.38.32

The NEID of 0.0.0.0 indicates that the device of this type does not support NEID, and the value is invalid.

It should be noted that the sequence of operations of step 305 and step 303-step 304 is interchangeable.

Step 306: Configure a route between the access NE and the EMS, and re-advertise the route to the OSPF routing protocol, and specify the route from the EMS side to each network element.

Here, the route between the access network element and the EMS is configured, and the route is re-advertised to the OSPF routing protocol through OSPF route redistribution, and the route from the EMS side to each network element is specified; thus, the EMS and the entire PTN network network are opened. Routing between the elements; wherein the EMS side includes an EMS and a gateway;

In this embodiment, the EMS is in the network segment 10.0.0.0.0/255.255.0.0 and is not directly connected to the DCN network. You need to add a static route. The destination network segment is 10.8.0.0 and the hop is 255.255.0.0. The next hop is 194.194. Static route of 194.1, and republish the static route to the OSPF routing protocol;

Specifies the route from the EMS and the gateway device to each NE. The first byte of the management IP address of the NE generated by the NE is specified. The route configuration on the EMS is simplified. Specify the following:

EMS: destination network segment 131.0.0.0, mask 255.0.0.0, next hop for gateway device 10.8.63.144;

Gateway device: destination network segment 131.0.0.0, mask 255.0.0.0, next hop is the access port of the access network element 194.194.194.123.

Step 307: Create a logical network element corresponding to the access network element, and establish a connection between the EMS and the access network element.

Here, the establishing the connection between the EMS and the access network element is specifically: establishing a TCP/IP connection between the EMS and the access network element.

Step 308: The access network element sends each network element information to the EMS.

The step specifically includes: the access network element actively sends information about each network element of the entire DCN network. To the EMS, the access network element receives the NE information request sent by the EMS, and sends the NE information of the entire DCN network to the EMS.

Step 309: The EMS parses the network element information sent by the access network element, creates a logical network element corresponding to the non-access network element, and establishes a connection with the non-access network element.

The specific steps include: the EMS parses the information of each network element sent by the access network element, and obtains the network element management IP address, the network element type, the network element MAC address, or the NEID of each network element, and creates a logic corresponding to the non-access network element. The network element establishes a connection with the non-access network element according to the standard TCP/IP protocol, that is, establishes a TCP/IP connection with the non-access network element; thus, the EMS can implement management of all network elements.

Step 310: End the processing flow.

4 is a schematic structural diagram of a DCN open system according to an embodiment of the present invention. As shown in FIG. 4, the DCN open system component of the embodiment of the present invention includes: an access network element 41, a non-access network element 42 and an EMS 43; The element 41 may be one or more, and the non-access network element 42 may be one or more;

The access network element 41 and the non-access network element 42 are respectively configured to generate an network element management IP address according to a preset management address generation rule, and configure the network element management IP address to the management loopback interface, and Create an OSPF route instance of the DCN.

The EMS 43 is configured to parse each network element information sent by the access network element 41, create a logical network element corresponding to the non-access network element 42, and establish a connection with the non-access network element 42.

As an implementation manner, the access network element 41 and the non-access network element 42 are respectively configured to create a DCN network management instance and a management loopback interface.

Here, the DCN network management instance refers to a dedicated DCN VRF instance created for the DCN network, which can isolate the management route and service route of the PTN network to avoid mutual interference.

As an implementation manner, the management address generation rule includes: determining whether the network element supports the NEID mapping into the network element management IP address, and if yes, mapping the NEID to the network element management IP address; if not, the network element MAC address is not supported. Mapping to an NE management IP address;

Correspondingly, the access network element 41 and the non-access network element 42 respectively generate the network element management IP address according to the preset management address generation rule, and the access network element 41 and the non-access network element 42 respectively determine whether Supports NEID to generate an IP address management IP address. If supported, directly maps the NEID to the NE management IP address; if not, maps its own MAC address to the NE management IP address;

The access network element 41 and the non-access network element respectively create an OSPF routing instance of the DCN, and then configure the management loopback interface to the OSPF routing protocol to enable route negotiation between the network elements.

The management loopback interface uses a 32-bit mask.

As an implementation manner, the preset condition is that the Ethernet interface status is UP;

The access network element 41 and the non-access network element 42 respectively create an Ethernet sub-interface. The IP address routing table for generating the DCN includes: the access network element 41 and the non-access network element 42 respectively create a peer-to-peer type Ethernet. The network sub-interface binds the Ethernet sub-interface to the VLAN and configures the OSPF routing protocol to generate an IP address routing table of the DCN according to the OSPF routing protocol. The IP address of the Ethernet sub-interface is leased by the DCN. The way the address is managed;

The access network element 41 and the non-access network element 42 respectively configure the network element information to the OSPF routing protocol, so that when the OSPF routing protocol works normally, the extended LSA including the network element information is flooded in the DCN domain. The flooding, in which the access network element obtains the network element information of each network element in the DCN domain in its own OSPF database;

The network element information includes: an NEID, a network element MAC address, an element management IPv4 address, a network element device manufacturer identifier, and a network element type.

As an implementation manner, the access network element 41 is further configured to configure a route between the access network element and the EMS, and re-advertise the route to the OSPF routing protocol;

Correspondingly, the system further includes a gateway 44;

The EMS 43 is further configured to specify a route of the EMS 43 to the gateway 44;

The gateway 44 is configured to specify a route from the gateway 44 to each network element.

As an implementation manner, the EMS 43 is further configured to create a logical network element corresponding to the access network element 41, and establish a TCP/IP connection between the EMS 43 and the access network element 41.

The access network element 41 is further configured to send each network element information to the EMS 43.

As an implementation manner, the EMS 43 parses the network element information sent by the access network element 41, creates a logical network element corresponding to the non-access network element 42, and establishes a connection with the non-access network element 42. The EMS 43 analyzes the network element information sent by the access network element 41, and obtains the network element management IP address, the network element type, the network element MAC address, or the NEID of each network element, and creates a logical network element corresponding to the non-access network element 42. The connection with the non-access network element 42 is established according to the standard TCP/IP protocol, that is, the TCP/IP connection with the non-access network element 42 is established; thus, the EMS 43 can implement management of all network elements.

Both the access network element 41 and the non-access network element 42 in the embodiment of the present invention may be PTN devices.

The embodiment of the invention further describes a storage medium in which a computer program is stored, the computer program being configured to execute the data communication network DCN activation method of the foregoing embodiment.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Industrial applicability

In the present invention, the access network element and the non-access network element respectively generate an IP address management IP address according to the preset management address generation rule, configure the network element management IP address to the management loopback interface, and create a DCN. OSPF routing instance; when the Ethernet interface status meets the preset conditions, an Ethernet sub-interface is created, the DCN IP address routing table is generated, and the NE information is configured to the OSPF routing protocol; the EMS resolves the network sent by the access NE. Meta information, created corresponding to non-access network elements Logical network element and establish a connection with the non-access network element. It can automatically open the data communication network, save a lot of manpower and financial costs, improve user satisfaction, and has high efficiency and reliability.

Claims

A method for opening a data communication network DCN, comprising:

The access network element and the non-access network element respectively generate an IP address management network protocol IP address according to the preset management address generation rule, configure the network element management IP address to the management loopback interface, and create an open type of the DCN. The shortest path first OSPF routing instance;

After determining the status of the Ethernet interface to meet the preset conditions, create an Ethernet sub-interface, generate an IP address routing table of the DCN, and configure the NE information to the OSPF routing protocol.

The network element management system EMS parses the network element information sent by the access network element, creates a logical network element corresponding to the non-access network element, and establishes a connection with the non-access network element.
The method according to claim 1, wherein the method further comprises: accessing the network element and before the access network element and the non-access network element respectively generate the network element management IP address according to the preset management address generation rule. The non-access NE creates an instance of the DCN NMS and manages the loopback interface.
The method according to claim 1 or 2, wherein the management address generation rule comprises: determining whether the network element supports the network element identity NEID mapping into a network element management IP address, and if so, mapping the NEID to the network element management IP address. If not supported, map the NE media access control MAC address to the NE management IP address.
The method according to claim 1 or 2, wherein the creating an Ethernet sub-interface, generating an IP address routing table of the DCN comprises: creating an Ethernet sub-interface of a point-to-point type, and binding the Ethernet sub-interface to a virtual local area network VLAN And configuring an OSPF routing protocol, and generating an IP address routing table of the DCN according to the OSPF routing protocol; wherein the IP address of the Ethernet sub-interface adopts a method of renting a DCN management address.
The method according to claim 1 or 2, wherein after the configuring the network element information to the OSPF routing protocol, the method further comprises: configuring a route between the access network element and the EMS, and re-publishing the route to OSPF In the routing protocol, the route from the EMS side to each NE is specified.
The method according to claim 1 or 2, wherein the EMS parses each of the transmissions sent by the access network element Before the network element information, the method further includes: creating a logical network element corresponding to the access network element, and establishing a connection between the EMS and the access network element, where the access network element sends each network element information to the EMS .
A DCN-enabled system includes: an access network element, a non-access network element, and an EMS; wherein

The access network element and the non-access network element are respectively configured to generate an network element management IP address according to the preset management address generation rule, configure the network element management IP address to the management loopback interface, and create a DCN. OSPF routing instance;

And determining that the Ethernet interface status meets the preset condition, creating an Ethernet sub-interface, generating a DCN IP address routing table, and configuring the network element information to the OSPF routing protocol;

The EMS is configured to parse each network element information sent by the access network element, create a logical network element corresponding to the non-access network element, and establish a connection with the non-access network element.
The system of claim 7, wherein the access network element and the non-access network element are further configured to create a DCN network management instance and a management loopback interface.
The system according to claim 7 or 8, wherein the management address generation rule comprises: determining whether the network element supports mapping of the NEID to the network element management IP address, and if so, mapping the NEID to the network element management IP address; if not supported Map the network element MAC address to the NE management IP address.
The system according to claim 7 or 8, wherein the access network element and the non-access network element respectively create an Ethernet sub-interface, and the IP address routing table for generating the DCN includes: the access network element and the non-access The network element respectively creates a point-to-point type Ethernet sub-interface, binds the Ethernet sub-interface to the VLAN, and configures an OSPF routing protocol to generate a DCN IP address routing table according to the OSPF routing protocol. The IP address of the sub-interface is the way to lease the DCN management address.
The system of claim 7 or 8, wherein the access network element is further configured to configure a route between the access network element and the EMS, and re-advertise the route to the OSPF routing protocol;

Correspondingly, the system further comprises a gateway;

The EMS is further configured to specify a route of the EMS to the gateway;

The gateway is configured to specify a route from the gateway to each network element.
The system of claim 7 or 8, wherein the EMS is further configured to create a logical network element corresponding to the access network element, and establish a connection between the EMS and the access network element;

The access network element is further configured to send each network element information to the EMS.
A storage medium storing a computer program configured to perform the data communication network DCN activation method according to any one of claims 1 to 6.