JPH11205320A - Network management method - Google Patents

Abstract

An object of the present invention is to simplify network management by enabling management as one node in network management by SNMP even when a plurality of routers are connected due to an increase in the number of lines. In a device configuration in which a plurality of network connecting devices are connected by a device connecting switch, a representative network connecting device is determined from operating routers in accordance with a priority determined in advance by a configuration definition. The representative network connecting device manages access to the logical data structure (MIB) of the management information held by the agent as a local manager for the SNMP agent on each network connecting device including its own device. In response to an access request to the MIB from the SNMP manager operating on the management device, the device operates and responds as an agent on a single virtual device that holds the above-mentioned MIB collectively.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a network management technique, and more particularly to a network management technique suitable for network management in a configuration in which a plurality of inter-network connecting devices such as routers are connected.

[0002]

2. Description of the Related Art When the required number of lines exceeds the number of lines that can be accommodated by a router due to expansion of a network, a router is added as one method for securing the required number of lines. Assignment of a managed router name occurs due to the addition of routers, and SNMP (Simple Network)
When automatically drawing a network configuration as a map with a management protocol (Manager) manager, network management becomes complicated due to an increase in the number of symbols displayed on one screen.

[0003]

In the above prior art, an increase in the number of lines directly leads to an increase in the number of managed routers, and a work of assigning a managed router name occurs.
Also, in the network management by the SNMP manager, the number of symbols displayed on the screen as the network configuration increases, so that the network management becomes complicated.

An object of the present invention is to provide a network management method capable of suppressing an increase in managed routers and facilitating maintenance and operation of a network even when a plurality of inter-network connecting devices such as routers are connected. To provide.

[0005]

SUMMARY OF THE INVENTION In a device configuration in which a plurality of network connecting devices are connected by a device connecting switch, a representative network is selected from routers in operation according to a priority determined in advance by a configuration definition. The network connection device is determined, and the representative network connection device acts as a local manager for the SNMP agent on each network connection device including its own device, and the logical data structure (MI
B) manages access to B) and operates as an agent on a single virtual device that collectively holds the MIB in response to an MIB access request from an SNMP manager operating on a network management device. ,respond.

[0006]

Embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 1 shows a configuration example of a router connected by an inter-device connection switch. In this example, the lines (10a, 10a
router (10) accommodating b), router (11) accommodating line (11a), line (12a, 12b, 12c)
The router (12) that accommodates the
0) via a housing connection link (50).

[0008] It is assumed that the routing information of each router is synchronized so that the same routing table is obtained, and each router can identify the operating state of another router by a health check.

FIG. 2 is a diagram showing a MIB (Man) according to a request from an SNMP manager operating on a network management apparatus.
(Agement Information Base)
FIG. 3 is a diagram for explaining a functional configuration of management by SNMP when making access.

FIG. 3 shows a PDU (Protococo) of SNMP.
FIG. 3 is a diagram illustrating a format of (l Data Unit).

FIG. 4 is a view for explaining the configuration of the instance index management table. The external index is used between the SNMP manager and the router (10), (11) and (12) when the router is regarded as one router. Is a value that specifies the MIB (managed object) to be operated, and the internal index is the SN within each router.
This value specifies the corresponding MIB for the MP agent. The router identification is information that uniquely indicates a router that manages the MIB.

FIG. 5 shows an example of values set in the instance index management table of the IF group in the device configuration shown in FIG.

FIG. 6 is a diagram showing an example of an operation sequence between SNMP function blocks at the time of initial startup.

FIG. 7 shows SNMP on the network management device.
FIG. 9 is a diagram illustrating an example of an operation sequence between SNMP function blocks when a MIB access request is issued from a manager.

In the following, at the time of initial startup, T
rap to the manager of the IF group
The operation will be described taking as an example a case where a GetRequest-PDU for B is received.

In the configuration of FIG. 1, the router (10, 1
When [1] and [12] start up when the power is turned on, a representative router for SNMP management is determined according to the priority defined by the configuration after the elapse of the initialization delay time defined by the configuration.

In this example, the priority of the three routers is (10)
If all of them have been normally started as>(11)> (12), the router (10) becomes the representative router for SNMP management.

The instance index management (10i) on the router (10) simulates the SN with respect to the SNMP agent (10e, 11e, 12e) on each router.
It operates as an MP manager and creates an instance index management table corresponding to the object group by a GetNext operation.

In the case of this example, the values shown in FIG. 5 are set in the interface index management table assigned to each interface by the operation shown in the sequence of FIG. 6 below.

Instance index management (10
Since e) collects the instance index of the interface group, the object identifier is 1.3.6 in the Name field for the SNMP agent (10e) of the router (10) according to the priority between routers defined in the configuration definition. .1.2.1.2.2.2.1.2.
GetN with instance index set to 0 in
The value of IfIndex is requested by transmitting extRequest-PDU (100).

The SNMP agent (10e) is Get
In the Value field of the NextRequest-PDU, the I corresponding to the interface of the line (10a) is set.
A response (10) is set by setting "1" which is the value of fIndex.
1) Yes.

