Network management server, network device and misconnection detection program

Abstract

To handle a connection with a different port from before not as a wrong connection when there is no influence on communication etc., even on connecting with any of a plurality of ports in replacement work for network equipment.SOLUTION: When a cable is reconnected as a network device is replaced, a wrong connection detection part of a network management server compares opposite identification information of current value information with opposite identification information of expectation value information, and refers to port configuration information to compare group identification information before the replacement of the network device with group identification information after the replacement of the network device so as to determine whether a wrong connection of the cable is made based upon results of the comparisons.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a network management server, a network device, and an erroneous connection detection program. [Background technology]

[0002] In recent years, changes in social conditions and lifestyles have led to the spread of network systems, with network devices being installed everywhere. However, there is a shortage of personnel to operate and manage network devices, and the number of personnel available on-site is limited, so non-expertise and efficiency are required for the operation and management of a large number of network devices.

[0003] When replacing network devices, which is one part of operational management, it is necessary to connect the many cables connected to the devices to the same ports as before. If a misconnection occurs during this process, specialized troubleshooting is required to understand the communication status, detect the misconnection, and identify the location of the misconnection, and it takes time to restore the system. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-176393 A [Patent Document 2] JP 2008-124791 A Summary of the Invention [Problem to be solved by the invention]

[0005] Patent Document 1 describes an invention that detects incorrect cable connection to a port of a network device. The invention uses the MAC (Media Access Control) address received via LLDP (Link Layer Discovery Protocol) or OAM (Operation Administration and Maintenance) as the opposing endpoint ID of the opposing side, and compares an expected value of the opposing endpoint ID that is set and stored in advance with the current value of the opposing endpoint ID received from the opposing side after the cable is reconnected, detecting whether the connection is incorrect based on whether they match or mismatch.

[0006] Also, the invention described in Patent Document 2 is a method in which the MAC address in an FDB (Forwarding Database) is used as the opposing endpoint ID, and the opposing endpoint ID received in advance from the opposing side is used as the expected value.

[0007] These methods have the problem that in the case of a Layer 2 switch, which is a network device, even if there are multiple ports to which a terminal can be connected without affecting communications, etc., simply connecting to a port different from the previous one will be detected as an incorrect connection.

[0008] An object of the present invention is to, in the replacement work of network equipment, when a connection to a port different from the previous one is not treated as an erroneous connection if the connection to any of a plurality of ports will not affect communication, etc. [Means for solving the problem]

[0009] A network management server according to one embodiment of the present invention is a network management server connected via a network to a network device having a plurality of ports connected to a plurality of opposing devices by cables, the network management server having a misconnection detection unit, the misconnection detection unit stores expected value information in which a plurality of the ports are associated with the opposing identification information of a plurality of the opposing devices in a state before the network device is replaced, current value information in which a plurality of the ports are associated with the opposing identification information of a plurality of the opposing devices in a state after the network device is replaced, and port configuration information in which a plurality of the ports are associated with group identification information grouped according to the configuration of the ports, and when the cable is reconnected due to replacement of the network device, the misconnection detection unit compares the opposing identification information in the current value information with the opposing identification information in the expected value information, refers to the port configuration information, compares the group identification information before the network device is replaced with the group identification information after the network device is replaced, and determines whether or not the cable is misconnected based on the result of the comparison.

[0010] A network device according to one embodiment of the present invention is a network device having a plurality of ports connected to a plurality of opposing devices by cables, the network device having the misconnection detection unit and a removable auxiliary storage medium, the auxiliary storage medium stores expected value information in which a plurality of the ports are associated with opposing identification information of a plurality of the opposing devices in a state before the network device is replaced, the misconnection detection unit stores current value information in which a plurality of the ports are associated with the opposing identification information of a plurality of the opposing devices in a state after the network device is replaced, and port configuration information in which the ports are associated with group identification information grouped according to the configuration of the ports, and when the cable is reconnected due to replacement of the network device, the auxiliary storage medium is replaced from the network device before replacement to the network device after replacement, and the misconnection detection unit compares the opposing identification information of the current value information with the opposing identification information of the expected value information stored in the auxiliary storage medium, refers to the port configuration information, compares the group identification information before the network device is replaced with the group identification information after the network device is replaced, and determines whether or not the cable is misconnected based on the result of the comparison.

[0011] A misconnection detection program according to one embodiment of the present invention is a misconnection detection program stored in a network management server connected via a network to a network device having a plurality of ports connected to a plurality of opposing devices by cables, the misconnection detection program being configured to be executed by a computer to perform the following processes: storing expected value information in which a plurality of the ports are associated with opposing identification information of a plurality of the opposing devices in a state before the network device is replaced, current value information in which a plurality of the ports are associated with the opposing identification information of a plurality of the opposing devices in a state after the network device is replaced, and port configuration information in which a plurality of the ports are associated with group identification information grouped according to the configuration of the ports; when the cable is reconnected due to replacement of the network device, comparing the opposing identification information of the current value information with the opposing identification information of the expected value information; referring to the port configuration information, comparing the group identification information before the replacement of the network device with the group identification information after the replacement of the network device; and determining whether or not the cable is misconnected based on a result of the comparison. Effect of the Invention

[0012] According to one aspect of the present invention, when replacing network equipment, if connecting to any of multiple ports will not affect communications, etc., connecting to a port different from the previous one can be done without being treated as an incorrect connection. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 illustrates a network configuration. [Diagram 2] FIG. 13 is a diagram showing a network configuration after reconnection. [Diagram 3] FIG. 2 is a diagram illustrating a configuration of a network management server according to the first embodiment. [Figure 4] 1 is a diagram illustrating a configuration of a Layer 2 switch according to a first embodiment. [Diagram 5]FIG. 11 is a diagram showing expected values ​​of LLDP information. [Figure 6] FIG. 13 is a diagram showing expected values ​​of FDB information. [Figure 7] FIG. 13 is a diagram showing the current value of LLDP information. [Figure 8] FIG. 13 is a diagram showing the current values ​​of FDB information. [Figure 9] FIG. 13 is a diagram showing LLDP information for comparison. [Figure 10] FIG. 13 is a diagram showing FDB information for comparison. [Figure 11] FIG. 13 is a diagram showing port configuration information. [Figure 12] 5 is a flowchart showing the overall operation of erroneous connection detection in the first embodiment. [Figure 13] 13 is a flowchart showing an operation of collecting an expected value. [Figure 14] 13 is a flowchart showing a current value collection operation and a peer ID comparison operation. [Figure 15] 13 is a flowchart showing a collection operation and a grouping and comparison operation of a port configuration. [Figure 16] 13 is a flowchart showing a final comparison operation. [Figure 17] FIG. 13 is a diagram showing an example of a user I / F screen. [Figure 18] FIG. 11 illustrates a configuration of a Layer 2 switch according to a second embodiment. [Figure 19] FIG. 11 is a diagram illustrating an example of LLDP information in a Layer 2 switch. [Figure 20] FIG. 11 is a diagram illustrating an example of FDB information in a layer 2 switch. [Figure 21] 13 is a flowchart showing the overall operation of erroneous connection detection in the second embodiment. [Figure 22] FIG. 11 is a diagram illustrating a network configuration in a third embodiment. [Diagram 23] FIG. 13 is a diagram illustrating a network configuration after reconnection in the third embodiment. [Figure 24] FIG. 13 is a diagram showing an expected value of FDB information in the third embodiment. [Diagram 25]FIG. 13 is a diagram showing the current value of FDB information in the third embodiment. [Figure 26] FIG. 13 is a diagram showing FDB information for comparison in the third embodiment. [Figure 27] 13 is a flowchart showing the overall operation of erroneous connection detection in the third embodiment. [Figure 28] 13 is a flowchart showing a comparison operation of a plurality of candidates in the third embodiment. [Figure 29] FIG. 13 is a diagram illustrating an example of a user I / F screen in the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, the embodiments will be described with reference to the drawings. EXAMPLES

