Lantronix Local Managers can be managed by a Lantronix Control Center, a centralized web-based interface for managing multiple systems in an enterprise. Once integrated, the Lantronix Control Center becomes the vehicle for scheduling tasks across the enterprise, archiving data, events and device information, and integrating with other enterprise network management systems.
Local Managers communicate with the Lantronix Control Center server via a "heartbeat" function. The interval is configurable; the default is 30 seconds.
In LMS 6.3, support for heartbeat certificates was added for non-FIPS systems. This allows users to replace the default certificate with a custom version. If the default certificate is changed prior to bringing a factory-default Local Manager online, you may be prompted to accept the new certificate when enabling management.
Do you trust this certificate? (y/n) [n]: y Do you want to commit these changes? (y/n): y
For more information, see Heartbeat Certificates.
To configure the Local Manager to communicate with a Lantronix Control Center, use the interactive config system management command.
[admin@LantronixLM]# config system management --- Existing Values --- Use Management Server: auto Hostname or IP: (searching) Port: Heartbeat interval (seconds): 30 Heartbeat band: all Always use minimal heartbeat: false Last successful heartbeat: (not yet contacted) Change these? (y/n) [n]: y --- Enter New Values --- Use Management Server (y/n/auto) [auto]: y Hostname or IP [127.0.0.1]: 10.10.10.25 Set NTP location to 10.10.10.25 (y/n) [n]: y Port : Heartbeat interval (seconds) : Heartbeat during [all]: Connecting to 172.30.5.48:8443 TCP connection established. Management server returned a trusted certificate. Do you want to commit these changes? (y/n): y
Management server settings include:
Once you save the settings, the Local Manager will automatically attempt to contact the Control Center. You can view heartbeat status with the show system management command.
[admin@LantronixLM]# show system management Use Management Server: yes Hostname or IP: 10.10.10.25 Port: 8443 Heartbeat interval (seconds): 30 Heartbeat band: all Always use minimal heartbeat: false Last successful heartbeat: 11/01/2020 10:08:34 CDT (Full)
The last line of the output shows when the last heartbeat occurred and what kind it was (full vs minimal). If the time is more than 30 seconds (by default) in the past, try running show alarms to view any potential heartbeat alarms.
When Control Center management is enabled, the system will begin uploading alarms data via the heartbeat and archive features. Most data transferred via heartbeat is real-time information such as uptime, CPU usage, alarms, and events every 30 seconds. Larger data, such as user sessions and device files, are sent via archive every 60 minutes. Archiving uses high data compression to reduce network impact.
By default, archives are cached when operating out-of-band or during network failure.
System configuration can be performed via the CLI or Control Center. If a change is made on the CLI, the new setting will be pushed up to the Control Center during the next heartbeat. Similarly, changes made on the Control Center will transfer down and take effect on the system during the next heartbeat.
To view the system's current archive settings, use the show system archive command.
[admin@LantronixLM]# show system archive Time Between Archivals (seconds): 3,600 Maximum Archives Stored Locally: 100 Enable While Out-of-Band: false
To edit the system's archive settings, use the config system archive command.
[admin@LantronixLM]# config system archive --- Existing Values --- Time Between Archivals (seconds): 3,600 Maximum Archives Stored Locally: 100 Enable While Out-of-Band: false Change these? (y/n) [n]: y --- Enter New Values --- Time Between Archivals (300-36000 seconds) : 1800 Maximum Archives Stored Locally (1-100) : Enable While Out-of-Band (y/n) [n]: Do you want to commit these changes? (y/n): y
When archives are created, they are tagged with a destination target based on the archive settings at the time of creation. If an archive is generated and destination IP, username, and/or password change before the archive can be transferred to the Control Center, an alarm will be generated indicating the failure. Verifying the correct settings in config system archive is not sufficient to clear the alarm; the old (improperly configured) archive must be deleted.
Here is an example of an archive alarm:
[admin@LantronixLM]# show alarms CDT Elapsed Device Interface Message ---- ------- ------ --------- ------------------------------------ 1/07 2:19 Archive failed. (connect timed out)
To remove old archives, use the config system clear archive command.
[admin@LantronixLM]# config system clear archive Remove Queued Archive Files (y/n) [n]: y Successfully removed queued archive files.