WO2018036255A1 - 一种恢复网络设备的出厂配置的方法、装置及网络设备 - Google Patents

一种恢复网络设备的出厂配置的方法、装置及网络设备 Download PDF

Info

Publication number
WO2018036255A1
WO2018036255A1 PCT/CN2017/089468 CN2017089468W WO2018036255A1 WO 2018036255 A1 WO2018036255 A1 WO 2018036255A1 CN 2017089468 W CN2017089468 W CN 2017089468W WO 2018036255 A1 WO2018036255 A1 WO 2018036255A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
netconf
factory
configuration
configuration data
Prior art date
Application number
PCT/CN2017/089468
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 华为技术有限公司
Priority to EP17842680.5A priority Critical patent/EP3496337B1/en
Priority to EP20208552.8A priority patent/EP3843335A1/en
Publication of WO2018036255A1 publication Critical patent/WO2018036255A1/zh
Priority to US16/283,585 priority patent/US11159372B2/en
Priority to US17/487,512 priority patent/US11658870B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/24—Resetting means
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0826—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for reduction of network costs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • 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/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
    • H04L41/0863—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions by rolling back to previous configuration versions

Definitions

  • the present invention relates to the field of configuration management technologies, and in particular, to a method, an apparatus, and a network device for restoring a factory configuration of a network device.
  • each service module in the network device saves its own factory configuration data, and the Yang model of each service module is defined.
  • a remote procedure call (RPC) command to restore the factory configuration. If the network device is running, the device may run abnormally due to the configuration. The user can trigger the NETCONF client according to the locally stored network.
  • the RPC command in the Yang model of each service module of the device sends the corresponding RPC command to each service module in the network device. After receiving the RPC command, each service module performs the factory configuration flag. When the network device restarts, each service is performed.
  • the module replaces the data in the startup configuration data set of the NETCONF server with the factory configuration data of the service module through the database read/write interface of the NETCONF server in the network device, and the NETCONF server replaces the data in the running configuration data set with the startup.
  • the NETCONF server sends the data in the running configuration data set to the corresponding service modules, and each service module makes the factory configuration data take effect, so that the network device has the factory configuration.
  • each service module needs to register its own factory configuration processing function, which is not conducive to third-party expansion, which increases the development difficulty, and the NETCONF client needs to pass NETCONF.
  • the server delivers different RPC commands for restoring the factory configuration to different service modules, and the maintenance is poor.
  • the embodiment of the invention provides a method, a device and a network device for restoring the factory configuration of the network device, and the method for restoring the factory configuration of the network device in the prior art is not conducive to third-party expansion and increases the development difficulty. And the problem of poor maintenance.
  • a method for restoring a factory configuration of a network device includes a NETCONF server and a plurality of service modules, and the method includes: the NETCONF server determines that the network device needs to be restored to the factory configuration.
  • the NETCONF server replaces the start configuration data set in the NETCONF server and the data in the running configuration data set with the factory configuration data in the factory configuration data set.
  • the factory configuration data set is dedicated to the factory configuration data of the storage network device; the NETCONF server will The data in the running configuration data set is delivered to multiple service modules; the multiple service modules perform the effective operation based on the data delivered by the NETCONF server.
  • the method provided by the first aspect adopts a factory configuration data set to store the factory configuration data of the network device, thereby avoiding each service module saving its own factory configuration data, and the NETCONF server itself can restore the factory configuration of the network device, therefore, it is not required
  • Each service module re-registers its own factory configuration processing function, which facilitates third-party extension, and the NETCONF client does not need to issue a factory-reset command to each service module in the network device through the NETCONF server for easy maintenance.
  • the NETCONF server determines that the network device needs to be restored to the factory configuration, including: when the NETCONF server determines that the network device first starts or receives a command to restore the factory configuration sent by the NETCONF client, The NETCONF server determines that the network device needs to be restored to factory configuration.
  • the NETCONF server when the network device is first started, replaces the data in the startup configuration data set and the running configuration data set in the NETCONF server with
  • the factory configuration data in the factory configuration data set includes: NETCONF server replaces the data in the startup configuration data set with the factory configuration data; the NETCONF server replaces the data in the running configuration data set with the data in the startup configuration data set.
  • the NETCONF server when the NETCONF server receives the command to restore the factory configuration sent by the NETCONF client, the NETCONF server sets the startup configuration data in the NETCONF server.
  • the data in the set and running configuration data sets is replaced with the factory configuration data in the factory configuration data set, including: the NETCONF server replaces the data in the startup configuration data set with the factory configuration data; after the network device is restarted, the NETCONF server will run the configuration data set.
  • the data is replaced with the data in the startup configuration data set.
  • the NETCONF server when the NETCONF server receives the command to restore the factory configuration sent by the NETCONF client, the NETCONF server sets the startup configuration data in the NETCONF server.
  • the data in the set and running configuration data sets is replaced with the factory configuration data in the factory configuration data set, including: the NETCONF server replaces the data in the startup configuration data set and the running configuration data set in the NETCONF server with the factory configuration data in the factory configuration data set.
  • the NETCONF server delivers the data in the running configuration data set to multiple service modules, including: the NETCONF server delivers the replaced running configuration data set and the different data in the running configuration data set before the replacement to multiple service modules.
  • the method further includes: the NETCONF server establishes a session-oriented transport protocol session with the NETCONF client; the NETCONF server sends the NETCONF server capability set to the NETCONF client, and Receiving the capability set of the NETCONF client sent by the NETCONF client, the NETCONF server's capability set includes the NETCONF server's recovery factory configuration capability flag, and the factory reset capability flag is used to characterize the NETCONF server with the ability to restore the factory configuration.
  • This possible implementation allows the NETCONF client to know that the NETCONF server has the ability to restore the factory configuration.
  • the method further includes: the NETCONF server receiving the NETCONF client The command sent by the terminal to save the factory configuration; the NETCONF server replaces the data in the factory configuration data set with the target data, and the target data is the preset data, the data in the preset configuration data set or the data in the preset file.
  • the command to restore the factory configuration is a remote procedure call RPC added to restore the factory configuration of the network device in the Yang model of the NETCONF protocol.
  • the command to save the factory configuration is the RPC command added to the Yang model of the NETCONF protocol to save the factory configuration of the network device.
  • a method for restoring a factory configuration of a network device comprising: the NETCONF client receiving an indication that the user restores the factory configuration of the network device; the NETCONF client invoking the RPC command according to the remote procedure added in the Yang model of the NETCONF protocol Sending a command to restore the factory configuration to the NETCONF server in the network device, so that the NETCONF server replaces the data in the start startup configuration data set and the running execution configuration data set in the NETCONF server with the factory configuration data in the factory configuration data set, and will run
  • the data in the configuration data set is delivered to multiple service modules, so that multiple service modules perform the operation based on the data delivered by the NETCONF server.
  • the factory configuration data set is dedicated to the factory configuration data of the storage network device.
  • the NETCONF client sends a command to restore the factory configuration to the NETCONF server, so that the NETCONF server restores the factory configuration of the network device according to its own capabilities. Therefore, each service module does not need to register its own factory configuration processing.
  • the function is beneficial to the third-party extension, and the NETCONF client does not need to issue a command to restore the factory configuration to each service module in the network device through the NETCONF server, which is convenient for maintenance.
  • the method further includes: The NETCONF client determines that the NETCONF server has the ability to restore factory configuration.
  • the method further includes: the NETCONF client receiving the NETCONF server sending The capability set of the NETCONF server, and the ability set to send the NETCONF client to the NETCONF server.
  • the NETCONF server's capability set includes the NETCONF server's factory reset capability flag, and the factory reset capability flag is used to characterize the NETCONF server with the ability to restore the factory configuration; NETCONF client The end determines that the NETCONF server has the ability to restore the factory configuration, including: NETCONF client centralized recovery according to the capabilities of the NETCONF server The factory configuration capability flag determines that the NETCONF server has the ability to restore factory configuration.
  • the method further includes: the NETCONF client receiving the user saves the network equipment from the factory The indication of the configuration; the NETCONF client sends a command to save the factory configuration to the NETCONF server in the network device according to the RPC command added in the Yang model of the NETCONF protocol for saving the factory configuration of the network device, so that the NETCONF server will concentrate the factory configuration data.
  • the data is replaced with target data, and the target data is preset data, data in a preset configuration data set, or data in a preset file.
  • a network device including: a determining unit, configured to determine that a network device needs to be restored to a factory configuration; and a replacing unit, configured to replace a start startup configuration data set and a data running the running configuration data set in the network device
  • the factory configuration data set is dedicated to the factory configuration data of the storage network device; the delivery unit is configured to deliver the data of the replaced running configuration data set to the execution unit; The validation operation is performed on the data delivered based on the delivery unit.
  • the various units in the network device are used to implement the method in the foregoing first aspect. Therefore, the beneficial effects of the network device can be seen in the beneficial effects of the foregoing method, and details are not described herein again.
  • a fourth aspect provides an apparatus for restoring a factory configuration of a network device, including: a receiving unit, configured to receive an indication that a user restores a factory configuration of the network device; and a sending unit, configured to add a remote terminal according to a NETCONF protocol
  • the process invokes the RPC command to send a command to restore the factory configuration to the network device, so that the network device replaces the data in the start startup configuration data set and the running execution configuration data set in the network device with the factory configuration data in the factory configuration data set, and is based on running
  • the data in the configuration data set is validated.
  • the factory configuration data set is dedicated to the factory configuration data of the storage network device.
  • a fifth aspect provides a network device, including: a memory and a processor, wherein the memory is configured to store a set of codes, and the processor is configured to perform the following actions according to the set of codes: determining that the network device needs to be restored to a factory configuration; The data of the startup configuration data set and the running execution configuration data set are replaced with the factory configuration data of the factory configuration data set.
  • the factory configuration data set is dedicated to the factory configuration data of the storage network device; the data execution based on the replaced running configuration data set takes effect. operating.
  • the device in the network device is used to implement the method in the foregoing first aspect. Therefore, the beneficial effects of the network device can be seen in the beneficial effects of the foregoing method, and details are not described herein again.
  • a sixth aspect provides an apparatus for recovering a factory configuration of a network device, including: a transmitter, a receiver, and a processor; the processor is configured to receive, by the receiver, an indication that the user restores a factory configuration of the network device; the processor is configured to send The device sends a command to restore the factory configuration to the network device according to the remote procedure call RPC command added in the Yang model of the NETCONF protocol, so that the network device replaces the data in the start startup configuration data set and the running running configuration data set in the network device with the factory. Configure the factory configuration data in the data set and perform the effective operation based on the data in the running configuration data set.
  • the factory configuration data set is dedicated to the factory configuration data of the storage network device.
  • the device in the device is used to implement the method of the second aspect. Therefore, the beneficial effects of the device can be seen in the beneficial effects of the above method, and details are not described herein again.
  • FIG. 2 is a schematic structural diagram of an automatic configuration system of NETCONF according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for restoring a factory configuration of a network device according to an embodiment of the present invention
  • FIG. 4 is a flowchart of still another method for restoring a factory configuration of a network device according to an embodiment of the present disclosure
  • FIG. 5 is a flowchart of still another method for restoring a factory configuration of a network device according to an embodiment of the present invention
  • FIG. 6 is a flowchart of still another method for restoring a factory configuration of a network device according to an embodiment of the present invention
  • FIG. 7 is an interaction flowchart of a method for restoring a factory configuration of a network device according to an embodiment of the present invention
  • FIG. 8 is an interaction flowchart of still another method for restoring a factory configuration of a network device according to an embodiment of the present disclosure
  • FIG. 9 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of still another network device according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of still another network device according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of an apparatus for restoring a factory configuration of a network device according to an embodiment of the present disclosure
  • FIG. 13 is a schematic structural diagram of another apparatus for restoring a factory configuration of a network device according to an embodiment of the present disclosure
  • FIG. 14 is a schematic structural diagram of another apparatus for restoring a factory configuration of a network device according to an embodiment of the present invention.
  • the NETCONF protocol is a new network configuration and management protocol.
  • the NETCONF protocol proposes a set of structural and functional issues for the Simple Network Management Protocol (SNMP).
  • SNMP Simple Network Management Protocol
  • a new mechanism for managing configuration and status information for network devices such as switches, routers, and the like.
  • the message transmission of the NETCONF protocol is divided into four levels, as shown in FIG. 1, including: a transport layer, a message layer, an operation layer, and a content layer.
  • the transport layer is mainly used to establish a communication path between the network device and the NETCONF client.
  • the protocol of the transport layer may be a Secure Shell (SSH) protocol or a Secure Transport Layer (English: Transport Layer Security, TLS for short). Protocol, Simple Object Access Protocol (SOAP) and Blocks Extensible Exchange Protocol (BEEP).
  • SSH Secure Shell
  • SOAP Simple Object Access Protocol
  • BEEP Blocks Extensible Exchange Protocol
  • the message layer represents the RPC-based communication model. Therefore, the message layer can also be called the RPC layer.
  • the message layer encapsulates the operation request message with the ⁇ rpc> element and sends the request to the network device through a secure, connection-oriented session.
  • the network device will encapsulate the response message of the operation request with the ⁇ rpc-reply> element, and then send the response message to the requester.
  • the operation layer defines a set of basic operation elements, which are the most basic RPC operation elements, including: ⁇ get-config> (query), ⁇ edit-config> (modification), ⁇ copy-config> (overwrite), ⁇ delete-config>, etc., ⁇ edit-config> is limited to operating the running configuration datastore and the candidate configuration datastore. ⁇ delete-config> is limited to operation startup.
  • the configuration datastore startup configuration datastore).
  • the NETCONF protocol defines three configuration data sets for storing configuration data.
  • the three configuration data sets are: startup configuration data set, running configuration data set, and candidate configuration data set.
  • the startup configuration data set is used to store the restart configuration of the network device.
  • the configuration of the network device is the next time the system is restarted.
  • the configuration is different from the runtime configuration.
  • the startup configuration data set is effective when the system is started.
  • the data set is loaded by the network device when the system starts.
  • the running configuration data set is used to store the running configuration of the network device.
  • the running configuration is the running configuration of the current active state of the network device, and the running status is the same. You can copy the data in the running configuration data set to the startup configuration data.
  • the set updates the current configuration to the startup configuration data set and uses this configuration data as the configuration data to be loaded at the next system startup.
  • the candidate configuration data set is used to store the optional configuration of the network device.
  • the optional configuration is a candidate configuration that does not take effect.
  • the NETCONF client can use the RPC command, which can be a commit command to apply the optional configuration to the network device. This makes the optional configuration the current runtime configuration.
  • the content layer describes the configuration data involved in network management, including configuration data and configuration objects, which basically depends on the device vendor.
  • the architecture of the automatic configuration system of the NETCONF protocol is as shown in FIG. 2, and the architecture includes: a NETCONF client and a network device, where the network device includes a plurality of service modules in the NETCONF server and the network device, and the service module may specifically include: Interface module, dynamic host configuration protocol (DHCP) module and wireless local area network (WLAN) module, NETCONF client and NETCONF server connection, NETCONF server It is connected to multiple service modules.
  • the NETCONF server also includes a configuration database.
  • the configuration database includes a startup configuration data set, a running configuration data set, and a candidate configuration data set.
  • a session is established between the NETCONF client and the NETCONF server by a connection-oriented transport protocol (eg, SSH, TLS, SOAP, or BEEP, etc.).
  • the content communicated between the NETCONF client and the NETCONF server is a two-way extensible markup language defined by the NETCONF protocol (English: Extensible Markup)
  • the Language (referred to as XML) RPC message includes a request message sent from the NETCONF client to the NETCONF server, and a response message returned by the NETCONF server to the NETCONF client. In this way, the NETCONF client can obtain and modify the configuration data of the NETCONF server.
  • the message format of the RPC message is defined by the Yang model, which defines the format of the message and the format of the configuration data contained in the message.
  • the NETCONF protocol is improved in the embodiment of the present invention, which includes: adding a factory configuration data set in the NETCONF protocol, and the factory configuration data set is used to store the factory configuration data of the network device, and an example.
  • the data set can be named factory configuration data set.
  • the naming is just an exemplary naming.
  • the name of the factory configuration data set can also be other names.
  • the factory reset capability flag is added. It indicates that the NETCONF protocol implemented by the NETCONF server supports the function of restoring the factory configuration recovery.
  • the factory reset capability flag can be: urn:ietf:params:netconf:capability:factory:1.0; the Yang model in the NETCONF protocol
  • the RPC command is added to restore the factory configuration and save the factory configuration.
  • the format of the RPC command and the format of the configuration data included in the RPC command are defined by the Yang model.
  • the name of the RPC command to restore the factory configuration may be ⁇ Factory-restore>
  • the name of the factory-configured RPC command can be ⁇ Factory-store>.
  • An embodiment of the present invention provides a method for restoring a factory configuration of a network device.
  • the network device includes a NETCONF server and multiple service modules. As shown in FIG. 3, the method includes:
  • the NETCONF server determines that the network device needs to be restored to the factory configuration.
  • the step 301 is implemented by: when the NETCONF server determines that the network device starts for the first time or receives a command to restore the factory configuration sent by the NETCONF client, the NETCONF server determines that the network device needs to be restored to the factory configuration.
  • the NETCONF client can be software running on other computers or server hardware devices outside of the network device.
  • the NETCONF server can determine whether the startup configuration data set is empty during the startup process of the network device to determine whether the network device is started for the first time. Specifically, when the startup configuration data set is empty, the network device starts for the first time, and in addition, the NETCONF server It is also possible to determine the first startup of the network device according to the preset first-initiated flag, which is not specifically limited in this embodiment of the present invention.
  • the NETCONF server replaces the data in the startup configuration data set and the running configuration data set in the NETCONF server with the factory configuration data in the factory configuration data set.
  • the factory configuration data set is specifically used to store the factory configuration data of the network device.
  • the factory configuration data set is the data set added in the existing NETCONF protocol, only when the network device is first started or the NETCONF server receives the command to restore the factory configuration.
  • the NETCONF server replaces the data in the startup configuration data set and the running configuration data set with the factory configuration data in the factory configuration data set.
  • the NETCONF server delivers the data in the running configuration data set to multiple service modules.
  • the network device includes multiple service modules, for example, an interface module, a DHCP module, and a WLAN module.
  • Different service modules are used to process different data. Therefore, when the NETCONF server sends data, it provides different services. The module delivers the data processed by the service module.
  • the multiple service modules perform the effective operation based on the data delivered by the NETCONF server.
  • step 304 the network device resumes the factory configuration.
  • the method provided by the embodiment of the present invention uses a factory configuration data set to store the factory configuration data of the network device, thereby avoiding each service module storing its own factory configuration data, and the NETCONF server itself can restore the factory configuration of the network device, therefore,
  • Each service module needs to be registered with its own factory configuration processing function, which facilitates third-party extension, and the NETCONF client does not need to issue a command to restore the factory configuration to each service module in the network device through the NETCONF server, which is convenient for maintenance.
  • FIG. 3 The method shown in FIG. 3 is further illustrated by different application scenarios. The following explanations based on the embodiments described in FIG. 4, FIG. 5, and FIG. See the embodiment described in Figure 3.
  • Scenario 1 The network device is started for the first time.
  • the foregoing methods include:
  • the NETCONF server determines that the network device is started for the first time.
  • step 401 For the specific implementation of the step 401, reference may be made to the above, and details are not described herein again.
  • the NETCONF server replaces the data in the startup configuration data set with the factory configuration data in the factory configuration data set.
  • the NETCONF server replaces the data in the running configuration data set with the data in the startup configuration data set.
  • step 404 the same as step 303.
  • step 405 the same as step 304.
  • Scenario 2 The network device receives the command to restore the factory configuration sent by the NETCONF client.
  • the foregoing method may be implemented by using the method shown in FIG. 5 or FIG. 6. Specifically, as shown in FIG. include:
  • the NETCONF server receives a command to restore the factory configuration sent by the NETCONF client.
  • the NETCONF server replaces the data in the startup configuration data set and the running configuration data set in the NETCONF server with the factory configuration data in the factory configuration data set.
  • the NETCONF server delivers the replaced running configuration data set and the different data in the running configuration data set before the replacement to multiple service modules.
  • step 504 the same as step 304.
  • the above method includes:
  • the NETCONF server receives the command to restore the factory configuration sent by the NETCONF client.
  • the factory-reset command can be used to restore the factory-configured RPC commands added to the NETCONF protocol's Yang model.
  • the NETCONF server replaces the data in the startup configuration data set with the data in the factory configuration data set.
  • Factory configuration data
  • the NETCONF server replaces the data in the running configuration data set with the data in the startup configuration data set.
  • step 604 the same as step 303.
  • step 605 the same as step 304.
  • the NETCONF server can restore the factory configuration of the network device according to the setting in the network device or the method shown in FIG. 5 or FIG. 6 after receiving the command to restore the factory configuration, or restore the factory configuration.
  • the command indicates whether a restart is required. If the command needs to be restarted, restore the factory configuration of the network device by using the method shown in Figure 6. If the indication does not need to be restarted, restore the factory configuration of the network device by using the method shown in Figure 5. .
  • the NETCONF server can also restore the factory configuration of the network device by using steps 402-405.
  • the embodiment of the present invention further provides a method for restoring the factory configuration of the network device, which is used to exemplify the method shown in FIG. 5 , as shown in FIG. 7 , the method specifically includes:
  • the NETCONF server obtains a factory configuration data set.
  • the NETCONF server can obtain the factory configuration data set during the startup process of the network device, and specifically can create a factory configuration data set according to the startup program or directly call the stored factory configuration data set.
  • the NETCONF server establishes a session for the connection-oriented transport protocol with the NETCONF client.
  • connection-oriented transport protocol between the NETCONF server and the NETCONF client can be SSH, TLS, SOAP or BEEP.
  • the NETCONF server interacts with the NETCONF client to set each other's capabilities.
  • the step 703 may include: the NETCONF server sends the capability set of the NETCONF server to the NETCONF client, and receives the capability set of the NETCONF client sent by the NETCONF client; the NETCONF client sends the capability set of the NETCONF client to the NETCONF server, and receives The set of capabilities of the NETCONF server sent by the NETCONF server.
  • the NETCONF protocol describes the protocol version and function supported by the NETCONF server or the NETCONF client through the Capability.
  • the NETCONF server and the NETCONF client can exchange each other's capability sets through the Hello message.
  • the capability set of the NETCONF server (or NETCONF client) is used to describe the protocol versions and functions supported by the NETCONF server (or NETCONF client), for example, the Yang model version supported by the NETCONF server (or NETCONF client) and the version of the NETCONF protocol. .
  • the NETCONF server's ability to focus includes the NETCONF server's factory-reset capability flag, which is used to characterize the NETCONF server's ability to restore factory configuration, exemplary,
  • the factory reset capability flag can be: urn:ietf:params:netconf:capability:factory:1.0.
  • the NETCONF client determines that the NETCONF server has the ability to restore the factory configuration according to the capability set of the NETCONF server.
  • the NETCONF client determines that the NETCONF server's capability set includes restoring the factory configuration capability flag, it is determined that the NETCONF server has the ability to restore the factory configuration.
  • step 704 if the user instructs to restore the factory configuration of the network device, steps 705-708 are performed. If the user indicates to save the factory configuration of the network device, steps 709-710 are performed.
  • the NETCONF client sends a factory-reset RPC command to the NETCONF server according to the factory-reset RPC command in the Yang model of the NETCONF protocol.
  • the RPC command to restore the factory configuration is an RPC command added in the Yang model of the existing NETCONF protocol.
  • the name of the RPC command to restore the factory configuration may be ⁇ factory-restore>, in this case, NETCONF
  • the RPC command to restore the factory configuration to the NETCONF server can be:
  • the first two lines of the four lines of code indicate that the command is an RPC command, ⁇ factory-restore/> is the name of the RPC command, and ⁇ no-restart/> indicates that the factory configuration is restored without restarting. /rpc> indicates that the command ends.
  • the NETCONF server receives the factory-reset RPC command sent by the NETCONF client, and replaces the data in the startup configuration data set and the running configuration data set with the factory configuration data in the factory configuration data set according to the RPC command.
  • the NETCONF server delivers the data in the running configuration data set after the replacement to the different service modules in the running configuration data set before the replacement.
  • the multiple service modules perform the effective operation based on the data delivered by the NETCONF server.
  • the NETCONF client sends a factory-configured RPC command to the NETCONF server according to the factory-configured RPC command in the Yang model of the NETCONF protocol.
  • the command to save the factory configuration is used to update the factory configuration data of the network device.
  • the RPC command to save the factory configuration is an RPC command added in the Yang model of the existing NETCONF protocol.
  • the name of the RPC command that saves the factory configuration may be ⁇ factory-store>.
  • NETCONF The RPC command saved by the client to the NETCONF server to save the factory configuration can be:
  • the first two lines of the eight lines of code indicate that the command is an RPC command
  • ⁇ factory-store> is the name of the RPC command
  • ⁇ source> indicates the source of the data
  • ⁇ running/> indicates that the source of the data is running.
  • Configure the data set, and the last three lines of code indicate the end of the command.
  • the default data of the RPC command goes to the factory configuration data set. This command is used to instruct the NETCONF server to replace the data in the factory configuration data set with the data of the running configuration data set.
  • the ⁇ source> field can receive parameters other than ⁇ running>, which can also be ⁇ startup>, ⁇ config>, ⁇ url. >; where ⁇ config> refers to the specific data, and ⁇ url> is used to indicate the file of the specified path.
  • the NETCONF server receives the RPC command sent by the NETCONF client to save the factory configuration, and replaces the data in the factory configuration data set with the target data.
  • the target data may be preset data, data in a preset configuration data set, or data in a preset file.
  • the target data is data in the running configuration data set.
  • the embodiment of the present invention further provides a method for restoring the factory configuration of the network device, which is used to illustrate the method shown in FIG. 6 .
  • the method specifically includes:
  • Step 801-Step 804 is the same as Step 701-Step 704 in FIG. 7.
  • Step 801-Step 804 is the same as Step 701-Step 704 in FIG. 7.
  • Step 801-Step 804 is the same as Step 701-Step 704 in FIG. 7.
  • FIG. 7 For details, refer to the embodiment of FIG. 7.
  • other explanations related to the foregoing embodiment refer to the foregoing embodiment. .
  • step 804 if the user instructs to restore the factory configuration of the network device, steps 805-809 are performed. If the user instructs to save the factory configuration of the network device, steps 810-811 are performed.
  • the NETCONF client delivers the factory-reset RPC command to the NETCONF server according to the factory-reset RPC command in the Yang model of the NETCONF protocol.
  • the RPC command to restore the factory configuration is an RPC command added in the Yang model of the existing NETCONF protocol.
  • the name of the RPC command to restore the factory configuration may be ⁇ factory-restore>, in this case, NETCONF
  • the RPC command to restore the factory configuration to the NETCONF server can be:
  • the first two lines of the four lines of code indicate that the command is an RPC command, ⁇ factory-restore/> is the name of the RPC command, and ⁇ restart/> indicates that the factory configuration is restored by restarting (if not, the default is Restore the factory configuration by rebooting, ⁇ /rpc> indicates the end of the command.
  • the NETCONF server receives the factory-reset RPC command sent by the NETCONF client, and replaces the data in the startup configuration data set in the NETCONF server with the factory configuration data in the factory configuration data set according to the RPC command.
  • the NETCONF server replaces the data in the running configuration data set in the NETCONF server with the data in the startup configuration data set.
  • the NETCONF server delivers the data in the running configuration data set to multiple service modules.
  • the network device includes multiple service modules, for example, an interface module, a DHCP module, and a WLAN module.
  • Different service modules are used to process different data. Therefore, when the NETCONF server sends data, it provides different services. The module delivers the data processed by the service module.
  • the multiple service modules perform the effective operation based on the data delivered by the NETCONF server.
  • Step 810-811 Step 810 is the same as Step 709, and Step 811 is the same as Step 710.
  • Step 810 is the same as Step 709, and Step 811 is the same as Step 710.
  • steps 701-704 may also be included before step 401, and will not be described in detail herein.
  • the method provided by the embodiment of the present invention uses a factory configuration data set to store the factory configuration data of the network device, thereby avoiding each service module storing its own factory configuration data, and the NETCONF server itself can restore the factory configuration of the network device, therefore,
  • Each service module needs to be registered with its own factory configuration processing function, which facilitates third-party extension, and the NETCONF client does not need to issue a command to restore the factory configuration to each service module in the network device through the NETCONF server, which is convenient for maintenance.
  • the command to restore the factory configuration needs to be sent to each service module in the network device, it is also necessary to add an RPC command for restoring the factory configuration in the Yang model of each service module, which is disadvantageous.
  • the present invention since there is no need to issue a command to restore the factory configuration to each service module in the network device, it is not necessary to add the Yang model of each service module.
  • the RPC command used to restore the factory configuration is beneficial to the inheritance and expansion of the Yang model.
  • the embodiment of the invention further provides a network device 90, as shown in FIG. 9, comprising:
  • a determining unit 901 configured to determine that the network device needs to be restored to a factory configuration
  • the replacing unit 902 is configured to replace the data in the start startup configuration data set and the running running configuration data set in the network device with the factory configuration data in the factory configuration data set, where the factory configuration data set is dedicated to storing the network device.
  • Factory configuration data
  • a sending unit 903 configured to send the data of the replaced running configuration data set to the executing unit 904;
  • the executing unit 904 is configured to perform an effective operation based on data sent by the sending unit 903.
  • the determining unit 901 is specifically configured to:
  • the determining unit 901 determines that the network device first starts or determines that a command to restore the factory configuration sent by the NETCONF client is received, the determining unit 901 determines that the network device needs to restore the factory configuration.
  • the replacing unit 902 is specifically configured to:
  • the data in the running configuration data set is replaced with the data in the startup configuration data set.
  • the replacing unit 902 is specifically configured to:
  • the data in the running configuration data set is replaced with the data in the startup configuration data set.
  • the determining unit 901 determines that the command to restore the factory configuration sent by the NETCONF client is received
  • the replacing unit 902 is specifically configured to: replace the data in the startup configuration data set and the running configuration data set with the factory configuration data in the factory configuration data set;
  • the sending unit 903 is specifically configured to send the replaced running configuration data set and the different data in the running configuration data set before the replacement to the executing unit 904.
  • the network device 90 further includes:
  • a session unit 905, configured to establish a session of the connection-oriented transmission protocol between the network device and the NETCONF client;
  • the transceiver unit 906 is configured to send the capability set of the network device to the NETCONF client, and receive a capability set of the NETCONF client sent by the NETCONF client, where the capability of the network device includes the network device
  • the factory reset capability flag is used to characterize the network device with the ability to restore factory configuration.
  • the transceiver unit 906 is further configured to receive a command for saving the factory configuration sent by the NETCONF client;
  • the replacing unit 902 is further configured to replace the data in the factory configuration data set with the target data, where the target data is preset data, data in a preset configuration data set, or data in a preset file.
  • the command to restore the factory configuration is a remote procedure call RPC command added in the Yang model of the NETCONF protocol for restoring the factory configuration of the network device, where the command to save the factory configuration is in the NETCONF protocol.
  • the various units in the network device 90 provided by the embodiment of the present invention are used to perform the foregoing method. Therefore, the beneficial effects of the network device 90 can be referred to the beneficial effects described in the foregoing method, and details are not described herein again.
  • the embodiment of the present invention further provides a network device 110, as shown in FIG. 11, comprising: a memory 1101, a processor 1102, and a transceiver 1103.
  • the memory 1101 is configured to store a set of codes
  • the processor 1102 is configured to use the set of codes according to the set of codes.
  • the processor is further configured to perform steps 701-702, steps 706-708, and 710 in the method shown in FIG. 7
  • the processor is further configured to execute In steps 801-802, 806-809, and 811 in the method shown in FIG. 8
  • the transceiver 1103 is configured to perform step 703, step 706, and step 710 in the method shown in FIG. Step 803, step 806, and step 811 in the method shown in FIG.
  • the memory 1101, the processor 1102 and the transceiver 1103 are coupled together by a bus system 1104.
  • the memory 1101 may include a random access memory, and may also include a non-volatile memory, such as at least one disk storage.
  • the bus system 1104 can be an industry standard architecture (English: Industry Standard Architecture, ISA for short) bus, an external device interconnection (English: Peripheral Component, PCI) bus or an extended industry standard architecture (English: Extended Industry Standard Architecture, short for EISA) bus and so on.
  • the bus system 1104 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 11, but it does not mean that there is only one bus or one type of bus.
  • the transceiver unit 906 in FIG. 9 and FIG. 10 may be the transceiver 1103, and the remaining units may be the processor 1102.
  • the remaining units may be embedded in hardware or in a processor independent of the network device, or may be in software.
  • the processor can perform the operations corresponding to the above units, and the processor can be a central processing unit (English: Central Processing Unit, CPU for short), and a specific integrated circuit (English: Application Specific Integrated Circuit) (ASIC for short) or one or more integrated circuits configured to implement embodiments of the present invention.
  • Each device in the network device 110 provided by the embodiment of the present invention is used to perform the foregoing method. Therefore, the beneficial effects of the network device 110 can be referred to the beneficial effects described in the foregoing method, and details are not described herein again.
  • the embodiment of the present invention further provides a device 120 for restoring a factory configuration of a network device. As shown in FIG. 12, the method includes:
  • the receiving unit 1201 is configured to receive an indication that the user restores a factory configuration of the network device
  • the sending unit 1202 is configured to send, according to the remote procedure call RPC command added in the Yang model of the NETCONF protocol, a command to restore the factory configuration to the network device, so that the network device is in the network device.
  • the start configuration data set and the data in the running configuration data set are replaced with the factory configuration data in the factory configuration data set, and an effective operation is performed based on the data in the running configuration data set, the factory configuration data set is dedicated to storing the Factory configuration data for network devices.
  • the apparatus 120 further includes: a determining unit 1203, configured to determine that the network device has a capability of restoring factory configuration.
  • the receiving unit 1201 is further configured to: receive a capability set of the network device that is sent by the network device, where the sending unit 1202 is further configured to send, to the network device, a capability set of the device 120, where The capability set of the network device includes a recovery factory configuration capability flag of the network device, and the recovery factory configuration capability flag is used to indicate that the network device has a capability of restoring factory configuration;
  • the determining unit 1203 is specifically configured to: determine, according to the re-factory configuration capability flag of the capability set of the network device, that the network device has the capability of restoring factory configuration.
  • the receiving unit 1201 is further configured to receive an indication that the user saves a factory configuration of the network device;
  • the sending unit 1202 is further configured to send, to the network device, a command to save a factory configuration according to an RPC command added to save a factory configuration of the network device, which is added in a Yang model of the NETCONF protocol, so that the network device
  • the data in the factory configuration data set is replaced with target data, which is preset data, data in a preset configuration data set, or data in a preset file.
  • the various units in the device 120 provided by the embodiments of the present invention are used to perform the foregoing methods. Therefore, the beneficial effects of the device 120 can be referred to the beneficial effects described in the foregoing method sections, and details are not described herein again.
  • the embodiment of the present invention further provides a device 140 for restoring the factory configuration of the network device.
  • the device 140 includes a transmitter 1401, a receiver 1402, a memory 1403, and a processor 1404.
  • the processor 1404 is configured to use the memory 1403.
  • the code stored in it performs the corresponding action.
  • the transmitter 1401, the receiver 1402, the memory 1403, and the processor 1404 are coupled together by a bus system 1405.
  • the memory 1403 may include a random access memory, and may also include a non-volatile memory, such as at least A disk storage.
  • the bus system 1405 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus system 1405 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 14, but it does not mean that there is only one bus or one type of bus.
  • the processor 1404 is configured to perform, by using the transmitter 1401, steps 703, 705, and 709 in the method shown in FIG. 7 and steps 803, 805, and 810 in the method shown in FIG.
  • the processor 1404 is also operative to perform steps 702 and 704 in the method as shown in FIG. 7 and steps 802 and 804 in the method as shown in FIG.
  • the receiving unit 1201 in FIG. 12 and FIG. 13 may be the receiver 1402, the sending unit 1202 may be the transmitter 1401, and the determining unit 1203 may be the processor 1404.
  • the determining unit may be embedded in hardware or independent of the recovery network.
  • the processor of the factory-configured device of the device may also be stored in software in the memory of the factory-configured device of the recovery network device, so that the processor invokes the operation corresponding to each unit above,
  • the processor can be a CPU, an ASIC, or one or more integrated circuits configured to implement embodiments of the present invention.
  • the various devices in the device 140 provided by the embodiments of the present invention are used to perform the foregoing methods. Therefore, the beneficial effects of the device 140 can be referred to the beneficial effects described in the foregoing method sections, and details are not described herein again.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the modules is only a logical function division.
  • there may be another division manner for example, multiple modules or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the modules described as separate components may or may not be physically separated.
  • the components displayed as modules may or may not be physical modules, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional module in each embodiment of the present invention may be integrated into one processing module, or two or more modules may be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of hardware plus software function modules.
  • the above-described integrated modules implemented in the form of software function modules can be stored in a computer readable storage medium.
  • the software functional modules described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform some of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (English: read-only memory, ROM for short), a random access memory (English: random access memory, RAM), a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例公开了一种恢复网络设备的出厂配置的方法、装置及网络设备，涉及配置管理技术领域，用以解决现有技术中的恢复网络设备的出厂配置的方法不利于第三方扩展、增大了开发难度以及维护性差的问题。该方法包括：NETCONF服务器确定网络设备需要恢复出厂配置；NETCONF服务器将NETCONF服务器中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，出厂配置数据集专用于存储网络设备的出厂配置数据；NETCONF服务器将替换后的running配置数据集中的数据下发到多个业务模块；多个业务模块基于NETCONF服务器下发的数据执行生效操作。

Description

一种恢复网络设备的出厂配置的方法、装置及网络设备
本申请要求于2016年8月24日提交中国专利局、申请号为201610716564.4、发明名称为“一种恢复网络设备的出厂配置的方法、装置及网络设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及配置管理技术领域，尤其涉及一种恢复网络设备的出厂配置的方法、装置及网络设备。
背景技术
通常情况下，大部分设备都具备恢复出厂配置的功能，以便在设备功能不稳定或者用户忘记设备的登录密码时，通过将设备恢复出厂配置使设备恢复正常。
目前，基于网络配置协议(英文：Network Configuration Protocol，简称NETCONF)恢复网络设备出厂配置的方法中，网络设备中的各业务模块保存各自的出厂配置数据，并且每个业务模块的Yang模型中定义了一个用于恢复出厂配置的远程过程调用(英文：remote procedure call，简称RPC)命令，若网络设备在运行时发生了因为配置导致设备运行异常的问题，用户可以触发NETCONF客户端根据本地存储的网络设备的各个业务模块的Yang模型中的RPC命令向网络设备中的各个业务模块下发相应的RPC命令，各个业务模块接收到RPC命令后，进行出厂配置标记，在网络设备重新启动时，各个业务模块通过网络设备中的NETCONF服务器的数据库读写接口将NETCONF服务器的开始(startup)配置数据集中的数据替换为业务模块的出厂配置数据，NETCONF服务器将运行(running)配置数据集中的数据替换为startup配置数据集中的数据，NETCONF服务器再将running配置数据集中的数据下发到对应的各个业务模块，各个业务模块使得出厂配置数据生效，从而使网络设备具备了出厂配置。
由于网络设备中的多个业务模块保存各自的出厂配置数据，因此，每个业务模块需要注册各自的出厂配置处理函数，不利于第三方扩展，增大了开发难度，并且NETCONF客户端需要通过NETCONF服务器分别下发不同的恢复出厂配置的RPC命令给不同的业务模块，维护性差。
发明内容
本发明的实施例提供了一种恢复网络设备的出厂配置的方法、装置及网络设备，用以解决现有技术中的恢复网络设备的出厂配置的方法不利于第三方扩展、增大了开发难度以及维护性差的问题。
为达到上述目的，本发明的实施例采用如下技术方案：
第一方面，提供了一种恢复网络设备的出厂配置的方法，网络设备包括NETCONF服务器和多个业务模块，该方法包括：NETCONF服务器确定网络设备需要恢复出厂配 置；NETCONF服务器将NETCONF服务器中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，出厂配置数据集专用于存储网络设备的出厂配置数据；NETCONF服务器将替换后的running配置数据集中的数据下发到多个业务模块；多个业务模块基于NETCONF服务器下发的数据执行生效操作。
第一方面提供的方法，采用了出厂配置数据集专门存储网络设备的出厂配置数据，避免了每个业务模块保存各自的出厂配置数据，NETCONF服务器本身能够恢复网络设备的出厂配置，因此，不需要每个业务模块再注册各自的出厂配置处理函数，有利于进行第三方扩展，并且NETCONF客户端不需要通过NETCONF服务器向网络设备中的每个业务模块下发恢复出厂配置的命令，便于维护。
结合第一方面，在第一种可能的实现方式中，NETCONF服务器确定网络设备需要恢复出厂配置，包括：当NETCONF服务器确定网络设备首次启动或接收到NETCONF客户端发送的恢复出厂配置的命令时，NETCONF服务器确定网络设备需要恢复出厂配置。
结合第一方面的第一种可能的实现方式，在第二种可能的实现方式中，当网络设备首次启动时，NETCONF服务器将NETCONF服务器中的startup配置数据集和running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，包括：NETCONF服务器将startup配置数据集中的数据替换为出厂配置数据；NETCONF服务器将running配置数据集中的数据替换为startup配置数据集中的数据。
结合第一方面的第一种可能的实现方式，在第三种可能的实现方式中，当NETCONF服务器接收到NETCONF客户端发送的恢复出厂配置的命令时，NETCONF服务器将NETCONF服务器中的startup配置数据集和running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，包括：NETCONF服务器将startup配置数据集中的数据替换为出厂配置数据；在网络设备重启后，NETCONF服务器将running配置数据集中的数据替换为startup配置数据集中的数据。
结合第一方面的第一种可能的实现方式，在第四种可能的实现方式中，当NETCONF服务器接收到NETCONF客户端发送的恢复出厂配置的命令时，NETCONF服务器将NETCONF服务器中的startup配置数据集和running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，包括：NETCONF服务器将NETCONF服务器中的startup配置数据集和running配置数据集中的数据同时替换为出厂配置数据集中的出厂配置数据；NETCONF服务器将running配置数据集中的数据下发到多个业务模块，包括：NETCONF服务器将替换后的running配置数据集与替换前的running配置数据集中的不同的数据下发到多个业务模块。
结合第一方面，第一方面的第一种可能的实现方式至第四种可能的实现方式中的任一种，在第五种可能的实现方式中，在NETCONF服务器确定网络设备需要恢复出厂配置之前，该方法还包括：NETCONF服务器与NETCONF客户端建立面向连接的传输协议的会话；NETCONF服务器向NETCONF客户端发送NETCONF服务器的能力集，并 接收NETCONF客户端发送的NETCONF客户端的能力集，NETCONF服务器的能力集中包括NETCONF服务器的恢复出厂配置能力标记，恢复出厂配置能力标记用于表征NETCONF服务器具备恢复出厂配置能力。
该种可能的实现方式，可以使得NETCONF客户端获知NETCONF服务器具备恢复出厂配置能力。
结合第一方面，第一方面的第一种可能的实现方式至第五种可能的实现方式中的任一种，在第六种可能的实现方式中，该方法还包括：NETCONF服务器接收NETCONF客户端发送的保存出厂配置的命令；NETCONF服务器将出厂配置数据集中的数据替换为目标数据，目标数据为预设数据、预设配置数据集中的数据或预设文件中的数据。
结合第一方面的第六种可能的实现方式，第七种可能的实现方式中，恢复出厂配置的命令为在NETCONF协议的Yang模型中增加的用于恢复网络设备的出厂配置的远程过程调用RPC命令，保存出厂配置的命令为在NETCONF协议的Yang模型中增加的用于保存网络设备出厂配置的RPC命令。
第二方面，提供了一种恢复网络设备的出厂配置的方法，包括：NETCONF客户端接收用户恢复网络设备的出厂配置的指示；NETCONF客户端根据NETCONF协议的Yang模型中增加的远程过程调用RPC命令向网络设备中的NETCONF服务器发送恢复出厂配置的命令，以使得NETCONF服务器将NETCONF服务器中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，并将running配置数据集中的数据下发到多个业务模块，从而使得多个业务模块基于NETCONF服务器下发的数据执行生效操作，出厂配置数据集专用于存储网络设备的出厂配置数据。
第二方面提供的方法，NETCONF客户端通过向NETCONF服务器发送恢复出厂配置的命令从而使得NETCONF服务器根据自身的能力恢复网络设备的出厂配置，因此，不需要每个业务模块再注册各自的出厂配置处理函数，有利于进行第三方扩展，并且NETCONF客户端不需要通过NETCONF服务器向网络设备中的每个业务模块下发恢复出厂配置的命令，便于维护。
结合第二方面，在第一种可能的实现方式中，在NETCONF客户端根据NETCONF协议的Yang模型中增加的RPC命令向网络设备中的NETCONF服务器发送恢复出厂配置的命令之前，该方法还包括：NETCONF客户端确定NETCONF服务器具备恢复出厂配置能力。
结合第二方面的第一种可能的实现方式，在第二种可能的实现方式中，在NETCONF客户端确定NETCONF服务器具备恢复出厂配置能力之前，该方法还包括：NETCONF客户端接收NETCONF服务器发送的NETCONF服务器的能力集，并向NETCONF服务器发送NETCONF客户端的能力集，NETCONF服务器的能力集中包括NETCONF服务器的恢复出厂配置能力标记，恢复出厂配置能力标记用于表征NETCONF服务器具备恢复出厂配置能力；NETCONF客户端确定NETCONF服务器具备恢复出厂配置能力，包括：NETCONF客户端根据NETCONF服务器的能力集中的恢 复出厂配置能力标记确定NETCONF服务器具备恢复出厂配置能力。
结合第二方面、第二方面的第一种可能的实现方式或第二种可能的实现方式，在第三种可能的实现方式中，该方法还包括：NETCONF客户端接收用户保存网络设备的出厂配置的指示；NETCONF客户端根据NETCONF协议的Yang模型中增加的用于保存网络设备的出厂配置的RPC命令向网络设备中的NETCONF服务器发送保存出厂配置的命令，以使得NETCONF服务器将出厂配置数据集中的数据替换为目标数据，目标数据为预设数据、预设配置数据集中的数据或预设文件中的数据。
第三方面，提供了一种网络设备，包括：确定单元，用于确定网络设备需要恢复出厂配置；替换单元，用于将网络设备中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，出厂配置数据集专用于存储网络设备的出厂配置数据；下发单元，用于将替换后的running配置数据集中的数据下发到执行单元；执行单元，用于基于下发单元下发的数据执行生效操作。
该网络设备中的各个单元用于实现上述第一方面的方法，因此，该网络设备的有益效果可以参见上述方法的有益效果，在此不再赘述。
第四方面，提供了一种恢复网络设备的出厂配置的装置，包括：接收单元，用于接收用户恢复网络设备的出厂配置的指示；发送单元，用于根据NETCONF协议的Yang模型中增加的远程过程调用RPC命令向网络设备发送恢复出厂配置的命令，以使得网络设备将网络设备中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，并基于running配置数据集中的数据执行生效操作，出厂配置数据集专用于存储网络设备的出厂配置数据。
该装置中的各个单元用于实现上述第二方面的方法，因此，该装置的有益效果可以参见上述方法的有益效果，在此不再赘述。
第五方面，提供了一种网络设备，包括：存储器和处理器，存储器用于存储一组代码，处理器用于根据该组代码执行以下动作：确定网络设备需要恢复出厂配置；将网络设备中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，出厂配置数据集专用于存储网络设备的出厂配置数据；基于替换后的running配置数据集中的数据执行生效操作。
该网络设备中的各个器件用于实现上述第一方面的方法，因此，该网络设备的有益效果可以参见上述方法的有益效果，在此不再赘述。
第六方面，提供了一种恢复网络设备的出厂配置的装置，包括：发送器、接收器和处理器；处理器用于通过接收器接收用户恢复网络设备的出厂配置的指示；处理器用于通过发送器根据NETCONF协议的Yang模型中增加的远程过程调用RPC命令向网络设备发送恢复出厂配置的命令，以使得网络设备将网络设备中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，并基于running配置数据集中的数据执行生效操作，出厂配置数据集专用于存储网络设备的出厂配置数据。
该装置中的各个器件用于实现上述第二方面的方法，因此，该装置的有益效果可以参见上述方法的有益效果，在此不再赘述。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍。
图1为现有技术中的NETCONF的分层示意图；
图2为本发明实施例提供的NETCONF的自动化配置系统的架构示意图；
图3为本发明实施例提供的一种恢复网络设备的出厂配置的方法的流程图；
图4为本发明实施例提供的又一种恢复网络设备的出厂配置的方法的流程图；
图5为本发明实施例提供的又一种恢复网络设备的出厂配置的方法的流程图；
图6为本发明实施例提供的又一种恢复网络设备的出厂配置的方法的流程图；
图7为本发明实施例提供的一种恢复网络设备的出厂配置的方法的交互流程图；
图8为本发明实施例提供的又一种恢复网络设备的出厂配置的方法的交互流程图；
图9为本发明实施例提供的一种网络设备的组成示意图；
图10为本发明实施例提供的又一种网络设备的组成示意图；
图11为本发明实施例提供的又一种网络设备的组成示意图；
图12为本发明实施例提供的一种恢复网络设备的出厂配置的装置的组成示意图；
图13为本发明实施例提供的又一种恢复网络设备的出厂配置的装置的组成示意图；
图14为本发明实施例提供的又一种恢复网络设备的出厂配置的装置的组成示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
NETCONF协议是一种新的网络配置和管理协议。为了适应当前网络规模不断扩大、网络复杂性增加、可靠性要求增强等用户需求，NETCONF协议针对简单网络管理协议(英文：Simple Network Management Protocol，简称SNMP)在结构和功能上的问题，提出一套对网络设备(例如交换机、路由器等)的配置信息和状态信息进行管理的新的机制。
NETCONF协议的消息传输被划分为4个层次，如图1所示，包括：传输层、消息层、操作层和内容层。
传输层主要用于在网络设备和NETCONF客户端之间建立通信路径，传输层的协议具体可以为安全壳(英文：Secure Shell，简称SSH)协议、安全传输层(英文：Transport Layer Security，简称TLS)协议、简单对象访问协议(英文：Simple Object Access Protocol，简称SOAP)以及块可扩展交换协议(英文：Blocks Extensible Exchange Protocol，简称BEEP)等。
消息层表示了基于RPC的通信模型，因此，消息层也可以称为RPC层，消息层采用<rpc>元素封装操作请求消息，并通过一个安全、面向连接的会话将请求发送给网络设备，而网络设备将采用<rpc-reply>元素封装该操作请求的响应消息，然后将此响应消息发送给请求者。
操作层定义了一组基本操作元素，这些操作是最基本的RPC操作元素，具体包括：<get-config>(查询)、<edit-config>(修改)、<copy-config>(覆盖)、<delete-config>(清空)等，<edit-config>仅限于操作running配置数据集(running configuration datastore)和候选(candidate)配置数据集(candidate configuration datastore)，<delete-config>仅限于操作startup配置数据集(startup configuration datastore)。
NETCONF协议定义了三个配置数据集，用于存储配置数据，三个配置数据集分别为：startup配置数据集、running配置数据集和candidate配置数据集。startup配置数据集用于存储网络设备的重启时配置，重启时配置是网络设备的系统下次重启时的配置，可以和运行时配置不一样，startup配置数据集是网络设备的系统启动时默认生效的数据集，在系统启动时被网络设备加载。running配置数据集用于存储网络设备的运行时配置，运行时配置是网络设备当前激活状态的运行中的配置，和运行的状态完全一致，可以通过将running配置数据集中的数据拷贝到startup配置数据集更新当前配置到startup配置数据集，并将此配置数据作为下次系统启动时要加载的配置数据。candidate配置数据集用于存储网络设备的可选配置，可选配置是没有生效的候选配置，NETCONF客户端可使用RPC命令，具体可以为commit(提交)命令，将可选配置应用到网络设备，从而使得可选配置变为当前的运行时配置。
内容层描述了网络管理所涉及的配置数据，具体包括配置数据和配置对象，它基本上依赖于设备厂商。
NETCONF协议的自动化配置系统采用的架构具体如图2所示，该架构包括：NETCONF客户端和网络设备，其中，网络设备包括NETCONF服务器和网络设备中的多个业务模块，业务模块具体可以包括：接口模块(interface module)、动态主机配置协议(英文：Dynamic Host Configuration Protocol，简称DHCP)模块和无线局域网(英文：wireless local area network，简称WLAN)模块等，NETCONF客户端和NETCONF服务器连接，NETCONF服务器和多个业务模块连接，NETCONF服务器中还包括配置数据库，配置数据库包括startup配置数据集、running配置数据集和candidate配置数据集。
NETCONF客户端和NETCONF服务器之间由面向连接的传输协议(例如，SSH、TLS、SOAP或BEEP等)建立会话。NETCONF客户端和NETCONF服务器之间通信的内容是NETCONF协议定义的双向的可扩展标记语言(英文：Extensible Markup  Language，简称XML)式的RPC消息，包括从NETCONF客户端发送到NETCONF服务器的请求消息，以及NETCONF服务器向NETCONF客户端返回的响应消息。这样，NETCONF客户端就可以获取并修改NETCONF服务器的配置数据。RPC消息的消息格式由Yang模型定义，Yang模型可以定义消息的格式以及消息中包含的配置数据的格式。为了解决现有技术中的问题，本发明实施例中对NETCONF协议进行了改进，具体包括：在NETCONF协议中增加一个出厂配置数据集，出厂配置数据集用于存储网络设备的出厂配置数据，示例性的，该数据集可以命名为factory配置数据集，该命名仅仅是示例性的命名，出厂配置数据集的名称还可以为其他名称；在NETCONF服务器的能力集中增加恢复出厂配置能力标记，用于表明该NETCONF服务器所实现的NETCONF协议支持恢复出厂配置恢复的功能，示例性的，恢复出厂配置能力标记具体可以为：urn:ietf:params:netconf:capability:factory:1.0；在NETCONF协议的Yang模型中增加恢复出厂配置和保存出厂配置的RPC命令，该RPC命令的格式以及该RPC命令中包含的配置数据的格式均由Yang模型定义，示例性的，恢复出厂配置的RPC命令的名称可以为<factory-restore>，保存出厂配置的RPC命令的名称可以为<factory-store>。
本发明实施例提供了一种恢复网络设备的出厂配置的方法，网络设备包括NETCONF服务器和多个业务模块，如图3所示，该方法包括：
301、NETCONF服务器确定网络设备需要恢复出厂配置。
可选的，步骤301在具体实现时可以为：当NETCONF服务器确定网络设备首次启动或接收到NETCONF客户端发送的恢复出厂配置的命令时，NETCONF服务器确定网络设备需要恢复出厂配置。
NETCONF客户端可以是运行在网络设备外的其他计算机或服务器硬件装置上的软件。
具体的，NETCONF服务器可以在网络设备启动的过程中判断startup配置数据集是否为空确定网络设备是否为首次启动，具体的，当startup配置数据集为空时，网络设备首次启动，另外，NETCONF服务器还可以根据预设的首次启动的标记确定网络设备首次启动，本发明实施例对此不做具体限定。
302、NETCONF服务器将NETCONF服务器中的startup配置数据集和running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据。
出厂配置数据集专门用于存储网络设备的出厂配置数据，出厂配置数据集为在现有的NETCONF协议中增加的数据集，只有在网络设备首次启动或NETCONF服务器接收到恢复出厂配置的命令时，NETCONF服务器才会将startup配置数据集和running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据。
303、NETCONF服务器将running配置数据集中的数据下发到多个业务模块。
需要说明的是，网络设备中包括多个业务模块，例如，接口模块、DHCP模块和WLAN模块等，不同的业务模块用于处理不同的数据，因此，NETCONF服务器在下发数据时，给不同的业务模块下发该业务模块处理的数据。
304、多个业务模块基于NETCONF服务器下发的数据执行生效操作。
在执行步骤304之后，网络设备恢复了出厂配置。
本发明实施例提供的方法，采用了出厂配置数据集专门存储网络设备的出厂配置数据，避免了每个业务模块保存各自的出厂配置数据，NETCONF服务器本身能够恢复网络设备的出厂配置，因此，不需要每个业务模块再注册各自的出厂配置处理函数，有利于进行第三方扩展，并且NETCONF客户端不需要通过NETCONF服务器向网络设备中的每个业务模块下发恢复出厂配置的命令，便于维护。
以下通过不同的应用场景对图3所示的方法进行进一步的说明，以下基于图4、图5、图6所述的实施例中的与基于图3所述的实施例中的相关的解释可以参见图3所述的实施例。
场景一、网络设备首次启动，该场景下，如图4所示，上述方法包括：
401、NETCONF服务器确定网络设备首次启动。
步骤401的具体实现方式可以参考上文，在此不再赘述。
402、NETCONF服务器将startup配置数据集中的数据替换为出厂配置数据集中的出厂配置数据。
403、NETCONF服务器将running配置数据集中的数据替换为startup配置数据集中的数据。
404；与步骤303相同。
405；与步骤304相同。
场景二、网络设备接收到NETCONF客户端发送的恢复出厂配置的命令，该场景下，上述方法可以采用如图5或如图6所示的方法实现，具体的，如图5所示，上述方法包括：
501、NETCONF服务器接收NETCONF客户端发送的恢复出厂配置的命令。
502、NETCONF服务器将NETCONF服务器中的startup配置数据集和running配置数据集中的数据同时替换为出厂配置数据集中的出厂配置数据。
503、NETCONF服务器将替换后的running配置数据集与替换前的running配置数据集中的不同的数据下发到多个业务模块。
504；与步骤304相同。
在场景二下，如图6所示，上述方法包括：
601、NETCONF服务器接收NETCONF客户端发送的恢复出厂配置的命令。
恢复出厂配置的命令可以为在NETCONF协议的Yang模型中增加的恢复出厂配置的RPC命令。
602、NETCONF服务器将startup配置数据集中的数据替换为出厂配置数据集中的 出厂配置数据；
603、在网络设备重启后，NETCONF服务器将running配置数据集中的数据替换为startup配置数据集中的数据。
604；与步骤303相同。
605；与步骤304相同。
上述方法在具体实现时，NETCONF服务器在接收到恢复出厂配置的命令后，可以根据网络设备中的设置采用图5或图6所示的方法恢复网络设备的出厂配置，也可以在恢复出厂配置的命令中指示是否需要进行重启，若指示需要进行重启，则采用图6所示的方法恢复网络设备的出厂配置，若指示不需要进行重启，则采用图5所示的方法恢复网络设备的出厂配置。
另外一种可实现的方式，NETCONF服务器在接收到恢复出厂配置的命令后，NETCONF服务器若采用预设首次启动标识的方式，则NETCONF服务器还可以通过采用步骤402-405恢复网络设备的出厂配置。
本发明实施例还提供了一种恢复网络设备出厂配置的方法，用于对图5所示的方法进行示例性说明，具体如图7所示，该方法具体包括：
701、NETCONF服务器获取出厂配置数据集。
具体的，NETCONF服务器可以在网络设备启动的过程中获取出厂配置数据集，具体可以根据启动程序创建出厂配置数据集或者直接调用存储的已创建好的出厂配置数据集。
702、NETCONF服务器与NETCONF客户端建立面向连接的传输协议的会话。
NETCONF服务器与NETCONF客户端之间的面向连接的传输协议可以为SSH、TLS、SOAP或BEEP等。
703、NETCONF服务器与NETCONF客户端交互彼此的能力集。
步骤703在具体实现时可以包括：NETCONF服务器向NETCONF客户端发送NETCONF服务器的能力集，并接收NETCONF客户端发送的NETCONF客户端的能力集；NETCONF客户端向NETCONF服务器发送NETCONF客户端的能力集，并接收NETCONF服务器发送的NETCONF服务器的能力集。
具体的，NETCONF协议通过能力(Capability)描述NETCONF服务器或NETCONF客户端支持的协议版本和功能，NETCONF服务器与NETCONF客户端之间可以通过Hello消息交互彼此的能力集。NETCONF服务器(或NETCONF客户端)的能力集用于描述NETCONF服务器(或NETCONF客户端)所支持的协议版本和功能，例如，NETCONF服务器(或NETCONF客户端)支持的Yang模型版本和NETCONF协议的版本。
NETCONF服务器的能力集中包括NETCONF服务器的恢复出厂配置能力标记，该恢复出厂配置能力标记用于表征NETCONF服务器具备恢复出厂配置能力，示例性的， 恢复出厂配置能力标记具体可以为：urn:ietf:params:netconf:capability:factory:1.0。
704、NETCONF客户端根据NETCONF服务器的能力集确定NETCONF服务器具备恢复出厂配置能力。
具体的，若NETCONF客户端确定NETCONF服务器的能力集中包括恢复出厂配置能力标记，则确定NETCONF服务器具备恢复出厂配置能力。
在步骤704之后，若用户指示恢复网络设备的出厂配置，则执行步骤705-708，若用户指示保存网络设备的出厂配置，则执行步骤709-710。
705、NETCONF客户端根据NETCONF协议的Yang模型中的恢复出厂配置的RPC命令向NETCONF服务器下发恢复出厂配置的RPC命令。
具体的，恢复出厂配置的RPC命令为在现有的NETCONF协议的Yang模型中增加的RPC命令，示例性的，恢复出厂配置的RPC命令的名称可以为<factory-restore>，该情况下，NETCONF客户端向NETCONF服务器下发的恢复出厂配置的RPC命令具体可以为：
Figure PCTCN2017089468-appb-000001
其中，这四行代码中的前两行代码表示该命令为一个RPC命令，<factory-restore/>为该RPC命令的名称，<no-restart/>表示采用不重启的方式恢复出厂配置，</rpc>表示该命令结束。
706、NETCONF服务器接收NETCONF客户端发送的恢复出厂配置的RPC命令，并根据该RPC命令将startup配置数据集和running配置数据集中的数据同时替换为出厂配置数据集中的出厂配置数据。
707、NETCONF服务器将替换后的running配置数据集中的与替换前的running配置数据集中的不同的数据下发到多个业务模块。
708、多个业务模块基于NETCONF服务器下发的数据执行生效操作。
709、NETCONF客户端根据NETCONF协议的Yang模型中的保存出厂配置的RPC命令向NETCONF服务器下发保存出厂配置的RPC命令。
其中，保存出厂配置的命令用于更新网络设备的出厂配置数据。
具体的，保存出厂配置的RPC命令为在现有的NETCONF协议的Yang模型中增加的RPC命令，示例性的，保存出厂配置的RPC命令的名称可以为<factory-store>，该情况下，NETCONF客户端向NETCONF服务器下发的保存出厂配置的RPC命令具体可以为：
Figure PCTCN2017089468-appb-000002
其中，这八行代码中的前两行代码表示该命令为一个RPC命令，<factory-store>为该RPC命令的名称，<source>表示数据的来源，<running/>表示数据的来源为running配置数据集，最后三行代码表示该命令结束。该RPC命令默认数据的去向为出厂配置数据集。该命令用于指示NETCONF服务器将出厂配置数据集中的数据替换为running配置数据集的数据，<source>字段可以接收的参数除了<running>外，还可以为<startup>、<config>、<url>；其中，<config>是指具体的数据，<url>用于指示指定路径的文件。
710、NETCONF服务器接收NETCONF客户端发送的保存出厂配置的RPC命令，并将出厂配置数据集中的数据替换为目标数据。
其中，目标数据可以为预设数据、预设配置数据集中的数据或预设文件中的数据。在步骤709的示例中，目标数据为running配置数据集中的数据。
本发明实施例还提供了一种恢复网络设备的出厂配置的方法，用于对图6所示的方法进行示例性说明，具体如图8所示，该方法具体包括：
801-804；步骤801-步骤804与图7中的步骤701-步骤704分别相同，具体内容可以参见图7的实施例，该实施例中其他与上述实施例相关内容的解释可以参见上述实施例。
在步骤804之后，若用户指示恢复网络设备的出厂配置，执行步骤805-809，若用户指示保存网络设备的出厂配置，执行步骤810-811。
805、NETCONF客户端根据NETCONF协议的Yang模型中的恢复出厂配置的RPC命令向NETCONF服务器下发恢复出厂配置的RPC命令。
具体的，恢复出厂配置的RPC命令为在现有的NETCONF协议的Yang模型中增加的RPC命令，示例性的，恢复出厂配置的RPC命令的名称可以为<factory-restore>，该情况下，NETCONF客户端向NETCONF服务器下发的恢复出厂配置的RPC命令具体可以为：
Figure PCTCN2017089468-appb-000003
或者，
Figure PCTCN2017089468-appb-000004
其中，这四行代码中的前两行代码表示该命令为一个RPC命令，<factory-restore/>为该RPC命令的名称，<restart/>表示采用重启的方式恢复出厂配置(若没有则默认采用重启的方式恢复出厂配置)，</rpc>表示该命令结束。
806、NETCONF服务器接收NETCONF客户端发送的恢复出厂配置的RPC命令，并根据该RPC命令将NETCONF服务器中的startup配置数据集中的数据替换为出厂配置数据集中的出厂配置数据。
807、在网络设备重启后，NETCONF服务器将NETCONF服务器中的running配置数据集中的数据替换为startup配置数据集中的数据。
808、NETCONF服务器将running配置数据集中的数据下发到多个业务模块。
需要说明的是，网络设备中包括多个业务模块，例如，接口模块、DHCP模块和WLAN模块等，不同的业务模块用于处理不同的数据，因此，NETCONF服务器在下发数据时，给不同的业务模块下发该业务模块处理的数据。
809、多个业务模块基于NETCONF服务器下发的数据执行生效操作。
810-811；步骤810与步骤709相同，步骤811与步骤710相同，具体内容可以参见基于图7所述的实施例。
另外，在如图4所示的方法中，步骤401之前也可以包括步骤701-704所示的步骤，在此不再详述。
本发明实施例提供的方法，采用了出厂配置数据集专门存储网络设备的出厂配置数据，避免了每个业务模块保存各自的出厂配置数据，NETCONF服务器本身能够恢复网络设备的出厂配置，因此，不需要每个业务模块再注册各自的出厂配置处理函数，有利于进行第三方扩展，并且NETCONF客户端不需要通过NETCONF服务器向网络设备中的每个业务模块下发恢复出厂配置的命令，便于维护。另外，现有技术中由于需要向网络设备中的每个业务模块下发恢复出厂配置的命令，因此，还需要在每个业务模块的Yang模型中增加用于恢复出厂配置的RPC命令，不利于Yang模型的继承性和扩展性，本发明实施例中，由于不需要向网络设备中的每个业务模块下发恢复出厂配置的命令，因此，就不需要在每个业务模块的Yang模型中增加用于恢复出厂配置的RPC命令，有利于Yang模型的继承和扩展。
本发明实施例还提供了一种网络设备90，如图9所示，包括：
确定单元901，用于确定所述网络设备需要恢复出厂配置；
替换单元902，用于将所述网络设备中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，所述出厂配置数据集专用于存储所述网络设备的出厂配置数据；
下发单元903，用于将所述替换后的running配置数据集中的数据下发到执行单元904；
所述执行单元904，用于基于所述下发单元903下发的数据执行生效操作。
可选的，所述确定单元901具体用于：
当所述确定单元901确定所述网络设备首次启动或确定接收到NETCONF客户端发送的恢复出厂配置的命令时，所述确定单元901确定所述网络设备需要恢复出厂配置。
可选的，当所述网络设备首次启动时，所述替换单元902具体用于：
将所述startup配置数据集中的数据替换为所述出厂配置数据；
将所述running配置数据集中的数据替换为所述startup配置数据集中的数据。
可选的，当所述确定单元901确定接收到NETCONF客户端发送的恢复出厂配置的命令时，所述替换单元902具体用于：
将所述startup配置数据集中的数据替换为所述出厂配置数据；
在所述网络设备重启后，将所述running配置数据集中的数据替换为所述startup配置数据集中的数据。
可选的，当所述确定单元901确定接收到NETCONF客户端发送的恢复出厂配置的命令时，
所述替换单元902具体用于：将所述startup配置数据集和running配置数据集中的数据同时替换为出厂配置数据集中的出厂配置数据；
所述下发单元903具体用于：将替换后的所述running配置数据集与替换前的所述running配置数据集中的不同的数据下发到所述执行单元904。
可选的，如图10所示，所述网络设备90还包括：
会话单元905，用于建立所述网络设备和所述NETCONF客户端之间的面向连接的传输协议的会话；
收发单元906，用于向所述NETCONF客户端发送所述网络设备的能力集，并接收所述NETCONF客户端发送的所述NETCONF客户端的能力集，所述网络设备的能力集中包括所述网络设备的恢复出厂配置能力标记，所述恢复出厂配置能力标记用于表征所述网络设备具备恢复出厂配置能力。
可选的，所述收发单元906，还用于接收所述NETCONF客户端发送的保存出厂配置的命令；
所述替换单元902，还用于将出厂配置数据集中的数据替换为目标数据，所述目标数据为预设数据、预设配置数据集中的数据或预设文件中的数据。
可选的，所述恢复出厂配置的命令为在NETCONF协议的Yang模型中增加的用于恢复所述网络设备的出厂配置的远程过程调用RPC命令，所述保存出厂配置的命令为在NETCONF协议的Yang模型中增加的用于保存网络设备出厂配置的RPC命令。
本发明实施例提供的网络设备90中的各个单元用于执行上述方法，因此，网络设备90的有益效果可以参见上述方法部分所述的有益效果，在此不再赘述。
本发明实施例还提供了一种网络设备110，如图11所示，包括：存储器1101、处理器1102和收发器1103，存储器1101用于存储一组代码，处理器1102用于根据该组代码执行如图3-图6中所示的任意一种方法，处理器还用于执行如图7所示的方法中的步骤701-702、步骤706-708和步骤710，处理器还用于执行如图8所示的方法中的步骤801-802、步骤806-809和步骤811，收发器1103用于执行如图7所示的方法中的步骤703、步骤706和步骤710，还用于执行如图8所示的方法中的步骤803、步骤806和步骤811。
其中，存储器1101、处理器1102和收发器1103之间是通过总线系统1104耦合在一起的，其中存储器1101可能包含随机存取存储器，也可能还包括非易失性存储器，例如至少一个磁盘存储器。总线系统1104可以是工业标准体系结构(英文：Industry Standard Architecture，简称ISA)总线、外部设备互连(英文：Peripheral Component，简称PCI)总线或扩展工业标准体系结构(英文：Extended Industry Standard Architecture，简称EISA)总线等。该总线系统1104可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
其中，图9和图10中的收发单元906可以为收发器1103，其余单元可以为处理器1102，其余单元可以以硬件形式内嵌于或独立于网络设备的处理器中，也可以以软件形式存储于网络设备的存储器中，以便于处理器调用执行以上各个单元对应的操作，该处理器可以为中央处理器(英文：Central Processing Unit，简称CPU)、特定集成电路(英文：Application Specific Integrated Circuit，简称ASIC)或者是被配置成实施本发明实施例的一个或多个集成电路。
本发明实施例提供的网络设备110中的各个器件用于执行上述方法，因此，网络设备110的有益效果可以参见上述方法部分所述的有益效果，在此不再赘述。
本发明实施例还提供了一种恢复网络设备的出厂配置的装置120，如图12所示，包括：
接收单元1201，用于接收用户恢复所述网络设备的出厂配置的指示；
发送单元1202，用于根据NETCONF协议的Yang模型中增加的远程过程调用RPC命令向所述网络设备发送恢复出厂配置的命令，以使得所述网络设备将所述网络设备中 的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，并基于所述running配置数据集中的数据执行生效操作，所述出厂配置数据集专用于存储所述网络设备的出厂配置数据。
可选的，如图13所示，所述装置120还包括：确定单元1203，用于确定所述网络设备具备恢复出厂配置能力。
可选的，所述接收单元1201还用于：接收所述网络设备发送的所述网络设备的能力集，所述发送单元1202还用于向所述网络设备发送所述装置120的能力集，所述网络设备的能力集中包括所述网络设备的恢复出厂配置能力标记，所述恢复出厂配置能力标记用于表征所述网络设备具备恢复出厂配置能力；
所述确定单元1203具体用于：根据所述网络设备的能力集中的恢复出厂配置能力标记确定所述网络设备具备恢复出厂配置能力。
可选的，所述接收单元1201，还用于接收所述用户保存所述网络设备的出厂配置的指示；
所述发送单元1202，还用于根据NETCONF协议的Yang模型中增加的用于保存所述网络设备的出厂配置的RPC命令向所述网络设备发送保存出厂配置的命令，以使得所述网络设备将出厂配置数据集中的数据替换为目标数据，所述目标数据为预设数据、预设配置数据集中的数据或预设文件中的数据。
本发明实施例提供的装置120中的各个单元用于执行上述方法，因此，装置120的有益效果可以参见上述方法部分所述的有益效果，在此不再赘述。
本发明实施例还提供了一种恢复网络设备的出厂配置的装置140，如图14所示，包括：发送器1401、接收器1402、存储器1403和处理器1404，处理器1404用于根据存储器1403中存储的代码执行相应的动作。
其中，发送器1401、接收器1402、存储器1403和处理器1404之间是通过总线系统1405耦合在一起的，其中存储器1403可能包含随机存取存储器，也可能还包括非易失性存储器，例如至少一个磁盘存储器。总线系统1405可以是ISA总线、PCI总线或EISA总线等。该总线系统1405可以分为地址总线、数据总线、控制总线等。为便于表示，图14中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
具体的，处理器1404用于通过发送器1401执行如图7所示的方法中的步骤703、步骤705和步骤709以及如图8所示的方法中的步骤803、步骤805和步骤810，处理器1404还用于执行如图7所示的方法中的步骤702和704以及如图8所示的方法中的步骤802和804。
其中，图12和图13中的接收单元1201可以为接收器1402，发送单元1202可以为发送器1401，确定单元1203可以为处理器1404，确定单元可以以硬件形式内嵌于或独立于恢复网络设备的出厂配置的装置的处理器中，也可以以软件形式存储于恢复网络设备的出厂配置的装置的存储器中，以便于处理器调用执行以上各个单元对应的操作，该 处理器可以为CPU、ASIC或者是被配置成实施本发明实施例的一个或多个集成电路。
本发明实施例提供的装置140中的各个器件用于执行上述方法，因此，装置140的有益效果可以参见上述方法部分所述的有益效果，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。
所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能模块可以集成在一个处理模块中，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用硬件加软件功能模块的形式实现。
上述以软件功能模块的形式实现的集成的模块，可以存储在一个计算机可读取存储介质中。上述软件功能模块存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(英文：read-only memory，简称ROM)、随机存取存储器(英文：random access memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (24)

  1. 一种恢复网络设备的出厂配置的方法，所述网络设备包括网络配置协议NETCONF服务器和多个业务模块，其特征在于，所述方法包括：
    所述NETCONF服务器确定所述网络设备需要恢复出厂配置；
    所述NETCONF服务器将所述NETCONF服务器中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，所述出厂配置数据集专用于存储所述网络设备的出厂配置数据；
    所述NETCONF服务器将所述替换后的running配置数据集中的数据下发到所述多个业务模块；
    所述多个业务模块基于所述NETCONF服务器下发的数据执行生效操作。
  2. 根据权利要求1所述的方法，其特征在于，所述NETCONF服务器确定所述网络设备需要恢复出厂配置，包括：
    当所述NETCONF服务器确定所述网络设备首次启动或接收到NETCONF客户端发送的恢复出厂配置的命令时，所述NETCONF服务器确定所述网络设备需要恢复出厂配置。
  3. 根据权利要求2所述的方法，其特征在于，当所述网络设备首次启动时，所述NETCONF服务器将所述NETCONF服务器中的startup配置数据集和running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，包括：
    所述NETCONF服务器将所述startup配置数据集中的数据替换为所述出厂配置数据；
    所述NETCONF服务器将所述running配置数据集中的数据替换为所述startup配置数据集中的数据。
  4. 根据权利要求2所述的方法，其特征在于，当所述NETCONF服务器接收到NETCONF客户端发送的恢复出厂配置的命令时，所述NETCONF服务器将所述NETCONF服务器中的startup配置数据集和running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，包括：
    所述NETCONF服务器将所述startup配置数据集中的数据替换为所述出厂配置数据；
    在所述网络设备重启后，所述NETCONF服务器将所述running配置数据集中的数据替换为所述startup配置数据集中的数据。
  5. 根据权利要求2所述的方法，其特征在于，当所述NETCONF服务器接收到NETCONF客户端发送的恢复出厂配置的命令时，
    所述NETCONF服务器将所述NETCONF服务器中的startup配置数据集和running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，包括：所述NETCONF服务器将所述NETCONF服务器中的startup配置数据集和running配置数据集中的数据同时替换为出厂配置数据集中的出厂配置数据；
    所述NETCONF服务器将所述running配置数据集中的数据下发到所述多个业务模块，包括：所述NETCONF服务器将替换后的所述running配置数据集与替换前的所述 running配置数据集中的不同的数据下发到所述多个业务模块。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，在所述NETCONF服务器确定所述网络设备需要恢复出厂配置之前，所述方法还包括：
    所述NETCONF服务器与所述NETCONF客户端建立面向连接的传输协议的会话；
    所述NETCONF服务器向所述NETCONF客户端发送所述NETCONF服务器的能力集，并接收所述NETCONF客户端发送的所述NETCONF客户端的能力集，所述NETCONF服务器的能力集中包括所述NETCONF服务器的恢复出厂配置能力标记，所述恢复出厂配置能力标记用于表征所述NETCONF服务器具备恢复出厂配置能力。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    所述NETCONF服务器接收所述NETCONF客户端发送的保存出厂配置的命令；
    所述NETCONF服务器将出厂配置数据集中的数据替换为目标数据，所述目标数据为预设数据、预设配置数据集中的数据或预设文件中的数据。
  8. 根据权利要求7所述的方法，其特征在于，所述恢复出厂配置的命令为在NETCONF协议的Yang模型中增加的用于恢复所述网络设备的出厂配置的远程过程调用RPC命令，所述保存出厂配置的命令为在NETCONF协议的Yang模型中增加的用于保存网络设备出厂配置的RPC命令。
  9. 一种恢复网络设备的出厂配置的方法，其特征在于，包括：
    网络配置协议NETCONF客户端接收用户恢复所述网络设备的出厂配置的指示；
    所述NETCONF客户端根据NETCONF协议的Yang模型中增加的远程过程调用RPC命令向所述网络设备中的NETCONF服务器发送恢复出厂配置的命令，以使得所述NETCONF服务器将所述NETCONF服务器中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，并将所述running配置数据集中的数据下发到所述多个业务模块，从而使得所述多个业务模块基于所述NETCONF服务器下发的数据执行生效操作，所述出厂配置数据集专用于存储所述网络设备的出厂配置数据。
  10. 根据权利要求9所述的方法，其特征在于，在所述NETCONF客户端根据NETCONF协议的Yang模型中增加的RPC命令向所述网络设备中的NETCONF服务器发送恢复出厂配置的命令之前，所述方法还包括：
    所述NETCONF客户端确定所述NETCONF服务器具备恢复出厂配置能力。
  11. 根据权利要求10所述的方法，其特征在于，在所述NETCONF客户端确定所述NETCONF服务器具备恢复出厂配置能力之前，所述方法还包括：
    所述NETCONF客户端接收所述NETCONF服务器发送的所述NETCONF服务器的能力集，并向所述NETCONF服务器发送所述NETCONF客户端的能力集，所述NETCONF服务器的能力集中包括所述NETCONF服务器的恢复出厂配置能力标记，所述恢复出厂配置能力标记用于表征所述NETCONF服务器具备恢复出厂配置能力；
    所述NETCONF客户端确定所述NETCONF服务器具备恢复出厂配置能力，包括：所述NETCONF客户端根据所述NETCONF服务器的能力集中的恢复出厂配置能力标记确定所述NETCONF服务器具备恢复出厂配置能力。
  12. 根据权利要求9-11任一项所述的方法，其特征在于，所述方法还包括：
    所述NETCONF客户端接收所述用户保存所述网络设备的出厂配置的指示；
    所述NETCONF客户端根据NETCONF协议的Yang模型中增加的用于保存所述网络设备的出厂配置的RPC命令向所述网络设备中的NETCONF服务器发送保存出厂配置的命令，以使得所述NETCONF服务器将出厂配置数据集中的数据替换为目标数据，所述目标数据为预设数据、预设配置数据集中的数据或预设文件中的数据。
  13. 一种网络设备，其特征在于，包括：
    确定单元，用于确定所述网络设备需要恢复出厂配置；
    替换单元，用于将所述网络设备中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，所述出厂配置数据集专用于存储所述网络设备的出厂配置数据；
    下发单元，用于将所述替换后的running配置数据集中的数据下发到执行单元；
    所述执行单元，用于基于所述下发单元下发的数据执行生效操作。
  14. 根据权利要求13所述的网络设备，其特征在于，所述确定单元具体用于：
    当确定所述网络设备首次启动或确定接收到NETCONF客户端发送的恢复出厂配置的命令时，确定所述网络设备需要恢复出厂配置。
  15. 根据权利要求14所述的网络设备，其特征在于，当所述网络设备首次启动时，所述替换单元具体用于：
    将所述startup配置数据集中的数据替换为所述出厂配置数据；
    将所述running配置数据集中的数据替换为所述startup配置数据集中的数据。
  16. 根据权利要求14所述的网络设备，其特征在于，当所述确定单元确定接收到NETCONF客户端发送的恢复出厂配置的命令时，所述替换单元具体用于：
    将所述startup配置数据集中的数据替换为所述出厂配置数据；
    在所述网络设备重启后，将所述running配置数据集中的数据替换为所述startup配置数据集中的数据。
  17. 根据权利要求14所述的网络设备，其特征在于，当所述确定单元确定接收到NETCONF客户端发送的恢复出厂配置的命令时，
    所述替换单元具体用于：将所述startup配置数据集和running配置数据集中的数据同时替换为出厂配置数据集中的出厂配置数据；
    所述下发单元具体用于：将替换后的所述running配置数据集与替换前的所述running配置数据集中的不同的数据下发到所述执行单元。
  18. 根据权利要求13-17任一项所述的网络设备，其特征在于，所述网络设备还包括：
    会话单元，用于建立所述网络设备和所述NETCONF客户端之间的面向连接的传输协议的会话；
    收发单元，用于向所述NETCONF客户端发送所述网络设备的能力集，并接收所述NETCONF客户端发送的所述NETCONF客户端的能力集，所述网络设备的能力集中包括所述网络设备的恢复出厂配置能力标记，所述恢复出厂配置能力标记用于表征所述网络设备具备恢复出厂配置能力。
  19. 根据权利要求13-18任一项所述的网络设备，其特征在于，
    所述收发单元，还用于接收所述NETCONF客户端发送的保存出厂配置的命令；
    所述替换单元，还用于将出厂配置数据集中的数据替换为目标数据，所述目标数据为预设数据、预设配置数据集中的数据或预设文件中的数据。
  20. 根据权利要求19所述的网络设备，其特征在于，所述恢复出厂配置的命令为在NETCONF协议的Yang模型中增加的用于恢复所述网络设备的出厂配置的远程过程调用RPC命令，所述保存出厂配置的命令为在NETCONF协议的Yang模型中增加的用于保存网络设备出厂配置的RPC命令。
  21. 一种恢复网络设备的出厂配置的装置，其特征在于，包括：
    接收单元，用于接收用户恢复所述网络设备的出厂配置的指示；
    发送单元，用于根据NETCONF协议的Yang模型中增加的远程过程调用RPC命令向所述网络设备发送恢复出厂配置的命令，以使得所述网络设备将所述网络设备中的开始startup配置数据集和运行running配置数据集中的数据替换为出厂配置数据集中的出厂配置数据，并基于所述running配置数据集中的数据执行生效操作，所述出厂配置数据集专用于存储所述网络设备的出厂配置数据。
  22. 根据权利要求21所述的装置，其特征在于，所述装置还包括：
    确定单元，用于确定所述网络设备具备恢复出厂配置能力。
  23. 根据权利要求22所述的装置，其特征在于，
    所述接收单元还用于：接收所述网络设备发送的所述网络设备的能力集，所述发送单元还用于向所述网络设备发送所述装置的能力集，所述网络设备的能力集中包括所述网络设备的恢复出厂配置能力标记，所述恢复出厂配置能力标记用于表征所述网络设备具备恢复出厂配置能力；
    所述确定单元具体用于：根据所述网络设备的能力集中的恢复出厂配置能力标记确定所述网络设备具备恢复出厂配置能力。
  24. 根据权利要求21-23任一项所述的装置，其特征在于，
    所述接收单元，还用于接收所述用户保存所述网络设备的出厂配置的指示；
    所述发送单元，还用于根据NETCONF协议的Yang模型中增加的用于保存所述网络设备的出厂配置的RPC命令向所述网络设备发送保存出厂配置的命令，以使得所述网络设备将出厂配置数据集中的数据替换为目标数据，所述目标数据为预设数据、预设配置数据集中的数据或预设文件中的数据。
PCT/CN2017/089468 2016-08-24 2017-06-22 一种恢复网络设备的出厂配置的方法、装置及网络设备 WO2018036255A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP17842680.5A EP3496337B1 (en) 2016-08-24 2017-06-22 Method and device for resetting network device to factory settings, and network device
EP20208552.8A EP3843335A1 (en) 2016-08-24 2017-06-22 Method and apparatus for restoring network device to factory defaults, and network device
US16/283,585 US11159372B2 (en) 2016-08-24 2019-02-22 Method and apparatus for restoring network device to factory defaults, and network device
US17/487,512 US11658870B2 (en) 2016-08-24 2021-09-28 Method and apparatus for restoring network device to factory defaults, and network device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610716564.4A CN107786350B (zh) 2016-08-24 2016-08-24 一种恢复网络设备的出厂配置的方法、装置及网络设备
CN201610716564.4 2016-08-24

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/283,585 Continuation US11159372B2 (en) 2016-08-24 2019-02-22 Method and apparatus for restoring network device to factory defaults, and network device

Publications (1)

Publication Number Publication Date
WO2018036255A1 true WO2018036255A1 (zh) 2018-03-01

Family

ID=61246418

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/089468 WO2018036255A1 (zh) 2016-08-24 2017-06-22 一种恢复网络设备的出厂配置的方法、装置及网络设备

Country Status (4)

Country Link
US (2) US11159372B2 (zh)
EP (2) EP3496337B1 (zh)
CN (2) CN113726581B (zh)
WO (1) WO2018036255A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109547257B (zh) * 2018-12-05 2022-08-12 深圳前海微众银行股份有限公司 网络流量控制方法、装置、设备、系统及存储介质
CN112688794A (zh) * 2019-10-18 2021-04-20 华为技术有限公司 Yang模型的管理方法、装置、系统、设备及存储介质
CN113064658B (zh) * 2019-12-31 2023-09-08 北京华为数字技术有限公司 配置数据的拷贝方法、装置、设备及计算机可读存储介质
CN112399174A (zh) * 2020-11-03 2021-02-23 珠海格力电器股份有限公司 网络摄像头的故障恢复方法和装置、存储介质、电子装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102223291A (zh) * 2010-04-14 2011-10-19 华为技术有限公司 实现设备访问方法和设备及通信系统
CN103281197A (zh) * 2013-04-08 2013-09-04 浙江工商大学 一种基于NETCONF的ForCES配置方法
CN103701653A (zh) * 2014-01-06 2014-04-02 迈普通信技术股份有限公司 一种接口热插拔配置数据的处理方法及网络配置服务器
US9021010B1 (en) * 2012-06-29 2015-04-28 Juniper Networks, Inc. Configuration of applications for distributed computing systems
CN104883266A (zh) * 2014-02-28 2015-09-02 杭州华三通信技术有限公司 网络配置访问方法及装置
US20160103692A1 (en) * 2014-10-09 2016-04-14 Brocade Communications Systems, Inc. Fast reboot for a switch

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6336161B1 (en) * 1995-12-15 2002-01-01 Texas Instruments Incorporated Computer configuration system and method with state and restoration from non-volatile semiconductor memory
US7577829B2 (en) * 2006-04-28 2009-08-18 Dell Products L.P. System and method for maintaining multiple information handling system configuration images
US8145894B1 (en) * 2008-02-25 2012-03-27 Drc Computer Corporation Reconfiguration of an accelerator module having a programmable logic device
US8335171B1 (en) * 2009-09-29 2012-12-18 Juniper Networks, Inc. NETCONF-enabled provisioning in rollback agnostic environment
US8248958B1 (en) * 2009-12-09 2012-08-21 Juniper Networks, Inc. Remote validation of network device configuration using a device management protocol for remote packet injection
HUE036311T2 (hu) * 2010-10-15 2018-07-30 Deutsche Telekom Ag Eljárás egy távvezérelt hálózati elem mûködtetésére
US8533164B2 (en) * 2010-12-09 2013-09-10 International Business Machines Corporation Method and tool to overcome VIOS configuration validation and restoration failure due to DRC name mismatch
US8913519B2 (en) * 2012-09-20 2014-12-16 Tail-f Systems AB Method and network management system for reconfiguring a data network node
US9179336B2 (en) * 2013-02-19 2015-11-03 Mimosa Networks, Inc. WiFi management interface for microwave radio and reset to factory defaults
US10184882B2 (en) * 2013-03-12 2019-01-22 Fedex Supply Chain Logistics & Electroncis, Inc. System and method for providing user guidance for electronic device processing
US9870490B2 (en) * 2014-02-25 2018-01-16 Samsung Electronics Co., Ltd. Apparatus and method for an antitheft secure operating system module
CN111669362B (zh) * 2014-06-09 2022-04-08 华为技术有限公司 信息处理方法、网络节点、验证方法和服务器
WO2017076476A1 (en) * 2015-11-06 2017-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Configuration technique for a network element in a communication network
CN106896888B (zh) * 2015-12-21 2020-04-21 华为技术有限公司 一种恢复出厂设置的装置及方法
US10374884B2 (en) * 2016-07-22 2019-08-06 Cisco Technology, Inc. Automatically, dynamically generating augmentation extensions for network feature authorization

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102223291A (zh) * 2010-04-14 2011-10-19 华为技术有限公司 实现设备访问方法和设备及通信系统
US9021010B1 (en) * 2012-06-29 2015-04-28 Juniper Networks, Inc. Configuration of applications for distributed computing systems
CN103281197A (zh) * 2013-04-08 2013-09-04 浙江工商大学 一种基于NETCONF的ForCES配置方法
CN103701653A (zh) * 2014-01-06 2014-04-02 迈普通信技术股份有限公司 一种接口热插拔配置数据的处理方法及网络配置服务器
CN104883266A (zh) * 2014-02-28 2015-09-02 杭州华三通信技术有限公司 网络配置访问方法及装置
US20160103692A1 (en) * 2014-10-09 2016-04-14 Brocade Communications Systems, Inc. Fast reboot for a switch

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3496337A4 *

Also Published As

Publication number Publication date
EP3496337A1 (en) 2019-06-12
US11159372B2 (en) 2021-10-26
US20220014432A1 (en) 2022-01-13
CN107786350B (zh) 2021-10-15
EP3496337B1 (en) 2020-12-30
US20190190779A1 (en) 2019-06-20
CN107786350A (zh) 2018-03-09
EP3843335A1 (en) 2021-06-30
US11658870B2 (en) 2023-05-23
EP3496337A4 (en) 2019-09-18
CN113726581A (zh) 2021-11-30
CN113726581B (zh) 2022-09-23

Similar Documents

Publication Publication Date Title
US11658870B2 (en) Method and apparatus for restoring network device to factory defaults, and network device
US20230118489A1 (en) Network-Assisted Consensus Protocol
JP2020530722A (ja) Ｐｄｕタイプ設定方法、ｕｅポリシー設定方法、および関連エンティティ
EP2133790A1 (en) MFP software update using web service
US10069942B2 (en) Method and apparatus for changing configurations
EP2945055A1 (en) Application upgrade method and device
US10721335B2 (en) Remote procedure call using quorum state store
US20150378719A1 (en) Information processing device and program updating method
TWI364199B (zh)
WO2019201248A1 (zh) 轻量级机器到机器系统中重新引导的方法和装置
US8725856B2 (en) Discovery of network services
EP2693691A1 (en) Method and apparatus for initializing gateway in device management system
CN113746641A (zh) 一种基于分布式存储的odx协议处理方法
JP5509564B2 (ja) メッセージ送信方法及びプログラム
US10904746B2 (en) Implementation method, apparatus and system for remote access
US8788630B2 (en) System and method for proxy address neutrality
WO2022121492A1 (zh) 文件传输方法、装置、计算机设备及存储介质
US9634987B2 (en) Obtaining a MAC address from an external source
JP2021184235A5 (zh)
JP2009245118A (ja) アプリケーションサービス提供システム、及び方法、並びにアプリケーション移行方法
CN114205404B (zh) 媒体流保持方法、装置、电子设备以及存储介质
CN116414579B (zh) 基于分布式群组通信实现的多副本间数据一致性的方法
WO2013004108A1 (zh) 低级网管系统的管理方法及装置、系统
JP2011108093A (ja) 高可用サーバシステム、高可用サーバシステムの障害時復旧方法、および高可用サーバ
CN117938928A (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: 17842680

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017842680

Country of ref document: EP

Effective date: 20190306