A-101
User Guide for Resource Manager Essentials 4.1
OL-11714-01
Appendix A RME Troubleshooting Tips and FAQs
cwcli config
cwcli config
This section provides the troubleshooting information for the cwcli config commands:
BTKT0020 Device(s) are not
supported by Cisco.com.
For a device to get the details of
its bug from the Cisco.com
database, the device must have
been added to this database. In
this case it has not been added.
Check bugtoolkit.log for more details.
BTKT0021 Cannot retrieve the URL
limits or the Thread
limits.
• Either:
The Bugtool.properties file does
not exist
Or
• The Bugtool.properties file
exists but with wrong url
and thread limits or no url or
thread limits.
Check whether the file
Bugtool.properties exists or if you have
entered the values correctly or ensure
that the url limits and thread limits are
given in the Bugtool.properties file and
the file exists.
BTKT0022 Devices are not
supported by Cisco.com
or Cisco.com URL
Connection Timeout. Try again later.
Message ID Error Message Probable Cause Possible Action
Message-ID Error Message Probable Cause Possible Action
CCLI0001 Could not get any
device(s) to work on.
This problem occured because of
any of the following:
• Specified device(s) is not
managed by RME.
• You have not used the correct
Device Display name
• DCR server is down
Do any of the following, depending on what
caused the problem:
• Specify valid devices that are managed
by RME
• Use a valid Device Display name.
• Use the pdshow command to verify
whether the DCR server is running.
CCLI0002 The job could not be
created since no device is
available.
This problem occured because of
any of the following:
• You have entered invalid
arguments for the command.
• You have entered devices
that are not managed by
RME.
• CTMJrmServer and jrm are
down.
• ConfigMgmtServer process
is down.
Do any of the following, depending on what
caused the problem:
• Enter valid arguments.
• Verify that the devices you have entered
are managed by RME.
• Use the pdshow command to verify
whether the CTMJrm server and jrm are
running.
• The ConfigMgmtServer process should
be up for the configuration Download
and Fetch options.