CN105337754B - Data communication network opening method and system - Google Patents

Abstract

The invention discloses a method for opening a data communication network (DCN). The method includes: an access network element and a non-access network element respectively generate a network element management IP address according to a preset management address generation rule; The meta management IP address is configured on the management loopback interface, and an OSPF routing instance of the DCN is created; when it is determined that the status of the Ethernet interface meets the preset conditions, an Ethernet sub-interface is created, the IP address routing table of the DCN is generated, and the NE information Configure the OSPF routing protocol; EMS parses the information of each network element sent by the access network element, creates a logical network element corresponding to the non-access network element, and establishes the connection with the non-access network element. The invention also discloses a DCN activation system at the same time.

Description

A method and system for opening a data communication network

technical field

The present invention relates to a related technology for opening a data communication network (DCN, Data Communication Network) in a packet transport network (PTN, Packet Transport Network), in particular to a method and system for opening a DCN.

Background technique

For a newly deployed PTN device network, after all devices are successfully connected at the physical layer, the DCN needs to be activated first, so that maintenance personnel can use the telecom operator's Element Management System (EMS, Element Management System) to monitor each network element (NE, Element Management System). Net Element) telecommunications services are remotely deployed and monitored centrally. With the continuous increase in the scale of PTN equipment network deployment, the labor cost of opening the DCN network is also increasing.

At present, the industry usually adopts the built-in Internal Gateway Protocol (IGP, Internal Gate-way Protocol) routing instance, for example, through the Open Shortest Path First (OSPF, Open Shortest Path First) bootstrapping method to automatically establish the DCN between each network element channel, and improve the efficiency of DCN opening. However, the current DCN network cannot achieve true automatic opening. Each network element in the DCN network must have a unique Internet Protocol (IP, Internet Protocol) address, that is, the DCN management address of the network element, which is used to communicate with the network management server. However, at present, the DCN management address usually needs to be manually specified or rely on special equipment for distribution.

The latest DCN solutions of equipment manufacturers have added the function of automatic IP address generation. However, the IP generation rules of various manufacturers lack unified planning, and the IP addresses of different equipment manufacturers may conflict. The requirement for automatic provisioning of the DCN network has affected the flexible planning of the operator's network. In addition, the network management system is usually deployed on high-performance computers or other visual control systems, and does not participate in the IGP route learning of the device network, and cannot directly perceive the device information in the network. It needs to manually create logical network elements in the network management system.

SUMMARY OF THE INVENTION

In view of this, the embodiments of the present invention are expected to provide a DCN activation method and system, which can automatically activate a data communication network, and has high efficiency and high reliability.

In order to achieve the above object, the technical scheme of the present invention is achieved in this way:

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

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, configure the network element management IP address on the management loopback interface, and create an open DCN. Shortest path first OSPF routing instance;

When it is determined that the status of the Ethernet interface meets the preset conditions, an Ethernet sub-interface is created, the IP address routing table of the DCN is generated, and the network element information is configured to the OSPF routing protocol;

The network element management system EMS parses the information of each network element 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 above 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: judging whether the network element supports the mapping of the network element identity 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 to the network element management IP address; The MAC address of the medium access control is mapped to the management IP address of the network element.

In the above scheme, the described creation of the Ethernet sub-interface, and the generation of the IP address routing table of the DCN include: creating a point-to-point type Ethernet sub-interface, binding the Ethernet sub-interface to a virtual local area network VLAN, and being configured to the OSPF routing protocol, The IP address routing table of the DCN is generated according to the OSPF routing protocol; wherein, the IP address of the Ethernet sub-interface adopts the mode of leasing the DCN management address.

In the above solution, after configuring the network element information to the OSPF routing protocol, the method further includes: configuring a route between the access network element and the EMS, republishing the route to the OSPF routing protocol, and specifying the EMS side Routes to NEs.

In the above solution, before the EMS parses the network element information sent by the access 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, the The access network element sends each network element information to the EMS.

The embodiment of the present invention further provides a DCN activation system, the 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 used to generate a network element management IP address according to a preset management address generation rule, configure the network element management IP address on the management loopback interface, and create a DCN The OSPF routing instance;

