Document ID: 7275
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Step One
Set up on a Router
Set up on a Switch
Step Two
Step Three
Troubleshoot
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
This document explains how to launch CiscoView from CastleRock Computing's SNMPc when the map and icon are generic.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
This document is not restricted to specific software and hardware versions.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Step One
The first step is to set up Simple Network Management Protocol (SNMP) on a router or switch. Both setups are explained in this section.
Set up on a Router
You need to configure these in order to set up SNMP on a router:
snmp-server community <public or private> RO snmp-server community <public or private> RW snmp-server host <ip_address_of_network_management_station> <read only string from above>
This is an example SNMP router setup:
snmp-server community <public> RO snmp-server community <private> RW snmp-server host <145.65.43.1> <public>
Set up on a Switch
Switches (assuming the Catalyst 5000 series) are configured to use community string public for read-only (RO) and community string private for read-write (RW) by default. You need to issue these commands in order to change these community strings:
set snmp community read-only <public or private> set snmp community read-write <public or private>
Step Two
By default, the SNMPc application uses an RO string of public and an RW string of netmon. You have to set up across your network in order to change these defaults to the string names. Complete these steps:
-
From the SNMPc map, choose the Edit menu.
-
Choose Node Defaults, then choose Comm.
A window appears that allows you to set string names.
You can also set up community strings for individual nodes in a similar manner.
-
With the node selected, choose the Edit menu.
-
Choose Edit Object.
Step Three
Complete these steps:
-
From the SNMPc Map, choose the Edit menu and choose Discover Nodes.
-
Then, click Setup in the window that displays.
If you have already done a discovery, but your Cisco devices were not found correctly, you can open a new map and click Clear Log first.
-
Make sure the Communities listed on the left side of the window match what was configured in step one.
-
Restart Discovery, and click Layout when done.
Troubleshoot
This section provides troubleshooting steps to perform if the devices still do not automatically launch CiscoView.
-
On the SNMPc Map, choose the generic device.
-
Choose the Edit menu, and choose Edit Object.
-
From the menu bar, click Comm and verify that the communities match those configured in step one.
If they do not match, change them so that they match the communities from step one.
-
From the Node Attributes main window, verify that the Type field shows Agent and not Ping.
-
Also, from the Node Attributes main window, verify that the Exec shows Auto.EXE.
-
Then, choose the Manage menu and choose SNMP poll in order to verify that it is recognized as a Cisco device.
You can tell it is recognized as a Cisco device if the autoico.exe file has been updated to support this device type. If it is recognized as a Cisco device, try to relaunch CiscoView on the device.
Complete these steps in order to verify if the CiscoView package is installed for that device family:
-
Look in ..\CWW\bin and perform cview.exe.
This displays the main CiscoView window.
-
From the menu bar, choose Help.
-
Choose About CiscoView, and then click Packages Installed.
The window that appears indicates the version of each package for each device type. Write down this information, as well as the show version command output from the device in question, because it might be needed for later troubleshooting if you contact Technical Support.
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for Network Management |
| Network Infrastructure: Network Management |
| Virtual Private Networks: Network and Policy Management |
Related Information
| Updated: Aug 24, 2006 | Document ID: 7275 |
