Configuring the ECN330-switch
1071553-KDU 137 365 Uen D 2006-06-16
SNMP defines both the format of the MIB specifications and the protocol used
to access this information over the network.
The ECN330-switch includes an onboard agent that supports SNMP versions 1,
2c, and 3. This agent continuously monitors the status of the ECN330-switch
hardware, as well as the traffic passing through its ports. A network
management station can access this information using SNMP-based
management software. Access to the onboard agent from clients using SNMP
v1 and v2c is controlled by community strings. To communicate with the
ECN330-switch, the management station must first submit a valid community
string for authentication.
Access to the ECN330-switch using from clients using SNMPv3 provides
additional security features that cover message integrity, authentication, and
encryption; as well as controlling user access to specific areas of the MIB tree.
The SNMPv3 security structure consists of security models, with each model
having it’s own security levels. There are three security models defined,
SNMPv1, SNMPv2c, and SNMPv3. Users are assigned to “groups” that are
defined by a security model and specified security levels. Each group also has
a defined security access to set of MIB objects for reading and writing, which are
known as “views.” The ECN330-switch has a default view (all MIB objects) and
default groups defined for security models v1 and v2c. Table 10 shows the
security models and levels available and the system default settings.
Table 10 SNMPv3 Security Models and Levels
Model Level Group Read
View
Write
View
Notify
View
Security
v1 noAuthNoPriv public default
view
none none Community string
only
v1 noAuthNoPriv private default
view
default
view
none Community string
only
v1 noAuthNoPriv user
defined
user
defined
user
defined
user
defined
Community string
only
v2c noAuthNoPriv public default
view
none none Community string
only
To Next Page
Loading...
