Table Of Contents
RME Troubleshooting Tips and FAQs
Device Management
Inventory
Inventory Reports
Archive Management
NetConfig
Config Editor
Software Management
Syslog Analyzer and Collector
Job Approval
Bug Toolkit
cwcli config
cwcli export
NetShow
Administration
Contract Connection
RME Troubleshooting Tips and FAQs
This Appendix covers the Troubleshooting tips and FAQs for:
•
Device Management
• Inventory
• Inventory Reports
• Archive Management
• NetConfig
• Config Editor
• Software Management
• Syslog Analyzer and Collector
• Job Approval
• Bug Toolkit
• cwcli config
• cwcli export
• NetShow
• Administration
• Contract Connection
For other Installation related FAQs and Troubleshooting tips, see the Installing and Getting Started with CiscoWorks LAN Management Solution 3.0
Device Management
This section provides troubleshooting information and FAQs for the Device Management application:
• Device Management FAQs
• Troubleshooting Device Management:
Device Management FAQs
• Can we add or import devices directly to RME?
• How can I verify that the Device Credentials configured on the device match those in the RME inventory?
• How do I edit the device credentials in RME?
• How can I check the device credentials while adding the devices to RME?
• What are device credentials and RME device attributes?
• How are the device credentials mapped in Device and Credential Repository?
• What happens when I delete a device in RME?
• What are the most frequent causes of device import failures?
• How do I increase the SNMP Timeout and Telnet Timeout values for RME devices?
Q. Can we add or import devices directly to RME?
A. No, you cannot add or import devices directly to RME. You have to first add or import devices to Device and Credential Repository (DCR) (Common Services > Device and Credentials > Device Management).
If the Automatically Manage Devices from Credential Repository option is enabled in the Device Management Settings window (Resource Manager Essentials > Admin > Device Mgmt > Device Management Settings), then the devices are added automatically to RME. By default, this option is enabled.
If this option is disabled, then you have to add devices to RME manually from RME Devices window (Resource Manager Essentials > Devices Device Management RME Devices).
Q. How can I verify that the Device Credentials configured on the device match those in the RME inventory?
A. Click on the View Credential Verification Report in the Device Credential Verification (Devices > Device Management > Device Credential Verification) dialog box:
–If you have already selected the credentials that have to be verified then the Credential Verification Report appears.
–If you have not selected the credentials that have to be verified, then a message appears:
None of the devices have credential verification data. Click Check Device Credential to select the credentials that have to be verified and then click Credential Verification.
See Using Device Credential Verification Window section in Chapter 3: Adding and Troubleshooting Devices Using Device Management of the User Guide for Resource Manager Essentials 4.1 for more information at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_user_guide_list.html
Q. How do I edit the device credentials in RME?
A. You can edit the credentials either in:
•Common Services (Common Services > Device and Credentials > Device Management > Edit (button)
or
•RME (Resource Manager Essentials > Devices > Device Management > Device Credential Verification > Edit Device Credentials (button))
Q. How can I check the device credentials while adding the devices to RME?
A. To check the device credentials while adding devices to RME, you have to enable the Verify Device Credentials While Adding Devices option in the Device Management Settings window (Resource Manager Essentials > Admin > Device Mgmt > Device Management Settings).
You can select the device credentials that have to be verified in the Device Credential Verification Settings window (Resource Manager Essentials > Admin > Device Mgmt > Device Credential Verification Settings).
Q. What are device credentials and RME device attributes?
A. The following are the device credentials:
•SNMP Read Community String
•SNMP Write Community String
•SNMPv3
•Telnet
•Telnet Enable Mode User Name and Password
•SSH
•SSH Enable Mode User Name and Password
The following are the RME device attributes:
•Serial Number
•SNMP Retry
•SNMP Timeout
•Telnet Timeout
•RME ID (NAT ID)
Q. How are the device credentials mapped in Device and Credential Repository?
A. The following table describes the mapping of device credentials in Device and Credential Repository:
Device Credentials
|
Device and Credential Repository
|
Telnet password
|
primary_password
|
Enable password
|
primary_enable_password
|
Enable secret
|
primary_enable_password
|
Tacacs username
|
primary_username
|
Tacacs password
|
primary_password
|
Tacacs enable username
|
Not used in CSV 3.0
|
Tacacs enable password
|
primary_enable_password
|
Local username
|
primary_username
|
Local password
|
primary_password
|
The order of preference to set these values in Device and Credential Repository is:
•If Tacacs username, password, enable password is set, then these values will be set as primary_username, primary_password and primary_enable_password.
•If Local username and password is set, then the values will be set as primary_username and primary_password.
•If Telnet password, Enable Password, and Enable Secret are set, then the values will be set as primary_password, and primary_enable_password (for both Enable Password, and Enable Secret).
Q. What happens when I delete a device in RME?
A. When you delete a device in RME, all RME data related to that particular device is deleted.
However, the device data is still available in the Device and Credential Repository. You can re-add the devices into RME using RME Devices window (Resource Manager Essentials > Devices > Device Management > RME Devices > Add Devices).
Q. What are the most frequent causes of device import failures?
If after importing a device, it remains in the Pre-deployed state, to troubleshoot, see Diagnosing Pre-deployed Devices under Chapter 3: Adding and Troubleshooting Devices Using Device Management of the User Guide for Resource Manager Essentials 4.1 for more information at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_user_guide_list.html
For more about RME device states, see User Guide for Resource Manager Essentials 4.1:
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_user_guide_list.html
Q. How do I increase the SNMP Timeout and Telnet Timeout values for RME devices?
A. You can edit the RME device attributes using either of these options:
–Set a default device attributes value for all RME devices using Resource Manager Essentials > Admin > System Preferences > RME Device Attributes.
Or
–Set different device attributes value for different RME devices using Resource Manager Essentials > Devices > Device Management > RME Devices > Edit Device Attributes.
See Editing RME Device Attributes section under Chapter 3: Adding and Troubleshooting Devices Using Device Management of the User Guide for Resource Manager Essentials 4.1 for more information at this URL:
http://www.cisco.com/en/US/products/sw/cascara/ps2073/products_user_guide_list.html
Troubleshooting Device Management:
Message ID
|
Error Message
|
Probable Cause
|
Possible Action
|
DM0001
|
Select a Normal device and click this option.
|
You have not selected a Normal device before performing the action
|
Select a Normal device and perform the action.
|
DM0003
|
This software has a RESTRICTED license for managing a limited number of devices. Click here <a href=/cwhp/maas.licenseInfo.do target=_blank> for current licensing information.
Contact your Cisco representative to determine if additional licenses can be purchased for this server.
|
Software has a restricted license to manage a limited number of devices
|
Purchase additional license and perform the action
|
DM0004
|
File name should be between 1 and 255 characters
|
The file name given for Export or Import either has no characters or more than 255 characters
|
Enter a file name between 1 and 255 characters.
|
DM0005
|
Either you have not selected a valid file or the file does not have required permission
|
The file selected for Export or Import does not have the required permissions for Read/Write.
|
Modify the file permissions to get Read/Write permisions.
|
DM0006
|
Selected file name is invalid or blank.
|
You have not selected a file for Export.
|
Select a file and perform the action
|
DM0007
|
Attribute values for devices are invalid. See EssentialsDM.log for more details.
|
You have entered invalid values for some attributes while importing attributes for devices.
|
Enter valid values for the attributes and perform the task.
|
DM0008
|
There are no new devices in DCR. Add new devices to DCR and continue with this flow.
|
All devices in DCR are already managed by RME. There are no new devices to be managed.
|
Add some more devices in DCR and perform the task.
|
DM0009
|
Either you have not entered a valid filename or the file does not exist.
|
The filename that you entered for Import task either does not exist or does not have Read permission.
|
Enter a valid filename and perform the task.
|
Inventory
This section provides the troubleshooting information and FAQs for the Inventory application:
• Inventory FAQs
• Troubleshooting Inventory
Inventory FAQs
• Where can I find out what devices are supported by RME Inventory?
• What are the main methods that I have for performing data collection?
• What does the Inventory Poller do?
• How do I know when a schedule collection was last performed and how long it took?
• How can I see the most recent changes?
• Where can I find out what devices are supported by RME Inventory?
• Why is the Device Serial Number field blank in Inventory?
• How can I make sure a device's serial number is correct, and fix it, if it is wrong?
• Why am I receiving an error message, Write Community = INCORRECT although I have entered the correct Write Community String?
• What do I need to collect from my Solaris or Windows machine when troubleshooting RME Inventory?
• Is there an option to disable/enable Secondary Credentials fallback in RME?
• How can I generate an End of Sale / End of Life Report?
• How can I generate a PSIRT Summary Report?
• How can I change the Cisco.com Fetch interval for End of Sale/End of Life report and PSIRT reports?
• What is the prerequisite to generate the PSIRT/End of Sale End of Life reports?
• Is it possible to generate PSIRT Summary report for all categories of devices?
• Why are there multiple End of Sale/End of Life announcements for a device?
• Is it possible to schedule an Immediate PSIRT Summary or End of Sale/End of Life report job?
Q. Where can I find out what devices are supported by RME Inventory?
A. You can find out what devices are supported by RME Inventory in any one of the following ways:
•Check the Supported Device Table on Cisco.com to see whether or not an upgrade to RME is required.
Or
•Follow this procedure:
a. Select CiscoWorks Common Services > Software Center > Device Update.
The Device Updates dialog box appears.
b. Click Resource Manager Essentials.
The Package Map dialog box appears with the list of supported devices.
Or
•In the RME Device Selector if the device is grayed out, it means that RME does not support the device.
Q. What are the main methods that I have for performing data collection?
A. At the time of RME installation, system jobs are created for both Inventory collection and polling with their own default schedules. A periodic inventory collection job collects inventory data from all managed devices and updates your inventory database.
Similarly, the periodic polling polls devices and updates the inventory database. You can change the schedule of these default, periodic system jobs (Resource Manager Essentials > Admin > Inventory > System Job Schedule).
System Inventory Collection is the heavyweight collection method. It collects all managed devices at a scheduled time and updates the database. You can view Inventory Collection status at Resource Manager Essentials > Devices > Inventory > View Inventory Collection Status.
You can also create and run an Inventory Collection job on selected devices by creating a job (Resource Manager Essentials > Devices > Inventory > Inventory Jobs. In the Inventory Job Browser that appears, click Create. For details on how to create a job, see User Guide for Resource Manager Essentials 4.1).
Q. What does the Inventory Poller do?
A. The Inventory Poller uses a "lightweight" mechanism to determine whether database information is out-of-date. Although the Inventory Poller itself does not perform an actual collection, it determines whether any device information is out-of-date. If information is outdated, the Inventory Poller initiates a full collection on the pertinent devices.
Q. How do I know when a schedule collection was last performed and how long it took?
A. In the Inventory Job Browser (Resource Manager Essentials > Devices > Inventory > Inventory Jobs) click on the Job ID for a specified job. The Job Details dialog box appears. You can view the complete details of the inventory collection here, by browsing through the left navigation pane.
At a high level, you can view Inventory Collection status at Resource Manager Essentials > Devices > Inventory > View Inventory Collection Status.
Q. How can I see the most recent changes?
A. To view inventory changes made in the last 24 hours, use the 24 Hour Inventory Change Report option:
a. Select Resource Manager Essentials > Reports > Report Generator.
The Report Generator dialog box appears.
b. From the first drop-down list, select the Inventory application.
c. From the second drop-down list, select 24 Hour Inventory Change Report.
The Inventory Change Report dialog box appears.
d. Select the devices, using the Device Selector, and leave the Run Type as Immediate.
e. Click Finish.
The 24 Hour Inventory Change Report appears.
To view changes made since the last scheduled collection, use the Change Audit application.
Q. Why is the Device Serial Number field blank in Inventory?
A. The field is blank because inventory could not obtain the information from the device. This is caused by one of these reasons:
–The serial number was not set in the device software when the device was introduced to the network. This should have been done using CLI, as described in the device configuration guide.
–The device does not support MIBs for serial numbers.
In either case, you can set the serial number in the inventory database in this way:
a. Select Resource Manager Essentials > Devices > Device Management > RME Devices > Edit Device Attributes.
The Device Attributes Information dialog box appears.
b. Select the device and enter the correct serial number printed on the device chassis, in the RME ID field and click Modify.
Q. How can I make sure a device's serial number is correct, and fix it, if it is wrong?
The serial number in inventory should always match the number printed on the chassis. If the serial number does not match the number on the chassis, you can change it in this way:
a. Select Resource Manager Essentials > Devices > Device Management > RME Devices > Edit Device Attributes.
The Device Attributes Information dialog box appears.
b. Select the device and enter the correct serial number printed on the device chassis, in the RME ID field and click Modify.
Q. Why am I receiving an error message, Write Community = INCORRECT although I have entered the correct Write Community String?
A. Check whether you have dropped the system group from the view (read-view and write-view). The system group must be available for Read and Write task. In MIB-II, the system group is available as the default.
Q. What do I need to collect from my Solaris or Windows machine when troubleshooting RME Inventory?
A. You can collect troubleshooting information about the status of the server using the Collect Server Information option in Common Services:
a. Login as Administrator.
b. Select Common Services > Server > Admin > Collect Server Information.
The Collect Server Information dialog box appears.
c. Click Create.
A list of report modules and options are displayed.
d. Select the modules you want to include and click OK.
By default, all the modules are selected.
If you collect server information using the Collect Server Information GUI option the data is stored in /opt/CSCOpx/htdocs/collect.
A command line script is also available at /opt/CSCOpx/bin/collect.info. The command script outputs data to STDOUT. For more details on the command script, see the User Guide.
For both Windows and Solaris, you can turn on the debug for ICServer and other processes from the GUI.
You can use the LogLevel Settings option to set the logging levels for RME packages. You can set the log levels for all RME packages, or at a package (application) level.
To set the log levels:
a. Select Resource Manager Essentials > Admin > System Preferences > Loglevel Settings.
The Set Application Logging Levels dialog box appears.
b. Select the application from the drop-down list.
c. Select the appropriate log level from the Logging Level drop-down list.
d. Click Default to apply the default logging levels.
e. After you set the log levels, click Apply.
A message appears, that the log levels have been successfully updated.
Log files are stored at these locations:
On Windows: NMSROOT/log, where NMSROOT is the CiscoWorks installation directory.
On Solaris: /var/adm/CSCOpx/log
You need to collect the following log files:
On Windows:
–IC_Server.log
–EssentialsDM_Server.log
–EssentialsDM.log
–ICServer.log
–ICServer_UI.log
–InvReports.log
Job-specific log files that you need are at these locations:
–NMSROOT\files\rme\jobs\InvPoller
–NMSROOT\files\rme\jobs\Inventory
–NMSROOT\files\rme\jobs\ICServer
On Solaris:
–daemons.log
–EssentialsDM_Server.log
–IC_Server.log
Job-specific log files that you need are at these locations:
–/var/adm/CSCOpx/files/rme/jobs/ICServer
–/var/adm/CSCOpx/files/rme/jobs/InvPoller
–/var/adm/CSCOpx/files/rme/jobs/inventory
You can then e-mail these debug log files along with the Collect Server Info output, to Cisco TAC.
Q. Is there an option to disable/enable Secondary Credentials fallback in RME?
A. You can Enable or Disable fallback to Secondary Credentials by following the steps below:
Step 1 Select Resource Manager Essentials > Admin > System Preferences > RME Secondary Credentials
The RME Secondary Credentials dialog box appears.
Step 2 Do either of the following:
•Check the Fallback to Secondary Credentials checkbox if you want to enable the Secondary Credential fallback.
Or
•Uncheck the Fallback to Secondary Credentials checkbox if you want to disable the Secondary Credential fallback.
Step 3 Click either Apply to apply the option or click Cancel to discard the changes.
Q. How can I generate an End of Sale / End of Life Report?
A. To generate End of Sale / End of Life Report:
Step 1 Select Resource Manager Essentials > Reports > Report Generator.
The RME Reports dialog box appears, in the Report Generator page.
Step 2 Go to the first drop-down list box, and select Inventory.
Step 3 Go to the second drop-down list box, select the End of Sale / End of Life Report.
Step 4 Select the required devices using the Device Selector.
Step 5 Enter the required information to generate the required report.
Q. How can I generate a PSIRT Summary Report?
A. To generate a PSIRT Summary Report:
Step 1 Select Resource Manager Essentials > Reports > Report Generator.
The RME Reports dialog box appears, in the Report Generator page.
Step 2 Go to the first drop-down list box, and select Inventory.
Step 3 Go to the second drop-down list box, select the PSIRT Summary Report.
Step 4 Select the required devices using the Device Selector.
Step 5 Enter the required information to generate the required report.
Q. How can I change the Cisco.com Fetch interval for End of Sale/End of Life report and PSIRT reports?
A. To update the Cisco.com Fetch interval:
Step 1 Go to Resource Manager Essentials > Admin > Inventory > Cisco.com Fetch Interval.
Step 2 Select a frequency at which you require the PSIRT information to be retrieved from Cisco.com.
The duration can be 1 hour or 3 hours or 24 hours or 7 days or 30 days. The default value is 24 hours.
Step 3 Select a frequency at which you require the EoSale/EoL information to be retrieved from Cisco.com.
The duration can be 1 hour or 3 hours or 24 hours or 7 days or 30 days. The default value is 7 days.
Step 4 Click Save to save the changes to the frequencies.
Q. What is the prerequisite to generate the PSIRT/End of Sale End of Life reports?
A. Ensure that Inventory collection for devices has taken place before you generate a PSIRT/End of Sale End of Life report.
Q. Is it possible to generate PSIRT Summary report for all categories of devices?
A. The PSIRT Summary report displays the PSIRTs only for Cisco IOS device categories.
Q. Why are there multiple End of Sale/End of Life announcements for a device?
A. A device consists of many components. Each component is subject to End of Sale/End of Life. So there maybe multiple End of Sale/End of Life announcements for a device.
Q. Is it possible to schedule an Immediate PSIRT Summary or End of Sale/End of Life report job?
A. Yes. You can schedule an Immediate PSIRT Summary or End of Sale/End of Life report job. You can use the Cisco.com Fetch Interval option to configure the interval at which the PSIRT and End of Sale/End of Life announcements are retrieved from Cisco.com.
However, there maybe delays upto 3 hours as the announcements are refreshed in the Cisco servers every 3 hours. So the information that is represented in the Immediate PSIRT Summary report or End of Sale/End of Life report is 3 hours old.
Troubleshooting Inventory
This section provides the troubleshooting information for the Inventory application:
Message ID
|
Error Message
|
Probable Cause
|
Possible Action
|
ICSU0001
|
Could not create database connection.
|
Could not create database connection. RME DB Service may be down.
|
Make sure that RME DB Service is running.
If the problem persists, contact Cisco TAC.
|
ICSU0002
|
Could not create JRM interface object.
|
Could not communicate with JRM. Jrm/CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running.
If the problem persists, contact Cisco TAC.
|
ICSU0003
|
Could not create job.
|
Unknown exception occured.
|
Retry after sometime.
If the problem persists, contact Cisco TAC.
|
ICSU0004
|
Could not display Job Details.
|
Could not communicate with JRM. Jrm/CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running.
If the problem persists, contact Cisco TAC.
|
ICSU0005
|
Could not display Job Details.
|
RME DB Service may be down.
|
Make sure that RME DB Service is running.
If the problem persists, contact Cisco TAC
|
ICSU0006
|
Could not get device support information.
|
Device packages may not be installed.
|
Check whether the device packages have been completely installed.
If the problem persists, contact Cisco TAC.
|
ICSU0007
|
Could not create job.
|
Could not communicate with JRM. Jrm/CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running.
If the problem persists, contact Cisco TAC.
|
ICSU0008
|
Could not create job.
|
RME DB Service may be down.
|
Make sure that RME DB Service is running.
If the problem persists, contact Cisco TAC.
|
ICSU0009
|
Could not display job settings for editing.
|
Could not communicate with JRM. Jrm/CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running.
If the problem persists, contact Cisco TAC.
|
ICSU0010
|
Could not display job settings for editing.
|
RME DB Service may be down.
|
Make sure that RME DB Service is running.
If the problem persists, contact Cisco TAC.
|
ICSU0011
|
Could not display job settings for editing.
|
Unknown error occured.
|
Retry after sometime.
If the problem persists, contact Cisco TAC.
|
ICSU0012
|
Could not edit job.
|
Could not communicate with JRM. Jrm/CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running. If the problem persists, contact Cisco TAC.
|
ICSU0013
|
Could not edit job.
|
RME DB Service may be down.
|
Make sure that RME DB Service is running.
If the problem persists, contact Cisco TAC.
|
ICSU0014
|
Could not edit job.
|
Unknown error occured.
|
Retry after sometime.
If the problem persists, contact Cisco TAC.
|
ICSU0015
|
Could not stop job.
|
Could not communicate with JRM. Jrm/CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running.
If the problem persists, contact Cisco TAC.
|
ICSU0016
|
Could not delete job.
|
RME DB Service may be down.
|
Make sure that RME DB Service is running.
If the problem persists, contact Cisco TAC.
|
ICSU0017
|
Could not display job browser entries.
|
Could not communicate with JRM. Jrm/CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running.
Also make sure that RME DB Service is running. If the problem persists, contact Cisco TAC.
|
ICSU0018
|
Could not filter based on given options.
|
Could not communicate with JRM. Jrm/CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running.
If the problem persists, contact Cisco TAC.
|
ICSU0019
|
Could not filter based on given options.
|
RME DB Service may be down.
|
Make sure that RME DB Service is running.
If the problem persists, contact Cisco TAC.
|
ICSU0020
|
Could not filter based on given options.
|
Could not communicate with JRM or with RME DB Service.
Jrm/CTMJrmServer or RME DB Service may be down.
|
Make sure that Jrm/CTMJrmServer is running. Also make sure that RME DB Service is running.
If the problem persists, contact Cisco TAC.
|
ICSU0021
|
Could not show summary.
|
RME DB Service may be down.
|
Make sure that RME DB Service is running.
If the problem persists, contact Cisco TAC.
|
ICSU0022
|
Could not get the Inventory Last Collected Time.
|
Inventory may not be collected at least once.
|
Try to collect Inventory for this device and try this task after the Inventory Collection.
If the problem persists, contact Cisco TAC.
|
ICSU0023
|
Could not stop job.
|
Could not communicate with JRM. Jrm/CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running.
If the problem persists, contact Cisco TAC.
|
ICSU0024
|
Could not work with Resource Manager Essentials Database.
|
EssentialsDBEngine and/or RMEDbMonitor may be down.
|
Make sure that EssentialsDBEngine/
RMEDbMonitor is running.
Check the log file for more details.
If the problem persists, contact Cisco TAC.
|
ICSU0025
|
Could not work with Job Resource Manager.
|
Jrm and/or CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running.
Check the log file for more details.
If the problem persists, contact Cisco TAC.
|
ICSJ0001
|
Could not create database connection.
|
RME DB Service may be down.
|
Make sure that RME DB Service is running.
If the problem persists, contact Cisco TAC.
|
ICSJ0002
|
Could not run job.
|
Cannot communicate with JRM. Jrm/CTMJrmServer may be down.
|
Make sure that Jrm/CTMJrmServer is running.
If the problem persists, contact Cisco TAC.
|
ICSJ0003
|
Could not run the job.
|
Job ID passed by Jrm is null.
|
Restart Jrm.
If the problem persists, contact Cisco TAC.
|
ICSJ0004
|
Could not run job.
|
Invalid license.
|
Obtain a valid License.
|
ICSJ0005
|
Could not create log file.
|
There is already a file with the same name as the directory to be created.
|
Delete the file with the same name as the directory to be created.
|
ICSJ0006
|
Could not create log file.
|
There is already a file with the same name as the Job ID.
|
Delete the file with the same name as the Job ID.
|
ICSJ0007
|
Could not run the job.
|
Could not create CSTM Server
|
Retry after some time. If the problem persists, restart Daemon Manager.
If the problem persists, contact Cisco TAC.
|
ICSJ0008
|
Request to collect inventory failed.
|
ICServer may be down.
|
Start the ICServer and try again.
If the problem persists, contact Cisco TAC.
|
ICSJ0009
|
Could not send e-mail.
|
SMTP Server may be down
|
Check the SNMP server.
If the problem persists, contact Cisco TAC.
|
ICSJ0010
|
Could not send e-mail.
|
No SMTP Server configured.
|
Configure the SMTP Server and try again.
If the problem persists, contact Cisco TAC.
|
ICSJ0011
|
Could not access DCR Server
|
The user is not authorized to perform the task.
|
Check the role of the user.
|
ICSJ0012
|
Could not establish connection to Daemon Manager.
|
Unknown error while connecting to Daemon Manager.
|
Restart Daemon Manager.
If the problem persists, contact Cisco TAC.
|
ICSJ0013
|
Could not send OK Signal to Daemon Manager.
|
Unknown error while connecting to Daemon Manager.
|
Restart Daemon Manager.
If the problem persists, contact Cisco TAC.
|
ICSJ0014
|
Could not run job.
|
Error while running the job framework
|
Retry after some time.
If the problem persists, contact Cisco TAC.
|
ICSJ0015
|
Could not run the job.
|
CSTM error while publishing the URN.
|
Retry after some time. If the problem persists, restart Daemon Manager.
If the problem persists, contact Cisco TAC.
|
ICSJ0016
|
Exception while running the job.
|
Error occured while receiving the message through the Event Sub- system.
|
Retry after some time. If the problem persists, restart Daemon Manager.
If the problem persists, contact Cisco TAC.
|
RICS0001
|
Cannot successfully collect Inventory Information for the device.
|
Internal Error
|
Try Collecting Inventory for the device again. If the problem persists, in the log directory look for IC_Server.log.
If you search for the Device IP, you will see an exception trace. Contact Cisco TAC with these details.
|
ICSJ0017
|
Cannot run more than 33 concurrent jobs in RME.
|
More than 33 jobs running concurrently in RME.
|
$NMSROOT\CSCOpx\MDC\tomcat\webapps\rme\WEB-INF\lib\ctm_config.txt has MAX_VM_PORTS set by default to 40.
Increase this if you want more than 33 concurrent jobs.
|
Inventory Reports
This section provides the troubleshooting information for the Inventory Reports application:
Message ID
|
Error Message
|
Probable Cause
|
Possible Action
|
INVREP0002
|
You have not updated the template.
|
Either the database may not be running or there may be other database related problems.
|
Check the invreports.log for more details.
Make sure that RMEDbEngine service is running.
|
INVREP0003
|
You have not created the template.
|
Either the database may not be running or there may be other database related problems.
|
Check the invreports.log for more details.
Make sure RMEDbEngine service is running.
|
INVREP0007
|
The Query building task failed.
|
Either there is a problem in the building join conditions or the database may not be running
|
Check the invreports.log for more details.
Verify the generated queries in the log generated in debug mode.
|
INVREP0008
|
Report generation failed.
|
The template may have been deleted from another browser or by another user.
|
Check the Custom templates screen for this template. If it is not there, create it.
|
INVREP0009
|
Report generation failed.
|
One of the UDFs given in the template might have modified or deleted.
|
Check the invreports.log for modified or deleted UDF details and redefine the template.
•If the UDF has been modified, modify the corresponding rule accordingly.
•If UDF has been deleted, delete the corresponding rule from template.
|
INVREP0013
|
Could not create file with the name filename
|
You may not have permissions to create a new file in the current folder.
|
Check the permissions.
Check the invreports.log for more details.
|
INVREP0015
|
Report generation failed.
Could not get device ids from Device and Credential Repository (DCR)
|
The DCR server may not be running
|
Check the log for more details.
Make sure the DCR Server is running.
|
INVREP0016
|
Could not generate CSV File -%1.
|
You may not have permissions to create a new file in the current folder.
|
Check the permissions.
Check the invreports.log for more details.
|
INVREP0017
|
Reports generation partially succeeded.
|
You have attempted to run many commands from a file. Some of the commands have failed.
|
1. Check the invreports.log
2. Execute the same command with the -log option
3. See the corresponding log for more details.
|
INVREP0021
|
Error occured while generating report.
|
Unknown error.
|
Check the invreports.log for more details.
|
INVREP0022
|
Data not available or the database connection failed.
|
Check whether the RME database is running.
|
If the database engine is not running start the engine and try again.
|
INVREP0023
|
Job creation failed.
|
JRM Server may not be running.
|
1. Check the status of JRMServer using the pdshow jrm command
2. Start JRM and try creating the job
|
INVREP0028
|
Could not get database connection.
|
Check whether the RME database is running.
|
If the database engine is not running start the engine and try again.
|
INVREP0025
|
Job creation failed.
|
The JRM Server may not be running.
|
Start JRM and try creating the job
|
INVREP0026
|
Could not get data from the database.
|
Check whether the RME database is running.
|
1. Check the status of JRMServer using the pdshow jrm command
2. Start JRM and try creating the job
If the database engine is not running start the engine and try again.
|
INVREP0027
|
Database connection resource release failed.
|
Check whether the RME database is running.
|
If the database engine is not running start the engine and try again.
|
INVREP0028
|
Could not update the database.
|
Check whether the RME database is running.
|
If the database engine is not running start the engine and try again.
|
INVREP0029
|
Could not find the selected archive in the database.
|
The archive folder could have been deleted.
|
Check whether the archive id folder exists under
NMSROOT/ files\rme\jobs\inventory\reports
\archives
If the folder does not exist:
1. Delete the archive from the UI
2. Create another job to create an archive.
|
INVREP0030
|
Could not get device IDs from DCR.
|
Check whether the DCR Server is running
|
If the DCR Server is not running, restart it.
|
INVREP0031
|
Job not found.
|
The job folder or the job object may not exist under
NMSROOT/ files\rme\jobs\inventory
\reports\jobs.
|
If the folder does not exist, delete the job from the Job Browser.
|
INVREP0032
|
Graph generation failed.
|
You may not have enough disk space.
|
Check the invreports.log for more details.
|
INVREP0033
|
Could not generate Report Print format
|
Unknown error
|
Check the invreports.log for more details.
|
INVREP0034
|
Report Generation failed.
|
Unknown error.
|
Check the invreports.log for more details.
|
INVREP0035
|
Could not access the archive on disk.
|
The archive folder may be deleted.
|
Check whether the archive id folder exists under
NMSROOT/ files\rme\jobs\inventory\reports
\archives
If the folder does not exist:
1. Delete the archive from the UI
2. Create another job to create an archive.
|
INVREP0036
|
Could not retrieve Device Credential data.
|
Check whether the DCR Server is running.
|
Check the invreports.log for more details.
If the DCR Server is not running, restart it.
|
INVREP0037
|
Could not retrieve device type information.
|
Check whether the DCR Server is running.
|
Check the invreports.log for more details.
If the DCR Server is not running, restart it.
|
INVREP0038
|
Could not retrieve device serial number information.
|
Check whether the DCR Server is running.
|
Check the invreports.log for more details.
If the DCR Server is not running, restart it.
|
INVREP0039
|
Could not retrieve user defined fields.
|
Check whether the DCR Server is running.
|
Check the invreports.log for more details.
If the DCR Server is not running, restart it.
|
INVREP0040
|
Database related failure.
|
Check whether the RME database is running.
|
Check the invreports.log for more details.
If the database engine is not running start the engine and try again.
|
CRIN0001
|
Not authorized to delete {0} template(s).
Contact your system administrator for further help.
|
You may not have authorization to perform this task.
|
Contact your system administrator to get permissions.
|
CRIN0002
|
Not authorized to modify template {0}.
Contact your system administrator for further help.
|
You may not have authorization to perform this task.
|
Contact your system administrator to get permissions.
|
CRIN0003
|
Template(s) {0} not found. Check the log for more details.
|
The templates may have been deleted from another browser or by another authorized user at the same time.
|
You must recreate the required templates.
|
CRIN0004
|
One or more of the selected archives are missing.
Check the log for more details.
|
The archives may have been deleted from another browser or by another authorized user at the same time.
|
You must recreate the jobs and get the required archives.
|
CRIN0005
|
Job(s) {0} not found.
Check the log for more details.
|
The jobs may have been deleted from another browser or by another authorized user at the same time.
|
You must recreate the jobs.
|
CRIN0006
|
Could not get templates from {0}. Check the log for more details.
|
Either:
•There is a specific problem with {0} application.
Or
•The templates were deleted from another browser or by another authorized user.
|
Review the specific application log and cri.log. If required, recreate the templates.
|
CRIN0007
|
Could not get archives from {0}. Check the log for more details.
|
Either:
•There is a specific problem with {0} application.
Or
•The archives were deleted from another browser or by another authorized user.
|
Review the specific application application log and cri.log. and recreate the jobs.
|
CRIN0008
|
Could not delete templates {0}. Check the log for more details.
|
The templates may have been deleted from another browser or by another authorized user at the same time.
|
No workaround.
|
CRIN0009
|
Could not delete jobs {0}. Check the log for more details.
|
The jobs may have been deleted from another browser or by another authorized user at the same time.
|
No workaround.
|
CRIN0010
|
Could not delete jobs{0} in running state.
|
This is the expected behavior.
|
You can delete the job after it has completed.
|
CRIN0011
|
Could not delete jobs{0} in scheduled state
|
This is the expected behavior.
|
No workaround.
|
CRIN0012
|
Could not delete one or more of selected archives.
Check the log for more details.
|
The cause will be in the Cri.log.
|
Check the Cri.log for the probable cause and action.
|
CRIN0013
|
Could not get template details for {0}. Check the log for more details.
|
Either:
•There is a specific problem with {0} application.
Or
•The templates were deleted from another browser or by another authorized user.
|
Review the specific log and cri.log. If required, recreate the templates.
|
CRIN0014
|
Operation failed, caused by failure in connecting to JRM. Make sure jrm and/or CTMJrmWrapper services are running.
|
JRM or CTMJrmServer services may not be running.
|
Start JRM and CTMJrmServer.
To do this use the commands, pdstart jrm and pdstart CTMJrmServer
|
CRIN0015
|
Could not apply purge settings. Check the log {0} for more details.
|
The cause will be in the Cri.log.
|
Check the Cri.log for the probable cause and action.
|
CRIN0016
|
Registration with CCR failed or no related entries found in CCR registry.
Check cri.log for more details or contact System Administrator for more help.
|
CCR entry is not done for the required archive setting.
|
Check cri.log and contact System Administrator for further help.
|
CRIN0017
|
Directory {0} not found. Choose valid directory for setting the new archive location.
|
Chosen directory might not exist.
|
Create a new directory at required location and choose the same again.
|
CRIN0018
|
You do not have write permission to {0}.
Select the directory to which you have write permission.
|
No write permission to the selected folder.
|
Select the folder one to which you have write permission or change permissions to the current chosen folder.
|
CRIN0020
|
Changing reports archive location failed.
Check the cri.log for more details.
|
Some other user may be accessing archives or job is running.
|
While changing the archive location, make sure that no job is running or no archives are accessed.
Otherwise this task will not succeed.
|
CRIN0021
|
Moving the report archives to the chosen location failed. Check the cri.log for more details
|
This may be caused by any of the following:
•Some other user may be accessing archives or job is running.
•You may not have write permission to that folder.
•Disk space may not be sufficient.
|
•Check the cri.log for more details.
•Make sure that no archives are accessed or no job is running while moving archives to new location.
•Make sure that the new location has more free space than the old archive directory size.
|
Not Applicable
|
Inventory Report job remains in the running state forever.
|
The default runtime memory is set as follows:
Minimum heap size:
128 MB
Maximum heap size:
512 MB
If the job requires heap size more than 512 MB, then the job will have insufficient memory and will hangs or fail displaying this message:
out of memory
|
1. Cancel the currently running job.
2. Increase minimum and maximum heap in the following file: NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\inventory\reports\datagenerators\IRConfig.properties
to 512 MB and 1024 MB respectively.
3. Schedule another job.
|
Archive Management
This section provides the troubleshooting information and FAQs for the Archive Management application:
• Archive Management FAQs
•
