JP6537115B2 - Network device, configuration exchange method, maintenance exchange method, configuration exchange program, and maintenance exchange program - Google Patents

Description

  The present invention relates to a network device, a configuration exchange method, a maintenance exchange method, a configuration exchange program, and a maintenance exchange program.

  When a failure occurs in a device configuring a network system (hereinafter referred to as "network device"), maintenance and replacement of the failed network device with a normal network device is performed, and the same network environment as before the maintenance replacement is promptly processed. Recovery is necessary. The network device includes, for example, a router, a switch, and the like. In particular, in the case of maintenance exchange in a large scale network system such as a telecommunications carrier or a bank, prompt and accurate exchange work is required. In other words, at the time of maintenance and replacement of the network device, it is necessary to reduce the number of man-hours for workers and to avoid the risk of misconfiguration of the configuration.

  Here, "config" means the setting of the device. Also, “configuration information” means information on device settings, and includes “configuration file”. "Configuration file" means a device configuration file. And "config name" means the name of the configuration file. In other words, "config name" means the name of the device configuration file.

  In recent years, there has been known a method in which software-defined networking (SDN) can be introduced to centrally manage the configuration of network devices. Here, "SDN" means performing software configuration management, setting, and control of the network system without changing the existing network equipment.

  However, in this method, since it is necessary to introduce the controller server and the client device necessary for the SDN, not only the cost is increased, but also a large amount of work is required to reconstruct the network.

  Prior art documents related to the present invention are known.

  Patent Document 1 discloses a "fault detection apparatus" which can identify a fault location even when a silent fault occurs in a network. In Patent Document 1, a network monitoring system includes a failure detection device and a network configured of a plurality of switch devices. Adjacent switch devices mutually transmit and receive LLDP (Link Layer Discovery Protocol) packets. Here, the “LLDP packet” is a packet for notifying the adjacent node of the name of the switch device, setting information, and the like. Also, LLDP is a layer 2 protocol for exchanging device identification information, setting information, and the like, and is defined by the standard IEEE (The Institute of Electronic and Electronics Engineers) 802.1 AB.

  Note that LLDP is a protocol for acquiring information on nearby devices. In this LLDP, there is a method of transmitting / receiving information on the network as a LLDP frame between a network connection device connected to a LAN (Local Area Network) and a neighboring device on the same LAN, and storing the information in the own device. (See, for example, Patent Document 2).

  In Patent Document 1 described above, the reading unit of the failure detection apparatus reads out Management Information Base (MIB) information for each adjacent switch device from each of the switch devices configuring the network. “MIB information” indicates information such as the cumulative reception packet number (reception data amount), the cumulative transmission packet number (transmission data amount), and the link status. The MIB information storage unit of the failure detection apparatus stores the MIB information read by the reading unit.

  In Patent Document 1, a switch device holds information of an adjacent switch device by transmitting and receiving LLDP packets, and a failure detection device reads information of the adjacent switch device as MIB information. Thus, the failure detection device does not need to manage the network configuration in advance, and identifies the failure point by storing at least the name of the switch device that configures the network and the IP (Internet Protocol) address. Can. Also, the failure detection apparatus identifies a failure point based on the difference in MIB information obtained by polling twice. Therefore, it is not necessary to perform accurate synchronization processing for each of the switch devices, and it is possible to easily perform processing for identifying a failure point.

  Further, Patent Document 3 discloses a program, a computer, a communication device, and a communication control system capable of avoiding communication disconnection of a virtual machine after completion of migration. In Patent Document 3, the physical switch stores configuration information of a virtual machine operating on an information processing apparatus accommodated by the own apparatus. When the physical switch receives, from the physical server, information indicating that the state of the virtual machine has changed, the physical switch updates the configuration information based on the received information. Patent Document 3 describes that the LLPD frame is composed of a Destination MAC Address, a Source MAC Address, an EtherType, and an LLD PDU.

JP 2011-211350 A JP 2008-227987 A JP, 2011-198299, A

The above-described known maintenance replacement / restoration method has the following problems.
Problem 1: A maintenance worker must manage configuration information in order to maintain all network devices, and it takes time to prepare configuration information at the time of maintenance replacement.
Problem 2: The maintenance worker needs to manually input the prepared configuration information to the network device for which maintenance has been exchanged, from the console PC (personal computer) of the maintenance worker.
Problem 3: When a maintenance worker inputs configuration information into a network device, there is a risk that a wrong configuration file is input and a network failure occurs. In addition, extra work is required to recover from the network failure.
Problem 4: In order to use Software Defined Network (SDN) for automatically changing the configuration information of a network device, a controller server for managing the SDN and a client device corresponding to the SDN are required, and for network reconfiguration There will be a cost.

  Further, Patent Document 1 merely discloses a failure detection device capable of identifying a failure point, and does not disclose or suggest any maintenance replacement / restoration method. Moreover, Patent Document 1 only describes normal LLDP in which the switch device name and setting information are exchanged between adjacent devices (in this example, switch devices). The “setting information” is defined in a general LLDP standard specification such as the type of device or interface information (type / port number).

  Patent Document 2 merely discloses a network connection device that makes it possible to obtain correct neighbor device information using an LLDP frame, and does not disclose or suggest any maintenance / replacement method. Not. The information on the proximity device in Patent Document 2 specifically refers to a chassis ID and a port ID.

  Further, in Patent Document 3, the physical switch merely stores or updates configuration information of a virtual machine and discloses an LLDP frame. In Patent Document 3, an LLDP frame is used to transmit information including the content of the change of the state of the virtual machine to the physical switch.

  An object of the present invention is to provide a network device, a configuration exchange method, a maintenance exchange method, a configuration exchange program, and a maintenance exchange program, which solve the problems described above.

  The configuration exchange method of the present invention includes the steps of acquiring an adjacent configuration file from an adjacent network device, and storing the acquired adjacent configuration file in the memory of the own network device.

  The configuration exchange method of the present invention includes the steps of storing the own configuration file of the own network device in a memory, and transmitting the stored own configuration file to the adjacent network device.

  In the maintenance and replacement method of the present invention, the step of acquiring the configuration file for the own network device from the adjacent network device when the maintenance exchange is performed, and the acquired configuration file in the memory of the own network device as the own configuration file And a step of storing.

  The configuration exchange program of the present invention causes a computer, which is a network device, to realize a function of acquiring an adjacent configuration file from an adjacent network device and a function of storing the acquired adjacent configuration file in the memory of the own network device. Is a program for

  Further, the configuration exchange program of the present invention has a function of storing the own configuration file of the own network device in the memory and a function of transmitting the saved own configuration file to the adjacent network device to the computer which is the network device. It is a program to be realized.

  The maintenance and exchange program according to the present invention includes a function of acquiring a configuration file for the own network device from an adjacent network device when maintenance exchange is performed on a computer which is a network device, and the acquired configuration file of the self network device. It is a program that realizes a function of saving as a self configuration file in a memory.

  A network device according to the present invention comprises: a memory for storing an own configuration file of an own network device and an adjacent configuration file of an adjacent network device; a table for storing an adjacent configuration name of the adjacent configuration file; A transmission / reception unit that transmits / receives a configuration request frame, an LLDP frame storing a configuration name, a configuration information frame storing a configuration file to / from a network device, an LLDP frame processing unit generating and expanding the LLDP frame, And a data processing unit configured to process the configuration request frame, the LLDP frame, and the configuration information frame, which are transmitted and received by the transmission / reception unit.

  According to the present invention, it is possible to apply an appropriate configuration file to a network device that has been subjected to maintenance exchange.

FIG. 1 is a configuration diagram showing a network system to which a maintenance exchange / recovery method (configuration exchange method) according to an embodiment of the present invention is applied. FIG. 7 is a flow chart for explaining the operation of a configuration exchange method implemented by the first network device (device A) in the network system shown in FIG. 1. FIG. 3 is a flowchart describing the operation in step S110 in FIG. 2 in further detail. In the network system shown in FIG. 1, a third network device (device C) which is an adjacent network device is maintenance-exchanged with a fourth network device (device D) which is another network device. It is a flow chart explaining operation of a configuration exchange method in one network device (device A). FIG. 5 is a flowchart describing the operation in step S140 in FIG. 4 in further detail. It is a flowchart explaining the operation | movement of the configuration exchange method implemented by a 2nd network apparatus (apparatus B) in the network system shown by FIG. FIG. 7 is a flowchart describing the operation in step S220 in FIG. 6 in further detail. FIG. 10 is a flow chart for explaining the operation of the maintenance exchange method implemented in the fourth network device (device D) which is another network device in the network system shown in FIG. 1; FIG. 9 is a flowchart describing the operation in step S410 in FIG. 8 in further detail. FIG. 1 is a configuration diagram showing a network system to which a maintenance exchange / recovery method (configuration exchange method) according to an embodiment of the present invention is applied. FIG. 11 is a configuration diagram for describing operations at the time of configuration change and at the time of maintenance and replacement of the network device using the same configuration as FIG. FIG. 1 is a block diagram showing a network system according to a first embodiment of the present invention. FIG. 13 is a diagram showing an example of creating a configuration name of a first network device 100 (device A) in the network system shown in FIG. 12; It is a figure which shows the format of the LLDP flame | frame used in the network system shown by FIG. FIG. 13 is a diagram showing a format of a configuration request frame used when requesting configuration from a neighboring network device in the network system shown in FIG. 12; FIG. 13 is a diagram showing a format of a configuration information frame used when transmitting a configuration file to an adjacent network device in the network system shown in FIG. 12; It is a figure which shows the 1st LLDP MIB table used by the 1st network apparatus of the network system shown by FIG. It is a flowchart explaining the operation | movement at the time of the configuration change of the network system based on the 1st Example of this invention shown by FIG. It is a flowchart explaining the operation | movement in the case of applying a configuration automatically at the time of maintenance replacement | exchange of the network system based on the 1st Example of this invention shown by FIG. It is a block diagram which shows the network system which concerns on the 2nd Example of this invention. It is a figure which shows the format of the MACsec encryption LLDP frame used in the network system shown by FIG. FIG. 21 is a diagram showing a format of a MACsec encryption configuration request frame which is used when requesting a configuration from an adjacent network device in the network system shown in FIG. 20. FIG. 21 is a diagram showing a format of a MACsec encryption configuration information frame used when transmitting a configuration file to an adjacent network device in the network system shown in FIG. 20. It is a block diagram which shows the network system which concerns on the 3rd Example of this invention.

