Method for managing dynamic address equipment and agenty device

Abstract

A method for managing dynamic address device includes setting fixed device identification for dynamic address device, obtaining changed address and device identification of dynamic address device with changed address by agent unit and informing NMS, confirming dynamic address device with changed address by NMS according to received information and updating current IP address of said dynamic address device. The agent unit used for realizing said method is also disclosed.

Description

technical field [0001] The invention relates to network equipment management technology, in particular to a method and agent device for managing dynamic address equipment. Background technique [0002] With the continuous development of Internet technology, the scale of the network continues to expand, and the complexity of the network continues to increase. More and more computers use dynamically assigned IP addresses, which are called dynamic address devices. In the above network environment, there are one or several Dynamic Address Assignment Protocol (DHCP) servers to assign addresses to other devices and computers. [0003] Network Management System (NMS) is a system for managing network devices. In traditional NMS, it is assumed that: at any time after a device is added to the NMS, the device has a unique and constant management IP address (this address may also is one of the service addresses), and the NMS accesses the device through the management IP address to obta...

AI Technical Summary

Problems solved by technology

The two collection tasks belong to different devices and have no relationship, so necessary analysis such as historical trends cannot be viewed, resulting in discontinuous management

[0009] 2. When the address of a dynamic address device is assigned to other devices, the management information may be disordered

If the address of device A is assigned to device B after it is released, then for NMS, the communication of device A will be considered normal, but in fact at this time, device A in NMS has been wrongly mapped to device B, and various management information is disordered.

[0010] 3. Periodic automatic discovery makes device information not updated in time

For devices that are already running on the Internet, due to limitations in hardware and other aspects, they are not even upgradeable.

This makes the program unfeasible

[0015] 2. Access efficiency is much lower than SNMP

In a non-NAT environment, when the network management system actively initiates an access request, an additional communication is required

[0016] 3. Insufficient standardization of network protocols

Since the registered port must be known, this requires that the ports provided by the network management must be limited. When the network scale is large, it will inevitably lead to poor performance.

Of course, it is also possible to use each device to register with different ports, but in this way, not only the configuration management is quite complicated, but also there are performance problems because the network management system needs to monitor a large number of ports.

[0021] 2. Taking the IP address as the unique identifier of the device will also lead to discontinuous management and information disorder

[0022] 3. In addition to SNMP, traditional management protocols such as Telnet and ping are also used. Therefore, when multiple management protocols are used at the same time, multiple tunnels are required, which not only makes the performance problem more serious, but also leads to an increase in transformation costs.

[0023] It can be seen from the above that the current dynamic address device management method cannot guarantee the simplicity of network transformation and the continuity of device management at the same time

Images