
Chapter 12
12 - 14
Forcing a serial terminal to be the console
In the case where you have not yet connected the serial terminal or it is not
active when the BIG-IP is booted, as it might be if you are using a terminal
server or dial-up modem, you can force the controller to use the serial
terminal as a console. Note that you do not need to disconnect the keyboard
if you use this procedure to force the serial line to be the console.
To force a serial terminal to be the console
1. Edit the /etc/boot.default file.
Find the entry -console auto. Change this entry to -console com.
2. Save the /etc/boot.default file and exit the editor.
3. Plug the serial terminal into the serial port on the BIG-IP.
4. Turn on the serial terminal.
5. Reboot the BIG-IP.
Once you configure a serial terminal as the console for the BIG-IP, the
following conditions apply:
Keyboard/monitor access is disabled, and logging in is only possible via
Secure Telnet (SSH), if configured, or the serial line.
If the boot.default file is corrupted, the system does not boot at all. Save a
backup copy of the original file and keep a bootable CD-ROM on hand.
The boot.default file must contain either the line: -console com or the line:
-console auto. Do not configure both settings. This could cause problems
when you attempt to boot the system.
Configuring RADIUS or LDAP authentication
You can configure the BIG-IP to use a RADIUS or LDAP server on your
network to authenticate users attempting to access the controller with SSH.
In this configuration, the RADIUS or LDAP server can function as a central
repository of users that are allowed access to the BIG-IP for administrative
purposes.
To configure RADIUS login support
Follow these steps to enable RADIUS authentication on BIG-IP.
1. Create the directory /etc/raddb.
Kommentare zu diesen Handbüchern