[Features of the invention]
The present invention is an invention using a protocol that extends the function of Link Layer Discovery Protocol (LLDP) defined in the standard IEEE (The Institute of Electronic and Electronics Engineers) 802.1 AB. According to the present invention, configuration files of adjacent network devices are exchanged with each other by extending and using LLDP for exchanging information of adjacent network devices. Further, in the present invention, the configuration file of the adjacent network device exchanged and acquired is stored in the memory. According to the present invention, when maintenance or replacement of a network device is performed to a new network device at the time of failure or inspection, the configuration file suitable for the network device replaced and maintained is used by using the configuration file held by the adjacent network device. It becomes possible to apply.

  Therefore, in the present invention, the maintenance worker does not need to prepare the configuration information before the maintenance replacement of the problem 1 and input man-hours of the configuration information at the time of the maintenance replacement of the problem 2. Can be avoided. Further, in the present invention, unlike the SDN environment of Problem 4, there is no need to newly construct a controller server, so the construction cost can be suppressed.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

Summary of the Embodiments of the Invention
An overview of an embodiment of the present invention will be described with reference to FIG.

  FIG. 1 is a block diagram showing a network system to which a maintenance replacement / restoration method (a configuration replacement method) according to an embodiment of the present invention is applied. The illustrated network system includes a first network device 100, a second network device 200, and a third network device 300. In the illustrated example, the first network device 100 is indicated by “device A”, the second network device 200 is indicated by “device B”, and the third network device 300 is indicated by “device C”.

  In the network system shown in FIG. 1, an example of maintenance exchange of the third network device 300 to the fourth network device 400 is shown. The fourth network device 400 is indicated by “device D”.

  Each of the first to fourth network devices 100 to 400 (device A, device B, device C, device D) is a network device such as a router or a switch. In the network system shown in FIG. 1, the first network device 100 (device A) connects to the second network device 200 (device B) and the third network device 300 (device C) by an Ethernet (registered trademark) cable. Has a configuration that

  Port 1 of the first network device 100 (device A) is connected to port 1 of the second network device 200 (device B) via an Ethernet cable. The port 2 of the first network device 100 (device A) is connected to the third network device 300 (device C) via an Ethernet cable.

  Each of the first to fourth network devices 100 to 400 (device A, device B, device C, device D) has substantially the same configuration. That is, the first network device 100 (device A), as described later, uses a first table 130 for storing adjacent configuration names of adjacent configuration files, and a first table 130 for storing configuration files as described later. And a first processing unit 150 that processes data.

  Similarly, the second network device 200 (device B) includes a second table 230, a second memory 240, and a second processing unit 250. The third network device 300 (device C) includes a third table 230, a third memory 340, and a third processing unit 350. The fourth network device 400 (device D) includes a fourth table 430, a fourth memory 440, and a fourth processing unit 450.

  Each of the first to fourth network devices 100 to 400 (device A, device B, device C, device D) actually performs substantially the same operation. However, in the following description, in order to facilitate understanding of the present invention, the first to fourth network devices 100 to 400 (device A, device B, device C, device D) perform different operations. Explain as.

  First, a configuration exchange method implemented in the first network device 100 (device A) will be described. In this case, the second network device 200 (device B) is the adjacent network device. The third network device 300 (device C) is also an adjacent network device, but its operation is omitted for the sake of simplicity. Therefore, in this case, the first network device 100 (device A) is the own network device.

  FIG. 2 is a flowchart for explaining the operation of the configuration exchange method implemented by the first network device 100 (device A).

  The first processing unit 150 of the first network device 100 (device A) acquires the adjacent configuration file from the second network device 200 (device B) which is the adjacent network device (step S110). That is, the first processing unit 150 works as a file acquisition unit that acquires the adjacent configuration file from the adjacent network device 200.

  Subsequently, the first processing unit 150 of the first network device 100 (device A) stores the acquired adjacent configuration file in the first memory 140 of the own network device 100 (device A) (step S120). . That is, the first processing unit 150 works as a file storage unit that stores the acquired adjacent configuration file in the memory 140 of the own network device 100.

  As described above, since the first network device 100 (device A) stores the adjacent configuration file of the adjacent network device obtained by exchange, when the adjacent network device is maintenance-replaced by another network device. , It becomes possible to use the adjacent configuration file.

  Next, with reference to FIG. 3, the operation in step S110 will be described in more detail.

  The first processing unit 150 of the first network device 100 (device A) stores the adjacent configuration name of the adjacent configuration file in the first table 130 of the own network device 100 (device A) (step S111). ). That is, the first processing unit 150 works as a configuration name storage unit that stores the adjacent configuration name of the adjacent configuration file in the table 130 of the own network device 100.

  In this state, the first processing unit 150 of the first network device 100 (device A) uses the adjacent configuration name from the LLDP frame transmitted from the second network device 200 (device B) which is the adjacent network device. It extracts (Step S112). That is, the first processing unit 150 works as a configuration name extraction unit that extracts the adjacent configuration name from the LLDP frame transmitted from the adjacent network device.

  Then, the first processing unit 150 of the first network device 100 (device A) compares the extracted adjacent configuration name with the adjacent configuration name stored in the first table 130 (step S113). That is, the first processing unit 150 works as a configuration name comparing unit that compares the extracted adjacent configuration name with the stored adjacent configuration name.

  When there is a difference in the comparison result (“mismatch” in step S113), the first processing unit 150 of the first network device 100 (device A) is the second network device 200 (device B) that is an adjacent network device. The configuration request frame is sent out (step S114). That is, the first processing unit 150 acts as a request sending means for sending the configuration request frame to the adjacent network device 200 when there is a difference in the comparison result.

  As described later, the second processing unit 250 of the second network device 200 (device B) which has received the configuration request frame receives the configuration information frame stored in the second memory 240 as the configuration information frame. , And transmits the configuration information frame to the first network device 100 (device A). Here, it should be noted that the own configuration file of the second network device 200 (device B) is an adjacent configuration file for the first network device 100 (device A).

  The first processing unit 150 of the first network device 100 (device A) receives the configuration information frame transmitted from the second network device 200 (device B) which is the adjacent network device (step S115). That is, the first processing unit 150 works as configuration information receiving means for receiving the configuration information frame transmitted from the adjacent network device 200.

  Then, the first processing unit 150 of the first network device 100 (device A) extracts the adjacent configuration file from the received configuration information frame (step S116). That is, the first processing unit 150 works as a file extraction unit that extracts an adjacent configuration file from the received configuration information frame.

  In this manner, the first network device 100 (device A) can acquire the adjacent configuration file of the second network device 200 (device B).

  If the extracted adjacent configuration name matches the stored adjacent configuration name in step S113, the first memory 140 already has the adjacent configuration file of the second network device 200 (device B). It is saved. Therefore, in this case, the first processing unit 150 of the first network device 100 (device A) ends the process without doing anything.

  Next, referring to FIG. 4, in the case where the third network device 300 (device C) which is the adjacent network device is maintenance-replaced by the fourth network device 400 (device D) which is another network device. The operation of the configuration exchange method in the first network device 100 (device A) will be described.

  Steps S110 and S120 in FIG. 4 are the same as steps S110 and S120 in FIG. 2, and thus the description thereof will be omitted.

  As shown in FIG. 1, it is assumed that the third network device 300 (device C) which is an adjacent network device is maintenance-replaced by the fourth network device 400 (device D) which is another network device (step S130). Yes).

  In this situation, the first memory 140 of the first network device 100 (device A) operates in the same manner as described above to form the third network device 300 (device C), which is an adjacent network device. Adjacent configuration files are also saved.

  The first processing unit 150 of the first network device 100 (device A) stores the adjacent configuration file of the third network device 300 (device C) stored in the first memory 140 into another network device. To the fourth network device 400 (device D) (step S140). That is, the first processing unit 150 is a file transmission unit that transmits the adjacent configuration file stored in the memory 140 to another network device 400 when the adjacent network device 300 is maintenance-replaced by another network device 400. Act as.

  As described above, when the first network device 100 (device A) is replaced and maintained, it is possible to transmit the stored adjacent configuration file to another network device 400 that has been replaced and maintained.

  Next, with reference to FIG. 5, the operation in step S140 will be described in more detail.

  As described later, the fourth network device 400 (device D) subjected to maintenance exchange transmits an LLDP frame storing a default configuration name to the first network device 100 (device A). Here, "default configuration name" means the name of a configuration file (default configuration file) set as default.

  Therefore, the first processing unit 150 of the first network device 100 (device A) receives an LLDP frame storing a default configuration name from the fourth network device 400 (device D) which is another network device. (Step S141). That is, the first processing unit 150 works as a configuration name receiving unit that receives an LLDP frame storing a default configuration name from another network device 400.

  Then, the first processing unit 150 of the first network device 100 (device A) refers to the default configuration name stored in the received LLDP frame, and stores the third configuration stored in the first memory 140. The adjacent configuration file of the network device 300 (device C) is stored in the configuration information frame. Then, the first processing unit 150 transmits the configuration information frame to the fourth network device 400 (device D) which is another network device (step S142). That is, the first processing unit 150 refers to the default configuration name stored in the received LLDP frame, stores the adjacent configuration file stored in the memory 140 in the configuration information frame, and stores the configuration information frame. It acts as configuration information transmission means for transmitting to another network device 400.

  Thus, the adjacent configuration file of the third network device 300 (device C) is transmitted to the fourth network device 400 (device D).

  The first processing unit 150 may be realized using a combination of hardware and software. In the combination of hardware and software, the configuration exchange program is expanded in RAM (random access memory), and hardware such as a control unit (CPU (central processing unit)) is operated based on the program. Realize as various means. Further, the configuration exchange program may be recorded on a recording medium and distributed. The configuration exchange program recorded in the recording medium is read into the memory via the wired, wireless, or recording medium itself, and operates the control unit and the like. Incidentally, examples of the recording medium include an optical disc, a magnetic disc, a semiconductor memory, a hard disc and the like.

  If the above embodiment is described in another expression, the computer to be operated as the first processing unit 150 is based on the configuration exchange program developed in the RAM, file acquisition means, file storage means, configuration name storage means, configuration This can be realized by operating as a name extraction unit, a configuration name transmission unit, a request transmission unit, a configuration information reception unit, a file extraction unit, a file transmission unit, a configuration name reception unit, and a configuration information transmission unit.

  Next, a configuration exchange method implemented in the second network device 200 (device B) will be described. In this case, the first network device 100 (device A) is the adjacent network device. Therefore, in this case, the second network device 200 (device B) is the own network device.

  FIG. 6 is a flowchart for explaining the operation of the configuration exchange method implemented by the second network device 200 (device B).

  The second processing unit 250 of the second network device 200 (device B) stores the own configuration file of the own network device 200 in the second memory 240 (step S210). That is, the second processing unit 250 works as a file storage unit for storing the own configuration file of the own network device 200 in the memory 240.

  The second processing unit 250 of the second network device 200 (device B) transmits the own configuration file stored in the second memory 240 to the first network device 100 (device A) which is an adjacent network device. (Step S220). That is, the second processing unit 250 works as a file transmission unit that transmits the stored own configuration file to the adjacent network device 100.

  Thus, the second network device 200 (device B) can transmit its own configuration file to the adjacent network device. Therefore, when the second network device 200 (device B) is maintenance-replaced by another network device, it becomes possible to use the own configuration file acquired from the adjacent network device for another network device.

  Next, with reference to FIG. 7, the operation in step S220 will be described in more detail.

  As described above, the second processing unit 250 of the second network device 200 (device B) receives the configuration request frame from the first network device 100 (device A) which is the adjacent network device (step S221). . The second processing unit 250 functions as a request receiving unit that receives the configuration request frame from the adjacent network device 100.

  Subsequently, in response to the received configuration request frame, the second processing unit 250 of the second network device 200 (device B) uses its own configuration file stored in the second memory 240 as a configuration information frame. Store. Then, the second processing unit 250 transmits the configuration information frame to the first network device 100 (device A) which is the adjacent network device (step S222). That is, in response to the received configuration request frame, the second processing unit 250 stores the own configuration file stored in the memory 240 in the configuration information frame, and transmits the configuration information frame to the adjacent network device 100. Works as a means of transmitting configuration information.

  Thus, the own configuration file of the second network device 200 (device B) is transmitted to the first network device 100 (device A) which is the adjacent network device.

  The second processing unit 250 may be realized using a combination of hardware and software. In the combination of hardware and software, the configuration exchange program is expanded in RAM (random access memory), and hardware such as a control unit (CPU (central processing unit)) is operated based on the program. Realize as various means. Further, the configuration exchange program may be recorded on a recording medium and distributed. The configuration exchange program recorded in the recording medium is read into the memory via the wired, wireless, or recording medium itself, and operates the control unit and the like. Incidentally, examples of the recording medium include an optical disc, a magnetic disc, a semiconductor memory, a hard disc and the like.

  If the above embodiment is described in another expression, the computer operated as the second processing unit 250 is based on the configuration exchange program expanded in the RAM, and the file storage unit, the file transmission unit, the request reception unit, and the configuration. It can be realized by operating as information transmission means.

  Next, a maintenance and replacement method implemented by the fourth network device 400 (device D) that has been maintenance-replaced will be described. In this case, the first network device 100 (device A) is the adjacent network device. Then, the fourth network device 400 (device D) becomes the own network device.

  FIG. 8 is a flowchart for explaining the operation of the maintenance and replacement method implemented by the fourth network device 400 (device D) which is another network device.

  When maintenance and replacement are performed as shown in FIG. 1, the fourth processing unit 450 of the fourth network device 400 (device D) starts its own operation from the first network device 100 (device A) which is an adjacent network device. The configuration file for the network device 400 is acquired (step S410). That is, the fourth processing unit 450 functions as a file acquisition unit that acquires the configuration file for the own network device from the adjacent network device 100 when maintenance and replacement are performed.

  Subsequently, the fourth processing unit 450 of the fourth network device 400 (device D) saves the acquired configuration file as the own configuration file in the fourth memory 440 of the own network device 400 (step S420). ). That is, the fourth processing unit 450 works as a file storage unit that stores the acquired configuration file in the memory 440 of the own network device 400 as the own configuration file.

  As described above, since the fourth network device 400 (device D) stores the configuration file acquired from the adjacent network device as its own configuration file, it is possible to apply an appropriate configuration file when performing maintenance and replacement. Become.

  Next, with reference to FIG. 9, the operation in step S410 will be described in more detail.

  As described above, the fourth processing unit 450 of the fourth network device 400 (device D) transfers the LLDP frame storing the default configuration name to the first network device 100 (device A), which is an adjacent network device. It transmits (step S411). That is, the fourth processing unit 450 works as a default configuration name transmission unit that transmits the LLDP frame storing the default configuration name to the adjacent network device 100.

  Subsequently, as described above, the fourth processing unit 450 of the fourth network device 400 (device D) receives the configuration file (third file) from the first network device 100 (device A) which is the adjacent network device. The configuration information frame storing the adjacent configuration file of the network device 300 (device B) is received (step S412). That is, the fourth processing unit 450 works as a configuration information receiving unit that receives the configuration information frame storing the configuration file from the adjacent network device 100.

  Then, the fourth processing unit 450 of the fourth network device 400 (device D) extracts the configuration file from the received configuration information frame (step S413). That is, the fourth processing unit 450 works as a file extraction unit that extracts the configuration file from the received configuration information frame.

  In this way, the fourth network device 400 (device D) that has been maintenance-exchanged can obtain the configuration file for its own network device 400 from the first network device 100 (device A) that is the adjacent network device. It becomes possible.

  The fourth processing unit 450 may be realized using a combination of hardware and software. In the combination form of hardware and software, a maintenance exchange program is developed in RAM (random access memory), and hardware such as a control unit (CPU (central processing unit)) is operated based on the program. Realize as various means. Also, the maintenance and replacement program may be recorded on a recording medium and distributed. The maintenance and exchange program recorded in the recording medium is read into the memory via a wired, wireless, or recording medium itself to operate the control unit and the like. Incidentally, examples of the recording medium include an optical disc, a magnetic disc, a semiconductor memory, a hard disc and the like.

  If the above embodiment is described in another expression, the computer for operating as the fourth processing unit 450 may be a file acquisition unit, a file storage unit, a default configuration name transmission unit, based on the maintenance and exchange program expanded in the RAM. It can be realized by operating as configuration information receiving means and file extracting means.

