About md command execution failures

msh errors are largely divided into API command execution failures and errors within msh commands.

Errors of API

API errors that can occur as the result of values input from a user command and their causes are as follows.

Status code	Main factors
400	When you use the monitor, sagroup command, etc., and attempt to add an element that exceeds the maximum allowed
403	access_key or access_key_secret is not set properly
404	When you set a code or ID that does not exist or that is not manageable

Example of status code 400

msh(tsa********)> show monitor
---
- Monitor_0:
    MonitorGroup ID:
    MonitorGroup Name:
    Member: 1
- Monitor_1:
    MonitorGroup ID: 1
    MonitorGroup Name: Monitor
    Member: 0
- Monitor_2:
    MonitorGroup ID: 3
    MonitorGroup Name: Monitor
    Member: 0
- Monitor_3:
    MonitorGroup ID: 5
    MonitorGroup Name: Monitor
    Member: 0
- Monitor_4:
    MonitorGroup ID: 7
    MonitorGroup Name: Monitor
    Member: 1
- Monitor_5:
    MonitorGroup ID: 9
    MonitorGroup Name: Monitor
    Member: 0
msh(tsa********)> add monitor Monitor
API response status code is 400 (Bad Request).
msh(tsa********)>

Example of status code 403

msh(tsa********)> set env access_key invalid_key access_key_secret invalid_secret
proxy_addr : proxy.sacm.jp
proxy_port : 8080
domain : demo.sacm.jp
path : /public-api/v1
access_key : invalid_key
access_key_secret : invalid_secret
user_code : tsa********
ssl_verify : false
msh(tsa********)> show sa
API response status code is 403 (Forbidden).
msh(tsa********)>

Example of status code 404

msh(tsa********)> show monitor
---
- Monitor_0:
    MonitorGroup ID:
    MonitorGroup Name:
    Member: 1
- Monitor_1:
    MonitorGroup ID: 1
    MonitorGroup Name: Monitor
    Member: 0
- Monitor_2:
    MonitorGroup ID: 3
    MonitorGroup Name: Monitor
    Member: 0
- Monitor_3:
    MonitorGroup ID: 5
    MonitorGroup Name: Monitor
    Member: 0
- Monitor_4:
    MonitorGroup ID: 7
    MonitorGroup Name: Monitor
    Member: 1
- Monitor_5:
    MonitorGroup ID: 9
    MonitorGroup Name: Monitor
    Member: 0
msh(tsa********)> show monitor 0
API response status code is 404 (Not Found).
msh(tsa********)>

msh errors

Of errors that occur in msh commands, the following are common elements of many of the commands.

Error	Main factors
<command> is unknown command.	Unknown command was input
<command>: required parameter missing.	Required parameter was not input
<operaton>: failed.	Task is registered in the SACM but the target service adaptor is down

Example of execution when unknown command is input

msh(tsa********)> ping6 tsw00000000 ::1
ping6 tsw00000000 ::1 is unknown command.
msh(tsa********)>

Example of execution when required parameter is not input

msh(tsa********)> ping ::1
ping : required parameter missing.
msh(tsa********)>

Example of execution when attempt is made to execute task on a down service adaptor

msh(tsa********)> ping tsw11111111 ::1
.
ping: failed.
msh(tsa********)>