The command status for this connection map configuration row/record. The value used in a SET will be replaced by a response value in the GET RESPONSE indicating success or failure.

Default Response State used in GET RESPONSE Command ready-for-command (0) initial default status for a row

Map Commands used in SET Command (1..99) update-map (1) Update the map name and/or map description. delete-map (2) Delete all connections from an inactive map. activate-map (7) Make this map the active map. Changing the Map Status from inactive to active for a map will result in the current active map to be changed to inactive. save-map (8) Save the connection data configured for this map. Each time the save-map command is used, the map version and date will be updated. The maps should be saved after changing the system connection configuration to avoid losing those changes in the event of unexpected power loss or system reset. copy-map-to-tagged-maps(9) Copy the connection configuration from this map to all other maps tagged as a destination.

Response States used in GET RESPONSE Command (100..199) command-in-progress (100) map command is still working update-successful (101) map data has been successfully changed delete-successful (102) map connection data has been successfully deleted activate-successful (107) connection map has been successfully activated and previous active map has been de-activated. save-successful (108) connection map has been successfully saved copy-successful (109) connection map has been successfully copied

Map Config Error Codes used in GET RESPONSE Command (200..799) err-general-map-config-error (200) Unknown map configuration error occurred err-invalid-map-command (202) Unrecognized map command-action err-invalid-map-name (203) Configured map name too long err-invalid-map-desc (204) Configured map description too long err-invalid-map-status (205) Unrecognized map status or invalid for current map err-data-locked-by-another-user (450) Another administrative user is making changes to this part of the system via a terminal session. Check Event Log for user name err-snmp-parse-failed (500) Agent could not parse variable err-invalid-snmp-type (501) Variable ASN type does not match Agent defined type err-invalid-snmp-var-size (502) Variable size is too big