Filter
Top Products
60 Sun Fire V100 Server User’s Guide • December 2001
Separating LOM From the Console on
the Serial A/LOM Port
By default, the LOM device shares the Serial A/LOM port with the console, and
when it has an event report to send, it takes control of the Serial A/LOM port itself,
interrupting any console activity you are performing. To prevent the LOM device
from interrupting the console, either turn serial event reporting off (see Chapter 6),
or dedicate the Serial A/LOM port to the LOM device and use the Serial B port for
console activity. The next section, “To Dedicate Serial A/LOM to LOM” on page 60,
gives more detail.
The advantages of dedicating the Serial A/LOM port to the LOM device and using
Serial B as your console port include:
■ Preserving the ability to power on or reset the server (from the lom> prompt on
Serial A/LOM) even if for any reason you lose access to Solaris on your console
port (Serial B).
■ Capturing all LOM events passively on a terminal connected to the dedicated
LOM port (Serial A/LOM). Note, however, that if you dedicate the Serial A/LOM
port to the LOM device, you cannot use the console command to quit the LOM
shell. Instead, for access to the Solaris environment, you must connect to the
server using the Serial B port.
■ Preventing a user with console access from using the LOM escape sequence to
exit the Solaris environment and access the LOM shell. If you dedicate the Serial
B port to the console, users cannot bring up the LOM shell, which means that
they cannot interrogate or reconfigure the LOM device.
■ Performing binary data transfers. To perform any task other than an ASCII
transfer, you must use the Serial B port.
▼ To Dedicate Serial A/LOM to LOM
1. Set up console connections to both the Serial A/LOM port and the Serial B port.
2. At the Solaris prompt, type:
# eeprom input-device=ttyb
# eeprom output-device=ttyb
# reboot