Carrier Access 1750 Benutzerhandbuch

The following summarizes the way that the SNMP tables are used.

User Management:

User, Community, View, Access, and Group Tables (from VACM)

Format for the PDU to send (also used for Proxies):

Target Address Table – contains domain and addressing information, timeout 
and retry information, and a tag list (snmpTargetAddrTagList) to define 
where to send notifications (and to forward proxied messages). There is also 
a link into the Target Params table.

Target Params Table – contains the definition of parameters such as the 
Message Processing Model, the Security Model, the Security Level, and the 
Security Name to build and SNMPv3 PDU.

Tables to identify targets and provide finer selection of events to send:

Notifications Table – how to group targets to send notifications and what type 
of notification to send

Notify Filter Profile Table – a list of filters used by a notification for finer 
grained control over trap destinations

Notify Filter Table – filters to limit the number of notifications generated for 
a particular target

The Broadmore predefines some SNMP v1/v2 trap parameters 

to ensure proper operation with ATM switches. For example, there is a 
predefined v1/v2 “get” user that can be added to a community (such as 
“public”) in the communities table.

When configuring traps, please note the consequences of 

selecting certain “Storage Type” parameters in the tables. “Permanent” 
entries cannot be deleted except by deleting the entire SNMP configuration 
and rebooting. “Read Only” entries can only be edited or removed by 
deleting the entire SNMP configuration and rebooting.