WO2012155430A1

WO2012155430A1 - Method and network management for calculating network element interfaces

Info

Publication number: WO2012155430A1
Application number: PCT/CN2011/080054
Authority: WO
Inventors: 孙凯意; 张伟
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-05-19
Filing date: 2011-09-22
Publication date: 2012-11-22
Also published as: CN102790692B; CN102790692A

Abstract

Disclosed in the present invention are a method and network management for calculating network element interfaces, wherein the method comprises obtaining an opposite network element physically connected to a local network element via a topological link; respectively establishing a first Virtual Local Area Network (VLAN) interface set and a first Internet Protocol (IP) interface set of the local network element, a second VLAN interface set and a second IP interface set of the opposite network element; based on the first VLAN interface set, the first IP interface set, the second VLAN interface set and the second IP interface set, calculating the matched VLAN interfaces and matched IP interfaces between the local network element and the opposite network element. The present invention avoids the problems that manual configuration is extremely error prone and disconnected services caused by IP collision or mismatched VLAN and IP, thus ensuring the configuration accuracy and improving the configuration efficiency.

Description

Method and network management method for computing network element interface

The present invention relates to the field of network technologies for supporting Layer 3 switching, and in particular, to the automatic calculation of the Layer 2 and Layer 3 interfaces of the network element by the network management, and is specifically a method and network management method for computing the network element interface. Background technique

A virtual local area network (VLAN) is a technology that divides a physical network into multiple logical (virtual) local area networks (LANs). With VLAN technology, network administrators can divide user logic in the same physical LAN into different broadcast domains (each broadcast domain is a VLAN) according to actual application requirements. Each VLAN is logically a separate LAN with the same attributes as a physically formed LAN. All broadcast and unicast traffic in the same VLAN is restricted to this VLAN and not forwarded to other VLANs. When NEs of different VLANs want to communicate, they must pass through Layer 3 routing. When a port is assigned to a VLAN based on a network element, each port of the network element can be assigned to a different VLAN, which involves a Layer 2 interface and a Layer 3 interface. The Layer 2 interface refers to the VLAN interface. The Layer 3 interface refers to the Internet interconnection protocol. (IP, Internet Protocol) interface.

Layer 3 interfaces are created based on VLANs. On a Layer 3 switching network, you need to ensure that the two physical interfaces of the two NEs that are physically connected must be in the same VLAN and the IP address of the Layer 3 interface where the VLAN resides. Must be in the same network segment. As shown in Figure 1, network element A is connected to network element B. Port 1 is the UNI port of network element A, port 4 is the UNI port of network element B, and port 2 is the NNI side port of network element A. Port 3 serves as the NNI side port of network element B, and port 2 and port 3 are physically connected by a fiber link. To ensure that services are transmitted between port 1 and port 4, you need to divide port 2 and port 3 into the same VLAN interface, and the Layer 3 interface to which the VLAN interface belongs. The IP address of the port is on the same network segment.

The existing NE interface configuration mode requires the operator to manually configure the VLAN interface and IP interface for the NEs on the network. However, when the network is large, it is easy to configure errors, causing IP conflicts or VLANs and IPs that do not match, resulting in poor communication, which reduces configuration efficiency. Summary of the invention

The main purpose of the present invention is to provide a method and network management method for computing a network element interface, which aims to improve configuration accuracy and configuration efficiency.

In order to achieve the above object, the present invention provides a method for computing a network element interface, where the method includes:

Obtaining a peer network element that has a physical connection with the local network element by using the topology connection;

Establishing a first VLAN interface set, a first IP interface set, and a second VLAN interface set and a second IP interface set of the peer network element respectively.

The matching VLAN interface and the matching IP interface of the local network element and the opposite network element are calculated based on the first VLAN interface set, the first IP interface set, the second VLAN interface set, and the second IP interface set.

Preferably, the calculating, by the first VLAN interface set, the first IP interface set, the second VLAN interface set, and the second IP interface set, the matching VLAN interface and the matching IP interface of the local network element and the peer network element, Includes:

Calculating a matching VLAN interface between the local network element and the remote network element based on the first VLAN interface set and the second VLAN interface set;

The matching IP interface between the local network element and the remote network element is calculated based on the matched VLAN interface, the first IP interface set, and the second IP interface set.

Preferably, the calculating, by the first VLAN interface set and the second VLAN interface set, the matching VLAN interface between the local network element and the remote network element, including: Querying the first VLAN interface set and the second VLAN interface set respectively; if one of the first VLAN interface set and the second VLAN interface set is an empty set, the VLAN interface set that is not an empty set is used as the local end A matching VLAN interface between the NE and the peer NE;

