Configuring SNMP V1/V2c in Cisco Unified Serviceability

Available Languages

Download Options

PDF (136.9 KB)
View with Adobe Reader on a variety of devices

Updated:August 25, 2008

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Configuring SNMP V1/V2c in Cisco Unified Serviceability

Table Of Contents

Configuring SNMP V1/V2c in Cisco Unified Serviceability

How to Work with SNMP Community Strings

Configuring a Community String

Finding a Community String

Deleting a Community String

How to Work with SNMP Notification Destinations

Configuring a Notification Destination for SNMP V1/V2c

Finding a Notification Destination for SNMP V1/V2c

Deleting a Notification Destination for SNMP V1/V2c

Configuring SNMP V1/V2c in Cisco Unified Serviceability

May 19, 2009

•How to Work with SNMP Community Strings

•How to Work with SNMP Notification Destinations

How to Work with SNMP Community Strings

•Configuring a Community String

•Finding a Community String

•Deleting a Community String

Configuring a Community String

Because the SNMP agent provides security by using community strings, you must configure the community string to access any management information base (MIB) in a Cisco Unified Presence system. Change the community string to limit access to the Cisco Unified Presence system. To add, modify, and delete community strings, access the SNMP Community String Configuration window.

Before You Begin

Review the SNMP configuration checklist.

Procedure

Step 1 Perform one or more of the following actions:

If you want to:

Action

Add a new community string

a. Click Add New

b. Go to Step 2

Modify an existing community string

a. Locate the community string.

b. Click the name of the community string that you want to edit.

c. Go to Step 2.

Note You cannot change the name of the community string or the server for the community string.

Step 2 Enter the community string configuration settings, as described in the table below.

Table 13-1 Community String Configuration Settings

Field

Description

Server

This setting in the Community String configuration window displays as read only because you already specified your choice of server.

Community String

Enter a name for the community string. The name can contain up to 32 characters and can contain any combination of alphanumeric characters, hyphens (-), and underscore characters (_).

Tip Select community string names that will be hard for outsiders to figure out.

When you edit a community string, you cannot change the name of the community string.

Accept SNMP Packets from any host

To accept SNMP packets from any host, click this radio button.

Accept SNMP Packets only from these hosts

To accept SNMP only from specified hosts, click this radio button.

Tip In the Host IP Address field, enter a host from which you want to accept packets and click Insert. Repeat this process for each host from which you want to accept packets. To delete a host, select that host from the Host IP Addresses list box and click Remove.

Access Privileges

From the list box, select the appropriate access level from the following list:

•ReadOnly—The community string can only read the values of MIB objects.

•ReadWrite—The community string can read and write the values of MIB objects.

•ReadWriteNotify—The community string can read and write the values of MIB objects and send MIB object values for a trap and inform messages.

•NotifyOnly—The community string can only send MIB object values for a trap and inform messages.

•None—The community string cannot read, write, or send trap information.

Tip To change the Cisco Unified Presence trap configuration parameters, you need to use a community with NotifyOnly or ReadWriteNotify privileges.

Apply To All Nodes

Check to apply the community string to all nodes in the cluster.

Step 3 Perform one of the following actions after you complete the configuration:

a. Click Add New to save a new community string.

b. Click Save to save changes to an existing community string.

Step 4 Perform one of the following actions:

a. Click OK to restart the SNMP master agent service and effect the changes.

b. Click Cancel to continue the configuration without restarting the SNMP master agent.

Troubleshooting Tips

•If you are adding a new community string, you can click Clear All at any time to delete all information that you entered for all settings.

•Cisco recommends that you wait until you finish all the SNMP configuration before you restart the SNMP master agent service.

Related Topics

•SNMP Configuration Checklist, page 12-9

•Configuring a Community String.

•Configuring SNMP V3 in Cisco Unified Serviceability, page 14-1

•Configuring MIB2 System Group in Cisco Unified Serviceability, page 15-1

•Chapter 11, "Configuring and Viewing Services in Cisco Unified Serviceability."

Finding a Community String

Before You Begin

Review the SNMP configuration checklist.

Procedure

Step 1 Select Snmp > V1/V2c > Community String.

Step 2 Select the specific search criteria that you want to use for the community string from the Find Community Strings where Name list box.

Step 3 Enter the community string for which you want to search.

Step 4 Enter the hostname or IP address of the server where the community string exists in the Server field.

Step 5 Click Find.

Step 6 If you want to apply the configuration from one of the options in the search results to all nodes in the cluster, check the name of the option and check Apply to All Nodes.

Step 7 Click the community string that you want to view from the list of results.

Troubleshooting Tips

