Ciscoworks 2000 download

Type end. For Solaris, view the file pointed to by the line "local7. If this file does not exist, create one, and make sure that it is accessible by syslogd. If the syslog message is not there, check that the syslog daemons are running properly. Ensure that the device is logging to the correct Essentials server. Refer to the device system documentation for details on enabling syslog. Ensure that the Startup Parameters field contains the location of the SaenvProperties.

Syslog Analyzer: new messages not appearing in reports after changing syslog message file defined using: Admin; Syslog Analysis; Change Storage Options. On Windows NT, run the registry editor Regedit. Refer to the Solaris man pages for more information.

Syslog Analyzer: server runtime error when running Tasks Syslog Analyzer tasks. Log in to Essential as admin.

Start the system. If the task still fails, select Admin; Troubleshooting; Process Failures to get a list of Essential back-end processes that have failed. The Syslog Standard Device Report displays messages for all selected devices and dates. These devices must be managed by Essentials inventory. This error could arise if the device is not managed by Essentials inventory.

After adding the device, messages formerly in the Unexpected Device Report will not be transferred to the Standard Report, but new messages for the device will be displayed in the Standard Report. If the device is managed by Essentials inventory, it could be a name resolution problem. Syslog analyzer uses all IP addresses associated with the device name to try to map it to a device managed by Essentials Inventory. For Windows NT, view the syslog.

Note the source of the syslog messages from the device the source is the host name appearing immediately after the timestamp.

Obtain a list of IP addresses perform nslookup on the device name at the command prompt. Generate a detailed device report Tasks; Inventory; Detailed Device Report for the particular device. Check the Network Address column, and verify that the IP addresses returned from nslookup appear on the list. If any IP addresses are not on the list, then the device name-to-IP address mapping is incorrect.

Same action steps as the previous row, which has "CMLogger is not running" as a possible reason. To use many of the troubleshooting techniques, you must first understand the background processes of CWSI Campus. CWSI Campus includes the following major technology components that enhance the overall performance:. These background processes are described in Table The server processes represent the processes controlled by the CWSI Campus software; these are the background processes for the client processes.

The client processes require user input. To verify that these processes are running, you can use the pdshow command from any command prompt. ANI is a multithreaded Java program. It is installed as a daemon process and runs in the background, beginning as the workstation starts up. The database engine is responsible for checking all ANI information into the database. For ANI, this is a checkpoint only. ANI performs all its operations from the data stored in memory.

The database stores user-entered information and allows ANI to quickly load its data model into memory upon a subsequent restart.

All servers must register with the OsAgent, and all clients looking for service find it with the help of the OsAgent. This process is used by the AtmDirector application for periodic polling of the network for status of devices and links.

This process sends events to all servers and clients that have registered with it. This process downloads a complete picture of the topology so that selection and display are done locally.

It receives events from ANI about changes in discovery or network status. This process provides a graphical user interface for the UserTracking application. This process provides a graphical user interface for the VlanDirector application.

This process displays network topology and is used as the primary starting point for other applications. TrafficDirector does not link directly with any of the background processes.

Some of the troubleshooting steps may require that you enable trace or debug in ANI to gather additional information. To enable trace and debug , follow these steps:. Step 3 Start ANI and enable trace and debug by entering the following command:. The troubleshooting instructions or the TAC representative will provide you with the appropriate subsystem name.

Step 4 To stop the process, press Ctrl-C from the command prompt or shell window. Open a command prompt or shell window. When the prompt returns, all the daemons have been stopped. To restart the processes, enter startcwsiserver and wait until the prompt returns. If an error occurs stating that you have lost connection to EventChannel, follow these steps:. Step 1 From the command prompt or shell window, enter pdshow AniServer to determine whether AniServer is still running.

If it is not running, continue with Step 3. If AniServer did go down without your knowledge, open the ani. Step 3 From the command prompt or shell window, enter pdshow EventChannel to determine whether EventChannel is running.

If EventChannel is not running, continue with Step 5. If you still cannot log in, refer to the previous section of "Troubleshooting Information for CiscoWorks Installation and Setup.

A corrupt database cannot be easily identified. However, these problems have been resolved. Currently, the only way to know definitively whether the database is corrupt is to look at the ani. If many SQL exceptions and errors are present in the ani. ANI cannot perform effectively with a corrupt database. If you determine that you have a corrupt database, you need to reinitialize a new database.

