WO2021136358A1 - 网络设备管理方法、系统及网络设备 - Google Patents

网络设备管理方法、系统及网络设备 Download PDF

Info

Publication number
WO2021136358A1
WO2021136358A1 PCT/CN2020/141316 CN2020141316W WO2021136358A1 WO 2021136358 A1 WO2021136358 A1 WO 2021136358A1 CN 2020141316 W CN2020141316 W CN 2020141316W WO 2021136358 A1 WO2021136358 A1 WO 2021136358A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
repair
information
protocol stack
management system
Prior art date
Application number
PCT/CN2020/141316
Other languages
English (en)
French (fr)
Inventor
陈娟娟
张丽晖
耿兴元
萧宇青
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2021136358A1 publication Critical patent/WO2021136358A1/zh

Links

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

Definitions

  • the embodiments of the present disclosure relate to the field of communication technologies, and in particular, to a network device management method, system, network device, and computer-readable medium.
  • the existing network equipment management method usually builds a fault management system into the protocol stack system of the network equipment.
  • Network equipment is managed, that is, the fault management system exists as a functional module in the protocol stack system. This method will cause the fault management system to easily affect the communication and system performance of the network equipment.
  • the present disclosure at least to some extent solves one of the technical problems existing in some situations.
  • the embodiments of the present disclosure provide a network device management method, system, network device, and computer-readable medium.
  • the present disclosure provides a network device management method, which is applied to the fault management system side, wherein the management system runs in a container environment of the network device, and the method includes: generating first control information; based on a protocol The communication interface configured by the stack system sends the first control information to the protocol stack system.
  • the present disclosure also provides a network device management method, applied to the protocol stack system side, the method includes: receiving a first control sent by a fault management system running in a container environment based on a communication interface configured by itself Information; manage the network device according to the first control information.
  • 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 to communicate with the fault management system Communication interface for communication.
  • the present disclosure provides a network device, including: one or more processors; a storage device, on which a first program and/or a second program are stored, when the first program is used by the one or more Executed by two processors, so that the one or more processors implement the steps in the network device management method provided in 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 in the second aspect of the present disclosure.
  • the present disclosure provides a computer-readable medium on which a computer program is stored, wherein the program is executed by a processor to implement the steps in the network device management method provided in the first and second aspects of the present disclosure .
  • Fig. 1 is a schematic structural diagram of a network device management system provided by the present disclosure.
  • FIG. 2 is a flowchart of a network device management method provided by an embodiment of the disclosure
  • FIG. 3 is a flowchart of another network device management method provided by an embodiment of the disclosure.
  • FIG. 4 is a flowchart of another network device management method provided by an embodiment of the disclosure.
  • FIG. 5 is a flowchart of yet another network device management method provided by an embodiment of the present disclosure.
  • FIG. 6 is a flowchart of yet another network device management method provided by an embodiment of the present disclosure.
  • FIG. 7 is a flowchart of yet another network device management method provided by an embodiment of the present disclosure.
  • FIG. 8 is a flowchart of yet another network device management method provided by an embodiment of the present disclosure.
  • FIG. 9 is a flowchart of yet another network device management method provided by an embodiment of the present disclosure.
  • FIG. 10 is a flowchart of a configuration method of a network device management system provided by an embodiment of the disclosure.
  • the network device management method provided by the present disclosure is used to manage network devices.
  • information about the network device is configured, part of the status data of the network device is subscribed and inquired, and the network device is monitored for failure, and automatically after a failure occurs Repair according to the preset strategy and so on.
  • the network device management method provided by the present disclosure is implemented based on a network device management system, as shown in FIG. 1, which shows a schematic structural diagram of the network device management system provided by the present disclosure.
  • the network device management system includes a fault management system 1 With the protocol stack system 2, the two communicate through a preset communication interface to realize the management of the network equipment.
  • the fault management system 1 runs in the container environment of the network device
  • the protocol stack system 2 runs in the host operating system of the network device.
  • the container environment is relative to the host operating system of the network device (for example, The Linux native system) is independent, so that the resource isolation between the fault management system and other functional modules (such as the protocol stack system) in the network device can be realized.
  • the following describes the network device management method provided by the present disclosure with the fault management system 1 and the protocol stack system 2 as the executive bodies respectively.
  • FIG. 2 is a flowchart of a network device management method provided by an embodiment of the present disclosure.
  • the method uses the fault management system 1 as the execution body. As shown in FIG. 2, the method includes:
  • Step S101 Generate first control information.
  • the first control information refers to the information used by the user to control and manage the network device.
  • the first control information may include configuration event information or subscription event information, etc., wherein the configuration event information indicates that the user will The network device performs configuration operations, and the subscription event information indicates that the user will subscribe to certain operating data of the network device.
  • the embodiment of the present disclosure does not limit the type of the first control information, as long as it can characterize the user's control and management of the network device. It belongs to the scope of protection of this disclosure.
  • the first control information may be automatically generated by the fault management system after receiving the management information input by the user.
  • Step S102 Send the first control information to the protocol stack system based on the communication interface configured by the protocol stack system.
  • Stack system also known as protocol stack system, implemented by software computer network protocol suite.
  • the protocol stack system is specifically configured with a communication interface capable of communicating with the fault management system, which can implement the fault management system and protocol Network communication between stack systems.
  • the communication interface may include: a management plane interface and a control plane interface, and users can call different interfaces for data transmission based on their own needs.
  • the communication interface can be set by the user based on the user's needs.
  • the communication interface may include: an interface of a network configuration protocol server (Network Configuration Protocol Server, referred to as NETCONF server) and an interface of a remote procedure call server (Google Remote Procedure Call Protocol server, referred to as GRPC server), where , NETCONF server and GRPC server are two servers set in the protocol stack system.
  • NETCONF server and GRPC server are two servers set in the protocol stack system.
  • NETCONF server and GRPC server are two servers set in the protocol stack system.
  • the corresponding clients are set in the fault management system.
  • IDL interface description language
  • the NETCONF server interface can be used as a management plane interface
  • the GRPC server interface can be used as a control plane interface. That is, the management plane interface provides external services through the NETCONF server, and the control plane interface provides external services through the GRPC server.
  • the network connection between the fault management system and the protocol stack system can be realized based on the IP address, that is, the interface of the server and the interface of the client can be interconnected based on the IP address.
  • the NETCONF server and GRPC server in the protocol stack system respectively create their own communication address IP1 and communication address IP2 as their own communication flags
  • the NETCONF client and GRPC client in the fault management system create the communication address IP3.
  • the fault management system can establish a network link through the communication address IP3 and the communication address IP1 and IP2 of the protocol stack system, so that the fault management system can be used
  • the management plane interface and control plane interface provided by the protocol stack system.
  • the network device management method provided by the embodiment of the present disclosure runs the fault management system in the container environment of the network device, and configures the protocol stack system with a communication interface capable of communicating with the fault management system, and the fault management system uses the communication interface to communicate with the fault management system.
  • a control information is sent to the protocol stack system to manage the network device.
  • the network device management method provided by the embodiments of the present disclosure realizes the resource isolation between the fault management system and the host operating system of the network device, thereby causing the fault The operating status of the management system will not affect the communication status of the network equipment, thereby improving the stability of the performance of the network equipment.
  • FIG. 3 is a flowchart of another network device management method provided by an embodiment of the present disclosure.
  • the first control information includes: configuration Event information.
  • the configuration event information includes: a configuration strategy.
  • the configuration event information is used to describe that the user will perform certain configurations on certain functional modules of the network device.
  • the configuration strategy depends on the functional modules configured by the user. Therefore, the present disclosure does not limit the form of the configuration strategy.
  • step S102 includes:
  • Step S1021 Send the first control information to the protocol stack system based on the communication interface, so that the protocol stack system configures the network device according to the configuration strategy.
  • the communication interface selects the management plane interface.
  • the protocol stack system After receiving the first control information, the protocol stack system sends the configuration event information to the corresponding functional module in the protocol stack system according to the configuration event information. After receiving the first control information, the functional module sends the configuration event information according to the configuration event information.
  • the configuration strategy automatically configures information.
  • FIG. 4 is a flowchart of another network device management method provided by an embodiment of the present disclosure.
  • the first control information Including: subscribing to event information; at this time, after step S102, it also includes:
  • Step S103 Receive subscription response information fed back by the protocol stack system based on the communication interface.
  • the subscription event information is used to describe that the user will obtain certain dynamic data of the network device.
  • the subscription event information includes: a subscription information collection strategy, and the fault management system subscribes to the event information based on the communication interface
  • the protocol stack system sends the subscription event information to the corresponding functional module according to the subscription event information.
  • the functional module collects the corresponding target data according to the subscription information collection strategy, where the subscription The information collection strategy can include information such as the type of target data to be collected and collection requirements.
  • this functional module packs the target data and generates subscription response information.
  • the subscription response information includes the target data and subscribes
  • the response information is fed back to the fault management system based on the communication interface, and the fault management system receives the subscription response information and feeds it back to the user for the user to consult.
  • the communication interface selects a control plane interface.
  • the user can subscribe to the dynamic data of the equipment he is interested in based on the fault management system, so that the different needs of different users can be met, and the user can avoid manual screening from massive data.
  • FIG. 5 is a flowchart of another network device management method provided by the implementation of the present disclosure.
  • the first control information includes: repair Event information, the repair event information is used to describe that the user will track and repair certain failures of the network device.
  • the repair event information is used to describe that the user will track and repair certain failures of the network device.
  • it may include:
  • Step S103' receiving repair response information fed back by the protocol stack system based on the communication interface.
  • Step S104' Obtain a preset repair strategy corresponding to the repair event information.
  • Step S105' Send the repair strategy to the protocol stack system based on the communication interface.
  • the protocol stack system sends the repair event information to the corresponding functional module, and each functional module is monitored according to the monitoring contained in the repair event information.
  • the data collection strategy collects target monitoring data in real time, and determines whether the target monitoring data meets the repair trigger conditions contained in the repair event information.
  • the target monitoring data is used to characterize the abnormal state of the network equipment. When it is determined that the target monitoring data meets When repairing the trigger condition, it means that the network device is currently experiencing abnormal state characteristics.
  • 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 based on the communication interface Information (step S103'), and obtain the pre-stored repair strategy corresponding to the repair event information (step S104').
  • the repair strategy is pre-configured by the user in the fault management system and can be saved by the fault management system ,
  • the repair strategy includes the repair operations that should be used when the device is in a certain abnormal state.
  • the fault management system After obtaining the repair strategy, the fault management system sends the repair strategy to the protocol stack system based on the communication interface (step S105'), the protocol stack system After receiving the repair strategy, the network device is controlled to perform a corresponding repair operation according to the repair strategy to repair the abnormality of the network device.
  • the communication interface selects a control plane interface.
  • the fault management module can generate the first control information based on the following methods: 1) The user inputs the management information in the fault management system based on web page configuration and command line configuration, and the fault management system is configured according to the web page Information and command line configuration information to generate the first control information; 2) The user uses the script language programming method, based on the communication interface (management plane interface and control plane interface) of the protocol stack system, and enters the management information for the fault management system to follow The written program block generates the first control information, where the script language can be PYTHON, JAVA, C, GO language, etc.; 3) The management model is preset in the fault management system, and each management model is defined with model parameters. When the user needs to manage the network equipment, he can choose the applicable model to fill in. After the fault management system receives the management model filled in by the user, it automatically generates the first control information according to the relevant parameters of the management model.
  • the method further includes: in response to a restart completion instruction, obtaining pre-stored user management information; generating second control information based on the user management information, and controlling the second control information based on the communication interface
  • the information is sent to the protocol stack system. It should be noted that after the user enters the management information, the fault management system will automatically save the management information entered by the user, and after the fault management system is restarted due to a fault or artificially restarted, the stored management information will be retrieved and generated based on the user management information
  • the second control information is further sent to the protocol stack system based on the communication interface. It should be noted that the "first" and “second” in the "second control information" and the aforementioned "first control information" are only used as distinguishing identifiers.
  • the restart of the fault management system will not affect the communication activities performed on the main operating system of the network device, and because the fault management system is pre-stored With the management information input by the user, the restarted fault management system can quickly re-manage the network equipment based on the user's intention.
  • the following describes the network device management method provided by the present disclosure with the protocol stack system as the executive body.
  • FIG. 6 is a flowchart of another network device management method provided by an embodiment of the disclosure. As shown in FIG. 6, the method includes:
  • Step S201 Based on the communication interface configured by itself, receive the first control information sent by the fault management system running in the container environment.
  • step S201 corresponds to step S102 in the above-mentioned embodiment. Therefore, please refer to the description of step S102, which will not be repeated here.
  • Step S202 Manage the network device according to the first control information.
  • the protocol stack system After receiving the first control information, the protocol stack system performs corresponding management on the network equipment according to the event type contained in the first control information.
  • the network device management method provided by the embodiment of the present disclosure runs the fault management system in the container environment of the network device, and configures the protocol stack system with a communication interface capable of communicating with the fault management system, and the fault management system uses the communication interface to communicate with the fault management system.
  • a control information is sent to the protocol stack system to manage the network device.
  • the network device management method provided by the embodiments of the present disclosure realizes the resource isolation between the fault management system and the host operating system of the network device, thereby causing the fault The operating status of the management system will not affect the communication status of the network equipment, thereby improving the stability of the performance of the network equipment.
  • FIG. 7 is a flowchart of yet another network device management method provided by an embodiment of the disclosure.
  • the first control information includes: configuration information.
  • the configuration information Including: configuring a strategy.
  • step S202 includes:
  • Step S2021 Perform corresponding configuration on the network device according to the configuration strategy.
  • the network device management method provided by the embodiment of the present disclosure corresponds to the steps of the method shown in FIG. 3. Please refer to the description of the corresponding steps in the method shown in FIG. 3, which will not be repeated here.
  • FIG. 8 is a flowchart of another network device management method provided by an embodiment of the present disclosure.
  • the first control information includes: subscription event information.
  • subscription event The information includes: a subscription information collection strategy.
  • step S202 includes:
  • Step S2021' collecting target data corresponding to the subscription event information.
  • Step S2022' Generate subscription response information based on the target data.
  • Step S2023' feedback the subscription response information to the fault management system through the communication interface.
  • the network device management method provided by the embodiment of the present disclosure corresponds to the steps of the method shown in FIG. 4, please refer to the description of the corresponding steps in the method shown in FIG. 4, which will not be repeated here.
  • FIG. 9 is a flowchart of another network device management method provided by an embodiment of the disclosure.
  • the first control information includes: repair event information; in some embodiments, repair event The information includes: monitoring data collection strategy and repair trigger conditions.
  • step S202 includes:
  • Step S2021 collecting target monitoring data in real time according to the monitoring data collection strategy.
  • Step S2022 it is judged whether the target monitoring data meets the repair trigger condition.
  • step S2023 is executed, and when it is determined that the target monitoring data meets the repair trigger condition, then return to continue to perform step S2021".
  • Step S2023 generating repair response information, and feedback the repair response information to the fault management system through the communication interface.
  • Step S2024" receiving the repair strategy sent by the fault management system.
  • Step S2025" control the network device to perform the repair operation according to the repair strategy.
  • the network device management method provided by the embodiment of the present disclosure corresponds to the steps of the method shown in FIG. 5, please refer to the description of the corresponding steps in the method shown in FIG. 5, which will not be repeated here.
  • the following uses scenarios to assist in describing the network device management method provided by the present disclosure.
  • Step 1 Enable the proxy service module, protocol stack system, and container system in the network device, and open the communication link between the protocol stack system and the container system through the proxy service module.
  • Step 2 Create communication address IP1 in the protocol stack system, configure it as NETCONF server, create communication address IP2, and configure it as the server address of GRPC server, the management plane interface provides external services through NETCONF server, and the control plane interface through GRPC server Provide services to the outside world.
  • Step 3 Each service function module in the protocol stack system registers with the NETCONF server and GRPC server the set of management plane interface capabilities and control plane interface capabilities provided to the outside.
  • Step 4 Start the NETCONF client and GRPC client in the fault management system, and create the address IP3; the fault management system establishes a connection with the NETCONF server and GRPC server in the protocol stack system through IP3, and establishes a communication channel for network element management operations. This channel is established After success, the fault management system can call the management plane interface and control plane interface provided by the protocol stack system. The call interface is generated by the automatic conversion tool and the development package is pre-installed in the container where the fault management system is located. The fault management system can be directly accessed and called.
  • Step 5 The user configuration requires monitoring the statistics of received packets of the tunnel interface IF1 in the device, and when the monitored packets exceed 80% of the bandwidth of the tunnel interface, adjust the tunnel bandwidth to increase the specified value by 5G.
  • Step 6 After the fault management system reads the configuration, it initiates an RPC (Romote Procedure Call, RPC for short) request according to the interface identifier of the control plane interface, and publishes the monitoring requirements to the protocol stack system.
  • RPC Remote Procedure Call
  • Step 7 After the GRPC server in the protocol stack system receives the information, it distributes it to the business function module-the interface management module according to the interface registration information.
  • the interface management module parses the information, generates a monitoring node, and changes the bandwidth statistics of the interface. Judging, if the interface packet statistics information exceeds 80% of the bandwidth, the RPC response is immediately encapsulated to notify the fault management system that the monitoring event has occurred.
  • the information is organized by the business function module and sent to the GRPC server.
  • the GRPC server finds the RPC connection requesting the information, and will The information is sent out and finally arrives at the fault management system. Since only the state of interest of the management software system is monitored, resources and communication are saved.
  • Step 8 After the fault management software receives the RPC response, it reads the execution information configured by the user when the exception occurs, and informs the device through the management plane interface to adjust the bandwidth of the tunnel interface IF1 to increase the 5G bandwidth.
  • Step 9 After receiving the information, the NETCONF server in the protocol stack system distributes the information to the service function module—the interface management module according to the yang model.
  • the interface management module immediately adjusts the bandwidth of the tunnel interface IF1 to increase the 5G bandwidth.
  • Step 10 When the fault management system restarts abnormally, the user configuration will be automatically loaded, and step 6 will be re-entered to issue the monitoring requirements to the protocol stack system, and the management function will resume.
  • the embodiment of the present disclosure also provides a configuration method of the network device management system, which is used to initialize the configuration of the network device management system. As shown in FIG. 10, the method includes:
  • Step S301 Instantiate the fault management system in the container environment.
  • a container is created based on the host operating system of the network device (for example, a Linux native system), and a fault management system is instantiated in the container to realize resource isolation between the fault management system and other functional modules in the network device.
  • the creation of the container and the instantiation of the system in the container belong to the conventional technical means in the field, and will not be repeated in this disclosure.
  • Step S302 Configure a communication interface for the protocol stack system based on the interface description language.
  • Step S303 Establish a communication network between the fault management system and the protocol stack system.
  • step S102 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. Please refer to the related description in step S102, which will not be repeated here.
  • the configuration method of the network device management system runs the fault management system in the container environment of the network device, and configures the protocol stack system with a communication interface capable of communicating with the fault management system, thereby realizing the fault management system It is isolated from the resources of the host operating system of the network device, so that the operating state of the fault management system will not affect the communication state of the network device, and the stability of the performance of the network device is improved.
  • the communication interface includes: a network configuration protocol server (Network Configuration Protocol Server, referred to as NETCONF server) interface and a remote procedure call server (G Remote Procedure Call Protocol server, referred to as GRPC server) interface, where the network configuration
  • NETCONF server Network Configuration Protocol Server
  • GRPC server Remote Procedure Call Protocol server
  • the protocol server interface can be used as a management plane interface
  • the remote procedure call server interface can be used as a control plane interface.
  • the embodiment of the present disclosure also provides a network equipment management system.
  • 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; and the protocol stack system 2 A communication interface for communicating with the fault management system 1 is configured.
  • the embodiment of the present disclosure also provides a network device, including: one or more processors and a storage device, wherein at least one of a first program and a second program is stored on the storage device. Multiple processors execute, so that the one or more processors implement the steps in the network device management method with the fault management system as the execution subject provided by the embodiments of the present disclosure; when the second program is executed by one or more processors, The one or more processors are enabled to implement the steps in the network device management method with the protocol stack system as the execution subject provided by the embodiments of the present disclosure.
  • a third program may also be stored in the network device.
  • the third program is executed by one or more processors, the one or more processors can implement the steps in the configuration method of the network device management system provided by the embodiments of the present disclosure. step.
  • the embodiment of the present disclosure further provides a computer-readable medium on which a computer program is stored, where the program is executed by a processor to implement the network device management method provided by the embodiment of the present disclosure.
  • the network device management method, system, network device, and computer readable medium provided by the embodiments of the present disclosure run the fault management system in the container environment of the network device, and configure the protocol stack system with a communication interface capable of communicating with the fault management system
  • the fault management system sends the first control information to the protocol stack system based on the communication interface to manage the network equipment.
  • the network equipment management method provided by the embodiments of the present disclosure realizes the connection between the fault management system and the network equipment.
  • the resource isolation of the host operating system makes the operating state of the fault management system not affect the communication state of the network device, thereby improving the stability of the performance of the network device.
  • Such software may be distributed on a computer-readable medium
  • the computer-readable medium may include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium).
  • the term computer storage medium includes volatile and non-volatile data implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data).
  • Information such as computer-readable instructions, data structures, program modules, or other data.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or Any other medium used to store desired information and that can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media. .

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

