Fujitsu SPARC Enterprise T5120 Руководство по началу работы - Страница 3

Просмотреть онлайн или скачать pdf Руководство по началу работы для Сервер Fujitsu SPARC Enterprise T5120. Fujitsu SPARC Enterprise T5120 12 страниц. Sparc enterprise
Также для Fujitsu SPARC Enterprise T5120: Обзорное руководство (34 страниц), Руководство по планировке территории (26 страниц), Руководство по началу работы (12 страниц), Руководство по безопасности и соблюдению требований (34 страниц)

Fujitsu SPARC Enterprise T5120 Руководство по началу работы

Quick Setup Instructions

1. Unpack the server, and check that you received all of the shipping contents (
2. Place the server in its intended location for verification.
For rackmounting instructions, refer to the instructions included with the rail kit, the service label on the
server, and to the online SPARC Enterprise T5120 and T5220 Servers Installation Guide.
3. Connect a serial cable between the server's SER MGT port (
This connection provides your initial communication with the SP.
The device must be set up to communicate using 9600 baud, 8 bit, no parity, 1 stop bit. A null modem
configuration is needed, meaning the transmit and receive signals are reversed (crossed over) for DTE to
DTE communications. You can use the supplied RJ-45 crossover adapters with a standard RJ-45 cable to
achieve the null modem configuration.
Server Connections
FIGURE 2
n
Numbered cables
correspond to setup steps.
4. (Optional) Connect an Ethernet cable between the server's NET MGT port (
which future connections to the SP and host will be made.
After the initial configuration of the system using the SER MGT port, communication with the SP and host is
usually performed through this Ethernet interface.
5. Connect an Ethernet cable between one of the server's NET ports (
server will communicate.
SER MGT
NET MGT
RJ-45
RJ-45
RJ-45 to DB-25
crossover
RJ-45 to DB-9
crossover
FIGURE 2
NET 0 to NET 3
RJ-45
Host to Ethernet
SP to Ethernet
(Optional)
adapter
adapter
).
FIGURE 1
) and a terminal device.
Terminal
device
) and the network to
FIGURE 2
) and the network to which the
FIGURE 2