JP2000172603A - Method and device for managing network, and storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an efficient network managing method, while suppressing increase in network traffic and increase in processing at a device. SOLUTION: When a message length over error occurs in a response, while processing to plural objects can be requested with one message and the broadcasting of the message is enabled (S104), a request message packet is retransmitted while being divided, and an agent where the error occurs is detected (S108). Then, in place of the broadcasting request message packet, a non-broadcasting request message is retransmitted to the agent where the error occurs (S109).

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for managing a network to which a plurality of data processing devices are connected, and more particularly to a network management method capable of reducing traffic increase on a network and processing load on the data processing device.

[0002]

2. Description of the Related Art Several attempts have been made by a number of standards organizations to manage data processing devices (devices) on a network. The International Organization for Standardization (ISO) has established an open system between systems. Connection (Open Sys
tem Interconnection (OSI) model was provided. The OSI model of the network management protocol is based on the Common Management Information Protocol (Co
mmon Management Information Protocol (CMIP). CMIP is a common European network management protocol.

In the United States, a simple network management protocol (SN) is used as a more common network management protocol.
There is a variant of the protocol related to CMIP called MP). ("Introduction to TCP / IP Network Management Aiming at Practical Management" MT Rose = Author / Takeshi Nishida =
(See the first edition issued by Toppan Co., Ltd. on August 20, 1992).

According to the SNMP network management technology,
The network management system includes at least one network management station (NMS), each of which is an SNMP.
Includes several managed nodes, including agents, and network management protocols used by management stations and SNMP agents to exchange management information. The user can acquire and change data on the network by communicating with the SNMP agent software on the managed node using the network management software on the NMS.

[0005] An SNMP agent is software that runs as a background process for each target device. In contrast, the NMS and the network management software operating on the NMS are generally SN
Called MP manager.

When the SNMP manager requests management data from a device on the network by a user operation, the SNMP manager sends the object identification information in a management packet or frame to the target agent. The SNMP agent interprets the object identification information, extracts data corresponding to the object identification information, puts the data in a packet, and sends it back to the SNMP manager. Occasionally, a corresponding process is called to retrieve the data.

[0007] The SNMP agent holds data on its own status in the form of a database. This database is called MIB (Management Informatio
n Base). FIG. 8 is a conceptual diagram showing the structure of the MIB. As shown in FIG. 8, the MIB has a tree-structured data structure, and all nodes are uniquely numbered. In FIG. 8, the number written in parentheses is the identifier of the node.

For example, in FIG. 8, the identifier of the node 901 is 1. The identifier of the node 902 is the node 901
Since it is 3 below, it is written as 1.3. Similarly, the identifier mgmt (2) of the node 903 is described as 1.33.6.1.2.

This node identifier is called an object identifier (OBJECT IDENTIFIER). This MIB has a management information structure (SMI: Structure of Managemen).
t Information), RFC1155 Structure and Ide
ntification of ManagementInformation for TCP / IP-ba
sed Internets.

FIG. 8 shows an MI defined as a standard.
Among B, only a part is extracted and described.
Reference numeral 904 denotes a node serving as the top of an object group called a standard MIB provided as standard in a device managed by SNMP. The detailed structure of an object under this node is described in RFC1213 Management Informatlon Bas.
e for NetworkManagement of TCP / IP-based internets:
It is specified in MIB-II.

Reference numeral 905 denotes a node which is a vertex of an object group called a printer MIB provided as a standard in a printer managed by SNMP. The detailed structure of an object under this node is described in RFC 1759 Pri.
nter MIB.

Reference numeral 906 denotes a private MIB, which is a node serving as a vertex for companies and organizations to define their own MIB. A node 907 is called a company extension MIB, and is a node serving as an item for a company to perform its own extension in the private MIB. A company number 1602 is assigned to Canon Inc. as a company number in order to perform a unique definition, and a vertex node 908 for defining Canon MIB (Canon MIB) which is a unique MIB of Canon is a node representing a company. Node 907
Is located below. The object identifier of the vertex node of the Canon MIB is 1, 3, 6, 1, 4, 1, 160
2.

In SNMP, the following messages are used to check and set the MIB variables of the SNMP agent.・ GET REQUEST message (from SNMP manager to SNMP agent) Read specified MIB variable ・ GET NEXT REQUEST message (from SNMP manager to SN
Reads the next value of the specified MIB variable according to the order of the MIB. ・ GET RESPONSE message (from SNMP agent to SN)
Response to request (GET / GET NEXT / SET REQUEST) from SNMP agent ・ SET REQUEST message (from SNMP manager to SNMP agent) Set value specified in MIB variable ・ TRAP message (from SNMP agent to SNMP) To the manager) The occurrence of abnormalities and events from the SNMP agent to SNMP
The SNMP message notified to the manager is composed of a version number, an SNMP community name, and a PDU (Protocol Data Unit). 1 (Abstract S
It conforms to the BER (Basic Encoding Rule) of the syntax notation 1).

The following five PDs corresponding to each message
U must be supported. -PDU for Get Request-PDU GET REQUEST message-PDU for Get Next Request-PDU GET NEXT REQUEST message-PDU for Get Response-PDU GET RESPONSE message-PDU for Set Request-PDU SET REQUEST message -PDU for Trap-PDU Trap message The data format of these PDUs (Trap-PDU
FIG. 9).

Referring to FIG. 1, reference numeral 201 denotes an SNMP message; 202, an area for storing SNMP version information; 203, one SNMP agent to be managed by SNMP and one or more S agents managing the SNMP agent;
This is an area for setting the name of a community (community name) in which NMP managers are grouped. The SNMP agent compares it with the community name to which it belongs,
Accept the request only if they match. 204 is each S
An area where NMP PDU is stored, 205 is a PD
Indicates U. The SNMP message contains the type of the message (GET REQUEST, GET NEXT REQUEST, SE) in the header of the PDU.
T REQUEST).