一种网络设备管理方法，应用于故障管理系统侧，其中，所述管理系统运行于网络设备的容器环境内。网络设备管理方法包括：生成第一控制信息(S101)；基于协议栈系统所配置的通信接口将所述第一控制信息发送至所述协议栈系统(S102)。

Description

网络设备管理方法、系统及网络设备
相关申请的交叉引用
本申请基于申请号为201911396966.0、申请日为2019年12月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开实施例涉及通信技术领域，特别涉及一种网络设备管理方法、系统、网络设备及计算机可读介质。
背景技术
随着网络规模的日益庞大，能否对网络设备进行有效管理给运维人员带来不小的压力，现有的网络设备管理方法通常是在网络设备的协议栈系统中内置故障管理系统来对网络设备进行管理，即故障管理系统作为协议栈系统中的一个功能模块而存在，这种方法会导致故障管理系统易对网络设备的通信及系统性能造成影响。
发明内容
本公开至少在一定程度上解决在一些情形下存在的技术问题之一，本公开实施例提供一种网络设备管理方法、系统、网络设备及计算机可读介质。
第一方面，本公开提供了一种网络设备管理方法，应用于故障管理系统侧，其中，所述管理系统运行于网络设备的容器环境内，所述方法包括：生成第一控制信息；基于协议栈系统所配置的通信接口将所述第一控制信息发送至所述协议栈系统。
第二方面，本公开还提供一种网络设备管理方法，应用于协议栈系统侧，所述方法包括：基于自身所配置的通信接口，接收运行于容器环境中的故障管理系统发送的第一控制信息；根据所述第一控制信息对网络设备进行管理。
第三方面，本公开提供一种网络设备管理系统，包括：故障管理系统和协议栈系统；所述故障管理系统实例化于容器环境中；所述协议栈系统配置有与所述故障管理系统进行通信的通信接口。
第四方面，本公开提供一种网络设备，包括：一个或多个处理器；存储装置，其上存 储有第一程序和/或第二程序，当所述第一程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现本公开第一方面提供的网络设备管理方法中的步骤；当所述第二程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现本公开第二方面提供的网络设备管理方法中的步骤。
第五方面，本公开提供一种计算机可读介质，其上存储有计算机程序，其中，所述程序被处理器执行时实现本公开第一方面和第二方面提供的网络设备管理方法中的步骤。
附图说明
附图用来提供对本公开实施例的进一步理解，并且构成说明书的一部分，与本公开的实施例一起用于解释本公开，并不构成对本公开的限制。通过参考附图对详细示例实施例进行描述，以上和其他特征和优点对本领域技术人员将变得更加显而易见，在附图中：
图1为本公开提供的一种网络设备管理系统的结构示意图。
图2为本公开实施例提供的一种网络设备管理方法的流程图；
图3为本公开实施例提供的另一种网络设备管理方法的流程图；
图4为本公开实施例提供的又一种网络设备管理方法的流程图；
图5为本公开实施例提供的再一种网络设备管理方法的流程图；
图6为本公开实施例提供的再一种网络设备管理方法的流程图；
图7为本公开实施例提供的再一种网络设备管理方法的流程图；
图8为本公开实施例提供的再一种网络设备管理方法的流程图；
图9为本公开实施例提供的再一种网络设备管理方法的流程图；
图10为本公开实施例提供的一种网络设备管理系统的配置方法的流程图。
具体实施方式
为使本领域的技术人员更好地理解本发明的技术方案，下面结合附图对本发明提供的一种网络设备管理方法、系统、网络设备及计算机可读介质进行详细描述。
在下文中将参考附图更充分地描述示例实施例，但是所述示例实施例可以以不同形式来体现且不应当被解释为限于本文阐述的实施例。反之，提供这些实施例的目的在于使本公开透彻和完整，并将使本领域技术人员充分理解本公开的范围。
本文所使用的术语仅用于描述特定实施例，且不意欲限制本公开。如本文所使用的， 单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。还将理解的是，当本说明书中使用术语“包括”和/或“由……制成”时，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加一个或多个其他特征、整体、步骤、操作、元件、组件和/或其群组。
将理解的是，虽然本文可以使用术语第一、第二等来描述各种元件/指令/请求，但这些元件/指令/请求不应当受限于这些术语。这些术语仅用于区分一个元件/指令/请求和另一元件/指令/请求。
除非另外限定，否则本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本文明确如此限定。
本公开提供的网络设备管理方法用于对网络设备进行管理，在一些实施例中，配置网络设备的信息、订阅查询网络设备的部分状态数据以及监控网络设备是否发生故障，并在发生故障后自动按照预设策略进行修复等等。本公开提供的网络设备管理方法基于一种网络设备管理系统实现，如图1所示，图1示出了本公开提供的网络设备管理系统的结构示意图，该网络设备管理系统包括故障管理系统1和协议栈系统2，二者通过基于预设的通信接口进行交互通信以实现对网络设备的管理。需要特别说明的是，本公开中，故障管理系统1运行于网络设备的容器环境内，协议栈系统2运行于网络设备的主机操作系统内，该容器环境相对于网络设备的主机操作系统(例如Linux原生系统)是独立的，从而可实现故障管理系统与网络设备内的其他功能模块(例如协议栈系统)的资源隔离。
下面将分别以故障管理系统1和协议栈系统2作为执行主体来对本公开提供的网络设备管理方法进行描述。
图2为本公开实施例提供的一种网络设备管理方法的流程图，该方法以故障管理系统1作为执行主体，如图2所示，该方法包括：
步骤S101、生成第一控制信息。
本公开中，第一控制信息是指用户对网络设备进行控制管理的信息，在一些实施例中，第一控制信息可以包括配置事件信息或订阅事件信息等，其中，配置事件信息表征用户将 要对网络设备进行配置操作，订阅事件信息表征用户将要对网络设备进行某些运行数据的订阅，本公开实施例不对第一控制信息的种类进行限定，只要能表征用户对网络设备进行控制管理的信息皆属于本公开保护的范围。
在实际应用中，第一控制信息可由故障管理系统在接收到用户输入的管理信息后自动生成。
步骤S102、基于协议栈系统所配置的通信接口将第一控制信息发送至协议栈系统。
协议栈系统，又称协议堆叠系统，由计算机 网络协议套件的软件实现。本公开中，因故障管理系统运行于独立于网络设备主机操作系统的容器环境中，因而协议栈系统专门配置有能够与故障管理系统进行通信的通信接口，该通信接口可实现故障管理系统与协议栈系统之间的网络通信。在一些实施例中，通信接口可包括：管理面接口和控制面接口，用户可基于自身需求来调用不同的接口以进行数据传输。
本公开中，通信接口可基于用户的需求由用户自行进行设置。在一些实施例中，通信接口可包括：网络配置协议服务端(Network Configuration Protocol Server，简称NETCONF server)的接口和远程过程调用服务端(Google Remote Procedure Call Protocol server，简称GRPC server)的接口，其中，NETCONF server和GRPC server为设置于协议栈系统内的两个服务端，对应的，在故障管理系统内设置对应的客户端(NETCONF client和GRPC client)，通过采用接口描述语言(Interface description language，简称IDL)来为服务端和客户端定义接口，并使用自动转换工具生成不同编程语言的开发接口，以供服务端和客户端直接使用。其中，NETCONF server的接口可作为管理面接口使用，GRPC server的接口可作为控制面接口使用，即是说，管理面接口通过NETCONF server对外提供服务，控制面接口通过GRPC server对外提供服务。
在实际应用中，故障管理系统与协议栈系统之间的网络连接可基于IP地址实现，即是说，服务端的接口和客户端的接口可基于IP地址实现互通。在一些实施例中，协议栈系统中的NETCONF server和GRPC server分别创建自身的通信地址IP1和通信地址IP2，以作为自身的通信标志，故障管理系统中的NETCONF client和GRPC client创建通信地址IP3，通过设置代理服务模块来为故障管理系统和协议栈系统进行配置协同，而使得故障管理系统能够通过通信地址IP3与协议栈系统的通信地址IP1和IP2建立起网络链接， 进而使故障管理系统能够使用协议栈系统提供的管理面接口和控制面接口。
本公开实施例提供的网络设备管理方法，将故障管理系统运行于网络设备的容器环境中，并为协议栈系统配置能够与故障管理系统进行通信的通信接口，故障管理系统基于该通信接口将第一控制信息发送至协议栈系统以对网络设备进行管理，相较于一些情形，本公开实施例提供的网络设备管理方法实现了故障管理系统与网络设备的主机操作系统的资源隔离，从而使得故障管理系统的运行状态不会对网络设备的通信状态造成影响，进而提升了网络设备性能的稳定性。
图3为本公开实施例提供的另一种网络设备管理方法的流程图，如图3所示，在一些实施例中，当用户仅对网络设备进行信息配置时，第一控制信息包括：配置事件信息，在一些实施例中，该配置事件信息中包括：配置策略，该配置事件信息用于描述用户将要对网络设备的某些功能模块进行某些配置，配置策略因用户所配置的功能模块的不同以及配置信息的不同而不同，因此，本公开不对配置策略的形式进行限定。对应的，此时，步骤S102包括：
步骤S1021、基于通信接口将第一控制信息发送至协议栈系统，以供协议栈系统根据配置策略对网络设备进行配置。
在一些实施例中，通信接口选择管理面接口。
协议栈系统在接收到第一控制信息后，根据配置事件信息，将配置事件信息下发至协议栈系统中对应的功能模块，该功能模块在接收到第一控制信息后，根据配置事件信息中的配置策略自动进行信息配置。
图4为本公开实施例提供的又一种网络设备管理方法的流程图，如图4所示，在一些实施例中，当用户需要获取网络设备的某些动态运行数据时，第一控制信息包括：订阅事件信息；此时，在步骤S102之后，还包括：
步骤S103、基于通信接口接收协议栈系统反馈的订阅响应信息。
本公开实施例中，订阅事件信息用于描述用户将要获取网络设备的某些动态数据，在一些实施例中，订阅事件信息中包括：订阅信息采集策略，故障管理系统基于通信接口将订阅事件信息发送至协议栈系统后，协议栈系统根据订阅事件信息将订阅事件信息发送至对应的功能模块，该功能模块在接收到订阅事件信息后，根据订阅信息采集策略采集相应 的目标数据，其中，订阅信息采集策略中可包括待采集的目标数据的类型和采集要求等信息，该功能模块在数据采集完毕后，将目标数据打包并生成订阅响应信息，该订阅响应信息中包括目标数据，并将订阅响应信息基于通信接口反馈至故障管理系统，故障管理系统接收订阅响应信息，并反馈至用户以便用户查阅。
在一些实施例中，通信接口选择控制面接口。
本公开实施例中，用户基于故障管理系统可对其感兴趣的设备动态数据进行订阅，从而可满足不同用户的不同需求，避免用户从海量的数据中进行人工筛选。
图5为本公开实施提供的再一种网络设备管理方法的流程图，如图5所示，在一些实施例中，当用户需要对网络设备进行故障定义跟踪时，第一控制信息包括：修复事件信息，该修复事件信息用于描述用户将要对网络设备的某些故障进行跟踪及修复，此时，在步骤S102之后可包括：
步骤S103’、基于通信接口接收协议栈系统反馈的修复响应信息。
步骤S104’、获取预设的与修复事件信息对应的修复策略。
步骤S105’、基于通信接口将修复策略发送至协议栈系统。
本公开实施例中，当故障管理系统基于通信接口向协议栈系统发送修复事件信息后，协议栈系统将修复事件信息发送至对应的功能模块，各该功能模块根据修复事件信息中所包含的监控数据采集策略实时采集目标监控数据，并判断该目标监控数据是否满足修复事件信息中所包含的修复触发条件，其中，目标监控数据用于表征网络设备的异常状态特征，当判断出目标监控数据满足修复触发条件时，则说明网络设备当前出现异常状态特征，此时协议栈系统生成修复响应信息，并通过通信接口将该修复响应信息反馈至故障管理系统，故障管理系统基于通信接口接收该修复响应信息(步骤S103’)，并获取预先存储的与该修复事件信息对应的修复策略(步骤S104’)，需要说明的是，修复策略由用户在故障管理系统中预先配置，可由故障管理系统进行保存，修复策略中包含了当设备处于某种异常状态时应当采用的修复操作，故障管理系统在获取到修复策略后，基于通信接口将修复策略发送至协议栈系统(步骤S105’)，协议栈系统接收到修复策略后，根据修复策略控制网络设备执行对应的修复操作，以修复网络设备的异常。
在一些实施例中，通信接口选择控制面接口。
在上述各实施例中，故障管理模块可基于以下几种方式来生成第一控制信息：1)用户基于web页面配置和命令行配置在故障管理系统中输入管理信息，故障管理系统根据web页面配置信息和命令行配置信息来生成第一控制信息；2)用户利用脚本语言编程的方式，基于协议栈系统的通信接口(管理面接口和控制面接口)，输入管理信息，以供故障管理系统根据所编写的程序块生成第一控制信息，其中，脚本语言可以是PYTHON，JAVA，C、GO语言等；3)在故障管理系统中预先设置管理模型，每个管理模型都定义有模型参数，当用户需要对网络设备进行管理时，可选择适用的模型进行填写，故障管理系统接收到用户填写的管理模型后，自动根据管理模型的相关参数生成第一控制信息。
在一些实施例中，所述方法还包括：响应于重启完成指令，获取预先存储的用户管理信息；基于所述用户管理信息生成第二控制信息，并基于所述通信接口将所述第二控制信息发送至所述协议栈系统。需要说明的是，用户输入管理信息后，故障管理系统会自动保存用户输入的管理信息，并在故障管理系统因故障重启或人为重启后，重新获取该存储的管理信息，并基于用户管理信息生成第二控制信息，进而基于通信接口将第二控制信息发送至协议栈系统。需要说明的是，“第二控制信息”及上述“第一控制信息”中的“第一”和“第二”仅作为区分标识使用。本公开实施例中，由于故障管理系统是运行于网络设备的容器环境中的，因而故障管理系统的重启不会影响网络设备主体操作系统上进行的通信活动，并且，由于故障管理系统内预先存储了用户输入的管理信息，因而重启后的故障管理系统能够快速重新基于用户意图来对网络设备进行管理。
下面以协议栈系统作为执行主体来对本公开所提供的网络设备管理方法进行描述。
图6为本公开实施例提供的再一种网络设备管理方法的流程图，如图6所示，该方法包括：
步骤S201、基于自身所配置的通信接口，接收运行于容器环境中的故障管理系统发送的第一控制信息。
本公开实施例中，步骤S201与上述实施例中步骤S102对应，因此，请参照步骤S102的描述，此处不再赘述。
步骤S202、根据第一控制信息对网络设备进行管理。
协议栈系统在接收到第一控制信息后，根据第一控制信息所包含的事件类型对网络设 备进行相应的管理。
本公开实施例提供的网络设备管理方法，将故障管理系统运行于网络设备的容器环境中，并为协议栈系统配置能够与故障管理系统进行通信的通信接口，故障管理系统基于该通信接口将第一控制信息发送至协议栈系统以对网络设备进行管理，相较于一些情形，本公开实施例提供的网络设备管理方法实现了故障管理系统与网络设备的主机操作系统的资源隔离，从而使得故障管理系统的运行状态不会对网络设备的通信状态造成影响，进而提升了网络设备性能的稳定性。
图7为本公开实施例提供的再一种网络设备管理方法的流程图，如图7所示，在一些实施例中，第一控制信息包括：配置信息，在一些实施例中，该配置信息包括：配置策略，此时，步骤S202包括：
步骤S2021、根据配置策略对网络设备进行相应配置。
本公开实施例所提供的网络设备管理方法与图3所示方法的步骤对应，请参照图3所示方法中对应步骤的描述，此处不再赘述。
图8为本公开实施例提供的再一种网络设备管理方法的流程图，如图8所示，在一些实施例中，第一控制信息包括：订阅事件信息，在一些实施例中，订阅事件信息包括：订阅信息采集策略，此时，步骤S202包括：
步骤S2021’、采集与订阅事件信息对应的目标数据。
步骤S2022’、基于目标数据生成订阅响应信息。
步骤S2023’、将订阅响应信息通过通信接口反馈至所述故障管理系统。
本公开实施例提供的网络设备管理方法与图4所示方法的步骤对应，请参照图4所示方法中对应步骤的描述，此处不再赘述。
图9为本公开实施例提供的再一种网络设备管理方法的流程图，图图9所示，在一些实施例中，第一控制信息包括：修复事件信息；在一些实施例中，修复事件信息中包括：监控数据采集策略和修复触发条件，此时，步骤S202包括：
步骤S2021”、根据监控数据采集策略实时采集目标监控数据。
步骤S2022”、判断目标监控数据是否满足修复触发条件。
当判断出目标监控数据满足所述修复触发条件时，执行步骤S2023”，当判断出目标 监控数据满足所述修复触发条件时，则返回继续执行步骤S2021”，当然，在实际应用中，还可设置时间阈值来对监控的时长进行限制，以避免无终止的监控。
步骤S2023”、生成修复响应信息，并通过通信接口将修复响应信息反馈至故障管理系统。
步骤S2024”、接收故障管理系统发送的修复策略。
步骤S2025”、根据修复策略控制网络设备执行修复操作。
本公开实施例所提供的网络设备管理方法与图5所示的方法的步骤对应，请参照图5所示方法中对应步骤的描述，此处不再赘述。
下面以使用场景来对本公开提供的网络设备管理方法进行辅助描述。
步骤1：网络设备中启用代理服务模块、协议栈系统和容器系统，通过代理服务模块将协议栈系统和容器系统的通信链路打通。
步骤2：协议栈系统内创建通信地址IP1,将其配置为NETCONF server、创建通信地址IP2，将其配置为GRPC server的服务器地址，管理面接口通过NETCONF server对外提供服务，控制面接口通过GRPC server对外提供服务。
步骤3：协议栈系统内的各业务功能模块向NETCONF server、GRPC server注册对外提供的管理面接口能力和控制面接口能力集合。
步骤4：故障管理系统内启动NETCONF client、GRPC client，创建地址IP3；故障管理系统通过IP3与协议栈系统内的NETCONF server、GRPC server建立连接，建立对网元管理操作的通信通道，该通道建立成功后，故障管理系统可调用协议栈系统提供的管理面接口和控制面接口，调用接口由自动转换工具生成开发包并预先安装到了故障管理系统所在容器内，故障管理系统可直接访问调用。
步骤5：用户配置要求监控设备内隧道接口IF1的接收报文统计信息，并且当监控到接收报文超过隧道接口带宽的80％时，将隧道带宽调整，增大指定数值5G。
步骤6：故障管理系统读取配置后，根据控制面接口的接口标识，发起RPC(Romote Procedure Call，远程过程调用，简称RPC)请求，将监控要求发布给协议栈系统。
步骤7：协议栈系统中的GRPC server接收到该信息后，根据接口注册信息分发给业务功能模块——接口管理模块，接口管理模块解析信息，生成监控节点，对该接口的带宽 统计信息变化进行判断，如果接口收包统计信息超过带宽的80％，立即封装RPC应答，通知故障管理系统监控事件发生，信息由业务功能模块组织，发送给GRPC server，GRPC server找到请求该信息的RPC连接，将信息发送出去，最终到达故障管理系统。由于仅仅对管理软件系统感兴趣的状态进行监控，节约了资源和通信量。
步骤8：故障管理软件收到RPC应答后，读取用户配置的该异常发生是时的执行信息，通过管理面接口通知设备将隧道接口IF1的带宽调整，增加5G带宽。
步骤9：协议栈系统中的NETCONF server收到该信息后，根据yang模型将信息分发给业务功能模块——接口管理模块，接口管理模块立即将隧道接口IF1的带宽调整，增加5G带宽。
步骤10：当故障管理系统异常重启后，自动加载用户配置，重新进入步骤6将监控要求下发至协议栈系统中，管理功能恢复使用。
本公开实施例还提供一种网络设备管理系统的配置方法，用于对网络设备管理系统进行初始化配置，如图10所示，该方法包括：
步骤S301、在容器环境中实例化故障管理系统。
本公开实施例中，基于网络设备的主机操作系统(例如Linux原生系统)创建容器，并在该容器内实例化故障管理系统，以实现故障管理系统与网络设备中其他功能模块的资源隔离，其中，容器的创建及在容器内实例化系统属于本领域的常规技术手段，本公开不再赘述。
步骤S302、基于接口描述语言为协议栈系统配置通信接口。
步骤S303、建立故障管理系统与协议栈系统之间的通信网络。
上述实施例中步骤S102中已对通信接口的配置过程以及故障管理系统与协议栈系统的网络连接建立过程进行描述，请参照步骤S102中的相关描述，此处不再赘述。
本公开实施例提供的网络设备管理系统的配置方法，将故障管理系统运行于网络设备的容器环境中，并为协议栈系统配置能够与故障管理系统进行通信的通信接口，从而实现了故障管理系统与网络设备的主机操作系统的资源隔离，进而使得故障管理系统的运行状态不会对网络设备的通信状态造成影响，提升了网络设备性能的稳定性。
在一些实施例中，通信接口包括：网络配置协议服务端(Network Configuration  Protocol Server，简称NETCONF server)接口和远程过程调用服务端(G Remote Procedure Call Protocol server，简称GRPC server)接口，其中，网络配置协议服务端接口可作为管理面接口使用，远程过程调用服务端接口可作为控制面接口使用。
本公开实施例还提供一种网络设备管理系统，如图1所示，该系统包括：故障管理系统1和协议栈系统2；其中，故障管理系统1实例化于容器环境中；协议栈系统2配置有与故障管理系统1进行通信的通信接口。
本公开实施例还提供一种网络设备，包括：一个或多个处理器以及存储装置，其中存储装置上存储有第一程序和第二程序中的至少一者，当第一程序被该一个或多个处理器执行，使得该一个或多个处理器实现本公开实施例提供的以故障管理系统作为执行主体的网络设备管理方法中的步骤；当第二程序被一个或多个处理器执行，使得该一个或多个处理器实现本公开实施例提供的以协议栈系统作为执行主体的网络设备管理方法中的步骤。
当然，网络设备中还可以存储有第三程序，当第三程序被一个或多个处理器执行，使得该一个或多个处理器实现本公开实施例提供的网络设备管系统的配置方法中的步骤。
本公开实施例还提供一种计算机可读介质，其上存储有计算机程序，其中，该程序被处理器执行时实现本公开实施例所提供的网络设备管理方法。
本公开实施例提供的网络设备管理方法、系统、网络设备及计算机可读介质，将故障管理系统运行于网络设备的容器环境中，并为协议栈系统配置能够与故障管理系统进行通信的通信接口，故障管理系统基于该通信接口将第一控制信息发送至协议栈系统以对网络设备进行管理，相较于一些情形，本公开实施例提供的网络设备管理方法实现了故障管理系统与网络设备的主机操作系统的资源隔离，从而使得故障管理系统的运行状态不会对网络设备的通信状态造成影响，进而提升了网络设备性能的稳定性。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可 以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
本文已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则可单独使用与特定实施例相结合描述的特征、特性和/或元素，或可与其他实施例相结合描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本公开的范围的情况下，可进行各种形式和细节上的改变。