If the first VLAN interface set and the second VLAN interface set are both empty and have a VLAN interface intersection, the VLAN interface intersection is used as a matching VLAN interface between the local network element and the remote network element;

Otherwise, a new VLAN interface is assigned as the matching VLAN interface between the local NE and the peer NE.

Preferably, the principle of determining the intersection of the VLAN interfaces is as follows: The VLAN IDs of the VLAN interfaces are the same; the VLAN interface is allocated as follows: The VLAN IDs are unique and equal within the network element.

Preferably, the matching IP interface between the local network element and the remote network element is calculated based on the matching VLAN interface, the first IP interface set, and the second IP interface set, and includes:

Querying, in the first IP interface set and the second IP interface set, the same IP interface as the matching VLAN interface ID;

If the first IP interface set and the second IP interface set are empty sets, and the IP interfaces in the IP interface set that are not empty sets are not used on the corresponding network element, the network corresponding to the empty set is An IP interface that is in the same network segment as the IP interface address of the IP interface set that is not an empty set and that is unique to the entire network, and the IP interface set that is not an empty set and the assigned IP interface are used as the local network element. a matching IP interface corresponding to the peer network element;

If the first IP interface set and the second IP interface set are not empty sets, and at least one pair of IP interfaces have IP addresses in the same network segment, the at least one pair of IP interfaces is used as the local network element and The matching IP interface corresponding to the peer network element;

Otherwise, an IP interface that is unique to the entire network and whose IP address is on the same network segment is assigned as the matching IP interface corresponding to the local NE and the peer NE. Preferably, before the obtaining, by the topology connection, the peer network element that has a physical connection with the local network element, the method further includes:

The local network element is used as the query condition, and the topology connection is obtained by querying the database. If the topology connection is empty, the user is prompted to establish a physical connection between the local network element and the remote network element.

The invention also provides a network management system for calculating a network element interface, where the network management system includes:

An obtaining module, configured to obtain, by using a topology connection, a peer network element that has a physical connection with the local network element;

Establishing a module, configured to respectively establish a first VLAN interface set of the local network element, a first IP interface set, and a second VLAN interface set and a second IP interface set of the peer network element;

a calculation module, configured to calculate, according to the first VLAN interface set, the first IP interface set, the second VLAN interface set, and the second IP interface set, the matching VLAN interface and the matching IP address of the local network element and the peer network element interface.

Preferably, the calculation module comprises:

a VLAN interface calculation unit, configured to calculate a matching VLAN interface between the local network element and the remote network element based on the first VLAN interface set and the second VLAN interface set;

The IP interface calculation unit is configured to calculate a matching IP interface between the local network element and the remote network element based on the matched VLAN interface, the first IP interface set, and the second IP interface set.

Preferably, the VLAN interface calculation unit includes:

a first query subunit, configured to respectively query the first VLAN interface set and the second

VLAN interface set;

a first computing subunit, configured to: when the one of the first VLAN interface set and the second VLAN interface set is an empty set, the VLAN interface set that is not an empty set is used as the local network element and the peer network element. Matching the VLAN interface; when the first VLAN interface set and the second VLAN interface set are both empty sets and there is a VLAN interface intersection, the VLAN interface intersection is used as the local The matching VLAN interface between the end network element and the peer network element; otherwise, a new VLAN interface is assigned as the matching VLAN interface between the local network element and the remote network element.

Preferably, the IP interface calculation unit includes:

a second query subunit, configured to query, in the first IP interface set and the second IP interface set, an IP interface that is the same as the ID of the matching VLAN interface;

a second calculating subunit, configured to: when one of the first IP interface set and the second IP interface set is an empty set, and the IP interface in the IP interface set that is not an empty set is not used on the corresponding network element Assigning, to the network element corresponding to the empty set, an IP interface that is in the same network segment as the IP interface address in the IP interface set that is not an empty set and is unique to the entire network, and is not an empty set IP interface set and allocated. The IP interface is the matching IP interface corresponding to the local network element and the peer network element; when the first IP interface set and the second IP interface set are not empty sets, and at least one pair of IP interfaces have the same IP address. In the network segment, the at least one IP interface is used as the matching IP interface between the local network element and the ^ end network element; otherwise, an IP interface with a unique network and the IP address in the same network segment is allocated as the local end. The matching IP interface corresponding to the NE and the peer NE.

Preferably, the network management further includes:

The query obtaining module is configured to obtain the topology connection by querying the database by using the local network element as a query condition.

The prompting module is configured to prompt the user to establish a physical connection between the local network element and the remote network element when the topology connection is empty.