And when it is determined that the status of the Ethernet interface meets the preset conditions, the Ethernet sub-interface is created, the IP address routing table of the DCN is generated, and the network element information is configured to the OSPF routing protocol;

The EMS is used to parse the 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 further used to create a DCN network management instance and manage a loopback interface, respectively.

In the above solution, the management address generation rule includes: judging whether the network element supports the mapping of the NEID to the management IP address of the network element, if so, mapping the NEID to the management IP address of the network element; if not, mapping the MAC address of the network element to the network element management IP address. NE management IP address.

In the above solution, the access network element and the non-access network element respectively create an Ethernet sub-interface, and the generation of the IP address routing table of the DCN includes: the access network element and the non-access network element respectively create a point-to-point Ethernet sub-interface. The network sub-interface, binds the Ethernet sub-interface to VLAN, and is configured to the OSPF routing protocol, and generates the IP address routing table of the DCN according to the OSPF routing protocol; wherein, the IP address of the Ethernet sub-interface adopts the leased DCN How addresses are managed.

In the above solution, the access network element is also used to configure the route between the access network element and the EMS, and republish the route to the OSPF routing protocol;

Correspondingly, the system further includes a gateway;

The EMS is also used to specify a route from the EMS to the gateway;

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

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

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

In the DCN provisioning method and system provided by the embodiments of the present invention, the access network element and the non-access network element respectively generate a network element management IP address according to a preset management address generation rule, and configure the network element management IP address to the management On the loopback interface, create an OSPF routing instance of the DCN; when it is determined that the status of the Ethernet interface meets the preset conditions, create an Ethernet sub-interface, generate the IP address routing table of the DCN, and configure the NE information to the OSPF routing protocol; EMS Parse the 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 this way, the data communication network can be automatically opened, a lot of manpower and financial costs are saved, user satisfaction is improved, and the efficiency and reliability are high.

Description of drawings

1 is a schematic flowchart of a method for opening a DCN according to Embodiment 1 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 activation system according to an embodiment of the present invention.

Detailed ways

In this embodiment of the present invention, the access network element and the non-access network element respectively generate a network element management IP address according to a preset management address generation rule, configure the network element management IP address on the management loopback interface, and Create an OSPF routing instance of the DCN; when it is determined that the status of the Ethernet interface meets the preset conditions, create an Ethernet sub-interface, generate the IP address routing table of the DCN, and configure the NE information to the OSPF routing protocol; EMS parses the access NE to send information of each network element, create a logical network element corresponding to the non-access network element, and establish a connection with the non-access network element;

Wherein, the network element information includes the network element information of the access network element and the non-access network element.

FIG. 1 is a schematic flowchart of a DCN activation method according to Embodiment 1 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 a network element management IP address according to a preset management address generation rule, configure the network element management IP address on the management loopback interface, and create an OSPF of the DCN routing instance;

Before this 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, VirtualRoute Forwarding) instance created for the DCN network, which can isolate the management route and service route of the PTN network to avoid mutual interference.

Further, the management address generation rule includes: judging whether the network element supports the network element identity identifier (NEID, Net Elemet Identification) to be mapped to the network element management IP address, if supported, the NEID is mapped to the network element management IP address; Support, map the network element Media Access Control (MAC, Media Access Control) address to the network element management IP address;

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

Wherein, the NEID is the unique digital identifier of the network element, with a length of 4 bytes, and is written by each manufacturer when the equipment is generated and shipped. In the embodiment of the present invention, the NEID definition rules are as follows:

Device NEID is defined as 4 bytes, 32 bit serial number, NEID is currently defined as 24 bits, of which BIT[20~27] are reserved, the first 4 bits of the first byte are used to identify the device type, and the remaining 20 bytes bits are used to identify the device hardware serial number. NEID supports non-volatile storage. For devices with storage space on the backplane, the NEID is required to be stored in the non-volatile memory on the backplane; for devices without 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 sections in bytes from high to low:

