Network element management method and system

Abstract

The invention discloses a network element management method and system. The method comprises the steps that after a network management system on a network management server is started, a corresponding soft routing system file is loaded according to the type of an operating system of the network management server, and the soft routing system file is integrated in a system software package of the network management system; and after the soft routing system file is loaded, creating a soft routing instance and configuring the soft routing instance, and after configuration is completed, running a soft routing process corresponding to the soft routing instance, so that the soft routing process forwards the OAM message sent by the network management system to the remote equipment. According to the application, the soft routing system file is integrated in the system software package of the network management system, so that the soft routing system becomes a sub-service of the network management system, the soft routing system can normally pass security scanning, and unified management of deployment and operation of the soft routing system is realized.

Description

Technical Field

[0001] This application relates to the technical field of equipment control, and specifically relates to a network element management method and system. Background Art

[0002] DCN is the abbreviation of Data Communication Network, also known as the data communication network, which refers to the network for transmitting OAM (Operation Administration and Maintenance) information between the NMS (Network Management System) and network elements. It is a communication network built by operators to manage equipment. Refer to Figure 1 , Figure 1 FIG. is a schematic diagram of the scenario for network element management based on DCN.

[0003] For Figure 1 the scenario shown, in order to manage network elements, the current conventional solution is as follows:

[0004] Install the NMS and the soft routing system on the network management server respectively, but the installation and configuration software of the soft routing system is independent of the NMS, that is, the soft routing system runs independently of the NMS in the form of a third-party plugin.

[0005] This will cause the following problems:

[0006] 1. The soft routing system is deployed on the network management server in the form of a third-party plugin. For the security scanning software in the network management server, it will consider the soft routing system a security threat, resulting in the soft routing system being unable to pass the security scan and thus unable to run properly;

[0007] 2. For two different operating systems, Linux and Windows, the deployment and operation of the soft routing system adopt different methods, which is not conducive to unified management by customers. For example, for the Linux system, the soft routing system files are encapsulated, deployed, and run and managed in the virtual docker container of the Linux system; while in the Windows system, a separate graphical interface third-party control tool and.exe file need to be installed additionally, and the.exe file is started and configured based on the third-party tool to realize the operation of the soft routing system. Summary of the Invention

[0008] This application provides a network element management method and system, which can solve the technical problem that the soft routing system runs independently of the NMS in the form of a third-party plugin in the prior art.

[0009] In a first aspect, an embodiment of this application provides a network element management method, and the network element management method includes:

[0010] After the network management system on the network management server is started, the corresponding soft routing system file is loaded according to the operating system type of the network management server, and the soft routing system file is integrated in the system software package of the network management system;

[0011] After the soft routing system file is loaded, a soft routing instance is created and configured. After the configuration is completed, the soft routing process corresponding to the soft routing instance is run, so that the soft routing process forwards the OAM message sent by the network management system to the remote device. Among them, the soft routing process receives the OAM message sent by the network management system through the first interface and forwards the OAM message to the remote device through the second interface.

[0012] Combined with the first aspect, in an implementation manner, the network element management method further includes:

[0013] During the running of the soft routing process, identify abnormal soft routing processes;

[0014] When it is identified that there are abnormal soft routing processes, restart the abnormal soft routing processes.

[0015] Combined with the first aspect, in an implementation manner, the network element management method further includes:

[0016] During the running of the soft routing process, collect the packet length and number of OAM messages received by the first interface and the packet length and number of OAM messages sent by the second interface at a preset period, and report the collection results to the network management system.

[0017] Combined with the first aspect, in an implementation manner, the network element management method further includes:

[0018] During the running of the soft routing process, monitor the connectivity of the first communication link between the first interface and the network management system and the connectivity of the second communication link between the second interface and the remote device;

[0019] When the connectivity monitoring result of at least one communication link is abnormal, trigger an alarm.

[0020] Combined with the first aspect, in an implementation manner, the network element management method further includes:

[0021] During the running of the soft routing process, monitor the connectivity of the third communication link between the loopback network card on the network management server and the F interface of the remote device;

[0022] When the connectivity monitoring result of the third communication link is abnormal, trigger an alarm.

[0023] Combined with the first aspect, in an implementation manner, the network element management method further includes:

