TP-Link T1500 Series User Manual page 765

Hide thumbs Also See for T1500 Series:
Table of Contents

Advertisement

Configuring SNMP & RMON
 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 TP-
Link Switches which can be found on the training center of our website:
http://www.tp-link.com/en/configuration-guides.html
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 ending 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 and unambiguously identify the SNMP entity within that
administrative domain.
SNMP Version
The device supports three SNMP versions: SNMPv1, SNMPv2c and
lists features supported by different SNMP versions, and
application scenarios.
Table 1-1
Features Supported by Different SNMP Versions
Feature
Access Control
Authentication
and Privacy
Trap
Inform
SNMPv1
Based on SNMP
Community and MIB View
Based on Community
Name
Supported
Not supported
Table 1-3
SNMPv2c
Based on SNMP
Community and MIB View
Based on Community
Name
Supported
Supported
SNMPv3.Table 1-2
shows corresponding
SNMPv3
Based on SNMP User, Group,
and MIB View
Supported authentication and
privacy modes are as follows:
Authentication: MD5/SHA
Privacy: DES
Supported
Supported
Configuration Guide
SNMP
743

Advertisement

Table of Contents
loading

Table of Contents