In SACM, the configuration of the service adaptor is stored and managed on the server side. Configurations in the SACM specify the data that regulates service adaptor operations. In general, this is the CLI-formatted configuration of the router, the setup information of the server’s various programs, or general binary data, etc.
It is typical for this content to vary depending on the equipment being set and may include, for example, IP address, host name, filter information, etc. SACM creates and saves a separate configuration for each piece of equipment (each SA code). When the equipment boots, the Pull operation reads the configuration assigned to the device and then runs operations.
Because the SACM management feature is device independent, SACM conducts no analysis whatsoever regarding configuration content. As such, the SACM system cannot be used to ascertain whether or not a created configuration is correct. Please note that even if configuration content is incorrect and device boot fails, SACM will not detect such problems in advance.
Depending on conditions, configurations managed through SACM are categorized into the following types.
Config type |
Description |
|---|---|
Working config |
Configuration saved on the server. Reflected on the service adaptor by running “Reflect Configuration at Startup.” |
Startup config |
The configuration created when “Reflect Configuration at Startup” is run for the Working config. Configuration reflected at service adaptor startup. |
Running config |
Configuration that has been reflected in the service adaptor and is actually running. Created when the reflect config is reflected in the service adaptor and when “reflect immediately” is run on the Working config. |
Service adapter configurations are managed by editing or reflecting configurations from the Control Panel.
SACM management does not involve using ssh/telnet, etc., to login to a service adapter and directly update the configuration. This is because updating the configuration directly on the service adaptor would result in inconsistencies between the service adapter configuration and the configuration saved on the server, and SACM would be unable to determine the status of the configuration currently running.
As such, some types of service adaptors restrict the ability to login directly and edit the configuration while SACM is running.
Two configuration formats are used in SACM: text format and binary format.
Text format
Configurations that can be handled in text format. SACM allows you to edit and browse configurations directly. This is the format typically used for router equipment, etc.
Binary format
All configs that cannot be handled in text format are formatted as binary configurations. For these configurations, SACM cannot directly edit or browse config content, and only downloading and uploading are allowed.
At present, the only compatible text format is US-ASCII text. If the config contains Japanese characters or other multi-byte character strings, it must be handled as a binary config.
Also, along with module definitions the config type is normally predetermined by the hardware vendor and cannot be updated by the user.
Normally, SACM does not detect whether or not config content is accurate. However, a config validation function is provided for certain devices, allowing you check whether or not the syntax is correct. A list of device currently compatible with the validation function is as follows.
device name |
Validation content |
|---|---|
SEIL/X1 |
|
SEIL/X2 |
|
SEIL/B1 |
|
SA-W1 |
|