Patton electronic SmartNode 4110 Series manual Accessing the SmartWare CLI task list, If desired

SmartWare Software Configuration Guide 4 • Accessing the CLI

Introduction

SmartNode products are designed for remote management and volume deployment. The management and configuration of SmartNodes is therefore based on IP network connectivity. Once a SmartNode is connected to, and addressable in, an IP network, you can remotely perform all configuration, management, and mainte- nance tasks.

This chapter describes the procedures for entering SmartWare commands via the command line interface (CLI), to obtain help, to change operator mode, and to terminate a session. You can access a SmartNode as follows:

•Directly, via the console port (if available)

•Remotely, via the IP network (by using a Telnet application)

The ports available for connection and their labels are shown in the getting started guide that came with your unit.

Remember that the CLI supports a command history and command completion. By scrolling with the up and down arrow keys, you can find many of your previously entered commands. Another timesaving tool is com- mand completion. If you type part of a command and then press the <tab> key, the SmartWare shell will present you with either the remaining portion of the command or a list of possible commands. These features are described in chapter 3, “Command line interface (CLI)” on page 49. The telnet server can be disabled

if desired.

Although SmartWare supports concurrent sessions via Telnet or the console port, we do not recommend working with more than

one session to configure a specific SmartNode. However, using IMPORTANT one session for configuration and another for debugging is a

good idea.

Accessing the SmartWare CLI task list

The following sections describe the basic tasks involved in accessing the SmartWare command line interface. Depending on your application scenario, some tasks are mandatory while others could be optional.

•Accessing via the console port (see page 55)

•Accessing via a Telnet session (see page 55)

•Using an alternate TCP listening port for the Telnet server (see page 56)

•Disabling the Telnet server (see page 56)

•Logging on (see page 56)

•Selecting a secure password (see page 57)

•Configuring operators and administrators (see page 58)

•Displaying the CLI version (see page 60)

•Displaying account information (see page 60)

•Switching to another log-in account (see page 61)

•Checking identity and connected users (see page 61)

Introduction 54