The first section: the equipment manufacturer number, occupying the first byte of the IPv4 address, and the operator assigns a fixed number for different telecom equipment manufacturers according to network requirements;

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

The third section: IP address serial number, occupying 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 from the same manufacturer, the network can support up to 0xfffff, that is, 1,048,575 units, which can fully meet the network requirements of telecom operators.

Further, 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 according to the generation rule of the NEID is:

The first segment of the network element management IP address: a fixed value defined by telecom operators for each equipment manufacturer;

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

The third segment of the network element management IP address: the 20Bit effective device serial number of the lower 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 network element management IP address according to the generation rule of the network element MAC address is:

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

The second section of the network element management IP address: This section is fixed to 0 to distinguish the situation where the NEID is generated;

The third segment of the NE management IP address: ignore the manufacturer ID part of the MAC address, that is, the first 3 bytes, only use the last three bytes of the MAC address for mapping, and the last 3 bytes represent the manufacturer's internal hardware number. The number is unique within the manufacturer. Since each device usually needs to occupy multiple MAC addresses consecutively, after the last three bytes of the MAC address are shifted right by N bits in binary, the lower 24 bits are copied into the third segment. Among them, the number of bits shifted to the right is N=log2(M), and M is the displacement number of the MAC address occupied by the device.

Further, an OSPF routing instance of the DCN is created, and then the management loopback interface can be configured to the OSPF routing protocol to enable routing negotiation between network elements;

Wherein, the management loopback interface adopts a 32-bit mask.

Step 102: when it is determined that the status of the Ethernet interface meets the preset condition, an Ethernet sub-interface is created, an IP address routing table of the DCN is generated, and the network element information is configured to the OSPF routing protocol;

Here, the preset condition refers to that the Ethernet interface state is UP;

This step specifically includes: the access network element and the non-access network element respectively periodically detect the Ethernet interface status, and when the Ethernet interface status is UP, create a point-to-point Ethernet sub-interface, and bind the Ethernet sub-interface. The interface is connected to a virtual local area network (VLAN, Virtual Local Area Network), and is configured to the OSPF routing protocol, and the IP address routing table of the DCN is generated according to the OSPF routing protocol, so that the routes between the network elements can be communicated; The IP address of the interface adopts the method of leasing the DCN management address;

The configuration of the network element information to the OSPF routing protocol, so that when the OSPF routing protocol works normally, the extended link state configuration (LSA, Link-State Advertisement) containing the network element information is flooded in the DCN domain, Then, the access network element can obtain the network element information of each network element in the DCN domain in its own OSPF database;

Wherein, the network element information includes: NEID, network element MAC address, network element management IPv4 address, network element equipment manufacturer identification and network element type;

The OSPF routing protocol uses a special type10 Opaque LSA to carry network element 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 network element information in TLV format:

Network element equipment manufacturer identification: type: 0x8000; length: the length of the identification name string;

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.

Further, after configuring the network element information to the OSPF routing protocol, the method further includes: configuring a route between the access network element and the EMS, republishing the route to the OSPF routing protocol, and specifying the EMS side to each network element routing; in this way, the routing between the EMS and the entire PTN network element is opened up;

Wherein, the EMS side includes an EMS and a gateway;

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

Step 103: the EMS parses the information of each network element 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 this 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, and the access network element sends information of each network element 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 of the information of each network element by the access network element to the EMS includes: the access network element actively sends the information of each network element of the entire DCN network to the EMS; or, the access network element receives the network element information request sent by the EMS, Send the network element information of the entire DCN network to the EMS.

Further, this step specifically includes: the EMS parses the information of each network element sent by the access network element, obtains the network element management IP address, network element type, network element MAC address or NEID of each network element, and creates a non-access network element. The corresponding logical network element establishes the connection with the non-access network element according to the standard TCP/IP protocol, that is, establishes the TCP/IP connection with the non-access network element; management.

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

FIG. 3 is a schematic flowchart of a DCN activation method according to Embodiment 2 of the present invention. With reference to FIG. 2 and FIG. 3 , the DCN activation method according to the 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 and run, a DCN VRF instance is automatically created, a management loopback interface loopback 1023 is created, and the management loopback interface is bound to the DCN VPN.

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

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

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