206 is GET REQUEST, GET NEXT REQUES
A request ID set by the SNMP manager at the time of T, SET REQUEST request is set. The SNMP agent sets the same value in the GET RESPONSE of the response so that the SNMP manager can determine which request the response is to. An area 207 stores an error status. The error status is used for notification (GET RESPONSE) from the SNMP agent to the SNMP manager when there is an error in the SNMP message requested by the SNMP manager.
DU sets noError.

There are the following errors that can be notified as an SNMP agent.・ NoError: Normal (no error). TooBig: The resulting response was converted to an SNMP message, which exceeded the length limit of the SNMP agent. -NoSuchName: The specified object name cannot be found. In the case of GET NEXT REQUEST, this error is returned at the end of the search. -BadValue: The length, type, and value of the object specified by SET REQUEST are incorrect. • readOnly: SET REQUEST was requested for an object that can only be read. -GenErr: An error other than the above occurred on the SNMP agent side. An area 208 stores an error index indicating the number of an object in the requested SNMP message that has an error.

209 is an object name (210, 21)
2) and an array (variable-
bindings) is the variable binding area where the bindings are stored. Thus, SNMP messages can store requests for multiple objects in one message.

FIG. 10 shows an SNMP manager.
For a certain SNMP agent (Agent1), multiple objects (ObjectA, Ob
FIG. 4 is a sequence diagram when acquiring setting values of (jectB, ObjectC). In FIG. 10, for the sake of simplicity, only the error status area 207 and the variable connection area 209 of the PDU 205 in the message structure shown in FIG. 9 are described.

In FIG. 10, first, the Manager is Agent1
A GET REQUEST message 401 is sent to obtain the values of ObjectA, ObjectB, and ObjectC. In response, Agent 1 sends a GET RESPONSE message 402 to notify Manager of the values, X1, Y1, and Z1, set in the respective objects.

FIG. 11 shows an SNMP manager.
Uses broadcast packets to send multiple SNMP agents (Agent1, Agent1,
FIG. 11 is a sequence diagram when the same operation as in FIG. 10 is performed on Object2, Object3).

First, the Manager sends Agent1, Agent2 and Agent3 connected to the network to the Object
A GET REQUEST message 501 is transmitted by a broadcast packet for acquiring the values of A, ObjectB, and ObjectC.

Next, the Agent 1 responds to the broadcast packet 501 sent from the Manager, and returns a GET RESPONSE message 502 to notify the set values X1, Y1 and Z1 of the requested object.

Similarly, the set values X2, Y2, Z2 and X3 of the plurality of objects for which Agent 2 and Agent 3 are requested
GET RESPONSE messages 503 and 504 are returned to notify Y3 and Z3. Note that the response order of the Agents 1 to 3 can be any order.

As described above, when information is to be obtained using a broadcast packet, all of the S connected to the network and capable of communicating with the SNMP manager are obtained.
The NMP agent returns a response.

In FIG. 12, the same operation as in FIG. 11 is performed for a plurality of SNMP agents. In this sequence, the Manager has a function of retransmitting a packet (message) notified of an error in the response, and
3 is that if the requested setting values of ObjectA, ObjectB, and ObjectC are notified to the Manager by one SNMP message GET RESPONSE, the data length exceeds the data length of the packet that Agent 3 can send, and an error (error It is assumed that the value of the status area 207 is “tooBig”).

In the figure, first, an SNMP message by a broadcast packet for acquiring the values of ObjectA, ObjectB, and ObjectC from Agent to Agent1, Agent2, and Agent3 connected to the network.
GET REQUEST 601 is sent.

Next, Agent 1 returns a GET RESPONSE message 602 to notify the set values X1, Y1 and Z1 of the requested object in response to the broadcast packet 601 sent from the Manager.

Similarly, Agent 2 responds to the broadcast packet 601 sent from the Manager, and returns a GET RESPONSE message 603 to notify the set values X2, Y2 and Z2 of the requested object.

Similarly, a GET RESPONSE message 604 is sent from Agent 3, but the requested object (Obje
(ctA, ObjectB, ObjectC) when notifying the Manager of the setting value, the data length exceeds the data length of the packet that can be transmitted by Agent3, so a “tooBig” error occurs and the error status of the GET RESPONSE message 604 The value of the area is a value indicating a tooBig error.

Agent 3 receives a GET RESPONSE message 6
When "04" is returned, as a general operation of the SNMP agent, when a request from the SNMP manager cannot be processed normally, NULL is set to the value of the object notified to the SNMP manager by GET RESPONSE.

Since the Manager has a function of retransmitting the message notified of the error as described above, the error of the SNMP message GET RESPONSE from the Agent 3 (“tooBi
g ”), the broadcast packet 605 having the same contents as the broadcast packet 601 is retransmitted.

In response to this, Agent1, Agent2, and Agent3 again transmit the same GE messages as GET RESPONSE messages 602 to 604.
Return T RESPONSE messages 606-608.

Further, network management software for retransmitting an errored request is generally conventional.

[0035]

As described above, according to the conventional method, when an error occurs in the GET RESPONSE for notifying the setting value of the object requested by the SNMP manager, the SNMP manager makes the request. Data regarding the object cannot be obtained, which has been a significant obstacle in controlling network devices by SNMP. In particular, one SN that is a feature of SNMP
When processing for a plurality of objects is requested by the MP message, the possibility of such a situation increases.

In the conventional method, retransmission of an erroneous message is performed irrespective of the type of a request message. Therefore, when a broadcast packet is used, an SNMP agent including information for which information has already been obtained can be used. All SNMs connected to the network
The request is sent again to the P agent,
This was a significant impediment to network traffic and the operation of network devices.

Accordingly, a first object of the invention according to the present application is to provide a network management method capable of acquiring data as much as possible even when an error response is returned to a message. .

The second object of the invention according to the present application is as follows.
An object of the present invention is to provide a network management method capable of efficiently performing data acquisition using an SNMP message by a broadcast packet.

[0039]

That is, the first aspect of the present invention is as follows.
The gist of the invention is that a request message for requesting the managed device to perform a predetermined process is transmitted from the management device to at least one managed device connected to the management device via a network, and the managed device sends the request message in the request message. Performed processing, in a network management method for managing the network including the management device and the managed device by returning the result as a response message, a transmission step of transmitting a request message,
A determination step of determining whether a response message to the request message includes information indicating an error, and if the determination step determines that the message includes information indicating an error, the same as the request message transmitted in the transmission step Retransmitting a request message of another type including a request.

Preferably, in the first aspect, the request message transmitted in the transmitting step is in a broadcast message format, and the retransmitting step includes a response message determined in the determining step to include information indicating an error. A detecting step of detecting the transmitted managed device; and a retransmitting message generating step of generating a retransmitting request message in a non-broadcast message format having the same request content as the broadcast message, and detecting the retransmitting request message. 2. The network management method according to claim 1, wherein the transmission is performed to the managed device detected in the step.

Preferably, in the first aspect, the request message transmitted in the transmitting step has a message format requesting a plurality of processes, and the retransmitting step includes:
A retransmission message generation step of generating a plurality of retransmission request messages assigned by dividing a plurality of processes,
A network management method characterized by retransmitting a retransmission request message.

Preferably, in the first aspect, the request message transmitted in the transmitting step is a broadcast message format requesting a plurality of processes, and the detecting step includes an error type detecting step of detecting an error type. A detecting step of detecting the managed device that has transmitted the response message determined to include the information indicating the error in the determining step, and a re-transmitting step when the error type is a predetermined error type. A plurality of non-broadcast message format retransmission request messages assigned by dividing the above process, and if the error type is other than the above, the non-broadcast message format retransmission And a retransmission message generation step of generating a request message. If the error type is a predetermined error type, Transmitting a request message to the managed device detected in the detecting step, and, if the error type is other than the error type, to the managed device other than the managed device detected in the detecting step. Exist.

According to another aspect of the present invention, a request message for requesting a predetermined process is transmitted to at least one managed device connected to a network, and a response message to the managed device request message is analyzed. A management device for managing a network and / or a managed device, comprising: a transmission unit that transmits a request message; and a determination unit that determines whether a response message to the request message includes information indicating an error. Resending means for resending a request message of another format including the same request as the request message transmitted by the transmitting means when the determining means determines that the information includes information indicating an error. Exist in the device.

Another aspect of the present invention is a storage medium storing a program that can be executed by an apparatus. The storage medium that has executed the program is transferred to at least one managed device connected to a network by a predetermined process. A management device for transmitting a request message for requesting the managed device, analyzing a response message to the managed device request message, and managing the network and / or the managed device, and transmitting means for transmitting the request message; A determination unit that determines whether a response message to the message includes information indicating an error, and, if the determination unit determines that the message includes information indicating the error, the request is the same as the request message transmitted by the transmission unit. Resending means for resending another type of request message including Resides in a storage medium, characterized in that.

[0045]

DESCRIPTION OF THE PREFERRED EMBODIMENTS (First Embodiment) A network device control apparatus and method including network management software using SNMP according to the present invention will be described below with reference to the drawings.

(Hardware Configuration) FIG. 1 is a block diagram showing the configuration of a data processing device (PC) on which network management software according to the present invention can operate. In FIG. 1, reference numeral 701 denotes a PC on which network management software operates. The PC 701 executes a network management program stored in the ROM 703 or the hard disk (HD) 712 or supplied from the floppy disk drive (FD) 713.
02, and comprehensively controls each device connected to the system bus 705.

A RAM 704 functions as a main memory, a work area, and the like for the CPU 702. Reference numeral 706 denotes a keyboard controller (KBC), and a keyboard (KB) 71
It controls input of instructions from 0 or a pointing device (not shown). 707 is a CRT controller (CRTC)
Controls the display on the CRT display (CRT) 711. A disk controller (DKC) 708 controls access to a hard disk (HD) 712 and a floppy disk controller (FD) 713 that store a boot program, various applications, editing files, user files, a network management program, and the like. A network interface card (NIC) 709 exchanges data with an SNMP agent or a network device via the LAN 700.

Next, the configuration of the network management software of the present invention will be described. The network management device of the present invention is realized on a PC having the same configuration as a PC capable of realizing the conventional network management device as shown in FIG. The hard disk (HD) 712 stores a program of network management software according to the present application, which is an operation main body in all the descriptions below. In all the following descriptions, the subject of execution is the CPU 702 on hardware unless otherwise specified. On the other hand, the subject of control on software is network management software stored in a hard disk (HD) 712. In the present embodiment, for example, Windows (registered trademark of Microsoft Corporation) 95 (product name) is assumed as the OS, but the OS is not limited to this.

The network management program according to the present invention may be supplied in a form stored in a storage medium such as a floppy disk or CD-ROM. In this case, a floppy disk controller (FD) 71 shown in FIG.
3 or a CD-ROM drive (not shown) reads a program from a storage medium and installs the program on a hard disk (HD) 712.

(Software Configuration) FIG. 2 is a module diagram showing an example of the module configuration of the network management software according to the present invention.

The network management software according to the present invention is stored in the hard disk 712 in FIG. At that time, CP
U702 uses the RAM 704 as a work area.

In FIG. 2, reference numeral 801 denotes a device list module which displays a list of devices connected to the network. Reference numeral 802 denotes an overall control module that supervises other modules based on instructions from the device list. Reference numeral 803 denotes a configurator module that performs special processing related to the network setting of the SNMP agent. A search module 804 searches for a device connected to the network. Devices searched by the search module 804 are displayed as a list in a device list 801.

Reference numeral 805 denotes the status of the print job in Net Wa.
Get from network server using re API816
Net Ware job module. (Note that Net Ware A
Regarding PI, for example, “Ne
t Ware Programmer's Guide for C ", etc. This book can be purchased from Novell, Inc.) 806
Reference numerals 807 and 807 denote UI modules for displaying a device detail window for displaying more detailed information according to the type of device. There is a UI module for each target model for displaying detailed information. 808 and 8
Reference numeral 09 denotes a control module which is responsible for control specific to the target model from which detailed information is acquired. As with the UI module, a control module exists for each target model for displaying detailed information. The control A module 808 and the control B module 809 obtain MIB data from the device to be managed using the MIB handling module 810, convert the data as necessary, and correspond to the corresponding UIA module 806 or UIB module 80, respectively.
Pass the data to 7.

The MIB handling module 810 includes:
Overall control module 802, control A module, control B
Information (community name, object identifier, etc.) necessary for generating an SNMP message in response to a request from the module is notified to the SNMP module 811.

Reference numeral 811 denotes an SNMP module.
Send and receive packets. A common transport module 812 absorbs a difference between lower protocols for transporting SNMP data. In practice, depending on the protocol selected by the user during operation, I
Either the PX handler 813 or the UDP handler 814 plays a role in transferring data. The UDP handler uses WinSock 817 as an implementation. (WinSock
For details, refer to the specification of Windows Socket APIv1.1, for example. This document is available from multiple sources, but is bundled with, for example, Visual C ++ (product name), a Microsoft compiler. )

The current protocol 815 used by the configurator 803 indicates either the IPX protocol or the UDP protocol selected by the user during operation.

(Operation of Software) FIG. 3 is a flowchart showing the operation of the network management method according to the first embodiment of the present invention. This embodiment is a process when an SNMP message for one Object is transmitted using a broadcast packet.

In step S201, one Object
Is transmitted using a broadcast packet. Next, a timer for setting a time limit from packet transmission to response reception is checked (step S202), and if not timed out, response reception is waited for (step S203). When the response is received, the error status area of GetResponsePDU is checked to determine whether an error has occurred (step S204). If no error has occurred, the process returns to step S202 to receive the next response. On the other hand, if an error has occurred, GetResponseP
From the DU object identifier area, Ag where the error occurred
The address of ent is detected (step S205). Then, except that the detected address is designated, step S20
The same SNMP message as that transmitted in step 1 is transmitted (step S206), and the process returns to step S201. If a timeout occurs in step S201, the process ends.

By such processing, even if an error response is returned to the SNMP message using the broadcast packet, a normal response is returned because the broadcast packet does not need to be retransmitted.
There is no need for the Agent to perform the processing again, the addition of the processing can be reduced, and the network resources used for transmitting the message and returning the response can be largely saved.

(Second Embodiment) FIG. 4 is a flowchart showing the operation of the network management method according to the second embodiment of the present invention. The present embodiment is processing when an SNMP message for a plurality of objects is transmitted using a non-broadcast packet.

First, SNMP for a plurality of objects
Sends a message to a certain Agent (step S30)
1). Waits for a response from the Agent (step S302), and returns a GetResponseP
The error status area of the DU is checked to determine whether an error has occurred (step S303). If there is no error, the process ends normally. On the other hand, if an error has occurred, it is determined whether the type is a tooBig error (step S304). In the case of a tooBig error, it is highly likely that the problem will be solved by reducing the number of objects requested at one time. Therefore, the message is reconfigured to request one Object with one SNMP message (step S308).
It resends (step S307).

On the other hand, if it is an error other than a tooBig error in step S304, a plurality of requested Obje
GetR to find out which object of ct caused the error
It is detected from the error index area of the responsePDU (step S305). Then, an SNMP message is created again except for the Object in which the error has occurred (step S3).
06), and resend (step S307). Step S3
At 06, as if a tooBig error occurred,
An SNMP message may be created for each Object.

By performing such processing, even in the case of performing retransmission processing of a message corresponding to the return of an error response, it is possible to request only a necessary Object. Agent on request
In addition to reducing the processing load, unnecessary increase in network traffic can be suppressed.

It should be noted that the response of the SNMP message retransmitted after the occurrence of the tooBig error is repeated in FIG.
By applying the processing from step S302 onward,
It can also be applied when other errors have newly occurred.

(Third Embodiment) FIG. 5 is a flowchart for explaining the operation of the network management software according to the third embodiment of the present invention. In the present embodiment, an operation in a case where acquisition of data for a plurality of objects is attempted by an SNMP message using a broadcast packet will be described. In the present embodiment, tooBig
Only the handling of the error will be described, but it goes without saying that the processes described in the second embodiment can be combined.

In the figure, in step S100, the user uses the keyboard (KB) 710 or an input device such as a mouse with the PC 701 to input a hard disk (H).
D) Activate the network management software according to the present invention stored in 712 and operate to acquire and set information for the network device to be managed. With this operation, the device list module 801,
A request is generated from one of the UIA module 806 and the UIB module 807, and the API of the MIB handling module 810 is called from the control module of the general control module 802, the control A module 808, or the control B module 809 in response to the request. Is done.

