How Secure Remote Management Works
Because secure remote management (SRM) appliances are deployed at remote locations, they can locally manage a wide variety of networking gear, including satellite modems, switches and routers, as well as intelligent racks, and power and environmental control systems.
To ensure the SRM appliances can communicate during a network outage, a secure and reliable alternative communication path is designed into the architecture. Dial-up and wireless service can be used; if the VSAT is in an extremely remote location, low earth orbit connections can also be used. Many satellite service providers use service from Globalstar or Iridium for their secondary connection.
Through this direct connection to the console (serial) ports of the remote devices, the appliance can query the connected devices every few seconds, storing the data locally. Since the data is stored locally and doesnt need to be transmitted on a regular basis, there isnt a cost penalty for sampling frequently. Detailed event logs are available on an as-needed basis to help with problem resolution.
Once a sufficient repository of data has been gathered, it can then be analyzed. For a SRM appliance polling console ports at a remote location, the amount of data to indicate a problem can usually be gathered in 30-seconds or less. Once the data has been gathered, a policy engine inside the appliance determines if a parameter is in or out of specification, and either resolves the incident based on pre-approved guidelines, or communicates the problem to the network management center.
Once a problem signature is recognized, the SRM appliance can take steps to automatically resolve the incident and restore the service. In addition to restoring network connectivity, the logged and stored management data enable IT and service providers to establish a root cause that required the reboot. Such a determination can help to avoid in the future, or establish as a routine device issue that the SRM appliance is authorized to address automatically.
Unexpected downtime is always a possibility during software upgrades of network hardware. In some cases, the devices fail to boot after a new software load, thereby requiring a reliable and secure way to backtrack. In these cases, the SRM appliance needs to be able to restore the last-known-good-configuration automatically. The local control logs can then be examined once the network has been restored to understand what caused the network aberration.
Management actions and associated logging data exchanges between the NOC and the remote sites should be safeguarded. Designing a remote management platform with a robust AAA (authentication, authorization, and audit) security model, combined with the physical properties of a specific purpose appliance, ensures the protection of the systems and network devices and the network itself. This way, all actions are logged and stored locally, giving visibility to all management actions to these devices.
|
|