User`s manual

SIP User's Manual 14. SNMP-Based Management
Version 5.0 313 December 2006
In addition to the listed traps, the device also supports the following standard traps:
coldStart
authenticationFailure
linkDown
linkup
entConfigChange
14.8 SNMP Interface Details
This section describes details of the SNMP interface that is required when developing an
Element Manager (EM) for any of the TrunkPack-VoP Series products, or to manage a
device with a MIB browser.
The gateway offers the following SNMP security features:
SNMPv2c community strings
SNMPv3 User-based Security Model (USM) users
SNMP encoded over IPSec (refer to Section 12.1 on page 279)
Combinations of the above
Currently, both SNMP and ini file commands and downloads are not encrypted. For ini file
encoding, refer to Section E.1.2 on page 365.
14.8.1 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’.
The following community strings can be defined:
Up to five read-only community strings
Up to five read-write community strings
A single trap community string
Each community string must be associated with one of the following predefined SNMP
groups:
Table 14-2: SNMP Predefined Groups
Group Gets Access Sets Access Sends Traps
ReadGroup
Yes No Yes
ReadWriteGroup
Yes Yes Yes
TrapGroup
No No Yes
14.8.1.1 Configuration of Community Strings via the Web
For detailed information on configuration the community strings via the Embedded Web
Server, refer to Section 5.6.6.2 on page 180.
14.8.1.2 Configuration of Community Strings via the ini File
The following ini file parameters are used to configure community strings:
SNMPReadOnlyCommunityString_<x> = '#######'
SNMPReadWriteCommunityString_<x> = '#######'
Where <x> is a number from 0 to 4. The '#' character represents any alphanumeric
character. The maximum length of the string is 20 characters.