|
|
These release notes provide important installation information and describe the new features and caveats for the components of CiscoWorks for Switched Internetworks (CWSI) Release 2.1 (Solaris) and the Cisco Resource Manager (CRM) application, which ships with CWSI as a required installation component.
This document contains the following sections:
Before installing CWSI with CRM, make sure that the installation requirements described in this section have been met.
You must install CRM 1.1 before installing CWSI 2.1.1.
The hardware platform, memory, and disk space requirements for installing CWSI and CRM are as follows:
CWSI and CRM require either Solaris 2.6 or Solaris 2.5.1 software (with patch 103738-xx).
If you are using Solaris 2.5.1, Cisco recommends you use patch 103738-03 or later (103738-05 is the current patch) because it fixes a known Solaris problem with syslogd. The Solaris patch is available only to users with Sun service contracts. You can find additional information about the Solaris 2.5.1 patch at the following location:
http://www.cisco.com/kobayashi/sw-center/netmgmt/rm-planner.shtml
Review the following information before installing CWSI 2.1.1 and CRM 1.1:
| Device | Version |
|---|---|
| LightStream 1010 Series | Cisco IOS Release 11.2(801)FWA4_1 |
| Routers | IOS Release 11.2(10) |
| Catalyst 5000 Series | NMP (2.4.3)/ATM 3.2(5) |
| Catalyst 3000 Series | 2.2(2) |
| Software | Version |
|---|---|
| HP OpenView | 4.11, 5.0, and 5.01 |
| CiscoWorks | 3.2 and 4.0 |
| CWSI | 1.3 and 2.X |
If you have purchased and plan on installing multiple copies of CWSI 2.1.1 in your network, you should be aware of how CWSI's discovery process works in this environment.
The discovery process uses the Asynchronous Network Interface (ANI) daemon, which runs as a server process and exchanges information with other CWSI applications running as clients. Each ANI server is intended to manage a single domain. Therefore, if you install another copy of CWSI 2.1.1 configured with the same ANI server name (AniServer by default) in your network, unpredictable behavior might result depending on which ANI server the client chooses as it's default ANI server.
Depending on the available system resources on your initial CWSI system, this may result in poor system performance of all CWSI systems accessing and utilizing the resources of the default AniServer.
If you want to install another copy of CWSI to manage another domain, then you must manually configure your systems to run separate AniServer processes. This can be done as follows:
Step 1 Close all CWSI applications.
Step 2 Access the command prompt window by selecting Start>Programs>Command Prompt and stop the CWSI daemons by typing stopcwsiserver at the prompt.
Step 3 Access the <CWSIROOT>/bin directory on your system.
Step 4 Open and edit the cwsi.properties file with text editor
Step 5 Change the following line to rename the AniServer process running on your [local] workstation:
For example, if you just installed a Solaris version of CWSI, you could rename the AniServer to SOLAniServer.
After making these changes, save the file and close your text editor
Step 6 Restart the CWSI daemons (including AniServer on your local system) by rebooting your workstation or by typing startcwsiserver at the shell window command prompt.
You can uninstall CWSI if necessary by entering the following commands:
cd /op/CSCOcwsi/bin (or to wherever it is installed)
./uninstall.sh
After uninstalling CWSI, some directories and files might remain. If this is the case, delete these directories and files manually. If you are unable to delete them, and the message "the file is in use" appears, reboot your machine. You should then be able to delete the remaining files.
Refer to the installation guide (CD booklet) and the caveats in this section for CWSI startup information.
If you want to launch TrafficDirector from CiscoView, you must first make sure to source the TrafficDirector environment file. To source the file, enter the following at the command prompt:
source $CWSIROOT/.traffdir.cshrc
You can select and launch both CiscoView and TrafficDirector applications from HP OpenView (HP-OV) manager or SunNet Manager (SNM). The additional CWSI functions, including the CWSI topology mapping services, VlanDirector, AtmDirector, and UserTracking applications, must be started from the main CWSI interface, which is launched from Solaris as part of the normal start-up procedures for CWSI.
TrafficDirector and CiscoView are device-focused applications and are easily launched from HP-OV and SNM based upon the device discovery process within HP-OV and SNM. The additional CWSI functions require more detailed network-wide topology data than HP-OV and SNM can provide. The CWSI discovery and database services must be running for these additional applications to function, which means you need to start these services from the main CWSI window.
The CWSI components are as follows:
This section contains information that applies to all of these components. Notes and caveats for the individual components are described in these release notes in the sections about the specific component.
In addition to these release notes, the CWSI documentation set includes the following documents:
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback on the toolbar, and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Using an X terminal to access and control CWSI 2.1.1 applications is not officially supported.
Many X terminal systems might appear to run some of the CWSI functions satisfactorily. However, there is a known problem when running a CWSI client to an X display on a non-Solaris workstation. JavaSoft's Java Runtime Engine (JRE) does not function properly because fonts are specified that are not available on many X11 servers. The result is that the X server on the remote system refuses to establish the session and exits.
A possible workaround is to delete (or rename) the /opt/CSCOcwsi/lib/font.properties file on the CWSI client machine (that is, the Solaris machine where AniServer is running). The X terminal will revert to its default fonts and an X session can be established. The workaround has is known to work when displaying on the following platforms:
The above procedure is a workaround and is not supported by Cisco.
The online help supports Netscape 3.0 and 4.0 and Internet Explorer 4.0 (not Internet Explorer 4.0 with Active Desktop). The online help does not support Internet Explorer 3.0.
If you choose to use Netscape as your browser and it has not already been installed, you can install it at any time. CWSI does not provide the interaction for the user to view and accept the Netscape licensing information, so you must launch Netscape at least once before launching CWSI help so that you can accept the Netscape licensing information. If you do not launch Netscape before launching CWSI help, CWSI help will not launch.
All CWSI 2.1.1 components are Year 2000 compliant.
Some of the error messages do not have online help. The Help button on the error message window is unavailable (grayed-out).
This section contains important information about the CWSI network map.
This section provides device-specific caveats about the CWSI network map.
Moving ports between virtual local area networks (VLANs) will fail on Catalyst 3000 switches running software versions prior to Release 2.2(2).
Not all modules are shown in the Node Attributes window. You can access the Node Attributes window by selecting the device and clicking the right mouse button. [CSCdj40028, CSCdj40030]
The following are LAN Emulation (LANE) issues:
In Getting Started with CWSI, page 3-4 incorrectly shows an Edit option called "Delete Device." This feature is not available, and was documented in error.
The temporary workaround is to delete all links to the device, and then drag the device icon to an less conspicuous corner of your map. However, this action does not actually delete the device from the database or system configuration.
This section describes new features and provides notes and caveats for the VlanDirector application.
The VlanDirector application provides the following new features:
This section provides important notes and caveats about the VlanDirector application.
The VlanDirector application permits you to display and configure the VLANs in your network. It requires at least one VLAN trunking protocol (VTP) server for each VTP domain. Other switches may be configured as VTP clients to participate in the VTP protocol, or may be configured in transparent mode, ignoring the VTP advertisements.
You must use the VlanDirector menu properties dialog window to enable VLANs on switches in transparent mode.
If there is an LS1010 switch in your network that is unreachable, the VlanDirector application will not highlight trunk links in the network. To resolve this, ensure that CWSI can talk to all LS1010s in the network.
After a new VLAN and its associated ATM VLAN have been created through CWSI, the VLAN name is displayed in the VlanDirector Names window under a VTP Domain folder. However, its associated ATM VLAN is displayed under a Fabric folder.
CWSI cannot ensure the bridging of a VTP VLAN to an ATM VLAN until LANE LEC clients (created outside of CWSI) join the LANE services (created by CWSI). After the LANE LEC clients are created (using the CLI or through enabling VTP), doing a Rediscover Map (on the CWSI Topology window) and a Refresh (on VlanDirector) will bind the ATM VLAN to the VLAN and show it as one VLAN in the Names window.
Although CWSI supports Simple Server Redundancy Protocol (SSRP), CWSI does not support LANE on a fabric containing multiple active LECS (that is, acting as master). When CWSI LANE discovery runs on such a fabric, CWSI chooses and processes the first active LANE configuration server (LECS) it encounters and ignores the other active LECS. All backup LECS will be processed by CWSI.
When multiple LES/BUS servers are specified to be configured as part of the CWSI ATM VLAN configuration, CWSI processes these configurations in parallel and cannot guarantee that the ORDER field which corresponds to each server matches the actual priority order of the created server.
The Discrepancy Report does not include any LANE discrepancies.
When an ATM fabric name is changed through the ATMDirector application, it is not automatically reflected in CWSI. The new ATM fabric name will be correctly displayed in the VlanDirector Names window after you do a Refresh in the VlanDirector application. [CSCdj68621]
UserTracking is a new application within CWSI that allows you to:
This section describes the features of and provides notes and caveats for the UserTracking application.
The UserTracking application uses information that it reads from network devices switches and routers) to display information (for example, MAC address and IP address) for network administrators about end-user nodes attached to switches in the network. The UserTracking application displays information for end-user nodes connected to ports that are statically assigned to a specific VLAN as well as for end-user nodes that are connected to ports that are dynamically assigned a VLAN based on the MAC address of the end-user node.
For Ethernet networks, the UserTracking application also enables network administrators to create and download configuration information (MAC-to-VLAN mapping information, and groups and port restriction information) to VMPS servers.
The VMPS mapping information you specify in the UserTracking application is used only when you connect an end-user node to a dynamic port. When you connect an end-user node to a static port, the node is connected to the VLAN that is statically associated with that port; none of the UserTracking information about MAC-to-VLAN mappings pertains, though information about such end-user nodes is displayed in the UserTracking client.
UserTracking cannot discover the MAC addresses of end-user nodes on VLANs that exist only on switches running VTP in transparent mode (sometimes called local VLANs).
UserTracking does not work with secondary addresses configured on a router. UserTracking checks only the lowest IP subnet configured on an interface. The application does not find addresses on other subnets.
If ping sweeps are enabled (by selecting either Action>Ping Sweeps>Enable or Action>Discover>Subnet...), UserTracking performs a ping sweep only for subnets with Class C IP addresses. It does not perform ping sweeps for subnets with Class A or Class B addresses.
When you invoke Action>Configure TFTP Servers, you might not see any domains displayed in the Select Domain list in the upper left hand corner of the window. This situation might occur for the following reasons:
There must be a router present in your network for UserTracking to display any entries.
Catalyst 5000 series switches must be running software release 2.3 or higher.
If you export a table in UserTracking and try to read it with Microsoft Excel version 7.0, by default Excel formats the data in the Port column as a date if the Port column uses a module/port format. For example, the field might contain the entry 2/3, to which Excel applies its general format. The 2/3 will be interpreted as a date and will be expanded to 2/3/1997.
You can resolve this situation in Excel. When you import the file in Excel, you go through the Text Import Wizard. In Step 3 (of 3), you can specify how Excel will format each column being imported. Scroll the window until the Port column is visible and select it. In the Column Data Format box, select Text. Excel will then treat the Port column as text rather than converting it to a date.
In UserTracking, you can discover a specific subnet by selecting Action>Discover>Subnet.... UserTracking displays a dialog window in which you can click a check box to specify whether you want UserTracking to perform a ping sweep process before acquiring information for the specified subnet. If you select to perform the ping sweep process and click the Discover button, the UserTracking client will be unresponsive until the ping sweep process completes. This could take several minutes. When the ping sweep process completes, UserTracking displays a message that the discovery process has been initiated. When the discovery process completes, UserTracking displays a message that the discovery process has completed.
This section describes new features and provides notes and caveats for the TrafficDirector application.
The TrafficDirector application includes the following new major features and enhancements:
This section provides note and caveats about the TrafficDirector application.
The TrafficDirector 5.1 application does not support the creation of Alarms and Events for any device running IOS 11.1 or greater. The TrafficDirector application assumes that the RMON statistics group is always supported, which is not the case for IOS.
Deleting all TRAPs from an agent does not delete the ADMIN entry. By default, TrafficDirector listens to TRAPs 162 and 395.
In Configuration Manager, when specifying the analyzer port number for a roving agent, you must specify a two-digit port number. For example, for Module 5 port 2, you would specify 5/02 as the module/port. The module/port number must match the port name in the window.
Only the first eight characters of any agent name, switch, or port are displayed in Configuration Manager.
The CWSI 2.1.1 TrafficDirector application ships with the default pingoff file. This file is required for successful pings on selected agents if you are running either the Solaris or TCP/Pro TCP/IP stacks. For pings to be performed successfully when you are running any other TCP/IP stack, delete $NSHOME/usr/pingoff.
To integrate the TrafficDirector application with other NMS platforms, refer to "Integrating Traffic Director with Other Managers" in Appendix C of Using TrafficDirector.
When you try to print a TrafficDirector screen that contains more than one graph per file, the TrafficDirector application drops the last letter of the name you specify and replaces it with a number. The application creates a separate file per graph.
When setting thresholds on a device with a large number of ports (more than 100), you may encounter performance problems. The thresholds will be installed, but this may take up to five minutes. [CSCdj47127]
In order to launch TrafficDirector Port Zoom from the CWSI Topology window, the CiscoView td_intg package must be installed. Select Help>About to check whether this package is installed. If it is not installed, you must install it from the CWSI CD. If you selected all packages when installing CWSI, then this package is installed.
Table 2 indicates whether you need to use either a shared property file or a custom property file when configuring a specific property for agent or switch type.
| Agent Class | Properties | ||||||
|---|---|---|---|---|---|---|---|
| Monitor Domains | Domain Traps | Report Logging | RT Delays | RT Logging | Proxy SNMP | Resource Traps | |
| Agent | Shared | Shared | Shared | Custom Mgt Intf. | Custom Mgt Intf. | Custom Mgt Intf. | Custom Mgt Intf. |
| Frm-Rly | Shared | Shared | Shared | Custom Mgt Intf. | Custom | Custom Mgt Intf. | Custom Mgt Intf. |
| DLCI (Frm-Rly) | Protocol domains from Shared | Custom | Custom | N/A | N/A | N/A | N/A |
| Switch | Shared | N/A | N/A | N/A | N/A | N/A | N/A |
| Switch Ports | Shared is copied | Custom | Custom | N/A | N/A | N/A | N/A |
Table 3 lists the devices supported by the TrafficDirector application.
| Device1 | RMON Support2 | Roving Support |
|---|---|---|
| Catalyst 1200 | Full RMON I | n |
| Catalyst 1600 | Mini-RMON | y |
| Catalyst 1800 | Mini-RMON | y |
| Catalyst 1900 | Mini-RMON | y |
| Catalyst 1912 | Mini-RMON | y |
| Catalyst 2100 | Proxy RMON | y |
| Catalyst 2800 | Proxy RMON | y |
| Catalyst 2820 | Mini-RMON | y |
| Catalyst 2900 | Mini-RMON | y |
| Catalyst 2926 | Mini-RMON | y |
| Catalyst 3000 | Mini-RMON | y |
| Catalyst 3100 | Mini-RMON | y |
| Catalyst 3200 | Mini-RMON | y |
| Catalyst 3900 | Mini-RMON | y |
| Catalyst 5000 | Mini-RMON | y |
| Catalyst 5002 | Mini-RMON | y |
| Catalyst 5500 | Mini-RMON | y |
| Catalyst 5505 | Mini-RMON | y |
| CPW2200 | Mini-RMON | y |
| 2500 Series | Full RMON I | n |
Proxy RMON is not supported for the Catalyst 1700 switch in this release.
The following installation and startup issues exist for this release of the TrafficDirector application:
Error accessing agent domain rmon while retrieving ETSTATS error: entry or group not present in agent.
When a property file is installed on a probe, the file is applied to all ports on that probe. If you have a multiport probe, be aware that when defining the properties, the last property files to be installed are applied to all ports on that probe. To avoid conflicts, either ensure that the property files for each port are identical or define properties for only one port on the probe.
The TrafficDirector application can be used to set TRAPs on non-RMON MIB objects. (For example, a non-RMON object would be ifOutoctets, which is the number of bytes within a packet transmitted out of a router or switch port.)
To set a TRAP on a non-RMON OID, following these steps:
Step 1 Edit the $NSHOME/usr/usrtrap.oid to include the non-RMON OID MIB.
Step 2 Access Configuration Manager.
Step 3 Select the switch, then select Custom.
Step 4 Select Property.
Step 5 In the bottom half, select Add.
Step 6 In the Stats Type field, select User Defined, then select the non-RMON OID from the trap variable field.
Step 7 Select OK.
Step 8 Select Install.
An alternate way to set the TRAP is to add the MIB to the $NSHOME/usr directory in the same format as the other '*.mib' files. You can then use the Proxy SNMP feature with a probe to configure the TRAP.
The TrafficDirector 5.1 application roves to the specified port when you select data capture from the main TrafficDirector screen. For other applications, such as All Talkers, perform roving manually from Configuration Manager or launch the application from Traffic Monitor. [CSCdj62108]
If you want TrafficDirector 4.1.3 and TrafficDirector 5.1/CWSI 2.1.1 to coexist on the same machine, you must make sure that your environment settings are set correctly. To ensure this do the following:
To run TrafficDirector 4.1.3, enter the following command:
source <TD 4.1.3 directory>/.traffdir
To run TrafficDirector 5.1, enter the following command:
source <TD 5.1 directory>/.traffdir
If you are using a switch probe for roving and monitoring a switch, please note that the probe does not reinitialize itself or relearn its location when it is physically moved from one location to another (for example, SPAN destination has changed). If you disconnect your probe and reconnect it to another switch or a different port on the same switch, you must reinitialize your probe. This step can be done by resetting the probe; if you are running CWSI 2.1.1 for Solaris, run the 'rm_rove' script in the $NSHOME/usr directory. If you fail to reinitialize the probe, you will encounter errors when trying to use the probe for roving.
The Catalyst 3900 switch supports only the following Token Ring RMON MIB groups:
If you try to set thresholds on objects in any of the other Token Ring groups, an "Install aborted unexpected SNMPAPI Error" error appears. [CSCdj52569]
This section describes new features and provides notes and caveats for the AtmDirector application.
This section describes the new features of the AtmDirector application.
The AtmDirector application now provides a main AtmDirector naming window, which has a list of all ATM Fabrics and ATM-VLANs within that fabric in form of a tree structure. The Private Network-Network Interface or Private Network-Node Interface (PNNI) peer group information also appears in the lower section of the window. You can use this window for viewing summary information and for navigating to map windows.
The consolidated status of the ATM-VLANs is reflected in the main window on the ATM-VLAN cloud icon. If there are any ATM-VLAN components that are down, the icon turns red.
The fabric name can be changed by editing the name in the tree widget. To edit the name, click on the fabric name again after selecting it and type in a new name.
VC trace now displays the trace on the main fabric map showing the VPI/VCI values that are used between devices.
VC list between devices feature allows you to click links between two end devices and to view the list of VCs between the two devices.
Enhanced traffic parameter setup is provided during configuration of SPVC/SPVP. You can also add new Traffic table rows in the agent for future use.
Link status is also polled periodically and link downs are displayed with a dashed line.
The AtmDirector application now displays a topology map for each ATM-VLAN showing all the ATM-VLANs components and the links between those components.
the status of each ATM-VLAN component is displayed as background colors on the corresponding icons.
Context-based popup menus are available by pressing the right mouse button while moving the mouse over the ATM-VLAN components.
The map contains menu options for Status, Diagnosis and Performance tools for debugging the LANE network.
The AtmDirector application now displays a logical PNNI map with the node topology with all the nodes in one Peer Group.
The AtmDirector application configures and displays various PNNI properties in the PNNI network.
The AtmDirector application now allows you to set up a soft permanent virtual circuit (SPVC) or soft permanent virtual path (SPVP) between end stations that are not displayed on the ATM fabric map. Replace the procedure, "Setting Up Soft Permanent Virtual Channels or Paths," on page 7-10 in the Using AtmDirector guide with the following procedure.
You can set up SPVCs or SPVPs between two end stations in an ATM network, whether they are displayed on the ATM Fabric map or not.
To set up an SPVC/SPVP between two manageable end stations, you configure the SPVC/SPVP by selecting the links connected to the two end stations.
To set up an SPVC/SPVP between two unmanageable end stations, you configure an SPVC between the ATM switch ports to which the end stations are connected.
To set up an SPVC/SPVP, follow these steps:
Step 1 From the AtmDirector main window, select the source and destination link or switch, depending on whether the end station is manageable or not:
(a) To set up an SPVC/SPVP between two manageable end stations, select the source and destination links connected to the end stations.
(b) To set up an SPVC/SPVP between two unmanageable end stations, select the source and destination switch to which the end stations are connected. If the two unmanageable end stations are connected to the same switch, select only that switch.
Step 2 Select Tools>SPVC/SPVP Setup or SPVC/SPVP Setup from the toolbar.
The SPVC/SPVP Setup window opens (Figure 1).
Step 3 Select either SPVC or SPVP.
The ATM address is automatically filled in, depending on the destination link selected.
Step 4 If you are configuring an SPVC/SPVP between two unmanageable end stations, you need to define the switch ports to which these end stations are connected. Select the ports from the pull-down list in the ATM Port fields.
Step 5 Select either VCI (for SPVC) or VPI (for SPVP) from the Used VCI/VPIs pull-down list, or enter that value in the Used VCI/VPIs field.
Step 6 Click Advanced Parameters, if you want to specify traffic parameters for the SPVC or SPVP.
The advanced parameters options window opens (Figure 2).
Step 7 If you clicked Advanced Parameters, set the SPVC parameters as follows:
(a) Enter the interval between connection retries for setting up SPVC/SPVP in the switch in the Slow Retry Interval field.
(b) Set up Usage Parameter Control (UPC) values as follows:
(c) If you clicked Advanced Parameters, click Select to specify the transmit traffic parameters. The Traffic Descriptor Table window opens displaying all the currently available traffic descriptors (Figure 3).
Step 8 Select one of the traffic parameter rows. When you select a row, the values from that row are filled in the fields below, which explains the meaning of each parameter. Refer to Table 4 for an explanation of the traffic parameter fields.
(a) Click Apply. The values are filled in the Traffic Parameter fields in the SPVC/SPVP window.
(b) In the SPVC/SPVP window, select the Rx. Traffic Parameters field to specify the receive traffic parameters.
(c) Repeat Steps 8(c) and 8(d).
(d) Click Close to close the Traffic Descriptor Table window.
Step 9 Click Rerouting/Route Optimization Parameters in the SPVC/SPVP window to configure the Rerouting parameters for the SPVCs/SPVPs originating from the source interface.
The Reroute Parameters window opens (Figure 4).
Rerouting is done automatically for Soft PVCs. If a fault occurs along the path of an SPVC/SPVP, a different path will re-established automatically. No configuration is necessary to turn this feature on.
The SPVC/SPVP route optimization feature is used to return connections to shorter paths when the original paths come back up. This is done by periodically checking the administrative weight of the current path against the administrative weight of the best path seen by the PNNI process. This feature must be configured to take effect. The period and time-of-day interval can be configured to control when rerouting to better paths can take place.
Step 10 Configure the fields in the Reroute Parameters window as follows:
(a) Click the ReRoute check box to configure rerouting for the interface.
(b) Click Soft PVC to set the interface type to SPVC.
(c) Set the number of seconds for the Optimization Interval using the pull-down list.
(d) Set the start and end times for rerouting to be in effect by sliding the bars to the corresponding start and end times on the timeline.
(e) Perform one of the following actions:
Step 11 Click Apply in the SPVC/SPVP window.
The configuration request is sent to the source switch. Error messages are displayed in a popup window.
| Field | Explanation |
|---|---|
| QoS | Quality of service. |
| PCR (0+1) | Peak cell rate, in cells per second, for cells with cell loss priority 0 or 1. |
| PCR (0) | Peak cell rate, in cells per second, for cells with cell loss priority 0. |
| SCR (0+1) | Sustained cell rate, in cells per second, for cells with cell loss priority 0 or 1. |
| SCR (0) | Sustained cell rate, in cells per second, for cells with cell loss priority 0. |
| CDVT | Cell delay variation tolerance in cell-times. |
| MBS | Maximum burst size in cells. |
| MCR | Minimum cell rate in cells per second. |
Add the following section after the "Setting Up Soft Permanent Virtual Channels or Paths" section on page 7-15 in the Using AtmDirector guide.
To configure interfaces on switches, follow these steps:
Step 1 From the AtmDirector main window, select the switch containing the interface or the switch and link that you want to configure.
Step 2 Select Tools>Interface Configuration....
The Interface Configuration window opens (Figure 5).
Step 3 If you selected only a switch from the AtmDirector main window, select the interface to configure using the pull-down window in the ATM Port/Interface field. If you selected a switch and link from the AtmDirector main window, the interface number is automatically displayed in the ATM port/Interface field.
Step 4 Configure the Interface Parameters as follows:
(a) Click Enable or Disable in the Auto Interface Type Detection field.
(b) In the Type field, select the type of interface from the pull-down window. Valid types are PNNI, IISP, UNI, NNI PVC Only, and Others.
(c) In the Interface Side field, select the side of the interface that you are configuring. Valid values are User, Network, and Not Applicable.
(d) Click the Interface hard reset required check box if the switch to which the interface belongs is running a Cisco IOS software release lower than 11.2(10)WA3(4)r. If the switch is running 11.2(10)WA3(4)r do not click this check box.
Step 5 Configure the Link Selection and Administrative Weight parameters using the field descriptions in Table 5.
| Field | Description |
|---|---|
| Link Selection | Specifies the method for selecting a link for constant bit rate and variable bit rate call setups. Options are as follows:
|
|
Adm. Wt. CBR | The administrative weight of this interface for the constant bit rate service category. |
| Adm. Wt. rtVBR | The administrative weight of this interface for the real-time variable bit rate service category. |
| Adm. Wt. nrtVBR | The administrative weight of this interface for the non-real-time variable bit rate service category. |
| Adm. Wt. ABR | The administrative weight of this interface for the available bit rate service category. |
| Adm. Wt. UBR | The administrative weight of this interface for the unspecified bit rate service category. |
Step 6 Click Rerouting in the Interface Configuration window (Figure 5) to configure the Rerouting parameters for the SPVCs/SPVPs originating from the source interface.
The Reroute Parameters window opens (Figure 4). Configure the fields as follows:
(a) Click the ReRoute check box to configure rerouting for the interface.
(b) Click Soft PVC to set the interface type to SPVC.
(c) Set the number of seconds for the Optimization Interval using the pull-down list.
(d) Set the start and end times for rerouting to be in effect by sliding the bars to the corresponding start and end times on the timeline.
(e) Perform one of the following actions:
Step 7 Click OK to apply the configuration to the interface.
This section provides note and caveats about the AtmDirector application.
ATM-RMON features are not available in this release, but will be available in the following release. The unavailable features are reflected by the grayed-out menu options listed below:
The following items in ATM-VLAN map are not supported:
The polling feature is not supported for nodes displayed in the PNNI map. Nodes in the PNNI map appear as light blue, indicating that the PNNI node operational status is not polled.
The following caveats apply to the ATM main window:
The following caveats apply to the ATM fabric map:
Traffic Type not understood. To resolve this, add a new row for the ABR traffic with the appropriate traffic parameters and apply it towards the SPVP/SPVC setup.
In some cases while displaying the Control Connection VCs, the Destination Host name field is blank. This situation is caused by the host name not being correctly resolved from the ATM Address.
The following caveats apply to PNNI:
Help is currently unavailable from the SPVC/SPVP Setup window in the AtmDirector Fabric map. Refer to the "SPVC/SPVP Configuration" section in these release notes for information about this window. [CSCdj89381]
CWSI 2.1.1 is a network management product that focuses on managing Cisco Catalyst and Light Stream switches. As part of the CWSI product, CiscoView also provides basic device management of routers.
New devices are supported on all platforms unless otherwise noted. A README file describing device support is included on the Cisco Connection Online (CCO) service. Make the following selections from CCO to locate the CiscoView device support packages:
The latest devices packages are located within the Download CiscoView Software Updates section on this page.
To mount and install devices from the support CD, refer to the special CD booklet included in the package. Be sure to read the README files on CCO.
This section describes new features and provides notes and caveats for the CiscoView application.
The latest devices packages are located within the Download CiscoView Software Updates section on this page.
The number of MIB objects that can be queried has been increased from 512 to 2048.
Caution Before installing CiscoView devices, read the caveats in "Troubleshooting"This section provides notes and caveats for the CiscoView application.
CiscoView devices support Cisco IOS Software Release 10.2 through Release 11.2. Cisco 4000 series devices require Cisco IOS Release 10.3 or later.
New devices and further specific information on Cisco IOS support will be updated as devices become supported. For the online release notes, refer to one of the following:
New devices are supported on all platforms unless otherwise noted. A README file describing device support is included on the Cisco Connection Online (CCO) service.
The following devices are supported by CiscoView:
Table 6 describes the applications supported by CiscoView.
| Application | Description | Cisco IOS | Device Support |
|---|---|---|---|
| Threshold Manager1 | Threshold management application that monitors the availability and performance of Cisco devices. | Release 11.1 or 11.2 with RMON events and alarms group support | All devices with appropriate Cisco IOS or RMON features |
| StackMaker | StackMaker manages the device membership in a Cisco stack. | Releases 10.0 through 11.2 | Cisco and CiscoPro 1600, 3600, 3620, 3640, Catalyst 1900, Catalyst 2820, CPW1220, CPW1420, Fasthub 100+ and NetBeyond Fasthub 300 |
| Flash File System | The Flash File System provides file copying and editing features for the 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers. | Releases 10.0 through 11.2 | Cisco 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers |
If you cannot open a device in CiscoView, a message indicates that the device is unmanageable and specifies one of the following reasons:
When the SNMP Debug option is enabled, it displays a separate pop-up console window that shows the SNMP traffic to and from the device. If you close this window, CiscoView will exit.
If you start CiscoView on the interface icon of an expanded node (for example, foo.cisco.com:1), you will not be able to telnet to that device because telnet thinks it should use port 1. Do not start CiscoView on device interfaces. [CSCdi56385]
In high traffic situations, you might experience timeouts. To increase the timeout period, select Options>Properties from the CiscoView menu and change the value for the Timeout field.
Do not reduce the physical view polling interval below (retries*timeout), especially if you experience timeouts. This reduction can exhaust resources on Windows and result in a general error.
If you want to upgrade the Catalyst 5000, Catalyst 5500, Catalyst 2900, or CPW 2200 to device package version 2.1, you must upgrade each of the other packages mentioned if they are installed and if you want to continue to manage the device.
For example, if you want to upgrade the Catalyst 5000 device package to 2.1 and you also have the CPW 2200 installed, which you want to continue to manage, you must also upgrade the CPW 2200 to device package version 2.1.
To delete an entry from the Set Managers configuration, enter an IP address of 0.0.0.0. The agent on the devices will not accept a blank entry for an IP address. [CSCdj03444]
When using the Switch Zoom menu (if Traffic Director is installed) from CiscoView to view multiple switch ports, the default configuration for the Catalyst 1200 is to configure Statistics, Short-Term history, Long-Term history, and Host group. To see the Short-Term or Long-Term history from Traffic Monitor, use the Configuration Manager to configure the Short-Term and Long-Term group manually or use Segment Zoom to view the port first.
If you launch Switch/Port Zoom from CiscoView and then delete one of the RMON Agents using TrafficDirector, you must relaunch CiscoView before attempting to launch Switch/Port Zoom again.
If you see an "IP address is not set in sysIpAddr MIB variable" message, the Catalyst 1200 SNMP agent is not storing the correct IP address in the sysIpAddr MIB variable. To correct this situation, use CiscoView to select Configure>Device, enter the correct IP address in the corresponding field, then click Modify.
The device agent does not update the IP Address Table of MIB-II properly and does not reflect the correct IP Address information of all the device interfaces. You will not be able to view the correct IP Address information of the device by selecting Device>Configure>IP Address Table.
You will not be able to create new static entries for IP Route Table and ARP Table through CiscoView.
In the interface configuration (Port>Config>Interface), if you modify the IP parameters, an error message always appears but the modification completes successfully.
You will not be able to change the bridge type of the FDDI port to sr-only or srt.
You will not be able to change the bridge type of the Token Ring port to srtb or tb-only.
The system time configuration is not included as part of device configuration.
CPW1200, CPW1220, CPW1400, CPW1420, Catalyst 1900, Catalyst 2100, Catalyst 2800, and Catalyst 2820--The General Bridge window shows the bridge information for VLAN1 only. Bridge information for other VLANs is not available.
CPW1220, CPW1420, Catalyst 1900, and Catalyst 2820--In the CDP Configuration Dialog window, changing the transmission time of one port will change the transmission time of all ports. This is a feature of the implementation of the corresponding MIB objects in the device firmware. [CSCdi83959]
CPW1200, CPW1220, CPW1400, CPW1420, Catalyst 1900, Catalyst 2100, Catalyst 2800, and Catalyst 2820--The Spanning Tree Protocol Window for switched ports is available for ports in VLAN1 only. This window does not show valid information for ports not in VLAN1.
On the front panel display of the device, the Connect and Disabled LEDs on FDDI modules do not reflect the appropriate status.
Although there is a Monitor menu option available for both FDDI and repeater ports, this feature is not supported on these modules.
The Configure>Module option is supported for only one module type, even though it can be invoked for multiple module types.
The Catalyst 2600 device package contains two versions of the enterprise MIBs for the Catalyst 2600 switch:
If you are using a MIB browser tool, you will see the MIB variables defined in each of these versions under different branches at the same time. However, any particular Catalyst 2600 switch will respond to queries on only one of the MIBs based on the release of software in the device. Cisco recommends that you upgrade your Catalyst 2600 switches to version 2.2.1 or later.
If you launch Switch/Port Zoom (if the TrafficDirector application is installed) from CiscoView and delete one of the RMON Agents using TrafficDirector, you must relaunch CiscoView before attempting to launch Switch/Port Zoom again.
When multiple ports are selected, the Port>Configure window will not display the Broadcast Suppression category. This feature is available for single-port selection only.
When you enable port security administration on a port, timeouts may occur. If this situation happens, increase the SNMP timeout value to approximately 10 seconds.
The WS-X2901 module speed LED is lighted only when the speed is configured as 100 Mbps and the port is connected.
When accessing a stack with six or more devices, you might encounter some significant performance problems. The performance can be improved by increasing the SNMP timeout settings.
The Catalyst 3000 software does not support RMON on either a stack or an ATM port.
You might notice timeout messages and SNMP Set Failed messages when using the EtherChannel Configuration tool. If this happens, increase the SNMP timeout values for better performance.
If you are running version 2.0(1) of the Catalyst 3000 software, you will not be able to drag a port to a VLAN that does not already have ports assigned to it. This problem can be fixed by upgrading to a later release of Catalyst 3000 software.
If you are running version 2.0(1) of the Catalyst 3000 software, changes to Full/Half Duplex settings will not always be reported correctly. This problem can be fixed by upgrading to a later release of Catalyst 3000 software.
If you are running version 2.0(1) of the Catalyst 3000 software, the SAID value entered when creating a new VLAN will be redisplayed as a different value. However, the VLAN will have been created with the SAID value you specified. This problem can be fixed by upgrading to a later release of Catalyst 3000 software.
Because of restrictions in the Catalyst 3000 software, the WS-X3006B is displayed in CiscoView as a WS-X3006A.
If you launch Switch/Port Zoom from CiscoView (if Traffic Director is installed) and then delete one of the RMON Agents using TrafficDirector, you must relaunch CiscoView before attempting to launch Switch/Port Zoom again. TrafficDirector works only if CWSI is installed.
CiscoView does not show the rear view of the Catalyst 3900 box.
When attempting to drag ports to drop into one of the CRFs in the VLAN table, CiscoView might exit with an error. To work around this problem, first select the ports of interest, then bring the focus back to the VLAN Table Window, and then drag the selected ports and drop them into the desired CRF.
The Configure... option under Bridge Configuration category allows you only to view a current configuration. This option reports an error when you attempt to configure new values for any parameter.
The Threshold Manager and TrafficDirector applications have not been fully tested with the Catalyst 3900.
If you are using CiscoView 4.1 and want to view or manage both LightStream 1015 and WS-X5304, you must install the system module update (SMU) for the Catalyst 5X00 RSM from the following location:
ftp://ftp.cisco.com/cisco.netmgmt/ciscoview/4.1
If you are using CiscoView 4.0 and want to view or manage the WS-X5304, you must install the SMU for the Catalyst 5X00 RSM from the following location:
ftp://ftp.cisco.com/cisco.netmgmt/ciscoview/4.0
In some cases, after an online insertion/removal (OIR) event (also called a "hot-swap"), CiscoView does not show the correct module or port status. The only way to display the correct status is to re-open the device, or relaunch CiscoView. [CSCdj39860]
ATM, FDDI, and CDDI do not support Broadcast Suppression.
For machines that do not have a /tftpboot directory (such as a PC), an error will be displayed whenever the Upload/Download feature is invoked on a Catalyst 5000 module.
When using the Switch Zoom menu (available only if the TrafficDirector application is installed) from CiscoView to view multiple switch ports, the default configuration for the Catalyst 5000 switch is to configure Statistics only. To see the Short-Term or Long-Term history from traffic monitor, use the Configuration Manager to configure the Short-Term and Long-Term group manually or use Segment Zoom to view the port first.
When you select the repeater module port on a Catalyst 5000 switch, it always uses the first port of the selected segment to create the RMON agent group.
If all Catalyst 5500 slots are populated with modules and you experience timeouts, increase the SNMP timeout value to 15 seconds.
The WS-X5213 and WS-X5213A modules show the 100 Mbps speed LED lighted only if the speed is configured at 100 Mbps and the port is connected.
If a general error (genErr) is displayed when changing vlanPortIslStatus, the selected port may not support ISL.
The values ifAdminStatus and ifLinkUpDownTrapEnable cannot be changed on an ATM port.
Port duplex settings cannot be changed on ATM and FDDI ports.
The value portSpanTreeFastStart cannot be changed on ATM and FDDI ports.
Table 7 details the availability of Broadcast Suppression in terms of packets per second (pps) or percentage (%) for modules on Catalyst 5000 series switches. The following conventions are used in the table:
Modules not on this list do not have Broadcast Suppression. The Broadcast Suppression feature is not available on ATM and FDDI. [CSCdi90909]
| Module | Packets per Second (pps) | Percentage | Note |
|---|---|---|---|
| WS-X5013 | + | + | |
| WS-X5011 | + | - | |
| WS-X5010 | + | + | Percentage available with newer hardware only |
| WS-X5113 | + | - | |
| WS-X5111 | + | - | |
| WS-X5213 | + | - | |
| WS-X5020 | + | - | |
| WS-X5114 | + | - | |
| WS-X5223 | + | + | |
| WS-X5224 | + | + | |
| WS-X5213A | + | - |
If you are configuring ports to unsupported speeds, a general error (genErr) is displayed. This is due to a problem in the device software.
For NetBeyond Fasthub 100+ and 300 Series devices that have an expansion module, the port numbering is not consistent with the management console. Ports 17 through 32 are listed in CiscoView as Repeater 2: Port 1 through 16. [CSCdi77159]
After the first reset of a NetBeyond Fasthub 100+ and 300 Series device, you must set the rptrReset MIB variable to noReset (default value) before the next reset can be performed. This is due to a problem on the device software and will be fixed in a later release. [CSCdi77452]
On a Catalyst 116 and CPW 316 fasthub, to delete an entry from the Set Managers configuration, enter a blank field. The IP address of 0.0.0.0 will not remove the entry from the Set Manager Table.
The CPW 1200/1400 and Catalyst 2100/2800 devices do not support the CDP and CGMP protocols. The CiscoView dialogs for these will display error messages.
When multiple ports of different types are selected, selecting Port>Config might show duplicate categories.
A Cisco IOS defect causes CiscoView to not display the "DS1 Line Channelized info" when a T1/E1 port is configured for "cas-group." This is applicable when the option is selected from the global menu item "Connection Info" or if it is selected through the Line_ds1 config dialog box. [CSCdj44707]
In the channel_modem view, CiscoView does not properly reflect the status of the T1/E1 channel_ports (timeslots) that have been configured for "channel-group." This is a Cisco IOS software problem.
When you try to open a horizontal-chassis device, such as the 7204, 7206, or 7505, with a Fast Ethernet port adapter installed, the error message "can't read 'DD(port-23.port-26.pos)': no such element in array" is displayed. To fix this bug, upgrade to the latest 7000 CiscoView package at http://www.cisco.com/cgi-bin/tablebuild.pl/cview40 [CSCdj16247]
No MIB object is associated with the test port on a CT3IP card. [CSCdj18638]
CiscoView always displays the multimode fiber SC type of ATM connector on the ATM interface processors (AIPs), even when the media interface is another type. [CSCdi53420]
CiscoView displays an FEIP2-FX interface processor as an FEIP2-TX for all Cisco IOS versions before Release 11.1(11)CA. [CSCdj15831]
An invalid port level FSIP Config category will appear for devices with MIP cards running Cisco IOS software before Release 11.1. The dialog box shows N/A for the variables displayed in it, because these are not applicable to it. [CSCdj23970]
To configure an LECS address for a LightStream 1010 from CiscoView, ServiceId needs to be the following:
10.1.3.6.1.4.1.353.1.5.1.Index
where Index is the row differentiator for configuring multiple LECS addresses. Index is an integer.
From CiscoView for LS1010, ATM Traffic Descriptor table does not show any rows. This is an agent bug. [CSCdj00685]
The creation of the full-text search database (Find option) in online help might take several minutes, depending on the number of devices you have installed. Because of the way a master CiscoView contents file is used by the software when multiple CiscoView device package help files are present, the list of files to include when setting up a customized find operation contains multiple items, all called "CiscoView." [CSCdj62089]
The Cisco 4000 Series Help incorrectly states that they are stack devices. There is also a link to the StackMaker Help that does not work. To reach StackMaker Help, ensure the StackMaker Help package is installed and select Help>Contents to locate the StackMaker Help topics. [CSCdj01872]
Before providing procedures for troubleshooting, this section includes a description of the CWSI daemons and their interactions with clients.
Asynchronous Network Interface (ANI or AniServer) is a multithreaded Java program. ANI is responsible for the discovery of the network, both of devices and users. It is also responsible for all communication with the clients.
The database engine (dbEng50) is responsible for checkpointing all ANI information into the database. For ANI, this is a checkpoint only. ANI performs all of its operations from the data stored in memory. The database stores user-entered information and allows ANI to load its data model quickly into memory upon a subsequent restart. (The CRM database engine has the same name, so your system should be running two processes with this name.)
The CORBA agent (OsAgent) is responsible for monitoring interprocess communication messages. All servers must register with the OsAgent. All clients looking for service can find it with the help of the OsAgent. Use the CWSI login window to register the CWSI client with OsAgent and to indicate that OsAgent is searching for an ANI named AniServer.
To see all servers registered with CORBA, and where they are located, run osfind.exe from a DOS window.
This very useful troubleshooting tool is found in $CWSIROOT/bin.
RTPoller is used for periodic polling of the network for status of devices and links.
The event channel (EventChannel) is used to send events to all servers and clients who have registered with it.
The following command-line scripts control the CWSI daemons:
To use these scripts, open a shell window Command Prompt window. Enter stopcwsiserver to stop the CWSI server processes. When the shell prompt returns, all the daemons have been stopped. To restart the processes, enter startcwsiserver and wait until the shell prompt returns. Wait a few minutes to allow the processes to start and get into a steady state before starting CWSI.
After running osfind, if you see that the AniServer or one of the other servers is missing, or you see in the processes lookup that your database engine is missing, stop the CWSI servers and start them again.
If you have just rebooted your machine and are unable to log in to AniServer, ANI may not yet be ready to receive messages. Wait five minutes, then try again.
If you are still unable to log in, run the osfind program to verify that AniServer has registered with the OSAgent. If so, verify that the name of AniServer in the login box is the same name as the name registered with OsAgent.
If you do not find AniServer, run the stopcwsiserver script (see "Stopping and Starting CWSI Daemons," earlier in this section), then run the startcwsiserver script. Run osfind again. If AniServer is there, log in to CWSI. If AniServer is still not registered, you might have a corrupt database.
To determine whether you have a corrupt database, first turn on trace to see if messages indicate this condition. If you are still unable to verify the status, contact your Cisco TAC for instructions.
ANI cannot perform effectively with a corrupt database. If you determine you have a corrupt database, you need to create a new one.
To create a new database, follow these steps:
Step 1 Run the stopcwsiserver script.
Step 2 Delete the current database $CWSIROOT/db/data/cwsi.db.
Step 3 Copy the file cwsi_ini.db to the file cwsi.db. This is a fresh database file.
Step 4 Delete the file cwsi.log.
CRM ships with CWSI and is a required component to successfully run CWSI. This section contains information, notes, and caveats about CRM.
CRM is supported on the browsers shown in Table 8.
| Browser | Version1 | Operating System |
|---|---|---|
Netscape Navigator2 | 3.03 | Solaris 2.6 and Solaris 2.5.1 |
| 3.04 | Windows NT 4.0 and Windows 95 | |
| 4.03 | Solaris 2.6, Solaris 2.5.1, Windows NT 4.0, Windows 95, HP-UX 10.20, and AIX 4.2 | |
Microsoft Internet Explorer3 | 3.02 | Windows NT 4.0 and Windows 95 |
| 4.0 | Windows NT 4.0 and Windows 95 |
CRM supports the devices listed in Table 9. See the "Cisco IOS Versions Supported" section for information on the supported Cisco IOS versions. See the "Devices Supported by Software Management" section for the devices that the CRM Software Management module supports.
| Routers and Access Servers | Switches | Hubs | ||
|---|---|---|---|---|
| Cisco | CiscoPro | Cisco | CiscoPro | |
| CS500 | Viper Switch CPW16, ESP2015 | FastHub 300 and FastHub 100+Series FastHub 316T, 316C, 3116, 216T, 116T, 116C, 1116 | ||
| 741, 742, 743, 744, 751, 752, 753, 761, 762, 765, 766, 771, 772, 775, 776 | CPA741, CPA742, CPA743, CPA744, CPA751, CPA752, CPA753, CPA761, CPA762, CPA765, CPA766, CPA771, CPA772, CPA775, CPA776 | Catalyst 1200, 1220, 1600, 1700, 1800, 1900, 2200, 2600, 2820, 2900, 2908, 2910, 2916, 2924, 2926, 3000, 3001, 3011, 3100, 3200, 3500, 3900, 5000, 5002, 5301, 5500, 5505 | ||
| 1000, 1003, 1004, 1005, 1020 | CPA1000, CPA1003, CPA1004, CPA1005, CPA1020 | EtherSwitch 1000, 10/100, 1200, 1220, 1400, 1402, 1408, 1420, 1422, 1428, 1442, 1448, 1600, 1601, 1900, 2100, 2200 | CPW1100, CPW1200, CPW1220, CPW1400, CPW1402, CPW1408, CPW1420, CPW1422, CPW1428, CPW1442, CPW1448, CPW1600, CPW1601, CPW1900, CPW2200 | |
| 1601, 1602, 1603, 1604 | CPA1601, CPA1602, CPA1603, CPA1604 | Workgroup concentrator 1000, 1100, 1400 | ||
| LS1010, LS2020 | ||||
| 2500, 2501, 2502, 2503, 2504, 2505, 2507, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 2516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF | CPA2500, CPA2501, CPA2502, CPA2503, CPA2504, CPA2505, CPA2507, CPA2509, CPA2510, CPA2511, CPA2512, CPA2513, CPA2514, CPA2515, CPA2516, CPA2517, CPA2518, CPA2519, CPA2520, CPA2521, CPA2522, CPA2523, CPA2524, CPA2525, CPA2501CF, CPA2502CF, CPA2501LF, CPA2502LF | Stratacom BPX, IPX, IGX (Version 8.1 and later)
StrataCom Axis (Version 2.1 and later) | ||
| 2102, 2202 | ||||
| 3000, 3620, 3640, 3101, 3102, 3103, 3104, 3202, 3204 | CPA3620, CPA3640
| |||
| 4000, 4000-M, 4500, 4500-M, 4700, 4700-M | CPA4000, CPA4000-M, CPA4500, CPA4500-M, CPA4700, CPA4700-M | |||
| AS5200, AS2509RJ, AS2511RJ, AS5300 access servers | ||||
| 7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513 | ||||
| Router IGS, AGS+, AccessPro RC, AccessPro EC, Router Gateway Server | ||||
The CRM Software Management module supports Cisco IOS system software upgrades for the following devices:
Full support is provided for devices running Cisco IOS Versions 10.3 to 11.2 only. Unless your devices are running at least Cisco IOS Version 10.3, all of the MIB values might not be supported. As a result, devices running versions of IOS earlier than 10.3 might not provide all device details.
The documentation for CRM consists of the following items:
Customer documentation can also be found on the Cisco Enterprise Customer Documentation CD or on Cisco Connection Online (CCO).
A CCO web page for CRM contains links to marketing and technical documentation and includes the latest downloadable CRM files. To find the latest CRM information, point your web browser to the following location:
http://www.cisco.com/kobayashi/sw-center/netmgmt/rm-planner.shtml
This section contains the notes and general caveats that apply to CRM on the Solaris 2.6 and 2.5.1 operating systems. It consists of the following sections:
CRM relies on host-name-to-IP-address lookup for accessing devices and interacting with the web server. The lookup mechanism used by the CRM server must guarantee that all host name lookups for a given IP address always return the same string for all environments in your network. See the Cisco Resource Manager 1.1 Installation Guide for Solaris for more information about server requirements.
Using the Apache http server to support software not installed by CRM is not supported.
The following caveats describe installation issues.
If the Solaris system on which you are installing CRM already has a web server running on port 80, you must ensure the following line appears in /etc/services file to indicate its presence:
httpd 80/tcp # web server
If you do not enter this line, CRM will conflict with the other web server. [CSCdj60413]
If you install CRM somewhere other than the default directory (/opt/CSCOpx), the uninstall script, uninstall.sh, does not remove the CRM directory. To resolve this issue, run the following commands after running uninstall.sh:
# cd /opt
# rm -f ./CSCOpx
# rm -rf directory
where directory is the full pathname to the directory in which CRM was installed.
If you are upgrading to CRM 1.1 from CRM 1.0, Cisco recommends you back up your database completely when you complete the upgrade.
If any screens do not look right, for example, if a graph looks awkward or text scrolls off a screen, reload or refresh the browser page. If you reload or refresh the page, the problem usually corrects itself.
The printing feature does not work reliably. To print an exact copy of a CRM screen, use the Print Screen or Capture Screen function on your machine.
If your site operates behind a firewall that is filtering JavaScript, you might not connect successfully to the CCO home page if you select Home > Cisco Connection Online > Home Page. The CCO home page will generate errors because of JavaScript references outside the <SCRIPT> tag boundaries. To avoid this situation, do not select the home page, because it is the only page using JavaScript. [CSCdj56560]
The following sections describe caveats for particular web browsers.
If you alternate between CRM windows and windows not generated by CRM, Navigator 3.x might not display the CRM navigation tree. If you have administrative privileges, click Login. If you logged in previously, the navigation tree appears. If you did not log in previously, the Login dialog box appears and you can log in normally.
If you do not have administrative privileges, exit the browser and relaunch it.
To avoid this situation completely, do not use the CRM browser window for interacting with other Web-based applications. Launch a separate browser instead. [CSCdj56775]
The Navigator 4.03 right mouse button popup menu provides the Open Frame in New Window option. If you select this option while in CRM and continue using CRM in the new window, you will receive error messages and CRM will not complete its tasks. To avoid this, complete all tasks in CRM windows. [CSCdj50947]
On Solaris, HP-UX, and AIX systems, Navigator 4.03 does not dynamically update the Reachability Dashboard (Tasks>Availability>Reachability Dashboard) when devices change state. To update the information in the Reachability Dashboard, click the Navigator Reload button. [CSCdj55007]
If you access the Glossary (Help>Glossary) with Navigator 4.03 on a Solaris, HP-UX, or AIX system, clicking the Back button in the help window might take you to the help contents page instead of the beginning of the glossary section. To return to the Glossary, click Glossary. [CSCdj57449]
If you are using Navigator 4.03 on an HP-UX system, the Get button does not appear when you open the Ping dialog box (Tools>Connectivity Tools>Ping) or the Traceroute dialog box (Tools>Connectivity Tools>Traceroute). To display the Get button, either enter the desired name in the Device field and press Enter, or click the space between the Device field and the Clear button. With either action, the Get button appears. [CSCdj58691]
If you click the Help button in the Filter Select Devices window after logging into CRM when using Navigator 4.03, Navigator displays a message stating that access is disallowed. The Filter Select Devices window appears when you add static or dynamic views, or when you produce reports. [CSCdj60013]
If you click the Help button in the Filter Select Devices window when using Internet Explorer 3.02, Internet Explorer displays a Microsoft Jscript runtime error instead of Help. The Filter Select Devices window appears when you add static or dynamic views, or when you produce reports. [CSCdj62204]
You cannot correct typing errors in the Save Static Views dialog box (Admin>Device Views>Add Static Views>Next) with the Backspace key if you are using Internet Explorer 4.0. To correct text, you can either select it and enter the desired information, or you can move the cursor to the left of the mistyped characters and press the Delete key to remove them. [CSCdj56328]
The following caveats describe issues with administration functions.
In the "Preparing to Use Resource Manager Packages" chapter of the Cisco Resource Manager 1.1 Installation Guide for Solaris, you are told to verify that TFTP is enabled by entering one of the following commands:
# netstat -a | grep tftp
or:
# /opt/CSCOpx/bin/mping -s tftp localhost_machine_name
The /opt/CSCOpx/bin/mping command does not work for Solaris 2.6; use the netstat command instead. [CSCdj58219]
If you start CRM by logging in as root and entering the following command in a C shell:
#/etc/init.d/dmgtd start
Make sure you do not suspend the root session using the suspend command. If you suspend the root session after manually starting CRM, other processes such as the Daemon Manager, DIServer, and IcServer are also suspended. To resolve this issue, unsuspend the root session, and the processes restart normally.
If you select Tasks>Availability>Availability Monitor and select a device to view its availability, the Availability Monitor dialog box appears. If you click the Interface Status icon for a device, the Interface Details dialog box appears. If you use the page up or page down keys to scroll up and down the screen, you might get the following error:
Internal Error: Unable to retrieve cookie for form element <element> Probable Cause: The cookie might have expired or it was not set in the browser.
This error message might result from the expiration of the cookies, which are used to pass cgi-bin parameters to the reports. To resolve this issue, retry the operation. [CSCdj19695]
The CRM Inventory Manager can actively manage approximately 1,000 devices. Because of restrictions in the software, the Availability module does not correctly track devices if you ever added or imported more than 4,000 devices into the CRM database. If you added or imported more than 4,000 devices, the AvInputGen process has a memory failure, and the list of devices polled by the Availability module is never updated.
To avoid this issue, upgrade to Availability 1.2 when it becomes available on CCO. Until Availability 1.2 is available, contact the TAC for assistance. [CSCdj83419]
When you add or import a device or change device information, avoid using angle brackets (< or >) in the User or Serial Number fields. When some browsers encounter these characters, they might interpret the information incorrectly. [CSCdj24567]
If you encounter problems when importing devices, make sure your target system is configured correctly. Consult the following CRM online Help topics for instructions on what you need to do before importing devices:
When troubleshooting a device import from HP OpenView or CiscoWorks, you can run the DataPrep.pl script from the command line to help determine the cause of the failure. If you enter the command-line options incorrectly or omit them, DataPrep.pl will not report any errors. Refer to the CRM online Help for the correct use of the DataPrep.pl script and troubleshooting. [CSCdj54272]
The Software Management feature distribute software to most Cisco IOS devices and Catalyst switches. The distribution is verified and scheduled so multiple devices can be updated quickly and easily.
The following caveats describe issues with Software Management.
If you import a large number of images that takes more than 20 minutes to complete, the browser might time out and display a message that says, "Document contains no data." To avoid this issue, decrease the number of images you import at one time to ensure that the import takes less than 20 minutes. [CSCdj25733]
If you import an image from CCO when the temporary directory's file system is full, you might receive server errors when executing other CRM functions. To avoid these errors, keep the temporary directory clear of unneeded files. [CSCdj44161]
If you select the Use tftp fallback option in the Job Control Information dialog box when setting up an upgrade for IOS devices, CRM leaves unused software image files in your temporary directory (/var/tmp). Cisco recommends you remove these files from this directory when the upgrade is complete. [CSCdj62050]
If you do not select the Error halts processing of subsequent devices option in the Job Control Information dialog box, the software upgrade status is reported as complete even if some devices failed to upgrade their software. Review the Job Summary windows to confirm the success or failure of the upgrade on each device in the job. [CSCdj57460]
When upgrading software images, single Flash bank devices require Telnet access. Therefore, when adding the device to the CRM, you must provide the appropriate passwords and access information. Refer to the online Help for more information about passwords and access information.
RSP 7000 and 7500 series routers running Cisco IOS Versions 10.3(x) through 11.0(x) do not support Flash MIBs. As a result, RSP 7000 and 7500 series routers running one of these IOS versions require Telnet access when you upgrade their software images, and you must provide the appropriate passwords and access information. Refer to the online Help for more information about passwords and access information.
Router Switch Modules (RSMs) on Catalyst 5000 and 5500 devices run IOS software and have their own host names and IP addresses. To upgrade the RSM on a Catalyst device, select the IOS device type in the Select Device Type dialog box (Tasks>Software Management>Distribute Images) and click Next. The Select IOS Devices dialog box appears. Click Add and enter the host name of the RSM module in the device name field in the dialog box that appears. Add the RSM host name to inventory as well. [CSCdj62469]
The following caveats describe issues with syslog analysis.
Syslog analysis does not show the primary facility of Channel Interface Processor (CIP) messages. For example, the CIP message:
..%CIP4-6-MSG: %MSG802-6-LLC.START: Starting LLC-2...
will be stored as:
%MSG802 6 LLC_START Starting LLC-2...
where MSG802 is the facility, 6 is the severity, LLC_START is the mnemonic, and the remaining text is the description. The first part (CIP4-6-MSG) is not used. Only the second part of the CIP messages is stored. [CSCdj16580]
For Catalyst devices only: If you do not receive syslog messages in the syslog analysis reports (Tasks>Syslog Analysis) and the syslog message file (/var/log/syslo.info file pointed to by local7.info in the /etc/syslog.conf file) does contain messages, the DNS name or the name defined in /etc/hosts is different from the name in the CRM inventory. To resolve this issue, change the DNS name or the name in /etc/hosts so the device name is the same as the name in the CRM inventory. [CSCdj58347]
Syslog analysis ignores some valid messages if the message it is processing is from a device that is imported with an IP address and is in an unmanaged state. To avoid this situation, import devices using their host names rather than their IP addresses. [CSCdj60068]
Syslog reports do not have IOS explanations for some messages. Refer to the latest IOS reference manual for additional information on reported messages. [CSCdj61218]
SmartNet or warranty support calls for CRM 1.1 running on the Solaris Japanese release are handled during Japan standard time only through the Japanese TAC.
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the Information Packet that shipped with your product.
For service and support for a product purchased directly from Cisco, use CCO.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
|
|
