CHAPTER 2 SNMP Overview
Mediant 800 SBC | SNMP Reference Guide
●
A detailed explanation of each parameter can be viewed in the MIB Description
field.
●
A detailed description in HTML format of all MIBs can be found in the MIBs
directory (included in the Release package).
●
Not all groups in the MIB are implemented.
●
MIB Objects that are marked as 'obsolete' are not implemented.
●
When a parameter is Set to a new value via SNMP, the change may affect device
functionality immediately or may require that the device be soft reset for the
change to take effect. This depends on the parameter type.
●
The current (updated) device configuration parameters are configured on the device
provided the user doesn't load an ini file to the device after reset. Loading an ini file
after reset overrides the updated parameters.
SNMP Interface Details
This subsection describes details of the SNMP interface needed when developing an Element
Management System (EMS) for any AudioCodes devices, or to manage a device with a MIB
browser.
There are several alternatives for SNMP security:
■
SNMPv2c community strings
■
SNMPv3 User-based Security Model (USM) users
■
SNMP encoded over IPSec
■
Various combinations of the above
Currently, both SNMP and ini file commands and downloads are not encrypted. For ini file
encoding, refer to the device's
User's Manual
.
SNMP Community Names
By default, the device uses a single, read-only community string of "public" and a single read-
write community string of "private". Up to five read-only community strings and up to five
read-write community strings, and a single trap community string can be configured. Each
community string must be associated with one of the following predefined groups:
Table 2-1: SNMP Predefined Groups
Group
Get Access
Set Access
Sends Traps
ReadGroup
Yes
No
Yes
ReadWriteGroup
Yes
Yes
Yes
TrapGroup
No
No
Yes
- 8 -