[0024] During the operation of the soft router process, if there are M memory application events within N unit time periods, then based on N, M, L max and S, a new storage space size is obtained, where M is a positive integer greater than or equal to 1, and L max is the message length of the OAM message with the longest message length among the forwarded OAM messages, and S is the number of storage units included in the initial storage space.

[0025] Combined with the first aspect, in one implementation, the obtaining of the new storage space size based on N, M, L max and S includes:

[0026] Substitute N, M, L max and S into the dynamic memory calculation formula to obtain the new storage space size. The dynamic memory calculation formula is:

[0027]

[0028] where Mem′ is the new storage space size.

[0029] Combined with the first aspect, in one implementation, the network element management method further includes:

[0030] During the operation of the soft router process, if there are no memory application events within N unit time periods, then reduce the current storage space size by a preset ratio.

[0031] Combined with the first aspect, in one implementation, after the network management system on the network management server is started and before loading the corresponding soft router system file according to the operating system type of the network management server, it further includes:

[0032] Determine the functional modules required by the soft router system;

[0033] Encode based on the functional modules required by the soft router system to obtain the source code of the soft router system;

[0034] Compile the source code of the soft router system to generate the soft router system file and integrate it into the system software package of the network management system.

[0035] In a second aspect, an embodiment of the present application provides a network element management system, and the network element management system includes:

[0036] A loading module, configured to load the corresponding soft router system file according to the operating system type of the network management server after the network management system on the network management server is started. The soft router system file is integrated in the system software package of the network management system;

[0037] A forwarding implementation module, which is used to create a soft router instance and configure the soft router instance after the soft router system file is loaded. After the configuration is completed, the soft router process corresponding to the soft router instance is run, so that the soft router process can forward the OAM packets sent by the network management system to the remote device. Among them, the soft router process receives the OAM packets sent by the network management system through the first interface and forwards the OAM packets to the remote device through the second interface.

[0038] The beneficial effects brought by the technical solution provided in the embodiment of the present application include:

[0039] In the embodiment of the present application, after the network management system on the network management server is started, the corresponding soft router system file is loaded according to the operating system type of the network management server, and the soft router system file is integrated in the system software package of the network management system; after the soft router system file is loaded, a soft router instance is created and the soft router instance is configured. After the configuration is completed, the soft router process corresponding to the soft router instance is run, so that the soft router process can forward the OAM packets sent by the network management system to the remote device. Among them, the soft router process receives the OAM packets sent by the network management system through the first interface and forwards the OAM packets to the remote device through the second interface. Through the embodiment of the present application, the soft router system file is integrated in the system software package of the network management system, so that the soft router system becomes a sub-service of the network management system, and the soft router system can pass the security scan normally; in addition, by loading the soft router system file corresponding to the operating system type to adapt to different operating systems, unified management of the deployment and operation of the soft router system is realized. Description of the Drawings

[0040] Figure 1 It is a schematic diagram of the scenario for network element management based on DCN;

[0041] Figure 2 It is a schematic flowchart of an embodiment of the network element management method of the present application;

[0042] Figure 3 It is a schematic diagram of the architecture of the network management system (i.e., the network management system) in an embodiment of the network element management method of the present application;

[0043] Figure 4 It is a schematic diagram of the functional modules required by the soft router system in an embodiment of the network element management method of the present application;

[0044] Figure 5 It is a schematic diagram of the OAM packet forwarding scenario in an embodiment of the network element management method of the present application;

[0045] Figure 6 It is a schematic diagram of the forwarding process monitoring in an embodiment of the network element management method of the present application;

[0046] Figure 7 This is a schematic diagram of the functional modules of an embodiment of the network element management system of the present application. Detailed implementation manners

[0047] In order to enable those skilled in the art of the present technology to better understand the solution of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0048] To make the purpose, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0049] In a first aspect, an embodiment of the present application provides a network element management method.

[0050] In one embodiment, referring to Figure 2 , Figure 2 This is a flowchart of an embodiment of the network element management method of the present application. As Figure 2 shown, the network element management method includes:

[0051] Step S10, after the network management system on the network management server is started, load the corresponding soft router system file according to the operating system type of the network management server, and the soft router system file is integrated in the system software package of the network management system;