Claims (10)

  1. 一种网络设备管理方法，应用于故障管理系统侧，其中，所述管理系统运行于网络设备的容器环境内，所述方法包括：
    生成第一控制信息；
    基于协议栈系统所配置的通信接口将所述第一控制信息发送至所述协议栈系统。
  2. 根据权利要求1所述的方法，其中，所述第一控制信息包括：配置事件信息、订阅事件信息和修复事件信息中的至少一者。
  3. 根据权利要求2所述的方法，其中，当所述第一控制信息包括修复事件信息时，在所述根据协议栈系统的通信接口将所述第一控制信息发送至所述协议栈系统的步骤之后，还包括：
    基于所述通信接口接收所述协议栈系统反馈的修复响应信息；
    获取预设的与所述修复事件信息对应的修复策略；
    基于所述通信接口将所述修复策略发送至所述协议栈系统。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    响应于重启完成指令，获取预先存储的用户管理信息；
    基于所述用户管理信息生成第二控制信息，并基于所述通信接口将所述第二控制信息发送至所述协议栈系统。
  5. 一种网络设备管理方法，应用于协议栈系统侧，其中，所述方法包括：
    基于自身所配置的通信接口，接收运行于容器环境中的故障管理系统发送的第一控制信息；
    根据所述第一控制信息对网络设备进行管理。
  6. 根据权利要求5所述的方法，其中，所述第一控制信息包括：配置事件信息、订阅事件信息和修复事件信息中的至少一者。
  7. 根据权利要求6所述的方法，其中，当所述第一控制信息包括：修复事件信息时， 所述根据所述第一控制信息对网络设备进行控制管理的步骤包括：
    根据所述修复事件信息中的监控数据采集策略实时采集目标监控数据；
    若采集到的所述目标监控数据满足所述修复事件信息中的修复触发条件，则生成修复响应信息，并通过所述通信接口将所述修复响应信息反馈至所述故障管理系统；
    接收所述故障管理系统发送的修复策略；
    根据所述修复策略控制网络设备执行修复操作。
  8. 一种网络设备管理系统，其中，包括：故障管理系统和协议栈系统；
    所述故障管理系统实例化于容器环境中；
    所述协议栈系统配置有与所述故障管理系统进行通信的通信接口。
  9. 一种网络设备，其中，包括：
    一个或多个处理器；
    存储装置，其上存储有第一程序和/或第二程序，当所述第一程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-4中任一所述的方法中的步骤；当所述第二程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求5-7中任一所述的方法中的步骤。
  10. 一种计算机可读介质，其上存储有计算机程序，其中，所述程序被处理器执行时实现如权利要求1-7中任一所述的方法中的步骤。
