CN113132127A - Network equipment management method, system and network equipment - Google Patents
Network equipment management method, system and network equipment Download PDFInfo
- Publication number
- CN113132127A CN113132127A CN201911396966.0A CN201911396966A CN113132127A CN 113132127 A CN113132127 A CN 113132127A CN 201911396966 A CN201911396966 A CN 201911396966A CN 113132127 A CN113132127 A CN 113132127A
- Authority
- CN
- China
- Prior art keywords
- management system
- network device
- repair
- protocol stack
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 189
- 238000004891 communication Methods 0.000 claims abstract description 70
- 238000000034 method Methods 0.000 claims abstract description 43
- 230000008439 repair process Effects 0.000 claims description 66
- 238000012544 monitoring process Methods 0.000 claims description 25
- 230000004044 response Effects 0.000 claims description 22
- 238000013480 data collection Methods 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 3
- 238000002955 isolation Methods 0.000 abstract description 7
- 230000006870 function Effects 0.000 description 12
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/34—Signalling channels for network management communication
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The present disclosure provides a network device management method, applied to a fault management system side, where the management system runs in a container environment of a network device, the method includes: generating first control information; and sending the first control information to a protocol stack system based on a communication interface configured by the protocol stack system. The network equipment management method provided by the disclosure realizes the resource isolation between the fault management system and the host operating system of the network equipment, so that the running state of the fault management system does not influence the communication state of the network equipment, and the stability of the performance of the network equipment is further improved. The present disclosure also provides a network device management system, a network device and a computer readable medium.
Description
Technical Field
The disclosed embodiments relate to the field of communications technologies, and in particular, to a network device management method,
A system, a network device, and a computer-readable medium.
Background
With the increasing huge network scale, whether effective management can be performed on network devices brings about a lot of pressure to operation and maintenance personnel, the existing network device management method usually installs a fault management system in a protocol stack system of the network devices to manage the network devices, that is, the fault management system exists as a functional module in the protocol stack system, and this method can cause the fault management system to easily affect the communication and system performance of the network devices.
Disclosure of Invention
The present disclosure solves at least one of the technical problems in the prior art, and embodiments of the present disclosure provide a network device management method, system, network device, and computer readable medium.
In a first aspect, the present disclosure provides a network device management method applied to a fault management system side, where the management system runs in a container environment of a network device, and the method includes:
generating first control information;
and sending the first control information to a protocol stack system based on a communication interface configured by the protocol stack system.
In some embodiments, the first control information comprises: at least one of configuration event information, subscription event information, and repair event information.
In some embodiments, when the first control information includes repair event information, after the step of sending the first control information to the protocol stack system according to the communication interface of the protocol stack system, further includes:
receiving repair response information fed back by the protocol stack system based on the communication interface;
acquiring a preset repair strategy corresponding to the repair event information;
sending the repair policy to the protocol stack system based on the communication interface.
In some embodiments, the method further comprises:
responding to a restart completion instruction, and acquiring pre-stored user management information;
and generating second control information based on the user management information, and sending the second control information to the protocol stack system based on the communication interface.
In a second aspect, the present disclosure further provides a network device management method, applied to a protocol stack system side, where the method includes:
receiving first control information sent by a fault management system operating in a container environment based on a communication interface configured by the fault management system;
and managing the network equipment according to the first control information.
In some embodiments, the first control information comprises: at least one of configuration event information, subscription event information, and repair event information.
In some embodiments, when the first control information includes: when the event information is repaired, the step of controlling and managing the network device according to the first control information specifically includes:
collecting target monitoring data in real time according to a monitoring data collection strategy in the repair event information;
if the collected target monitoring data meets the repair triggering condition in the repair event information, generating repair response information, and feeding back the repair response information to the fault management system through the communication interface;
receiving a repair strategy sent by the fault management system;
and controlling the network equipment to execute the repair operation according to the repair strategy.
In a third aspect, the present disclosure provides a network device management system, including: a fault management system and a protocol stack system;
the fault management system is instantiated in a container environment;
the protocol stack system is configured with a communication interface for communicating with the fault management system.
In a fourth aspect, the present disclosure provides a network device, comprising:
one or more processors;
a storage device, on which a first program and/or a second program are stored, when the first program is executed by the one or more processors, the one or more processors are caused to implement the steps in the network device management method provided by the first aspect of the present disclosure; when the second program is executed by the one or more processors, the one or more processors implement the steps in the network device management method provided by the second aspect of the present disclosure.
In a fifth aspect, the present disclosure provides a computer readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the steps in the network device management methods provided in the first and second aspects of the present disclosure.
Compared with the prior art, the network device management method provided by the embodiment of the disclosure realizes resource isolation between the fault management system and a host operating system of the network device, so that the operating state of the fault management system does not affect the communication state of the network device, and further improves the stability of the performance of the network device.
Drawings
The accompanying drawings are included to provide a further understanding of the embodiments of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the principles of the disclosure and not to limit the disclosure. The above and other features and advantages will become more apparent to those skilled in the art by describing in detail exemplary embodiments thereof with reference to the attached drawings, in which:
fig. 1 is a schematic structural diagram of a network device management system according to the present disclosure.
Fig. 2 is a flowchart of a network device management method according to an embodiment of the present disclosure;
fig. 3 is a flowchart of another network device management method provided in the embodiments of the present disclosure;
fig. 4 is a flowchart of another network device management method according to an embodiment of the present disclosure;
fig. 5 is a flowchart of a further network device management method according to an embodiment of the present disclosure;
fig. 6 is a flowchart of a further network device management method according to an embodiment of the present disclosure;
fig. 7 is a flowchart of another network device management method according to an embodiment of the present disclosure;
fig. 8 is a flowchart of a further network device management method according to an embodiment of the present disclosure;
fig. 9 is a flowchart of a further network device management method according to an embodiment of the present disclosure;
fig. 10 is a flowchart of a configuration method of a network device management system according to an embodiment of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, a network device management method, a network device management system, a network device and a computer readable medium provided by the present invention are described in detail below with reference to the accompanying drawings.
Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but which may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It will be understood that, although the terms first, second, etc. may be used herein to describe various elements/instructions/requests, these elements/instructions/requests should not be limited by these terms. These terms are only used to distinguish one element/instruction/request from another element/instruction/request.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The network device management method provided by the present disclosure is used for managing the network device, for example, configuring information of the network device, subscribing to query partial status data of the network device, monitoring whether the network device fails, and automatically repairing the network device according to a preset policy after the network device fails, and the like. The network device management method provided by the present disclosure is implemented based on a network device management system, as shown in fig. 1, fig. 1 shows a schematic structural diagram of the network device management system provided by the present disclosure, and the network device management system includes a fault management system 1 and a protocol stack system 2, which perform interactive communication through a preset communication interface to implement management of a network device. It should be noted that, in the present disclosure, the fault management system 1 runs in a container environment of the network device, and the protocol stack system 2 runs in a host operating system of the network device, and the container environment is independent from the host operating system of the network device (for example, Linux native system), so that resource isolation of the fault management system from other functional modules (for example, protocol stack system) in the network device can be realized.
The network device management method provided by the present disclosure will be described below with the fault management system 1 and the protocol stack system 2 as execution subjects, respectively.
Fig. 2 is a flowchart of a network device management method provided in an embodiment of the present disclosure, where the method uses a fault management system 1 as an execution subject, and as shown in fig. 2, the method includes:
step S101, generating first control information.
In this disclosure, the first control information refers to information for controlling and managing the network device by the user, for example, the first control information may include configuration event information or subscription event information, where the configuration event information indicates that the user is about to perform configuration operation on the network device, and the subscription event information indicates that the user is about to perform subscription of some operation data on the network device.
In practical applications, the first control information may be automatically generated by the fault management system after receiving the management information input by the user.
And S102, sending the first control information to the protocol stack system based on the communication interface configured by the protocol stack system.
A protocol stack system, also called a protocol stack system, is a specific software implementation of a computer network protocol suite. In the present disclosure, since the fault management system operates in a container environment independent of the host operating system of the network device, the protocol stack system is specially configured with a communication interface capable of communicating with the fault management system, and the communication interface can implement network communication between the fault management system and the protocol stack system. In some embodiments, the communication interface may include: the management interface and the control interface, and the user can call different interfaces for data transmission based on own requirements.
In the present disclosure, the communication interface may be set by the user himself or herself based on the user's needs. For example, in some embodiments, the communication interface may include: the method comprises the steps of setting an Interface of a Network Configuration Protocol Server (NETCONF Server for short) and an Interface of a Remote Procedure Call Server (Google Mobile Protocol Call Protocol Server for short), setting corresponding clients (NETCONF client and GRPC client) in a fault management system correspondingly, defining interfaces for the Server and the client by adopting an Interface Description Language (IDL) and generating development interfaces of different programming languages by using an automatic conversion tool so as to be directly used by the Server and the client. The interface of the NETCONF server can be used as a management plane interface, and the interface of the GRPC server can be used as a control plane interface, that is, the management plane interface provides services to the outside through the NETCONF server, and the control plane interface provides services to the outside through the GRPC server.
In practical applications, the network connection between the fault management system and the protocol stack system may be implemented based on an IP address, that is, the interface of the server and the interface of the client may implement interworking based on the IP address. Specifically, NETCONF server and GRPC server in the protocol stack system respectively create own communication address IP1 and communication address IP2 to serve as own communication marks, NETCONF client and GRPC client in the fault management system create communication address IP3, and a proxy service module is arranged to perform configuration cooperation on the fault management system and the protocol stack system, so that the fault management system can establish network link with the communication addresses IP1 and IP2 of the protocol stack system through the communication address IP3, and further the fault management system can use a management plane interface and a control plane interface provided by the protocol stack system.
Compared with the prior art, the network equipment management method provided by the embodiment of the disclosure realizes resource isolation between the fault management system and a host operating system of the network equipment, so that the running state of the fault management system does not affect the communication state of the network equipment, and further improves the stability of the performance of the network equipment.
Fig. 3 is a flowchart of another network device management method provided in an embodiment of the present disclosure, and as shown in fig. 3, in some embodiments, when a user only performs information configuration on a network device, the first control information includes: configuring event information, further comprising: the configuration event information is used for describing that a user is about to perform certain configuration on certain functional modules of the network device, and the configuration policy is different according to different functional modules configured by the user and different configuration information, so that the specific form of the configuration policy is not limited in the present disclosure. Correspondingly, at this time, step S102 specifically includes:
and S1021, sending the first control information to the protocol stack system based on the communication interface so that the protocol stack system can configure the network equipment according to the configuration strategy.
Preferably, in the embodiment of the present disclosure, the communication interface selects the management plane interface.
After receiving the first control information, the protocol stack system sends the configuration event information to a corresponding functional module in the protocol stack system according to the configuration event information, and after receiving the first control information, the functional module automatically configures the information according to a configuration strategy in the configuration event information.
Fig. 4 is a flowchart of another network device management method provided in an embodiment of the present disclosure, and as shown in fig. 4, in some embodiments, when a user needs to obtain some dynamic operation data of a network device, the first control information includes: subscribing to event information; at this time, after step S102, the method further includes:
and step S103, receiving subscription response information fed back by the protocol stack system based on the communication interface.
In the embodiment of the present disclosure, the subscription event information is used to describe that the user is going to acquire some dynamic data of the network device, and further, the subscription event information may include: the method comprises the steps that an information acquisition strategy is subscribed, a fault management system sends subscription event information to a protocol stack system based on a communication interface, the protocol stack system sends the subscription event information to a corresponding function module according to the subscription event information, the function module acquires corresponding target data according to the subscription information acquisition strategy after receiving the subscription event information, the subscription information acquisition strategy can comprise information such as the type and acquisition requirement of the target data to be acquired, the function module packages the target data and generates subscription response information after data acquisition is finished, the subscription response information comprises the target data and feeds the subscription response information back to the fault management system based on the communication interface, and the fault management system receives the subscription response information and feeds the subscription response information back to a user for the user to look up.
Preferably, in the embodiment of the present disclosure, the communication interface selects the control plane interface.
In the embodiment of the disclosure, the user can subscribe the device dynamic data in which the user is interested based on the fault management system, so that different requirements of different users can be met, and the user is prevented from manually screening massive data.
Fig. 5 is a flowchart of still another network device management method implemented by the present disclosure, and as shown in fig. 5, in some embodiments, when a user needs to perform fault definition tracking on a network device, the first control information includes: repair event information describing that a user is going to track and repair some failures of the network device, in this case, after step S102, the method may include:
step S103', the repair response information fed back by the protocol stack system is received based on the communication interface.
And step S104', acquiring a preset repair strategy corresponding to the repair event information.
Step S105', sending the repair policy to the protocol stack system based on the communication interface.
In the embodiment of the present disclosure, after the fault management system sends the repair event information to the protocol stack system based on the communication interface, the protocol stack system sends the repair event information to the corresponding function modules, each function module collects target monitoring data in real time according to a monitoring data collection policy included in the repair event information, and determines whether the target monitoring data meets the repair trigger condition included in the repair event information, where the target monitoring data is used to characterize an abnormal state characteristic of the network device, and when it is determined that the target monitoring data meets the repair trigger condition, it indicates that the network device currently has the abnormal state characteristic, and at this time, the protocol stack system generates repair response information and feeds the repair response information back to the fault management system through the communication interface, and the fault management system receives the repair response information based on the communication interface (step S103'), and acquiring a pre-stored repair policy corresponding to the repair event information (step S104 '), where it is noted that the repair policy is pre-configured in the fault management system by a user and can be stored by the fault management system, the repair policy includes a repair operation that should be adopted when the device is in a certain abnormal state, the fault management system sends the repair policy to the protocol stack system based on the communication interface after acquiring the repair policy (step S105'), and the protocol stack system controls the network device to execute the corresponding repair operation according to the repair policy after receiving the repair policy, so as to repair the abnormality of the network device.
Preferably, in the embodiment of the present disclosure, the communication interface selects the control plane interface.
In the above embodiments, the fault management module may generate the first control information based on the following ways: 1) a user inputs management information in a fault management system based on web page configuration and command line configuration, and the fault management system generates first control information according to the web page configuration information and the command line configuration information; 2) a user inputs management information based on a communication interface (a management surface interface and a control surface interface) of a protocol stack system by using a scripting language programming mode so that a fault management system can generate first control information according to a programmed program block, wherein the scripting language can be PYTHON, JAVA, C, GO and the like; 3) management models are preset in a fault management system, each management model is defined with model parameters, when a user needs to manage network equipment, an applicable model can be selected to be filled, and after the fault management system receives the management models filled by the user, first control information is automatically generated according to the relevant parameters of the management models.
It should be noted that, after the user inputs the management information, the fault management system may automatically store the management information input by the user, and after the fault management system is restarted due to a fault or manually restarted, the stored management information is re-acquired, and second control information is generated based on the user management information, and then the second control information is sent to the protocol stack system based on the communication interface. In the "second control information" and the "first" and the "second" in the "first control information", the "first" and the "second" are used only as the distinguishing marks. In the embodiment of the present disclosure, since the fault management system is operated in the container environment of the network device, the restart of the fault management system does not affect the communication activities performed on the operating system of the network device main body, and since the management information input by the user is stored in the fault management system in advance, the restarted fault management system can quickly manage the network device based on the user intention again.
The network device management method provided by the present disclosure is described below with a protocol stack system as an execution subject.
Fig. 6 is a flowchart of a further network device management method according to an embodiment of the present disclosure, and as shown in fig. 6, the method includes:
step S201, receiving first control information sent by a fault management system operating in a container environment based on a communication interface configured by the fault management system.
In the embodiment of the present disclosure, step S201 corresponds to step S102 in the above embodiment, and therefore, please refer to the description of step S102 for details, which is not repeated herein.
Step S202, managing the network equipment according to the first control information.
And after receiving the first control information, the protocol stack system correspondingly manages the network equipment according to the event type contained in the first control information.
Compared with the prior art, the network equipment management method provided by the embodiment of the disclosure realizes resource isolation between the fault management system and a host operating system of the network equipment, so that the running state of the fault management system does not affect the communication state of the network equipment, and further improves the stability of the performance of the network equipment.
Fig. 7 is a flowchart of a further network device management method according to an embodiment of the present disclosure, and as shown in fig. 7, in some embodiments, the first control information includes: configuration information, further, the configuration information includes: configuring a policy, in this case, step S202 specifically includes:
step S2021, correspondingly configuring the network device according to the configuration policy.
The network device management method provided in the embodiment of the present disclosure corresponds to the steps of the method shown in fig. 3, and please refer to the description of the corresponding steps in the method shown in fig. 3, which is not described herein again.
Fig. 8 is a flowchart of a further network device management method according to an embodiment of the present disclosure, and as shown in fig. 8, in some embodiments, the first control information includes: subscribing to the event information, further subscribing to the event information comprising: subscribing to an information collection policy, at this time, step S202 specifically includes:
step S2021', collects target data corresponding to the subscription event information.
Step S2022', generates subscription response information based on the target data.
Step S2023', feed back the subscription response information to the fault management system through the communication interface.
The network device management method provided in the embodiment of the present disclosure corresponds to the steps of the method shown in fig. 4, and please refer to the description of the corresponding steps in the method shown in fig. 4, which is not described herein again.
Fig. 9 is a flowchart of a further network device management method according to an embodiment of the present disclosure, and as shown in fig. 9, in some embodiments, the first control information includes: repairing the event information; further, the repair event information includes: monitoring a data acquisition strategy and a repair triggering condition, wherein at this time, the step S202 specifically includes:
and step S2021', collecting target monitoring data in real time according to a monitoring data collection strategy.
Step S2022', it is judged whether the target monitoring data satisfies the repair triggering condition.
When the target monitoring data is judged to meet the repair triggering condition, executing the step S2023 ", and when the target monitoring data is judged to meet the repair triggering condition, returning to continue executing the step S2021", where of course, in practical application, a time threshold may also be set to limit the monitoring duration so as to avoid non-terminated monitoring.
Step S2023 ″, generating repair response information, and feeding back the repair response information to the fault management system through the communication interface.
Step S2024', a repair strategy sent by the fault management system is received.
Step S2025 ″, the network device is controlled to perform the repair operation according to the repair policy.
The network device management method provided in the embodiment of the present disclosure corresponds to the steps of the method shown in fig. 5, and please refer to the description of the corresponding steps in the method shown in fig. 5, which is not described herein again.
The network device management method provided by the present disclosure is described below with the specific use scenario as an aid.
Step 1: the network equipment starts a proxy service module, a protocol stack system and a container system, and communication links of the protocol stack system and the container system are communicated through the proxy service module.
Step 2: communication addresses IP1 are created in the protocol stack system, and are configured as NETCONF server, communication addresses IP2 are created, and are configured as server addresses of GRPC server, the management interface provides services to the outside through the NETCONF server, and the control interface provides services to the outside through the GRPC server.
And step 3: each service function module in the protocol stack system registers a management plane interface capability and a control plane interface capability set provided by the outside to NETCONF server and GRPC server.
And 4, step 4: starting a NETCONF client and a GRPC client in the fault management system, and creating an address IP 3; the fault management system establishes connection with NETCONF server and GRPC server in the protocol stack system through IP3, establishes communication channel for network element management operation, after the channel is established successfully, the fault management system can call the management interface and control interface provided by the protocol stack system, the call interface is generated into development packet by automatic conversion tool and is pre-installed in the container where the fault management system is located, and the fault management system can directly access and call.
And 5: the user configuration requires monitoring of the received message statistics of the tunnel interface IF1 in the device and when it is monitored that the received message exceeds 80% of the tunnel interface bandwidth, the tunnel bandwidth is adjusted by increasing the specified value 5G.
Step 6: after the fault management system reads the configuration, it initiates an RPC (remote Procedure Call, abbreviated as RPC) request according to the interface identifier of the control plane interface, and issues the monitoring request to the protocol stack system.
And 7: after receiving the information, the GRPC server in the protocol stack system distributes the information to a specific service function module, namely an interface management module according to the interface registration information, the interface management module analyzes the information to generate a monitoring node, judges the bandwidth statistical information change of the interface, immediately packages RPC response if the interface packet receiving statistical information exceeds 80% of the bandwidth, informs a fault management system of monitoring event occurrence, organizes the information by the service function module, sends the information to the GRPC server, and the GRPC server finds the RPC connection requesting the information, sends the information out and finally reaches the fault management system. Since only the states of interest to the management software system are monitored, resources and traffic are saved.
And 8: after receiving the RPC response, the fault management software reads the execution information configured by the user when the exception occurs, and informs the device to adjust the bandwidth of the tunnel interface IF1 through the management interface, so as to increase the 5G bandwidth.
And step 9: after receiving the information, NETCONF server in the protocol stack system distributes the information to a specific service function module, namely an interface management module, according to the yang model, and the interface management module immediately adjusts the bandwidth of the tunnel interface IF1 and increases the 5G bandwidth.
Step 10: and when the fault management system is abnormally restarted, automatically loading user configuration, re-entering the step 6, sending the monitoring requirement to the protocol stack system, and recovering the management function.
An embodiment of the present disclosure further provides a configuration method of a network device management system, configured to perform initialization configuration on the network device management system, as shown in fig. 10, where the method includes:
step S301 instantiates the fault management system in the container environment.
In the embodiment of the present disclosure, a container is created based on a host operating system (e.g., Linux native system) of a network device, and a fault management system is instantiated in the container to implement resource isolation between the fault management system and other functional modules in the network device, where the creation of the container and the instantiation of the system in the container belong to conventional technical means in the art, and details of the disclosure are omitted.
And S302, configuring a communication interface for the protocol stack system based on the interface description language.
Step S303, establishing a communication network between the fault management system and the protocol stack system.
In the foregoing embodiment, the configuration process of the communication interface and the network connection establishment process between the fault management system and the protocol stack system have been described in step S102, and please refer to the related description in step S102, which is not described herein again.
According to the configuration method of the network device management system provided by the embodiment of the disclosure, the fault management system is operated in the container environment of the network device, and the protocol stack system is configured with the communication interface capable of communicating with the fault management system, so that resource isolation between the fault management system and the host operating system of the network device is realized, the communication state of the network device is not affected by the operating state of the fault management system, and the stability of the performance of the network device is improved.
In some embodiments, the communication interface comprises: a Network Configuration Protocol Server (NETCONF Server for short) interface and a Remote Procedure Call Server (G Remote Procedure Call Server for short) interface, where the Network Configuration Protocol Server interface can be used as a management plane interface and the Remote Procedure Call Server interface can be used as a control plane interface.
An embodiment of the present disclosure further provides a network device management system, as shown in fig. 1, the system includes: a fault management system 1 and a protocol stack system 2; wherein the fault management system 1 is instantiated in a container environment; the protocol stack system 2 is provided with a communication interface for communicating with the fault management system 1.
An embodiment of the present disclosure further provides a network device, including: one or more processors and a storage device, wherein the storage device has at least one of a first program and a second program stored thereon, and when the first program is executed by the one or more processors, the one or more processors implement the steps in the network device management method with the fault management system as an execution subject provided by the embodiment of the disclosure; when the second program is executed by one or more processors, the one or more processors implement the steps in the network device management method with the protocol stack system as an execution subject provided by the embodiment of the present disclosure.
Of course, the network device may further store a third program, and when the third program is executed by one or more processors, the one or more processors implement the steps in the method for configuring a network device management system provided in the embodiment of the present disclosure.
The disclosed embodiments also provide a computer readable medium, on which a computer program is stored, where the program, when executed by a processor, implements the network device management method provided by the disclosed embodiments.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted in a generic and descriptive sense only and not for purposes of limitation. In some instances, features, characteristics and/or elements described in connection with a particular embodiment may be used alone or in combination with features, characteristics and/or elements described in connection with other embodiments, unless expressly stated otherwise, as would be apparent to one skilled in the art. Accordingly, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the disclosure as set forth in the appended claims.
Claims (10)
1. A network device management method applied to a fault management system side, wherein the management system runs in a container environment of a network device, the method comprising:
generating first control information;
and sending the first control information to a protocol stack system based on a communication interface configured by the protocol stack system.
2. The method of claim 1, wherein the first control information comprises: at least one of configuration event information, subscription event information, and repair event information.
3. The method of claim 2, wherein when the first control information includes repair event information, after the step of sending the first control information to the protocol stack system according to the communication interface of the protocol stack system, further comprising:
receiving repair response information fed back by the protocol stack system based on the communication interface;
acquiring a preset repair strategy corresponding to the repair event information;
sending the repair policy to the protocol stack system based on the communication interface.
4. The method of claim 1, wherein the method further comprises:
responding to a restart completion instruction, and acquiring pre-stored user management information;
and generating second control information based on the user management information, and sending the second control information to the protocol stack system based on the communication interface.
5. A network device management method is applied to a protocol stack system side, wherein the method comprises the following steps:
receiving first control information sent by a fault management system operating in a container environment based on a communication interface configured by the fault management system;
and managing the network equipment according to the first control information.
6. The method of claim 5, wherein the first control information comprises: at least one of configuration event information, subscription event information, and repair event information.
7. The method of claim 6, wherein when the first control information comprises: when the event information is repaired, the step of controlling and managing the network device according to the first control information specifically includes:
collecting target monitoring data in real time according to a monitoring data collection strategy in the repair event information;
if the collected target monitoring data meets the repair triggering condition in the repair event information, generating repair response information, and feeding back the repair response information to the fault management system through the communication interface;
receiving a repair strategy sent by the fault management system;
and controlling the network equipment to execute the repair operation according to the repair strategy.
8. A network device management system, comprising: a fault management system and a protocol stack system;
the fault management system is instantiated in a container environment;
the protocol stack system is configured with a communication interface for communicating with the fault management system.
9. A network device, comprising:
one or more processors;
storage means having stored thereon a first program and/or a second program which, when executed by the one or more processors, causes the one or more processors to carry out the steps of the method according to any one of claims 1-4; when executed by the one or more processors, cause the one or more processors to implement the steps in the method of any one of claims 5-7.
10. A computer-readable medium, on which a computer program is stored, which program, when being executed by a processor, carries out the steps of the method according to any one of claims 1-7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911396966.0A CN113132127A (en) | 2019-12-30 | 2019-12-30 | Network equipment management method, system and network equipment |
| PCT/CN2020/141316 WO2021136358A1 (en) | 2019-12-30 | 2020-12-30 | Network device management method and system, and network device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911396966.0A CN113132127A (en) | 2019-12-30 | 2019-12-30 | Network equipment management method, system and network equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113132127A true CN113132127A (en) | 2021-07-16 |
Family
ID=76687094
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911396966.0A Pending CN113132127A (en) | 2019-12-30 | 2019-12-30 | Network equipment management method, system and network equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113132127A (en) |
| WO (1) | WO2021136358A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023164916A1 (en) * | 2022-03-04 | 2023-09-07 | 新华三技术有限公司 | Network device management method, system and apparatus |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101110822A (en) * | 2007-07-06 | 2008-01-23 | 华为技术有限公司 | Event notice sending method, system and equipment based on network configuration protocol |
| CN102420697A (en) * | 2011-09-07 | 2012-04-18 | 北京邮电大学 | Service-configurable comprehensive resource monitoring managing system and method |
| US20170205791A1 (en) * | 2014-07-18 | 2017-07-20 | Samsung Electronics Co., Ltd. | Home appliance and control method for the same |
| US20180131745A1 (en) * | 2016-11-04 | 2018-05-10 | Google Inc. | Network Management Interface |
| CN109245953A (en) * | 2018-11-22 | 2019-01-18 | 新华三技术有限公司 | A kind of network collocating method and device |
| US20190245740A1 (en) * | 2018-02-07 | 2019-08-08 | Mavenir Networks, Inc. | Management of radio units in cloud radio access networks |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6611867B1 (en) * | 1999-08-31 | 2003-08-26 | Accenture Llp | System, method and article of manufacture for implementing a hybrid network |
| CN101072129A (en) * | 2007-06-25 | 2007-11-14 | 北京邮电大学 | JMX based network service management method and its application system |
| CN102739428B (en) * | 2011-04-15 | 2014-08-13 | 中兴通讯股份有限公司 | Method and device for data acquisition, and system |
| CN109495331B (en) * | 2017-09-11 | 2020-09-11 | 大唐移动通信设备有限公司 | System monitoring method and device of network management system |
-
2019
- 2019-12-30 CN CN201911396966.0A patent/CN113132127A/en active Pending
-
2020
- 2020-12-30 WO PCT/CN2020/141316 patent/WO2021136358A1/en active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101110822A (en) * | 2007-07-06 | 2008-01-23 | 华为技术有限公司 | Event notice sending method, system and equipment based on network configuration protocol |
| CN102420697A (en) * | 2011-09-07 | 2012-04-18 | 北京邮电大学 | Service-configurable comprehensive resource monitoring managing system and method |
| US20170205791A1 (en) * | 2014-07-18 | 2017-07-20 | Samsung Electronics Co., Ltd. | Home appliance and control method for the same |
| US20180131745A1 (en) * | 2016-11-04 | 2018-05-10 | Google Inc. | Network Management Interface |
| US20190245740A1 (en) * | 2018-02-07 | 2019-08-08 | Mavenir Networks, Inc. | Management of radio units in cloud radio access networks |
| CN109245953A (en) * | 2018-11-22 | 2019-01-18 | 新华三技术有限公司 | A kind of network collocating method and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023164916A1 (en) * | 2022-03-04 | 2023-09-07 | 新华三技术有限公司 | Network device management method, system and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021136358A1 (en) | 2021-07-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3758293A1 (en) | Service upgrade management method, apparatus, and storage medium | |
| WO2018153185A1 (en) | Method for enabling automation of management and orchestration of network slices | |
| US11658870B2 (en) | Method and apparatus for restoring network device to factory defaults, and network device | |
| CN112399455B (en) | Lora gateway control method and Lora communication system | |
| JP2012053882A (en) | Method and system for processing a scheduling task in device management | |
| KR102005361B1 (en) | Cloud-Based Terminal Integrating Management System Using OTA Technique of IoT Terminal Over LPWA Network | |
| CN112328274A (en) | Software upgrading control method and system, server and intelligent terminal equipment | |
| CN112073555A (en) | Method for configuring IP address, electronic device and computer readable storage medium | |
| WO2021136358A1 (en) | Network device management method and system, and network device | |
| CN109391982B (en) | Information packet generation method, arrangement management method, network element and storage medium | |
| CN114268938A (en) | Method, device, equipment and storage medium for managing user front equipment | |
| CN111966519B (en) | Method, device, equipment and readable medium for adjusting log level | |
| WO2024103943A1 (en) | Service processing method and apparatus, storage medium, and device | |
| CN112394675B (en) | Monitoring system, method and server for rail transit | |
| CN111857763B (en) | Data processing method, device, electronic equipment and storage medium | |
| CN105072185A (en) | TR069 (Technical Report 069) remote monitoring method and system, and communication equipment | |
| US11822952B2 (en) | Managing downtime to networking managers during configuration updates in cloud computing environments | |
| CN113949631A (en) | Client disaster tolerance processing method and system and electronic equipment | |
| EP3713261A1 (en) | Aggression management for a mobile device | |
| CN112311570A (en) | Method and device for opening network equipment | |
| CN113472599B (en) | Data communication method and system of network node | |
| CA2972558C (en) | Method and device for upgrading multi-dwelling unit | |
| CN114143905B (en) | Session establishing method, communication system, electronic device and storage medium | |
| CN114710494B (en) | Application management method, device and storage medium | |
| CN118260092A (en) | Computing power distribution method and device, seed server and multi-element computing power service cluster |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210716 |