The method for calculating a network element interface and the network management provided by the present invention automatically establish a VLAN interface set and an IP interface set of the local network element and the opposite network element respectively, and then automatically calculate according to the established VLAN interface set and the IP interface set. The matching VLAN interface and the IP interface required for the local NE and the peer NE to transmit data. When the network is large, the manual configuration is highly error-prone, IP conflicts, or services such as VLANs and IPs do not match. The accuracy of the configuration improves the efficiency of the configuration. DRAWINGS

1 is a schematic diagram of a conventional network element connection;

2 is a schematic flow chart of a method for computing a network element interface according to an embodiment of the present invention;

3 is a method for computing a network element interface according to an embodiment of the present invention. The local network element and the peer network element are calculated based on the first VLAN interface set, the first IP interface set, the second VLAN interface set, and the second IP interface set. Schematic diagram of matching the VLAN interface and the matching IP interface;

4 is a schematic flowchart of calculating a matching VLAN interface between a local network element and a remote network element based on a first VLAN interface set and a second VLAN interface set in the method for calculating a network element interface according to an embodiment of the present invention;

5 is a schematic flowchart of calculating a matching IP interface between a local network element and a remote network element based on a matched VLAN interface, a first IP interface set, and a second IP interface set in the method for calculating a network element interface according to an embodiment of the present invention;

6 is a schematic flowchart of another embodiment of a method for computing a network element interface according to the present invention; FIG. 7 is a schematic diagram of a connection between network elements in a three-layer switching network in another embodiment of a method for computing a network element interface according to the present invention;

8 is a schematic structural diagram of an embodiment of a network management system for computing a network element interface according to the present invention;

9 is a schematic structural diagram of a computing module in an embodiment of a network management system for computing a network element interface according to the present invention; FIG. 10 is a schematic structural diagram of a VLAN interface computing unit in an embodiment of a network management system for computing a network element interface according to the present invention;

11 is a schematic structural diagram of an IP interface calculation unit in an embodiment of a network management system for computing a network element interface according to the present invention;

FIG. 12 is a schematic structural diagram of another embodiment of a network management system for computing a network element interface according to the present invention.

In order to make the technical solutions of the present invention clearer and clearer, the following will be further reviewed in conjunction with the accompanying drawings. detailed description

The solution of the embodiment of the present invention is mainly: establishing the local network element and the peer network element respectively

The VLAN interface set and the IP interface set automatically calculate the matching VLAN interface and IP interface required for the local NE and the peer NE to transmit data according to the established VLAN interface set and the IP interface set, so as to improve the accuracy and efficiency of the configuration.

As shown in FIG. 2, an embodiment of the present invention provides a method for computing a network element interface, including: Step S101: Obtain a peer network element that has a physical connection with a local network element by using a topology connection; The NMS needs to synchronize the NE data to determine whether there is a physical connection between the local NE and the peer NE. If there is no physical connection, the user is prompted to establish a physical connection or LLDP (Link Layer Discovery Protocol) link auto discovery.

In this embodiment, the local network element and the peer network element have established corresponding physical connections. At the same time, all the peer NEs that establish physical connections with the local NE are obtained through the topology connection.

Step S102: Establish a first VLAN interface set, a first IP interface set, and a second VLAN interface set and a second IP interface set of the peer network element, respectively.

The network management query aggregates all VLAN interfaces and all IP interfaces of the physical port of the interface that need to be configured with the local NE. The VLAN set 1 and IP set 1 are formed, that is, the first VLAN interface set and the first IP interface set of the local NE are established. At the same time, query all the VLAN interfaces and all IP interfaces of the physical port that need to be configured with the peer NE to form the VLAN set 2 and form the IP set 2, that is, establish the second VLAN interface set and the second IP of the peer network element. Interface collection. Therefore, the matching VLAN interface and the matching IP interface between the local network element and the opposite network element are calculated according to the foregoing sets.

Step S103: Calculate a matching VLAN interface and a matching IP interface between the local network element and the opposite network element based on the first VLAN interface set, the first IP interface set, the second VLAN interface set, and the second IP interface set. In this step, the matching VLAN interface between the local network element and the remote network element is calculated according to the first VLAN interface set and the second VLAN interface set, and then the first IP interface set is calculated and combined according to the calculated matching VLAN interface. The second IP interface set calculates a matching IP interface between the local network element and the peer network element.

Specifically includes the following process:

1. Calculate the VLAN interface and determine the calculation result of the VLAN interface of the local NE (that is, the matching VLAN interface of the local NE) and the VLAN interface calculation result of the peer NE (that is, the matching VLAN interface of the peer NE).

If the element in the VLAN set 1 is empty, and the element in the VLAN set 2 is not empty, the VLAN of the VLAN set 2 is used as the standard, and the same VLAN interface is assigned to the local network element as the VLAN interface of the local network element. The result of the calculation is 1, and the newly added VLAN interface is identified in the VLAN interface calculation result 1. VLAN set 2 is used as the VLAN interface calculation result of the peer NE. Otherwise the same treatment;

