JPH06224915A - Network management system - Google Patents

Abstract

PURPOSE:To eliminate the need for setting revision of setting information specific to each equipment newly with respect to a network equipment having no direct communication function with the network management terminal equipment even when the connection configuration of the network equipment is revised. CONSTITUTION:The system is made up of an SNMP manager 2, master HUB 31, 32, and slave HUB 41, 42, 43, 44 and the master HUB executes in behalf the communication of management information between the slave HUB and the SNP manager. The slave HUB has a down-load server 6 in a network having an identification in the network and network management information corresponding to the identification number. The master HUB reads the identification number of the slave HUB whose communication is to be substituted and receives the network management information corresponding to the identification from the down-load server 6 through its transfer.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network management system for managing network equipment such as HUB, bridge and modem.

[0002]

2. Description of the Related Art Generally, in networks such as LAN and WAN, SNMP (Simple Network M) is used.
The network device is managed by using a network management protocol such as the management protocol). The target of management is MIB (Manag)
A management object called “element Information Base” is used, and setting information (device name, installation location, administrator in charge, etc.) unique to each device, and event counting information (number of packets received, number of error occurrences, etc.)
And information such as real-time status information (such as the link status of HUB ports).

For example, when a network device such as a HUB is to be managed, the HUB must have a managed function such as execution of the SNMP protocol and holding and updating of the managed object database in addition to the repeater function that the HUB originally has. I won't. Therefore, it is indispensable to mount a CPU, a LAN controller, an IC such as a memory, and software, which are unnecessary only with the repeater function. Therefore, a HUB having a managed function is more expensive than a HUB having no managed function.

Therefore, when a plurality of HUBs are used, not all HUBs are provided with managed functions, but one HUB equipped with an SNMP protocol function and a management object database holding / updating function as shown in FIG. HU
B3 (hereinafter referred to as a master HUB) and at least one HUB4 (hereinafter referred to as a slave HUB) that does not have these functions are connected by a dedicated bus 5 or the like to obtain an SNMP.
A method is adopted in which the master HUB 3 acts on behalf of the manager 2 in response to a read request for reading management information from the slave HUB 4. For example,
When the SNMP manager 2 sends the read request packet of the state of the designated port of the designated slave HUB4, the master HUB3 receives this and reads the state of the designated port of the designated slave HUB4 via the bus 5. , Returns the status to the SNMP manager 2.

According to this method, only one master HUB3 is equipped with a CPU, a LAN controller, an IC such as a memory, and software necessary for storing and updating SNMP communication and management objects. Since the slave HUB 4 does not have to be mounted, there is an advantage that the cost of the entire system can be reduced. Moreover, since the number of slave HUBs 4 connected to the master HUB 3 can be made variable, there is an advantage that the user can flexibly change the connection configuration of these network devices.

By the way, in addition to real-time information such as port status, the management target includes information unique to each device set by the user. For example, in MIB-II defined in RFC1213, sysContact (name of device administrator, contact method, etc.), sysNa
me (device management name), sysLocation
Objects such as (device installation location) are defined, and a MIB uniquely specified by the manufacturer such as the purchase date and installation date of the device may be considered. The device-specific information set by these users is requested to be set and managed not only in the master HUB but also in the slave HUB.

[0007] However, in the conventional system in which the master HUB 3 substitutes and holds the user setting information peculiar to these devices for the slave HUB 4, and the master HUB 3 responds to the inquiry from the SNMP manager 2 by acting as a slave, HUB4 is a master H
When the connection configuration of these network devices is changed by disconnecting from the UB3 and newly connecting to another master HUB3, there is a problem that the user has to set new information again. Further, if the slave HUB 4 is configured to hold the information peculiar to these devices, a non-volatile memory or the like for that is required, which is expensive.

[0008]

[Problems to be Solved by the Invention] Conventional master HUB
The first type network device having a direct communication function with the network management terminal like the above, and the second type which does not have the direct communication function with the network management terminal like the slave HUB.
In a system in which a first type network device acts as a proxy for the communication between the second type network device and the network management terminal by connecting the second type network device from the first type network device, When the connection configuration of these network devices is changed by disconnecting or newly connecting, the user has to newly set the device-specific setting information for the second type network device. there were.

The present invention has been made in view of the above circumstances, and an object thereof is to provide a direct communication function with a network management terminal even when the connection configuration of network equipment is changed as described above. It is to provide a network management system in which the user does not have to newly set the setting information unique to each device for network devices that do not have the.

[0010]

In the network management system of the present invention, in order to solve the above-mentioned problems,
As shown in FIG. 1, a network management terminal such as an SNMP manager 2, first-type network equipment such as master HUBs 31 and 32 having direct communication means with the network management terminal, and the network management terminal. Slave HUB41 without direct communication means of
In a system including a second type network device such as 42, 43 and 44, the first type network device acts as a proxy for communication of management information between the network management terminal and the second type network device. This kind of network device is provided with a means for holding an identification number in the network, and a download server 6 that holds network management information corresponding to the identification number is provided in the network.
The kind of network device is provided with means for reading and holding the identification number of the second kind of network device which should perform the communication on behalf of, and means for transferring and holding the network management information corresponding to the identification number from the download server 6. It is characterized by that.

[0011]

Since the network management system of the present invention is configured as described above, a second type network device that does not have a direct communication function with the network management terminal can be used.
When the connection configuration of these network devices is changed by disconnecting from or newly connecting to the network management terminal of the first type network device that has a direct communication function, the first type network device does not communicate. Read the identification number of the second type of network device that should act on your behalf,
Since the network management information corresponding to the identification number is transferred from the download server 6 and retained, it is not necessary for the user to newly set the device-specific setting information set by the user.

[0012]

1 is a block diagram of a network management system according to the present invention. 1 is a LAN wiring, for example, I
It is composed of Ethernet that conforms to the EEE802.3 standard. 2 is an SNMP manager, SNM
It is a terminal having a network management function conforming to P. 31 and 32 are HUBs having a function of directly communicating with the SNMP manager 2 (hereinafter referred to as a master HUB), 41
Numerals 44 to 44 are HUBs (hereinafter referred to as slave HUBs) that do not have the function of directly communicating with the SNMP manager, and all of them are twisted pair LANs compliant with 10Base-T.
Has a function as a repeater. 5 is master H
UB31 and 32 and slave HUB41, 42 and 4
This is a dedicated bus for connecting the three and fourty-four. Also, 6
Is a download server that holds the user setting data of the slave HUBs 41 to 44.

FIG. 2 is a block diagram showing the internal structure of the master HUB 31 according to the present invention. Master HUB31
Is a communication processing unit 311 for communicating with the LAN wiring 1, a managed object management unit 312 for storing and updating the MIB, and 1
Ports 313 (1) to 313 (n) for 0Base-T
And a bus interface unit 31 connected to the repeater unit 314 for repeating packets between these ports and the dedicated bus 5 for information communication with the slave HUBs 41 and 42.
5 and an ID read / hold unit 316.

Here, the communication processing unit 311 includes a CPU and an LA.
The N controller, memory, LAN driver, and other hardware and software that executes a communication protocol are used to perform communication processing by the SNMP manager 2 by the SNMP and communication processing by the download server 6 by the file transfer protocol (TFTP). The ID reading / holding means 316 includes a CPU, a memory and software, and via the bus interface unit 315, ID setting / holding means 416 of slave HUBs 41 and 42, which will be described later,
The ID number held by 426 is read and held. The repeater unit 314 includes hardware such as a repeater IC and a LAN driver. The repeater IC is, for example, a National Semiconductor.
r DP83950 and AT & T Microele
Am79C980 manufactured by ctronics or the like is used. These repeater ICs have a function of detecting a link state of each port and occurrence of various errors, in addition to a function of repeating a packet between ports. The managed object management unit 312 includes hardware such as a memory and a CPU, and software, and counts the number of received packets in the communication processing unit 311, reads the current state in the repeater unit 314, records and counts error events, and the like. And the repeater unit 414 of the slave HUBs 41 and 42, which will be described later, via the bus interface unit 315.
The current state in 424 is read, error events are recorded and counted, and the management object (MIB) is held and updated. The communication processing unit 311, the ID reading / holding unit 316, the memory in the managed object management unit 312, the hardware such as the CPU, and the software may be shared or integrated.

FIG. 3 shows a slave HUB 41, according to the present invention.
It is a block diagram which shows the internal structure of 42. Slave HU
B41 is the port 413 (1) for 10Base-T
413 (n), a repeater unit 414 that repeats packets between these ports, a bus interface unit 415 connected to the dedicated bus 5 for information communication with the master HUB 31, and an ID setting holding unit 416.
Here, the repeater unit 414 is configured with the same hardware as the repeater unit 314 of the master HUB 31. I
The D setting holding means 416 is composed of a DIP switch or the like, and a user can set slave HUBs 41 to 4 in the network.
A unique ID number can be set in each of the four. The master HUB 32 has the same configuration as the master HUB 31. In addition, slave HUB42,4
Reference numerals 3 and 44 have the same configuration as the slave HUB 41.

Next, the operation of this embodiment will be described.
The user selects slave HUBs 41, 42 and 43, 44
When connecting to the master HUBs 31 and 32, a unique ID is set by the ID setting holding means of each slave HUB. Next, a unique setting item corresponding to each ID, for example, sysDescr (device notation), sy
sContact (device name, contact method, etc.), sysName (device management name),
Items such as sysLocation (device installation location) are set, and a setting data file as shown in Table 1 is stored on the download server 6.

[0017]

[Table 1]

The master HUB 31 is connected to the slave HUB 41 by the ID reading and holding means 316.
The ID numbers (# 1 and # 2, respectively) held in the ID setting holding means 416 and 426 of 42 are read to detect that the HUBs of # 1 and # 2 are newly connected. Next, the communication processing unit 311 sends a download request packet of the setting data of # 1 and # 2 to the download server 6 by using the TFTP protocol, and downloads. The downloaded setting data is held in the managed object management unit 312. Similarly,
Master HUB 32 is connected to slave HUB 4
The ID numbers of 3 and 44 (# 3 and # 4, respectively) are read, the setting data of # 3 and # 4 are downloaded from the download server 6, and the managed object management unit 322 is executed.
Hold in. For example, the master HUB 31 receives the SNMP manager 2's sysCo of the HUB having the ID number # 1.
When the read request packet of ntact is received, the master HUB 31 reads the # 1 sysContact held by the managed object management unit 312, and S
Respond to NMP manager 2.

Next, the operation when the user disconnects the slave HUB 42 from the master HUB 31 and connects it to the master HUB 32 to change the device connection configuration will be described. 4 is an explanatory diagram showing the network configuration after changing the device connection configuration, and FIG. 5 is an explanatory diagram showing the operation of the master HUB 31 when the slave HUB 42 is disconnected. Master H with slave HUB 42 disconnected
The UB 31 reads out that the ID number of the connected slave HUB is # 1 by the ID reading and holding means 316, and compares it with the values # 1 and # 2 held from before, and thus It detects that the slave HUB has been newly disconnected. In accordance with the detection of the disconnection of the slave hub # 2, the managed object management unit 312 deletes the user setting management information # 2 previously held, and the communication processing unit 311 sends a TRAP packet to the SNMP manager 2. It is sent to notify that the slave HUB # 2 has been disconnected.

Next, FIG. 6 is an explanatory diagram showing the operation of the HUB 32 when the slave HUB 42 is newly connected.
Master HUB 32 connected to slave HUB 42
Detects that the ID numbers of the connected HUBs are # 3, # 4, and # 2 by the ID reading and holding unit 326, and compares them with the previously held values # 3 and # 4. , Detects that the slave hub # 2 is newly connected. According to the connection detection of # 2 slave HUB,
A TRAP packet is sent to the SNMP manager 2 to notify that the slave HUB # 2 has been newly connected, and the download server 6 is notified # 2.
The download request packet of the user setting information is sent. After downloading is complete, the managed object management unit 32
2 stores the user setting information of # 2, and SNM
A TRAP packet is sent to the P manager 6 to notify the completion of downloading the # 2 user setting information.

Thus, in this embodiment, each slave H
A unique ID number is set in the UB, and user setting information unique to each slave HUB is held on the download server 6, and the master HUB is the slave HUB.
ID number of the slave HUB is detected, when the disconnection of the slave HUB is detected, the unique information of the slave HUB is deleted, and when a new connection of the slave HUB is detected, the unique information of the slave HUB is downloaded to the download server. Since it is downloaded from and stored in the master HUB, a slave HUB can be stored in a master HU.
Even when moving from B to another master HUB and changing the connection configuration of the network device, the user does not need to reset the setting information unique to the slave HUB.

In this embodiment, the slave HUB I
Although the DIP switch is used as the D setting holding means for the user to set the ID setting, for example, a device-specific ID number such as a serial number may be provided at the time of product shipment and written in the memory. In this case, the setting work by the user becomes unnecessary. In addition, as a target LAN, Ethernet
Although 10 et Base-T is illustrated, other media may be used. Further, although SNMP is exemplified as the management communication protocol, other protocols may be used, and TFTP is exemplified as the file transfer protocol, but other protocols may be used. Further, although the master HUB and the slave HUB are connected to each other through a dedicated bus, they may be connected via a serial port or the like.

Although the SNMP manager and the download server are configured by different terminals, respectively, two processes of the SNMP manager and the download server may be operated on one personal computer or workstation, or the SNMP manager may be operated. The download server may be integrated into one process. Furthermore, although the HUB was targeted as a network device, it is needless to say that it can be applied to other network devices such as a bridge and a modem.

[0024]

According to the network management system of the present invention, the second type network device having no direct communication function with the network management terminal is replaced with the first type network device having the direct communication function with the network management terminal. Even when the connection configuration of these network devices is changed by disconnecting from or newly connecting the devices, there is an effect that the user does not need to newly set the setting information unique to each device set by the user.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a network management system according to the present invention.

FIG. 2 is a block diagram showing an internal configuration of a master HUB according to the present invention.

FIG. 3 is a block diagram showing an internal configuration of a slave HUB according to the present invention.

FIG. 4 is an explanatory diagram showing a modification example of the device connection configuration according to the present invention.

FIG. 5 is an operation explanatory diagram when the slave HUB is disconnected in the present invention.

FIG. 6 is an operation explanatory diagram when a slave HUB is newly connected in the present invention.

FIG. 7 is a configuration diagram of a network management system according to a conventional example.

[Explanation of symbols]

 1 LAN wiring 2 SNMP manager 31 master HUB 32 master HUB 311 communication processing unit 312 managed object management unit 316 ID reading and holding means 41 slave HUB 42 slave HUB 43 slave HUB 44 slave HUB 416 ID setting holding means 426 ID setting holding means 6 download server

─────────────────────────────────────────────────── ─── Continuation of the front page (51) Int.Cl. ⁵ Identification number Reference number within the agency FI Technical display location H04L 12/26 8732-5K H04L 11/08 (72) Inventor Koichi Yamamoto 1048 Kadoma, Kadoma, Osaka Prefecture Address Matsushita Electric Works, Ltd. (72) Inventor Koji Sakamoto 1048, Kadoma, Kadoma-shi, Osaka Prefecture Matsushita Electric Works, Ltd.

Claims (1)

[Claims] 1. A network management terminal, a first type network device having a direct communication means with the network management terminal, and a second type network device having no direct communication means with the network management terminal. In a system in which the first type network device acts as a proxy for communication of management information between the network management terminal and the second type network device, the second type network device is a means for holding an identification number in the network. And a download server that holds network management information corresponding to the identification number is provided in the network, and the first-type network device reads and retains the identification number of the second-type network device that should act for communication. The network management information corresponding to the identification number is transferred from the download server and saved. A network management system characterized by comprising a means having.