In this embodiment, NEs A to C support the mapping of NEIDs to NE management IP addresses, while NE D and NEE do not support mapping NEIDs to NE management IP addresses; the value of the first byte of the NE management IP allocated by the operator is 131 (decimal). ), the 4 bits of the identifier assigned by the manufacturer to NE A are 0001 (binary), the identifiers assigned to NE B to E are 0002 (binary), and each NE is assigned 8 MAC addresses continuously. The generated NE management IP addresses are:

NE A: Generate 131.17.1.1 according to the NEID;

NE B: Generate 131.33.1.5 according to NEID;

NE C: Generate 131.33.1.4 according to NEID;

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

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

Further, an OSPF routing instance of the DCN is created, and then the management loopback interface can be configured to the OSPF routing protocol to enable routing negotiation between network elements;

Wherein, the management loopback interface adopts a 32-bit mask.

Step 303: Detect the state of the Ethernet interface, and determine whether the state of the Ethernet interface meets the preset condition, and when the preset condition is met, execute step 304; when the preset condition is not met, execute step 303;

Here, the detection of the Ethernet interface state is to periodically detect the Ethernet interface state;

The preset condition means that the state of the Ethernet interface is UP, and the non-compliance with the preset condition means that the state of the Ethernet interface is DOWN.

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

This step specifically includes: the access network element and the non-access network element respectively create a point-to-point Ethernet sub-interface, bind the Ethernet sub-interface to a VLAN and configure it to the OSPF routing protocol, and generate a DCN according to the OSPF routing protocol The IP address routing table, so that the routes between each network element can be communicated; wherein, the IP address of the Ethernet sub-interface adopts the mode of leasing the DCN management address;

In this embodiment, when the state of the Ethernet interface is UP, 4094 point-to-point Ethernet sub-interfaces are automatically created and bound to VLAN 4094. The specific creation is as follows:

Ethernet sub-interfaces gei_1/1.4094 and gei_1/3.4094 are created by default on NE A;

Ethernet sub-interfaces gei_1/3.4094 and gei_1/2.4094 are created by default on NE B;

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

Ethernet sub-interfaces gei_1/1.4094 and gei_1/2.4094 are created by default on NE D;

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

Bind the Ethernet sub-interface created above to DCNVPN and configure it to the OSPF routing protocol, and the access network elements and non-access network elements perform route learning according to the OSPF routing protocol to generate the IP address routing table of the DCN; Routes between NEs can be communicated.

Step 305: configure the network element information to the OSPF routing protocol to perform network-wide flooding 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 containing the network element information is flooded in the DCN domain, Then, the access network element can obtain the network element information of each network element in the DCN domain in its own OSPF database;

Wherein, the network element information includes: NEID, network element MAC address, network element management IPv4 address, network element equipment manufacturer identification and network element type;

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

NE A:

Manufacturer's logo: 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's logo: 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's logo: 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's logo: 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's logo: XXX

NE ID: NE E

NE MAC address: 00d0.d001.3101

NEID: 0.0.0.0

NE management IP: 131.0.38.32

Among them, when the NEID is 0.0.0.0, it means that the device of this type does not support NEID, and the value is invalid.

It should be noted that, the operation sequence of step 305 and step 303-step 304 can be interchanged.

Step 306: Configure the route between the access network element and the EMS, republish 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, the route is republished to the OSPF routing protocol through OSPF route redistribution, and the route from the EMS side to each network element is specified; in this way, the EMS and the entire PTN network are connected. Routing between elements; wherein, the EMS side includes an EMS and a gateway;

In this embodiment, the EMS is in the 10.8.0.0/255.255.0.0 network segment and is not directly connected to the DCN network, so a static route needs to be added; the destination network segment is configured as 10.8.0.0, the mask is 255.255.0.0, and the next hop is 194.194. 194.1 static route, and republish the static route to OSPF routing protocol;

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