2. If there is an intersection between VLAN Set 1 and VLAN Set 2, calculate the intersection of the two. The principle of the intersection is that the VLAN IDs of the VLAN interfaces are the same. Record the intersection of VLAN interfaces as the match between the local NE and the peer NE. The calculation result of the VLAN interface;

3. If there is no intersection between VLAN set 1 and VLAN set 2, a new VLAN interface is assigned to the two NEs as the matching result of the matching VLAN interface between the local NE and the peer NE, and in the calculation result. The VLAN interface is added. The above-mentioned allocation principle is that the VLAN ID is unique within the NE and is equal.

2. Calculate the IP interface and determine the matching IP interface between the local NE and the peer NE.

1. In IP set 1, look up the IP interface corresponding to the calculation result 1 of the local network element VLAN interface. The search principle is that the ID of the IP interface is equal to the VLAN ID in the calculation result 1 of the local network element VLAN interface. If it exists, record it. Correspondence between the VLAN ID and the IP interface. If it does not exist, the mapping between the VLAN ID and the null value is recorded. 2. The IP set 2 and the VLAN interface are calculated in the same step D1 to generate a corresponding relationship 2;

3. Traverse the corresponding relationship 1 and the corresponding relationship 2, and compare the IP interfaces corresponding to the same VLAN ID. If all the IP interfaces corresponding to the VLAN IDs exist, and the IP addresses of at least one pair of IP interfaces are in the same network segment. You do not need to generate a new IP interface. If the IP addresses of all the VLAN IDs exist, but the IP addresses of the two IP interfaces are in the same network segment, you need to re-assign a new network to the NEs. The VLAN interface is used as the calculation result of the matching VLAN interface between the local NE and the peer NE. The VLAN interface is added to the calculation result.

4. Traverse the corresponding relationship 1 and the corresponding relationship 2. If the IP interfaces in the two corresponding relationships are all empty, allocate two IP addresses that are unique to the entire network and on the same network segment, and the network segment is on the NEs at both ends. Not used;

5, traversing the corresponding relationship 1 and the corresponding relationship 2, if there is a null value in the IP interface corresponding to the same VLAN ID, then a new IP interface needs to be assigned, and the identifier is added, for the new IP interface The IP address needs to be calculated based on the IP address that is not empty. If the IP address of the network segment where the IP address is located is not configured on the peer network, the IP address of the network segment where the IP address is located is the same as the IP address of the network segment where the IP address is located. If the configuration has been configured, the two IP addresses of the same network segment are assigned to the entire network segment, and the network segment is not used on the NEs at both ends. According to the above steps, one of the two corresponding relationships is identified as a new one, and one identifier is ^ ίι tampering.

As shown in FIG. 3, step S103 includes:

Step S1031: Calculate a matching VLAN interface between the local network element and the remote network element based on the first VLAN interface set and the second VLAN interface set.

Step S1032: Calculate a matching IP interface between the local network element and the remote network element based on the matching VLAN interface, the first IP interface set, and the second IP interface set.

As shown in FIG. 4, step S1031 includes: Step S10311: query the first VLAN interface set and the second VLAN interface set respectively; Step S10312: If one of the first VLAN interface set and the second VLAN interface set is an empty set, the VLAN interface set is not an empty set. As the matching VLAN interface between the local network element and the peer network element; if the first VLAN interface set and the second VLAN interface set are not empty sets and there is a VLAN interface intersection, the VLAN interface intersection is used as the local network element and the pair. The matching VLAN interface of the end network element; otherwise, a new VLAN interface is assigned as the matching VLAN interface between the local NE and the peer NE.

The principle of determining the intersection of the VLAN interfaces is as follows: The VLAN IDs of the VLAN interfaces are the same. The VLAN interface assignment principle is as follows: The VLAN IDs are unique and equal in the NEs.

As shown in FIG. 5, step S1032 includes:

Step S10321: Query an IP interface with the same ID as the matching VLAN interface in the first IP interface set and the second IP interface set respectively.

Step S10322: If one of the first IP interface set and the second IP interface set is an empty set, and the IP interface in the IP interface set that is not an empty set is not used on the corresponding network element, the corresponding is an empty set. The network element allocates an IP interface that is in the same network segment as the IP interface address of the IP interface set that is not an empty set and is unique to the entire network. The IP interface set that is not an empty set and the assigned IP interface are used as the local network element. a matching IP interface corresponding to the peer network element; if the first IP interface set and the second IP interface set are not empty sets, and at least one pair of IP interfaces have IP addresses in the same network segment, the at least one The IP interface is used as the matching IP interface corresponding to the local NE and the peer NE. Otherwise, an IP interface with the same network and the IP address on the same network segment is assigned as the matching IP address of the local NE and the peer NE. interface.

