WO2017004995A1

WO2017004995A1 - Method and device for managing routing link state data

Info

Publication number: WO2017004995A1
Application number: PCT/CN2016/074578
Authority: WO
Inventors: 黄彪雄
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-07-03
Filing date: 2016-02-25
Publication date: 2017-01-12
Also published as: CN106330527A; CN106330527B

Abstract

Provided are a method and device for managing routing link state data in the present invention, wherein the method comprises the steps: multiple processes are created on pre-selected network elements, and all of the network elements accessing the pre-selected network elements are divided into multiple regions according to the multiple processes, wherein the multiple regions are corresponding with the multiple processes; the routing link state data in the multiple regions is respectively managed by the pre-selected network elements. Solved is the problem that the management efficiency for the link data in the network system is low in the related art.

Description

Method and device for managing route link state data

Technical field

The present invention relates to the field of communications, and in particular to a method and an apparatus for managing routing link state data.

Background technique

Open Shortest Path First (OSPF) is a routing protocol developed by the Internet Engineering Task Force.

With the increasing scale of the Data Communication Network (DCN) network based on OSPF protocol networking, when routers in a large network run OSPF routing protocols, the number of routers will increase to cause a link state database ( The link state database (LSDB for short) is very large, occupies a large amount of storage space, and increases the complexity of running the SPF algorithm, resulting in a heavy CPU load.

After the network is increased, the probability of the topology change is also increased. The network is often in the "oscillation". As a result, a large number of OSPF packets are transmitted on the network, which reduces the bandwidth utilization of the network. More seriously, every change will cause all routers in the network to re-route calculations.

One solution to the above problem in the related art is to modify the OSPF protocol. When the IPv6 prefix address changes, only the incremental link state advertisement (LSA) is incrementally calculated. The process of recalculating the network topology and the IPv6 prefix routing information in the OSPFv3 area is avoided. This avoids excessive CPU usage of the CPU in the OSPFv3 area and avoids route flapping. However, the drawback of the above solution is that it involves OSPF protocol changes, the workload and risk are relatively large, and there is no isolation effect.

In view of the related problems in the related art that the link data management in the network system is inefficient and risky, an effective solution has not been proposed yet.

Summary of the invention

The embodiment of the invention provides a method and a device for managing routing link state data, so as to at least solve the problem that the link data management efficiency in the network system is low in the related art.

According to an aspect of the embodiments of the present invention, a method for managing routing link state data is provided, including: creating a plurality of processes on a preselected network element, and accessing the preselection according to the multiple processes. All the network elements of the network element are divided into a plurality of areas, wherein the plurality of areas are in one-to-one correspondence with the plurality of processes; and the pre-selected network elements respectively are used to route links in the plurality of areas Status data is managed.

Optionally, the multiple processes are created on the pre-selected network element, and all the network elements that access the pre-selected network element are divided into the multiple areas according to the multiple processes: Creating the plurality of the pre-selected network elements Configuring a corresponding process identifier for each of the plurality of processes, and dividing all network elements belonging to the same process from all the network elements according to the process identifier For the same area.

Optionally, when the pre-selected network element is an access network element that directly accesses the network management, all the networks belonging to the same process in all the network elements are all from the all network elements according to the process identifier. The dividing into the same area includes: assigning the interface identifier directly connected to the network management to the multiple processes; and adopting a preset algorithm and the interface identifier to establish separately by each of the multiple processes a route between the network elements of the process and the network management system; configuring the mapping between the interface identifiers of the network elements belonging to each process and the process, and dividing the network elements belonging to the same process into the same An area.

Optionally, the allocating the interface identifier that directly accesses the network management to the multiple processes includes: selecting one of the multiple processes, and setting the interface identifier directly connected to the network management And being configured to be sent to the selected process; the interface identifier directly connected to the network management device is distributed to the remaining processes of the plurality of processes that are not selected by the selected process.

Optionally, when the pre-selected network element is not an access network element that directly accesses the network management, all the all network elements belong to the same process from all the network elements according to the process identifier. The division of the network element into the same area includes: configuring a correspondence between each process of the multiple processes and one or more interfaces of the pre-selected network element; corresponding to each process according to the correspondence The network element to which the interface is connected is divided into the same area, where the area includes at least one access network element directly connected to the network management.

According to another aspect of the present invention, a device for managing link state data is provided, including: a dividing module, configured to create a plurality of processes on a preselected network element, and according to the multiple processes All the network elements that access the pre-selected network element are divided into multiple areas, wherein the multiple areas are in one-to-one correspondence with the multiple processes; and the management module is configured to separately use the pre-selected network elements. Routing link state data in the plurality of areas is managed.

Optionally, the dividing module includes: a configuration unit, configured to create the multiple processes on the pre-selected network element, and configure corresponding process identifiers for each of the multiple processes; The dividing unit is configured to divide all network elements belonging to the same process in all the network elements into the same area from all the network elements according to the process identifier.

Optionally, when the pre-selected network element is an access network element that directly accesses the network management, the dividing unit includes: an allocation sub-unit, configured to allocate the interface identifier directly connected to the network management to a plurality of processes; establishing a sub-unit, configured to use a preset algorithm and the interface identifier to establish, by each of the multiple processes, a route between each network element belonging to the process and the network management The first sub-unit is configured to configure a correspondence between the interface identifier of each network element belonging to each process and the process, and divide the network elements belonging to the same process into the same area.

Optionally, the allocating subunit is further configured to: select one of the multiple processes, and configure the interface identifier directly connected to the network management to the selected process; The selected process distributes the interface identifier directly connected to the network management to the remaining processes that are not selected among the multiple processes.

Optionally, when the pre-selected network element is not an access network element directly accessing the network management, the dividing unit includes: a sub-unit, configured to configure a correspondence between each process of the plurality of processes and one or more interfaces of the pre-selected network element; the second sub-unit is configured to be according to the correspondence The network element that is connected to the interface corresponding to each process is divided into the same area, where the area includes at least one access network element directly connected to the network management.

According to the embodiment of the present invention, a plurality of processes are created on a pre-selected network element, and all network elements accessing the pre-selected network element are divided into multiple areas according to the multiple processes, where the The plurality of regions are in one-to-one correspondence with the plurality of processes, such that the entire network system is divided into a plurality of independent regions bordered by the preselected network management, and finally the plurality of the plurality of regions are respectively selected by the preselected network elements. The routing link state data in the area is managed, which solves the problem that the link data management efficiency in the network system is low in the related art, thereby achieving the effect of reducing the bandwidth utilization and CPU load of the network.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a flowchart of a method for managing routing link state data according to an embodiment of the present invention;

2 is a structural block diagram of a device for managing link state data according to an embodiment of the present invention;

3 is a block diagram 1 of an optional structure of a device for managing link state data according to an embodiment of the present invention;

4 is a block diagram 2 of an optional structure of a device for managing link state data according to an embodiment of the present invention;

5 is a block diagram 3 of an optional structure of a device for managing link state data according to an embodiment of the present invention;

6 is a schematic diagram of an access network element OSPF multi-process according to an optional embodiment of the present invention;

FIG. 7 is a schematic diagram of a non-access network element OSPF multi-process according to an alternative embodiment of the present invention.

detailed description

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It should be noted that the terms "first", "second" and the like in the specification and claims of the embodiments of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. order.

In this embodiment, a method for managing routing link state data is provided. FIG. 1 is a flowchart of a method for managing routing link state data according to an embodiment of the present invention. As shown in FIG. 1, the process includes the following steps:

Step S102: Create a plurality of processes on the pre-selected network element, and divide all network elements that access the pre-selected network element into multiple areas according to the multiple processes, where the multiple areas and the multiple Process one-to-one correspondence;

In a data communication network system, a routing device is used. Optionally, the routing device is based on a protocol including: In the present embodiment, the information protocol, the intermediate system to the intermediate system protocol, the border network management protocol, the open shortest path first OSPF protocol, etc., are described by the open shortest path first protocol, but it should be noted that the routing device based on other protocols and The network system can also implement this solution, solve the same technical problems, and achieve the same end effect. Optionally, multiple processes are multiple OSPF processes, for example, OSPF1, OSPF2, and OSPF3. In the network system, multiple network elements and network management systems exist. The network management system can manage the network elements of the entire network system and is responsible for the upper layer. The device exchanges information. The network system where the pre-selected NEs are located is divided into three areas according to the created process OSPF1, OSPF2, and OSPF3. OSPF1 corresponds to the first area, OSPF2 corresponds to the second area, and OSPF3 and the third area. The area corresponds.

Step S104, managing routing link state data in the plurality of areas by using the pre-selected network elements.

Optionally, three pre-selected NEs run OSPF1, OSPF2, and OSPF3, and respectively correspond to the three divided areas. The pre-selected NEs are corresponding to the three processes: OSPF1, OSPF2, and OSPF3. The three areas are managed, and the routing link state data includes link information between the network element devices and routing information on the network element device.

According to the embodiment of the present invention, a plurality of processes are created on a pre-selected network element, and all network elements that access the pre-selected network element are divided into multiple areas according to the multiple processes, where the multiple areas are Corresponding to the above multiple processes, the entire network system is divided into a plurality of independent areas bordered by pre-selected network tubes, and finally the routing links in the plurality of areas are respectively separated by the pre-selected network elements. The state data is managed to solve the problem of low efficiency of link data management in the network system in the related art, thereby achieving the effect of reducing the bandwidth utilization and CPU load of the network.

In an optional implementation manner of the embodiment of the present invention, the foregoing multiple processes are created on the pre-selected network element, and all network elements that access the pre-selected network element are divided into the foregoing multiple according to the multiple processes. The areas include the following steps:

S11. The multiple processes are created on the pre-selected network element, and the corresponding process identifier is configured for each of the multiple processes.

Optionally, the process identifier may be a router identifier on the network element, and the router identifier is assigned to the corresponding OSPF according to the identifier of the router identifier or the priority of the OSPF1, OSPF2, and OSPF3.

S12. All the network elements belonging to the same process in all the foregoing network elements are divided into the same area from all the foregoing network elements according to the process identifier.

Optionally, the network element device running the same process is identified according to the router identifier configured in the process, because the process and the router identifier are unique and one-to-one correspondence, so that the entire network system selects the same one of the network element links in advance. The NE device will only run one process and only one router ID will exist.

According to the foregoing optional embodiment, when the pre-selected network element is the access network element directly accessing the network management, all the networks belonging to the same process in all the network elements are removed from all the network elements according to the process identifier. Dividing the element into the same area includes the following steps:

S21, the interface identifier directly connected to the network management device is allocated to the multiple processes.

Optionally, in this embodiment, the network element that directly accesses the network management device is the access network element, and the network element that accesses the network management device through other network elements is the non-access network element.

S22: The route between each network element belonging to the process and the network management device is established by using each of the multiple processes in the foregoing process by using a preset algorithm and the foregoing interface identifier.

Optionally, the access network element can directly communicate with the network management device through the port. For the non-access network element, the non-access network element can access the network element by configuring a static route and configuring a preset algorithm such as a stub area. The network management communicates.

S23. Configure a mapping between the interface identifier of each network element that belongs to each process and the process, and divide the network elements that belong to the same process into the same area.

Optionally, in an optional implementation manner of the embodiment of the present invention, the assigning the interface identifier directly connected to the network management to the multiple processes includes the following steps:

S31: Select one of the multiple processes, and configure the interface identifier directly connected to the network management device to the selected process.

Optionally, one of the multiple processes created may be selected as the primary process, the other is the secondary process, or a priority is set between multiple processes, and the other process is managed and configured by the primary process or a process with a higher priority. This can further save network resources.

S32. The interface identifier directly connected to the network management device is distributed to the remaining processes that are not selected among the multiple processes by using the selected process.

After one of the multiple processes is selected as the primary process, the interface ID corresponding to the primary process is distributed to the remaining processes. If OSPF1 is selected as the primary process, the interface ID corresponding to OSPF1 is distributed to OSPF2 and OSPF3.

Optionally, according to the foregoing optional embodiment, when the pre-selected network element is not the access network element directly accessing the network management, the foregoing all the network elements are attributed to all the network elements according to the process identifier. All network elements in the same process are divided into the same area, including the following steps:

S41. Configure a correspondence between each process of the foregoing multiple processes and one or more interfaces of the foregoing preselected network element.

S42. The network element that is connected to the interface corresponding to each process is divided into the same area according to the foregoing correspondence, where the area includes at least one access network element directly connected to the network management.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium (such as ROM/RAM, disk). , CD), including a number of instructions to make a terminal device (can be a mobile phone, computer, service The foregoing method of the embodiments of the present invention is executed by a server, or a network device.

In this embodiment, a device for managing the link state data is provided. The device is used to implement the foregoing embodiments and the preferred embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

2 is a structural block diagram of a device for managing link state data according to an embodiment of the present invention. As shown in FIG. 2, the device includes: a partitioning module 20 and a management module 22, as follows:

The dividing module 20 is configured to create a plurality of processes on the preselected network element, and divide all network elements that access the preselected network element into multiple areas according to the multiple processes, where the multiple areas are One-to-one correspondence of the above multiple processes;

In the data communication network system, a routing device is used, and the protocol based on the routing device includes: a routing information protocol, an intermediate system to an intermediate system protocol, a border network management protocol, an open shortest path first OSPF protocol, etc., in this embodiment. The description is based on the open shortest path priority protocol. However, it should be noted that the routing device and the network system based on other protocols can also implement the solution, solve the same technical problem, and achieve the same end effect. Optionally, multiple processes are multiple OSPF processes, such as OSPF1, OSPF2, and OSPF3. In the network system, multiple NEs and network management systems exist. The network management system can manage the network elements of the entire network system and is responsible for the upper-layer devices. For the information exchange, the partitioning module 20 divides the network system where the preselected network element is located into three areas according to the created process OSPF1, OSPF2, and OSPF3, where OSPF1 corresponds to the first area, OSPF2 corresponds to the second area, and OSPF3 and The third area corresponds.

The management module 22 is coupled to the partitioning module 20 and configured to manage routing link state data in the plurality of regions by using the preselected network elements.

FIG. 3 is a block diagram of an optional structure of a device for managing link state data according to an embodiment of the present invention. As shown in FIG. 3, the device includes: all the modules shown in FIG. The unit 30 and the dividing unit 32 are as follows:

The configuration unit 30 is configured to create the foregoing multiple processes on the pre-selected network elements, and configure corresponding process identifiers for each of the multiple processes.

The dividing unit 32 is coupled to the configuration unit 30, and is configured to divide all network elements belonging to the same process among all the network elements into the same area from all the network elements according to the process identifier.

Optionally, the network element device running the same process is identified according to the router identifier configured in the process, because the process and The router IDs are unique and one-to-one correspondence. In this way, the same network element device that selects the NE link in the entire network system only runs one process, and only one router identifier exists.

4 is a block diagram 2 of an optional structure of a device for managing link state data according to an embodiment of the present invention. As shown in FIG. 4, the device includes, in addition to all the modules shown in FIG. The subunit 40, the establishing subunit 42, and the first dividing subunit 44 are as follows:

The allocation sub-unit 40 is configured to allocate the interface identifier directly connected to the network management to the plurality of processes when the pre-selected network element is the access network element directly accessing the network management;

The establishing sub-unit 42 is coupled to the distribution sub-unit 40, and is configured to establish, by using a preset algorithm and the foregoing interface identifier, a route between each network element belonging to the process and the network management system by using each of the multiple processes. ;

The first dividing sub-unit 44 is coupled to the establishing sub-unit 42 and configured to configure the correspondence between the interface identifier of each network element belonging to each process and the process, and divide the network elements belonging to the same process into the same An area.

In an optional implementation manner of the present embodiment, the foregoing allocation sub-unit is further configured to: select one of the plurality of processes, and configure the interface identifier directly connected to the network management device to the selected process; The interface identifier directly connected to the network management system is distributed to the remaining processes that are not selected among the plurality of processes by using the selected process.

Among them, one of the multiple processes created may be selected as the primary process, the other is the secondary process, or a priority is set between multiple processes, and the other process is managed and configured by the primary process or a process with a higher priority. Further saving network resources. After one of the multiple processes is selected as the primary process, the interface ID corresponding to the primary process is distributed to the remaining processes. If OSPF1 is selected as the primary process, the interface ID corresponding to OSPF1 is distributed to OSPF2 and OSPF3.

5 is a block diagram 3 of an optional structure of a device for managing link state data according to an embodiment of the present invention. As shown in FIG. 5, the device includes, in addition to all the modules shown in FIG. The subunit 50 and the second subunit 52 are as follows:

The configuration sub-unit 50 is configured to configure, when the pre-selected network element is not an access network element directly accessing the network management, configure one or more interfaces of each process of the foregoing multiple processes and the pre-selected network element. Correspondence between

The second sub-unit 52 is coupled to the configuration sub-unit 50, and is configured to divide the network element accessed by the interface corresponding to each process into the same area according to the foregoing correspondence, where at least one of the foregoing areas is included The access NE connected directly to the NMS.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple At In the processor.

The embodiment is described in detail below with reference to an optional embodiment of the embodiment. This embodiment provides an embodiment in which an OSPF multi-process is used. In this embodiment, the autonomous system can be divided into different areas according to the OSPF protocol. A zone logically divides routers into different groups, each group being identified by an area ID. The boundaries of a zone are routers, not links. A router can belong to different areas, but a network segment (link) can only belong to one area, or each interface running OSPF must indicate which area it belongs to. After the area is divided, the route aggregation can be performed on the area border router to reduce the number of LSAs advertised to other areas. The impact of network topology changes can also be minimized.

This embodiment includes two alternative embodiments, as follows:

Optional implementation 1, accessing the network element OSPF multi-process, the scheme is configured to configure OSPF multi-process in the access network element, each process assigns an independent router identifier router id., and specifies each port to a specific OSPF process. Therefore, the DCN network is divided into different areas to isolate the DCN network.

Option 2, the network management system supports the OSPF multi-process by using the non-access NEs of different access network elements. The OSPF multi-process is configured on the non-access NEs, and multiple access NEs need to be connected differently. region.

FIG. 6 is a schematic diagram of an access network element OSPF multi-process according to an alternative embodiment of the present invention. As shown in FIG. 6, in an optional implementation 1, network element A is an access network element, and the rest are non-access network elements. On the network element A, two independent IP ring networks are connected, as follows:

S61: Create different OSPF instances on NE A: OSPF1, OSPF2.

S62. Configure, on the network element A, the interface connected to the network management system as a passive interface to the OSPF1 instance.

S63: Configure routing mutual-prevention on the network element A, so that the OSPF2 process learns the QX interface route.

S64, in the OSPF process on the network element A, configure a static route, a stub area, and the like, so that the non-access network element learns the route that reaches the network management.

S65. On the network element A, configure the interface connecting the D and E network elements to OSPF1, and configure the interface connecting the B and C network elements to OSPF2.

FIG. 7 is a schematic diagram of a non-access network element OSPF multi-process according to an alternative embodiment of the present invention. As shown in FIG. 7, in an alternative embodiment 2, A and B are access network elements, B, C, and D. For a non-access NE, the NMS manages the non-access NE through different access NEs to support OSPF multi-process. The NMS manages the network element ABCDE five NEs, as follows:

On S71, the OSPF multi-process is enabled on the D network and OSPF1 and OSPF2 are created.

On S72, on interface NE, configure

interfaces

1 and 2 to instance OSPF2, and interface 3 and interface 4 to OSPF1.

Through this embodiment, the technical problem of network "oscillation" is solved by isolating the data communication network DCN network.

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

S1. Create multiple processes on the pre-selected network element, and divide all network elements that access the pre-selected network element into multiple areas according to the multiple processes, where the multiple areas and the multiple processes are One-to-one correspondence;

S2: Manage routing link state data in the multiple areas by using the pre-selected network elements.

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

The present invention relates to the field of communications, and provides a method and an apparatus for managing routing link state data, where the method includes: creating multiple processes on a pre-selected network element, and accessing the access according to the multiple processes. All the network elements of the pre-selected network element are divided into a plurality of areas, wherein the plurality of areas are in one-to-one correspondence with the plurality of processes; and the pre-selected network elements are respectively used in the plurality of areas. The routing link state data is managed, and the problem of low efficiency of link data management in the network system in the related art is solved.

Claims

A method for managing routing link state data includes:

Deleting a plurality of processes on the pre-selected network element, and dividing, according to the multiple processes, all the network elements that access the pre-selected network element into multiple areas, where the multiple areas and the multiple One-to-one correspondence;

Routing link state data in the plurality of areas is managed by the pre-selected network elements.
The method of claim 1, wherein the plurality of processes are created on the pre-selected network element, and all network elements accessing the pre-selected network element are divided into The plurality of regions includes:

Creating the multiple processes on the pre-selected network element, and configuring corresponding process identifiers for each of the multiple processes;

All network elements belonging to the same process in all the network elements are divided into the same area from all the network elements according to the process identifier.
The method according to claim 2, wherein when the pre-selected network element is an access network element directly accessing the network management, all the network elements are selected from all the network elements according to the process identifier. All network elements that belong to the same process are divided into the same area, including:

Allocating the interface identifier directly connected to the network management to the multiple processes;

Determining, by using a preset algorithm and the interface identifier, a route between each network element belonging to the process and the network management by using each of the multiple processes;

The mapping between the interface identifier of each network element that belongs to each process and the process is configured, and the network elements that belong to the same process are divided into the same area.
The method according to claim 3, wherein the assigning the interface identifier directly connected to the network management to the plurality of processes comprises:

Selecting one of the plurality of processes, and configuring the interface identifier directly connected to the network management to the selected process;

And distributing, by the selected process, an interface identifier that directly accesses the network management to the remaining processes that are not selected among the multiple processes.
The method according to claim 2, wherein when the pre-selected network element is not an access network element directly accessing the network management, all the network elements are all from the all network elements according to the process identifier. All network elements belonging to the same process are divided into the same area including:

And configuring a correspondence between each process of the multiple processes and one or more interfaces of the pre-selected network element;

The network element that is connected to the interface corresponding to each process is divided into the same area according to the corresponding relationship, where the area includes at least one access network element directly connected to the network management.
A management device for routing link state data, comprising:

The dividing module is configured to create a plurality of processes on the preselected network element, and divide all network elements that access the preselected network element into multiple areas according to the multiple processes, where the multiple The area is in one-to-one correspondence with the plurality of processes;

The management module is configured to manage routing link state data in the multiple areas by using the preselected network element.
The apparatus of claim 6 wherein said dividing module comprises:

a configuration unit, configured to create the multiple processes on the pre-selected network element, and configure corresponding process identifiers for each of the multiple processes;

The dividing unit is configured to divide all network elements belonging to the same process in all the network elements into the same area from all the network elements according to the process identifier.
The apparatus of claim 7, wherein the dividing unit comprises:

An allocation subunit, configured to allocate the interface identifier directly connected to the network management to the multiple processes when the preselected network element is an access network element that directly accesses the network management;

Establishing a sub-unit, configured to use a preset algorithm and the interface identifier to establish, by each of the multiple processes, a route between each network element belonging to the process and the network management system;

The first sub-unit is configured to configure a correspondence between the interface identifier of each network element belonging to each process and the process, and divide the network elements belonging to the same process into the same area.
The apparatus of claim 8 wherein said assigning subunit is further configured to:

Selecting one of the plurality of processes, and configuring the interface identifier directly connected to the network management to the selected process;

And distributing, by the selected process, an interface identifier that directly accesses the network management to the remaining processes that are not selected among the multiple processes.
The apparatus according to claim 7, wherein the dividing unit comprises:

Configuring a sub-unit, configured to configure each process of the multiple processes and one or more of the pre-selected network elements when the pre-selected network element is not an access network element directly accessing the network management Correspondence between interfaces;

The second sub-unit is configured to divide the network element accessed by the interface corresponding to each process into the same area according to the corresponding relationship, where the area includes at least one access directly connected to the network management Network element.