Embodiment
Embodiments of the present invention will be described in detail with reference to FIGS. 10 and 11. FIG.

  FIG. 10 is a block diagram showing a network system to which a maintenance replacement / restoration method (configuration replacement method) according to an embodiment of the present invention is applied. The illustrated network system includes a first network device 100, a second network device 200, and a third network device 300. In the illustrated example, the first network device 100 is indicated by “device A”, the second network device 200 is indicated by “device B”, and the third network device 300 is indicated by “device C”.

  As described above, each of the first to third network devices 100 to 300 (device A, device B, device C) is a network device such as a router or a switch. The network system shown in FIG. 10 has a configuration in which the first network device 100 (device A) is connected to the second network device 200 (device B) and the third network device 300 (device C) by an Ethernet cable. doing.

  In the illustrated example, port 1 of the first network device 100 (device A) is connected to port 1 of the second network device 200 (device B) via an Ethernet cable. Port 2 of the first network device 100 (device A) is connected to port 1 of the third network device 300 (device C) via an Ethernet cable.

  The first to third network devices 100 to 300 (device A, device B, device C) each hold a unique chassis ID (identifier). The chassis ID can be changed by the configuration information. In the present embodiment, the chassis ID of the first network device 100 (device A) is “Site-A”, and the chassis ID of the second network device 200 (device B) is “Site-B”. The chassis ID of the network device 300 (device C) is “Site-C”.

  The first network device 100 (device A) includes a first LLDP MIB table 130 as a first table and a first memory 140. Although not shown, the first network device 100 (device A) also includes a first processing unit such as the first processing unit 150 in FIG.

  Similarly, the second network device 200 (device B) includes a second LLDP MIB table 230 as a second table, a second memory 240, and a second processing unit (not shown). .

  The third network device 300 (device C) includes a third LLDP MIB table 330 as a third table, a third memory 340, and a third processing unit (not shown).

  The first to third memories 140, 240, and 340 operate as first to third configuration storage units, respectively. Each of the first to third memories 140, 240, and 340 has its own device configuration region and an adjacent device configuration region.

  The own configuration file of each of the network devices 100-300 is stored in the own device configuration area of the first to third memories 140, 240, and 340 provided in the own network devices 100-300. Here, the configuration file is specified by the configuration name. In other words, the configuration file is linked to the corresponding configuration name. Here, as described above, “config name” means the configuration file name (config file name) of the device. In the present embodiment, each of the network devices 100 to 300 generates a configuration name from the chassis ID and the storage date and time.

  For example, the configuration name "Site-A-2015120115151729" of the first network device 100 (device A) is the chassis ID "Site-A" of the first network device 100 (device A), and the configuration save date "2015". It is decided by the combination with "15:17:29" on December 01. The own configuration file of the first network device 100 (device A) is stored in the own device configuration area of the first memory (first configuration storage unit) 140.

  Each of the network devices 100 to 300 supports LLDP, and exchanges LLDP information between adjacent network devices. Specifically, the first network device 100 (device A) transmits the first LLDP frame 11 to the second network device 200 (device B), and the second LLDP frame 14 is transmitted to the third network device. Send to 300 (apparatus C). The second network device 200 (device B) transmits the third LLDP frame 17 to the first network device 100 (device A). The third network device 300 (device C) transmits the fourth LLDP frame 20 to the first network device 100 (device A).

  In the LLDP frames 11, 14, 17, and 20 transmitted by each of the network devices 100 to 300, the chassis ID of the transmission source and the own device configuration area of the first to third memories 140, 240, and 340 are stored. It contains information including the own configuration name specifying the own configuration file. For example, the first LLDP frame 11 and the second LLDP frame 14 include the first chassis ID of the first network device (device A) and the first configuration name “Site-A-2015120115151729”. Information is included.

  The processing unit of each of the network devices 100-300 acquires (extracts) information including the chassis ID and the configuration name of the adjacent network device from the LLDP frame of the adjacent network device, and stores the information in the LLDP MIB tables 130, 230, 330 Do. For example, in the first LLDP MIB table 130, the first processing unit of the first network device 100 (device A) may use the third LLDP frame 17 and the third LLDP frame 17 of the second network device 200 (device B). The chassis ID and the configuration name acquired from the fourth LLDP frame 20 of the network device 300 (device C) are stored.

  Further, connection port numbers connected to the respective network devices 100 to 300 and valid periods of LLDP information are recorded in the LLDP MIB tables 130, 230, and 330. The lifetime of LLDP information is reset each time an LLDP frame is received. In the present embodiment, the effective period is set to 10 hours.

  The processing unit of each of the network devices 100 to 300 compares the adjacent configuration name acquired (extracted) from the LLDP frame of the adjacent network device with the adjacent configuration name stored in the LLDP MIB table. If there is a difference in the comparison result, the processing unit of each of the network devices 100 to 300 transmits a configuration request frame to the adjacent network device that is the transmission source of the LLDP frame.

  The processing unit of the adjacent network device that has received the configuration request frame stores, in the configuration information frame, the own configuration file stored in the configuration region for own device of the memory, and transmits the configuration information frame.

  For example, after receiving the third LLDP frame 17 of the second network device (device B), the first processing unit of the first network device 100 (device A) stores the third LLDP frame 17 in the third LLDP frame 17 The adjacent configuration name of the second network device 200 (device B) and the second network device 200 (device B) stored in the first LLDP MIB table 130 of the first network device (device A). Compare with adjacent config name. If there is a difference in the comparison result, the first processing unit of the first network device 100 (device A) transmits the first configuration request frame 10 to the second network device 200 (device B). Do. The second processing unit of the second network device 200 (device B) that has received the first configuration request frame 10 receives the configuration region for its own device of the second memory 240 of the second network device 200 (device B). Is stored in the third configuration information frame, and the third configuration information frame 18 is transmitted.

  The processing unit of the network device that has received the configuration information frame from the adjacent network device acquires the adjacent configuration file of the adjacent network device from the configuration information frame, and stores the adjacent configuration file in the memory for the adjacent device configuration area.

  For example, the first processing unit of the first network device 100 (device A) receives the third configuration information frame 18 from the second network device 200 (device B), and this third configuration information frame 18 The adjacent configuration file of the second network device 200 (device B) acquired by expanding the file is stored in the adjacent device configuration area of the first memory 140.

  FIG. 11 is a block diagram for explaining the operation at the time of configuration change and at the time of maintenance replacement of the network device, using the same configuration as that of FIG.

  First, the operation at the time of configuration change will be described using the connection between the first network device 100 (device A) and the second network device 200 (device B). Here, the first network device 100 (device A) and the second network device 200 (device B) have their adjacent configuration files in the adjacent device configuration area of the first and second memories 140 and 240. It assumes that it holds.

  When the configuration change of the second network device 200 (device B) is performed, the configuration name of the own configuration file is changed, and the own configuration file stored in the own device configuration area of the second memory 240 is updated. . The second network device 200 (device B) transmits an LLDP frame 31 storing the changed configuration name to the first network device 100 (device A) which is an adjacent network device.

  The first processing unit of the first network device 100 (device A) acquires the adjacent configuration name of the second network device 200 (device B) acquired (extracted) from the LLDP frame 31, and the first LLDP MIB table 130. And the adjacent configuration name of the second network device 200 (device B) stored in FIG. If there is a difference in the comparison result, the first processing unit of the first network device 100 (device A) sets the adjacent configuration name of the second network device 200 (device B) in the first LLDP MIB table 130 Update and reset the validity period. In the present embodiment, the effective period is set to 10 hours.

  The first processing unit of the first network device 100 (device A) deletes the adjacent configuration file of the second network device 200 (device B) stored in the adjacent device configuration area of the first memory 140. Then, the first processing unit of the first network device 100 (device A) sends the second network device 200 (device B) the adjacent configuration name after the change of the second network device 200 (device B). The stored configuration request frame 32 is transmitted.

  The second processing unit of the second network device 200 (device B) receives the configuration request frame 32, and acquires (extracts) the adjacent configuration name stored in the configuration request frame 32. The second processing unit of the second network device 200 (device B) acquires the configuration file of the acquired (extracted) adjacent configuration name from the configuration region for own device of the second memory 240, and uses the configuration information frame 33. It stores and transmits to the first network device 100 (device A).

  The first processing unit of the first network device 100 (device A) acquires the adjacent configuration file of the second network device 200 (device B) acquired (extracted) from the received configuration information frame 33 as the first network. It is stored in the adjacent device configuration area of the first memory 140 of the device 100 (device A).

  Next, the operation at the time of maintenance and replacement of the network device will be described using the connection between the first network device 100 (device A) and the first network device 400 (device D).

  The third network device 300 (device C) connected to port 2 of the first network device 100 (device A) is removed from the network configuration for maintenance replacement. At this time, the first processing unit of the first network device 100 (device A) determines that the connection of the port 2 is disconnected, and sets the effective period of the connection port 2 of the first LLDP MIB table 130 to null. .

  The fourth network device 400 (device D) in the factory shipment state is newly connected to the port 2 of the first network device 100 (device A). The factory-shipped fourth network device 400 (device D) stores the default configuration file in its own device configuration area of the fourth memory 440. Here, the "default configuration file" means, as described above, a configuration file set as a default.

  Here, the default configuration information includes a setting for enabling LLDP and a setting for storing a default configuration subtype that indicates that the LLDP frame 34 stores a default configuration name. Here, "default config name" means the name of the default config file, as described above. The “default configuration subtype” is information indicating that the information stored in the LLDP frame is a default configuration name.

  The factory-shipped fourth network device 400 (device D) is activated with the default configuration. The fourth network device 400 (device D 1) that has not exchanged the LLDP frame with the adjacent network device has no adjacent configuration file stored in the adjacent device configuration area of the fourth memory 440, and the fourth LLDP The information of LLDP is not stored in the MIB table 430 either.

  The fourth processing unit of the fourth network device 400 (device D) is an adjacent network device that stores an LLDP frame 34 storing a default configuration name and a default configuration sub-type which is known to store the default configuration name. It transmits to a certain first network device 100 (device A).

  When the first processing unit of the first network device 100 (device A) receives an LLDP frame that does not store the chassis configuration ID and default config subtype not assigned to the connection port of the first LLDP MIB table 130 , Discard the LLDP frame.

  The first processing unit of the first network device 100 (device A) receives the LLDP frame 34 at port 2 and determines that the connection of port 2 has been restored. In addition, the first processing unit of the first network device 100 (device A) resets the validity period of the connection port 2 of the first LLDP MIB table 140. In the present embodiment, the effective period is set to 10 hours.

  The first processing unit of the first network device 100 (device A) determines from the default configuration subtype stored in the LLDP frame 34 that the configuration name acquired from the LLDP frame 34 is the default configuration name. The first processing unit of the first network device 100 (device A) refers to the adjacent configuration name of the connection port 2 of the first LLDP MIB table 130. Then, the first processing unit of the first network device 100 (device A) stores in the configuration information frame 35 the adjacent configuration file of the adjacent configuration name referred from the adjacent device configuration area of the first memory 140. , The fourth network device 400 (device D). Here, the first processing unit of the first network device 100 (device A) stores, in the configuration information frame 35, the Ethertype for the configuration for the adjacent device so that it can be determined as the adjacent configuration file.

  The fourth processing unit of the fourth network device 400 (device D) refers to the Ethertype of the received configuration information frame 35, and uses the adjacent configuration file stored in the configuration information frame 35 as the configuration file for the adjacent network device. I judge that there is. In addition, the fourth processing unit of the fourth network device 400 (device D) stores the adjacent configuration file acquired (extracted) from the configuration information frame 35 in its own device configuration area of the fourth memory 440 in its own configuration file. Save as. The fourth processing unit of the fourth network device 400 (device D) stores the own configuration file in the own device configuration area of the fourth memory 440 and automatically restarts the fourth network device 400. Apply the own network device configuration file to (Device D). The fourth processing unit of the fourth network device 400 (device D) updates the chassis ID of the fourth network device 400 (device D) by applying its own configuration file.

  The first processing unit of the first network device 100 (device A) stores the chassis ID and the self-configuration name of the first network device 100 (device A) in the fourth network device 400 (device D). Send an LLDP frame 36.

  The fourth processing unit of the fourth network device 400 (device D) receives the LLDP frame 36, and acquires the chassis ID and the adjacent configuration name of the first network device 100 (device A) from the LLDP frame 36. The fourth processing unit of the fourth network device 400 (device D) uses the fourth LLDP MIB table 430 to acquire the acquired information (adjacent configuration name) of the first network device 100 (device A) and the connection port number. Save

  The fourth processing unit of the fourth network device 400 (device D) stores the configuration request frame 37 storing the adjacent configuration name of the first network device 100 (device A) acquired from the LLDP frame 36 as the first configuration request frame. It transmits to the network apparatus 100 (apparatus A).

  The first processing unit of the first network device 100 (device A) receives the configuration request frame 37. Then, the first processing unit of the first network device 100 (device A) stores the own configuration file of the first network device 100 (device A) stored in the own device configuration area of the first memory 140. Are stored in the configuration information frame 38 and transmitted to the fourth network device 400 (device D).

  The fourth processing unit of the fourth network device 400 (device D) receives the configuration information frame 38, and acquires (extracts) the adjacent configuration file of the first network device 100 (device A) from the configuration information frame 38. Do. The fourth processing unit of the fourth network device 400 (device D) places the acquired adjacent configuration file of the first network device 100 (device A) in the configuration region for the adjacent device of the fourth memory 440 (extraction). save.

  The following effects are achieved in the present embodiment.

  The first effect is that it is possible to reduce the number of steps involved in preparation of configuration information before maintenance replacement of a maintenance worker and input of configuration information at the time of maintenance replacement. The reason is that, in the network system according to the present embodiment, the process of automatically acquiring the configuration file from the adjacent network device at the time of maintenance and replacement works, so that man-hours for preparation of configuration information and input of configuration information by maintenance workers can be reduced. is there.

  The second effect is that it is possible to avoid the risk that a worker at the time of maintenance replacement inputs an incorrect configuration file to the network device. The reason is that since the adjacent configuration file of the adjacent network device before maintenance replacement is stored in the memory of the network device according to the present embodiment, at the time of maintenance replacement, an appropriate configuration file before maintenance replacement is received from the adjacent network device. It is because it can be acquired.