In this embodiment, the VLAN interface set and the IP interface set of the local network element and the peer network element are separately established, and the data of the local network element and the peer network element are automatically calculated according to the established VLAN interface set and the IP interface set. Matching VLAN interfaces and IP interfaces. When the network is large, manual configuration is highly error-prone, IP conflicts, or VLANs and IPs do not match. Such problems ensure the accuracy of the configuration and improve the configuration efficiency.

As shown in FIG. 6, another embodiment of the present invention provides a method for calculating a network element interface. On the basis of the foregoing embodiment, before step S101, the method further includes:

Step S90: The local network element is used as a query condition, and the topology connection is obtained by querying the database. Step S100: If the topology connection is empty, the user is prompted to establish a physical connection between the local network element and the peer network element.

As described above, before the network element interface is calculated, the network management system needs to synchronize the network element data to determine whether there is a physical connection between the local network element and the peer network element. If there is no physical connection, the user is prompted to establish a physical connection or perform automatic LLDP link discovery.

In this embodiment, the network management system queries the database, and obtains the topology connection by using the local network element as a query condition, and stores it in the TopoLinkList_T linked list structure. If the obtained link is empty or the length of the linked list structure is 0, the user is prompted to establish a fiber connection between the network elements.

The technical solution of this embodiment is described in detail below by using specific examples:

As shown in Figure 7, it is a schematic diagram of connections between network elements in a Layer 3 switching network. The intermediate node NE is named NE1, and the neighboring NEs are named NE2, NE3, and NE4.

NE1 and NE2 are connected to each other through Gei_l/9 and Gei_l/9. GEi_l/9 of NE1 is divided into Vlan2 and Vlan3, Vlan2 corresponds to Layer 3 interface ip2, IP address is 10.1.1.5/24, and Vlan3 corresponds to Layer 3 interface ip3. The IP address is 10.1.2.5/24; the Gei_l/9 of NE2 is divided into Vlan2 and Vlan3, the Layer 3 interface ip2 corresponding to Vlan2, the IP address is 10.1.1.6/24, and the Layer 3 interface ip3 corresponding to Vlan3, the IP address is 10.1.2.6/24.

NE1 and NE3 are connected by Gei_l/10 and Gei_l/10. The Gei_l/10 of NE1 is divided into Vlan4, Vlan4 corresponds to the Layer 3 interface ip4, and the IP address is 10.1.3.5/24. The Gd_l/10 of NE3 is divided into Vlan5. Vlan5 corresponds to the Layer 3 interface ip5, and the IP address is 10.1.4.6/24.

NE1 and NE4 are connected by Gei_l/8 and Gei_l/8, where Gei_l/8 of NE1 It is divided into Vlan5 and Vlan6, Vlan5 corresponds to Layer 3 interface ip5, IP address is 10.1.4.5/24, Vlan6 does not correspond to Layer 3 interface; NE4's Gei_l/8 is divided into Vlan5 and Vlan6, and Vlan5 corresponds to Layer 3 interface ip5, IP The address is 10.1.8.6/24, Vlan6 corresponds to the Layer 3 interface ip6, and the IP address is 10.1.6.6/24.

The NE is the local NE and the NEs NE2, NE3, and NE4 are the peer NEs. The procedure for automatically calculating the NE interface in the network is as follows:

The peer network element that has a physical connection with the local network element is obtained through the topology connection. At the same time, all the physical connections of the local network element are obtained, and the TopoLinkList_T linked list structure is stored, and the TopoLinkList_T linked list structure is traversed. One of the elements TopoLink_T is taken as an example, and the following processing is performed: From the TopoLink_T structure, the local physical port (named ortl) is parsed The physical port of the peer (named port2) is used as the query condition to query the VLAN interface containing the physical port of the local end and the physical port of the remote end. The VLAN interface of the local VLAN interface is stored in the vlanList1 linked list structure and the peer VLAN interface vlanList2 linked list structure. in. In addition, the local network element and the peer network element are also parsed from the TopoLink_T structure, and the IP interface of the local network element and the IP interface of the remote network element are respectively queried. The ipListl linked list structure of the local IP interface and the ipList2 linked list structure of the peer IP interface.

2. Traverse vlanListl and vlanList2, take the intersection of the two sets, and judge the intersection principle as the element with the same VLAN ID. If there is no intersection, assign a new VLAN ID, and generate a new VLAN interface, as an intersection, intersection storage. The data structure is: a mapl HashMap structure created by the local network element, a map2 HashMap structure created by the peer network element, and the element belonging to the vlanListl in the intersection is stored as a key into the ma l , and the element belonging to the vlanList2 in the intersection is used as the element The key is stored in map2.

