CN109120446B - Zero configuration starting method and equipment - Google Patents

Zero configuration starting method and equipment Download PDF

Info

Publication number
CN109120446B
CN109120446B CN201810962926.7A CN201810962926A CN109120446B CN 109120446 B CN109120446 B CN 109120446B CN 201810962926 A CN201810962926 A CN 201810962926A CN 109120446 B CN109120446 B CN 109120446B
Authority
CN
China
Prior art keywords
node
branch node
session
operation command
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810962926.7A
Other languages
Chinese (zh)
Other versions
CN109120446A (en
Inventor
刘宝琴
罗向征
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Maipu Communication Technology Co Ltd
Original Assignee
Maipu Communication Technology Co Ltd
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 Maipu Communication Technology Co Ltd filed Critical Maipu Communication Technology Co Ltd
Priority to CN201810962926.7A priority Critical patent/CN109120446B/en
Publication of CN109120446A publication Critical patent/CN109120446A/en
Application granted granted Critical
Publication of CN109120446B publication Critical patent/CN109120446B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • H04L41/0677—Localisation of faults
    • 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
    • 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/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's
    • 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/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • 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

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiment of the application discloses a zero configuration starting method and equipment, relates to the technical field of communication, and can solve the problem that the existing scheme can not universally carry out zero configuration starting on network equipment. The method comprises the following steps: the central node receives an operation command sent to the target branch node by the controller through the network configuration channel, and sends a session message to the target branch node through the two-layer forwarding channel, wherein the session message comprises the operation command, and the two-layer forwarding channel is established according to a two-layer forwarding table after generating the two-layer forwarding table for the network topology discovered according to the two-layer protocol and the identity of each node. The embodiment of the application is used for zero configuration starting of the network equipment in the headquarters-branch type network.

Description

Zero configuration starting method and equipment
Technical Field
The present application relates to the field of communications technologies, and in particular, to a zero configuration starting method and device.
Background
Software Defined Networking (SDN) is often used in an enterprise Network to implement separation of management, control and forwarding, so as to improve Network utilization, improve operation and maintenance level and quality, and accelerate efficiency of device provisioning and service deployment. The traditional network equipment has specific advantages in forwarding and interconnection, and is indispensable in enterprise networking. When the SDN controller is combined with the traditional network to achieve centralized control and visual operation and maintenance, the traditional network equipment is wide in distribution, complex in configuration, long in time consumption and not in line with the requirements of rapid deployment and rapid service opening of network expansion requirements, and much manpower needs to be invested for opening configuration and debugging.
The current solutions for solving the problem of complex network device configuration during enterprise networking include the following two solutions: the first scheme is as follows: the network equipment supports an OpenFlow protocol, the SDN controller is used for issuing and controlling the flow table in a centralized manner, and the network equipment only needs to be simply configured; the second scheme is as follows: the network device uses Link Layer Discovery Protocol (LLDP) technology, and cooperates with a Dynamic Host Configuration Protocol Server (DHCP Server)/DHCP Relay (DHCP Relay) and a network management platform to provide Configuration issuing, Configuration starting, and the like.
However, the first scheme requires that all network devices support the OpenFlow protocol, which has a certain limitation on part of enterprise network networking; the second scheme requires all network devices to operate in a shared network, and to configure a DHCP server, a gateway platform, and the like, and for a headquarters-branch type hierarchical network structure, a DHCP relay, and the like, need to be configured in the network. Accordingly, the Network device also needs to start functions such as multicast, LLDP, Simple Network Management Protocol (SNMP), and DHCP, and the device cannot be loaded and operated without configuration. When the network equipment is enabled to be in zero configuration starting, some intermediate equipment needs to be configured to achieve the purpose of automatic configuration loading, the intermediate equipment is in redundant configuration in the whole network operation, and when problems occur in the zero configuration loading process of the network equipment, remote debugging is inconvenient to carry out. Therefore, the existing scheme can not universally perform zero configuration starting of the network equipment, and the implementation method has limitations and high equipment maintenance cost.
Disclosure of Invention
The embodiment of the application provides a zero configuration starting method and equipment, which can solve the problem that the existing scheme can not universally carry out zero configuration starting of network equipment.
In a first aspect, a zero configuration boot method is provided, including: the central node receives an operation command sent to the target branch node by the controller through the network configuration channel; the central node sends a session message to the target branch node through the two-layer forwarding channel, wherein the session message comprises an operation command. By the scheme, the controller can perform unified and centralized management on the target branch nodes through the central node, remote control configuration file issuing, loading, uploading and the like can be realized, zero configuration starting of the target branch nodes is achieved, concurrent configuration of a plurality of target branch nodes can be supported, graphical fault location and the like can be supported, and efficiency of transportation and network deployment is improved while labor cost and time cost are saved.
In one possible design, before the central node receives the operation command sent by the controller to the target branch node through the network configuration protocol, the method further includes: the central node obtains a network topological structure between the central node and each branch node through a two-layer protocol running between the central node and each branch node, generates a two-layer forwarding table according to the identity of each branch node in the network topological structure, and establishes a two-layer forwarding channel with each branch node according to the two-layer forwarding table. The design can establish a two-layer forwarding channel between the central node and the branch nodes, so that the central node forwards corresponding session messages and operation commands to the branch nodes through the two-layer forwarding channel, and zero configuration starting of the branch nodes is realized.
In a possible design, if the operation command is used to instruct to issue the configuration file to the target branch node, before the central node sends the session packet to the target branch node through the two-layer forwarding channel, the method further includes: the central node determines whether a configuration file to be issued exists; if the configuration file exists, the central node packages the operation command and the file in a session message; and if the configuration file does not exist or the target branch node is not reachable, the central node feeds back operation failure to the controller. Before the central node sends the session message to the target branch node, the central node judges the configuration file and/or the operation command and carries out corresponding processing according to the judgment result, so that the session message can be effectively transmitted.
In one possible design, the session packet includes an acknowledgement-required flag, where the acknowledgement-required flag is used to indicate that the target branch node feeds back an acknowledgement packet when receiving the session packet, and the method further includes: and if the central node does not receive the confirmation message within the preset time, retransmitting the session message to the target branch node. By setting the flag to be confirmed in the session message, the session message can be reliably transmitted between the central node and the target branch node.
In one possible design, the method further includes: the central node receives a feedback message sent by the target branch node through the two-layer forwarding channel, and the feedback message indicates the execution result of the operation command or indicates that the session is cancelled; and the central node sends the execution result of the operation command to the controller through the network configuration channel. The design can lead the controller to timely acquire the execution result of the target branch node aiming at the issued operation command, so that the controller can conveniently carry out subsequent processing according to the execution result,
in a second aspect, a zero-configuration boot method is provided, including: and the branch node receives the session message issued by the central node through the two-layer forwarding channel and processes the session message, wherein the session message comprises an operation command. The design can lead the branch node to realize the zero configuration starting of the equipment according to the received conversation message under the condition of not needing intermediate configuration.
In a possible design, if a to-be-confirmed flag is set in a session message, a branch node sends a response message carrying the confirmation flag to a central node according to the session message, wherein the to-be-confirmed flag is used for indicating a target branch node to feed back the confirmation message when receiving the session message. By setting the flag to be confirmed in the session message, the reliable transmission of the session message between the branch node and the central node can be ensured.
In one possible design, when the branch node is a target branch node, the branch node verifies the session message, executes the operation command in the session for the message successfully verified, and acquires the execution result of the operation command; when the branch node is not the target branch node, the branch node forwards the session message; the method further comprises the following steps: the branch node reports a feedback message to the central node through the two-layer forwarding channel, and the feedback message indicates the execution result of the operation command or indicates that the session is cancelled. By the design, the session message can be forwarded to the target branch node hop by hop through each branch node, so that the target branch node can realize zero configuration starting.
In a third aspect, a central node device is provided, including: the controller communication unit is used for receiving the operation command sent by the controller through the network configuration channel; and the two-layer transmission unit is used for sending the session message to the target branch node through the two-layer forwarding channel, wherein the session message comprises an operation command or comprises an operation command.
In one possible design, the central node apparatus further includes: the second-layer forwarding channel establishing unit is used for acquiring a network topology structure between the central node and each branch node through a second-layer protocol running between the central node and each branch node, generating a second-layer forwarding table according to the identity of each branch node in the network topology structure, and establishing a second-layer forwarding channel between the central node and each branch node according to the second-layer forwarding table.
In one possible design, if the operation command is used to instruct the target branch node to issue the configuration file, the central node apparatus further includes: the command processing unit is used for determining whether the configuration file to be issued exists or not; the session processing unit is used for packaging the operation command and the configuration file in a session message; and the controller communication unit is also used for feeding back the operation failure to the controller.
In one possible design, the session message includes a flag to be confirmed, and the flag to be confirmed is used for indicating that the target branch node feeds back the confirmation message when receiving the session message; and the session processing unit is used for retransmitting the session message to the target branch node if the central node does not receive the confirmation message within the preset time.
In a possible design, the two-layer transmission unit is configured to receive a feedback message sent by a target branch node through a two-layer forwarding channel, where the feedback message indicates an execution result of an operation command or indicates to cancel the session; and the controller communication unit is also used for sending the execution result of the operation command to the controller through the network configuration channel.
In a fourth aspect, there is provided a branch node device, comprising: the system comprises a two-layer transmission unit, a central node and a second-layer forwarding unit, wherein the two-layer transmission unit is used for receiving a session message issued by the central node through a two-layer forwarding channel, and the session message comprises an operation command; and the session processing unit is used for processing the session message.
In one possible design, the branch node apparatus further includes: the command receiving unit is used for executing the operation command in the session message for the message successfully verified and acquiring the execution result of the operation command; and the two-layer transmission unit is used for reporting a feedback message to the central node through the two-layer forwarding channel, wherein the feedback message indicates the execution result of the operation command or indicates that the session is cancelled.
The embodiment of the application provides a zero configuration starting method and equipment.A central node receives an operation command sent to a target branch node by a controller through a network configuration channel and sends a session message to the target branch node through a two-layer forwarding channel, wherein the session message comprises the operation command. By the scheme provided by the embodiment of the application, zero configuration starting of the network equipment can be realized in a headquarters-branch type network without the assistance of any intermediate equipment, time and cost can be saved, and network operation and deployment efficiency can be effectively improved.
Drawings
Fig. 1 is a schematic diagram of a headquarters-branch network architecture according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a zero configuration starting method according to an embodiment of the present application;
fig. 3 is a schematic diagram of a header field structure of a session message provided in an embodiment of the present application;
fig. 4 is a schematic flowchart of a zero configuration starting method according to an embodiment of the present application;
fig. 5 is a schematic flowchart of a zero configuration starting method according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a central node device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a central node device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a central node device according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a branch node device according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a branch node device according to an embodiment of the present application;
fig. 11 is a schematic structural diagram of a branch node device according to an embodiment of the present application.
Detailed Description
For ease of understanding, some of the concepts related to the present application are illustratively presented for reference. As follows:
software defined networking: software Defined Network (SDN) is a new Network architecture technology, and is used to integrate management and control functions such as Network management, service deployment, Network and service visualization into one Software system, so that Network element devices receive centralized management and control of the Software system, thereby being beneficial to realizing requirements of rapid deployment, flexible scheduling and the like of the whole Network service.
OpenFlow: in the SDN network, a communication protocol is used between an SDN controller and network element equipment, and the SDN controller can manage and control forwarding strategies, running states and statistical information of the network element equipment by using the protocol.
Dynamic host configuration protocol: the Dynamic Host Configuration Protocol (DHCP) is a network Protocol of a local area network, and is used to automatically allocate an Internet Protocol (IP) address to an internal network device or a terminal.
Link layer discovery protocol: link Layer Discovery Protocol (LLDP) is a vendor-independent two-Layer Protocol that allows network devices to advertise their device identities and characteristics, etc. in a local subnet.
Simple network management protocol: simple Network Management Protocol (SNMP) is one of The protocols in The Internet Protocol cluster defined by The Internet Engineering Task Force (IETF), and is used for supporting a Network Management system, monitoring various events and states of Network devices and Network terminals, and The like.
Network configuration protocol: network Configuration Protocol (Network Configuration Protocol) is a Network Configuration Protocol based on Extensible Markup Language (XML), and is mainly used for data exchange, fault management, and the like, and the Protocol is divided into four layers: the device comprises a content layer, an operation layer, a Remote Procedure Call Protocol (RPC) layer and a communication Protocol layer.
A central node device: the central node is positioned at the central position of the network system and can establish a direct or indirect communication channel with all other node equipment in the network system.
The branch node device: the branch nodes are located at the edge of the network or between the center and the edge communication path, are used for accessing or converging network services, and may be referred to as converging branch nodes and accessing branch nodes respectively according to their locations.
The present application can be applied to a headquarters-branch type network of an enterprise, as shown in fig. 1, including: the SDN system comprises an SDN controller and forwarding equipment (router or switch), wherein the forwarding equipment can be divided into a central node and branch nodes according to different positions of the forwarding equipment, and the branch nodes comprise convergence branch nodes and access branch nodes. The central nodes and the SDN controller are in IP accessibility in the same IP network, are physically connected with all the convergence branch nodes and the access branch nodes in the network directly or indirectly through Ethernet lines, are physically accessible, and work independently. The central node is otherwise identical to the branch nodes, except that it needs to communicate with the controller.
The embodiment of the present application provides a zero configuration starting method, which is applied to a central node, and as shown in fig. 2, includes:
201. the central node receives the operation command sent by the controller to the target branch node through the network configuration channel.
The central node receives an operation command sent by the controller through a network configuration channel established between the central node and the controller, wherein the operation command is used for instructing the central node to issue a configuration file to a target branch node, or instructing the target branch node to load the configuration file or upload the configuration file or send an event status report.
Optionally, the operation command may also carry an Identifier (ID) of the target branch node.
The method for sending the operation command by the controller can be issued in a concurrent manner for a plurality of target branch nodes, specifically, a plurality of target branch nodes are selected on the controller, and the central node is notified to perform a corresponding operation command session concurrently, so that the deployment efficiency of the whole network can be effectively improved.
And the central node and the controller are communicated through a network configuration channel, so that the controller can be allowed to use a YANG model interface, and a graphical front-end interface is conveniently supported. Therefore, the opening deployment of the whole network, such as configuration file issuing, configuration file loading, configuration file uploading, fault removal and the like, can select the target branch node to perform corresponding operation through the visual front-end interface, so that the operability and convenience are improved, and the manpower resource and the time resource are saved.
202. The central node sends the conversation message to the target branch node through the two-layer forwarding channel.
After receiving the operation command from the controller, the central node checks whether the target branch node is reachable, and further, when the operation command is used for instructing the central node to issue the configuration file to the target branch node, the central node also checks whether the configuration file to be issued exists, and the configuration file to be issued can be transmitted to the central node by the controller through the IP channel.
The controller may transmit the configuration File to be delivered to the central node through the IP channel by using a File Transfer Protocol (FTP), or by using other methods, which is not limited in this application.
If the check is not passed, that is, the target branch is not reachable, and/or the configuration file to be issued does not exist, the central node feeds back the operation failure to the controller.
Optionally, an implementation manner provided in this embodiment of the present application is that, while the central node feeds back the operation failure to the controller, the central node may also carry a specific failure reason.
When the operation command indicates that the target branch node loads a configuration file or uploads the configuration file or sends an event state report, if the target branch node is determined to be reachable, the examination is passed; when the operation command is used for indicating the central node to issue the configuration file to the target branch node, the inspection is passed only when the target branch node is required to be reached and the configuration file to be issued exists. After the check is passed, the central node sends a session message to the target branch node through the two-layer forwarding channel, wherein the session message comprises an operation command.
Optionally, in this embodiment of the application, when the operation command is used to instruct the central node to issue the configuration file to the target branch node, the session packet may also include the configuration file to be issued.
If the configuration file to be delivered is too large, an optional implementation manner provided in this embodiment of the present application is that the central node encapsulates the operation command and the configuration file into a plurality of session message segments, that is, encapsulates the operation command and the configuration file to be delivered into at least one session message.
Optionally, an implementation manner provided in this embodiment of the present invention is that, as shown in fig. 3, a header field of a session packet includes a session ID, a session sequence number, a session type, a session subtype, and a session flag field, where these fields are used to ensure reliability of sessions between devices such as a central node and a branch node, and to handle problems such as disorder, packet loss, duplicate packets, and timeout of the session packet.
The session ID is used for distinguishing sessions of different times between the same central node and a target node pair, and the field is used for avoiding problems of message repetition and the like;
the session sequence number is used for identifying different messages in one session, so that the problems of disorder of message segments, packet loss, message repetition and the like in one session can be prevented;
the session type is used for distinguishing different types of sessions or services, such as configuration file issuing, operation command issuing, configuration file uploading and the like;
the session sub-types are used for distinguishing different types of messages in one session, for example, a session issued by one configuration can contain various sub-types of messages such as file information, file content, file verification results, session cancellation and the like, and the data areas of each type of message have different formats;
and the session mark is used for identifying optional characteristics of the session, such as a confirmation-needed mark, a confirmation mark, a fragmentation mark, whether data exists or not and the like. The flag to be confirmed indicates that the message needs to wait for the receiving confirmation of the destination node, if the message is not received, the message is retransmitted, and after the message is retransmitted for a plurality of times, if the confirmation is not received, the session is interrupted. The message with the confirmation mark is the confirmation of the received message needing to be confirmed. The fragmentation mark is used for indicating that the message is not transmitted completely, and message fragments are still transmitted subsequently. Whether the data mark exists or not represents whether a data field exists in the session message except the data head or not;
reserved fields for ensuring 4-byte alignment of the session messages and for subsequent field extension;
and the data is an optional field, the data content of the session message is contained, and the length of the field is 0-N bytes according to the session subtype.
When the session message includes the mark needing to be confirmed, the central node blocks and waits for the confirmation message sent by the target branch node after the session message is sent, and if the confirmation message is not received within the preset time, the session message is sent to the target branch node again. If the confirmation message is not received after the retransmission is carried out for a plurality of times, the session is interrupted. If the confirmation message is received, the subsequent process is continued, such as sending the next session message.
It should be noted that the session between the central node and the target branch node is uniquely identified by the central node ID, the target node ID, the session ID, and the session type field.
In the implementation process, the two-layer forwarding channel is established according to the network topology discovered by the two-layer protocol and the identity ID of each node, and the specific establishment process is as follows: the central node obtains a network topological structure between the central node and each branch node through a two-layer protocol running between the central node and each branch node, generates a two-layer forwarding table according to the identity of each branch node in the network topological structure, and establishes a two-layer forwarding channel with each branch node according to the two-layer forwarding table. The two-layer protocol can be customized and can also be expanded based on the existing two-layer protocol.
The embodiment of the application provides a zero configuration starting method, wherein a central node receives an operation command sent to a target branch node by a controller through a network configuration channel and sends a session message to the target branch node through a two-layer forwarding channel, wherein the session message comprises the operation command. By the scheme provided by the embodiment of the application, zero configuration starting of the network equipment can be realized in a headquarters-branch type network without the assistance of any intermediate equipment, time and cost can be saved, and network operation and deployment efficiency can be effectively improved.
After the central node sends a session packet to the target branch node, an embodiment of the present application provides a zero configuration starting method, which is applied to the central node, and as shown in fig. 4 in combination with fig. 2, includes:
203. and the central node receives a feedback message sent by the target branch node through the two-layer forwarding channel.
The central node may receive a feedback message sent by the target branch node through the two-layer forwarding channel, where the feedback message indicates an execution result of the operation command or indicates to cancel the session. If the feedback message indicates the execution result of the operation command, the central node may send the received execution result of the operation command to the controller through the network configuration channel.
Optionally, an implementation manner provided in this embodiment of the present application is that an execution result of the operation command is an execution result of the target branch node for the session packet, where the execution result of the session packet may include that the file is correctly or incorrectly issued, and if the file is incorrectly issued, the execution result may further include a specific error reason. The controller may perform subsequent processing or fault location according to the execution result of the received session packet.
Optionally, an implementation manner provided in this embodiment of the present application is that an execution result of the operation command is an execution result of loading the file by the target branch node, and the execution result of loading the file may include a successful loading or an error loading. If the file loading is wrong, the loading error reason can be further included, after the controller receives the execution result of the file loading error, remote fault location can be carried out according to the error reason, and after the corresponding error is modified, the issuing operation command is retransmitted, such as instructing the central node to issue the file to the target branch node, instructing the target branch node to load the file, and the like. Further, the controller may also issue an operation command to instruct the target branch node to upload a file, so as to compare configurations according to an error file, perform a new deployment operation, and the like.
Optionally, an implementation manner provided in this embodiment of the present invention is that, when an error occurs in the sending and receiving processes of multiple session packets between the central node and the target branch node, the target branch node may send a packet of "cancel session" to the central node to interrupt file transmission, where the message of cancel session may include a reason for canceling session. At this time, the feedback message received by the central node may also be used to instruct to cancel the session.
Of course, the central node may also send a message of "canceling session" to interrupt file transmission, which is not limited in this application.
The embodiment of the present application provides a zero configuration starting method, which is applied to a branch node, as shown in fig. 5, and includes:
501. and the branch node receives the session message sent by the central node through the two-layer forwarding channel.
The session message received by the branch node includes an operation command, and the operation command is used for instructing the central node to issue a configuration file to the target branch node, or instructing the target branch node to load the configuration file, or uploading the configuration file, or sending an event status report.
In this embodiment of the application, when the operation command is used to instruct the central node to issue the configuration file to the target branch node, the operation command may also include the configuration file to be issued.
Optionally, the operation command may also carry a target branch node ID.
The two-layer forwarding channel is established according to the network topology discovered by the two-layer protocol and the identity ID of each node, and the specific establishment process is as follows: the central node obtains a network topological structure between the central node and each branch node through a two-layer protocol running between the central node and each branch node, generates a two-layer forwarding table according to the identity of each branch node in the network topological structure, and establishes a two-layer forwarding channel with each branch node according to the two-layer forwarding table. The two-layer protocol can be customized and can also be expanded based on the existing two-layer protocol.
It should be noted that the session between the central node and the target branch node is uniquely identified by the central node ID, the target node ID, the session ID, and the session type field.
502. And the branch node processes the session message.
After receiving the session message from the central node, the branch node compares whether the branch node is a target node according to the target node ID in the session message, if not, searches a two-layer forwarding table stored in the node equipment, and sends the session message out from an outlet interface according to the two-layer forwarding table. If the session message is confirmed to be provided with the mark needing to be confirmed, the branch node sends a response message carrying the confirmation mark to the central node according to the session message, wherein the mark needing to be confirmed is used for indicating the target branch node to feed back the confirmation message when receiving the session message. Then, the branch node processes the conversation de-multiplexing processing to the conversation message, and executes different operation orders according to the conversation type.
Optionally, if the operation command is used to instruct the central node to send the configuration file to the target branch node, that is, instruct the target branch node to receive the configuration file, and after receiving the session packet, the branch node writes the file content data in the session packet into the corresponding local configuration file until all the session packets are received. After the file is received, the branch node checks the content of the received file to ensure integrity, for example, checking by using Message-Digest Algorithm 5 (MD 5) to obtain a check result.
After processing the session packet, an embodiment of the present application further provides a zero configuration starting method, which is applied to a branch node, as shown in fig. 5, and includes:
503. and the branch nodes report the feedback messages to the central node through the two-layer forwarding channel.
The branch node reports a feedback message to the central node through the two-layer forwarding channel, wherein the feedback message is used for indicating the execution result of the operation command or indicating the cancellation of the session.
Optionally, an implementation manner provided in this embodiment of the present application is that an execution result of the operation command is an execution result of the target branch node for the session packet, the execution result of the session packet may include that the file is correctly or incorrectly issued, and if the file is incorrectly issued, the execution result may further include a specific error reason.
Optionally, an implementation manner provided in this embodiment of the present application is that the execution result of the operation command is an execution result of loading the file by the target branch node, and the execution result of loading the file may include a successful loading or an error loading. If the file is loaded wrongly, the loading error reason can be further included.
Optionally, an implementation manner provided in this embodiment of the present invention is that, when an error occurs in the sending and receiving processes of multiple session packets between the central node and the target branch node, the target branch node may send a packet of "cancel session" to the central node to interrupt file transmission, where the message of cancel session may include a reason for canceling session. At this time, the feedback message reported by the branch node may also be used to indicate to cancel the session.
The embodiment of the application provides a zero configuration starting method, wherein a branch node receives a session message issued by a central node through a two-layer forwarding channel, the session message comprises an operation command, and after the branch node processes the session message according to the operation command in the session message, the branch node reports a feedback message to the central node through the two-layer forwarding channel. By the scheme provided by the embodiment of the application, zero configuration starting of the network equipment can be realized in a headquarters-branch type network without the assistance of any intermediate equipment, time and cost can be saved, and network operation and deployment efficiency can be effectively improved.
The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. It is to be understood that each network element, such as the central node apparatus, the branch node apparatus, etc., contains corresponding hardware structures and/or software modules for performing each function in order to realize the above functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The embodiment of the application can perform functional module division on the central node device according to the method example. For example, the functional blocks may be divided for the respective functions, or two or more functions may be integrated into one processing block. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.
In the case of dividing each functional module by corresponding functions, fig. 6 shows a schematic structural diagram of a possible central node device in the foregoing embodiment, and the central node device 60 in this application may include: a controller communication unit 601, a command processing unit 602, a session processing unit 603, a two-layer transmission unit 604, and a two-layer forwarding channel establishing unit 605. The controller communication unit 601 is configured to support the central node to execute the process 201 in fig. 2, the process 201 in fig. 4; command processing unit 602 is used to support the central node to perform other processes of the techniques described herein; session processing unit 603 is used to support the central node to perform other processes for the techniques described herein; the two-layer transmission unit 604 is configured to support the central node to perform the process 202 in fig. 2, and the processes 202 and 203 in fig. 4; layer two forwarding path setup unit 605 is used to support the central node to perform other processes for the techniques described herein. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.
In the case of integrated units, fig. 7 shows a schematic diagram of a possible structure of the central node device involved in the above-described embodiment. For example, processing module 701 is used to support a central node in performing other processes for the techniques described herein. The communication module 702 is used to support the central node to execute the processes 201, 202 in fig. 2, the processes 201, 202, 203 in fig. 4, and the communication between the central node and other network entities, for example, the communication between the functional modules or the network entities shown in fig. 1, fig. 9, fig. 10, and fig. 11. The memory module 703 is used to store program codes and data of the central node.
The Processing module 701 may be a Processor or a controller, such as a Central Processing Unit (CPU), a general-purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module 702 may be a transceiver, a transceiver circuit or a communication interface, etc.
Referring to fig. 8, the center node apparatus 80 includes: a transceiver 801, a processor 802, a memory 803, and a bus 804. Wherein, the transceiver 801, the processor 802 and the memory 803 are connected to each other by a bus 804; the bus 804 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus.
The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device. In the embodiment of the present application, functional modules may be divided for the central node according to the above method, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.
According to the method example, the functional modules of the branch node equipment can be divided. For example, the functional blocks may be divided for the respective functions, or two or more functions may be integrated into one processing block. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.
In the case of dividing each functional module by corresponding functions, fig. 9 shows a schematic diagram of a possible structure of the branch node apparatus in the foregoing embodiment, and the branch node apparatus 90 of the present application may include: a command processing unit 901, a session processing unit 902 and a two-layer transmission unit 903. Command processing unit 901 is used to support the branching node to perform other processes of the techniques described herein; the session processing unit 902 is used to support the branch node to execute the process 502 in fig. 5; the two-layer transmission unit 903 is used to support the branch node to execute the processes 501 and 503 in fig. 5. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.
In the case of an integrated unit, fig. 10 shows a possible structural diagram of the branch node device involved in the above-described embodiment. For example, processing module 1001 is used to support a branch node to perform process 502 in FIG. 5. The communication module 1002 is used to support the branch node to execute the processes 501 and 503 in fig. 5, and the communication between the branch node and other network entities, for example, the functional modules or network entities shown in fig. 1, fig. 6, fig. 7, and fig. 8. The storage module 1003 is used to store program codes and data of the central node.
The Processing module 1001 may be a Processor or a controller, such as a Central Processing Unit (CPU), a general-purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module 1002 may be a transceiver, a transceiver circuit or a communication interface, etc.
Referring to fig. 11, the branch node apparatus 110 includes: a transceiver 1101, a processor 1102, a memory 1103, and a bus 1104. Wherein the transceiver 1101, the processor 1102 and the memory 1103 are connected to each other by a bus 1104; the bus 1104 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 11, but this is not intended to represent only one bus or type of bus.
The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device.
Those skilled in the art will recognize that in one or more of the examples described above, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (15)

1. A zero configuration boot method, comprising:
the central node receives an operation command sent to the target branch node by the controller through the network configuration channel;
the central node sends a session message to the target branch node through a two-layer forwarding channel, wherein the session message includes the operation command, so that the target branch node completes zero configuration starting based on an operation instruction in the session message, and the operation command is used for instructing the central node to issue a configuration file to the target branch node, or instructing the target branch node to load the configuration file, upload the configuration file, or send an event status report.
2. The zero-configuration startup method according to claim 1, wherein before the central node receives the operation command sent by the controller to the target branch node through the network configuration protocol, the method further comprises:
the central node acquires a network topology structure between the central node and each branch node through a two-layer protocol running between the central node and each branch node of the central node, generates a two-layer forwarding table according to the identity of each branch node in the network topology structure, and establishes a two-layer forwarding channel with each branch node according to the two-layer forwarding table.
3. The zero-configuration startup method according to claim 1, wherein if the operation command is used to instruct to issue a configuration file to the target branch node, before the central node sends the session packet to the target branch node through the two-layer forwarding channel, the method further comprises:
the central node determines whether the configuration file to be issued exists;
if the configuration file exists, the central node packages the operation command and the configuration file in the session message;
and if the configuration file does not exist or the target branch node is not reachable, the central node feeds back operation failure to the controller.
4. The zero-configuration startup method according to any one of claims 1 to 3, wherein the session packet includes a flag that needs to be confirmed, and the flag that needs to be confirmed is used to instruct the target branch node to feed back a confirmation packet when receiving the session packet;
the method further comprises the following steps: and if the central node does not receive the confirmation message within the preset time, retransmitting the session message to the target branch node.
5. A zero-configuration boot method according to any of claims 1-3, characterized in that the method further comprises:
the central node receives a feedback message sent by the target branch node through the two-layer forwarding channel, wherein the feedback message indicates the execution result of the operation command, or the feedback message indicates that the session is cancelled;
and the central node sends the execution result of the operation command to the controller through the network configuration channel.
6. A zero configuration boot method, comprising:
a branch node receives a session message issued by a central node through a two-layer forwarding channel, wherein the session message comprises an operation command sent by a controller so that a target branch node completes zero configuration starting based on an operation instruction in the session message, and the operation command is used for indicating the central node to issue a configuration file to the target branch node, or indicating the target branch node to load the configuration file, upload the configuration file or send an event state report;
and the branch node processes the session message.
7. The zero-configuration starting method according to claim 6, wherein if the session packet is provided with a flag that needs to be confirmed, the branch node sends a response packet carrying a confirmation flag to the central node according to the session packet, wherein the flag that needs to be confirmed is used to indicate that the target branch node feeds back the confirmation packet when receiving the session packet.
8. The zero-configuration startup method according to claim 6, wherein the processing of the session packet by the branch node includes:
when the branch node is a target branch node, the branch node verifies the session message, executes the operation command in the session message for the message which is successfully verified, and acquires the execution result of the operation command; when the branch node is not a target branch node, the branch node forwards the session message;
the method further comprises the following steps:
and the branch node reports a feedback message to the central node through the two-layer forwarding channel, wherein the feedback message indicates the execution result of the operation command, or the feedback message indicates that the session is cancelled.
9. A center node apparatus, comprising:
the controller communication unit is used for receiving an operation command sent by the controller to a target branch node through a network configuration channel so as to enable the target branch node to complete zero configuration starting based on an operation instruction in a session message, wherein the operation command is used for indicating a central node to issue a configuration file to the target branch node, or indicating the target branch node to load the configuration file or upload the configuration file or send an event state report;
and the two-layer transmission unit is used for sending a session message to the target branch node through a two-layer forwarding channel, wherein the session message comprises the operation command.
10. The center node apparatus of claim 9, further comprising a two-layer forwarding path establishing unit, configured to obtain a network topology between the center node and each branch node of the center node through a two-layer protocol running between the center node and each branch node, generate a two-layer forwarding table according to an identity of each branch node in the network topology, and establish a two-layer forwarding path between the center node apparatus and each branch node according to the two-layer forwarding table.
11. The central node apparatus of claim 9, wherein if the operation command is used to instruct the target branch node to issue a configuration file, the central node apparatus further comprises:
the command processing unit is used for determining whether the configuration file to be issued exists or not;
the session processing unit is used for encapsulating the operation command and the configuration file into the session message;
the controller communication unit is further configured to feed back an operation failure to the controller.
12. The center node apparatus according to claim 9, wherein the session packet includes a flag that needs to be confirmed, and the flag that needs to be confirmed is used to instruct the target branch node to feed back a confirmation packet when receiving the session packet;
and the session processing unit is further used for retransmitting the session message to the target branch node if the central node does not receive the confirmation message within the preset time.
13. The center node device according to any one of claims 9 to 12, wherein the two-layer transmission unit is further configured to receive a feedback packet sent by the target branch node through the two-layer forwarding channel, where the feedback packet indicates an execution result of the operation command, or the feedback packet indicates to cancel the session; and/or the presence of a gas in the gas,
the controller communication unit is further configured to send an execution result of the operation command to the controller through the network configuration channel.
14. A branch node apparatus, comprising:
the system comprises a two-layer transmission unit, a two-layer forwarding channel and a central node, wherein the two-layer transmission unit is used for receiving a session message issued by the central node through the two-layer forwarding channel, the session message comprises an operation command sent by a controller so that a target branch node completes zero configuration starting based on an operation instruction in the session message, and the operation command is used for indicating the central node to issue a configuration file to the target branch node, or indicating the target branch node to load the configuration file, upload the configuration file or send an event state report;
and the session processing unit is used for processing the session message.
15. The branch node apparatus of claim 14,
the command receiving unit is used for executing the operation command in the session message for the message successfully verified and acquiring the execution result of the operation command;
the two-layer transmission unit is further configured to report a feedback packet to the central node through the two-layer forwarding channel, where the feedback packet indicates an execution result of the operation command, or the feedback packet indicates that the session is cancelled.
CN201810962926.7A 2018-08-22 2018-08-22 Zero configuration starting method and equipment Active CN109120446B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810962926.7A CN109120446B (en) 2018-08-22 2018-08-22 Zero configuration starting method and equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810962926.7A CN109120446B (en) 2018-08-22 2018-08-22 Zero configuration starting method and equipment

Publications (2)

Publication Number Publication Date
CN109120446A CN109120446A (en) 2019-01-01
CN109120446B true CN109120446B (en) 2022-02-15

Family

ID=64860072

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810962926.7A Active CN109120446B (en) 2018-08-22 2018-08-22 Zero configuration starting method and equipment

Country Status (1)

Country Link
CN (1) CN109120446B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110213089B (en) * 2019-05-17 2022-02-15 烽火通信科技股份有限公司 Method and system for accessing large-scale remote zero configuration equipment to network management
CN112865991A (en) * 2019-11-26 2021-05-28 中兴通讯股份有限公司 Zero configuration ZTP state switching method, implementation equipment and storage medium
CN113872783B (en) * 2020-06-30 2023-08-22 华为技术有限公司 Method, apparatus and computer readable storage medium for network configuration
CN113556784B (en) * 2021-07-29 2023-05-26 新华三技术有限公司 Network slice realization method and device and electronic equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104378296A (en) * 2013-08-15 2015-02-25 杭州华三通信技术有限公司 Message forwarding method and device
CN107360105A (en) * 2016-05-10 2017-11-17 中兴通讯股份有限公司 The method, apparatus and system, OLT of SDN management controls
CN108075908A (en) * 2016-11-11 2018-05-25 京东方科技集团股份有限公司 The method and device of processing operation request
CN108123870A (en) * 2016-11-30 2018-06-05 华为技术有限公司 Message forwarding method and device
CN108206746A (en) * 2016-12-16 2018-06-26 华为技术有限公司 A kind of network transmission control method and relevant device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104378296A (en) * 2013-08-15 2015-02-25 杭州华三通信技术有限公司 Message forwarding method and device
CN107360105A (en) * 2016-05-10 2017-11-17 中兴通讯股份有限公司 The method, apparatus and system, OLT of SDN management controls
CN108075908A (en) * 2016-11-11 2018-05-25 京东方科技集团股份有限公司 The method and device of processing operation request
CN108123870A (en) * 2016-11-30 2018-06-05 华为技术有限公司 Message forwarding method and device
CN108206746A (en) * 2016-12-16 2018-06-26 华为技术有限公司 A kind of network transmission control method and relevant device

Also Published As

Publication number Publication date
CN109120446A (en) 2019-01-01

Similar Documents

Publication Publication Date Title
CN109120446B (en) Zero configuration starting method and equipment
US9191290B2 (en) Methods and devices for monitoring a data path
JP4881564B2 (en) Data transfer device, multicast system, and program
JP3850391B2 (en) Router interface backup execution method using VRRP (Virtual Router Redundancy Protocol)
JP4840236B2 (en) Network system and node device
CN110324165B (en) Network equipment management method, device and system
EP1892929B1 (en) A method, an apparatus and a system for message transmission
CN104735001B (en) Link discovery method, apparatus and system in software defined network
US20130077481A1 (en) Network system and network redundancy method
US20210135967A1 (en) Intelligent in-band telemetry auto-configuration for ip networks
CN103916275A (en) BFD detection device and method
CN112769614B (en) Automatic management method of VPN (virtual private network) on demand and intercommunication system of heterogeneous network
CN108737183B (en) Method and device for monitoring forwarding table item
US8060628B2 (en) Technique for realizing high reliability in inter-application communication
US20080267080A1 (en) Fault Verification for an Unpaired Unidirectional Switched-Path
CN108599980B (en) Fault diagnosis method and device
WO2021143524A1 (en) Fault detection method, and apparatus
EP3059907B1 (en) Network packet forwarding method and device
CN109120520B (en) Fault processing method and equipment
KR102092015B1 (en) Method, apparatus and computer program for recognizing network equipment in a software defined network
CN108521336A (en) A kind of method and device for controlling routing networking IP address conflict
CN104754762A (en) Method for automatically finding controller in software-defined network, controller and system
JP4992962B2 (en) Data transfer device, multicast system, and program
CN114070781B (en) Data communication method, device, system and computer equipment
TWI451264B (en) Signal transformation apparatus with redundant mechanism and method of implementing redundancy

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant