JP2004054657A - Network device management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a network device management device capable of notifying users of information on a device which has disappeared from a network. <P>SOLUTION: The network device management device for monitoring or controlling the states of devices connected through the network is provided with a device retrieving means for retrieving devices connected to the network, a device attribute acquisition means for acquiring the values of a plurality of device attributes of the retrieved devices, a device list display means for displaying a part or all of the attribute values of the network devices acquired by the device attribute acquisition means as a list, a storage means for storing information on an optional network device once detected by the device retrieving means in a server for providing resources which can be shared by respective network devices, and an addition means for adding the device stored in the storage means to the device list display means. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a network device management apparatus that monitors or controls various devices connected to a network.
[0002]
[Prior art]
In recent years, a local area network (LAN) in which computers are connected to each other has become widespread. Such a local area network is built over a building floor or the whole building, a group of buildings (premises), a region, or a larger area. Further, such networks may be interconnected and connected to a worldwide network. Many devices such as a computer such as a PC and a printer can be connected to these networks. Also, each interconnected LAN uses a variety of hardware interconnection techniques and several network protocols.
[0003]
Here, in a simple LAN separated from others, individual users can perform device management. That is, the user can replace the device, install software, or diagnose a problem.
[0004]
However, large, complex LANs and large interconnected LAN groups require "management." Note that “management” means both management by a human network administrator and management by software used by the administrator. In the present application, "management" means management by software for managing the entire system, and "user" means a person who uses network management software. This "user" is usually the system administrator. By using network management software, a "user" can obtain management data on the network and modify this data.
[0005]
Large-scale network systems are usually dynamic systems that require constant addition and removal of equipment, software updates and problem detection. In general, there are different systems, owned by different people, and supplied by different vendors.
[0006]
As a method for managing network devices on a network constituting such a large-scale network system, several attempts have been made between a large number of standard devices. The International Organization for Standardization (ISO) has provided a universal reference framework called the Open System Interconnection (OSI) model. The OSI model of the network management protocol is called a Common Management Information Protocol (CMIP). CMIP is a common European network management protocol.
[0007]
In recent years, a simple network management protocol (Simple Network Management) has been used as a network management protocol with higher commonality.
There is a variant protocol related to CMIP called “Protocol, SNMP” (“Introduction to TCP / IP Network Management Aiming at Practical Management”, MT Rose = Author / Nishida Takeshi = Translation Toppan Co., Ltd. 1992 See the first edition of August 20, 2008).
[0008]
According to this SNMP network management technique, the network management system includes at least one network management station (NMS), several managed nodes each having an agent, and the management stations and agents used to exchange management information. Network management protocols. The user can obtain management data on the network and change the data by communicating with the agent software of the managed node using the network management software of the NMS.
[0009]
Here, the “agent” is software that runs as a background process on each managed node. When a user makes a request for management data to a managed node on the network, the network management software sends an object identifier (described later) in a management packet or frame to the agent of the managed node.
[0010]
The agent interprets the object identifier and retrieves data corresponding to the object identifier. Then, the data is put into a packet and returned to the network management software. At times, the agent may invoke the corresponding process to retrieve the data.
[0011]
The agent holds data on the managed node in a database format. This database is called MIB (Management Information Base).
[0012]
FIG. 7 is a conceptual diagram showing the structure of the MIB.
[0013]
As shown in FIG. 7, the MIB has a tree-structured data structure, and identifiers are uniquely assigned to all nodes. In FIG. 7, the identifier of the node is defined based on the number written in parentheses. For example, the identifier of the node 501 in FIG. Since the identifier of the node 502 is a child of the node 501, it is 1.3. Similarly, the identifier of the node 503 is 1.33.6.1.2. The identifier of this node is the object identifier (OBJECTIDENTIFIER). Here, FIG. 5 illustrates a part of the MIB defined as a standard.
[0014]
The structure of this MIB is called a management information structure (Structure of Management Information, SMI), and is RFC1155 Structure and Identification of Management Information for TCP / IP-based information.
Stipulated in
[0015]
Next, the SNMP protocol will be described.
[0016]
A PC on which network management software is operating (hereinafter, referred to as a manager) communicates with a managed network device on which an SNMP agent is operating (hereinafter, referred to as an agent) using the SNMP protocol. There are five types of commands in the SNMP protocol, which are called Get-request, Get-next-request, Get-response, Set-request, and Trap. FIG. 9 shows how these commands are exchanged between the manager and the agent.
[0017]
Get-request and Get-next-request are commands that the manager sends to the agent. The agent that has received this command sends a Get-response command to the manager to notify the value of the MIB object to the manager (901 and 902).
[0018]
Set-request is a command that the manager sends to the agent to set the value of the MIB object of the agent. The agent that has received this command sends a Get-response command to the manager to notify the manager of the setting result (903).
[0019]
Trap is a command that the agent sends to the manager in order to notify the manager of a change in its own state (904).
[0020]
FIG. 10 is a diagram showing the format of commands other than Trap, that is, Get-request, Get-next-request, Get-response, and Set-request (collectively referred to as SNMP messages). 800 is an SNMP message. The SNMP message includes a version 801, a community name 802, and a PDU 803. Reference numeral 810 indicates the details of the PDU 803.
[0021]
The PDU 810 includes a PDU type 811, a request ID 812, an error status 813, an error index 814, and MIB information 815. The PDU type 811 stores a value for identifying a command. If this value is 0, it is identified as Get-request, if it is 1, it is identified as Get-next-request, if it is 2, it is identified as Get-response, and if it is 3, it is identified as Set-request. In the error status 813, a value indicating error information is stored. This value is 0 when there is no error. In the MIB information 815, a MIB object identifier and a value of the MIB object are stored as a set.
[0022]
Next, a large-scale network that requires management will be described.
[0023]
FIG. 4 is a diagram showing a network when a network board (NB) 101 for connecting a printer to a network is connected to a printer 102 having an open architecture. The NB 101 is connected to a local area network (LAN) 100 via a LAN interface such as an Ethernet interface 10Base-2 having a coaxial connector or a 10Base-T having an RJ-45.
[0024]
A plurality of personal computers (PCs) such as a PC 103 and a PC 104 are also connected to the LAN 100. These PCs can communicate with the NB 101 under the control of the network operating system. One of the PCs, for example, the PC 103 can be designated to be used as a network management unit. Further, a printer such as the printer 105 connected to the PC 104 may be connected to each PC.
[0025]
A file server 106 is connected to the LAN 100, and manages access to files stored in a large-capacity (for example, 10 billion bytes) network disk 107. The print server 108 causes a printer such as the connected printers 109a and 109b or the printer 105 at a remote location to perform printing. Further, other peripheral devices (not shown) may be connected to the LAN 100.
[0026]
Further, the network shown in FIG. 4 can use network software such as Novell or UNIX to efficiently communicate between various network members. Any network software can be used, for example, Novell's NetWare (trademark of Novell, hereinafter abbreviated) software can be used (detailed description of this software package is included in the NetWare package). (See online documentation, which can be purchased with Novell's NetWare package.)
[0027]
Further, the configuration of FIG. 4 will be briefly described. The file server 106 performs transmission and reception of data files between LAN members, or stores, queues, and caches data files, and plays a role as a file management unit. For example, a data file created by each of the PC 103 and the PC 104 is sent to the file server 106. The file server 106 arranges these data files in order, and transmits the data files to the printer 109a according to a command from the print server 108.
[0028]
The PC 103 and the PC 104 generate data files, send the generated data files to the LAN 100, receive data files from the LAN 100, and display and / or process the data files. Although a PC is shown in FIG. 4, other computer devices may be used as long as they are suitable for executing network software. For example, if UNIX software is used, a UNIX workstation may be connected to the network. These UNIX workstations are used with the illustrated PC under appropriate circumstances.
[0029]
Typically, LAN 100 serves a somewhat local group of users, for example, a group of users on one floor or multiple consecutive floors in a building. Further, a wide area network (WAN) may be constructed as the users are separated, such as when the user is in another building or another prefecture. A WAN is basically a collection of LANs formed by connecting several LANs with a high-speed digital line such as an Integrated Services Digital Network (ISDN) telephone line.
[0030]
Therefore, as shown in FIG. 4, the LAN 100, the LAN 110, and the LAN 120 are connected via the modulation / demodulation (MODEM) / transponder 130 and the backbone 140, and a WAN is constructed. These connections are simple electrical connections with multiple buses. A dedicated PC is connected to each LAN, and although not always necessary, a file server and a print server are usually connected.
[0031]
Therefore, as shown in FIG. 4, the LAN 110 includes a PC 111, a PC 112, a file server 113, a network disk 114, a print server 115, a printer 116, and a printer 117. In contrast, the LAN 120 includes only the PC 121 and the PC 122. The devices connected to the LAN 100, the LAN 110, and the LAN 120 can access the functions of the devices of other LANs via the WAN connection.
[0032]
As an agent mounting method, it is conceivable to mount the agent on a network board for connecting a printer to a network. Thus, the printer can be managed by the network management software. Using the network management software, the user can acquire information on the printer to be managed and change the status of the printer. More specifically, for example, a character string displayed on a liquid crystal display of a printer can be obtained, or a default paper cassette can be changed.
[0033]
Next, an embodiment in which a network board (NB) equipped with an agent is connected to a printer will be described.
[0034]
As shown in FIG. 5, preferably, NB 101 is an “embedded” network node that is built into the internal expansion I / O slot of printer 102 and has the following processing and data storage functions. The configuration of the NB 101 has an advantage that a characteristic auxiliary function for managing and managing a large multi-area WAN network is provided. The auxiliary functions include, for example, printer control and status observation from a remote location on the network (such as the office of the network administrator), and a printer for providing a guaranteed initial environment for the next user after each print job. Includes printer logs or usage statistics that can be accessed over the network to automatically manage configuration and characterize printer load or schedule toner cartridge replacement.
[0035]
An important factor in this NB design is a function of accessing the printer control from the NB 101 via a bidirectional interface such as a shared memory. In addition to the shared memory, an interface such as a SCSI interface may be used. As a result, the printer status information is sent to the NB 101 or an external network node, and many auxiliary functions can be implemented.
[0036]
The print image information and the control information are configured by a microprocessor in the NB 101, described in a shared memory, and read out by the printer 102. Similarly, printer status information is sent from the printer 102 to the shared memory, where it is read by the NB processor.
[0037]
FIG. 5 is a sectional view showing a state in which the NB 101 is installed in the printer 102.
[0038]
As shown in FIG. 5, the NB 101 includes a phase plate 101b for network connection and a printed circuit board 101a on which the phase plate 101b is installed. The NB 101 is connected to the printer interface card 150 via the connector 170. Printer interface card 150 directly controls the printer engine of printer 102. The print data and the printer control command are input from the NB 101 to the printer interface card 150 via the connector 170.
[0039]
On the other hand, the printer status information is output from the printer interface card 150 via the connector 170. The NB 101 sends the printer status information to the LAN 100 via the network connector on the face plate 101b. The printer 102 can also receive print data from the conventional serial port 102a and parallel port 102b.
[0040]
FIG. 6 is a block diagram showing an electrical connection between the NB 101, the printer 102, and the LAN 100.
[0041]
The NB 101 is directly connected to the LAN 100 via a LAN interface and to the printer 102 via a printer interface card 150. The NB 101 includes a microprocessor 301 for controlling the NB 101, a ROM 303 storing an operation program of the microprocessor 301, a RAM 302 used as a work area when the microprocessor 301 executes a program, an NB 101 and a printer interface card. 150 and a shared memory 200 for exchanging data with each other, which are interconnected via an internal bus.
[0042]
A program for the NB 101 to operate as an SNMP agent is stored in the ROM 303. The microprocessor 301 operates according to the program stored in the ROM 303, and uses the RAM 302 as a work area. Further, the shared memory 200 is used as a buffer area for mutually communicating with the printer interface card 150.
[0043]
The microprocessor 151 of the printer interface card 150 exchanges data with the NB 101 via the shared memory 200 in the NB 101. The microprocessor 151 of the printer interface card 150 also communicates with the printer engine 160 that actually drives the printing mechanism.
[0044]
Next, a PC on which the network management software is executed will be described.
[0045]
FIG. 8 is a block diagram showing a configuration of a PC capable of executing network management software. In FIG. 8, reference numeral 600 denotes a PC capable of executing network management software, which is equivalent to the PC 103 in FIG. The PC 600 includes a CPU 601 that executes network management software stored in a ROM 5602 or a hard disk (HD) 611 or supplied by a floppy disk drive (FD) 612, and collectively manages each device connected to the system bus 504. To control.
[0046]
A RAM 603 functions as a main memory, a work area, and the like for the CPU 601. A keyboard controller (KBC) 605 controls input of instructions from a keyboard (KB) 609 or a pointing device (not shown). Reference numeral 606 denotes a CRT controller (CRTC), which controls display on a CRT display (CRT) 610. A disk controller (DKC) 607 controls a hard disk (HD) 611 and a floppy disk drive (FD) 612 that store a boot program, various application programs, edit files, user files, network management software, and the like. A network interface card (NIC) 608 exchanges data with an agent or a network device via the LAN 100 in both directions.
[0047]
Next, a configuration of network management software in a conventional example will be described.
[0048]
The network management device in the conventional example is realized by a PC similar to a PC capable of realizing the network management device as shown in FIG. The hard disk (HD) 611 stores network management software according to the present application, which is an operation main body of all the following descriptions. In all the descriptions below, the subject of execution in hardware is the CPU 601 and the subject of control in software is network management software unless otherwise specified. In this conventional example, the OS is assumed to be, for example, Windows (manufactured by Microsoft), but is not limited to this.
[0049]
The network management software according to the present invention may be supplied by being stored in a storage medium such as a floppy disk or a CD-ROM. In this case, the floppy disk drive 612 shown in FIG. The program is read from a storage medium by a drive or the like, and is installed in a hard disk (HD) 611.
[0050]
FIG. 9 is a module configuration diagram of the network management software according to the conventional example.
[0051]
This network management software is stored in the hard disk 611 in FIG. 8, and is executed by the CPU 601. At that time, the CPU 601 uses the RAM 603 as a work area. In FIG. 9, reference numeral 701 denotes a device list module, which is a module for listing and displaying network devices connected to the network (the state of the list display will be described later with reference to FIG. 14). FIG. 13 shows an example of a device list module displaying a list of devices (referred to as a device list display window). Reference numeral 702 denotes a general control module, which controls other modules based on an instruction from a device list.
[0052]
Reference numeral 703 denotes a module called a configurator, which performs a special process related to the network setting of the agent. Reference numeral 704 denotes a search module, which searches for a network device connected to the network. The network devices searched by the search module 704 are displayed in a list in the device list 701. Reference numeral 705 denotes a NetWare job module that obtains the status of a print job from a network server using the NetWare API 716 (for the NetWare API, see, for example, “NetWare Programmer's Guide C” issued by Novell, etc. Is available from Novell).
[0053]
Reference numerals 706 and 707 denote UI (User Interface) modules for displaying a device detail window described later. There are UI modules for each model of a target network device for which detailed information is to be displayed. Reference numerals 708 and 709 are control modules that perform control specific to each model of the target network device from which detailed information is to be obtained. Like the UI module, the control module exists for each model of the target network device from which the detailed information is acquired. The control A module 708 and the control B module 709 obtain MIB information from the network device to be managed using the MIB module 710, convert the data of the MIB information as necessary, and send the MIB information to the UIA module 706 and the UIB module 707. Pass that data.
[0054]
The MIB module 710 is a module that converts between an object identifier and an object key. An object key is a 32-bit integer that has a one-to-one correspondence with an object identifier. The object identifier is a variable-length identifier, which is cumbersome to implement in network management software. Therefore, in the network management software according to the present application, a fixed-length identifier corresponding to the object identifier on a one-to-one basis is internally used. . Modules higher than the MIB module 710 handle MIB information using this object key. This facilitates implementation of network management software.
[0055]
Reference numeral 711 is called an SNMP module, and performs transmission and reception of an SNMP packet. A common transport module 712 is a module for bridging with a lower protocol for transporting an SNMP packet. In practice, either the IPX handler 713 or the UDP handler 714 transfers packets according to the protocol selected by the user when the network management software operates. To implement the UDP handler 714, a WinSock API 717 is used. (For WinSock, refer to the specification of Windows Socket API v1.1. This document is available from a plurality of places. Compiled with VisualC ++.)
[0056]
The current protocol 715 used by the configurator 703 indicates either the IPX protocol or the UDP protocol selected by the user when the network management software operates.
[0057]
Further, a specific flow will be described.
[0058]
The MIB module 710 performs processing such as conversion from an object key to an object identifier in response to a request from the upper module, and requests the SNMP module 711 to send a Get-request command.
[0059]
The SNMP module 711 generates the PDU 810 of FIG. 8 in the RAM 603 in response to a command transmission request from the MIB module 710, and passes the SNMP packet to the common transport module 712.
[0060]
The common transport module 712 performs processing such as adding a header according to the protocol selected by the user when the network management software operates. Then, if the protocol selected by the user is the TCP / IP protocol, the packet is passed to the WinSock API module 717, and if the protocol is the NetWare protocol, the packet is passed to the NetWare API module 716.
[0061]
Hereinafter, description will be made on the assumption that the protocol selected by the user is the TCP / IP protocol. The WinSock API module 717 converts the received packet into an IP packet, and requests the OS to send the packet to the network. Then, the OS writes the packet on the RAM 603 to the NTC 608 via the system bus 604. The NIC 608 converts the written packet into a frame and sends the frame to the LAN 100.
[0062]
Conversely, packets from the network device are received by NIC 608. The NIC 608 notifies the OS that the packet has been received by interrupting it. The OS reads the packet from the NIC 608 via the system bus 604 and stores the packet in the RAM 603. The OS determines the protocol related to the packet from the protocol selected by the user or the received packet, and passes the packet to the WinSock API module 717 in the case of the TCP / IP protocol or to the NetWare API module 716 in the case of the NetWare protocol.
[0063]
Hereinafter, a case where the protocol based on the determination result is the TCP / IP protocol will be described.
[0064]
The WinSock API module 717 checks the destination address of the packet and determines whether the packet is addressed to the own address. If the packet is not addressed to the own address, the packet is discarded. If the address is addressed to the own address, the UPD handler 714 is activated to pass the packet to the common transport module 712.
[0065]
The common transport module 712 performs processing such as removal of the transport header, and passes the SNMP packet to the SNMP module 711. The SNMP module 711 removes the SNMP header and passes the MIB information in the PDU 810 to the MIB module 710. The MIB module 710 converts the MIB information into a format defined by MIBAPI, and notifies the upper module of the value of the MIB object using a callback function.
[0066]
The files necessary for installing the network management software are usually recorded on a physical medium such as a floppy disk (FD) or a CD-ROM and distributed, or transmitted via a network. After the user obtains a file necessary for installing the network management software by these means, the user starts the installation according to a predetermined installation procedure.
[0067]
The procedure for installing the network management software is the same as the procedure for installing other general software. That is, when the user starts the installer of the network management software on the personal computer (PC), the installer automatically installs the network management software. Further, the installer copies files required for the network management software to the hard disk of the PC, and has the user input information as necessary, and corrects or newly creates the files required for the network management software.
[0068]
Next, a search sequence in the network management software according to the conventional example will be described. FIG. 12 is a diagram showing a search sequence in the conventional network management software.
[0069]
12, a search module 1030 indicates a search module of the network management software, which is equivalent to 704 in FIG. This search module 1030 is executed by the CPU 601 in FIG. 8 on the PC 103 in FIG. 1 like other modules of the network management software.
[0070]
The device 1031 is connected to the network and is a device on which the SNMP agent is operating, such as the NP 101 in FIG. Similarly, device 1032 indicates NB 118.
[0071]
When a search start instruction is issued from the upper module, the search module 1030 specifies a broadcast address and sends out an SNMP packet for acquiring the device status and device type (1001). Since the broadcast address is specified, this packet is delivered to all network devices connected to the network.
[0072]
On the other hand, the network device equipped with the SNMP agent sends a response packet to the SNMP packet (1002 and 1003).
[0073]
The search module that has received the response packet from the network device transmits an SNMP packet to each network device to obtain more detailed information. More specifically, in FIG. 12, an SNMP packet of 1004 is transmitted for a response packet of 1002, and an SNMP packet of 1006 is transmitted for a response packet of 1003. This transmission of the SNMP packet is called device-specific information acquisition.
[0074]
The reason for not inquiring the value of the SNMP object 1001 instead of inquiring the value of the MIB object in transmitting the SNMP packet 1004 or 1006 is as follows. That is, if many MIB objects are queried at once by one packet, the response packet from the network device may exceed the maximum packet length (484 bytes) permitted by the SNMP protocol. is there. In such a case, an error "tooBig" in the SNMP protocol is returned from the network device, and no information can be obtained. Therefore, the value of the MIB object is queried for a plurality of SNMP packets.
[0075]
In particular, the SNMP packets 1004 and 1006 inquire about optional devices mounted on the network device. Here, if many optional devices are mounted on the network device, there is a high possibility that the packet length of the response packet from the network device becomes large. Furthermore, when the values of other MIB objects are also queried, the possibility that the packet length of the response packet exceeds the maximum length (484 bytes) is further increased. For this reason, it is safer to make the packet inquiring about the optional device an independent packet.
[0076]
The network device that has received the SNMP packet transmits a response packet. More specifically, 1005 packets are transmitted for 1004 packets, and 1007 packets are transmitted for 1006 packets.
[0077]
Next, when the device response timer 1021 expires, the search module 704 notifies the information of the network device obtained so far to the upper module (1021). This is called a search result notification.
[0078]
When the search interval timer 1022 expires, the search for a network device is started again. The processing in steps 1008 to 1014 is the same as the processing in steps 1001 to 1007, and a description thereof will not be repeated.
[0079]
Next, a procedure for displaying a device list in the network management software according to the conventional example will be described. FIG. 17 is a flowchart showing a procedure for displaying a device list in conventional network management software.
[0080]
First, a search for a device on the network is started in step S1501 in FIG.
[0081]
In step S1502, each time the device search unit finds a new device, a row is added to the detection device table.
[0082]
Here, information registered in the detection device table will be described.
[0083]
FIG. 13 is a diagram showing a data structure called a detection device table used to store information on network devices detected by the search module 1030. This data structure is held in the RAM 603 in FIG.
[0084]
A network address of the detected network device is registered in the network address column 1101.
[0085]
In the device type column 1102, the type of the network device is registered. In the device state column, the state of the network device in the current state is registered.
[0086]
In the equipment information column 1103, optional equipment mounted on the network device is registered.
[0087]
In the MAC address column 1104, a unique physical address is registered for each network board.
[0088]
Specifically, in FIG. 13, two network devices are registered in the detection device table 1110. The first is a network device having a network address of 192.168.6.1.1. This network device has a device type of LBP, and a 2,000-sheet deck is mounted as an optional device. Also, the device state is available (Ready).
[0089]
The second is a network device having a network address of 192.168.16.2. This network device has a device type of a copying machine (Copier), and is equipped with a sorter as an optional device. It is known from the device state that a paper jam (Jam) is currently occurring.
[0090]
Of the above information, information that can dynamically change over time is the device state 1103. The device status indicates the current status of the network device, and changes with a change in the status of the network device. This information is inquired in communication 901 for searching for a network device, and the value is returned from the network device in communication 902 or 903.
[0091]
Also, DHCP (Dynamic Host Configuration Protocol)
In an environment where a network address is dynamically assigned like a service, the network address 1101 is also information that can change.
[0092]
In step S1503, it is determined whether the search has been completed. If the determination in step S1503 is YES, the process proceeds to step S1504, and if NO, step S1502 and subsequent steps are repeated.
[0093]
In step S1504, a list of detected devices is displayed in a device list display window as shown in FIG. 14 based on the information registered in the detection device table.
[0094]
In step S1505, it is determined whether an operation for closing the device list has been performed by the user. If the device list display window is to be closed, the device list display window is closed in step S1506 and the process ends. If the device list display window is displayed as it is, it is determined in step S1507 whether an operation for opening a detailed information dialog box of a specific device selected on the device list has been performed. If the determination in step S1507 is YES, a specific device detailed information dialog box as illustrated in FIG. 15 is opened. If the determination in step S1507 is NO, the process returns to step S1505.
[0095]
Here, the device detailed information dialog box is a dialog box displayed by selecting a device in the device list, and contains more detailed information than the information displayed in the device list. Is displayed.
[0096]
Further, an administrator information display dialog box as shown in FIG. 17, for example, is called from the device detailed information dialog box. In the administrator information display dialog box, the name, contact information, and comment of the device administrator can be set and displayed.
[0097]
FIG. 18 is a flowchart showing a process when updating the detection device table. This process is executed at regular intervals during the time from step S1505 in FIG. 17 is repeated in order to reflect the latest network device information in the device list.
[0098]
First, in step S1601 in FIG. 18, all the contents of the detection device table are deleted, and the table is initialized.
[0099]
In step S1602, a search for a device on the network is started.
[0100]
In step S1603, each time the device search unit finds a new device, one line is added to the detection device table.
[0101]
In step S1604, it is determined whether the search for a device on the network has been completed. If the determination in step S1604 is YES, the process ends. If the determination is NO, step S1603 and subsequent steps are repeated.
[0102]
[Problems to be solved by the invention]
However, in the above-described conventional example, since a device that is not currently connected to the network or a device whose power is turned off is not displayed, there is a problem in that information such as the name, contact information, and comment of the administrator cannot be confirmed.
[0103]
For this reason, when a device that is usually used is disconnected from the network due to repair or the like, information such as where the device is located and when it can be used may not be easily known.
[0104]
SUMMARY OF THE INVENTION The present invention has been made in view of the above-described problem, and an object of the present invention is to provide a network device management apparatus capable of notifying a user of information about a device that is no longer present on the network, even if the device is no longer present on the network. To provide.
[0105]
[Means for Solving the Problems]
According to the present invention, in a management device for a network device that monitors or controls the status of a device connected via a network, a device search unit for searching for a device connected to the network, and a search by the search unit Device attribute acquiring means for acquiring values of a plurality of device attributes relating to the device detected in step 1, device list displaying means for displaying a list of some or all of the attribute values of the network device acquired by the device attribute acquiring means, A storage unit for storing information on an arbitrary network device once detected by the device search unit in a server that provides resources sharable by the network device, and storing the device stored by the storage unit in the device. Additional steps to add to the list display means By the provided, it is a device that no longer exist on the network, is to be able to announce information about the device.
[0106]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, a network device management apparatus according to an embodiment of the present invention will be described with reference to the drawings.
[0107]
In the following description, unless otherwise specified, the subject of execution and determination is a CPU in hardware, while a software is a network management program.
[0108]
1 to 3 are flowcharts showing a procedure for displaying a device list in the network management software according to the present embodiment.
[0109]
First, in step S101 in FIG. 1, all the contents of the detection device table are deleted, and the table is initialized.
[0110]
In step S102, a search for a device on the network is started.
[0111]
In step S103, each time the device search unit finds a new device, a row is added to the detection device table.
[0112]
In step S104, it is determined whether the search has been completed. If the determination in step S104 is YES, the process proceeds to step S105, and if NO, step S103 and the subsequent steps are repeated.
[0113]
In step S105, it is determined whether a previously detected device table exists on the server. If the determination in step S105 is YES, the process proceeds to step S106.
[0114]
In step S106, reading of the device table from the previously detected device table is started.
[0115]
In step S107, it is determined whether an entry of a device registered in the previously detected device table is present in the detected device table. This determination is made by comparing information that can be uniquely specified by the device, for example, a MAC address. If the determination in step S107 is YES, the process proceeds to step S109, and if NO, the process proceeds to step S108.
[0116]
In step S108, one row is added to the detection device table.
[0117]
In step S109, it is determined whether reading of the device table from the previously detected device table has been completed. If the determination in step S109 is YES, the process proceeds to step S110, and if NO, step S107 and the subsequent steps are repeated.
[0118]
In step S110, a list of detected devices is displayed or updated based on the information registered in the detected device table.
[0119]
In step S111, it is determined whether an operation has been performed by the user to close the device list display window. If the determination in step S111 is YES, the process proceeds to step S112. If the determination is NO, the process proceeds to step S119.
[0120]
In step S112, the device list display window is closed and the process ends.
[0121]
In step S113, the contents of the previously detected device table are all deleted, and the table is initialized.
[0122]
In step S114, reading of the device table from the detection device table is started.
[0123]
In step S115, it is determined whether or not the FLAG 1716 of the device registered in the previously detected device table is TRUE. This FLAG is for identifying whether or not the administrator information set in the administrator information setting dialog box as illustrated in FIG. 18A is stored in the server. TRUE, and if not stored in the server, FALSE. If the determination in step S115 is YES, the process proceeds to step S116, and if NO, the process proceeds to step S117.
[0124]
Here, the administrator information setting dialog box is a dialog box that is displayed by selecting a menu in the device detailed information dialog box, and includes settings such as a device administrator name, contact information, and comments. It can be carried out.
[0125]
In step S116, an entry of a device whose FLAG is TRUE is added to the detected device table.
[0126]
In step S117, it is determined whether the reading of the device table from the detected device table has been completed. If the determination in step S117 is YES, the process proceeds to step S118, and if the determination is NO, step S115 and subsequent steps are repeated.
[0127]
In step S118, the previously detected device table is stored in the server, and the process ends.
[0128]
If the device list display window is displayed as it is, it is determined in step S119 whether an operation for opening the detailed information dialog box of the specific device selected on the device list has been performed. If the determination in step S119 is YES, the process proceeds to step S120. If the determination is NO, the process proceeds to step S121.
[0129]
Here, the device detailed information dialog box is a dialog box displayed by selecting a device in the device list, and contains more detailed information than the information displayed in the device list. Is displayed.
[0130]
In step S120, it is determined whether the device selected on the device list is a device read from the previously detected device table. If the determination in step S120 is YES, the process proceeds to step S121. If the determination is NO, a detailed information dialog box of the specific device selected on the device list is opened.
[0131]
In step S121, an administrator information display dialog box as illustrated in FIG. 20B is displayed.
[0132]
If the administrator information display dialog box is displayed as it is, it is determined in step S122 whether an operation for closing the administrator information display dialog box has been performed. If the determination in step S122 is YES, the process proceeds to step S123. If the determination is NO, the process returns to step S122.
[0133]
In step S123, the administrator information display dialog box is closed, and the process returns to step S110.
[0134]
FIG. 18 is a flowchart showing a process when updating the detection device table. This process is executed at regular intervals while the process from step S110 in FIG. 2 is repeated to reflect the latest network device information in the device list.
[0135]
First, in step S1601 in FIG. 18, all the contents of the detection device table are deleted, and the table is initialized.
[0136]
In step S1602, a search for a device on the network is started.
[0137]
In step S1603, each time the device search unit finds a new device, one line is added to the detection device table.
[0138]
In step S1604, it is determined whether the search for a device on the network has been completed. If the determination in step S1604 is YES, the process ends. If the determination is NO, step S1603 and subsequent steps are repeated.
[0139]
FIG. 19A is a diagram showing a data structure called a detection device table used to store information on network devices detected by the search module 1030. This data structure is held in the RAM 603 in FIG.
[0140]
Information of the detected network device is registered in the detection device table 1720. Each time one network device is detected, one row is added to the detection device table.
[0141]
Hereinafter, information registered in the detection device table will be described.
[0142]
The network address of the detected network device is registered in the network address column 1701.
[0143]
In the device type column 1702, the type of the network device is registered. In the device state column, the state of the network device in the current state is registered.
[0144]
In the equipment information column 1703, the state of the network device at present is registered.
[0145]
In the equipment information column 1704, optional equipment mounted on the network device is registered.
[0146]
In the MAC address column 1705, a unique physical address is registered for each network board.
[0147]
A FLAG column 1706 is used to identify whether or not settings such as a device administrator name, a contact, and a comment in the administrator information setting dialog box as illustrated in FIG. When saving to the server, TRUE is registered. When not saving to the server, FALSE is registered.
[0148]
Specifically, in FIG. 17A, two network devices are registered in the detection device table 1520. The first is a network device having a network address of 192.168.6.1.1. This network device has a device type of LBP, and a 2,000-sheet deck is mounted as an optional device. Also, the device state is available (Ready). Since the FLAG status is TRUE, it is understood that the setting value of the administrator information dialog box of the device is stored on the server.
[0149]
The second is a network device having a network address of 192.168.16.2. This network device has a device type of a copying machine (Copier), and a sorter is mounted as an optional device. It is known from the device state that a paper jam (Jam) is currently occurring. Since the FLAG status is FALSE, it is understood that the setting value of the administrator information setting dialog box of the device is not stored on the server.
[0150]
Of the above information, information that can dynamically change over time is the device status 1503. The device status indicates the current status of the network device, and changes with a change in the status of the network device. This information is inquired in communication 901 for searching for a network device, and the value is returned from the network device in communication 902 or 903.
[0151]
Also, DHCP (Dynamic Host Configuration Protocol)
In an environment where a network address is dynamically assigned like a service, the network address 1501 is also information that can change.
[0152]
FIG. 17B is a diagram showing a data structure called a previously detected device table 1530 used for storing information of network devices detected by the search during the previous activation of the network management software.
[0153]
The network address 1711 to the MAC address 1715 in the previously detected device table has the same data structure as the detected device table 1720 in FIG.
[0154]
In the administrator name column 1716, the administrator name of the device in the administrator information setting dialog box is registered.
[0155]
In the contact column 1717, the contact information of the administrator in the administrator information setting dialog box is registered.
[0156]
In the comment column 1718, comments from the administrator of the administrator information setting dialog box are registered.
[0157]
This data structure is maintained on a server that provides resources that can be shared by network devices.
[0158]
In the above embodiment, a device not on the network is selected from the device list display window to directly display the administrator information display dialog box. However, as in the normal case, the device details display dialog box is displayed. May be displayed, and then an administrator information display dialog box may be displayed therefrom.
[0159]
Further, in the above embodiment, the manager information such as the manager name, the contact information, and the comment is stored. However, the present invention is not limited to this, and information about the device such as the installation location of the device may be used.
[0160]
Furthermore, in the above embodiment, when displaying the device list in the device list display window, the device detected as a result of the search and the device added from the previously detected device table are displayed without distinction. There may be an identification means such as changing an icon for distinction.
[0161]
The network management software according to the present invention described above may be implemented in such a manner that a program installed from the outside is executed by the PC 600. In such a case, a group of information including the program is transferred from the external storage medium to the RAM 603 of the PC 600 via a storage medium such as a CD-ROM, a flash memory, a floppy disk, or via a network such as e-mail or personal computer communication. By loading, the program is supplied to the PC 600. Even in this case, the present invention is applied.
[0162]
When the network management software of the present invention is installed on the PC 600, first, an installation program is loaded into the system of the PC 600 and executed by the CPU 601. Next, the installation program executed by the CPU 601 reads the network management software from the storage medium storing the network management software and stores the network management software in the hard disk 611.
[0163]
The present invention may be applied to a system or an integrated device including a plurality of devices (for example, a host computer, an interface device, a reader, and the like), or may be applied to a device including a single device.
[0164]
A storage medium storing program codes of software for realizing the functions of the above-described embodiments is supplied to a system or an apparatus, and a computer (or CPU or MPU) of the system or the apparatus is stored in the storage medium. It goes without saying that the object of the present invention is also achieved by reading and executing the program code. In this case, the program code itself read from the storage medium implements the novel function of the present invention, and the storage medium storing the program code constitutes the present invention.
[0165]
As a storage medium for supplying the program code, for example, a floppy disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, and the like can be used.
[0166]
The functions of the above-described embodiments are implemented when the computer executes the readout program code. In addition, the OS or the like running on the computer executes one of the actual processing based on the instruction of the program code. The functions of the above-described embodiments can also be realized by performing all or part of the processing and performing the processing.
[0167]
Further, after the program code read from the storage medium is written into a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. The CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments can also be realized by the processing.
[0168]
The present invention is also applicable to a case where the program is delivered from a storage medium storing a program code of software for realizing the functions of the above-described embodiments to a requester via a communication line such as a personal computer communication. It goes without saying that it can be applied.
[0169]
【The invention's effect】
As is apparent from the above description, according to the present invention, the information of the device once detected by the device searching means is stored and added to the device list display means at the next search, so that the device no longer exists on the network. Even if the device is the same, the effect of being able to notify the user of information about the device can be obtained.
[Brief description of the drawings]
FIG. 1 is a flowchart of an operation of network management software according to an embodiment of the present invention.
FIG. 2 is a flowchart of an operation of the network management software according to the embodiment of the present invention.
FIG. 3 is a flowchart of an operation of the network management software according to the embodiment of the present invention.
FIG. 4 is a diagram showing a form in which a network board for connecting the printer of the embodiment of the present invention to a network is connected to a printer having an open architecture.
FIG. 5 is a partially cutaway view showing an embodiment in which a network board on which an agent is mounted is connected to a printer.
FIG. 6 is a block diagram illustrating electrical connection between a network board, a printer, and a LAN.
FIG. 7 is a conceptual diagram showing the structure of an MIB.
FIG. 8 is a block diagram illustrating a configuration of a PC on which network management software can operate.
FIG. 9 is a diagram illustrating a module configuration of network management software.
FIG. 10 is a diagram showing a packet format when the SNMP protocol is used.
FIG. 11 is a diagram showing transmission and reception of SNMP commands between a manager and an agent.
FIG. 12 is a diagram showing a communication sequence between a search module and a network device.
FIG. 13 is a diagram showing a detection device table in a conventional example.
FIG. 14 is a diagram showing a display example of a device list display window.
FIG. 15 is a diagram illustrating a display example of a device details dialog box according to the related art or the embodiment of the present invention.
FIG. 16 is a diagram illustrating a display example of an administrator information setting dialog box according to a conventional example.
FIG. 17 is a flowchart illustrating a method of displaying a device list display window according to a conventional example.
FIG. 18 is a flowchart illustrating a method of updating a detection device table according to a conventional example or the embodiment of the present invention.
FIG. 19 is a diagram showing a detected device table (a) and a previously detected device table (b) in this embodiment.
FIG. 20 is a diagram illustrating a display example of an administrator information setting dialog box (a) and an administrator information display dialog box (b) according to the embodiment;
[Explanation of symbols]
100, 110, 120 LAN
101 Network Board
102, 105, 109a, 109b, 116, 117
104, 111, 112, 121, 122 PC
106,113 File server
107,114 Network disk
108,115 print server
130 Modem / Transponder
140 backbone
150 Printer interface card
151 Microprocessor
160 Printer Engine
200 shared memory
301 MPU
302 RAM
303 ROM
600 PC
601 CPU
602 ROM
603 RAM
604 system bus
605 keyboard controller
606 CRT controller
607 disk controller
608 Network Interface Card
609 keyboard
610 CRT
611 hard disk
612 floppy disk
701 Device list module
702 Total control module
703 Configurator
704 Search module
705 NetWare Job Module
706 UI A module
707 UI B module
708 Control A module
709 Control B module
710 MIB Module
711 SNMP module
712 Common Transport Module
713 IPX Handler
714 UDP handler
716 NetWare API
717 WinSock API
1030 Search module
1031 Device 1
1032 Device 2
1110, 1520 Detection device table
1530 Previous detection device table

Claims (9)

A management device for a network device that monitors or controls the state of a device connected via a network,
Device searching means for searching for a device connected to the network;
Device attribute acquisition means for acquiring values of a plurality of device attributes relating to the device detected by the search by the search means,
Device list display means for displaying a list of a part or all of the attribute values of the network device acquired by the device attribute acquisition means,
A storage unit for storing information on any network device once detected by the device search unit in a server that provides resources that can be shared by the network device;
Additional means for adding the device stored by the storage means to the device list display means,
A network device management apparatus comprising: 2. The network device management apparatus according to claim 1, further comprising an administrator information display unit for displaying administrator information on the device displayed on the device list display unit. 2. The network device management apparatus according to claim 1, further comprising an administrator information changing unit configured to change administrator information displayed on the administrator information display unit. 2. The apparatus according to claim 1, further comprising a setting unit configured to set whether or not information on the network device once detected by the device searching unit is stored in a server that provides a resource sharable by the network device. A network device management apparatus according to claim 1. 2. The network device management apparatus according to claim 1, further comprising a device selection unit for selecting a desired network device from the network devices displayed by the device list display unit. 2. The network device management apparatus according to claim 1, further comprising a device confirmation unit for confirming whether or not the device selected by the device selection unit exists on a network. 2. The network device management apparatus according to claim 1, further comprising device detail display means for displaying detailed information of the network device when the device exists on the network by the device confirmation means. 2. The network device management apparatus according to claim 1, further comprising: administrator information display means for displaying administrator information of the network device when the device is not present on the network by the device confirmation means. 2. The network device management apparatus according to claim 1, further comprising a display unit for displaying, on the device displayed on the device list display unit, a device stored in the storage unit.

Images