Carrier Access 1750 user manual Broadmore Implementation of Snmp tables in RFCs 2273

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 creates 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	View
-Name : char	-Name : char	-Name : char
-IP	-UserName : char	-SubTreeOID
-Port	-SecurityModel	-Storage : <unspecified> = non-vol
-TargetParms : char	-SecurityLevel
-TrapTag : char	-MP Model
-Enabled : bool = true	-Enabled : bool = true
-Storage : <unspecified> = Non-Vol	-Storage : <unspecified> = Non-Vol	Access
-Timeout : <unspecified> = 1500
-Retries : <unspecified> = 3		-Name : char
-MsgSize : <unspecified> = 484
	User	-ReadView : char
		-WriteView : char
	-Name	-NotifyView : char
		-SecurityModel
	-Auth/Encyptiontypes
(TrapTag)		-SecurityLevel
	-Auth/Encryptionkeys
		-Storage : <unspecified> = Non-Vol
	-Storage : <unspecified> = Non-Vol
Notification	Community	Group
-Name : char	(TrapTag)	-Name : char
	-Name : char
-TrapTag : char	-Index : char	-UserName : char
-Enabled : bool = true	-UserName : char	-SecurityModel
-Severity
	-TrapTag : char	-Storage : <unspecified> = Non-Vol
	-Enabled : bool = true
	-Storage : <unspecified> = Non-Vol
12-30		Broadmore 1750 - Release 4.6