[0052] In this embodiment, taking Linux and Windos as examples of the operating system type, before step S10, based on the source code of the soft router system, compile and generate the soft router system file (srouter.so file) and the soft router system file (srouter.dll file), and integrate the srouter.so file and the srouter.dll file into the system software package of the network management system.

[0053] After installing and starting the network management system on the network management server, start the management service and the configuration service. The management service loads the corresponding soft router system file according to the operating system type of the network management server. For example, if it is a Linux operating system, load the srouter.so file; if it is a Windos operating system, load the srouter.dll file. Among them, referring to Figure 3 , Figure 3 This is a schematic diagram of the architecture of the network management system (i.e., the network management system) in an embodiment of the network element management method of the present application. As Figure 3As shown, a soft router system is integrated into the network management system. The yellow-marked modules are related information of the soft router system. The specific functions of each module are described as follows:

[0054] a. At the network management configuration entry level: It supports two modes, northbound and WEB interface, and can configure information such as gneip, gateway ip, ospf domain, tunnel interface configuration (including interface ip, interface source ip, destination ip), static route, etc. required by the GNE soft router. These information are finally sent to the soft router system, and the soft router system generates interfaces, routing forwarding tables, and performs arp learning based on the configuration.

[0055] b. Network management / web value-added backend: It supports configuration distribution, tunnel interface alarm, and traffic performance monitoring and analysis.

[0056] c. GNE configuration processing module: It is located in the common layer of the network management product. It realizes the parsing of configuration data and the distribution of configuration to the GNE soft router system. Data processing supports addition, modification, and deletion operations.

[0057] d. GNE soft router system: It is located in the common layer of the network management product. The soft router system is based on the CLI module (receiving the command-line data sent by the configuration module). After receiving the configuration command line sent by the network management, it completes the I3 module (I3 is the abbreviation of interface inner integration), mainly the processing module of interfaces such as the mgmt management port and tunnel port), ospf, and static route creation.

[0058] Furthermore, in one embodiment, before step S10, it further includes:

[0059] Determine the functional modules required by the soft router system; code based on the functional modules required by the soft router system to obtain the source code of the soft router system; compile the source code of the soft router system to generate the soft router system file and integrate it into the system software package of the network management system.

[0060] In this embodiment, based on the minimum system unit required by the soft router system, module identification and construction are carried out, and unnecessary functional modules are trimmed. For example, the original soft router system solution would include functional modules such as MPLS-TP / QOS. Trimming these functional modules that are not required for tunnel forwarding can reduce the corresponding memory occupancy.

[0061] Refer to Figure 4 , Figure 4 is a schematic diagram of the functional modules required by the soft router system in one embodiment of the network element management method of this application. As Figure 4As shown in the figure, the functional modules required by the soft router system are: I3 module (providing management interfaces for tunnel routing forwarding addition, etc.), OSPF module (for the shortest path first protocol and dynamic routing learning), routing module (for IPV4 / IPV6 routing information processing, static routing configuration, etc.), RT ADV module (for routing broadcast announcements), address learning module (using the Address Resolution Protocol ARP in the IPV4 network and the Neighbor Discovery Protocol NDP in the IPV6 network), and TUNNEL module (for tunnel interface, interface IP address, MTU maximum transmission packet length configuration, etc.).

[0062] After determining the functional modules required by the soft router system, only code for these functional modules is written to obtain the source code of the soft router system. Among them, the coding process includes:

[0063] Optimizing the data initialization method in the static area of the coded code: For the static global variables required by each functional module, the conventional solution is usually to define the data in the data static area and assign it a value of 0. For example, if an int a[1024*1024] array is initialized to a non-zero value, the binary file will be 4MB larger. The optimization method in this embodiment is to only define the variables in the data static area without assignment processing, and then initialize the variables when the function code segment is executed, which can reduce the size of the compiled binary file.

[0064] Optimizing the memory pool management overhead of the code to improve memory utilization: For example, reducing the memory management overhead from 20 bytes to 8 bytes can reduce the alarm monitoring by 12MB for 1 million memory blocks. For example, modifying the length of the memory monitoring identification field of the existing BEP (beacon embedded platform) system. For the memory allocated by malloc, add identification fields before and after the memory. The original fields are 0X1122334455AABBCCDDEE and 0XEEDDCCBBAA5544332211, and they are modified to 0X1234ABCD and 0XDCBA4321 according to the optimization method in this embodiment.

