
SmartNA-X 1G/10G Modular | Command Line Reference |
153
SmartNA-X
™
1G/10G User Guide 1.4
©
2015 Network Critical Solutions Limited
The VACM sectoGroup table is used to store group information and is indexed by a securityModel and securityName.
Several group directives can specify the same group name, allowing a single access setting to apply to several users and/or
community strings.
Syntax
snmp show sectogroup
Parameters
This command has no arguments or keywords.
Example
List sectoGroups:
CONTROLLER>
snmp show sectogroup
SectoGroup number 0
Security Model : v1
sec name : port3CSec
group name : port3Grp
SectoGroup number 1
Security Model : v2c
sec name : port3C6Sec
group name : port3Grp
SectoGroup number 2
Security Model : v1
sec name : port3DSec
group name : port3DGrp
snmp create sectogroup
Use the
snmp create sectogroup
command to map (add) SNMP users/securityNames into a Security To Group
(sectoGroup) table, called a groupName.
The groupName is used to define an access control policy for a group of users. The combination of a securityModel
and a securityName maps to at most one groupName. That is, a given user/securityName whose communications are
protected by a given securityModel can only be included in one groupName. The VACM sectoGroup table is used to store
group information and is indexed by a securityModel and securityName. Several group directives can specify the same
groupName, allowing a single access setting to apply to several users and/or community strings.
Syntax
snmp create sectogroup
groupName
{
USM
|
v1
|
v2c
}
securityName
Parameters
•
groupName
Specify the groupName. The groupName must be alphanumeric, of length 1-32, and the first letter must
be a letter. groupNames are case sensitive (groupname and Groupname are not the same).
•
USM, v1, v2c
Specify the group securityModel. User Security Model (USM) is the most secure method as all SNMP
communications are authenticated and encrypted (see RFC 3414 for more information). v1 and 2vc are unsecured,
amounting to little more than a community string sent in clear text.
•
securityName
Specify the user/securityName to map to the group (this is the same user/securityName already created
with the
snmp create user
or
snmp create comtosec
commands).
Examples
Create a sectoGroup with USM security:
CONTROLLER>
snmp create sectogroup
groupName
USM
securityName
CONTROLLER>
apply