EMS: The destination network segment is 131.0.0.0, the mask is 255.0.0.0, and the next hop is the gateway device 10.8.63.144;

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

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 of 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 the information of each network element to the EMS;

This step specifically includes: the access network element actively sends the network element information of the entire DCN network 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. 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;

This step specifically includes: the EMS parses the information of each network element sent by the access network element, obtains the network element management IP address, network element type, network element MAC address or NEID of each network element, and creates logic corresponding to the non-access network element. The network element establishes the connection with the non-access network element according to the standard TCP/IP protocol, that is, establishes the TCP/IP connection with the non-access network element; in this way, the EMS can realize the management of all network elements.

Step 310: End the current processing flow.

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

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

And when it is determined that the status of the Ethernet interface meets the preset conditions, the Ethernet sub-interface is created, the IP address routing table of the DCN is generated, and the network element information is configured to the OSPF routing protocol;

The EMS 43 is used to parse the 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 .

Further, the access network element 41 and the non-access network element 42 are respectively used 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 the service route of the PTN network to avoid mutual interference.

Further, the management address generation rule includes: judging whether the network element supports the mapping of the NEID into the management IP address of the network element, and if so, mapping the NEID to the management IP address of the network element; if not, mapping the MAC address of the network element into the network element management IP address. Meta 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, including: the access network element 41 and the non-access network element 42 respectively determine whether they are Support NEID to generate NE management IP address, if supported, directly map NEID to NE management IP address; if not, map its own MAC address to 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 the management loopback interface can be configured to the OSPF routing protocol to enable routing negotiation between network elements;

Wherein, the management loopback interface adopts a 32-bit mask.

Further, the preset condition refers to that the Ethernet interface state is UP;

The access network element 41 and the non-access network element 42 respectively create Ethernet sub-interfaces, and the generation of the IP address routing table of the DCN includes: the access network element 41 and the non-access network element 42 respectively create a point-to-point Ethernet sub-interface. The network sub-interface, binds the Ethernet sub-interface to VLAN, and is configured to the OSPF routing protocol, and generates the IP address routing table of the DCN according to the OSPF routing protocol; wherein, the IP address of the Ethernet sub-interface adopts the leased DCN the manner in which addresses are 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 containing the network element information is panned in the DCN domain. In this way, the access network element can obtain the network element information of each network element in the DCN domain in its own OSPF database;

Wherein, the network element information includes: NEID, network element MAC address, network element management IPv4 address, network element equipment manufacturer identification and network element type.

Further, the access network element 41 is further configured to configure the route between the access network element and the EMS, and republish the route to the OSPF routing protocol;

Correspondingly, the system further includes a gateway 44;

The EMS43 is also used to specify the route from the EMS43 to the gateway 44;

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

Further, the EMS43 is also used to create a logical network element corresponding to the access network element 41, and establish a TCP/IP connection between the EMS43 and the access network element 41;

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

Further, the EMS43 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, including: EMS43 parsing Access the network element information sent by the network element 41, obtain the network element management IP address, network element type, network element MAC address or NEID of each network element, and create a logical network element corresponding to the non-access network element 42. According to the standard The EMS 43 can realize the management of all network elements by establishing a connection with the non-access network element 42 using the TCP/IP protocol, that is, establishing a TCP/IP connection with the non-access network element 42.

In the embodiment of the present invention, both the access network element 41 and the non-access network element 42 may be PTN devices.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (10)

1. A DCN opening method for a data communication network is characterized by comprising the following steps:

an access network element and a non-access network element respectively generate network element management Internet Protocol (IP) addresses according to preset management address generation rules, the network element management IP addresses are configured to a management loopback interface, an Open Shortest Path First (OSPF) routing instance of a DCN is established, and the management loopback interface is configured to the OSPF routing instance to start routing negotiation between the network elements;

the access network element and the non-access network element respectively establish an Ethernet subinterface when the Ethernet interface state is determined to meet the preset condition, an IP address routing table of the DCN is generated, and the network element information is configured to an OSPF routing protocol so that the OSPF routing protocol works normally;