Note If you have entered information into the UserTracking application, this information will be lost when you delete the corrupt database. If you run the script to replace a corrupt database, the script automatically stops all CWSI Campus servers. After the database engine stops, the script then erases the old database, sets the correct permissions, and replaces the old database with an empty, reinitialized database. Step 1 Run the reinitdb script. Step 2 Read the information that appears on the screen.

Step 3 Press any key to run the script, or press Ctrl-C to exit out of the script without running it. You should not need to manually replace a corrupt database because the script automatically performs all necessary steps for you.

However, you can use this method if you want to retain a copy of your old database. To prevent this, you must be sure that both the owner and the group are set to BIN.

Step 1 Run the stopcwsiserver script. Step 3 Back up the current database by renaming it. For example, you could name it cwsiold. This is a fresh database file. Step 6 Delete the cwsi. Step 7 Run the startcwsiserver script. Also, if you plan to install multiple copies of CWSI Campus on your network, you should change the name of the AniServer that each copy is accessing.

Each AniServer is intended to manage a single domain. Therefore, if you install another copy of CWSI Campus configured with the same AniServer name AniServer, by default in your network, unpredictable behavior might result, depending on which AniServer the client chooses as its default AniServer.

If you want to install another copy of CWSI Campus to manage another domain, you must manually configure your systems to run separate AniServer processes. Step 2 Run the stopcwsiserver script. Step 3 Locate and open the ani. The ani. Step 4 Change the following line to rename the AniServer process running on your local workstation:. Step 5 After making these changes, save the file and close your text editor. Step 6 Run the startcwsiserver script.

Step 1 Reduce the number of discovery threads. This process causes discovery to take less CPU power, but discovery will take longer. To change the discovery threads, follow these steps:. Follow the instruction carefully, and do not attempt to edit other information. Step 3 Increase the discovery time scheduling interval.

Step 4 Change the discovery time scheduling interval to be fixed once a day, twice a day based on your need for timely information. Step 5 Set up the system for high performance. Install enough physical memory to handle CWSI Campus and any other programs that you run simultaneously. You should avoid using swapping. Ensure a fast network connection; the connection should be better than a MB shared media connection.

Also, place the swap file on its own partition, if possible, or ensure that it remains unfragmented. To allow CWSI Campus to configure the devices in your network, you must ensure that the proper community strings are set.

These sections will help you troubleshoot problems that you may experience. When entering valid community strings, what determines whether these examples are invalid or valid? The first example is invalid because you have assigned different community strings to the same nested address. CWSI Campus probably will overwrite the first entry with the second. However, unpredictable results are also possible.

The second example is valid because If you accidentally enter an invalid write community string, you will still be able to discover the network provided that you entered a valid read-only community string. You will not be able to perform any write actions until you enter a valid read-write string. If you have experienced difficulty interpreting your discovered network, follow the suggestions in this section for assistance with common problems. When a link between devices appears as a dashed line, it means that during the last discovery cycle, CWSI Campus was incapable of doing a complete discovery of one of the devices at either end of the link.

This situation could happen if the link is inoperable for any reason, such as if the link was removed from the network. The most likely explanation for these dashed lines is an SNMP timeout. SNMP typically has the lowest priority of the background processes for the Cisco device system. You can lengthen the SNMP timeout for an individual device. To lengthen the timeout, follow these steps:. Step 2 Enter the community string using this syntax:.

Step 3 If individual devices are configured with different community strings, enter new lines for each device. Devices with a red X on them are not being discovered properly.

This icon is typically displayed for non-Cisco devices. Several factors determine how long a discovery will take, including the following:. Step 1 Restrict discovery to only the VTP domains that you want to manage. Step 2 Ensure that you have entered the appropriate community strings for your devices. Step 3 Increase the number of threads available to discovery if you have many devices to discover.

CWSI Campus allocates 12 threads to discovery. If you have many slow or unreachable devices, they can fill the thread pool and prevent other devices from being discovered. Step 4 To change or increase discovery threads, follow these steps:. Follow the instructions carefully, and do not attempt to edit other information. You cannot completely shut off discovery.