•The Add New button does not display in the SNMP Community String Configuration window until you click the Find button. If no community strings exist and you want to add want a community string, click the Find button and wait for the window to refresh. The Add New button displays.

•If you use SNMP version 3, see the "Configuring SNMP V3 in Cisco Unified Serviceability" section on page 14-1.

Related Topics

•SNMP Configuration Checklist, page 12-9

•Configuring a Community String

Deleting a Community String

Before You Begin

Review the SNMP configuration checklist.

Procedure

Step 1 Locate the community string.

Step 2 Check the community string that you want to delete from the list of matching records.

Step 3 Click Delete Selected. A message indicates that the system will delete notification entries that relate to this community string.

Step 4 Click OK to continue the deletion. A message indicates that changes will not take effect until you restart the SNMP master agent.

Step 5 Perform one of the following actions:

a. Click Cancel to continue the configuration without restarting the SNMP master agent.

b. Click OK to restart the SNMP master agent service.

Troubleshooting Tips

We recommend that you wait until you finish all the SNMP configuration before you restart the SNMP master agent service.

Related Topics

•SNMP Configuration Checklist, page 12-9

•How To Start and Stop Services in the Control Center or the Command Line Interface, page 11-3

How to Work with SNMP Notification Destinations

The following sections apply to SNMP notification destination configuration, depending on the SNMP version that you support:

•Configuring a Notification Destination for SNMP V1/V2c

•Finding a Notification Destination for SNMP V1/V2c

•Deleting a Notification Destination for SNMP V1/V2c

Configuring a Notification Destination for SNMP V1/V2c

You can configure the notification destination (trap/inform receiver) for V1/V2c.

Before You Begin

Review the SNMP configuration checklist.

Procedure

Step 1 Perform one or more of the following actions:

If you want to:

Action

Add a new SNMP notification destination

a. Click Add New

b. Go to Step 2

Note You configure the notification destination for the server that you select in the Server list box in the Find/List window.

Modify an existing SNMP notification destination

a. Locate the notification destination.

b. Click the name of the SNMP notification destination that you want to edit.

c. Go to Step 2.

Step 2 Enter the configuration settings, for V1/V2c as described in the table below.

Table 13-2 Notification Destination Configuration Settings for V1/V2

Field

Description

Server

This setting displays as read only because you already specified the server.

Host IP Addresses

From the list box, select the Host IP address of the trap destination or select Add New. If you select Add New, enter the IP address of the trap destination.

For existing notification destinations, you cannot modify the host IP address configuration.

Port Number

In the field, enter the notification-receiving port number on the destination server that receives SNMP packets.

V1 or V2C

From the SNMP Version Information pane, click the appropriate SNMP version radio button, either V1 or V2C, which depends on the version of SNMP that you are using.

•If you select V1, configure the community string setting.

•If you select V2C, configure the notification type setting and then configure the community string.

Community String

From the list box, select the community string name to be used in the notification messages that this host generates.

Only community strings with minimum notify privileges (ReadWriteNotify or Notify Only) display. If you have not configured a community string with these privileges, no options appear in the list box. If necessary, click the Create New Community String button to create a community string.

Notification Type

Select the appropriate notification type from the list box.

Apply To All Nodes

Check to apply the notification destination configuration to all nodes in the cluster.

Step 3 Perform one of the following actions:

a. Click Insert to save a notification destination.

b. Click Save to save changes to an existing notification destination. A message indicates that changes will not take effect until you restart the SNMP master agent.

Step 4 Perform one of the following actions:

a. Click OK to restart the SNMP master agent.

b. Click Cancel to continue the configuration without restarting the SNMP master agent.

Troubleshooting Tips

•If you are adding a new notification destination, you can click Clear at any time to delete all information that you entered for all settings.

•Cisco recommends that you wait until you finish the SNMP configuration before you restart the SNMP master agent service.

Related Topics

•SNMP Configuration Checklist, page 12-9

•How to Work with SNMP Notification Destinations

•Finding a Notification Destination for SNMP V3, page 14-6

•Configuring a Notification Destination for SNMP V3, page 14-5

•Deleting a Notification Destination for SNMP V3, page 14-7

Finding a Notification Destination for SNMP V1/V2c

Before You Begin

Review the SNMP configuration checklist.

Procedure

Step 1 Select Snmp > V1/V2c > Notification Destination.

Step 2 Select the specific search criteria that you want to use to find the notification destination from the Find Notification where Destination IP list box.

Step 3 Enter the notification destination for which you want to search.

Step 4 Enter the hostname or IP address of the server that supports the notification destination in the Server field.

Step 5 Click Find.

Step 6 Perform one or more of the following actions:

If you want to:

Action

Apply the configuration from one of the options in the search results to all nodes in the cluster

a. Check the name of the option.

