ssonodestatus
- Organization of this page
Format
- To register or change a node status and then issue an incident:
ssonodestatus -a -n node-name -s {Cri | Maj | Min | War | Nor} [-i message]- To delete node status:
ssonodestatus -d -n node-name
- To output the command usage:
ssonodestatus -h
Function
The ssonodestatus command is used to register, change, or delete a node status in the NNMi map view and to then issue an incident.
You can register only one node status for one node. You cannot register multiple node statuses at the same time.
When you change or delete a node status, the lifecycle status of the relevant issued incident is automatically changed to Closed.
Options
-a
Registers a new node status or changes a registered node status.
-d
Deletes a registered node status.
-n node-name
Specifies a node name of 255 bytes or less.
-s {Cri|Maj|Min|War|Nor}
Specifies the node status to be registered or the new node status to be changed to. The following lists the status types that can be specified and the node statuses as they will be registered in NNMi.
|
Status type |
Node status registered in NNMi |
|
|---|---|---|
|
Node status |
Conclusion |
|
|
Cri |
Critical |
ssonodestatus_Critical |
|
Maj |
Major |
ssonodestatus_Major |
|
Min |
Minor |
ssonodestatus_Minor |
|
War |
Warning |
ssonodestatus_Warning |
|
Nor |
Normal |
ssonodestatus_Normal |
-i message
Issues an appropriate incident according to whether the node status is registered or changed. Any message specified as an argument will be displayed in the NNMi incident view. Messages must be 255 bytes or less.
-h
Outputs the command usage. This option cannot be specified together with other options.
Return values
|
0 |
Normal termination |
|
-1 |
Execution error such as incorrect arguments |
|
-2 |
NNMi linkage is impossible, or an execution error occurred due to an incorrect node name |
|
-3 |
Execution error caused by an attempt to execute this command while it was already running |
Notes
-
Before issuing an incident, set the incident definition file (ssonodestatus.def) in NNMi. For details about how to set the incident definition, see 3.1.1 Flow of SSO installation and setup tasks.
-
You cannot perform operations that manipulate the node status for, or issue incidents to, the event-destination host.
-
Issuing an incident requires about 10 to 20 seconds for processing.
-
Do not execute this command while it is already running.