CWSI Campus was built on a real-time data model that relies upon discovery data. You can set the discovery interval to an extremely large number so that discovery occurs only when the ANI server starts or when you manually discover the network. If CWSI Campus has discovered a device that you do not want displayed on the map, you cannot delete this device. The following solutions are available:. This solution works well if the device is in your network, but you do not want to display it on the CWSI Campus map.

This solution works best for erroneously discovered devices that are not really in your network, or if you have removed a device since the initial discovery. Possible causes and their solutions include these:.

Use software image versions 3. In these cases, the link is displayed as Ethernet. Therefore, 10 M and M are displayed on the map. Make sure that your routers do not have the same sysName. You can also check the log file to see if a large number of duplicate devices has been discovered and rejected as duplicates. These subsections provide information about working with discrepancy reports. Step 2 To print the discrepancy report, select File; Export. The report is saved as a file.

You can print the report from the program in which it has been saved. The discrepancy report displays information on inconsistencies or irregularities in your network. Table describes these irregularities that may appear in your report. When interpreting the discrepancy report, keep in mind that configurations that you set up intentionally may appear as discrepancies. If you are aware that this is how you wanted to configure your network, then do not be overly concerned with the discrepancies.

Trunking ports versus nontrunking ports are configured on either side of a link. A link in a VTP domain is not set to trunk. There are devices in this domain that do not communicate through any trunk. Spanning tree is not supported with Catalyst software release 2. For Catalyst software release 3. You can customize the Discrepancy Report to display only those discrepancies about which you want to be notified.

Step 2 In the Properties window, select Discrepancy. The discrepancies are displayed. Step 3 Select only those discrepancies that you want displayed. Use the information provided here to help you troubleshoot problems with the VlanDirector application.

For most predictable results, Cisco recommends having at least one switch configured as a VTP server, and the remaining switches configured as VTP clients. If there are two servers with the same VTP domain that are not connected by trunks, the configurations managed by the two servers may diverge. This configuration is not supported by the VlanDirector application, and it creates a discrepancy. Discrepancies occur when there are identically named VLANs with other attributes that are different such as index and so on.

If the two VLANs share identical definitions, no discrepancy is detected. If the definitions are identical including name, VLAN index, and so on , the dragging process will probably work fine. However, if the definitions are not identical, then the results are undefined: The process may or may not work. Thus, if the VLAN state of a transparent switch differs from the state reported by a server in the same domain, the VlanDirector application will not properly handle VLAN changes to the transparent switch.

The lightning bolt on a port means that the port is part of a link either a device-to-device link or a connection into a shared media. The lightning bolt is used to differentiate between a port that is connected to another switch linking and a port that is configured as a user port. The bolt indicates that you cannot manipulate the port for VLAN configuration by itself; you must configure it as part of its corresponding link. Tables through provide you with detailed troubleshooting information for resolving LANE configuration problems.

Make sure that all devices are running the required software image version for LANE services. Increase the SNMP timeout for the devices, and rediscover the devices or network. If the configuration server resides on a Catalyst series switch, verify that the device has at least 16 MB of memory. Verify that the master configuration server has been discovered by selecting Edit; Configure Config Server from the VlanDirector Names window.

Cisco does not recommend using more than one master configuration server in an ATM fabric. If there are multiple master configuration servers, CWSI Campus will randomly select one of them to use for discovery, and the others will be ignored. The configuration server database should reflect the correct master ship state of the LE servers. Use the CLI to check the configuration server database.

A valid configuration server database is similar to the following:. The name Y does not appear anywhere. Enable trace and debug entering the following command:. This is the same as the probable cause in Table 's contents in rows 1 through 4. C5K -debug devices. C -debug devices. LS -debug devices. Router -debug devices. C3K -debug devices. C -logfile ani. Increase the timeout for the device on which you have configured the LE server. Make sure that the ATM address of the newly created LE server is not already present in the configuration server database.

Increase the timeout for the device on which you have configured the configuration server. Using the CLI, remove the existing configuration server database. The following is a sample configuration:. This subsection describes how you can use the tools within the AtmDirector application to troubleshoot and enhance your network.

The AtmDirector application logs error and debug messages that are useful when you need to troubleshoot your network or to resolve any problems.

The Global Preferences window opens. Step 2 Select the Miscellaneous index tab. The Miscellaneous options are displayed. Step 3 Click the On button to log error and debug messages, or click the Off button to stop logging the error and debug messages. Topology and discovery messages are automatically logged if the On button is selected. This is the default. Note If the discovery process is polling, messages are logged after Discovery has completed polling.

