4.2 Command log maintenance

The SDS, and then Maintenance, and then Command Log page shows a table containing a history of commands and their responses. This table shows the Timestamp, System ID, CID, and the Text of the commands received from both remote and local connections, including the GUI.

You can view provisioning logs of SDS data being provisioned from various sources. Also, you can export these provisioning logs.

To enable provisioning commands logging (including their responses), you must activate that functionality. Upon feature activation, the command log information is visible on the GUI. Each provisioning command has a response, both of which are stored in the command log information database. The rate of log table export is related to the System ID set in the SDS, and then Configuration , and then Connections page.

When calculating the command log export parameters, consider the following:

• When the storage table is full, new entries begin to overwrite newer entries overwrite the oldest entries.
• The table should be exported frequently enough to avoid information loss, but not so frequently that it becomes a resource drain.
• Consider the rate of command/response pairs when setting the log export parameters.
• It is recommended to export the command log data on a daily basis.

To prevent loss of data, you should export the logs before the data is overwritten by the latest entry in table after the table is filled completely. Based on the system usage, you can calculate when the records reach the throttle limit and logs need to be exported. If the log or logs reaches the throttling limit in one day, you must ensure to export the data on daily basis. Typical rates observed in the field tend to be close to 20 commands/second. Based on that rate, the command log would wrap in close to 3 days.

You can calculate your system setup's throttle limits to help determine when logs should be exported. Based on typical in-field throttle rates, a 2 GB table can store 5 million comments. If the system on average takes x commands per seconds, then the table will be overwritten by the latest entry in:

5000000/x seconds = 83333/x minutes = 1389/x hours = 58/x days (where x is the commands per second)

Every provisioning message exchanged between provisioning systems is written to the command log and is stored for up to seven days.