In step S101, the parameters of the API called in step S100 are analyzed in order to acquire and set information on the network device to be managed, and the SN for the appropriate object is analyzed.
Send an MP message. In response to this, the SNMP module 811 generates an SNMP message according to the request, and notifies the common transport module 812 of the message. The common transport module 812 transfers data to either the IPX handler 813 or the UDP handler 814 according to a protocol selected by the user during operation. After the above operation, the SNMP message is transmitted to the LAN 700 via the network interface card (NIC) 709.

In step S102, step S101
SNMP message (GET REQUEST, GE
An SNMP message (Get Response) is received from the network device to be managed via the network interface card (NIC) 709 as a response to T NEXT REQUEST, SET REQUEST). Received SN
The MP message has I
The SNMP module 811 is notified from the common transport module 812 to the SNMP module 811 via one of the PX handler 813 and the UDP handler 814, and the SNMP module 811 analyzes the received SNMP message.

In step S103, the SNMP module 811 receives the SNMP message received in step S102.
The PDU 205 of the message (Get Response) is analyzed. Here, the error status 2 of the PDU 205
Referring to FIG. 07, if the response was successfully received, the result is notified to the MIB handling module 810. If an error has occurred, the process proceeds to step S10.
Move to 4.

In step S104, the SNMP module 811 determines whether the error detected in step S103 is "tooBig".
If it is “ig”, the process moves to step S104, and if it is any other error, it notifies the MIB handling module 810 of the error.