[0015] In the first embodiment, a configuration is described in which a misconnection detection unit is included in a network management server, and when a cable is reconnected due to replacement of a Layer 2 switch, etc., a misconnection to a port that does not affect communication because it has the same port configuration is tolerated, while a misconnection that affects communication and causes actual damage is detected.

[0016] FIG. 1 is an explanatory diagram illustrating an example of the configuration of a network system according to a first embodiment of the present invention. In the network system of FIG. 1, a network management server S50 is connected to a layer 2 switch S10, which is a target for detecting misconnections, via a network N10. The layer 2 switch S10 has ports P11 to P17. Port P11 is connected to the opposite terminal A (U10), port P12 is connected to the opposite terminal B (U20), port P13 is connected to the opposite terminal C (U30), port P14 is connected to the opposite device A (S20), port P15 is connected to the opposite device B (S30), and port P16 is connected to the opposite device C (S40) by cables such as copper wires and optical fibers. Note that nothing is connected to port P17. Here, the opposite device refers to a layer 2 switch other than the layer 2 switch S10, or a layer 3 switch.

[0017] FIG. 3 is an explanatory diagram showing an example of the configuration of the network management server S50. The network management server S50 is composed of a CPU 100, a network I / F 101, and a memory 102, and has a misconnection detection unit M10 and a user I / F unit M20 in the memory 102. Furthermore, the misconnection detection unit M10 has a device information collection unit F10, a comparison unit F20, and a grouping unit F30 as processing units, and has tables of LLDP information (expected value) T10, LLDP information (current value) T11, LLDP information (comparison value) T12, FDB information (expected value) T20, FDB information (current value) T21, FDB information (comparison value) T22, and port configuration information T30. In this embodiment, the misconnection detection unit M10, the device information collection unit F10, the comparison unit F20, the grouping unit F30, and the user I / F unit M20 are all programs executed by the CPU 100.

[0018] The misconnection detection unit M10 collects information on the cable connection status of each port (P11 to P17) of the Layer 2 switch S10 and on the connected device from the Layer 2 switch S10 in each state before and after the replacement of the Layer 2 switch S10, and compares them to determine whether a cable is misconnected. The detailed operation, the contents of each table, and how to use them will be described later using the flowcharts in Figure 12 and subsequent figures.

[0019] FIG. 4 is an explanatory diagram showing an example of a general configuration of the Layer 2 switch S10. 4 is composed of a CPU 103, a network I / F 104 equipped with multiple ports, a memory 105, and a packet relay unit 106. The memory 105 has a control unit M40, a user I / F unit M30, and tables of LLDP information T40 and FDB information T50. Both the control unit M40 and the user I / F unit M30 are programs executed by the CPU 103.

[0020] In the Layer 2 switch S10, when a packet is received at any port of the network I / F 104, the packet forwarding unit 106 determines another port of the network I / F 104 to which the packet is to be forwarded based on the destination MAC address of the packet and the contents of the FDB information T50, and transmits the packet from that port. Alternatively, if the destination MAC address of the packet is the MAC address of the Layer 2 switch S10 itself, the packet is interpreted as being addressed to the Layer 2 switch S10 and forwarded to the CPU 103. Furthermore, if necessary, the combination of the source MAC address of the packet and the identifier of the port that received the packet is registered in the FDB information T50 (MAC address learning).

[0021] 20 is a diagram showing an example of FDB information T50. It is possible to store multiple entries of combinations of port identification information (port C500) and MAC address (counterpart ID (MAC address) C501), and holds information on which port a terminal with which MAC address is connected.

[0022] When the control unit M40 receives a packet addressed to the Layer 2 switch S10 from the packet relay unit 106, it executes appropriate processing according to the contents of the packet. For example, if the packet is a packet conforming to a protocol called LLDP, it stores the identification information of the opposing device (such as another Layer 2 switch) contained in the packet in the LLDP information T40 together with the identification information of the port that received the packet.

[0023] FIG. 19 is a diagram showing an example of the LLDP information T40.

[0024] It is possible to store multiple entries of combinations of port identification information (port C400) and identification information contained in the LLDP packet (counterpart ID (device) C401), and it holds information on which port a device such as a Layer 2 switch with which identification information is connected.

[0025] If the packet that the control unit M40 received from the packet relay unit 106 is an information collection command from the network management server S50, the control unit M40 performs processing to transmit the contents of the LLDP information T40 or FDB information T50 as a response to the network management server S50 in accordance with the contents of the command. As a protocol for such commands and responses, for example, SNMP (Simple Network Management Protocol) can be used.

[0026] The user I / F unit M30 provides a user I / F function that enables an administrator to carry out various setting processes and status confirmation for the layer 2 switch S10.

[0027] 2 is an explanatory diagram showing an example of the network configuration after replacing the Layer 2 switch S10. Note that the Layer 2 switch S10 is replaced with a physically different switch, but it has the same configuration as the Layer 2 switch S10 before the replacement, and the same components are denoted by the same reference numerals.

[0028] The network configuration in Fig. 2 shows that in the configuration in Fig. 1, Layer 2 switch S10 has been replaced, and the cables have been reconnected, resulting in port P11 being connected to opposite terminal B (U20), port P12 to opposite terminal A (U10), port P13 to opposite terminal C (U30), port P15 to opposite device A (S20), and port P17 to opposite device C (S40). Note that nothing is connected to ports P14 and P16.

[0029] An example of an operation for detecting the occurrence of a misconnection will be described below, taking as an example a case where a misconnection as shown in FIG. 2 occurs due to a reconnection operation after replacing a device in the system configuration of FIG.

[0030] FIG. 12 is a flowchart showing the overall operation of the misconnection detection by the misconnection detection unit M10.

[0031] The misconnection detection unit F10 determines whether it is time to execute the device information collection process (step F122), and if it is time to execute the device information collection process, it calls the device information collection unit F10 to execute the expected value collection process step F13 and then proceeds to step F123, otherwise it proceeds directly to step F123. The timing for executing the device information collection process may be, for example, to be periodically executed at a predetermined time interval, or may be the timing when the administrator receives a command to start the device information collection process through the user I / F unit M20.

[0032] 13 is a flowchart showing details of the expected value collection process (step F13). The process of step F13 is executed by the device information collection unit F10 called by the misconnection detection unit M10.

[0033] The device information collection unit F10 collects the contents of the LLDP information T40 and the FDB information T50 from the layer 2 switch S10 using a protocol such as SNMP (step F132).Then, it stores the collected contents of the LLDP information T40 in the LLDP information (expected value) T10, and the collected contents of the FDB information T50 in the FDB information (expected value) T20 (step F133).

[0034] 5 and 6 are diagrams showing the contents of LLDP information (expected value) T10 and FDB information (expected value) T20. LLDP information (expected value) T10 is made up of multiple entries that hold the combination of device C100, port C101, and peer ID (device) C102. FDB information (expected value) T20 is made up of multiple entries that hold the combination of device C200, port C201, and peer ID (MAC address) C202.

[0035] In step F132, the device information collection unit F10 stores the contents of the LLDP information T40 collected from the Layer 2 switch S10 in the fields of the same name, port C101 and peer ID (device) C102, of the LLDP information (expected value) T10, and also stores an identifier (for example, "S10") indicating that the information was collected from the Layer 2 switch S10 in a field of the device C100. Similarly, the value of the collected FDB information T50 is also stored in the corresponding field of the same name in the FDB information (expected value) T20, and also stores an identifier indicating that it was collected from the Layer 2 switch S10 in a field of the device C200.

[0036] The information stored in the LLDP information (expected value) T10 and the FDB information (expected value) T20 is called the "expected value" because it is used as information indicating the expected original connection state when the Layer 2 switch S10 is replaced and the cable is reconnected.

[0037] 12, the misconnection detection unit M10 next determines whether replacement of the Layer 2 switch S10 and associated reconnection of the cable have occurred (step F123). The misconnection detection unit M10 recognizes that replacement of the Layer 2 switch S10 and reconnection of the cable have occurred, for example, by receiving a notification based on a protocol such as SNMP that is sent when the replaced Layer 2 switch S10 starts up, or by receiving a command from the user I / F unit M20 from the administrator indicating that replacement of the Layer 2 switch S10 has been performed.

[0038] If the Layer 2 switch S10 is replaced and the cable is reconnected, the misconnection detection unit M10 starts the process for misconnection determination from step F14 onwards, and if not, returns to the process of step F122. That is, until the Layer 2 switch S10 is replaced and the cable is reconnected, the misconnection detection unit M10 repeatedly collects the latest LLDP information and FDB information from the Layer 2 switch S10 at a predetermined timing, and when the Layer 2 switch S10 is replaced and the cable is reconnected, it operates to start the process for determining whether or not a cable misconnection has occurred.

[0039] When the misconnection detection unit M10 determines in step F123 that the Layer 2 switch S10 has been replaced and the cable reconnected, it sequentially executes the following processes to determine whether or not there is a misconnection: a process of collecting current values ​​of device information after reconnection from the Layer 2 switch S10 and comparing them with the expected values ​​collected in step F13 (step F14), a process of collecting port configuration information from the Layer 2 switch S10, grouping and comparing them (step F15), and a final comparison process of determining whether or not there is a misconnection (step F16). Details of these processes will be described below.

[0040] FIG. 14 is a flow chart showing the details of the process (step F14) of collecting the current values ​​of the device information after reconnection from the layer 2 switch S10 and comparing them with the expected values.

[0041] After the process starts, the device information collection unit F10, called by the misconnection detection unit M10, collects the contents of the LLDP information T40 and FDB information T50 from the Layer 2 switch S10 using a protocol such as SNMP, and stores the collected contents of the LLDP information T40 in LLDP information (current value) T11, and the collected contents of the FDB information T50 in FDB information (current value) T21 (step F142).

[0042] 7 and 8 are diagrams showing the contents of LLDP information (current value) T11 and FDB information (current value) T21. These tables have the same structure as LLDP information (expected value) T10 and FDB information (expected value) T20, respectively. The process of the device information collection unit F10 in step 142 is also the same as the process of the device information collection unit F10 shown in FIG. 13, except that the storage destination tables for the acquired information are LLDP information (current value) T11 and FDB information (current value) T21, and a detailed description thereof will be omitted.

[0043] In the following explanation, since the same processing is performed on LLDP information and FDB information, they may be collectively referred to as LLDP / FDB information to avoid repeating the same explanation. Similarly, table names may be collectively referred to as multiple tables, for example, "LLDP / FDB information (current value) T11 / T21."

[0044] Next, the comparison unit F20 called by the misconnection detection unit M10 executes the processes from step F143 onwards.

[0045] First, the comparison unit F20 saves values ​​used for the connection destination comparison process before and after the cable reconnection in the LLDP / FDB information (for comparison) T12 / T22 (step F143). Specifically, for each entry of the LLDP information (expected value) T10, the values ​​of the device C100, port C101, and the peer ID (device) C102 are saved in the device C120, port C121, and peer ID expected value C122 of the LLDP information (for comparison) T12, respectively. Furthermore, for each entry of the LLDP information (current value) T11, the peer ID (device) C112 is saved in the peer ID current value C123 of the entry having the same device and port values ​​in the LLDP information (for comparison) T12. Also, for the FDB information (for comparison) T22, the contents of the FDB information (expected value) T20 and the FDB information (current value) T21 are saved in the same way as in the case of the LLDP information (for comparison) T12.

[0046] 9 and 10 are diagrams showing the contents of LLDP information (expected value) T12 and FDB information (for comparison) T22, respectively. These tables are made up of multiple entries that hold information for determining whether or not there is a port of the network I / F 104 whose connection destination has changed before and after the cable reconnection in the Layer 2 switch S10. Note that in the LLDP / FDB information (expected value) T12 / T22, fields that do not have information to be stored in step F143 are indicated with "-".

[0047] Next, the comparison unit F20 compares the peer ID expected value C122 / C222 with the peer ID current value C123 / C223 for each entry of the LLDP / FDB information (for comparison) T12 / T22 (step F144). The fact that the peer ID expected value C122 / C222 and the peer ID current value C123 / C223 are the same means that the device connected to the port of the device indicated by the entry is the same before and after the cable reconnection.

[0048] There are two types of peer IDs that are used for comparison with the connected device: those contained in the LLDP information (device identifier) ​​and those contained in the FDB information (device MAC address). The comparison process will use the LLDP information as a priority, and for ports connected to devices that do not support LLDP (i.e. ports that do not have LLDP information), the FDB information will be used.

[0049] If the comparison shows that the peer ID expected value C122 / C222 and the peer ID current value C123 / C223 are identical (YES in step F145), "match" is saved in the peer ID comparison C124 / C224 of the LLDP / FDB information (for comparison) T12 / T22 (step F146), and the current value collection process and peer ID comparison process F14 are terminated.

[0050] In step F145, if the peer ID expected value C122 / C222 and the peer ID current value C123 / C223 are not identical (NO in step F145), it is further determined whether the value of the peer ID current value C123 / C223 of the LLDP / FDB information (for comparison) T12 / T22 is stored (step F147). If there is no value (indicated as "-"), "not connected" is saved in the peer ID comparison C124 / C224 of the LLDP / FDB information (for comparison) T12 / T22 and the current value collection process and the peer ID comparison process F14 are terminated (step F148). If there is a value, "mismatch" is saved in the peer ID comparison C124 / C224 of the LLDP / FDB information (for comparison) T12 / T22 and the current value collection process and the peer ID comparison process F14 are terminated (step F149).

[0051] The processes from step F144 to step F149 are executed for all entries of the LLDP / FDB information (for comparison) T12 / T22.

[0052] FIG. 15 is a flowchart showing the details of the port configuration collection operation and grouping comparison process (step F15).

[0053] After the process starts, in process F152, the device information collection unit F10 called by the misconnection detection unit M10 collects port configuration information from the Layer 2 switch S10 using a protocol such as SNMP, and stores the information in the port configuration information T30. Note that in the first embodiment, it is assumed that the port configuration of the Layer 2 switch S10 is the same before and after the replacement.

[0054] 11 is a diagram showing the contents of the port configuration information T30. The port configuration information T30 is a table that stores the setting state of each port of the network I / F 104 acquired from the layer 2 switch S10, and has multiple entries for each port, each of which is made up of fields: VLANC302 that stores the VLAN identifier to which the port belongs, I / F speed C303 that indicates the line speed of the port, and port group IDC304 that stores the ID assigned to the port in step F153.

[0055] Next, the grouping unit F30 called by the misconnection detection unit M10 assigns a group ID to each port C301 in the port configuration information T30 so that ports with the same VLAN C302 and I / F speed C303 are grouped together, and stores the group ID in the group IDC304. To explain using the example values ​​shown in Fig. 11, for example, ports P11 and P12 both belong to the same VLAN "100" and both have I / F speeds of "1 Gbps", so the group ID "A" is assigned to both to indicate that they are in the same group.

[0056] Next, the comparison unit F20 called by the misconnection detection unit M10 performs a process of saving information required for comparing port configuration information for each entry in the LLDP / FDB information (for comparison) T12 / T22 for entries in which the peer ID comparison C124 / C224 is "mismatched" (step F154). Specifically, first, an entry in the port configuration information T30 that has the same value in port C301 as that stored in port C121 / C221 of the entry is searched for, and the value of group IDC304 of the searched entry is saved in the port group IDC125 / C225 of the target entry in the LLDP / FDB information (for comparison) T12 / T22. Next, an entry is searched for that has the same value in the peer ID expected value C122 / C222 as the peer ID current value C123 / C223 in the LLDP / FDB information (for comparison) T12 / T22, and the value of port C121 / C221 of the searched entry is saved in the current value port C126 / C226.

[0057] Finally, a search is made for an entry in the port configuration information T30 that has the same value for port C301 as the current value port C126 / C226 of the LLDP / FDB information (for comparison) T12 / T22, and the value of the group Id D304 of the searched entry is saved in the current value port group ID column C127 / C227 of the target entry in the LLDP / FDB information (for comparison) T12 / T22.

[0058] Next, the comparison unit F20 compares the port group IDC125 / C225 with the current port group IDC127 / C227 for the ports for which the peer ID comparison C124 / C224 of the LLDP / FDB information (for comparison) T12 / T22 is "mismatched" (step F155). If the comparison shows that the two port group ID values ​​are the same (YES in step F156), "Match" is stored in the port group ID comparison C128 / C228 in process F157 (step F157), and the process of F15 is terminated. If the two port group ID values ​​are not the same (NO in step F156), "Mismatch" is stored in the port group ID comparison C128 / C228 (step F158), and the process of F15 is terminated.

[0059] 16 is a flowchart showing the details of the comparison process (step F16) which is the final connection status determination process. The process of step F16 is executed for each entry of the LLDP / FDB information (for comparison) T12 / T22. The following explanation will be given of the contents executed for one target entry.

[0060] After the process starts, the comparison unit F20 called by the misconnection detection unit M10 saves "normal connection" in the final judgment C129 / C229 (step F163) and terminates the process of F16 if either the peer ID comparison C124 / C224 or the port group ID comparison C128 / C228 in the processing target entry of the LLDP / FDB information (for comparison) T12 / T22 shows "match" (YES in step F162).

[0061] If the result is not a "match" (NO in step F162), the process proceeds to step F164. Here, "normal connection" means that after the replacement of the Layer 2 switch S10, the same device as before the replacement is connected to the port indicated in the entry being processed, or a different device is connected but the device was connected to a port belonging to the same group ID before the replacement of the Layer 2 switch S10, so there is no problem with the connection.

[0062] Next, if the peer ID comparison C124 / C224 of the entry to be processed is not "unconnected" (NO in step F164), "misconnection" is stored in the final decision C129 / C229 (step F166), and the process of F16 is terminated. If it is "unconnected" (YES in step F164), the process proceeds to branch F165.

[0063] Here, "misconnection" means that after Layer 2 switch S10 is replaced, a different device is connected to the port indicated in the entry being processed, and that device was connected to a port belonging to a different group ID before Layer 2 switch S10 was replaced, and therefore a device that should not be connected to this port is connected.

[0064] Next, it is checked whether the value of port C121 / C221 of the entry to be processed is saved in the current value port C126 / C127 of another port, and if it is saved, and the port group ID comparison C128 / C228 of that port is "matched" (YES in step F165), "not targeted (moved)" is saved in the final decision column C129 / C229, and the processing of F16 is terminated (step F167). Otherwise (NO in step F165), "misconnection (not connected)" is saved in the final decision column C129 / C229, and the processing of F16 is terminated (step F168).

[0065] Here, "not targeted (moved)" means that the port indicated in the entry being processed is not connected to anything after replacing the Layer 2 switch S10, but the device that was connected to this port before the replacement has been reconnected to another port that belongs to the same group ID, so there is no problem. Also, "misconnected (not connected)" means that the port indicated in the entry being processed is not connected to anything after replacing the Layer 2 switch S10, and the device that was connected to this port before the replacement is not connected to any other port.

[0066] Through the series of processes described above, the state of cable reconnection after replacement of the Layer 2 switch S10 and the presence or absence of any misconnected ports that require reconnection are determined.

[0067] Returning to the flowchart of Fig. 12, the misconnection detection unit M10 notifies the user I / F unit M20 of the presence or absence of a misconnection of the cable detected in the processing up to step F16 (step F124). Specifically, the presence or absence of a misconnection of the final judgment C129 / C229 of the LLDP / FDB information (for comparison) T12 / T22 is notified by means of syslog / mail / Web-UI or the like. The notified information is used, for example, by an administrator to reconnect the cable based on the notification.

[0068] As an example of the Web-UI, an example of a user I / F screen is shown in Fig. 17. For the target layer 2 switch S10, a table D20 for port connection confirmation is displayed. In the table, port D200 displays the port C120 / C220 of LLDP / FDB information (for comparison) T12 / T22, group D201 displays the group ID of group ID C304 of port configuration information T30, judgment D202 displays the judgment of final judgment C129 / C229, previous port D203 displays the port C120 / C220 if the peer ID comparison C124 / C224 of LLDP / FDB information (for comparison) T12 / T22 is "matched", and the port of current value port C126 / C226 if it is "mismatched", and D204 displays an appropriate explanation.

[0069] After step F124, it is determined whether to continue or end the cable misconnection determination process (step F125). Specifically, if all of the final determination columns C129 / C229 of the LLDP / FDB information (for comparison) T12 / T22 are "normal connection" or "out of target (moved)" (which means that no misconnection has occurred), or if the user I / F unit M20 receives an end instruction from the user, the process F12 is ended. If otherwise, in step F125, the process returns to the current value collection process and the peer ID comparison process F14 and is repeated.

[0070] In the first embodiment, the target is a layer 2 switch, but the present invention can be applied to a layer 3 switch or a router in the same manner. In that case, it is easy to imagine that ARP information or routing information can be used as information indicating the connection state of the opposite terminal or device.

[0071] As described above, according to the first embodiment, when a device such as a layer 2 switch is replaced, it is possible to detect the occurrence of a cable misconnection before and after the replacement. Furthermore, by using port configuration information of a layer 2 switch or the like in combination, even if there is a misconnection, it is determined to be a normal connection as long as it does not affect the operation of the system, thereby minimizing the work of reconnecting cables due to a misconnection. EXAMPLES

[0072] In the second embodiment, a configuration is described in which a misconnection detection unit is included in a Layer 2 switch, and when a cable is reconnected due to replacement of a Layer 2 switch, etc., a misconnection to a port that does not affect communication because it has the same port configuration is tolerated, while a misconnection that affects communication and causes actual damage is detected.

[0073] 18 is an explanatory diagram showing a configuration example of a layer 2 switch S60 in the embodiment 2. Note that the same components as those in the layer 2 switch S10 shown in the embodiment 1 are denoted by the same reference numerals.

[0074] The configuration of the layer 2 switch S60 in Figure 18 is different from that of the layer 2 switch S10 shown in the first embodiment in that a misconnection detection unit M50, which is substantially the same program as the misconnection detection unit M10, is stored in the memory 105 and executed by the CPU 103, and further includes an auxiliary memory control unit 107 and an auxiliary memory medium 108.

[0075] The misconnection detection unit M50 includes the same processing units and tables as the misconnection detection unit M10 shown in Fig. 3. These are not shown in the figure, and in the following description, the reference numerals shown in Fig. 3 will be used for reference.

[0076] The auxiliary storage medium 108 is a removable non-volatile storage medium, and the auxiliary storage control unit 107 controls the reading and writing of data to the auxiliary storage medium 108. The auxiliary storage medium 108 is used to transfer information required for erroneous connection detection to the replaced device when the layer 2 switch S60 is replaced with another device, and is intended to be replaced with the replaced device.

[0077] Fig. 21 is a flowchart showing the overall operation of misconnection detection in the misconnection detection unit M50. This is basically almost the same as the processing in the flowchart of Fig. 12 explained in the first embodiment, so only the parts that differ from the flowchart of Fig. 12 will be explained below. In Fig. 21, elements that perform the same processing as in the flowchart of Fig. 12 are given the same reference numerals as in Fig. 12, and detailed explanations of their operations will be omitted.

[0078] First, as a first step after starting up the Layer 2 switch S60, the misconnection detection unit M50 checks whether LLDP / FDB information is stored in the auxiliary storage medium 108, and if not stored, proceeds to the processing of step F122 and subsequent steps, and if stored, proceeds to the processing of step F214 and subsequent steps (step F212). This processing is for determining, after starting up the Layer 2 switch S60, whether the current startup is a restart after replacing the Layer 2 switch S60 or the first startup after the system has been constructed. Using the presence or absence of LLDP / FDB information in the auxiliary storage medium 108 for this determination is one example, and other operation identification information may be stored in the auxiliary storage medium and used for the determination.

[0079] If it is found in step F212 that the LLDP / FDB information is not stored in the auxiliary storage medium 108, the processes of steps F122 and F13 are executed. These processes are basically the same as those described in the flowchart of Fig. 12. The difference is that in step F13, the device information collection unit F10 collects information from the layer 2 switch S10 using a protocol such as SNMP in the first embodiment, whereas in the second embodiment, it directly refers to information in the layer 2 switch S60 (the same applies to the subsequent processes). Alternatively, the information may be acquired from the control unit M40 by using SNMP or the like in local communication using a loopback interface in the layer 2 switch S60.

[0080] Next, the contents of the LLDP / FDB information (expected values) T10 / T20 are stored in the auxiliary storage medium 108, and the process returns to step F122 (step F213). If the LLDP / FDB information is stored in the auxiliary storage medium 108 in step F212, the LLDP / FDB information is first read from the auxiliary storage medium 108, and is stored in the LLDP / FDB information (expected values) T10 / T20 (step F214).

[0081] Next, the process proceeds to step F14 and subsequent steps to detect the connection error. The processes from step F14 onwards are the same as those described in the flowchart of FIG.

[0082] By the above processing, misconnection detection can be realized by the Layer 2 switch S60 alone. If the misconnection detection unit M50 performs misconnection detection not only for its own device but also for other Layer 2 switches, the processing for other Layer 2 switches can be performed by the operation shown in the flowchart of FIG.

[0083] Although the second embodiment is directed to a layer 2 switch, it can be applied to a layer 3 switch or a router in the same manner. In that case, it is easy to imagine that ARP information or routing information can be used as information indicating the connection state of the opposite terminal or device.

[0084] According to the second embodiment, even in a small-scale system where it is difficult to prepare a misconnection detection device that serves as an external server device, it is possible to perform misconnection detection using a single network device such as a Layer 2 switch, while allowing misconnections that do not affect the operation of the system.

[0085] In the above embodiment, in the replacement work of network equipment, if connecting to any of a plurality of ports will not affect communication, etc., connecting to a port different from the previous port is flexible enough not to be treated as an erroneous connection.

[0086] According to the above embodiment, it is possible to suppress the detection of erroneous connections that do not affect the operation of the network system during the replacement of network devices. This has the effect of reducing unnecessary reconnection of cables that have been erroneously connected after the replacement of network devices, and of making the replacement work more efficient. In particular, the effect is significant in the case of access side switches that connect terminals, since most of the ports generally allow erroneous connections that do not affect the operation. EXAMPLES

[0087] In the third embodiment, a configuration is provided in which a misconnection detection unit is provided within a network management server as in the first embodiment, or within a Layer 2 switch as in the second embodiment, and a device, such as a non-intelligent Layer 2 switch or a repeater hub, from which connection information cannot be obtained by LLDP or which is not managed, is present between the opposing terminal or device.

[0088] This section explains an example of how, when a cable is reconnected due to the replacement of a Layer 2 switch, etc., incorrect connections to ports that do not affect communication because they have the same port configuration are tolerated, while incorrect connections that affect communication and cause actual harm are detected and the correct connection destination is notified.

[0089] If a non-intelligent layer 2 switch or a repeater hub that does not support LLDP is inserted between the layer 2 switch and the terminal, the layer 2 switch cannot recognize the presence of them by LLDP. Therefore, even if a misconnection occurs when reconnecting by replacing the layer 2 switch, it cannot be detected directly. In the third embodiment, even in such a situation, the possibility of a misconnection can be estimated using information on the terminal connected beyond the LLDP-incompatible switch, and the network administrator can be notified.

[0090] 22 is an explanatory diagram showing a configuration example of a network system in the third embodiment of the present invention. Note that the same components as those in the configuration example of the network system shown in the first or second embodiment are denoted by the same reference numerals.

[0091] 22, a network management server S50 is connected to a Layer 2 switch S10, which is a target for detecting misconnections, via a network N10. The Layer 2 switch S10 has ports P12 to P15, which are connected to each other via cables such as copper wires or optical fibers.

[0092] Port P12 is connected to the opposite terminal A (U10), the opposite terminal B (U20), and the opposite terminal C (U30) via a layer 2 switch or a repeater hub (H10). Port P13 is connected to the opposite terminal D (U40) and the opposite terminal E (U50) via a layer 2 switch or a repeater hub (H20). Port P14 is connected to the opposite terminal F (U60) and the opposite terminal G (U70) via a layer 2 switch or a repeater hub (H30). Port P15 is connected to the opposite terminal H (U80) via a layer 2 switch or a repeater hub (H40).

[0093] The configuration of the layer 2 switch S10 in the third embodiment is the same as that in the first or second embodiment, and therefore a description thereof will be omitted.

[0094] The network configuration in Figure 23 shows that in the configuration in Figure 22, layer 2 switch S10 has been replaced, and subsequent cable reconnection has resulted in port P12 being connected to a layer 2 switch or repeater hub (H20), port P13 being connected to a layer 2 switch or repeater hub (H10), port P14 being connected to a layer 2 switch or repeater hub (H40), and port P15 being connected to a layer 2 switch or repeater hub (H30).

[0095] It also shows that the opposite terminal G (U70) that was connected to the layer 2 switch or repeater hub (H30) has been moved to the layer 2 switch or repeater hub (H40). This movement assumes a situation in which the opposite terminal G (U70) is reconnected to a different layer 2 switch or repeater hub while the layer 2 switch S10 is being replaced.

[0096] Because communication will be interrupted while the Layer 2 switch S10 is being replaced, this is to take into consideration the possibility that a user using a terminal during that time may try to resolve the situation by reconnecting the terminal to another Layer 2 switch or repeater hub.

[0097] An example of an operation for detecting the occurrence of a misconnection will be described below, taking as an example a case where a misconnection as shown in FIG. 23 occurs due to a reconnection operation after replacing a device in the system configuration of FIG.

[0098] Fig. 27 is a flowchart showing the overall operation of misconnection detection by the misconnection detection unit M10. This is basically almost the same as the processing in the flowchart of Fig. 12 explained in the first embodiment, except that step F28 has been added between step F16 and step F124. Therefore, only the part F28 that differs from the flowchart of Fig. 12 will be explained below. In Fig. 27, elements that perform the same processing as in the flowchart of Fig. 12 are given the same reference numerals as in Fig. 12, and detailed explanations of their operations will be omitted.

[0099] The processes up to step F16 are the same as those explained in the flowchart of Fig. 12 in the first embodiment, but when a state is created in which multiple terminals appear to be directly connected to one port of the layer 2 switch S10 by going through a layer 2 switch or a repeater hub, multiple peer IDs (MAC addresses) are stored in the peer ID column of each table of the FDB information (expected value) T20, the FDB information (current value) T21, and the FDB information (for comparison) T22. In that case, the set is treated as the peer ID.

[0100] FIG. 24 shows an example of FDB information (expected value) T20 including information collected in step F13 before the replacement of the layer 2 switch S10 (network configuration of FIG. 22).

[0101] FIG. 25 shows an example of FDB information (current values) T21 including information collected in step F14 after the replacement of the layer 2 switch S10 (network configuration of FIG. 23).

[0102] FIG. 28 is a flow chart showing the details of the process of comparing multiple candidates (step F28) added in the third embodiment. The process of step F28 is executed for each entry of FDB information (for comparison) T22 in Fig. 26. The FDB information (for comparison) in Fig. 26 is obtained by adding columns C261 to C266 to the FDB information (for comparison) T22 in Fig. 10. Also, values ​​have already been stored in columns C220 to C229 of FDB information (for comparison) T22 by the processes of steps F14 and F15 in the flowchart in Fig. 27 before the start of step F28. The following explanation will explain the contents executed for one target entry.

[0103] When the processing of step F28 starts, first, the comparison unit F20 called by the misconnection detection unit M10 terminates the processing of F28 if the final judgment C229 for the entry to be processed in the FDB information (for comparison) T22 is not “misconnection” (NO in step F282).

[0104] If the result is "misconnection" (YES in step F282), the process proceeds to step F283. Here, "misconnection" means that after the replacement of the Layer 2 switch S10, a set of peer IDs different from that before the replacement is connected to the port indicated in the entry being processed, and that set of peer IDs is a set of peer IDs that were connected to a port belonging to a group ID different from that before the replacement of the Layer 2 switch S10, so that there is a problem with the connection.

[0105] Next, in step F283, the number of matching IDs in the set of matching ID current values ​​C223 of the target entry is counted against the set of matching ID expected values ​​C222 of each entry in the FDB information (for comparison) T22, and the count is stored in the matching ID counts C261 to C264 corresponding to the ports C221 of each entry, and the process proceeds to step F284.

[0106] To explain a specific example with reference to FIG. 26, for example, in processing the first row (entry where port C221 is P12), the peer ID expected value C222 in the first row is the set "U10, U20, U30" and the peer ID current value C223 in the first row is the set "U40, U50", so there are no matching elements in both sets and the peer ID match count (P12) C261 in the first row is 0.

[0107] The peer ID expected value C222 in the second row (entry where port C221 is P13) is the set "U40, U50", and the peer ID current value C223 in the first row is the set "U40, U50", so two elements match in both sets and the peer ID match count (P13) C262 in the first row is 2. By repeating the same comparison process, the values ​​of the peer ID match count (P14) C263 in the first row and the peer ID match count (P15) C264 in the first row each become 0.

[0108] Next, in step F284, the port with the greatest number of peer ID match counts C261 to C264 is stored in the port with the greatest number of matches C265. If there are multiple ports with the greatest number of matches, multiple ports are stored and the process proceeds to step F285. For example, in the process for the first row (row where port C221 is P12), the greatest value of the peer ID match counts C261 to C264 is 2, which is stored in the peer ID match count (P13) C262, so P13 is stored in the port with the greatest number of matches C265.

[0109] In processing the third row (the row where port C221 is P14), the largest value among the peer ID match counts C261 to C264 is 1, which is stored in peer ID match count (P14) C263 and peer ID match count (P15) C264, so P14 and P15 are stored in the port with the most matches C265.

[0110] The above-described processing from step F282 to step F284 is executed for all entries of the FDB information (for comparison) T22 before proceeding to processing from step F285 onwards.

[0111] Next, in step F285, if there is one port stored in the most-matched port C265 (YES in step F285), the process of F28 is terminated.

[0112] If there are multiple ports (NO in step F285), the process proceeds to step F286.

[0113] In steps F286 and F287, from the set of ports stored in the most-matched port C265, the ports excluding those stored as single ports in the most-matched port C265 of other entries in the FDB information (for comparison) T22 are stored in the remaining matched port C266.

[0114] In the example of Figure 26, the third row (entry where port C221 is P14) includes multiple ports P14 and P15 in port C265 with the most matches, so it is the subject of processing in step F286. Of these, P14 is excluded because it is stored as a single port in port C265 with the most matches in the fourth row (entry where port C221 is P15), and as a result, in step F287, only P15 is stored in remaining matched port C266 in the third row.

[0115] Returning to the flowchart of Fig. 27, the process proceeds to step F124 and onwards to proceed with the misconnection detection process. The processes from step F124 onwards are the same as those described in the flowchart of Fig. 12.

[0116] FIG. 29 shows an example of a user I / F screen as an example of a Web-UI that displays the detection result of a misconnection in the third embodiment.

[0117] A port connection confirmation table D20 is displayed for the target Layer 2 switch S10. Each row of table D20 displays information corresponding to the contents of each entry of FDB information (for comparison) T22.

[0118] In each row, port D200 in the table displays the port of port C221 of FDB information (for comparison) T22. Group D201 displays the group ID of port group ID C225 of FDB information (for comparison) T22. Judgment D202 displays the judgment of final judgment C229.

[0119] In the previous port D203, if the peer ID comparison C224 in the FDB information (for comparison) T22 is "matched", the port of port C221 is displayed, and if it is "mismatched", if there is one port in the most matched port C265, that port is displayed, and if there are multiple ports in C265, the remaining matched port C266 is displayed. An appropriate explanation is displayed in D204.

[0120] Here, if the current port C226 is empty, the word "(estimated)" is further added after the port of the previous port D203. This is because the current port C226 being empty means that when the current port C226 was obtained in step F154 (FIG. 15), no entry was found that had a port set in the expected peer ID C222 that perfectly matches the current peer ID C223, and this is to inform the network administrator that the port displayed in the previous port D203 is an estimated value.

[0121] 26, port P12 of device S10 has C224 "mismatched", and there is one port stored in C265, P13, and C226 is not empty, so it displays the value "P13" in C265. Port P13 of device S10 also has C224 "mismatched", and there is one port stored in C265, P12, and C226 is not empty, so it displays the value "P12" in C265.

[0122] For port P14 of device S10, C224 is "mismatched", and there are two ports stored in C265, P14 and P15, and C226 is empty, so "P15 (estimated)" is displayed with "(estimated)" added to the value of C266. For port P15 of device S10, C224 is "mismatched", and there is only one port stored in C265, P14, and C226 is empty, so "P14 (estimated)" is displayed with "(estimated)" added to the value of C265.

[0123] In the network configurations of Figures 22 and 23 described as the third embodiment, there is no opposing device (a Layer 2 switch having LLDP function other than Layer 2 switch S10) connected to Layer 2 switch S10, so the description is omitted. However, if the opposing device were also connected, the judgment result based on LLDP information (for comparison) T12 would also be included and displayed in table D20 by processing similar to that for displaying the example screen of Figure 17 in the first embodiment.

[0124] Through the above processing, erroneous connection detection is realized even when there is a device between the opposite terminal or device, such as a non-intelligent Layer 2 switch or repeater hub, from which connection information cannot be obtained by LLDP.

[0125] In the above embodiment, in the replacement work of network equipment, if connecting to any of a plurality of ports will not affect communication, etc., connecting to a port different from the previous port is flexible enough not to be treated as an erroneous connection.

[0126] According to the above embodiment, it is possible to suppress the detection of erroneous connections that do not affect the operation of the network system during the replacement of network devices. This has the effect of reducing unnecessary reconnection of cables that have been erroneously connected after the replacement of network devices, and of making the replacement work more efficient. In particular, the effect is significant in the case of access side switches that connect terminals, since most of the ports generally allow erroneous connections that do not affect the operation.

[0127] According to the above embodiment, in the replacement of network equipment, even if there is an unmanaged Layer 2 switch between the connection with the opposite terminal or device, the detection of a misconnection is realized. Therefore, there is an effect that unnecessary reconnection of a cable that has been misconnected after the replacement of the network equipment is reduced, and the replacement work can be carried out efficiently. In particular, in the access side switch that connects the terminal, generally inexpensive non-intelligent Layer 2 switches that do not care about the cable connection form are often used, and the detection of a misconnection is realized even in the replacement of this upper switch, and the effect is great. [Explanation of symbols]

[0128] S10, S60 Layer 2 Switch S20 Opposite device A S30 Opposite device B S40 Opposite device C S50 Network Management Server U10 Opposite terminal A U20 Opposite terminal B U30 Opposite terminal C U40 Opposite terminal D U50 Opposite terminal E U60 Opposite terminal F U70 Opposite terminal G U80 Opposite terminal H H10, H20, H30, H40 Layer 2 Switch / Repeater Hub P11, P12, P13, P14, P15, P16, P17 ports M10, M50 Misconnection Detection Unit M20, M30 User I / F section F10 Equipment Information Collection Unit F20 comparison section F30 Grouping section T10 LLDP information (expected value) T11 LLDP information (current value) T12 LLDP information (for comparison) T20 FDB Information (Expected Value) T21 FDB information (current value) T22 FDB information (for comparison) T30 Port Configuration Information

Claims