Taking Figure 7 as an example, through the physical connection between NE1 and NE2, calculate:

Mapl contains two elements, keyl=nel/Vlan2, key2=ne lan3;

Map2 contains two elements, keyl=ne2/Vlan2, key2=ne2/Vlan3; Through the physical connection between NE1 and NE3, calculate:

Mapl contains an element, keyl=nel/vlan7;

Map2 contains an element, keyl=ne2/vlan7;

Through the physical connection calculated by NE1 and NE4, it is calculated:

Mapl contains two elements, keyl=nel/Vlan5, key2=ne lan6;

Map2 contains two elements, keyl=ne2/Vlan5 and key2=ne2/Vlan6.

3. Traverse the key in mapl, and query the ipListl for the same element with the same VLAN ID and IP ID. If it exists, it is stored as the value of mapl. If it does not exist, the value is empty. Map2 is treated with ma l.

Taking Figure 7 as an example, after traversing, the mapl containing elements of NE1 and NE2 are recorded as keyl=nel/Vlan2, value l=nel/ip2, key2=nel/Vlan3, value2=nel/ip3 ; map2 contains elements as keyl= Ne2/Vlan2 , value I=ne2/ip2 , key2=ne2/Vlan3 , value2=ne2/ip3;

Record map1 contains NE1 and NE3 elements are keyl=nel/vlan7, valuel=empty, map2 contains elements as keyl=ne2/vlan7, vlauel=empty;

Record the mapl containing elements of NE1 and NE4 as key 1 = nel / Vlan5 , value l = nel / ip5 , key2 = nel / Vlan6 , value2 = empty , map2 contains elements as keyl = ne2 / Vlan5 , vlauel = ne2 / ip5 , key2 =ne2/Vlan6 , value=ne2/ip6.

Fourth, traversing mapl and map2, if map1 and map2 have the same key, the value is not empty, and the IP address is in the same network segment, then the next key value is compared; if the value is empty, then the allocation The IP addresses in the network segments that are not used in the two network elements of the same network segment and the only two network elements are used to complete the value. If the value in mapl is empty, the vlaue in map2 is not empty. Then, verify that the value ip of mapl has the same network segment ip in ne2, if not used, assign a value of map2 to the same network segment as the value in mapl and the unique IP address of the whole network; Key case, if vlaue in mapl If the value in the map2 is not empty, but the IP address is not in the same network segment, you need to allocate two IP addresses in the network segment that are not used in the two network elements of the same network segment. l The value and the IP address of the value in map2.

Taking Figure 7 as an example, the mapl elements in NE1 and NE2: ma l contain elements: keyl=nel/Vlan2, valuel=nel/ip2:10.1.1.5/24, key2=nel/Vlan3, value2=nel/ip3 :10.1 .2.5/24; map2 contains elements for keyl=ne2/Vlan2, value 1 =ne2/ip2: 10.1.1.6/24 , key2=ne2/Vlan3, value2=ne2/i 3: 10.1.2.6/24 , two of them The IP addresses in the collection do not need to be completed and updated;

NE1 and NE3: ma l contains elements key1=nel/vlan7, valuel=empty, map2 contains elements as key 1 =ne2/vlan7, vlaue 1 = empty, elements in map 1 are updated to key 1 =ne 1 /vlan7 , valuel =nel/ip2:10.1.7.5/24, the elements in map2 are updated to keyl=ne2/vlan7, value 1= ne2/ip2: 10.1.7.6/24;

NE1 and NE4: ma l include elements as keyl=nel/Vlan5, valuel=nel/ip5:10.1.5.5/24, key2=nel/Vlan6, value2= nel/ip6:10.1.6.5/24, map2 contains elements as keyl =ne2/Vlan5 , vlaue 1 =ne2/ip5 :10.1.5.6/24 , key2=ne2/Vlan6, value=ne2/ip6: 10.1.6.6/24.

At this point, all calculation steps are completed. According to the calculation result, traffic can be transmitted between the local NE and the UNI port of the peer NE.

It can be seen from the above calculation process that the input data required for the calculation in this embodiment is simple. Before the network element interface is automatically calculated, the network management system only needs to synchronize the correct interface data on the network element to establish a correct optical fiber connection. The function automatically calculated by the network element interface in this embodiment can avoid manual configuration errors, ensure the accuracy of configuration, and improve configuration efficiency.

As shown in FIG. 8, an embodiment of the present invention provides a network management system for computing a network element interface, including: an obtaining module 801, an establishing module 802, and a computing module 803, where:

