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:
Table C-1 describes CLI error messages.
|
|
|
---|---|---|
The .conf file and code are out of synchronization, which should never occur in the field. |
||
Internal tables are out of synchronization, which should never occur in the field. |
||
Attempt to install the wrong file for your platform and version. |
||
|
The signature update or service pack is corrupt. Contact TAC. |
|
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 |
|
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 |
|
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 |
|
The administrator is attempting to change the password for a username that does not exist in the system. |
||
The user entered an invalid password while attempting to change the password. |
||
The curUserAccountList.xml file does not contain any entries, which should never occur in the field. |
||
An attempt to create a user that already exists in the system was made. |
||
|
One or more required applications is not responding to control transactions. |
|
The user attempted to copy or erase the backup config file but no backup config file has been generated. |
||
|
The .conf files could not be located, which should never occur in the field. |
|
The user attempted to copy or erase the packet-file but no packet-file has been captured. |
||
The user attempted to downgrade a system that has not been upgraded. |
||
The user attempted to display the file-info or the packet-file but no packet-file exists. |
||
Another user is currently capturing into the packet-file. Please try again later. |
||
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. |
|
The user attempted to copy or display an iplog that does not exist. |
||
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. |
|
|
The user was displaying or copying an iplog file that was overwritten. The partial file contents should still be viewable. |
|
Error: Iplog transfer failed. The copied log file is incomplete. |
Iplog transfer has failed. There may or may not be any partial copied file at remote server. |
|
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. |
|
Error: The log file might have been 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. |
|
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. |
|
The user attempted to start or stop an iplog on a non-existent virtual sensor. |
||
|
An operator or viewer user attempted to terminate a CLI session belonging to another user. |
|
|
The user attempted to cancel a CLI session that does not exist. |
|
|
Operator or viewer user attempted to log in when the maximum number of CLI sessions were already open. |
|
|
Administrator user attempted to log in when the maximum number of CLI sessions were already open. |
|
|
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. |
|
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. |
|
Not enough disk space is available to create a new instance of a configuration file. |
Table C-2 describes the validation error messages.