In step S105, step S101
Variable-bindi of the SNMP message sent in
It is determined in the SNMP module 811 whether or not a plurality of objects are included in the ngs 209,
If it is composed of one object,
The occurrence of “tooBig” is notified to the MIB handling module 810, and if it is configured by a plurality of objects, the process proceeds to step S105.

In step S106, step S101
Of the PDU 205 of the SNMP message transmitted in
If it is determined that the variable-bindings 209 is composed of a plurality of objects, the SNMP module 811 generates an SNMP message for each single object.

In step S107, step S101
A determination is made whether the SNMP message transmitted in is due to a broadcast packet,
If it is a broadcast packet, step S
Move to 108.

In step S108, step S102
In step S106, the address of the SNMP agent is detected from the received SNMP message (Get Response).
It is specified as the destination address of the NMP message.

In step S109, the newly generated SN is divided for each single object in step S106.
The MP message is transmitted to the common transport module 812.
, And the common transport module 812 uses the protocol selected by the user during operation to
The data is transferred to either the PX handler 813 or the UDP handler 814. After the above operation, the newly generated SNMP message is transmitted to the LAN 700 via the network interface card (NIC) 709.

As described above, the response of the SNMP message transmitted in step S101 is received in step S102, and if it is determined in step S103 that an error has occurred, it is determined whether "tooBig" has occurred in step S104. Is determined,
If it is "tooBig", it is determined in step S105 whether the request is for a plurality of objects. If it is determined that the request is for a plurality of objects, in step S106, a plurality of SNMPs are set for each single object. The message is divided into messages, and in step S107, the SN transmitted in step S101
It is determined whether the MP message is a broadcast packet. If the MP message is a broadcast packet, the process proceeds to step S107 in step S107.
2. The agent address is detected from the object identifier area of the SNMP message received in
In step S106, the object causing the error is detected. In step S106, the object is designated as the destination address of the SNMP packet divided for each single object, and transmitted in step S109. Request for data processing of the object of the request, the data length of the response exceeds the data length of the packet that can be sent by the SNMP agent, and "tooBig"
Occurs, a request for a plurality of objects included in the transmitted SNMP message is divided into a request for a single object, and the request is transmitted.
Prevents the occurrence of "tooBig" on the P agent side, and enables efficient acquisition and setting of information.

