Filter
Top Products
8000-A2-GB30-10 November 2003 77
7.7.2 Supporting MIBs.
7.7.3 SNMP-MPD-MIB (RFC 3412)
This MIB provides statistics for message processing. The following scalar MIB objects will
be supported to provide statistics about invalid or unknown conditions in the message
processing:
7.7.3.1 snmpUnknownSecurityModels
7.7.3.2 snmpInvalidMsgs
7.7.3.3 snmpUnknownPDUHandlers
7.7.4 SNMP Framework MIB (RFC 3411)
In addition to defining new textual conventions, this MIB defines the following scalar
objects that will be supported in the SCP:
7.7.4.1 snmpEngineID:
There will be a unique identifier for the SNMP engine running in the device. It will be set
up by following one of the schemes proposed in the RFC 3411. That is, it will use the private
enterprise number assigned to Paradyne (1795) by the Internet Assigned Numbers
Authority and the MAC address of the card (SCP) running the agent to generate a unique
identifier for the Engine.
For example the MAC address of my SCP card is ’00-E0-39-C1-CD-16’ will result in the
following snmpEngineID:
80 00 07 03 03 00 E0 39 C1 CD 16
See RFC 3411 for details on how this is formatted.
7.7.4.2 snmpEngineBoots:
Number of times this entity has been reboot. This number must be preserved upon reset of
the entity.
7.7.4.3 snmpEngineTime:
Actual sysUpTime since last reboot.
7.7.4.4 snmpMaxMessageSize: Based on configuration of the Emanate/Lite agent.
7.7.4.5 SNMP-TARGET-MIB (RFC 2573)
The SCP will use the SNMP-TARGET-MIB exclusively to configure trap managers. The
following MIB objects contained in SNMP-TARGET-MIB will be supported to configure
trap managers.
7.7.4.5.1 snmpTargetSpinLock:
It is used to control multiple simultaneous access to the target table. Users must follow the
procedure in RFC 2573 to add/modify entries in this table.
7.7.4.5.2 snmpTargetAddrTable:
It is used to configure transport addresses to be used in the generation of SNMP notification
messages.