Siemens RUGGEDCOM ROS v4.3 - Page 223

RUGGEDCOM ROS
User Guide
Chapter 5
Setup and Configuration
Adding an SNMP Group 207
9
7
8
6
5
4
3
2
1
Figure140:SNMP Access Form
1.Group Box 2.Security Model Box 3.Security Level Box 4.ReadViewName Box 5.WriteViewName Box 6.NotifyViewName
Box 7.Apply Button 8.Delete Button 9.Reload Button
3. Configure the following parameter(s) as required:
Parameter Description
Group Synopsis:  Any 32 characters
The group name to which the security model and name belong.
This name is used as an index to the SNMPv3 VACM Access Table.
SecurityModel Synopsis:  { snmpV1, snmpV2c, snmpV3 }
Default:  snmpV3
In order to gain the access rights allowed by this entry, configured
security model must be in use.
SecurityLevel Synopsis:  { noAuthNoPriv, authNoPriv, authPriv }
Default:  noAuthNoPriv
The minimum level of security reqwuired in order to gain
the access rights allowed by this entry. A security level of
noAuthNoPriv is less than authNoPriv, which is less than authPriv.
ReadViewName Synopsis:  { noView, V1Mib, allOfMib }
Default:  noView
This parameter identifies the MIB tree(s) to which this entry
authorizes read access. If the value is noView, then no read access
is granted.
WriteViewName Synopsis:  { noView, V1Mib, allOfMib }
Default:  noView
This parameter identifies the MIB tree(s) to which this entry
authorizes write access. If the value is noView, then no write
access is granted.
NotifyViewName Synopsis:  { noView, V1Mib, allOfMib }
Default:  noView
This parameter identifies the MIB tree(s) to which this entry
authorizes access for notifications. If the value is noView, then no
access for notifications is granted.