[0065] During coding, modularize the large memory allocation method: divide the large memory of the memory pool required by the functional module into independent chunks as much as possible, so that the memory can be quickly recycled to the operating system after the memory block is released, avoiding memory fragmentation waste. For example, based on common engineering scenarios, set the memory space required for the number of routing entries; in the development of the network management configurable interface options, support the adjustment of routing memory allocation, reducing the system memory unavailability and waste caused by memory fragmentation problems. Since the memory fragmentation waste problem is mainly caused by the programming user making small memory requests and then releasing them to the operating system. When subsequent large memory requests are made, due to the discontinuous memory, the operating system cannot use the released small memory, resulting in memory fragmentation. In this embodiment, a large piece of memory is first applied for the functional module, and the functional module divides and refines the applied large memory as needed for use and vacancy processing, avoiding the generation and waste of fragmentation caused by directly using the small memory requests and releases of the operating system.

[0066] Furthermore, during coding, a memory dynamic change algorithm can also be added to reduce the memory occupation during the operation of the soft routing system, reduce the same packet forwarding, and avoid the frequent requests and occupations of the system memory by each function call stack during the operation of the soft routing system.

[0067] After obtaining the source code of the soft routing system by coding, when compiling the source code of the soft routing system to generate the soft routing system file, use the strip command to strip the function symbol table method (implemented through the strip command during file compilation). This is because the symbol table is only temporarily mounted to the running environment when there is a need for gdb debugging for problem location; the symbol table is not loaded in the normal running environment, reducing the memory occupation of the symbol table on the server. The compiled output soft routing system file is: a.so dynamic file for the Linux system and a.dll file for the Windows system, and the soft routing system file is integrated into the system software package of the network management system.

[0068] Through the above embodiments, the minimum-level recognition of the functional modules required by the soft routing system, the stripping of symbols during software compilation to minimize the soft routing system file, the optimization of software coding and algorithms are realized, and the memory occupation of the server during the operation of the soft routing system is minimized. Finally, the purpose of implementing an extremely simple and lightweight soft routing system is achieved.

[0069] In step S20, after the soft routing system file is loaded, create a soft routing instance and configure the soft routing instance. After the configuration is completed, run the soft routing process corresponding to the soft routing instance, so that the soft routing process can forward the OAM packets sent by the network management system to the remote device. Among them, the soft routing process receives the OAM packets sent by the network management system through the first interface and forwards the OAM packets to the remote device through the second interface.

[0070] In this embodiment, after the soft router system files are loaded, the ice box srouter service is started. The operator configures the soft router instance, the tunnel interfaces in the instance, the tunnel IP, OSPF, etc. through the network management interface (including the northbound interface and the WEB front-end interface), and sends the configuration data to the configuration service module through the interface (including the northbound interface and the WEB front-end interface). On the one hand, the configuration service module stores the configuration data in the database, and on the other hand, it sends the configuration data to the ice box srouter module. The ice box srouter module creates a soft router instance according to the configuration and calls the relevant interface functions of the soft router system (such as the internally implemented process_ip_bind and other interfaces) to set the IP binding of the soft router instance;

[0071] After the soft router instance is created, the ice box srouter sends the configuration data to the soft router instance through TCP communication. The configuration data includes the tunnel interfaces of the soft router instance (including interface IP, srcip, dst ip), the route from the tunnel interface to the remote device, and the OSPF configuration. The soft router instance receives and parses the configuration, generates the corresponding tunnel interfaces, static routes, and OSPF domain entries, and saves the configuration to the configuration file.

[0072] After the above configuration is completed, the soft router process corresponding to the soft router instance can be run.

