Guest

CiscoWorks Resource Manager Essentials

Release Notes for Resource Manager Essentials 3.3 on Solaris

  • Viewing Options

  • PDF (321.8 KB)
  • Feedback
Release Notes for Resource Manager Essentials 3.3 on Solaris

Table Of Contents

Release Notes for Resource Manager Essentials 3.3 on Solaris

New Features

Documentation Roadmap

Cautions

Additional Release-Specific Information Online

Known Problems

Server, Browser, and Desktop Known Problems

Installation and Upgrade Known Problems

Administrator Known Problems

Availability Known Problems

Config Editor Known Problems

Configuration Management Known Problems

Contract Connection Known Problems

Inventory Known Problems

NetConfig Known Problems

Software Management Known Problems

Syslog Analysis Known Problems

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Release Notes for Resource Manager Essentials 3.3 on Solaris


These release notes are for use with CiscoWorks2000 Resource Manager Essentials 3.3 running on Solaris. Supported Solaris versions are 2.6 and 2.7.

These release notes provide:

New Features

Documentation Roadmap

Additional Release-Specific Information Online

Known Problems

Server, Browser, and Desktop Known Problems

Installation and Upgrade Known Problems

Administrator Known Problems

Availability Known Problems

Config Editor Known Problems

Configuration Management Known Problems

Contract Connection Known Problems

Inventory Known Problems

NetConfig Known Problems

Software Management Known Problems

Syslog Analysis Known Problems

Obtaining Documentation

Obtaining Technical Assistance

New Features

Resource Manager Essentials 3.3 contains these new features:

Support for Java Plug-in.

Support for new devices. (See the Supported Devices in Resource Manager Essentials 3.3.)

Inventory—New Custom Reports

The Serial Number report displays information about the devices in the selected view.

The Service Assurance Agent (SAA) is an IOS feature that measures Round Trip Response Time (RTR).

Syslog Analysis—Support added for the WorkFlow application on Cisco's Media Convergence servers.

Documentation Roadmap

Use these publications to learn how to install and use Resource Manager Essentials:

Getting Started with the CiscoWorks2000 Server (DOC-787167=)—Provides information about setting up, administering, and assessing the CiscoWorks2000 Server.

Installing and Setting Up Resource Manager Essentials on Windows 2000 and Windows NT (DOC-7811556=)—Provides installation instructions, including both server and client side system requirements, steps for installing and uninstalling, and installation troubleshooting information

Installing and Setting Up Resource Manager Essentials on Solaris (DOC-7811557=)—Provides information about Resource Manager Essentials requirements and how to install Resource Manager Essentials on Solaris.

Using Resource Manager Essentials (DOC-7811544=)—Provides information on using Resource Manager Essentials.

Online help—Provides task-oriented and context-sensitive help from every window that contains a Help button.

All Essentials documents are provided in PDF on your product CD.

Cautions

Before using Resource Manager Essentials, ensure that:

All applications are stopped before you upgrade Essentials. The upgrade depends on having reasonable interaction time with the database. If this is not possible, the upgrade fails.

You do not have CWSI Campus 2.x and Essentials 3.3 on the same machine.

Additional Release-Specific Information Online

For information about Essentials supported devices, refer to the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/e_3_x/3_3/e3_3.htm

The Incremental Device Update (IDU) 2.0 for Resource Manager Essentials (Essentials) 3.3 is a collection of updated files necessary for Essentials 3.3 to support new Cisco devices:

In addition to the devices supported, this package also contains fixes to known problems, as well as additional newly discovered problems.

If you are a registered user, you can download IDU 2.0 for Essentials 3.3 from:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

Known Problems

This section contains known problems for Resource Manager Essentials.

Server, Browser, and Desktop Known Problems

Installation and Upgrade Known Problems

Administrator Known Problems

Availability Known Problems

Config Editor Known Problems

Configuration Management Known Problems

Contract Connection Known Problems

Inventory Known Problems

NetConfig Known Problems

Software Management Known Problems

Syslog Analysis Known Problems

