TP-Link T1600G-28PS Jetstream Smart Switches User Guide - Page 879

Configuring SNMP & RMON SNMP ■■ RFC2620-RADIUS-Acc-Client.mib ■■ RFC2674-pBridge.mib ■■ RFC2674-qBridge.mib ■■ RFC2863-pBridge.mib ■■ RFC2925-Disman-Ping.mib ■■ RFC2925-Disman-Traceroute.mib For detail information about the supported public MIBs, see Supported Public MIBs for TPLink Switches. SNMP Entity An SNMP entity is a device running the SNMP protocol. Both the SNMP manager and SNMP agent are SNMP entities. SNMP Engine An SNMP engine is a part of the SNMP entity. Every SNMP entity has one and only one engine. An SNMP engine provides services for sending and receiving messages, authenticating and encrypting messages, and controlling access to managed objects. An SNMP engine can be uniquely identified by an engine ID within an administrative domain. Since there is a one-to-one association between SNMP engines and SNMP entities, we can also use the engine ID to uniquely identify the SNMP entity within that administrative domain. Notification Types Notifications are messages that the switch sends to the NMS host when important events occur. Notifications facilitate the monitoring and management of the NMS. There are two types of notifications: ■■ Trap: When the NMS host receives a Trap message, it will not send a response to the switch. Thus the switch cannot tell whether a message is received or not, and the messages that are not received will not be resent. ■■ Inform: When the NMS host receives an Inform message, it sends a response to the switch. If the switch does not receive any response within the timeout interval, it will resend the Inform message. Therefore, Inform is more reliable than Trap. SNMP Version The device supports three SNMP versions with the security level from low to high: SNMPv1, SNMPv2c and SNMPv3. Table 1-1 lists features supported by different SNMP versions, and Table 1-2 shows corresponding application scenarios. User Guide 854