Error Messages

Contents
casp1032
Contents
This section describes the most common error messages that the CLI throws in response of an invalid or wrongly executed command. Each error message includes reason and action to be performed.
ack alarm <alarm_id> invalid alarm id
Reason:
The alarm ID that you entered is invalid.
Action:
Enter the ack alarm command again, using a valid alarm_id.
ack alarm <landscape_handle> invalid landscape handle
Reason:
The landscape handle that you entered for the alarm is invalid.
Action:
Enter the ack alarm command again, using a valid landscape_handle.
command failed to connect with VnmShd, please run connect first
Reason:
You attempted to run other commands before running the connect command.
Action:
Begin a CLI session with the connect command.
connect already connected to <hostname> since <date/time>
Reason:
The attempt to connect is unnecessary. You are already connected to a
SpectroSERVER
host.
Action:
None.
connect cannot open resource file <pathname>/.vnmshrc
Reason:
The connect command cannot find the CLI resource file .vnmshrc.
Action:
The .vnmshrc resource file must be in the same directory as the connect command itself.
connect can only connect to
SpectroSERVER
s in <hostname> landscape map - other user(s) already connected
Reason:
The connect command has already been used to connect to a particular
SpectroSERVER
. You can connect only to a
SpectroSERVER
that is in the landscape map of the original
SpectroSERVER
.
Action:
None
connect ERROR No such
CA Spectrum
user as <username>
Reason:
The first user of the connect command is not defined as a
CA Spectrum
user.
Action:
Reconnect to the
SpectroSERVER
as a
CA Spectrum
user.
connect <hostname> not responding or not permitting access
Reason:
The connect command cannot connect to
SpectroSERVER
because the hostname is incorrect, the
SpectroSERVER
is not running, or the user has no user model.
Action:
Verify that the hostname is correct, that
SpectroSERVER
is running, and that the user has a user model.
connect <landscape_handle> invalid landscape handle
Reason:
The landscape_handle specified by the user is not valid for the specified hostname, or the handle cannot be accessed by your VNM.
Action:
Verify that the landscape_handle is valid for the specified hostname, and verify that the handle can be accessed by your VNM.
connect incompatible
SpectroSERVER
<version>
Reason:
The user is attempting to connect to a
SpectroSERVER
host whose version is incompatible with the CLI version.
Action:
Update the version of CLI that you are using.
connect invalid <value> for CLISESSID
Reason:
The connect command is used within a cron script or the windowing system returns 0 for ttyslot and the environment variable CLISESSID is set to a non-numeric value.
Action:
Use the connect command outside of a cron script and set CLISESSID to a numeric value.
connect variable <CLISESSID> not set
Reason:
You have attempted to use the connect command within a cron script without first setting the CLISESSID environment variable.
Action:
When using connect within a cron script, set the environment variable CLISESSID.
create user not permitted to create alarm
Reason:
You are not permitted to create an alarm.
Action:
Verify your user permissions.
create user not permitted to create association
Reason:
You are not permitted to create an association.
Action:
Verify your user permissions.
create user not permitted to create event
Reason:
You are not permitted to create an event.
Action:
Verify your user permissions.
create user not permitted to create model
Reason:
You are not permitted to create a model.
Action:
Verify your user permissions.
create alarm <probable_cause_id> invalid alarm cause
Reason:
The create alarm command was entered with an invalid probable_cause_id.
Action:
Re-enter the create alarm command with a valid probable_cause_id.
create alarm <alarm_severity> invalid alarm severity
Reason:
The create alarm command was entered with an invalid alarm_severity.
Action:
Re-enter the create alarm command with a valid alarm_severity.
create alarm <model_handle> invalid model handle
Reason:
The create alarm command was entered with an invalid model_handle.
Action:
Re-enter the create alarm command with a valid model_handle.
create association <left_model_handle> invalid model handle
Reason:
The create association command was entered with an invalid left_model_handle.
Action:
Re-enter the create association command with a valid left_model_handle.
create association models belong to different landscapes
Reason:
The create association command was entered with a left_model_handle and a right_model_handle in different landscapes.
Action:
Use the same landscape for both handles.
create association rel=<relation> invalid relation
Reason:
The create association command was entered with an invalid relation.
Action:
Re-enter the create association command with a valid relation.
create association <right_model_handle> invalid model handle
Reason:
The create association command was entered with an invalid right_model_handle.
Action:
Re-enter the create association command with a valid right_model_handle.
create event <event_type> invalid event type
Reason:
The create event command was entered with an invalid event_type.
Action:
Re-enter the create event command with a valid event_type.
create event <landscape_handle> unknown landscape
Reason:
The create event command was entered with an invalid landscape_handle.
Action:
Re-enter the create event command with a valid landscape_handle.
create event <model_handle> invalid model handle
Reason:
The create event command was entered with an invalid model_handle.
Action:
Re-enter the create event command with a valid model_handle.
create model <attribute_id> invalid attribute id
Reason:
No model is created because the create model command was entered with an invalid attribute_id.
Action:
Re-enter the create model command with a valid attribute_id.
create model DCM device unreachable
Reason:
No model was created because the create model command was entered with an invalid ip_address. The DCM (Device Communication Manager) issues this error message.
Action:
Re-enter the create model command with a valid ip_address.
create model Device limit exceeded
Reason:
No model was created because the Branch Manager
SpectroSERVER
(50 device model limit) or the Site Manager
SpectroSERVER
(250 device model limit) contains the maximum number of device models it can contain.
Action:
Verify that the number of device models on the
SpectroSERVER
have not met the prescribed limits. If they have, you may need to delete some and then re-enter the create model command.
create model <landscape_handle> invalid landscape handle
Reason:
No model was created because the create model command was entered with an invalid landscape_handle.
Action:
Re-enter the create model command with a valid landscape_handle.
create model <model_type_handle> invalid model type handle
Reason:
No model is created because the create model command was entered with an invalid model_type_handle.
Action:
Re-enter the create model command with a valid model_type_handle.
create model <value> invalid value
Reason:
No model is created because the create model command was entered with an invalid value.
Action:
Re-enter the create model command with a valid value.
create model <value> No community name
Reason:
The community name provided in the create request was incorrect.
Action:
Re-enter the create command with a valid community name.
current <model_handle> invalid model handle current model is <current_model_handle>
Reason:
An invalid model_handle was specified so the current model and the current landscape are unchanged.
Action:
Re-enter a valid model_handle if you want to modify the current model and current landscape.
current <landscape_handle> invalid landscape handle current landscape is <current_landscape_handle>
Reason:
Since an invalid landscape_handle was specified, the current model and the current landscape are unchanged.
Action:
Re-enter a valid landscape_handle if you want to modify the current model and current landscape.
current <landscape_handle> not responding or not permitting access current model is <current_model_handle>
Reason:
A landscape_handle was specified and the OneClick for the landscape was down or the user did not have a user model on that landscape.
Action:
Verify that the OneClick for the landscape in question is running; verify that you have a user model on the landscape in question; and then re-enter the landscape_handle.
current <landscape_handle> not responding or not permitting access current landscape is <current_landscape_handle>
Reason:
A model_handle was specified and the
SpectroSERVER
for the landscape containing that model was down or the user did not have a user model on that landscape.
Action:
Verify that the
SpectroSERVER
for the landscape in question is running; verify that you have a user model on the landscape in question; and then re-enter the model_handle.
destroy user not permitted to destroy alarm
Reason:
You are not permitted to destroy an alarm.
Action:
Verify your user permissions.
destroy user not permitted to destroy association
Reason:
You are not permitted to destroy an association.
Action:
Verify your user permissions.
destroy user not permitted to destroy model
Reason:
You are not permitted to destroy a model.
Action:
Verify your user permissions.
destroy alarm aid=<alarm_id> invalid alarm id
Reason:
The destroy alarm command was entered with an invalid alarm_id.
Action:
Re-enter the destroy alarm command with a valid alarm_id.
destroy alarm <landscape_handle> invalid landscape handle
Reason:
The destroy alarm command was entered with an invalid landscape_handle.
Action:
Re-enter the destroy alarm command with a valid landscape_handle.
destroy association rel=<relation> invalid relation
Reason:
The destroy association command was entered with an invalid relation.
Action:
Re-enter the destroy association command with a valid relation.
destroy association <left_model_handle> invalid model handle
Reason:
The destroy association command was entered with an invalid left_model_handle.
Action:
Re-enter the destroy association command with a valid left_model_handle.
destroy association <right_model_handle> invalid model handle
Reason:
The destroy association command was entered with an invalid right_model_handle.
Action:
Re-enter the destroy association command with a valid right_model_handle.
destroy association association does not exist between given models
Reason:
An attempt was made to destroy an association between two models that do not exist.
Action:
Verify the existence of the two models belonging to the association you are attempting to destroy.
destroy association models belong to different landscapes
Reason:
The destroy association command was entered with a left_model_handle and a right_model_handle in different landscapes.
Action:
Re-enter the destroy association command using a left_model_handle and a right_model_handle from the same landscape.
destroy model <model_handle> invalid model handle
Reason:
The destroy model command was entered with an invalid model_handle.
Action:
Re-enter destroy model command with a valid model_handle.
disconnect failed
Reason:
The disconnect command failed.
Action:
Re-try the disconnect command.
disconnect failed to connect with VnmShd, please run connect first
Reason:
An attempt was made to run disconnect when the CLI Local Server was not running.
Action:
None. You are already disconnected.
disconnect not connected
Reason:
The disconnect command failed since the user was not connected to the
SpectroSERVER
.
Action:
None. You are already disconnected.
jump <text_string> text string not defined
jump:<text_string>: text string not defined
where text_string1, text_string2... are the currently defined text strings.
Reason:
The jump command was entered with an undefined text_string.
Action:
Re-enter the jump command using any of the defined text strings.
<pathname>/VnmShd not found
<pathname>/VnmShd: not found
connect: failed where pathname represents the path to the directory in which CLI attempted to execute VnmShd.
Reason:
The connect command cannot find the CLI Local Server.
Action:
Make sure VnmShd and connect are in the same directory and then re-enter the connect command.
Please connect first
Reason:
After connect executed, you ran disconnect or stopShd and then attempted to run another command.
Action:
Reissue the connect command first.
seek <attribute_id> invalid attribute id
Reason:
The seek command was entered with an invalid attribute_id.
Action:
Re-enter the seek command with a valid attribute_id.
seek <error> attribute not keyed
Reason:
The seek command was entered with the attribute_id of an attribute that was not keyed.
Action:
Re-enter the seek command with an attribute_id of a keyed attribute.
seek <value> invalid value
Reason:
The seek command was entered with an invalid value.
Action:
Re-enter the seek command with a valid value.
show attributes <attribute_id> non list attribute
Reason:
The show attributes command was entered with an instance_id for a non list attribute_id.
Action:
Re-enter the show attributes command with an instance_id for a list attribute_id.
show attributes <attribute_id> invalid attribute id
Reason:
The show attributes command was entered with an invalid attribute_id.
Action:
Re-enter the show attributes command with a valid attribute_id.
show attributes <instance_id> invalid instance id
Reason:
The show attributes command was entered with an invalid instance_id. An instance_id is invalid if it does not consist of a sequence of non-negative integers or if it does not exist for the specified attribute.
Action:
Re-enter the show attributes command with a valid instance_id.
show attributes <model_type_handle> invalid model type handle
Reason:
The show attributes command was entered with an invalid model_type_handle.
Action:
Re-enter the show attributes command with a valid model_type_handle.
show <landscape_handle> invalid landscape handle
Reason:
A show command that uses an optional landscape_handle was entered with an invalid landscape_handle.
Action:
Re-enter the show command with a valid landscape_handle.
show <model_handle> invalid model handle
Reason:
A show command that uses an optional model_handle was entered with an invalid model_handle.
Action:
Re-enter the show command with a valid model_handle.
show no current model defined
Reason:
A show associations command that uses an optional model_handle was entered but no model_handle was specified and no current model was defined.
Action:
Re-enter the show associations command, including both a model_handle and current model.
show alarms no cause information available
Reason:
The show alarms command was used with the -x option, and the
CA Spectrum
alarm files containing the probable cause text messages are not available.
Action:
For the show alarms command to work with the -x option, which displays probable cause messages for alarms and expanded event messages, OneClick must be installed on the local server, and the environment variable SPECROOT must be set to the path of the Support root directory (SG-Support). For example, if the SG-Support files are in the following directory:
/usr/spectrum/SG-Support, set SPECROOT to /usr/spectrum.
show children <relation> invalid relation
Reason:
The show children command was entered with an invalid relation.
Action:
Re-enter the show children command with a valid relation.
show events no event format information available
Reason:
The show events command was entered with the -x option, and the
CA Spectrum
event files containing the event format text messages are not available.
Action:
For the show events command to work with the -x option, which displays probable cause messages for alarms and expanded event messages, OneClick must be installed on the local server, and the environment variable SPECROOT must be set to the path of the Support root directory (SG-Support). For example, if the SG-Support files are in the following directory:
/usr/spectrum/SG-Support, set SPECROOT to /usr/spectrum
show parents <relation> invalid relation
Reason:
The show parents command was entered with an invalid relation.
Action:
Re-enter the show parents command with a valid relation.
show rules <relation> invalid relation
Reason:
The show rules command was entered with an invalid relation.
Action:
Re-enter the show rules command with a valid relation.
show inheritance <model_type_handle> invalid model type handle
Reason:
The show inheritance command was entered with an invalid model_type_handle.
Action:
Re-enter the show inheritance command with a valid model_type_handle.
stopShd VnmShd not running
Reason:
An attempt was made to run stopShd when the CLI Local Server was not running.
Action:
Start the CLI Local Server.
stopShd failed
Reason:
The stopShd command failed.
Action:
Try connecting again, and then execute stopShd. If this does not work, kill the VnmShd process manually.
update <attribute_id> Attribute not writable
Reason:
No update occurred because an attempt was made to update model attributes that are non-writable.
Action:
Verify that the model attributes you want to update are writable and then re-enter the update command.
update <attribute_id> invalid attribute id
Reason:
No update occurred because the update command was entered with an invalid attribute_id.
Action:
Re-enter the update command with a valid attribute_id.
update <attribute_id> non shared attribute
Reason:
The update command was used for a model type and an attribute_id of a non-shared attribute was entered.
Action:
Re-enter the update command for the model type, this time using an attribute_id for a shared attribute.
update <instance_id> invalid instance id
Reason:
No update occurred because the update command was entered with an invalid instance_id.
Action:
Re-enter the update command with a valid instance_id.
update <landscape_handle> invalid landscape handle
Reason:
No update occurred because the update command was entered with an invalid landscape_handle.
Action:
Re-enter the update command with a valid landscape_handle.
update <model_handle> invalid model handle
Reason:
No update occurred since the update command was entered with an invalid model_handle.
Action:
Re-enter the update command with a valid model_handle.
update <model_type_handle> invalid model type handle
Reason:
No update occurred because the update command was entered with an invalid model_type_handle.
Action:
Re-enter the update command with a valid model_type_handle.
update <value> invalid value
Reason:
No update occurred because the update command was entered with an invalid value or values.
Action:
Re-enter the update command with valid values.
update <action_code> invalid action code
Reason:
No update occurred because the update command was entered with an invalid action_code.
Action:
Re-enter the update with a valid action_code.
VnmShd Error Failed to connect to
SpectroSERVER
Reason:
The CLI Local Server failed to connect to the
SpectroSERVER
.
Action:
Verify that the
SpectroSERVER
is running.
VnmShd Error Lost connection with
SpectroSERVER
Reason:
The CLI Local Server, detecting that the
SpectroSERVER
to which it was connected has terminated, terminates.
Action:
Restart the
SpectroSERVER
and then run the CLI Local Server.