PCT/CN2020/141316 2019-12-30 2020-12-30 网络设备管理方法、系统及网络设备 WO2021136358A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911396966.0 2019-12-30
CN201911396966.0A CN113132127A (zh) 2019-12-30 2019-12-30 网络设备管理方法、系统及网络设备

Publications (1)

Publication Number Publication Date
WO2021136358A1 true WO2021136358A1 (zh) 2021-07-08

Family

ID=76687094

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/141316 WO2021136358A1 (zh) 2019-12-30 2020-12-30 网络设备管理方法、系统及网络设备

Country Status (2)

Country Link
CN (1) CN113132127A (zh)
WO (1) WO2021136358A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114731324A (zh) * 2022-03-04 2022-07-08 新华三技术有限公司 一种网络设备管理方法、系统及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001017170A2 (en) * 1999-08-31 2001-03-08 Accenture Llp A system, method and article of manufacture for implementing a hybrid network
CN101072129A (zh) * 2007-06-25 2007-11-14 北京邮电大学 基于jmx的网络业务管理方法及其应用系统
CN102420697A (zh) * 2011-09-07 2012-04-18 北京邮电大学 一种可配置服务的综合资源监测管理系统及其方法
CN102739428A (zh) * 2011-04-15 2012-10-17 中兴通讯股份有限公司 一种数据采集方法、装置及系统
CN109495331A (zh) * 2017-09-11 2019-03-19 大唐移动通信设备有限公司 网管系统的系统监控方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101110822B (zh) * 2007-07-06 2011-11-02 华为技术有限公司 基于网络配置协议的事件通知发送方法、系统及设备
KR20160010785A (ko) * 2014-07-18 2016-01-28 삼성전자주식회사 가전기기 및 그 제어 방법
US10785278B2 (en) * 2016-11-04 2020-09-22 Google Llc Network management interface
US10644942B2 (en) * 2018-02-07 2020-05-05 Mavenir Networks, Inc. Management of radio units in cloud radio access networks
CN109245953B (zh) * 2018-11-22 2022-11-01 新华三技术有限公司 一种网络配置方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001017170A2 (en) * 1999-08-31 2001-03-08 Accenture Llp A system, method and article of manufacture for implementing a hybrid network
CN101072129A (zh) * 2007-06-25 2007-11-14 北京邮电大学 基于jmx的网络业务管理方法及其应用系统
CN102739428A (zh) * 2011-04-15 2012-10-17 中兴通讯股份有限公司 一种数据采集方法、装置及系统
CN102420697A (zh) * 2011-09-07 2012-04-18 北京邮电大学 一种可配置服务的综合资源监测管理系统及其方法
CN109495331A (zh) * 2017-09-11 2019-03-19 大唐移动通信设备有限公司 网管系统的系统监控方法及装置

