3Com V6100, User Manual Manual, Page: 365 / 496

V6100 and V7122 User Guide
365
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.
SNMP can be encoded over IPSec. For detailed information on IPSec, see IPSec
and IKE .
Currently, both SNMP and ini file commands and downloads are not encrypted. For ini file
encoding, see Secured ini File .
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’.
Users can configure up to 5 read-only community strings and up to 5 read-write community
strings, and a single trap community string is supported:
Configuration of Community Strings via the Web
For detailed information on configuration the community strings via the Embedded Web
Server, see
Configuring the SNMP Community Strings .
Configuration of Community Strings via the ini File
SNMPReadOnlyCommunityString_<x> = '#######'
SNMPReadWriteCommunityString_<x> = '#######'
where <x> is a number between 0 and 4, inclusive. Note that the '#' character represents any
alphanumeric character. The maximum length of the string is 20 characters.
Configuration of Community Strings via SNMP
To configure read-only and read-write community strings, the EM must use the SNMP-
COMMUNITY-MIB. To configure the trap community string, the EM must also use the
snmpVacmMIB and the snmpTargetMIB.
To add a read-only community string (v2user):
ƒ
Add a new row to the srCommunityTable with CommunityName v2user and GroupName
ReadGroup.