1. Network Management Specification
8000-A2-GB30-30
June 2004
97
8.4.6
SNMPv3 Coexistence.
This draft discusses the “Coexistence between Version 1, Version 2 and Version 3 of the
Internet-standard Network Management Framework”. Among other things, this mib defines
the snmpComunityTable. This table will be supported to configure community strings for
SNMP managers capable of processing SNMPv1/v2c messages. This table has no
significance and thus, it is not used for SNMPv3 users.
By default, the SNMP agent is configured to process SNMPv1 or SNMPv2c messages with
no authentication and no encryption. For this purpose, a default community string ’public’
with read/write access is defined; this default entry is stored as permanent and can not be
deleted. A second community string entry can be created by setting the
snmpCommunityStatus to createAndGo (4).
*
“Security-rw” mimics a read-write community string while a “Security-ro” mimics a
read-only community string.
8.4.7
Paradyne Enterprise Message Processing Dispatcher
(PDN-MPD-EXT-MIB.mib).
This enterprise mib allows configuration of the Message Processing Dispatcher to be
supported in the device. The following mib are supported:
Table 1-119. Coexistence mib support.
Object
Supported
Comments
snmpCommunityEntry
read-create
It shall be used by managers to
create new community string for
SNMPv1/v2c access.
Table 1-120. snmp default communities
snmpCommunityEntry
Default
snmpCommunityIndex
“public”
snmpCommunityName
“public”
snmpCommunitySecurityName
“Security-rw”
*
snmpCommunityContextEngineID
localSnmpID
snmpCommunityContextName
““
Table 1-121. PDN-MPD-EXT-MIB.
Object
Comments
pdnMpdExtSecurityModeConfig
Supported as is.
See section 8.7.8.1