Further, S by broadcast packet
When an error occurs in the response of the NMP message, the agent address is detected from the received response, and the SNMP message is transmitted by specifying the address, thereby eliminating unnecessary responses from the SNMP agent and reducing network traffic. , And unnecessary operation of the network device can be prevented.

FIG. 6 shows that the network management software according to the present invention uses SNMP by a broadcast packet.
Multiple objects (ObjectA, ObjectB, O
FIG. 14 is a sequence diagram in a case where acquisition of a setting value with respect to bjectC) is requested.

Note that, in FIG.
SNMP agents that can communicate with r) are Agent1 and Agent
2. Agent3, Agent3 is Obje sent from Manager
"tooBig" in the response of the SNMP message requesting acquisition of the setting values for ctA, ObjectB, and ObjectC
Is assumed to occur.

The sequence will be described below.
An SNMP message GET RE requesting the SNMP agent that can communicate with the Manager to obtain the setting values for multiple objects, ObjectA, ObjectB, and ObjectC.
QUEST is transmitted by the broadcast packet 301.

Agent 1 notifies SN of the set values of ObjectA, ObjectB, ObjectC, X1, Y1, Z1 to Manager.
The MP message GET RESPONSE 302 is returned. Agent2 is Ob
Set value of jectA, ObjectB, ObjectC, X2, Y2, Z2
GET RESPO SNMP message to notify Manager
Returns NSE 303.