1. A network device having multiple ports connected to multiple counterpart devices by cables A network management server connected via a network and having a misconnection detection unit, The erroneous connection detection unit is storing expected value information associating the plurality of ports with the corresponding identification information of the plurality of opposed devices in a state before the network device is replaced, current value information associating the plurality of ports with the corresponding identification information of the plurality of opposed devices in a state after the network device is replaced, and port configuration information associating the plurality of ports with group identification information grouped according to the configuration of the ports; When the cable is reconnected due to replacement of the network device, comparing the opposing identification information of the current value information with the opposing identification information of the expected value information; referring to the port configuration information, comparing the group identification information before the replacement of the network device with the group identification information after the replacement of the network device; determining whether or not the cable is misconnected based on a result of the comparison; The erroneous connection detection unit is As a result of the comparison, determining that the cable is normally connected when the counterpart identification information of the expected value information and the counterpart identification information of the current value information match; The erroneous connection detection unit is As a result of the comparison, determining that the connection of the cable is normal when the counterpart identification information of the expected value information and the counterpart identification information of the current value information do not match, and the group identification information before the replacement of the network device and the group identification information after the replacement of the network device match; The erroneous connection detection unit is As a result of the comparison, determining that the cable is misconnected when the counterpart identification information of the expected value information and the counterpart identification information of the current value information do not match and when the group identification information before the network device is replaced and the group identification information after the network device is replaced do not match; The erroneous connection detection unit is As a result of the comparison, A network management server characterized in that it determines that the cable is not connected when the opposing identification information of the expected value information and the opposing identification information of the current value information do not match and when the opposing identification information of the current value information does not exist.

2. 2. The network management server according to claim 1, wherein the expected value information and the current value information are composed of FDB information and LLDP information, respectively.

3. The network management server includes:

2. The network management server according to claim 1, further comprising a user interface unit for notifying the user of the presence or absence of a misconnection of the cable.

4. A network device having a plurality of ports connected to a plurality of counterpart devices by cables, The network device comprises: An erroneous connection detection unit; A removable auxiliary storage medium, The auxiliary storage medium is storing expected value information in which the plurality of ports and the corresponding identification information of the plurality of corresponding devices are associated with each other in a state before the network device is replaced; The erroneous connection detection unit is storing current value information in which the plurality of ports are associated with the corresponding identification information of the plurality of opposed devices in a state after the replacement of the network device, and port configuration information in which the plurality of ports are associated with group identification information grouped according to a configuration of the ports, When the cable is reconnected due to replacement of the network device, the auxiliary storage medium is replaced from the network device before replacement to the network device after replacement; The erroneous connection detection unit is comparing the counter identification information of the current value information with the counter identification information of the expected value information stored in the auxiliary storage medium; referring to the port configuration information, comparing the group identification information before the replacement of the network device with the group identification information after the replacement of the network device; determining whether or not the cable is misconnected based on a result of the comparison; The erroneous connection detection unit is As a result of the comparison, determining that the cable is normally connected when the counterpart identification information of the expected value information and the counterpart identification information of the current value information match; The erroneous connection detection unit is As a result of the comparison, determining that the connection of the cable is normal when the counterpart identification information of the expected value information and the counterpart identification information of the current value information do not match, and the group identification information before the replacement of the network device and the group identification information after the replacement of the network device match; The erroneous connection detection unit is As a result of the comparison, determining that the cable is misconnected when the counterpart identification information of the expected value information and the counterpart identification information of the current value information do not match and when the group identification information before the network device is replaced and the group identification information after the network device is replaced do not match; The erroneous connection detection unit is As a result of the comparison, A network device characterized in that when the opposing identification information of the expected value information and the opposing identification information of the current value information do not match and the opposing identification information of the current value information does not exist, the network device determines that the cable is not connected.

5. A misconnection detection program stored in a network management server connected via a network to a network device having a plurality of ports connected to a plurality of opposing devices by cables, The erroneous connection detection program is a process of storing expected value information associating the plurality of ports with the corresponding identification information of the plurality of opposed devices in a state before the network device is replaced, current value information associating the plurality of ports with the corresponding identification information of the plurality of opposed devices in a state after the network device is replaced, and port configuration information associating the plurality of ports with group identification information grouped according to a configuration of the ports; When the cable is reconnected due to replacement of the network device, A process of comparing the opposing identification information of the current value information with the opposing identification information of the expected value information; a process of comparing the group identification information before the replacement of the network device with the group identification information after the replacement of the network device by referring to the port configuration information; determining whether or not the cable is misconnected based on a result of the comparison; to be executed by a computer; The erroneous connection detection program is As a result of the comparison, determining that the cable is normally connected when the counterpart identification information of the expected value information and the counterpart identification information of the current value information match; The erroneous connection detection program is As a result of the comparison, determining that the connection of the cable is normal when the counterpart identification information of the expected value information and the counterpart identification information of the current value information do not match, and the group identification information before the replacement of the network device and the group identification information after the replacement of the network device match; The erroneous connection detection program is As a result of the comparison, determining that the cable is misconnected when the counterpart identification information of the expected value information and the counterpart identification information of the current value information do not match and when the group identification information before the network device is replaced and the group identification information after the network device is replaced do not match; The erroneous connection detection program is As a result of the comparison, A misconnection detection program characterized by determining that the cable is not connected when the opposing identification information of the expected value information and the opposing identification information of the current value information do not match and when the opposing identification information of the current value information does not exist.

6. 6. The misconnection detection program according to claim 5, wherein the expected value information and the current value information are composed of FDB information and LLDP information, respectively.

7. The erroneous connection detection program is 6. The misconnection detection program according to claim 5, further comprising a process for notifying the user of the presence or absence of a misconnection of the cable.

8. At least one of the plurality of ports is connected to the plurality of counterpart devices by the cable via another network device, The erroneous connection detection unit is When the cable is reconnected due to replacement of the network device, comparing the set of opposing identification information of the current value information with the set of opposing identification information of the expected value information; 2. The network management server according to claim 1, wherein the presence or absence of a misconnection of the cable is determined based on a result of the comparison.

9. The erroneous connection detection unit is When comparing the set of opposite identification information of the current value information with the set of opposite identification information of the expected value information, Counting the number of matches of the counterpart identification information in the expected value information for each of the ports; The port having the largest number of matches and not selected by any other port is presumed to be the correct port; 9. The network management server according to claim 8, wherein the presence or absence of a misconnection of the cable is determined based on a result of the comparison.

10. At least one of the plurality of ports is connected to the plurality of counterpart devices by the cable via another network device, The erroneous connection detection program is When the cable is reconnected due to replacement of the network device, comparing the set of opposing identification information of the current value information with the set of opposing identification information of the expected value information; 6. The misconnection detection program according to claim 5, wherein the presence or absence of a misconnection of the cable is determined based on a result of the comparison.

11. The erroneous connection detection program is When comparing the set of opposite identification information of the current value information with the set of opposite identification information of the expected value information, Counting the number of matches of the counterpart identification information in the expected value information for each of the ports; The port having the largest number of matches and not selected by any other port is presumed to be the correct port; 11. The misconnection detection program according to claim 10, wherein the presence or absence of a misconnection of the cable is determined based on a result of the comparison.

Images