Carrier Access 1750 12-30 Broadmore 1750 - Release 4.6, Trap Management Overview

12-30 Broadmore 1750 - Release 4.6
SNMP Configuration
Trap Management Overview
The idea is to organize the information into specific tables that can be tied to other
tables, as shown in the figure below. All the target addresses used by notifications
and proxies are put into one table. Another table is used to identify which elements
belong to the notifications. The target parameter table contains the information for
creating SNMPv3 PDUs. Other tables are used to identify which notifications
should go to which targets. When the Notification Originator cr eates an INFORM
or v2TRAP PDU for SNMPv3, as opposed to locating proper targets, it takes
information from the target address table and the target params table.
Broadmore Implementation of SNMP tables in RFCs 2273 and 2573.
Target TargetParms
Notification
(TrapTag)
User
Community
(TrapTag)
Group
Access
View
-Name : char
-Use rN ame : ch ar
-SecurityModel
-SecurityLevel
-MP Model
-Enabled : bool = true
-Stor age : <uns p ecified> = Non-Vol
-Nam e : char
-T r apTag : char
-Ena bled : boo l = true
-Severity
-Name : char
-IP
-Port
-TargetParms : char
-TrapTag : char
-Enabled : bool = true
-Storage : <unspeci fied> = Non-Vol
-Timeout : <unspecified> = 1500
-Retries : <unspecified> = 3
-MsgSize : <unspecified> = 484
-Name
-Auth/Encyptiontypes
-Auth/Encryptionkeys
-Stor age : <unspecified> = No n- Vol
-Name : char
-Index : char
-Use rN ame : char
-TrapTag : char
-Enabled : bool = true
-Stor age : <unspecified> = No n- Vol
-Name : cha r
-SubTreeOID
-Storage : <unspecified> = non-vol
-Name : char
-ReadView : char
-WriteView : char
-NotifyView : char
-SecurityModel
-SecurityLevel
-Storage : <unspecified> = Non-V ol
-Name : char
-UserN am e : char
-SecurityModel
-Storage : <unspecified> = Non-V ol