Set value of ObjectA, ObjectB, ObjectC, X
SNMP message GE for notifying 3, Y3, Z3
Since T RESPONSE exceeds the data length that can be transmitted by Agent3, the error status 207 is set to “tooBig” and GET RESPONSE 304 is returned.

Next, Age when the Manager generates “tooBig”
Analyzes GET RESPONSE from nt3, detects the address of Agent3, and requests SN to obtain the set value for ObjectA
The MP message GET REQUEST 305 is sent by specifying the address of Agent3.

The Manager similarly obtains an SNMP message GET requesting acquisition of the set values for ObjectB and ObjectC.
REQUESTs 306 and 307 are transmitted by designating the address of Agent3.

In response to the divided request message 305, Agent3 returns an SNMP message GET RESPONSE308 to notify the Manager of the set value of ObjectA, X3.

Then, similarly, the request message 306
And 307, the set values of ObjectB and ObjectC, Y
SNMP to notify Manager 3 and Z3 respectively
Messages GET RESPONSE 309 and 310 are returned.

As described above, when the GET REQUEST for a plurality of objects by the broadcast packet 301 transmitted by the Manager is not properly processed on the SNMP agent side and “tooBig” occurs in the GET RESPONSE 304 from the Agent 3, the Manager GET RES received
In addition to detecting the address of Agent 3 in which an error has occurred from PONSE 304, generating a GET REQUEST for each single object from information on multiple objects included in transmitted GET REQUEST 301, specifying the address of detected Agent 3, and requesting Messages 305, 30
By transmitting 6,307, the occurrence of "tooBig" in the SNMP agent can be prevented, and unnecessary SNMP messages from the SNMP agent due to retransmission of broadcast packets can be eliminated. It is possible to dramatically improve the efficiency of information acquisition and setting.

[0088]

