Cisco Intrusion Prevention System Sensor CLI Configuration Guide for IPS 7.1
CLI Error Messages
Downloads: This chapterpdf (PDF - 111.0KB) The complete bookPDF (PDF - 9.85MB) | Feedback

CLI Error Messages

Table Of Contents

CLI Error Messages

CLI Error Messages

CLI Validation Error Messages


CLI Error Messages


This appendix lists the CLI error messages and CLI validation error messages. It contains the following sections:

CLI Error Messages

CLI Validation Error Messages

CLI Error Messages

Table D-1 describes CLI error messages.

Table D-1 CLI Error Messages 

Error Message
Reason
Command
getVirtualSensorStatistics : 
Analysis Engine is busy

Analysis Engine is busy because the virtual sensor has not finished initializing.

show statistics virtual-sensor

getVirtualSensorStatistics : Analysis Engine is busy rebuilding regex tables. This may take a while.

Analysis Engine is busy building cache files immediately after the sensor has been imaged.

show statistics virtual-sensor

editConfigDeltaSignatureDefinition : Analysis Engine is busy rebuilding regex tables. This may take a while.

Analysis Engine is busy building cache files immediately after the sensor has been imaged.

service signature-definition

Invalid command received.

The .conf file and code are out of synchronization, which should never occur in the field.

All commands

Invalid port number was entered.

An out-of-range port number was entered in URI.

copy, upgrade,
show tech-support

Invalid scheme was entered.

Internal tables are out of synchronization, which should never occur in the field.

copy, upgrade,
show tech-support

Unknown scheme was entered.

An invalid scheme was entered in URI.

copy, upgrade,
show tech-support

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

User does not exist.

The Administrator is attempting to change the password for a username that does not exist in the system.

password

Incorrect password for user account.

The user entered an invalid password while attempting to change the password.

password

Empty user list.

The curUserAccountList.xml file does not contain any entries, which should never occur in the field.

username

User already exists.

An attempt to create a user that already exists in the system was made.

username

Cannot communicate with system processes. Please contact your system administrator.

One or more required applications is not responding to control transactions.

All commands

Source and Destination are the same.

copy

Backup config was missing.

The user attempted to copy or erase the backup config file but no backup config file has been generated.

copy
erase

Could not load CLI configuration files, can not complete request.

The .conf files could not be located, which should never occur in the field.

copy

Error writing to <URL>.

The URL specified in the destination could not be written.

copy

Error reading from <URL>.

The URL specified in the source could not be read.

copy

Packet-file does not exist.

The user attempted to copy or erase the packet-file but no packet-file has been captured.

copy
erase

No downgrade available.

The user attempted to downgrade a system that has not been upgraded.

downgrade

No packet-file available.

The user attempted to display the file-info or the packet-file but no packet-file exists.

packet

Log file exists but an error occurred during read.

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
packet display 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

You do not have permission to terminate the requested CLI session.

An operator or viewer user attempted to terminate a CLI session belonging to another user.

clear line

Invalid CLI ID specified, use the 'show users all' command to view the valid CLI session IDs.

The user attempted to cancel a CLI session that does not exist.

clear line

The maximum allowed CLI sessions are currently open, please try again later.

Operator or viewer user attempted to log in when the maximum number of CLI sessions were already open.

initial login

The maximum allowed CLI sessions are currently open, would you like to terminate one of the open sessions?

Administrator user attempted to log in when the maximum number of CLI sessions were already open.

initial login

Can not communicate with system processes. Please contact your system administrator.

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
service
component 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.


CLI Validation Error Messages

Table D-2 describes the validation error messages.

Table D-2 Validation Error Messages 

Error Message
Reason/Location

Interface `name' has not been subdivided.

The physical interface or inline interface name subinterface type is none (service interface submode).

Interface `name' subinterface `num' does not exist.

The physical interface name has been subdivided into inline VLAN pairs, but the specified subinterface number does not exist (service interface submode).

Interface `name' is the command-control interface.

The physical interface name is the command and control interface (service interface submode).

Interface `name' has been subdivided.

The physical interface name subinterface type is inline VLAN pair or VLAN group. Or the inline interface name subinterface type is VLAN group (service interface submode).

Interface `name' is assigned to 
inline-interfaces `inlinename.'

The physical interface name is assigned to an inline interface entry's interface1 or interface2 (service interface submode).

Vlan `vlannum' is assigned to subinterface `subnum.'

The VLAN vlannum is already assigned to a different subinterface subnum entry's vlan1 or vlan2 (service interface submode).

Vlan range `vlanrange' overlaps with vlans assigned to subinterface `subnum.'

The VLAN range vlanrange contains values that are already used in a different subinterface subnum entry's vlans range (service interface submode).

Unassigned vlans already assigned to subinterface `subnum.'

Unassigned VLANs have already been selected in a different subinterface subnum entry.

Inline-interface `inlinename' does not exist.

The inline interface inlinename does not exist (service interface submode).

The default-vlans for the selected interfaces do not match. interface1, `name' default-vlan is `vlannum,' interface2, `name' default-vlan is `vlannum.'

The user is trying to change the subinterface type of an inline interface to VLAN group, but the default VLANs for the two interfaces assigned to the inline interface do not match (service interface submode).

interface1 and interface2 must be set before the logical interface can be divided into subinterfaces.

The user is trying to change the subinterface type of an inline interface to VLAN group, but has not set both interface1 and interface2 (service interface submode).

Interface `name' has not been subdivided into inline-vlan-pairs.

The physical interface name subinterface type is not inline VLAN pair (service interface submode).

Interface already assigned to virtual sensor `vsname.'

The interface and optional sub-interface being added to the virtual sensor entry physical interface set has already been assigned to another virtual sensor entry.

The instance cannot be removed. Instance assigned to virtual sensor `vsname.'

The user is trying to remove a signature definition, event action rules, or anomaly detection configuration file that is currently in use by virtual sensor vsname.