The obtaining module 801 is configured to obtain, by using a topology connection, a peer that has a physical connection with the local network element. Network element

The establishing module 802 is configured to respectively establish a first VLAN interface set of the local network element, a first IP interface set, and a second VLAN interface set of the peer network element, and a second IP interface set; A VLAN interface set, a first IP interface set, a second VLAN interface set, and a second IP interface set are used to calculate a matching VLAN interface and a matching IP interface between the local network element and the peer network element.

Before calculating the NE interface, the NMS needs to synchronize the NE data to determine whether there is a physical connection between the local NE and the peer NE. If there is no physical connection, the user is prompted to establish a physical connection or automatically discover the LLDP link.

The network management query aggregates all VLAN interfaces and all IP interfaces of the physical port of the interface that need to be configured with the local NE. The VLAN set 1 and IP set 1 are formed, that is, the first VLAN interface set and the first IP interface set of the local NE are established. At the same time, query all the VLAN interfaces and all IP interfaces of the physical port that need to be configured with the peer NE to form the VLAN set 2 and form the IP set 2, that is, establish the second VLAN interface set and the second IP of the peer network element. Interface collection.

First, the matching VLAN interface between the local network element and the remote network element is calculated according to the first VLAN interface set and the second VLAN interface set, and then the first IP interface set and the second IP interface are calculated and combined according to the calculated matching VLAN interface. The set calculates the matching IP interface between the local NE and the peer NE.

Specifically includes the following process:

1. If the element in VLAN Set 1 is empty, the element in VLAN Set 2 is not empty, then The VLAN ID of VLAN 2 is used as the standard. The same VLAN interface is assigned to the local NE. The VLAN interface calculation result of the local NE is 1 and the newly added VLAN interface is identified in the VLAN interface calculation result 1. VLAN set 2 is used as the VLAN interface calculation result of the peer NE. Otherwise the same treatment;

1. In IP set 1, look up the IP interface corresponding to the calculation result 1 of the local network element VLAN interface. The search principle is that the ID of the IP interface is equal to the VLAN ID in the calculation result 1 of the local network element VLAN interface. If it exists, record it. Correspondence between the VLAN ID and the IP interface. If it does not exist, the mapping between the VLAN ID and the null value is recorded.

2. The IP set 2 and the VLAN interface are calculated in the same step D1 to generate a correspondence 2;

4. Traverse the correspondence 1 and the correspondence 2, if the IP interfaces in the two correspondences are If it is empty, it allocates two IP addresses unique to the entire network and the same network segment, and this network segment has not been used on the NEs at both ends;

As shown in FIG. 9, the calculation module 803 includes: a VLAN interface calculation unit 8031 and an IP interface calculation unit 8032, where:

The VLAN interface calculation unit 8031 is configured to calculate a matching VLAN interface between the local network element and the remote network element based on the first VLAN interface set and the second VLAN interface set.

The IP interface calculation unit 8032 is configured to calculate a matching IP interface between the local network element and the remote network element based on the matched VLAN interface, the first IP interface set, and the second IP interface set.

As shown in FIG. 10, the VLAN interface calculation unit 8031 includes: a first query subunit 80311 and a first calculation subunit 80312, where:

The first query subunit 80311 is configured to separately query the first VLAN interface set and the second VLAN interface set;

The first calculating sub-unit 80312 is configured to: when the one of the first VLAN interface set and the second VLAN interface set is an empty set, the VLAN interface set that is not an empty set is used as a match between the local network element and the remote network element. VLAN interface. When the first VLAN interface set and the second VLAN interface set are both empty sets and there is a VLAN interface intersection, the VLAN interface intersection is used as the matching VLAN interface between the local NE and the peer NE; otherwise, a new interface is assigned. VLAN interface as the local network The matching VLAN interface between the meta and the peer NE.

As shown in FIG. 11, the IP interface computing unit 8032 includes: a second query subunit 80321 and a second computing subunit 80322, where:

The second query sub-unit 80321 is configured to query, in the first IP interface set and the second IP interface set, an IP interface that is the same as the ID of the matching VLAN interface, respectively.

a second calculating sub-unit 80322, configured to: when one of the first IP interface set and the second IP interface set is an empty set, and the IP interface in the IP interface set that is not an empty set is not used on the corresponding network element, Assigning an IP interface corresponding to the IP interface address of the IP interface set that is not an empty set to the IP address of the IP interface set that is not an empty set and unique to the entire network, the IP interface set and the assigned IP address that are not empty sets The interface is a matching IP interface corresponding to the local network element and the peer network element; when the first IP interface set and the second IP interface set are not empty sets, and at least one pair of IP interfaces have IP addresses in the same network. In the segment, the at least one IP interface is used as the matching IP interface between the local network element and the ^ end network element; otherwise, an IP interface with the entire network and the IP address in the same network segment is allocated as the local network element. A matching IP interface corresponding to the peer network element.