Next, a first embodiment of the present invention will be described with reference to the drawings.

FIG. 12 is a block diagram showing a network system according to the first embodiment of the present invention. In the first embodiment, the second network device 200 (device B) is connected to the port 1 of the first network device 100 (device A) with an Ethernet cable, and the port of the first network device 100 (device A) It is the Example which connected the 4th network apparatus 400 (apparatus D) which is maintenance exchange of a factory shipment state to 2 by Ethernet cable.

  The configuration of a network system according to the first embodiment of the present invention will be described with reference to FIG.

Each network apparatus constituting the network system according to the first embodiment of the present invention includes a data processing unit that processes a frame transmitted and received from a port, an LLDP frame processing unit that generates and develops an LLDP frame, and LLDP acquired from an LLDP frame. It comprises an LLDP MIB table for storing information, and a memory (config storage unit) for storing an own configuration file and an adjacent configuration file.

Specifically, the first network device 100 (device A) includes a first data processing unit 110, a first LLDP frame processing unit 120, a first LLDP MIB table 130, and a first memory (first Configuration storage unit 140). The combination of the first data processing unit 110 and the first LLDP frame processing unit 120 serves as the first processing unit 150 (see FIG. 1).

  Each of port 1 and port 2 of the first network device 100 (device A) is an LLDP that stores a configuration request frame to be described later and a configuration name to be described later between the adjacent network devices 200 and 300 and the own network device 100. It functions as a transmitting / receiving unit that transmits / receives a frame and configuration information storing a configuration file to be described later.

  Similarly, the second network device 200 (device B) also includes a second data processing unit 210, a second LLDP frame processing unit 220, a second LLDP MIB table 230, and a second memory (second A configuration storage unit) 240 is provided. The combination of the second data processing unit 210 and the second LLDP frame processing unit 220 serves as the second processing unit 250 (see FIG. 1).

  The port 1 of the second network device 200 (device B), between the adjacent network device 100 and the self network device 200, includes a configuration request frame, an LLDP frame storing a configuration name, and configuration information storing a configuration file, and Act as a transceiver to send and receive

  The fourth network device (device D) also includes a fourth data processing unit 410, a fourth LLDP frame processing unit 420, a fourth LLDP MIB table 430, and a fourth memory (fourth configuration storage unit) 440. Equipped with The combination of the fourth data processing unit 410 and the fourth LLDP frame processing unit 420 serves as the fourth processing unit 450 (see FIG. 1).

  The port 1 of the fourth network device 400 (device D), between the adjacent network device 100 and the own network device 400, includes a configuration request frame, an LLDP frame storing a configuration name, and configuration information storing a configuration file, and Act as a transceiver to send and receive

  The first LLDP frame processor 120 of the first network device 100 (device A) and the second LLDP frame processor 220 of the second network device 200 (device B) generate LLDP frames 54 and periodically Send to adjacent network devices. When the configuration file of the network device is changed, each network device notifies the adjacent network device of the new configuration name by the LLDP frame 54. The adjacent network device that has received the LLDP frame 54 storing the new configuration name transmits a configuration request frame 55 to the network device that has transmitted the LLDP frame 54, and requests an adjacent configuration file.

  The network device 100 200 receiving the configuration request frame 55 stores the own configuration file stored in the configuration region for own device of the memories 140 240 in the configuration information frame 56, and the adjacent network transmits the configuration request frame 55. Send to device.

  The fourth network device 400 (device D) in the factory shipment state in which a specific configuration is not set stores the default configuration file in its own device configuration area 442 of the fourth memory 440. The default configuration information includes a setting for enabling LLDP and a setting for adding a default configuration subtype to the LLDP frame 57. The fourth network device 400 (device D 1) transmits an LLDP frame 57 storing the default configuration name to the first network device 100 (device A) which is the adjacent network device.

