LWFX

Networks can be large, not just topographically, but geographically. Even in a single building, running between multiple servers and terminals can be taxing and inefficient. Using Console  Management, an admin can eliminate running up and down between floors at work. Add Virtual Private Networks (VPNs) to the mix, and console management becomes a must, since a single intranet can easily span across the country, or even across continents.

Consoles can be used to remotely administer any machine in the network that is attached. The great thing about consoles is that they can be set up and “grown in,” with notes, special programs, and even custom keyboards or monitors that suit a particular admin. No matter how disparate machines in network may be, the admin is able to remotely work from a stable and comfortable environment. This saves both time and money for the organization. As soon as a support request is made, as long as the admin is not already busy fixing something else, he can respond to the request and fix it.

Security is obviously important with consoles, since a console can be a very powerful portal to controlling the entire intranet. Some consoles on very high security networks are wired directly to the machines they manage using serial cables. This may be too limiting and impractical, especially across multiple rooms or where VPNs are involved. If Ethernet is used, it is important to make the console a closed-off system. The console should be behind a high quality dedicated firewall. All ports and services should be blocked, except those necessary to operate as a console.

If remote access to the console is deemed necessary (so that an admin can respond on-call to network problems), SSH should be used with a key pair to encrypt traffic to the console. It is best to avoid using the standard port 22 to help throw would-be hackers off trail.

Filed under:
Business by guest