This chapter discusses the following:
This section discusses the following:
To set up the serial console, do the following:
Connect one end of your serial cable to your SGI server on COM1.
Connect the other end directly to one of the following:
Use your console device to gain shell access or use terminal emulator software running on a workstation (connected to your terminal server or serial concentrator equipment).
 | Note: By default, Linux does not allow telnet login for root. Therefore, there must be a regular user account already set up even if Bastille was not run. |
For security purposes, you should deny access to the telnet daemon from all public networks, using both ipchains(8) and tcp_wrappers for redundancy. You will perform this step as part of using the Bastille Linux script. See Chapter 5, “Server Lockdown Using Bastille Linux”.
Using a serial console access for preproduction tasks has the following advantages:
It allows you to place your SGI server in your network operations center while still performing preproduction tasks
You can move your SGI server into production mode without recabling
You will also want a remote console during production mode. In a production environment, you would typically have multiple server systems and use either a serial concentrator or a serial terminal server to access them all from a workstation in your network operations center.
This section discusses the following:
To set up the local console, do the following:
Plug the SVGA monitor into the video connector.
Plug the standard PC PS/2 keyboard into the keyboard connector.
Plug the PS/2 mouse into the mouse connector.
See the hardware documentation for more details.
You may want to use local console access while you are setting up your SGI server before placing it in production mode, especially if you are performing preproduction tasks in an area outside your network operations center. This method is simple, but may require you to physically move and recable your system later on.