The first network device 100 (device A) having received the LLDP frame 57 storing the default configuration name refers to the configuration name assigned to the port that has received the LLDP frame in the first LLDP MIB table 130. Further, the first network device 100 (device A) extracts the adjacent configuration file of the configuration name obtained by reference from the configuration region for the adjacent device of the first memory 140, and the configuration information frame 58 for the adjacent network device. Is sent to the fourth network device 400 (device D).

  The fourth network device 400 (device C) that has received the configuration information frame 58 for the adjacent network device uses the adjacent configuration file acquired from the configuration information frame 58 for the adjacent network device for its own device of the fourth memory 440. It is saved as a self configuration file in the configuration area 442. After the fourth network device 400 (device D) stores its own configuration file in its own device configuration area 442 of the fourth memory 440, the fourth network device 400 (automatically reboots) is executed to the fourth network device 400 (device D). Apply the configuration file for the own network device.

  FIG. 13 is a diagram showing an example of creating the configuration name of the first network device 100 (device A).

  The configuration name stored in the own device configuration area 142 of the first memory 140 is generated from the chassis ID and the configuration file storage date.

  FIG. 14 is a diagram showing the format of LLDP frame used in the embodiment of the present invention.

  There are two types of LLDP frames used in the embodiment of the present invention: an own apparatus configuration name storing LLDP frame and a default configuration name storing LLDP frame.

  In the LLDP frame, a transmission destination MAC (Media Access Control) address designates a multicast MAC address [01-80-C2-00-00-0E] of the LLDP frame defined by IEEE802.1AB. The transmission source MAC address specifies the MAC address of the interface that transmits the LLDP frame. Ethertype specifies LLDP Ethertype [88-CC].

  When the own configuration file is already stored in the own device configuration area of the memory, the local device configuration name storage LLDP frame is used. The configuration name storing LLDP frame for its own device stores the chassis ID and the own configuration name of the own configuration file in LLDP PDU (Protocol Data Unit).

  When the default configuration file is stored in the own device configuration area of the memory, the default configuration name storing LLDP frame is used. The default configuration name storage frame stores a default configuration subtype and a default configuration name which prove that the LLDP PDU is the default configuration.

  FCS in FIG. 14 is an abbreviation of Frame Check Sequence, and is a type of error detection method using a checksum for detecting an error in frame relay.

  FIG. 15 is a diagram showing the format of a configuration request frame used when requesting a configuration to an adjacent network device.

  In the configuration request frame, the transmission destination MAC address specifies the MAC address of the interface of the adjacent network device. The transmission source MAC address designates the MAC address of the interface of the own network device. Ethertype specifies Ethertype for the configuration request frame. The configuration name designates the adjacent configuration name of the adjacent network device acquired from the LLDP frame.

  FIG. 16 is a diagram showing the format of a configuration information frame used when transmitting a configuration file to an adjacent network device.

  There are two types of configuration information frames: an own apparatus configuration information frame that transmits an own configuration file to an adjacent network apparatus, and an adjacent apparatus configuration information frame that transmits an adjacent configuration file to an adjacent network apparatus.

  In the configuration information frame, the transmission destination MAC address specifies the MAC address of the interface of the adjacent network device. The transmission source MAC address designates the MAC address of the interface of the own network device.

  The Ethertype of the configuration information frame for own device designates an Ethertype for the configuration information frame for own device. Further, the configuration file for own device stores the own configuration file recorded in the configuration region for own device of the memory.

  The adjacent apparatus configuration information frame Ethertype specifies an Ethertype for the adjacent apparatus configuration information frame. The adjacent apparatus configuration file stores the adjacent configuration file recorded in the adjacent apparatus configuration area of the memory.

  FIG. 17 is a diagram showing a first LLDP MIB table 130 used in the embodiment of the present invention.

  In the first LLDP MIB table 130, the chassis ID is the chassis ID of the adjacent network device acquired from the LLDP frame. The connection port is a port number of the own network device to which the adjacent network device is connected. The configuration name is the adjacent configuration name of the adjacent network device acquired from the LLDP frame. The valid period is a period in which LLDP information is held in the first LLDP MIB table 130.

  Next, the operation of the first embodiment will be described using the flowcharts of FIG. 18 and FIG.

  First, the operation at the time of changing the configuration will be described with reference to FIG. In FIG. 18, the right side shows the operation of the second network device 200 (device B), and the left side shows the operation of the first network device 100 (device A).

  When the configuration change is performed, first, the second data processing unit 210 of the second network device 200 (device B) generates a second configuration file of its own configuration name including the chassis ID and the configuration save date and time. It is stored in the own device configuration area 242 of the memory 240 (step S501).

  Subsequently, in the second network device 200 (device B), the second LLDP frame processing unit 220 creates an LLDP frame 54 in which the own configuration name is stored in the LLDP PDU (step S502).

  The second data processing unit 210 of the second network device 200 (device B) transmits the created LLDP frame 54 from the port 1 to the first network device 100 (device A) which is the adjacent network device ( Step S503).

  In the first network device 100 (device A), which is an adjacent network device, the first data processing unit 110 receives the LLDP frame 54 at its port 1 (step S504).

  In the first network device 100 (device A), the first LLDP frame processing unit 120 expands the received LLDP frame 54, and acquires (extracts) the adjacent configuration name of the second network device 200 (device B). ) (Step S505).

  The first LLDP frame processing unit 120 checks the acquired (extracted) adjacent configuration name and the adjacent configuration name stored in the first LLDP MIB table 130 (step S506).

  The first LLDP frame processing unit 120 determines whether these adjacent configuration names are different (step S507). If the adjacent configuration names are not different (NO in step S507), the configuration change processing is completed.

  On the other hand, when the adjacent configuration names are different (YES in step S507), the first LLDP frame processing unit 120 acquires (extracts) the adjacent configuration name stored in the first LLDP MIB table 130. The name is updated (step S508). Then, the first LLDP frame processing unit 120 creates a configuration request frame 55 storing the acquired (extracted) adjacent configuration name (step S509).

  The first data processing unit 110 transmits the created configuration request frame 55 to the second network device 200 (device B) which is the adjacent network device that has transmitted the LLDP frame 54 (step S510).

  In the second network device 200 (device B), the second data processing unit 210 receives the configuration request frame 55, and stores its own configuration file stored in the own device configuration area 242 of the second memory 240. Are stored in the configuration information frame for own device 56 (step S511).

  Then, the second data processing unit 210 transmits its own device configuration information frame 56 to the first network device 100 (device A) that is the device that has transmitted the configuration request frame 55 (step S512).

  In the first network device 100 (device A), the first data processing unit 110 receives its own device configuration information frame 56 and adjoins the second network device 200 (device B), which is an adjacent network device. The configuration file is acquired (step S513).

  Then, the first data processing unit 110 stores the acquired adjacent configuration file in the adjacent device configuration area 144 of the first memory 140 (step S514).

  As described above, the configuration file can be changed.

  Next, with reference to FIG. 19, the operation in the case of automatically applying the configuration at the time of maintenance replacement will be described. In FIG. 19, the right side shows the operation of the fourth network device 400 (device D), and the left side shows the operation of the first network device 100 (device A).

  When performing maintenance and replacement of the network device, first, in the fourth network device 400 (device D) which is the network device that has been subjected to maintenance replacement, the fourth data processing unit 410 includes the configuration for its own device of the fourth memory 440. A default configuration file is held in the area 442 (step S601).

  Subsequently, in the fourth network device 400 (device D), the fourth LLDP frame processing unit 420 creates an LLDP frame 57 in which the default configuration subtype and the default configuration name are stored in the LLDP PDU (step S602).

  Then, the fourth data processing unit 410 of the fourth network device 400 (device D) transmits the LLDP frame 57 to the first network device 100 (device A) that is the adjacent network device (step S603).

  In the first network device 100 (device A) which is the adjacent network device, the first data processing unit 110 receives the LLDP frame 57 (step S604).

  Subsequently, in the first network device 100 (device A), the first LLDP frame processing unit 120 expands the received LLDP frame 57 (step S605).

  The first LLDP frame processing unit 120 determines whether there is a default configuration subtype in the LLDP frame 57 (step S606). If the default configuration subtype does not exist (NO in step S606), the first LLDP frame processing unit 120 discards the LLDP frame 57 and ends the processing.

  On the other hand, if there is a default configuration subtype (YES in step S606), the first LLDP frame processing unit 120 defaults the fourth network device 400 (device D), which is an adjacent network device, from the default configuration subtype. It is determined that the device holds the configuration file (step S607).

  Subsequently, the first LLDP frame processing unit 120 refers to the adjacent configuration name assigned to the port (in this example, port 2) that has received the LLDP frame 57 from the first LLDP MIB table 130 (step S608).

  The first LLDP frame processing unit 120 of the first network device 100 (device A) acquires the adjacent configuration file of the referred adjacent configuration name from the first adjacent device configuration area 144 of the first memory 140. (Step S609). Then, the first LLDP frame processing unit 120 stores the acquired adjacent configuration file in the adjacent apparatus configuration information frame 58 (step S610).

  The first data processing unit 110 of the first network device 100 (device A) is a fourth network device 400 (device D), which is an adjacent network device that has transmitted the LLDP frame 57 to the adjacent device configuration information frame 58. ) (Step S611).

  In the fourth network device 400 (device D), the fourth data processing unit 410 receives the adjacent device configuration information frame 58, and acquires (extracts) the adjacent configuration file stored therein (step S612). .

  Subsequently, the fourth data processing unit 410 stores the acquired (extracted) adjacent configuration file in the own device configuration area 442 of the fourth memory 440 as the own configuration file (step S613).

  Thereafter, the fourth data processing unit 410 of the fourth network device 400 (device D) performs an automatic restart, and stores the own configuration file stored in the own device configuration area 442 of the fourth memory 440. Apply to update the chassis ID (step S614).

  The above operation completes the automatic application of the configuration file at the time of maintenance replacement.

  Next, the effect of the first embodiment of the present invention will be described.

  The first embodiment of the present invention is effective in that it is possible to reduce the number of steps involved in preparation of configuration information before maintenance replacement of a maintenance worker and input of configuration information at the time of maintenance replacement. The reason is that, in the network system according to the first embodiment of the present invention, the process of automatically acquiring the configuration file from the adjacent network device at the time of maintenance and replacement works, so the number of steps for maintenance worker preparation for configuration information and configuration information input. It is possible to reduce

  The first embodiment of the present invention also has the effect of being able to avoid the risk of an operator at the time of maintenance replacement inserting an incorrect configuration file into the network device. The reason is that the memory of the network device according to the first embodiment of the present invention stores the adjacent configuration file of the adjacent network device before the maintenance replacement. This is because an appropriate configuration file can be obtained.

  FIG. 20 is a block diagram showing a network system according to the second embodiment of the present invention. The second embodiment is an embodiment in which a frame between network devices is encrypted using Media Access Control Security Protocol (MACsec) defined in IEEE 802.1AE.

  In the illustrated second embodiment, the configuration of the data processing unit constituting each network device is the same as that of FIG. 12 except that the configuration is different from that shown in FIG. 12, and operates. Therefore, in FIG. 20, the first, second, and fourth network devices are given reference numerals of 100A, 200A, and 400A, respectively, and the first, second, and fourth data processing units are Reference numerals 110A, 210A and 410A are given respectively. The same components as those shown in FIG. 12 carry the same reference numerals, and their description will be omitted for the sake of brevity.

  The first data processing unit 110A includes a first MACsec processing unit 112A. The first MACsec processing unit 112A performs MACsec encryption of the transmission frame and MACsec decryption of the reception frame.

  Similarly, the second data processing unit 210A includes a second MACsec processing unit 212A, and the fourth data processing unit 410A includes a fourth MACsec processing unit 412A.

  The default configuration file stored in the own device configuration area 442 of the fourth memory 440 of the fourth network device 400A (device D) includes a setting for enabling MACsec.

  The first LLDP frame processor 120 of the first network device 100 (device A) and the second LLDP frame processor 220 of the second network device 200A (device B) generate LLDP frames. The first MACsec processing unit 112A and the second MACsec processing unit 212A MACsec encrypt the generated LLDP frame, and periodically transmit the MACsec encrypted LLDP frame 93 to the adjacent network device. When the configuration file of the network device is changed, each network device notifies the adjacent network device of the new configuration name by the MACsec encrypted LLDP frame 93.

  The adjacent network device that receives the MACsec encrypted LLDP frame 93 storing the new configuration name transmits the MACsec encrypted configuration request frame 94 to the network device that transmitted the MACsec encrypted LLDP frame 93, and requests an adjacent configuration file. .

  The network devices 100A and 200B having received the MACsec encryption configuration request frame 94 store the own configuration file stored in the own device configuration areas 142 and 242 of the memories 140 and 240 in the MACsec encryption configuration information frame 95, The MACsec encrypted configuration information frame 95 is transmitted to the adjacent network device that has transmitted the MACsec encrypted configuration request frame 94.