[Other Embodiments] In the above embodiment, the SNMP
Although the case in which the present invention is applied to the network management using is described, it goes without saying that the present invention can be applied to other network management protocols having similar functions.

The network management software according to the present invention described above is executed by a PC 701 in FIG. 1 which is a block diagram showing a configuration of a PC on which the network management software can operate, by a program installed from the outside. Is also good. In this case, the program is stored in a storage medium such as a CD-ROM, a flash memory or a floppy disk, or an information group including the program from an external storage medium via a network such as e-mail or personal computer communication.
The present invention is applied even when the data is loaded on the PC 701 and supplied to the PC 701.

FIG. 7 shows a CD-RO as an example of a storage medium.
FIG. 6 is a diagram showing a memory map of M. An area 1003 stores directory information, and indicates the positions of an area 1002 storing an installation program and an area 1001 storing network management software. An area 1002 stores an installation program. An area 1001 stores network management software. When the network management software of the present invention is installed on the PC 701, first, the installation program stored in the area 1002 storing the installation program is loaded into the system and executed by the CPU 702. Next, the installation program executed by the CPU 702 reads the network management software from the area 1001 in which the network management software is stored, and stores the network management software on the hard disk 712.

The present invention can be applied to a system or an integrated device including a plurality of devices (for example, a host computer, an interface device, a reader, etc.).
You may apply to the apparatus which consists of one apparatus.

A storage medium storing software program codes for realizing the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus is stored in the storage medium. Needless to say, the object of the present invention can be achieved by reading and executing the program code.

In this case, the program code itself read from the storage medium realizes the new function of the present invention, and the storage medium storing the program code constitutes the present invention.

Examples of a storage medium for supplying the program code include a floppy disk, hard disk, optical disk, magneto-optical disk, CD-ROM,
DR, magnetic tape, nonvolatile memory card, ROM
Etc. can be used.

The functions of the above-described embodiments are implemented when the computer executes the readout program codes. In addition, the OS or the like running on the computer performs actual processing based on the instructions of the program codes. The functions of the above-described embodiment can be realized by performing a part or all of the above.

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, based on the instructions of the program code, A CPU or the like provided in the function expansion 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.

The present invention is 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. Needless to say, this can also be applied.

[0098]

As described above, according to the network management method of the present invention, in the network management method capable of requesting a plurality of objects by one message, even if an error occurs on the response side, the efficiency is improved. This has the effect that good information collection becomes possible.

Further, according to the present invention, when an object is requested at a plurality of places using the broadcast function, even if an error occurs at any place, the retransmission processing using the broadcast function is performed. Since the processing is not performed, the processing load on the responding side is reduced, and an increase in network traffic can be suppressed.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration example of a PC capable of implementing a network management method according to the present invention.

FIG. 2 is a diagram showing an example of a module configuration of software for implementing the network management method according to the present invention.

FIG. 3 is a flowchart showing an operation according to the first embodiment of the present invention.

FIG. 4 is a flowchart illustrating an operation according to a second embodiment of the present invention.

FIG. 5 is a flowchart illustrating an operation according to a third embodiment of the present invention.

FIG. 6 is a diagram showing a sequence in a third embodiment of the present invention.

FIG. 7 is a diagram showing an example of a memory map when the present invention is described in the form of a program.

FIG. 8 is a conceptual diagram showing the structure of an MIB.

FIG. 9 is a diagram showing a PDU data format (other than Trap-PDU) of an SNMP message.

FIG. 10 is a diagram showing a conventional sequence when processing data for a plurality of objects is requested by an SNMP message.

FIG. 11 is a diagram showing a conventional sequence when processing data for a plurality of objects is requested by an SNMP message by a broadcast packet.

FIG. 12 is a diagram showing a conventional sequence in a case where processing of data for a plurality of objects is requested by an SNMP message using a broadcast packet and an “tooBig” error occurs in the SNMP agent.

[Explanation of symbols]

201 SNMP message (other than Trap) 202 Version information 203 Community name 204 Data 205 PDU 206 Request ID area 207 Error status area 208 Error index area 209 Variable bindings area 700 Local area network (LAN) 701 PC 702 CPU 703 ROM 704 RAM 705 System bus 706 Keyboard controller (KBC) 707 CRT controller (CRTC) 708 Disk controller (DKC) 709 Network interface card (NIC) 710 Keyboard (KB) 711 CRT display (CRT) 712 Hard disk (HD) 713 Floppy disk Drive (FD) 801 Device list module 802 Overall control module 803 Configurator 804 Search module 805 NetWare job module 806 UI module A 807 UI module B 808 Control module A 809 Control module B 810 MIB handling module 811 SNMP module 812 Common transport module 813 IPX handler 815 UDPR The current protocol used by 816 NetWare API 817 WinSock

Claims (18)

