Network Critical SmartNA-X User Manual page 174

C L I R
OMMAND INE NTERFACE EFERENCE
VACM examples
Given a pre-existing user johnsmith (which can be set up using the snmp create user command), we could
configure full read-write access to the whole OID tree using the following commands:
CONTROLLER>snmp create sectogroup RWGroup usm johnsmith
CONTROLLER>snmp create view All include .1
CONTROLLER>snmp create view None exclude .1
CONTROLLER>snmp create access RWGroup usm priv All All None
This creates a new security group named "RWGroup" containing the SNMPv3 user "johnsmith", a new view "All"
containing the full OID tree, and a new view "None" excluding the full OID tree. And then allows those users in
the group "RWGroup" (i.e. "johnsmith") both read- and write-access to the view "All" (i.e. the full OID tree) when
using authenticated SNMPv3 requests, and excluded notify-access to the view "None" (i.e. the full OID tree).
As a second example, we could set up read-only access to a portion of the OID tree (for example .1.3) for an
SNMPv1/2c community using the commands:
CONTROLLER>snmp create comtosec comm2secname VACMCommunity 192.168.254.100 ipv4
CONTROLLER>snmp create sectogroup testgroup usm comm2secname
CONTROLLER>snmp create view mainview include .1.3
CONTROLLER>snmp create access testgroup usm noAuth mainview None None
This maps an existing SNMPv1 community "VACMCommunity" to a security username named
"comm2secname", and creates a new security group named "testgroup" containing "comm2secname", a new view
"mainview" containing just the OID tree based on .1.3, and then allows those users in the group "testgroup" (i.e.
"comm2secname") read-access, but not write- or notify-access to the view "mainview".
|
S NA™ 10G N
MART
DRAFT
A (S NA-X)
ETWORK CCESS MART
169