The fourth network device 400A (device D) in the factory shipment state in which a specific configuration has not been set stores a default configuration file in its own device configuration area 442 of the fourth memory 440. The default configuration information includes a setting for enabling LLDP and a setting for adding a default configuration subtype to the LLDP frame 57. The fourth network device 400A (device D) transmits a MACsec encrypted LLDP frame 96 storing the default configuration name to the first network device 100 (device A) which is the adjacent network device.

The first network device 100 (device A) that has received the MACsec encrypted LLDP frame 96 storing the default configuration name uses the configuration name assigned to the port that received the LLDP frame in the first LLDP MIB table 130. refer. Also, the first network device 100 (device A) extracts the adjacent configuration file of the configuration name obtained by reference from the configuration region for the adjacent device of the first memory 140, and extracts it from the MACsec encryption for the adjacent network device. It is stored in the configuration information frame 97 and transmitted to the fourth network device 400A (device D).

  The fourth network device 400A (device D) having received the MACsec encryption configuration information frame 97 for the adjacent network device acquires the adjacent configuration file acquired (extracted) from the MACsec encryption configuration information frame 97 for the adjacent network device. It is stored as the own configuration file in the own device configuration area 442 of the fourth memory 440. After the fourth network device 400A (device D) stores its own configuration file in its own device configuration area 442 of the fourth memory 440, the fourth network device 400A performs an automatic restart to the fourth network device 400A (device D). Apply the configuration file for the own network device.

  FIG. 21 is a diagram showing the format of a MACsec encrypted LLDP frame. As apparent from the comparison with FIG. 14, each of the configuration name storing LLDP frame for its own device and the default configuration name storing LLDP frame shown in FIG. 21 further includes an IEEE 802.1 AE header and an ICV (Integrity Check Value). There is. Encrypts LLDP information with the IEEE 802.1AE header and ICV.

  FIG. 22 is a diagram showing the format of a MACsec encryption configuration request frame. As apparent from the comparison with FIG. 15, the MACsec encryption configuration request frame shown in FIG. 22 also further includes an IEEE 802.1AE header and an ICV. Encrypts the configuration request information with the IEEE802.1AE header and ICV.

  FIG. 23 is a diagram showing the format of a MACsec encryption configuration information frame. As apparent from the comparison with FIG. 16, each of the configuration information frame for own apparatus and the configuration information frame for adjacent apparatus shown in FIG. 23 further includes an IEEE 802.1AE header and an ICV. Encrypts configuration information with the IEEE 802.1AE header and ICV.

  As described above, in the second embodiment, in order to encrypt all the frames between network devices by MACsec, it is possible to protect the configuration name stored in the frame and the information of the configuration file from those who try to eavesdrop on the information it can.

  FIG. 24 is a block diagram showing a network system according to the third embodiment of the present invention. The third embodiment is an embodiment in which the configuration area for the adjacent device is not held in the memory (configuration storage unit).

  In the illustrated third embodiment, the second network device and the fourth network device operate similarly to those of FIG. 12 except for the points different from those shown in FIG. Thus, in FIG. 24, the second and fourth network devices are labeled 200 B and 400 B, respectively. The same components as those shown in FIG. 12 carry the same reference numerals, and their description will be omitted for the sake of brevity.

  The second network device 200B has the same configuration as that of the second network device 200 shown in FIG. 12 except that the configuration of the second memory is different, and operates. Thus, the second memory is labeled 240 B.

  The second memory 240A includes only the own device configuration area 242, and does not include the adjacent device configuration area.

  Similarly, the fourth network device 400B has a configuration similar to that of the fourth network device 400 shown in FIG. 12 except that the configuration of the fourth memory is different. Thus, the fourth memory is labeled 440 B.

  The fourth memory 440A includes only its own device configuration area 442, and does not include the adjacent device configuration area.

  The first memory 140 of the first network device 100 (device A) has an adjacent device configuration area 142. Therefore, in the adjacent device configuration area 142 of the first memory 140, the adjacent configuration stored in the configuration information frame received from the second network device 200B (device B) and the fourth network device 400B (device D). I have saved a file.

  On the other hand, the second memory 240B of the second network device 200B (device B) and the fourth memory 440B of the fourth network device 400B (device D) do not have an adjacent device configuration area. Therefore, the second memory 240B and the fourth memory 440A do not store the adjacent configuration file of the first network device 100 which is the adjacent network device.

  Further, the second network device 200B (device B) and the fourth network device 400B (device D) do not transmit a configuration request frame for requesting an adjacent configuration file of the first network device 100 (device A).

  Thus, in the third embodiment of the present invention, it is possible to reduce the number of frames transmitted and received between network devices.

  The present invention is not limited to the above embodiment, and it goes without saying that various modifications can be made within the technical scope described in the claims.

  Some or all of the above-described embodiments and examples may be described as in the following appendices, but are not limited thereto.