Also Published As

Publication number Publication date
CN113132127A (zh) 2021-07-16

Similar Documents

Publication Publication Date Title
US10802906B2 (en) Monitoring method and apparatus of server, and storage medium
US11004024B2 (en) Service and resource orchestration system and method, and apparatus
US11658870B2 (en) Method and apparatus for restoring network device to factory defaults, and network device
US11418385B2 (en) Network alarm method, device, system and terminal
CN112799825A (zh) 一种任务处理方法和网络设备
JP2012053882A (ja) 装置管理において、スケジューリング・タスクを処理するための方法およびシステム
CN110636127B (zh) 一种各信息数据间的通信处理方法及系统
US11936527B2 (en) Multi-access edge computing (MEC)
CN111966519B (zh) 一种调整日志级别的方法、装置、设备及可读介质
CN111770151B (zh) 用于自定义流程的处理方法、装置、电子设备及存储介质
WO2021136358A1 (zh) 网络设备管理方法、系统及网络设备
CN112448987A (zh) 一种熔断降级的触发方法、系统和存储介质
CN112217845B (zh) 一种基于Netconf协议的数据传输方法及相关设备
CA3061451A1 (en) Task based service management platform
CN114268938A (zh) 用户前置设备的纳管方法、装置、设备以及存储介质
WO2024103943A1 (zh) 一种业务处理方法、装置、存储介质及设备
CN111061723A (zh) 工作流实现方法及装置
JP2024518946A (ja) 運行維持方法、装置、システム、サーバ、電子機器及び媒体
WO2017032212A1 (zh) 一种数据流处理方法和装置
CN118260092B (zh) 算力分配方法、装置、种子服务器及多元算力服务集群
KR100981381B1 (ko) 단말기 관리 에이전트 및 방법
CN112311570A (zh) 网络设备的开通方法及装置
CA2972558C (en) Method and device for upgrading multi-dwelling unit
CN115102854B (zh) 微服务的远程过程调用路由管理控制方法、系统及设备
WO2023035777A1 (zh) 网络配置方法、代理组件、控制器、电子设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20908998

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20908998

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 15/02/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20908998

Country of ref document: EP

Kind code of ref document: A1