As shown in FIG. 12, another embodiment of the present invention provides a network management system for calculating a network element interface. Based on the foregoing embodiments, the method further includes:

The query obtaining module 790 is configured to obtain a topology connection by querying the database by using the local network element as a query condition.

The prompting module 800 is configured to prompt the user to establish a physical connection between the local network element and the peer network element when the topology connection is empty.

In this embodiment, the network management system queries the database, and obtains the topology connection by using the local network element as a query condition, and stores it in the TopoLinkList_T linked list structure. If the obtained link is empty or chain If the length of the table structure is 0, the user is prompted to establish a fiber connection between the network elements.

The method for calculating a network element interface and the network management system in the embodiment of the present invention, respectively, respectively, establishing a VLAN interface set and an IP interface set of the local network element and the peer network element, and automatically calculating the local network element according to the established VLAN interface set and the IP interface set. The matching VLAN interface and the IP interface required to transmit data with the peer network element. When the network is large, the manual configuration is highly error-prone, IP conflicts, or services such as VLANs and IP mismatches are not available, ensuring accurate configuration. Sexuality improves configuration efficiency.

The above is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention, and equivalent structural or process changes made by the present specification and drawings may be directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of the present invention.

Claims

Claim

A method for computing a network element interface, the method comprising: obtaining, by using a topology connection, a peer network element having a physical connection with a local network element;

Establishing a first virtual local area network VLAN interface set of the local network element, a first Internet interconnection protocol IP interface set, and a second VLAN interface set and a second IP interface set of the opposite end network element respectively;

The method according to claim 1, wherein the calculating the local network element and the pair based on the first VLAN interface set, the first IP interface set, the second VLAN interface set, and the second IP interface set The matching VLAN interface of the end network element and the matching IP interface include: calculating a matching VLAN interface between the local network element and the remote network element based on the first VLAN interface set and the second VLAN interface set;

The method according to claim 2, wherein the calculating the matching VLAN interface between the local network element and the remote network element based on the first VLAN interface set and the second VLAN interface set includes:

Querying the first VLAN interface set and the second VLAN interface set respectively; if one of the first VLAN interface set and the second VLAN interface set is an empty set, the VLAN interface set that is not an empty set is used as the local end A matching VLAN interface between the NE and the peer NE;

If the first VLAN interface set and the second VLAN interface set are not empty sets and the VLAN interface intersection exists, the intersection of the VLAN interface is used as the match between the local network element and the remote network element. With a VLAN interface;

The method according to claim 3, wherein the principle of determining the intersection of the VLAN interfaces is as follows: the VLAN IDs of the VLAN interfaces are the same; the VLAN interface is allocated according to the principle that: the VLAN ID is unique within the network element. equal.

The method according to claim 3, wherein the matching IP interface between the local network element and the remote network element is calculated based on the matching VLAN interface, the first IP interface set, and the second IP interface set, Includes:

Otherwise, an IP interface that is unique to the entire network and whose IP address is on the same network segment is assigned as the matching IP interface corresponding to the local NE and the peer NE.

The method according to any one of claims 1 to 5, wherein before the obtaining a peer network element having a physical connection with the local network element by using the topology connection, the method further includes: The end network element is a query condition, and the topology connection is obtained by querying the database. If the topology connection is empty, the user is prompted to establish a relationship between the local network element and the peer network element. Connected.

A network management system for computing a network element interface, wherein the network management system includes: an obtaining module, configured to acquire, by using a topology connection, a peer network element that has a physical connection with the local network element;

The network management system according to claim 7, wherein the calculation module comprises:

The network management system according to claim 8, wherein the VLAN interface calculation unit comprises:

a first query subunit, configured to separately query the first VLAN interface set and the second VLAN interface set;

a first computing subunit, configured to: when the one of the first VLAN interface set and the second VLAN interface set is an empty set, the VLAN interface set that is not an empty set is used as the local network element and the peer network element. Matching the VLAN interface; when the first VLAN interface set and the second VLAN interface set are not empty sets and there is a VLAN interface intersection, the VLAN interface intersection is used as a matching VLAN interface between the local network element and the remote network element. Otherwise, a new VLAN interface is assigned as the matching VLAN interface between the local NE and the peer NE.

10. The network management system according to claim 8, wherein the IP interface computing unit Includes:

The network management system according to any one of claims 7 to 10, wherein the network management system further comprises:

The query obtaining module is configured to obtain the topology connection by querying the database by using the local network element as a query condition;