Why Does a Console Access Server Need Outbound SSH/Telnet Capability?

When managing a network, it’s always best to have several different ways to access command functions on remote network devices. Efficiently planned network infrastructure should always include an alternate path to allow communication with remote network elements when normal network communication is not available. A console access server that includes outbound SSH/Telnet capabilities provides a secure, reliable means to communicate with remote devices when normal communication channels are either down or impractical.

A console access server with Outbound SSH/Telnet capabilities can perform several functions; both as an alternate, secondary means of communication, and as a primary means of communication for applications where it’s either impractical or prohibitively expensive to run an Ethernet cable to a remote network equipment site.

When your primary network is down, Outbound SSH/Telnet can be used to establish an out of band connection to a remote device in order to perform troubleshooting, configuration or diagnostic tasks. For example, if the firewall at a remote site was down and normal channels for communication were not available, you could still establish a dial-up connection with the console access server and then employ outbound SSH or Telnet to communicate with the firewall in order to get it back up and running again. In this case, in addition to providing a much cheaper alternative to an expensive service call, outbound SSH/Telnet would also allow you to get your network back up and running again, without waiting for service personnel to reach the remote equipment site.

Outbound SSH/Telnet can also provide vital communication functions in cases of extremely remote equipment installations, where an Ethernet connection was not available or practical. Many remote network applications include a console access server with outbound SSH/Telnet to allow administrators to dial into the console access server via satellite modem, and then use Outbound SSH or Outbound Telnet to connect to other devices on the remote network. This allows communication with remote network devices, without the need to send tech support personnel on a long road trip to the remote site every time a device needed to be rebooted or reconfigured, and without the need to spend a ton of money running a network cable or phone line to the remote location.

Outbound SSH/Telnet allows secure, reliable method to access console port command functions on remote devices and provides a perfect solution for both applications that are too remote for normal network communication and applications that just require a workable, secondary means of communication when the primary network is not available.

Western Telematic, Inc. (WTI) designs and manufactures remote device management products for IT applications. WTI’s Serial Console Server products, Remote Reboot products, Switched PDU products and A/B Fallback products are engineered to allow you to securely manage and troubleshoot rack equipment in remote locations.

Tags: , , , , ,

Comments are closed.