[Claims] 1. A request message for requesting a predetermined process from a managed device is transmitted from a management device to at least one managed device connected to the management device via a network, and the managed device sends the request message to the managed device. In a network management method for managing a network including the management device and the managed device by performing a process requested by a request message and returning a result as a response message, a transmission step of transmitting the request message; A determining step of determining whether or not the response message to the request message includes information indicating an error; and if it is determined that the determining step includes information indicating an error, the transmitting step includes transmitting the information. Another form of request containing the same request as the request message A retransmission step of retransmitting the message. 2. The method according to claim 1, wherein the request message transmitted in the transmitting step is in a broadcast message format, and the retransmitting step transmits the response message determined to include information indicating an error in the determining step. A detecting step of detecting a management device; and a retransmission message generating step of generating a retransmission request message in a non-broadcast message format having the same request content as the broadcast message, wherein the detecting includes detecting the retransmission request message. 2. The network management method according to claim 1, wherein the transmission is performed to the managed device detected in the step. 3. The request message transmitted in the transmitting step has a message format requesting a plurality of processes, and the retransmitting step generates a plurality of retransmission request messages obtained by dividing and assigning the plurality of processes. 2. The network management method according to claim 1, further comprising a message generating step, wherein the retransmission request message is retransmitted. 4. The method of claim 3, wherein the predetermined error is an error exceeding a length limit of the response message.
The described network management method. 5. The request message transmitted in the transmitting step is a broadcast message format requesting a plurality of processes, the detecting step includes an error type detecting step of detecting the type of the error, and the retransmitting step includes: A detecting step of detecting the managed device that has transmitted the response message determined to include information indicating an error in the determining step; and A plurality of non-broadcast message format retransmission request messages assigned by dividing the processing, and if the error type is other than the above, the non-broadcast message format retransmission A retransmission message generation step of generating a request message, wherein the error type is a predetermined error type Transmitting the retransmission request message to the managed device detected in the detection step, and if the error type is other than the error type, to the managed device other than the managed device detected in the detection step. The network management method according to claim 1, wherein: 6. The method according to claim 5, wherein the predetermined error is an error exceeding a length limit of the response message.
The described network management method. 7. The method according to claim 1, wherein the request message, the response message, and the retransmission request message are SNMP (Simple) messages.
7. The network management method according to claim 1, wherein the network management method is a Network Management Protocol message. 8. A request message requesting a predetermined process is transmitted to at least one managed device connected to a network, and a response message to the managed device is analyzed by analyzing the response message to the network and / or the managed device. A management device that manages the managed device, a transmission unit that transmits the request message, and a determination unit that determines whether the response message to the request message includes information indicating an error. Resending means for resending a request message of another format including the same request as the request message sent by the sending means when it is determined that the information indicating the error is included by the judging means. To manage devices. 9. The request message transmitted by the transmitting means is in a broadcast message format, and the retransmitting means transmits the response message determined by the determining means to include information indicating an error. Detecting means for detecting a management device; and retransmission message generating means for generating a retransmission request message in a non-broadcast message format having the same request content as the broadcast message, wherein the retransmission request message is detected. 9. The management device according to claim 8, wherein the device is transmitted to the managed device detected by the means. 10. A request message transmitted by the transmitting unit is a message format requesting a plurality of processes, and the retransmitting unit generates a plurality of retransmission request messages divided and assigned to the plurality of processes. A message generating means,
The management device according to claim 8, wherein the retransmission request message is retransmitted. 11. The management device according to claim 10, wherein the predetermined error is an error exceeding a length limit of the response message. 12. The request message transmitted by the transmission unit is a broadcast message format requesting a plurality of processes, the detection unit has an error type detection unit for detecting the type of the error, and the retransmission unit is Detecting means for detecting the managed device that has transmitted the response message determined to contain information indicating an error by the determining means; and A plurality of non-broadcast message format retransmission request messages assigned by dividing the processing, and if the error type is other than the above, the non-broadcast message format retransmission Retransmission message generating means for generating a request message, wherein when the error type is a predetermined error type, the retransmission request message And transmitting, to the managed device detected by the detection unit, and to the managed device other than the managed device detected by the detection unit if the error type is other than the error type. 8. The management device according to 8. 13. The management device according to claim 12, wherein the predetermined error is an error exceeding a length limit of the response message. 14. The method according to claim 14, wherein the request message, the response message, and the retransmission request message are SNMP (Simplified) messages.
14. The management device according to claim 8, wherein the management device is an e-Network Management Protocol) message. 15. Apparatus configured to perform the method of any of the preceding claims. 16. A network system comprising the management device according to claim 8. 17. A storage medium storing a program executable by an apparatus, the method comprising: sending a request message requesting at least one managed device connected to a network to perform predetermined processing to the apparatus that has executed the program. A management device for transmitting and managing the network and / or the managed device by analyzing a response message to the request message to the managed device, wherein: a transmitting unit for transmitting the request message; Determining means for determining whether or not the response message includes information indicating an error; and determining that the response message includes information indicating an error, the request message transmitted by the transmitting means. Resending means for resending another type of request message containing the same request. Storage medium characterized by operating as a chair. 18. A storage medium storing a method according to claim 1 in a program format executable by an apparatus.