[0073] On the one hand, the soft router process realizes the OSPF negotiation with the remote device by itself (the specific method is to set the interface IP addresses of the tunnel interfaces in the soft router system and the tunnel interfaces of the remote device in the same network segment, such as 1.1.1.1 and 1.1.1.2 respectively; and add the two IP addresses to the same OSPF domain. In the same OSPF domain, based on the OSPF routing advertisement protocol, the existing routing information of each device is advertised); on the other hand, the OAM packets sent by the network management system are processed through the loopback network card, the first interface of the soft router system, and the MINM module to realize the tunnel encapsulation of the MAC address, tunnel IP, etc., and then sent to the physical network card through the second interface to penetrate the third-party DCN network and reach the remote device. Refer to Figure 5 , Figure 5 is a schematic diagram of the OAM packet forwarding scenario in an embodiment of the network element management method of this application. As Figure 5 shown, the specific forwarding details are as follows:

[0074] When the network management system sends an OAM message to a remote device, the encapsulated MAC address and destination IP are the MAC and IP of the remote device. After the OAM message is sent, based on the route configured in the server system, the OAM message is forwarded to the first interface through the loopback network card. After reaching the soft routing system through the first interface, the soft routing system looks up which tunnel interface the destination IP of the corresponding remote device is in the same domain based on the routing information learned by OSPF. After finding the corresponding tunnel interface, based on the destination IP of the tunnel interface, the message is encapsulated again, and the encapsulation function is completed by the MINM module. Specifically, on the original OAM message, an additional layer of MAC address and IP message header is added. Among them, the destination MAC is the MAC address of the DCN network interface learned by the tunnel interface based on ARP, the source MAC is the MAC of the tunnel interface itself, the destination IP is the destination IP configured by the tunnel interface, and the source IP is the IP of the tunnel interface itself. The encapsulated message is forwarded from the second interface to the physical network card interface of the network management server based on the routing forwarding table configured in the soft routing system. After the encapsulated message reaches the physical interface of the third-party DCN network through the physical network card interface, the third-party DCN network forwards the encapsulated message to the remote device based on the route configured in its own system.

[0075] In the embodiment of the present application, after the network management system on the network management server is started, the corresponding soft routing system file is loaded according to the operating system type of the network management server, and the soft routing system file is integrated in the system software package of the network management system. After the soft routing system file is loaded, a soft routing instance is created and configured. After the configuration is completed, the soft routing process corresponding to the soft routing instance is run to enable the soft routing process to forward the OAM message sent by the network management system to the remote device. Among them, the soft routing process receives the OAM message sent by the network management system through the first interface and forwards the OAM message to the remote device through the second interface. Through the embodiment of the present application, the soft routing system file is integrated in the system software package of the network management system, making the soft routing system a sub-service of the network management system, enabling the soft routing system to pass the security scan normally. In addition, by loading the soft routing system file corresponding to the operating system type to adapt to different operating systems, unified management of the deployment and operation of the soft routing system is achieved.

[0076] Further, in one embodiment, the network element management method further includes:

[0077] During the operation of the soft routing process, identify abnormal soft routing processes; when an abnormal soft routing process is identified, restart the abnormal soft routing process.

[0078] In the conventional solution, the soft router system and the NMS are deployed independently, lacking a process daemon mechanism. As a result, when the soft router process runs abnormally, the NMS system cannot detect it, and manual intervention is required to restart the process, which affects the control of remote devices by the network management server.

[0079] In this embodiment, during the operation of the soft router process, the management service monitors the soft router instances in real time to check whether the number of soft router instances is equal to the number of instances stored in the database. If they are not equal, the abnormal soft router process is restarted (using the interface of the operating system to start the process, such as the interface function NtCreateProcessEx in the Windows system). The process restarted by the soft router performs IP binding and searches for the configuration file in the corresponding soft router entity directory based on the IP. Based on the data saved in the configuration file, the creation of relevant tunnel interfaces, routes, OSPF and other entries is restored. This avoids the failure of the soft router process and affects the control of remote devices by the network management server.

[0080] Further, in one embodiment, the network element management method further includes:

[0081] During the operation of the soft router process, the packet length and number of OAM packets received by the first interface and the packet length and number of OAM packets sent by the second interface are collected at a preset period, and the collection results are reported to the network management system.

[0082] In this embodiment, during the operation of the soft router process, the soft router system performs real-time traffic collection on the first interface and the second interface based on the timer setting (the timer runs a code loop at regular intervals, and calculates the transceiver traffic based on the time period and the packet length and number of transceiver packets on the corresponding interface during this period. The general calculation formula is: packet length * number * 8bit / time period), and reports the collection results to the network management system for display on the background and interface of the network management system. The display results can be used for engineering maintenance to check whether the OAM packets are forwarded and the size of the forwarded traffic.