Known problems are unexpected behaviors or defects in Resource Manager Essentials software releases. They are graded according to severity levels. These release notes contain information for severity levels 1 and 2 only.

You can search for known problems on the Cisco bug tracking system tool, called Bug Navigator II. To access Bug Navigator II,

Enter http://www.cisco.com/support/bugtools in your web browser.

Log in to Cisco.com and select BugNavigator II


Note Essentials supports U.S. English and Japanese.


Server, Browser, and Desktop Known Problems

Table 1 Server, Browser, and Desktop Known Problems 

Bug ID
Summary
Explanation

None

Browsers running on remote X servers.

Browsers running on remote X servers are not supported.

None

Cisco Voice Manager.

Cisco Voice Manager must be installed on a different machine than Essentials.

None

Printing from a browser does not work reliably.

To print an Essentials window, use Print Screen or Capture Screen function on your machine.

CSCdp22312

Multiple sessions of Essentials on a single client is not supported.

Only one instance of Essentials can be run from any given client.

CSCdp74251

Application performance is very slow with HTTP proxy.

Accessing Essentials via HTTP proxy might cause significant performance degradation.

Workaround:

Access CiscoWorks2000 Server directly from client.

CSCdp82755

Navigator 4.x: Cannot access CiscoWorks2000.

After Config Editor Job browser is launched, you cannot access CiscoWorks2000 Desktop or Java console.

Workaround:

Close Config Editor Job browser before trying to access other applications.

CSCdp08278

Tasks might fail if server is not 100% up.

If you try to access CiscoWorks2000 before server is running fully, Login Manager will not appear.

Workaround:

For Navigator, click Reload.

For Internet Explorer, click Refresh.

At beginning of CiscoWorks2000 session, if you select a task from navigation tree before server is running fully, the task might fail.

Workaround:

Select the task again. If this does not help, restart the system using one of these methods:

Use GUI. Select Server Configuration > Administration > Process Management > Stop Process, select the System radio button, click Finish, then select Server Configuration > Administration > Process Management > Start Process, click System radio button, then click Finish.

From command line interface, enter:
/etc/init.d/dmgtd stop
/etc/init.d/dmgtd start

Make sure all process are running before relaunching tasks. Select Server Configuration > Administration > Process Status. The State column shows whether processes are running.

CSCds24797

Netscape exits when you quit from NetConfig.

This happens when you run Netscape client on Solaris without Java plug-in enabled.

Workaround:

Run the Netscape client with Java plug-in enabled.

CSCds16984

Unable to launch Essentials from Netscape or Internet Explorer.

One of the possible causes is JRun Proxy Server process is not running.

Workaround:

Reboot the system, running RME server.


Installation and Upgrade Known Problems

Table 2 Installation and Upgrade Known Problems 

Bug ID
Summary
Explanation

None

ATM image version and image family might be incorrect after upgrade.

After an upgrade to Essentials 3.3, delete the ATM images and then reimport ATM images from software image library.

CSCdk89921

Essentials screen appears without the login applet.

Do not change default file ownership and permissions for /var/sadm directory. If you do, casuser will not be able to read files in directory.

CSCdp11661

Server error when attempting to open Inventory report.

If you install TrafficDirector after Essentials and select /opt/CSCOpx for TrafficDirector installation directory (or the subdirectory where Essentials is installed), TrafficDirector could corrupt Essentials.

Workaround:

If problem occurs, uninstall both Essentials and TrafficDirector and reinstall both products. Uninstalling only TrafficDirector, does not clear problem in Essentials.

CSCdr72068

Command syntax is not clear for restore backup.

Restore backup fails with fresh RME installation, for the command:

restorebackup.pl -d 
database-backup-directory

The output message does not clearly explains the command syntax to be followed for restoring database backup on fresh RME installation.

Workaround:

Execute the command

/opt/CSCOpx/bin/perl 
/opt/CSCOpx/bin/restorebackup.pl -force 
-d backup-directory
to restore the backup database after installing 
RME 3.3.

CSCdt86208

Re-installation of RME 3.3 over CD Two, 3rd Edition has problems in config operations.

If you have upgraded to RME 3.3 from CD Two, 3rd Edition and uninstalled RME 3.3 later, re-installation of RME 3.3 again over CD Two might have problems in config application.

Work Around:

Uninstall CD Two, 3rd Edition completely before installing RME 3.3 again.

CSCdt24499

Wrong query while reinstalling Resource Manager Essentials over CD Two (inventory only).

A query

"CW2000 has been detected on this 
system. Are you sure you want to 
reinstall (y/n)"

will be displayed if you try to reinstall Essentials on a server on which CD Two (inventory only) was previously upgraded to Essentials and Essentials was uninstalled later.

Workaround:

Enter y to continue with reinstallation of Essentials.

CSCdt82319

System View not present after restoring database from rme.dborig.

Applicable system view for Media Convergence Server and VPN Devices are missing when runtime rme.db is replaced with pre-packaged rme.dborig.

Media Convergence Server that is under Resource Manager Essentials > Syslog Analysis > WorkFlow Report.

VPN Devices that is under the following:

VPN Management Solutions > Reports > Configuration Management > VPN Configuration Reports

VPN Management Solutions > Reports > SyslogAnalysis > Advanced

Workaround:

After replacing rme.db with rme.dborig do the following:

1. Stop daemon manager.

2. Change directory to: /opt/CSCOpx/conf/bg2rigel/rme

3. Execute the command:

/opt/CSCOpx/bin/perl /opt/CSCOpx/dbupdate/dbupdate.pl r06000vpn.txt

4. Restart daemon manager.

This will re-insert missing Applicable System View to RME database.


Administrator Known Problems

Table 3 Administrator Known Problems 

Bug ID
Summary
Explanation

None

Starting Essentials as root.

If you start Essentials by logging in as root and entering /etc/init.d/dmgtd start, make sure you do not suspend session with the suspend command. If you suspend the root session after manually starting Essentials, other processes, such as Daemon Manager, DIServer, and IcServer, are also suspended.

Workaround:

Unsuspend the root session.


Availability Known Problems

Table 4 Availability Known Problems 

Bug ID
Summary
Explanation

CSCdt10034

Private Views of one user shown to other users.

When you create a private view and add this view to Availability polling, your view will be visible if another user logs and opens reachability dashboard or any other availability options.


Config Editor Known Problems

Table 5 Config Editor Known Problems 

Bug ID
Summary
Explanation

CSCdp98004

Stopping a running job.

Stopping a job while it is running could cause unpredictable results.

CSCdr09236

Config Editor fails to download interactive config commands.

If you try to download a configuration in "merge" mode and it has interactive configuration commands, such as set interface commands in Catalyst switches, the download fails.

Workaround:

Remove interactive config commands before scheduling a download.

CSCdr14391

Unable to edit config file from Solaris Netscape browser.

You cannot edit a file after opening it by Device and Version or Pattern search. Private copies previously opened are also affected.

Workaround:

Restart Config Editor. Open a new file to edit private copies.

This works fine if Java plug-in is enabled in RME 3.3 version of Config Editor.

CSCds13128

If two users try to open a configuration for a device simultaneously, the device may occasionally go into a state where it will be shown as locked, but neither of the users will be able to unlock the device.

Workaround:

Delete the device from inventory and add it back again.

CSCds15225

Super user is able to unlock a file while a user is editing it.

The device could go to an unmanaged state if a super user unlocks a file while a user is editing it.

Workaround:

Remove the device from inventory and add it again.

CSCdp97125

Running Config Editor from Config Viewer or VPN Config Reports leaves an empty browser.

If you run Config Editor from Config Viewer or VPN Config Reports, an empty browser is launched.

Workaround:

Do not close the browser or some features might not function properly.


Configuration Management Known Problems

Table 6 Configuration Management Known Problems 

Bug ID
Summary
Explanation

None

Running Resource Manager Essentials on Multi-homed Machines.

By default Configuration Management assumes a non multi-homed machine.

Workaround:

If you want to run Essentials on a multi-homed machine, set the variable MULTI_HOME=true in the ($NMSROOT)\objects\cmf\data\Transport.ini file and restart ChangeAudit process.

None

TACACS with SecureID.

Essentials configuration archive does not support TACACS with SecureID. It supports static passwords, defined when you add or import devices into the Essentials inventory.

None

Configuration Import message.

Cwconfig cannot validate the syntactic correctness of configuration files uploaded to device via the import command. As a result, the import is reported as successful even if configuration file is invalid. Configuration Update does not succeed, but Cwconfig cannot detect failure.

None

Banner commands on devices.

Banner values are contained between quotation marks (") in config archive and between Ctrl-C (^C) characters in a device.

When using NetConfig or Config Editor, or Telneting to a device, do not add quotation marks or Ctrl-C characters to banner commands on devices. Banner commands containing these characters cause configuration applications to function incorrectly.

Do not use Banner commands that contain multiple line banners.

None

Updating modules in Catalyst 5000 Switches.

Cwconfig does not update or change configurations of individual modules in Catalyst 5000 switches even when import or write2run commands report a successful download. Cwconfig updates only supervisor engine module configuration.

None

Standard device prompts required for Configuration Archive Telnet mechanism.

Telnet transport mechanism cannot retrieve or update device configurations if any of the remote devices have nonstandard device prompts.

Accepted, standard device prompts on Cisco IOS devices have strings ending with greater than symbol (>) or the pound symbol (#) at Telnet login and enable mode. Accepted, standard device prompts on Catalyst devices end with keyword "enable" at Telnet enable mode.

It is recommended that all managed devices should have passwords.

None

Devices with multiple IP addresses.

TFTP transport mechanism might not work for devices with multiple IP addresses when device is managed by using hostname in the inventory database. The SNMP library used by TFTP queries for only one IP address for a given hostname while resolving hostname with corresponding domain name server.

For a device with more than one IP address, the hostname resolution might not return IP address of the interface running the SNMP agent. In such cases, TFTP fails and displays SNMP Time Out Error.

Workaround:

Import devices using IP address in inventory database.

None

Module configuration not retrieved even if the module has valid credentials for a CAT switch.

Configuration Management will not retrieve the configuration of the modules which have valid TELNET credentials, if a previous module had wrong credentials.

If in a CAT switch, the supervisor and ATM module have the same credentials and RSM has a different one, Configuration Management will retrieve the configurations of Supervisor, fail for RSM module and display the following message, "ERROR: Incorrect Telnet passwords" and will also fail for ATM module displaying the same error, even if it has valid credentials.

CSCdk12667

Command-line syntax errors.

When a Cwconfig session has multiple syntax errors, only first detected error is reported. Others remain unlisted.

CSCdp91314

Netshow error: "java.lang.outOfMemory".

Netshow might flag a "java.lang.outOfMemory" error on a device. This problem occurs only with specific types of devices and only if the number of threads (set in properties file) and number of devices supplied to the command are both greater than one.

Workaround:

Run command line interface application on problem device alone, or reduce number of threads to one, and run serially.

CSCdp98087

Selecting Config Editor from Device Config report throws Java exception.

Select Resource Manager Essentials > Configuration Management > NetConfig and create a new job. Select a device from the Select Devices dialog box, and then select View Configuration to display Device Configuration Quick View Report. If you select Config Editor from this report, it gives a Java exception.

If you try to use both NetConfig and Config Editor from same browser, one might fail.

CSCdp62990

Change Audit Reports might time out.

If inventory contains 3000 devices or more, selecting Change Audit > All Changes or 24-Hour Reports > Change Audit Report might cause timeout.

CSCdr00103

Netsys: Message incorrectly confirms the creation of a baseline.

When creating a baseline using an invalid Netsys installation directory, a message appears stating that a Netsys baseline was created successfully, although it failed.

CSCdr03091

Netsys: Setting the baseline name value.

Netsys setup creates a directory called sConfig under the Netsys installation directory which contains config files. Essentials passes these config files to Netsys. This directory is deleted after setup.

Workaround:

You should not set baseline name value in Netsys setup to sConfig or any sub-directory.

CSCdr09236

cwConfig fails to download interactive config commands.

When you use import or write2run commands, remove interactive config commands before scheduling a download.

CSCds19913

Netshow Batch reports do not work when you restart JRM.

Restart Daemon Manager.

CSCds20036

Launching Copy Job from Job Details window does not work.

Copying a Job from Job Details window might not work sometimes.

Workaround:

Launch copy job from Configuration Management > Network Show commands > BatchReports > Job Browser.

CSCdt14616

Launching Edit job fails from Job Details window

Editing a Job from Job Details window may not work sometimes.

Workaround:

Launch Edit job from
Configuration Management  >  Network Show Command  > Batch Reports  > Job Browser.

CSCdt35384

Command entered in Upper case get entered as lower case

When you create a command set and enter command with certain parameters in upper case using Resource Manager Essentials > Configuration Management > Network Show > Define Command Set, it gets entered as a lower case.

Workaround:

None

CSCdt24115

Catalyst 5000 Devices: Transport FallBack from TFTP to Telnet Fails.

Catalyst 5000 device says 'Device is busy with previous operation, Try later' when config fetch operation is attempted.

The device going into busy state is a feature of the Catalyst 5000 switches and this is to prevent too many TFTP/Telnet connections within short intervals of time.

Workaround:

Change Transport Order to the Telnet as the first protocol.

CSCdt87380

cwconfig -help displays wrong copyright strings.

cwconfig -help displays the copyright date as 1998-2000 and does not display 2001.

Workaround:

Install RME33.IDU.v2-0.sol.tar.Z available at http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme


Contract Connection Known Problems

Table 7 Contract Connection Known Problems 

ID
Summary
Explanation

CSCdm87814

Essentials' Check Contract Status tool generates information for routers only.

If you select Resource Manager Essentials > Contract Connection > Check Contract Status, information is generated for routers only.

Obtain information from CCO URL:

http://www.cisco.com/cgi-bin/front.x/
csadispatch?AppName=ContractAgent

From View Contracts, select By Contract > Serial > Purchase Order > Service Order Number (Contract Lookup) and find contract information.


Inventory Known Problems

Table 8 Inventory Known Problems 

Bug ID
Summary
Explanation

None

Importing desktop machines.

Do not import desktop machines unless they are running Cisco Call Manager applications. Otherwise, desktop machine appears incorrectly in the device selector under Call Managers.

None

IP address may change between reboots.

You must import cable modems ubr904 and ubr924 using fully qualified pathname. These devices get the IP address of the cable interface using DHCP from head-end cable router. The IP address might change between reboots.

None

PIX Firewall device.

Configure PIX Firewall device so Essentials can manage it: Enter IP address of Essentials server.

None

Check device attributes feature does not work properly.

For some devices, Inventory > Check Device Attribute reports incorrect for correct device credentials like community string, telnet password, enable password and reports correct if the device attributes are wrong. This behavior is randomly seen and with different device attributes.

Workaround:

Redo the step once or twice.

CSCdk35153

Chassis modem table is not polled correctly.

Inventory reports show only configured modems. An interval exists between modem installation and modem configuration. During this interval, the Inventory application might detect only one modem. Additionally, log messages might display database integrity violations. These messages can be ignored.

Workaround:

Go to device and configure modem, then reacquire inventory data.

CSCdm75952

Do not use special characters in user fields.

Do not enter special characters such as apostrophes ('), semicolons (;), or parentheses in user fields.

CSCdm01805

Adding devices to Essentials fails.

Adding devices to Essentials fails if case-insensitive community strings already exist in database. If you add a device to a database with community strings similar to devices already present, import fails.

Workaround:

1. Change the device to use a credential that has same case (upper or lower) as successfully managed device.

2. Change device to use a unique value for credential.

CSCdp61331

Comma included in password will cause device import to fail.

In comma separated value (CSV) format, the "," character is used as a delimiter. Therefore, fields in the CSV file should not contain the "," character.

If you use a "," character in password or other fields while adding a device, the CSV file generated after exporting will be invalid. An exported CSV file cannot be used for importing devices.

CSCdp78299

Device card names do not appear in Detailed Device Report.

The Detailed Device Report for BPX 8600, IGX 8400, and IPX devices running switch software releases earlier than 9.1 does not show interface information.

CSCdr02713

Chassis Summary and Software Version Graphs fail.

If you click Chassis Summary Graph or Software Version Graph and select 2000 or more devices, the operation will time out after 5 minutes.

Workaround:

Reduce number of devices.

CSCdr81211

When a hitherto managed device is disconnected from the network, Scheduler does not report the status as `Not Responding'.

Once a device has been managed using Essentials, it will not display the status as `Unmanaged' or `Not Responding'.

Workaround:

Manually delete the device from the inventory.

CSCds48244

Import operations fail for 7100 and 7200 routers due to IOS bug.

Import operations may fail for Cisco 7100 and 7200 routers because of snmp timeout.

Workaround:

Select Resource Manager Essentials > Administration > System Configuration and increase Slow SNMP Timeout to a value more than 60 seconds.

CSCds73696

IcServer increasing in size.

IcServer shows steady increase in memory size of the process over time.

Workaround:

Restart IcServer daemon periodically.

Enter:
$NMSROOT/bin/pdterm IcServer $NMSROOT/bin/pdexec IcServer

where NMSROOT is the CW2000 install directory

CSCdt72151

Log file increases in size for every inventory collection.

Inventory schedule collection, manual update of inventory, inventory polling (If inventory change is detected) and syslog initiated inventory update results in increase of log file size.

Workaround:

Monitor and clean up the following log files on a periodic basis.

Solaris:

/var/adm/CSCOpx/log/daemons.log


NetConfig Known Problems

Table 9 NetConfig Known Problems 

Bug ID
Summary
Explanation

CSCdp05515

After an Essentials uninstall, Job Resource Manager does not remove NetConfig jobs.

If you uninstall Essentials 3.x, you might notice NetConfig jobs are still displayed under Server Configuration > Administration > Job Management.

Workaround:

Reinstall Essentials, then remove residual jobs by selecting unwanted jobs and clicking the Remove button.

CSCdr05712

Password template fails to get module configurations.

If you run NetConfig job to change the password on a device, and ATM and RMS modules on that device are configured with same telnet and enable passwords. Passwords on those modules and NetConfig job will fail to retrieve module configurations from device.

Workaround:

Select Update Archive for device after NetConfig job is done.

CSCdr09236

NetConfig fails to download interactive config commands.

In NetConfig, do not use interactive config commands such as set interface commands in Catalyst switches, with adhoc templates.

CSCdr50519

Cannot write to startup config after changing telnet password.

It is not possible to enable the 'Write Running Configuration to Startup Configuration' option in a NetConfig job that changes the telnet passwords. For all other templates this works fine. If this is done the job will fail when trying to write the Running Configuration to Startup.

Workaround:

Add an adhoc template that does a `write mem' instead of using the `Write Running to Startup Configuration' option.

or

A second job can be created with a harmless change and `Write Running to Startup Configuration' option enabled to run after the first one.

CSCdr33026

Working on Netconfig and Config Editor simultaneously on the user interface displays an exception.

If you:

1. Schedule a few jobs in NetConfig.

2. Invoke the Netconfig Job Browser.

3. Go to Cisco Works 2000 desktop and invoke the Config Editor Application.

4. In the Netconfig Job browser, select any Netconfig job and try to click the "Copy Job" Button.

Essentials displays an exception.

Note When Java plug-in is enabled and the same sequence is followed, Dr.Watson message pops up and closes the window.

Workaround:

Do not launch NetConfig and ConfigEditor from the same browser. One of them may not function properly.


Software Management Known Problems

Table 10 Software Management Known Problems 

Bug ID
Summary
Explanation

CSCds33889

Image download to and from device with subdirectory fails.

Distribution to a device or an image import job from the device having images in the sub directory fails. While importing the images from the device's subdirectory, SWIM considers the images in the subdirectory and continues to schedule the job but the job displays an error message.

Workaround:

Copy the images that have to be imported from the device to the root directory. For distribution, images are distributed only to the root directory using SWIM.

CSCdr87269

SWIM hangs if inventory contains 5000 or more devices.

If Inventory contains 5000 or more devices, and all devices are selected in SWIM, SWIM may hang when device specific queries are issued, or may generate an error message.

Workaround:

Select a maximum of 50 devices at a time before issuing the queries.

CSCds66601

Image upgrade is proper but job is reported as error (1900 series).

This occurs while upgrading a 1900 device over a slow network. When the 1900 device upgrade is in progress and exceeds 5 minutes, SWIM assumes that the job has failed as it received no response from the device.This results in SWIM marking the job as failed. However, the upgrade is successful.

CSCds71189

Remote Software Image Management (SWIM) upgrade of 2948G router fails when subnet contains 3COM devices.

Workaround:

Use Trivial File Transfer Protocol (TFTP) to upgrade 2948G router when subnet contains 3COM devices.

CSCdt36628

Baselining, sychronization and backup image fails for 7140-2FE.

This is because the sysConfigName variable is not populated in certain ATA flash card devices.

Workaround:

Import device manually.

CSCdt03226

SWIM upgrade for Cat3524 PWR XL fails

While upgrading a 3524-PWR-XL the XP series of images are also recommended. The 3524-PWR-XL has features that are not supported in the XP series images. 3524 PWR XL support only XU and XW series.

Workaround:

None.

Check the Release notes for the image before applying it on the device.

CSCdt36634

Baselining, synchronization and backup image fails for Catalyst 4232.

This is because the sysConfigName variable is not populated in certain versions of the image.

Workaround:

Import image manually from the device.

CSCdt33990

Undo feature not working for the PIX devices.

Workaround:

Schedule a new job.


Syslog Analysis Known Problems

Table 11 Syslog Analysis Known Problems 

Bug ID
Summary
Explanation

CSCdk47488

Changing the default logging facility.

Syslog messages are logged to a file configured to store local7.info messages from routers, but for PIX devices, the default is not local7.

Workaround:

Set PIX device to facility 23.

CSCdr77668

VPN 3000 series concentrators are not automatically updated in the inventory.

Workaround:

To update the inventory with current device status, do one of the following:

Schedule inventory collection on a regular basis (weeks, days, hours).

Set Inventory Poller Schedule to work on a regular basis.

Update Inventory as a one time event for specific devices. Syslog triggered inventory update does not happen for VPN concentrators. So, manual update or scheduled inventory updates are the only available means to do the update.

CSCds91728

Advanced option in Syslog Analysis accepts invalid severity.

Advanced option in Syslog administrative wizards accept invalid severity. Only 0-6 are valid severity levels. The wizard can accept 7, 8 and 9 also.

Workaround:

Make sure that the severity entered is between 0 and 6.

CSCdt19282

Exception error message thrown when you try to invoke "Syslog Message Reference" from Device Center.

If the syslog reports are generated from the
Device Center > All Syslog Messages option, then clicking on the details hyperlink generates error message.

Workaround:

The reports generated under the Syslog Analysis folder can be used to view the details of error explanations.

CSCdt32881

Workflow Report custom/private views are not displayed

Your custom/private views will not be shown in the device selector shown in Workflow Reports. This is irrespective of whether the custom/private view has a few or only Workflow devices.

All the Workflow devices will be shown in the MCS Servers system view. You can choose any of them to see the reports.

Workaround:

None


Obtaining Documentation

These sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com

Translated documentation is available at this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.

You can e-mail your comments to bug-doc@cisco.com.

You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:

http://www.cisco.com

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Cisco TAC inquiries are categorized according to the urgency of the issue:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://www.cisco.com/register/

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.