b. Check Apply to All Nodes.

View the configuration for one of the items in the search results

Click the item.

Troubleshooting Tips

The Add New button does not display in the SNMP Notification Destination Configuration window until you click the Find button. If no notification destinations exist and you want to add want a notification destination, click the Find button and wait for the window to refresh. The Add New button displays.

Related Topics

•SNMP Configuration Checklist, page 12-9

•Configuring a Notification Destination for SNMP V1/V2c

Deleting a Notification Destination for SNMP V1/V2c

Before You Begin

Review the SNMP configuration checklist.

Procedure

Step 1 Locate the notification destination.

Step 2 Check the notification destination that you want to delete from the list of matching records.

Step 3 Click Delete Selected. A message asks whether you want to delete the notification entries.

Step 4 Click OK to continue the deletion. A message indicates that changes will not take effect until you restart the SNMP master agent.

Step 5 Perform one of the following actions:

a. Click OK to restart the SNMP master agent service.

b. Click Cancel to continue the configuration without restarting the SNMP master agent.

Troubleshooting Tips

Cisco recommends that you wait until you finish all the SNMP configuration before you restart the SNMP master agent service.

Related Topics

•SNMP Configuration Checklist, page 12-9

•How To Start and Stop Services in the Control Center or the Command Line Interface, page 11-3

If you want to:	Action
Add a new community string	a. Click Add New b. Go to Step 2
Modify an existing community string	a. Locate the community string. b. Click the name of the community string that you want to edit. c. Go to Step 2. Note You cannot change the name of the community string or the server for the community string.

Table 13-1 Community String Configuration Settings
Field	Description
Server	This setting in the Community String configuration window displays as read only because you already specified your choice of server.
Community String	Enter a name for the community string. The name can contain up to 32 characters and can contain any combination of alphanumeric characters, hyphens (-), and underscore characters (_). Tip Select community string names that will be hard for outsiders to figure out. When you edit a community string, you cannot change the name of the community string.
Accept SNMP Packets from any host	To accept SNMP packets from any host, click this radio button.
Accept SNMP Packets only from these hosts	To accept SNMP only from specified hosts, click this radio button. Tip In the Host IP Address field, enter a host from which you want to accept packets and click Insert. Repeat this process for each host from which you want to accept packets. To delete a host, select that host from the Host IP Addresses list box and click Remove.
Access Privileges	From the list box, select the appropriate access level from the following list: •ReadOnly—The community string can only read the values of MIB objects. •ReadWrite—The community string can read and write the values of MIB objects. •ReadWriteNotify—The community string can read and write the values of MIB objects and send MIB object values for a trap and inform messages. •NotifyOnly—The community string can only send MIB object values for a trap and inform messages. •None—The community string cannot read, write, or send trap information. Tip To change the Cisco Unified Presence trap configuration parameters, you need to use a community with NotifyOnly or ReadWriteNotify privileges.
Apply To All Nodes	Check to apply the community string to all nodes in the cluster.

If you want to:	Action
Add a new SNMP notification destination	a. Click Add New b. Go to Step 2 Note You configure the notification destination for the server that you select in the Server list box in the Find/List window.
Modify an existing SNMP notification destination	a. Locate the notification destination. b. Click the name of the SNMP notification destination that you want to edit. c. Go to Step 2.

Table 13-2 Notification Destination Configuration Settings for V1/V2
Field	Description
Server	This setting displays as read only because you already specified the server.
Host IP Addresses	From the list box, select the Host IP address of the trap destination or select Add New. If you select Add New, enter the IP address of the trap destination. For existing notification destinations, you cannot modify the host IP address configuration.
Port Number	In the field, enter the notification-receiving port number on the destination server that receives SNMP packets.
V1 or V2C	From the SNMP Version Information pane, click the appropriate SNMP version radio button, either V1 or V2C, which depends on the version of SNMP that you are using. •If you select V1, configure the community string setting. •If you select V2C, configure the notification type setting and then configure the community string.
Community String	From the list box, select the community string name to be used in the notification messages that this host generates. Only community strings with minimum notify privileges (ReadWriteNotify or Notify Only) display. If you have not configured a community string with these privileges, no options appear in the list box. If necessary, click the Create New Community String button to create a community string.
Notification Type	Select the appropriate notification type from the list box.
Apply To All Nodes	Check to apply the notification destination configuration to all nodes in the cluster.

If you want to:	Action
Apply the configuration from one of the options in the search results to all nodes in the cluster	a. Check the name of the option. b. Check Apply to All Nodes.
View the configuration for one of the items in the search results	Click the item.

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)

Configuring SNMP V1/V2c in Cisco Unified Serviceability

Available Languages

Download Options

Bias-Free Language

Table Of Contents