![]() SNMPv1 is the original version of the SNMP protocol and provides minimal network management functions. SNMP protocol is divided into three versions: SNMPv1, SNMPv2c and SNMPv3. As a standard protocol for network management widely used in TCP/IP networks, SNMP provides a uniform interface that enables unified management among different types and vendors of network devices. To address this problem, SNMP came into existence. There are various types of network devices, and the management interfaces (such as command line interfaces) of different devices provided by different vendors vary, which makes network management increasingly complicated. The following explains the SNMP principles and configures Huawei devices as SNMP agents. The Simple Network Management Protocol (SNMP) defines the standard for the management communication performed by the management end and the network devices. Therefore, managing the network requires a more macro management approach than managing network devices on a device-by-device basis.įor such complex systems, the most ideal management approach is for administrators to be able to access the working status of all managed devices in a timely manner through the operation interface of a management program, and to be able to configure all managed devices through this interface. Even if there are only a few common errors in the network, as long as the network is large enough, using the device management approach described earlier to troubleshoot them is akin to a blindfolded man trying to understand an elephant solely by touch. The above example shows that in a network, a complex system containing a large number of devices, it is often inadequate to initiate management access on a device-by-device basis. In other words, redundant devices are unable to optimally improve the network availability. Thus, the first time the administrator realizes that the primary device has failed is when the user complains to him about the disruption of network communication (caused by the breakdown of the backup device). The administrator is also unaware that the network has failed, and he certainly will not login to the primary device that has crashed and check for faults that could have caused the shutdown, much less repair or replace this device accordingly. However, when the primary device breaks down, the smooth switchover of the forwarding device from the primary device (and link) to the standby device (and link) goes unnoticed by any user. One of the key reasons is that technicians cannot predict on which component of which device network failures and network attacks will occur.įor example, a network deploys standby devices and corresponding high-availability technologies at certain critical points in the hope that the network will provide users with uninterrupted communication services 24/7. However, this method is not suitable for administrators to manage and maintain the entire network on a daily basis. This type of management method is appropriate for newly created projects or projects whose network is changed, because at this time the technicians proactively carry out all operations on each network device and the purpose of the operations is quite clear. ![]() Both of these management methods require administrators to establish connections and perform management on a device-by-device basis. ![]() There are only two means of network device management: one is to manage the device by connecting to the dedicated management interface of the network device (such as Console, MiniUSB) and using the virtual terminal software (such as SecureCRT) and the other is to launch Telnet/SSH remote management access to network devices by using the interface used for data transmission. Billing monitoring is mainly used to track and control the use of network resources by users and store the relevant information in the operation log database to provide a basis for billing. Security management protects the network and system from unauthorized access and security attacks.īilling management. The primary goal of fault management is to ensure that the network is always available and that faults are repaired as soon as possible when they occur. Performance management takes network performance as a guideline to ensure that the network can provide reliable and continuous communication capabilities while using fewer network resources and reducing time latency.įault management. Configuration management is responsible for monitoring the configuration information of the network, so that network administrators can generate, query, modify the operating parameters and conditions of hardware and software, and can configurate related services. ![]() The OSI reference model defines five major functional models of network managementĬonfiguration management. ![]()
0 Comments
Leave a Reply. |