(Supplementary Note 1) A process of acquiring an adjacent configuration file from an adjacent network device
Storing the acquired adjacent configuration file in the memory of the own network device;
Configuration exchange method including:

(Supplementary Note 2) The step of acquiring
Storing the adjacent configuration name of the adjacent configuration file in a table of the own network device;
Extracting an adjacent configuration name from the LLDP frame transmitted from the adjacent network device;
Comparing the extracted adjacent configuration name with the stored adjacent configuration name;
Sending a configuration request frame to the adjacent network device if there is a difference in the comparison result;
Receiving a configuration information frame transmitted from the adjacent network device;
Extracting the adjacent configuration file from the received configuration information frame;
The configuration exchange method according to appendix 1, comprising:

(Additional remark 3) When the said adjacent network apparatus was maintenance-exchanged by another network apparatus, the process of transmitting the said adjacent configuration file preserve | saved at the said memory to the said another network apparatus is included further. Configuration exchange method described in.

(Supplementary Note 4)
Receiving an LLDP frame storing a default configuration name from the other network device;
The adjacent configuration file stored in the memory is stored in a configuration information frame with reference to the default configuration name stored in the received LLDP frame, and the configuration information frame is transmitted to the other network device The process to
The configuration exchange method according to appendix 3, comprising:

(Supplementary Note 5) storing the own configuration file of the own network device in the memory;
Transmitting the stored own configuration file to an adjacent network device;
Configuration exchange method including:

(Supplementary Note 6)
Receiving a configuration request frame from the adjacent network device;
Storing the own configuration file stored in the memory in a configuration information frame in response to the received configuration request frame, and transmitting the configuration information frame to the adjacent network device;
The configuration exchange method according to appendix 5, comprising:

(Supplementary Note 7) A step of acquiring a configuration file for the own network device from the adjacent network device when performing maintenance and replacement,
Storing the acquired configuration file as a self configuration file in a memory of the self network device;
Maintenance replacement method including:

(Supplementary Note 8) The step of acquiring
Transmitting an LLDP frame storing a default configuration name to the adjacent network device;
Receiving a configuration information frame storing the configuration file from the adjacent network device;
Extracting the configuration file from the received configuration information frame;
The maintenance exchange method according to appendix 7, comprising

(Supplementary Note 9) A computer which is a network device
A function of acquiring an adjacent configuration file from an adjacent network device;
A function of storing the acquired adjacent configuration file in the memory of the own network device;
Configuration exchange program to realize.

(Supplementary Note 10) The function to be acquired is in the computer,
Storing an adjacent configuration name of the adjacent configuration file in a table of the own network device;
A function of extracting an adjacent configuration name from an LLDP frame transmitted from the adjacent network device;
A function of comparing the extracted adjacent configuration name with the stored adjacent configuration name;
Sending the configuration request frame to the adjacent network device if there is a difference in the comparison result;
A function of receiving a configuration information frame transmitted from the adjacent network device;
A function of extracting the adjacent configuration file from the received configuration information frame;
The configuration exchange program according to appendix 9, which realizes

(Supplementary Note 11) Allowing the computer to further realize the function of transmitting the adjacent configuration file stored in the memory to the other network device when the adjacent network device is maintenance-exchanged with another network device. , Configuration exchange program described in Supplementary Note 9 or 10.

(Supplementary Note 12) The transmission function may be sent to the computer,
A function of receiving an LLDP frame storing a default configuration name from the another network device;
The adjacent configuration file stored in the memory is stored in a configuration information frame with reference to the default configuration name stored in the received LLDP frame, and the configuration information frame is transmitted to the other network device Function to be
The configuration exchange program according to appendix 11, which realizes

(Supplementary Note 13) A computer which is a network device
A function to save the own configuration file of the own network device in the memory;
A function of transmitting the saved own configuration file to an adjacent network device;
Configuration exchange program to realize

(Supplementary Note 14) The transmission function may be sent to the computer,
A function of receiving a configuration request frame from the adjacent network device;
A function of storing the own configuration file stored in the memory in a configuration information frame in response to the received configuration request frame, and transmitting the configuration information frame to the adjacent network device;
The configuration exchange program according to Appendix 13, which realizes

(Supplementary Note 15) A computer which is a network device
A function of acquiring a configuration file for the own network device from an adjacent network device when performing maintenance replacement;
A function of storing the acquired configuration file in the memory of the own network device as the own configuration file;
Maintenance exchange program to realize.

(Supplementary Note 16) The function to be acquired is in the computer,
A function of transmitting an LLDP frame storing a default configuration name to the adjacent network device;
A function of receiving a configuration information frame storing the configuration file from the adjacent network device;
A function of extracting the configuration file from the received configuration information frame;
15. The maintenance exchange program according to appendix 15, which realizes

(Supplementary Note 17) A memory for storing an own configuration file of an own network device and an adjacent configuration file of an adjacent network device,
A table storing an adjacent configuration name of the adjacent configuration file;
A transmitting / receiving unit that transmits / receives a configuration request frame, an LLDP frame storing a configuration name, and a configuration information frame storing a configuration file between the adjacent network device and the own network device;
An LLDP frame processing unit that generates and expands the LLDP frame;
A data processing unit that processes the configuration request frame, the LLDP frame, and the configuration information frame that are transmitted and received by the transmission / reception unit;
A network device having

  The invention is applicable to telecommunication network infrastructures.

100, 100A first network device (device A)
110, 110A first data processing unit 112A first MACsec processing unit 120 first LLDP frame processing unit 130 first table (first LLDP MIB table)
140 First memory (first configuration storage unit)
142 first own device configuration area 144 first adjacent device configuration area 150 first processing unit 200, 200A, 200B second network device (device B)
210, 210A second data processing unit 212A second MACsec processing unit 220 second LLDP frame processing unit 230 second table (second LLDP MIB table)
240 Second memory (second config storage unit)
242 Second own device configuration area 244 second adjacent device configuration area 250 second processing unit 300 third network device (device C)
330 Third table (third LLDP MIB table)
340 Third Memory (Third Config Storage Unit)
350 Third Processing Unit 400, 400A, 400B Fourth Network Device (Device D)
410, 410A fourth data processing unit 412A fourth MACsec processing unit 420 fourth LLDP frame processing unit 430 fourth table (fourth LLDP MIB table)
440 Fourth memory (fourth config storage unit)
442 Fourth configuration for own device 444 Fourth configuration for adjacent device 450 Fourth processing unit

Claims (9)

Acquiring an adjacent configuration file from an adjacent network device;
Storing the acquired adjacent configuration file in the memory of the own network device;
Including
The step of acquiring is
Storing the adjacent configuration name of the adjacent configuration file in a table of the own network device;
A step of extracting the neighbor configuration name from the neighboring network devices transmitted from, LLDP frame storing adjacent configuration name,
Comparing the extracted adjacent configuration name with the stored adjacent configuration name;
Sending out a configuration request frame storing the extracted adjacent configuration name to the adjacent network device if there is a difference in the comparison result;
Receiving a configuration information frame storing the adjacent configuration file transmitted from the adjacent network device;
Extracting the adjacent configuration file from the received configuration information frame;
Have a configuration exchange method. And transmitting the adjacent configuration file stored in the memory to the other network device when the adjacent network device is maintenance-exchanged with another network device.
The transmitting step is
Receiving an LLDP frame storing a default configuration name from the other network device;
The adjacent configuration file stored in the memory is stored in a configuration information frame with reference to the default configuration name stored in the received LLDP frame, and the configuration information frame is transmitted to the other network device The process to
The configuration exchange method according to claim 1, comprising: Storing the own configuration file of the own network device in the memory;
Transmitting the stored own configuration file to an adjacent network device;
Including
The transmitting step is
Receiving a configuration request frame storing its own configuration name from the adjacent network device;
Storing the own configuration file stored in the memory in a configuration information frame in response to the received configuration request frame, and transmitting the configuration information frame to the adjacent network device;
Have a configuration exchange method. Obtaining a configuration file for the own network device from the adjacent network device at the time of maintenance replacement;
Storing the acquired configuration file as a self configuration file in a memory of the self network device;
Including
The step of acquiring is
Transmitting an LLDP frame storing a default configuration name to the adjacent network device;
Receiving a configuration information frame storing the configuration file from the adjacent network device;
Extracting the configuration file from the received configuration information frame;
Maintenance replacement method. In a computer that is a network device,
A function of acquiring an adjacent configuration file from an adjacent network device;
A function of storing the acquired adjacent configuration file in the memory of the own network device;
Configuration exchange program for realizing
The function to acquire is on the computer,
Storing an adjacent configuration name of the adjacent configuration file in a table of the own network device;
The neighbor network devices transmitted from the function of extracting the neighbor configuration name from LLDP frame storing adjacent configuration name,
A function of comparing the extracted adjacent configuration name with the stored adjacent configuration name;
A function of transmitting a configuration request frame including the extracted adjacent configuration name to the adjacent network device when there is a difference in the comparison result;
A function of receiving a configuration information frame storing the adjacent configuration file, transmitted from the adjacent network device;
A function of extracting the adjacent configuration file from the received configuration information frame;
Configuration exchange program to realize the. The computer further realizes a function of transmitting the adjacent configuration file stored in the memory to the other network device when the adjacent network device is maintenance-exchanged with another network device.
The function to transmit is to the computer,
A function of receiving an LLDP frame storing a default configuration name from the another network device;
The adjacent configuration file stored in the memory is stored in a configuration information frame with reference to the default configuration name stored in the received LLDP frame, and the configuration information frame is transmitted to the other network device Function to be
The configuration exchange program according to claim 5, wherein In a computer that is a network device,
A function to save the own configuration file of the own network device in the memory;
A function of transmitting the saved own configuration file to an adjacent network device;
Configuration exchange program to realize
The function to transmit is to the computer,
A function of receiving a configuration request frame storing its own configuration name from the adjacent network device;
A function of storing the own configuration file stored in the memory in a configuration information frame in response to the received configuration request frame, and transmitting the configuration information frame to the adjacent network device;
Configuration exchange program to realize the. In a computer that is a network device,
A function of acquiring a configuration file for the own network device from an adjacent network device when performing maintenance replacement;
A function of storing the acquired configuration file in the memory of the own network device as the own configuration file;
Maintenance exchange program to realize
The function to acquire is on the computer,
A function of transmitting an LLDP frame storing a default configuration name to the adjacent network device;
A function of receiving a configuration information frame storing the configuration file from the adjacent network device;
A function of extracting the configuration file from the received configuration information frame;
Maintenance exchange program to realize. A memory for storing an own configuration file of an own network device and an adjacent configuration file of an adjacent network device;
A table storing an adjacent configuration name of the adjacent configuration file;
A transmitting / receiving unit that transmits / receives a configuration request frame, an LLDP frame storing a configuration name, and a configuration information frame storing a configuration file between the adjacent network device and the own network device;
An LLDP frame processing unit that generates and expands the LLDP frame;
A data processing unit that processes the configuration request frame, the LLDP frame, and the configuration information frame that are transmitted and received by the transmission / reception unit;
A network device having

Images