[0083] Further, in one embodiment, the network element management method further includes:

[0084] During the operation of the soft router process, the connectivity of the first communication link between the first interface and the network management system and the connectivity of the second communication link between the second interface and the remote device are monitored;

[0085] When the connectivity monitoring result of at least one communication link is abnormal, an alarm is triggered.

[0086] In this embodiment, during the operation of the soft routing process, link connectivity monitoring can be initiated in real time or at a preset time interval. Based on the communication principle icpm ping method, the connectivity of the first communication link and the second communication link are monitored respectively. If the ping can be successful (icmp ping packet, there is a reply packet from the other end, and there is no packet loss, then the ping packet is considered normal), the link is considered normal; if the ping fails, it means that the link is abnormal. When the link is abnormal, a "link channel abnormality" alarm is reported, triggering the network management buzzer alarm reminder (mainly reflected in Figure 6 China Network Management / WEB value-added backend GNE interface, alarm analysis module function). Figure 6 , Figure 6 This is a schematic diagram of monitoring the forwarding process in an embodiment of the network element management method of the present application. Figure 6 The mngt0 in the figure is the first interface, and the mgmt is the second interface; the first communication link is Figure 6 The communication link from the network management operation data to mngt0, the second communication link is Figure 6 Communication link from mgmt to GEN TUNNEL at remote device end.

[0087] Furthermore, in one embodiment, the network element management method further includes:

[0088] During the running of the soft routing process, the connectivity of the third communication link between the loopback network card on the network management server and the F interface of the remote device is monitored;

[0089] When the connectivity monitoring result of the third communication link is abnormal, an alarm is triggered.

[0090] In this embodiment, continue to refer to Figure 6 , the connectivity of the third communication link between the loopback network card and the F interface of the remote device is monitored, and the icpm ping method is also adopted. When the connectivity monitoring result of the third communication link is abnormal, an alarm is triggered.

[0091] Furthermore, in one embodiment, the network element management method further includes:

[0092] During the running of the soft router process, if there are M memory request events within N unit time, based on N, M, L max and S to obtain the new storage space size, where M is a positive integer greater than or equal to 1, L max is the message length of the longest OAM message among the forwarded OAM messages, and S is the number of storage units contained in the initial storage space.

[0093] In this embodiment, modules such as the application interface and router share the data forwarding storage space, that is, the initial storage space (assuming the initial storage space includes P storage units / storage addresses). And the addresses for storing the OAM packet lengths to be forwarded by each soft router process are numbered.

[0094] When the OAM packet is transmitted among modules such as the interface, protocol stack, and router, it shares the storage addresses in the storage space, and locks and transmits the entry numbers to the downstream modules; in data forwarding, each module does not need to apply for a memory address separately.

[0095] When the OAM packet transmission and processing are completed, the tail module changes the corresponding entry number from locked to released. Among them, the modules for packet processing are called serially. For example, the interface calls ospf and then calls the MINM module. When the last module for packet processing finishes the packet sending process, it is considered that the packet forwarding process is completed. For example, the MINM module sets the corresponding entry number to the release flag.

[0096] For an overlong packet encountered during forwarding, when the allocated address length does not meet the actual packet length, memory is re-applied, and the address is numbered; at the same time, the memory address, memory length, and entry number of the new entry are sent to the memory monitoring module for subsequent memory optimization and integration processing. The memory monitoring module updates the packet length L of the longest packet in real time max 。

[0097] During forwarding, when all entries in the existing total memory space are in use and there is no available entry to provide memory for new packet forwarding, a shared space of the size of the existing total memory space is re-applied, and the increase times are sent to the memory monitoring module;

[0098] The memory monitoring module records in real time that there are M memory application events within N unit times, then combines L max and S to obtain the new storage space size.

[0099] Further, in an embodiment, obtaining the new storage space size based on N, M, L max and S includes:

[0100] Substitute N, M, L max and S into the dynamic memory calculation formula to obtain the new storage space size. The dynamic memory calculation formula is:

[0101]

