Product guide

QSSC-S4R Server System Product Guide Chapter 3: Server Utilities
Version 1.0
43
Display the network configuration of the BMC
IPMI 1.0, 1.5 and 2.0 authentication support
Packet encryption based on IPMI version
You can use any of the following consoles to launch dpccli or telnet and issue Command Line Interface
commands:
The Window’s command-line environment (command prompt)
A Linux* command shell
Using DPCCLI
The Command Line Interface tool has two modes: Platform Control mode and Serial Over LAN (SOL) Console
Redirection mode.
Platform control mode
When the Command Line Interface is in Platform Control mode, you can issue commands to the remote system.
To start a Command Line Interface session with dpccli, the network proxy dpcproxy must be running, either on
the managing console or a central network proxy system. However, by default you should not have to do
anything for the network proxy to be running, because the installation program installs the network proxy and
sets it up for automatic start upon reboot.
Serial Over LAN (SOL) mode
When the Command Line Interface is in SOL Console Redirection mode, you can perform, over a LAN
connection, any activity you could at the remote system’s console, including viewing the remote system’s
console output (SOL allows data from the server serial port to be redirected over the LAN).
The Serial over LAN Console Redirection mode of Command Line Interface lets servers transparently redirect
the serial character stream from the baseboard UART to and from the managing client system over the LAN.
Serial over LAN has the following benefits compared to a serial interface:
Eliminates the need for a serial concentrator
Reduces the amount of cabling
Allows remote management of servers without video, mouse, or keyboard (headless servers)
For a command prompt console, you must start dpccli before you can access the Command Line Interface
commands. The dpccli executable file acts as an interface between the console and the network proxy. Once the
interface is started, you can then connect to a server and enter commands.
DPCCLI ‘vs Telnet
There are two basic ways to issue Command Line Interface commands through the network proxy to a remote
server: by using the console interface, called dpccli; or by using telnet.
DPCCLI
An Command Line Interface session over dpccli requires a server name (or address) and login (user and
password), which can be supplied as arguments to the dpccli command.
Telnet
When using telnet to connect to the remote server (to issue Command Line Interface commands and to operate
in SOL mode), you must connect the telnet session to the dpcproxy by specifying (in the telnet command line)
the port on which dpcproxy is listening.
Once the Command Line Interface session over dpccli is running and the connection to the intended server is
established, you can begin issuing Command Line Interface commands to that server at the dpccli prompt. If
connecting via telnet, the same dpccli prompt is displayed when in Platform Control mode (default), and you can
issue Command Line Interface commands at the dpccli prompt over telnet.
Using telnet for both Platform Control and SOL Modes
Serial over LAN mode requires a telnet session from the managing console to the Network Proxy server,
regardless of which operating system (Microsoft Windows* or Linux*) you are running on either system. Start the
telnet session to the remote server as follows: