The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This appendix lists the CLI error messages and CLI validation error messages. It contains the following sections:
•CLI Validation Error Messages
Table A-1 describes CLI error messages.
|
|
|
---|---|---|
|
The .conf file and code are out of synchronization, which should never occur in the field. |
All commands |
|
An out-of-range port number was entered in URI. |
copy, upgrade, |
|
Internal tables are out of synchronization, which should never occur in the field. |
copy, upgrade, |
|
An invalid scheme was entered in URI. |
copy, upgrade, |
The filename <file> is not a valid upgrade file type. |
Attempt to install the wrong file for your platform and version. |
upgrade |
idsPackageMgr: digital signature of the update was not valid |
The signature update or service pack is corrupt. Contact TAC. |
upgrade |
Cannot create a new event-action-rules configuration. "rules0" is currently the only configuration allowed. |
An invalid logical instance name was entered for service event action rules.1 |
service event-action-rules |
Cannot create a new signature-definition configuration. "sig0" is currently the only configuration allowed. |
An invalid logical instance name was entered for service signature definition.2 |
service signature-definition |
Cannot create a new anomaly-detection configuration. "ad0" is currently the only configuration allowed. |
An invalid logical instance name was entered for service anomaly detection.3 |
service anomaly-detection |
|
The administrator is attempting to change the password for a username that does not exist in the system. |
password |
|
The user entered an invalid password while attempting to change the password. |
password |
|
The curUserAccountList.xml file does not contain any entries, which should never occur in the field. |
username |
|
An attempt to create a user that already exists in the system was made. |
username |
|
One or more required applications is not responding to control transactions. |
All commands |
|
— |
copy |
|
The user attempted to copy or erase the backup config file but no backup config file has been generated. |
copy |
|
The .conf files could not be located, which should never occur in the field. |
copy |
|
The URL specified in the destination could not be written. |
copy |
|
The URL specified in the source could not be read. |
copy |
|
The user attempted to copy or erase the packet-file but no packet-file has been captured. |
copy |
|
The user attempted to downgrade a system that has not been upgraded. |
downgrade |
|
The user attempted to display the file-info or the packet-file but no packet-file exists. |
packet |
|
The user was displaying or copying an iplog file that was overwritten. The partial file contents should still be viewable. |
packet |
Another user is currently capturing into the packet-file. Please try again later. |
— |
packet capture |
Another CLI client is currently displaying packets from the interface. |
The user must wait for the other CLI session to terminate display before this will be available. Multiple users may display the command control interface simultaneously. |
packet display |
Log does not exist. |
The user attempted to copy or display an iplog that does not exist. |
copy iplog |
The requested IPLOG is not complete. Please try again after the IPLOG status is 'completed.' |
The user attempted to copy or display an iplog that is not complete. |
copy iplog |
Could not create pipe /usr/cids/idsRoot/tmp/ pipe_cliPacket.<pid>.tmp |
Could not open pipe for sending iplog file. This indicates a space or resource limitation, which should not occur in the field. |
copy iplog |
The log file was overwritten while the copy was in progress. The copied log file may be viewable but is incomplete. |
The iplog was overwritten while it was being copied off the sensor. |
copy iplog |
Could not read license file. |
The license file was copied but cannot be opened. |
copy license-key |
Could not write the temporary license file location used to copy the file off the box. |
Could not open the temporary storage location /usr/cids/idsRoot/tmp/ips.lic. This indicates a space issue, which should not occur in the field. |
copy license-key |
Virtual sensor name does not exist. |
The user attempted to start or stop an iplog on a non-existent virtual sensor. |
iplog |
|
An operator or viewer user attempted to terminate a CLI session belonging to another user. |
clear line |
|
The user attempted to cancel a CLI session that does not exist. |
clear line |
|
Operator or viewer user attempted to log in when the maximum number of CLI sessions were already open. |
initial login |
|
Administrator user attempted to log in when the maximum number of CLI sessions were already open. |
initial login |
|
The CLI cannot contact the applications on the sensor to retrieve start-up information. This is a fatal error that should never happen. The user has to log in to the service account and manually reboot the sensor. |
initial login |
The instance cannot be removed. Instance assigned to virtual sensor name. |
The user attempted to remove a configuration instance that is currently assigned to a virtual sensor. Use the default service command to reset the configuration setting to default. |
no service component instance |
Insufficient disk space to complete request. |
Not enough disk space is available to create a new instance of a configuration file. |
copy instance |
1 This error only occurs on platforms that do not support virtual policies. 2 This error only occurs on platforms that do not support virtual policies. 3 This error only occurs on platforms that do not support virtual policies. |
Table A-2 describes the validation error messages.