the EMS analyzes each network element information which is sent by the access network element and is obtained under the condition of starting routing negotiation and normal work of a routing protocol, creates a logic network element corresponding to the non-access network element and establishes connection between the non-access network element and the EMS;

the management address generation rule includes: judging whether the network element supports the mapping of the network element identity NEID to the network element management IP address, if so, mapping the NEID to the network element management IP address; if not, mapping the MAC address of the network element medium access control into a network element management IP address;

the preset conditions include: the ethernet interface state is UP.

2. The method of claim 1, wherein before the access network element and the non-access network element generate the network element management IP addresses according to preset management address generation rules, the method further comprises: the access network element and the non-access network element establish a DCN network management instance and a management loopback interface.

3. The method according to claim 1 or 2, wherein the creating the ethernet subinterface and the generating the IP address routing table of the DCN comprises: creating a point-to-point type Ethernet subinterface, binding the Ethernet subinterface to a Virtual Local Area Network (VLAN), configuring the Ethernet subinterface to an OSPF routing protocol, and generating an IP address routing table of the DCN according to the OSPF routing protocol; and the IP address of the Ethernet subinterface adopts a mode of renting a DCN management address.

4. The method according to claim 1 or 2, wherein after configuring the network element information to the OSPF routing protocol, the method further comprises: configuring a route between an access network element and an Element Management System (EMS), re-issuing the route to an OSPF (open shortest path first) routing protocol, and designating the route from the EMS side to each network element.

5. The method according to claim 1 or 2, wherein before the EMS analyzes information of each network element sent by the access network element and obtained under the condition that the routing negotiation and routing protocol are started to work normally, the method further comprises: and establishing a logic network element corresponding to an access network element, establishing connection between an Element Management System (EMS) and the access network element, and transmitting each network element information to the EMS by the access network element.

6. A DCN provisioning system for a data communication network, said system comprising: an access network element, a non-access network element and an element management system EMS; wherein,

the access network element and the non-access network element are respectively used for generating a network element management IP address according to a preset management address generation rule, configuring the network element management IP address to a management loopback interface, and creating an OSPF routing instance of the DCN, wherein the management loopback interface is configured to the OSPF routing instance to start routing negotiation between the network elements;

the access network element and the non-access network element are respectively used for creating an Ethernet subinterface when the Ethernet interface state is determined to meet the preset condition, generating an IP address routing table of the DCN, and configuring the network element information to an OSPF routing protocol so as to enable the OSPF routing protocol to work normally;

the EMS is used for analyzing each network element information which is sent by the access network element and is obtained under the condition of starting routing negotiation and normal work of a routing protocol, creating a logic network element corresponding to the non-access network element and establishing connection between the non-access network element and the EMS;

the management address generation rule includes: judging whether the network element supports the mapping of the network element identity NEID to the network element management IP address, if so, mapping the NEID to the network element management IP address; if not, mapping the MAC address of the network element medium access control into a network element management IP address;

the preset conditions include: the ethernet interface state is UP.

7. The system of claim 6, 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, respectively.

8. The system according to claim 6 or 7, wherein the access network element and the non-access network element are further configured to create an ethernet subinterface and generate an IP address routing table of the DCN when it is determined that the ethernet interface status meets the preset condition, respectively, and include: the access network element and the non-access network element respectively establish point-to-point type Ethernet subinterfaces, bind the Ethernet subinterfaces to the VLAN, configure the Ethernet subinterfaces to an OSPF routing protocol, and generate an IP address routing table of the DCN according to the OSPF routing protocol; and the IP address of the Ethernet subinterface adopts a mode of renting a DCN management address.

9. The system according to claim 6 or 7, wherein said access network element is further configured to configure a route between the access network element and the EMS, and to reissue said route to the OSPF routing protocol;

correspondingly, the system also comprises a gateway;

the EMS further for specifying a route for the EMS to the gateway;

the gateway is used for appointing the route from the gateway to each network element.

10. The system according to claim 6 or 7, wherein the EMS is further configured to create a logical network element corresponding to an access network element, and establish a connection between the EMS and the access network element;

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

Images