Instance index management (10
i), when a normal response (101) is returned from the SNMP agent (10e), the value of Value is set as an internal index value corresponding to "1" which is the initial value of the external index value of the instance index management table; Update the instance index and send the next GetNextRequest-PDU (10
2) Do it.

Subsequently, the value of Value is sequentially set to the internal index value of the instance index management table, and the instance index is updated and GetNextReq until the information managed by the corresponding router disappears in response to the NoSuchName response.
The operation of transmitting the west-PDU is repeated.

When the response (105) of NoSuchName is received, the GetNextRequest-PD is sent to the SNMP agent (11e) of the router (11) having the next priority.
U is transmitted (110).

By repeating the above operation, the instance
Create an index management table.

The created instance index management table is distributed to the index management (11i, 12i) of each router so that the router of the next priority can operate as the representative router when the representative router fails. After the above operation is completed, the index management is performed by the SNMP manager (20 m) in the cold start trap (150).
Send

Next, according to FIG. 7, the object identifier is 1.3.6.
GetRequest-PDU whose instance index is set to “1” in 1.2.1.2.2.2.1.2
(200) from the line (12a) of the router (12)
The operation when this is done will be described.

In each of the routers (10), (11) and (12), all PDUs destined for the interface of the own router are transferred to the instance index management (10i) on the (10) which is the representative router for SNMP management. I do.

Instance index management (10
i) shows a PDU according to the index management table shown in FIG.
"4" which is the value of the instance index of the object identifier in "1" is converted to the internal index "1", and the object identifier is changed to 1.3.6.1.2.1.2.
It is reset to 2.1.2.4 and transmitted (210) to the SNMP agent (12e) of the router (12), which is the management source router determined by the management source router identification.

The SNMP agent (1
In 2e), the value of the object specified by the internal index is set in the value of GetResponse-PDU, and index management (10i) of the router (10) is performed.
(211).

In the index management (10i), when a response is received from the SNMP agent (12e) of the router (12), the internal index "1" is converted to the external index "4" and the object identifier of the GetResponse-PDU is set to 1.3. .6.1.2.1.2.2.2.
1.2.4 is set and transmitted to the SNMP manager via the line (12a) (220).

As described above, using the MIB of the IF group as an example,
The operation of the table type MIB has been described.

The non-table type MIB whose instance index is "0" such as the device name has the same information in each router, and the SNMP at that time.
By validating the MIB value of the representative router in management, it becomes possible to manage as one node in SNMP management.

[0034]

As described above, according to the present invention, even in an apparatus configuration in which a plurality of routers are connected by an inter-device connection switch, it can be managed as one router in network management, and the number of lines increases. As a result, it is possible to avoid an increase in the number of routers to be managed, thereby facilitating network management.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of an apparatus according to an embodiment of the present invention.

FIG. 2 is a functional configuration diagram of SNMP management according to an embodiment of the present invention.

FIG. 3 is an explanatory diagram of a format of an SNMP PDU.

FIG. 4 is a configuration diagram of an instance index management table.

FIG. 5 is an example of an instance index management table setting value.

FIG. 6 is an operation sequence diagram between SNMP function blocks at the time of initial startup.

FIG. 7 is an operation sequence diagram between SNMP function blocks at the time of an MIB access request.

[Explanation of symbols]

10-12: Router device, 10a, 10b, 11a, 1
2a, 12b, 12c ... line, 20 ... device connection switch, 50 ... housing connection link, 10i, 11i, 12i ...
Instance index management unit, 10e, 11e,
12e: SNMP agent, 20m: SNMP manager.

 ──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Yoshito Sako 810 Shimo-Imaizumi, Ebina-shi, Kanagawa Prefecture Hitachi Systems Ltd. Office Systems Division

Claims (1)

[Claims] In a device configuration in which a plurality of network connecting devices are connected by a device connecting switch, a representative network connecting device is selected from operating routers according to a priority determined in advance by a configuration definition. The network management device determines and determines access to the logical data structure of management information held by the agent as a local manager for the SNMP agent on each of the network connection devices including the own device. A network management unit that operates and responds to an access request to the data structure from an SNMP manager operating on the virtual machine as an agent on a single virtual device that collectively holds the data structure. Method.