[0102] where Mem′ is the new storage space size.

[0103] The memory monitoring module applies for new storage space in the system for the subsequent forwarding of packets newly received by the soft router forwarding system, and the memory in the original storage space is no longer used for the forwarding of newly added packets; when there are no entries in use in the original storage space (no forwarding packets use the corresponding memory and the usage bits of all entries are set to released), the memory in the original storage space is released.

[0104] Further, in one embodiment, the network element management method further includes:

[0105] During the operation of the soft router process, if there is no memory application event within N unit time intervals, the current storage space size is reduced by a preset ratio.

[0106] In this embodiment, during the operation of the soft router process, if there is no memory application event within N unit time intervals, it indicates that the memory required for forwarding within N unit time intervals is less than the current storage space size, and then the memory is reduced, for example, each time 1 / 10 of the entries are reduced for processing.

[0107] In a second aspect, an embodiment of the present application further provides a network element management system.

[0108] In one embodiment, referring to Figure 7 , Figure 7 is a schematic diagram of the function modules of an embodiment of the network element management system of the present application. As Figure 7 shown, the network element management system includes:

[0109] A loading module 10, configured to load a corresponding soft router system file according to the operating system type of the network management server after the network element management system on the network management server is started, where the soft router system file is integrated in the system software package of the network element management system;

[0110] A forwarding implementation module 20, configured to create a soft router instance and configure the soft router instance after the soft router system file is loaded, and run the soft router process corresponding to the soft router instance after the configuration is completed, so that the soft router process forwards the OAM packets sent by the network element management system to a remote device. Among them, the soft router process receives the OAM packets sent by the network element management system through a first interface and forwards the OAM packets to the remote device through a second interface.

[0111] Further, in one embodiment, the network element management system further includes a process monitoring module, configured to:

[0112] Identify abnormal soft router processes during the operation of the soft router process;

[0113] When it is identified that there are abnormal soft router processes, restart the abnormal soft router processes.

[0114] Further, in one embodiment, the network element management system further includes a traffic monitoring module for:

[0115] During the operation of the soft router process, collect the packet lengths and quantities of OAM packets received by the first interface and the packet lengths and quantities of OAM packets sent by the second interface at a preset period, and report the collection results to the network management system.

[0116] Further, in one embodiment, the network element management system further includes a first link monitoring module for:

[0117] During the operation of the soft router process, perform connectivity monitoring on the first communication link between the first interface and the network management system and perform connectivity monitoring on the second communication link between the second interface and the remote device;

[0118] When the connectivity monitoring result of at least one communication link is abnormal, trigger an alarm.

[0119] Further, in one embodiment, the network element management system further includes a second link monitoring module for:

[0120] During the operation of the soft router process, perform connectivity monitoring on the third communication link between the loopback network card on the network management server and the F interface of the remote device;

[0121] When the connectivity monitoring result of the third communication link is abnormal, trigger an alarm.

[0122] Further, in one embodiment, the network element management system further includes a memory management module for:

[0123] During the operation of the soft router process, if there are M memory application events within N unit time durations, then based on N, M, L max and S to obtain a new storage space size, where M is a positive integer greater than or equal to 1, and L max is the packet length of the OAM packet with the longest packet length among the forwarded OAM packets, and S is the number of storage units included in the initial storage space.

[0124] Further, in one embodiment, the memory management module is used for:

[0125] Substitute N, M, L max and S into the dynamic memory calculation formula to obtain a new storage space size, and the dynamic memory calculation formula is:

[0126]

[0127] where Mem′ is the new storage space size.

[0128] Further, in one embodiment, the memory management module is further configured to:

[0129] During the operation of the soft router process, if there is no memory application event within N unit time periods, reduce the current storage space size by a preset ratio.

[0130] Among them, the function implementation of each module in the above network element management system corresponds to each step in the above network element management method embodiment, and its function and implementation process will not be elaborated here one by one.

[0131] It should be noted that the serial numbers of the embodiments of the present application above are only for description and do not represent the advantages and disadvantages of the embodiments.

[0132] The terms "including" and "having" and any variations thereof in the specification, claims and drawings of the present application are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products or devices. The descriptions of the terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit that "first", "second" and "third" are different types.

