Specifications

© 2006 Cisco Systems, Inc.
All rights reserved.
Product Features 2-45
NAM / Traffic Analyzer v3.5 Tutorial
© 2006 Cisco Systems, Inc. All rights reserved.
Product Features 2-45
NAM / Traffic Analyzer v3.5 Tutorial
Getting Started
Third Party NMS Access to NAM using SNMP
Getting Started
Third Party NMS Access to NAM using SNMP
Choose Create to
add community
strings, or to delete,
click the radio button
to the left of the
string to delete and
click Delete.
Choose Create to
add community
strings, or to delete,
click the radio button
to the left of the
string to delete and
click Delete.
Configuring Contact,
NAM name, and
NAM location are
optional parameters,
but they facilitate the
use of the NAM for
engineers who may
be using it with other
third-party network
management systems
as well as existing
NAM users.
Configuring Contact,
NAM name, and
NAM location are
optional parameters,
but they facilitate the
use of the NAM for
engineers who may
be using it with other
third-party network
management systems
as well as existing
NAM users.
Configure NAM
community strings
to allow 3
rd
party
NMS to retrieve MIB
information from
NAM using SNMP;
SNMP v1/v2
supported.
Configure NAM
community strings
to allow 3
rd
party
NMS to retrieve MIB
information from
NAM using SNMP;
SNMP v1/v2
supported.
Disable SNMP
communication by
deleting SNMP
community strings
Disable SNMP
communication by
deleting SNMP
community strings
1
2
3
Third Party SNMP NAM Access
The last security configuration option available on the NAM is for configuring community strings. An SNMP
community is a domain of one or more SNMP agents and one or more SNMP management consoles that
share access information and configuration. Communities are formed by configuring each member of the
community with a “string” (either read-only or read-write in this case) to indicate its membership in the
community. In other words, community strings are similar to passwords, and they enable network
management agents and consoles to agree on what information and configuration options can be shared. For
example, if a network management console wants to retrieve information from an agent, the console must be
configured with the read-only “community string” of that agent to read data from it. If it wants to also set
parameters on the agent, it must be configured with the read-write community string.
When you configure your NAM community strings in the menu illustrated above, you are configuring
community strings that another third-party, external management console must use to collect information from
or send information to the NAM. To do so, simply click on the Create button and add the community strings
for read-only and read-write. To prevent any outside SNMP access to the NAM, simply do not configure the
SNMP strings.