Step 4 Click OK. You can start or stop logging the error and debug messages while the AtmDirector application is running. The option that you select On or Off will not change when the application is terminated. Note It is recommended that you keep the debug option On. You can begin to troubleshoot your network and resolve any problems by analyzing the error and debug messages that have been recorded in the logfile of the AtmDirector application.

Note If there are no error or debug messages in the logfile, the logging option was not On. The AtmDirector application monitors devices and links at defined intervals and shows their status on the topology map by changing the colors of the affected device icons and indicating the status of the links. You can redefine the intervals by changing the SNMP polling. The Timeout parameter default is 5 seconds. If the polling process does not receive a response from a device in the time specified, the device is considered unreachable.

The Retries parameter default is three attempts. If the discovery process cannot reach a device in the specified number of attempts, the device is considered unreachable. The Data Collection Polling Interval parameter default is 30 minutes. This polling interval is used by RMON.

The Utilization Polling Interval parameter default is 10 seconds. This polling interval is used for the utilization calculations in the VC list. You can troubleshoot your ATM network or monitor the traffic and usage of its virtual channels VCs by using specific reports and graphical displays provided by the AtmDirector application. Refer to the following sections of online AtmDirector manual, located at the following web addresses, for the information you need:.

The AtmDirector application has some features that require you to enable data collection for troubleshooting purposes. The collected data is used to help you perform the following tasks:. Table displays problems that you might encounter while using the AtmDirector application and provides probable causes and possible solutions.

Set up the SNMP connection to the end host. Make sure that all device requirements are met. Determine which LEC is generating heavy broadcast usage.

Check the TopN clients. Check the menu item "Graphing Client Performance Information" to get information about the control frames and to change the configuration accordingly. Then select the LightStream switch that contains the node, and rediscover the device. Then check to see if the level of the PNNI node is the same as the other nodes. Also check to see if any interfaces for this node are configured to PNNI.

Note: If the node level and interface information is correct, you need to rediscover the device. In some cases, the TrafficDirector environment does not work as you would expect. This subsection includes tips for troubleshooting your TrafficDirector environment. It explains the following:. Because the operations personnel who set up and configured your SwitchProbe devices may be different than the TrafficDirector administrator, a quick review of the implications of configuration settings at the SwitchProbe device can help you isolate possible problems.

Before the TrafficDirector application can support viewing of NetFlow statistics on the Network Analysis Module, you must verify that the NetFlow option is enabled on the device. To ensure that the TrafficDirector administrator has access privileges to the local console on the SwitchProbe device using the TrafficDirector Remote Login application, you must grant the optional administrative privileges read and write access to the TrafficDirector administrator.

User access privileges, if set at the SwitchProbe device, allow you to view the console settings but not to edit them. This user-level security setting is useful if you have multiple sites where operations personnel may be asked to track down but not necessarily fix a SwitchProbe agent problem. If you do not know the administrative password at the SwitchProbe device and one is set, you cannot use the Remote Login application.

These SwitchProbe security features are independent of the security options that you can enable for access to TrafficDirector administrator applications. To ensure that properties files can be reinstalled automatically when SwitchProbe devices are rebooted, follow these steps:.

Step 1 Use the default scripts to run dvcfg either startup for most agents, or fstartup for Frame Relay agents. Step 3 Verify that the TrafficDirector dvtrap daemon is running. If these conditions are met, you do not need to manually reinstall the properties files through the Configuration Manager.

To test for network connectivity to the SwitchProbe device, use the Test Agents application. For more information about agent configuration issues, see the Cisco SwitchProbe Installation and Configuration Guide. It will always reflect the information about the port that was roved from the TrafficDirector application and is not updated.

To test an agent, Frame Relay agent, or switch, follow these steps:. Step 1 Select the agent you want to test from the agent list box, either from the TrafficDirector main window or from Configuration Manager.

Step 2 Do one of the following:. When a test is successful, the information in Table is displayed. When you have finished viewing the information, click OK to close the Agent Test window. Passed —The connection is fully operational. Not Supported —The connection is fully operational but is not supported by the Resource Monitor option. The agent read community name as entered in the Configuration Manager application , and whether this name is the same as the agent's established read community name OK or is not Failed.

The agent write community name as entered in the Configuration Manager application , and whether this name is the same as the agent's established write community name OK or is not Failed.

Whether Resource Monitor is enabled in the agent. The number of the agent interface used to monitor activity on a network segment. The type of interface distinguished according to the physical link protocol, as described in RFC The name of the person responsible for the agent, and how to contact that person.

The physical location of the agent, as defined by the system administrator in the Configuration Manager. The date and time that the agent became operational on the network. Also, when the agent was last booted. The test information that is generated when communicating with a switch is slightly different from the information generated when you test an agent.

When you test a switch, the TrafficDirector software queries the switch and informs you if the query passed or failed. Figure shows the Switch Test window. The switch read community name as entered in the Configuration Manager application , and whether this name is the same as the agent's established read community name OK or is not Failed.

The switch write community name as entered in the Configuration Manager application , and whether this name is the same as the agent's established write community name OK or is not Failed.

The name of the person responsible for the switch, and how to contact that person. The physical location of the switch, as described by the system administrator in the Configuration Manager.

The date and time that the switch became operational on the network. Also, when the switch was last booted. I would be pleased about if you help to keep this document up to date and make it more useful! So feel free to edit what you think can or should be changed! Thsi is a wonderful document Martin! I guess its time for update it to version 8 with LMS 4. Buy or Renew. Find A Community. Cisco Community. Thank you for your support!

We're happy to announce that we met our goal for the Community Helping Community campaign! Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. All Community This category This board.

Cisco Works - Applications and Versions -. Labels: Network Management. Martin Ermel. As a consequence, there are some basic changes: - the application and version schema does not exist anymore - patches are bundled and provided in a different way - you can only install LMS as a whole not e.

Tags: ciscoview. Joe Clarke. Hall of Fame Cisco Employee. Wassim Aouadi. Vinod Arya. Cisco Employee. Latest Contents. Ping Over Bytes. Created by DM on AM. We have a Cisco and when trying to ping with a byte size of over , the ping fails unable to ping across the WAN or within the same VLAN with anything over bytes.

This works on other 's with the same image so seems to be an issue w Created by d. Hey, I have one router an 2 core-switch. I want to config FHRP for the 2 physical interfaces.

But when i try to config the second sub interface i get the error: Created by nuancebvdr on PM. Questions about EEM trimleft. Created by oyuto on PM. I have a question about the result of execution in EEM's trimleft command. While all users can view installed package information, only System or Network Administrators can:.

Schedule downloads of device packages to occur regularly. If you schedule downloads, new device packages are automatically downloaded from CCO to your staging area.

Step 8 Download the. Step 9 Any prerequisite files will automatically be added to your device file and zipped for download. For instructions about installing device packages, see " Installing Device Packages. Any existing sessions of CiscoWorks for Windows 6. Before installing or uninstalling device packages, it is recommended that you close any open CiscoView sessions. Step 3 Click Browse , navigate to the device package directory, then click Select.

A list of available device packages is displayed. Each entry provides the package name, the. Step 4 To install one or more device packages, click the Select to Install check box. Sometimes when you try to install or uninstall a device package and find that the CiscoView Package Support Updater does not allow you to do it. This is because you have selected a package with interdependencies that will disrupt the functioning of another CiscoView device package.

In addition, the utility will not install a package whose superseding version has already been installed. When you download a device package, the NMIDB files are also downloaded in the current source file location. If there is not enough disk space, an error message is displayed. Installation progress is indicated by messages displayed in the dialog box. Table describes error messages that might be displayed if the utility encounters problems:. The CiscoView Package Support Updater dialog box appears and displays the installed device packages, including package names, descriptions, and current version numbers.

Step 2 To uninstall one or more device packages, click the Select to Uninstall check boxes in the List of Installed Packages list. If the file you want to uninstall is a prerequisite for another installed device package, you will be able to select the file, but you will not be able to uninstall it.

The CiscoView Package Support Updater validates the selection and displays an error message if the selected set of device packages are not compatible. If the selected device packages are compatible, the Confirm Uninstall Operation dialog box appears. When the uninstallation is complete, a summary page displays the results. Netscape Navigator 4.

Intel Pentium MHz or higher. SVGA color monitor and graphics adapter. Mouse or mouse-compatible pointing device. If you install all available device packages, CiscoWorks for Windows 6.