[0133] In the description of the embodiments of the present application, "exemplary", "for example" or "for instance" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary", "for example" or "for instance" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of the words "exemplary", "for example" or "for instance" is intended to present related concepts in a specific manner.

[0134] In the description of the embodiments of the present application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B; "and / or" in the text is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality of" means two or more than two.

[0135] In some processes described in the embodiments of the present application, multiple operations or steps appear in a specific order. However, it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or may be executed in parallel. The serial numbers of the operations are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. Additionally, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0136] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation. Based on such an understanding, the technical solution of the present application, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium as described above (such as ROM / RAM, magnetic disk, optical disc) and includes several instructions for causing a terminal device to execute the methods described in various embodiments of the present application.

[0137] The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application. Any equivalent structural or equivalent process transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present application.

Claims

1. A network element management method, characterized in that: The network element management method comprises: After the network management system on the network management server is started, the corresponding soft routing system file is loaded according to the operating system type of the network management server, and the soft routing system file is integrated in the system software package of the network management system; After the soft routing system file is loaded, a soft routing instance is created and configured. After the configuration is completed, the soft routing process corresponding to the soft routing instance is run so that the soft routing process can forward the OAM messages sent by the network management system to the remote device. The soft routing process receives the OAM messages sent by the network management system through the first interface and forwards the OAM messages to the remote device through the second interface.

2. The network element management method according to claim 1, characterized in that: The network element management method further includes: During the running of the soft routing process, abnormal soft routing processes are identified; When an abnormal soft routing process is identified, the abnormal soft routing process is restarted.

3. The network element management method according to claim 1, characterized in that: The network element management method further includes: During the running of the soft routing process, the packet length and number of the OAM messages received by the first interface and the packet length and number of the OAM messages sent by the second interface are collected according to a preset period, and the collection results are reported to the network management system.

4. The network element management method according to claim 1, characterized in that: The network element management method further includes: During the running of the soft routing process, the connectivity of the first communication link between the first interface and the network management system is monitored, and the connectivity of the second communication link between the second interface and the remote device is monitored; When the connectivity monitoring result of at least one communication link is abnormal, an alarm is triggered.

5. The network element management method according to claim 1, characterized in that: The network element management method further includes: During the running of the soft routing process, the connectivity of the third communication link between the loopback network card on the network management server and the F interface of the remote device is monitored; When the connectivity monitoring result of the third communication link is abnormal, an alarm is triggered.

6. The network element management method according to claim 1, characterized in that: The network element management method further includes: During the running of the soft router process, if there are M memory request events within N unit time, based on N, M, L max and S to obtain the new storage space size, where M is a positive integer greater than or equal to 1, L max is the message length of the longest OAM message among the forwarded OAM messages, and S is the number of storage units contained in the initial storage space.

7. The network element management method according to claim 6, characterized in that: Based on N, M, L max And S gets the new storage space size, including: N, M, L max And S is substituted into the dynamic memory calculation formula to obtain the new storage space size, and the dynamic memory calculation formula is: Among them, Mem′ is the new storage space size.

8. The network element management method according to claim 1, characterized in that: The network element management method further includes: During the running of the soft router process, if there is no memory application event within N unit time, the current storage space size will be reduced according to the preset ratio.

9. The network element management method according to claim 1, characterized in that: After the network management system on the network management server is started, before the corresponding soft routing system file is loaded according to the operating system type of the network management server, it also includes: Determine the functional modules required by the soft routing system; Encode based on the functional modules required by the soft routing system to obtain the source code of the soft routing system; Compile the source code of the soft routing system, generate the soft routing system files and integrate them into the system software package of the network management system.

10. A network element management system, characterized in that: The network element management system comprises: A loading module, used to load the corresponding soft routing system file according to the operating system type of the network management server after the network management system on the network management server is started, wherein the soft routing system file is integrated in the system software package of the network management system; The forwarding implementation module is used to create a soft routing instance and configure the soft routing instance after the soft routing system file is loaded. After the configuration is completed, the soft routing process corresponding to the soft routing instance is run so that the soft routing process can forward the OAM message sent by the network management system to the remote device. The soft routing process receives the OAM message sent by the network management system through the first interface and forwards the OAM message to the remote device through the second interface.

Images