Views control the access to a managed object. The total MIB of a router can be viewed as a hierarchical tree. When a view is created, either the entire tree or a portion of the tree can be specified and made available to a user to manage the objects contained in the subtree. Object identifiers (OIDs) uniquely identify managed objects. A view defines the type of operations for the view such as read, write, or notify.
OIDs are organized in a hierarchical tree with specific values assigned to different organizations. A view defines a subset of the agent’s managed objects controlled by the access rules associated with that view.
The Nokia SNMP agent associates SNMPv1 and SNMPv2c community strings with a SNMPv3 view.
The following system-provisioned views are available through the config>system>security>snmp# view context, which are particularly useful when configuring SNMPv1 and SNMPv2c:
iso
It is intended for administrative-type access to the entire supported object tree (except Lawful Interception). The "iso" view is automatically associated with any SNMP community configured in the config>system>security>snmp context that has an access-permission of r, rw, or rwa.
no-security
Similar to iso view, but removes access to several security areas of the object tree (such as SNMP communities, user and profile configuration, SNMP engine ID, and so on). The no-security view is generally recommended over the iso view to reduce access to security objects.
li-view
It provides access to a small set of Lawful Interception related objects.
mgmt-view
It provides access to IF-MIB and a few other basics. The mgmt-view view is automatically associated with any SNMP community configured in the config>system>security>snmp context that has an access-permission of mgmt.
vprn-view
It is used to limit access to objects associated with a specific VPRN (for example, the Per-VPRN Logs and SNMP Access feature). The vprn-view view is automatically associated with any SNMP community configured in the config>service>vprn>snmp context.