test

Sun Remote System Control (RSC) User's Guide

Chapter 4 Using the RSC Command Shell

The easiest way to use Sun Remote System Control is through the graphical user interface (GUI). Online Help is available when you use the GUI.

If you need to use RSC and the GUI is not available, you can use the RSC command shell. The RSC command shell is a simple command-line interface that supports commands that allow you to administer or diagnose the server. It also has commands for configuring RSC.

RSC supports a maximum of two concurrent telnet connections per server. These connections can be command-line interface sessions or RSC GUI connections to the server console (Open Console). In addition, RSC supports up to three concurrent RSC GUI sessions.

After you log in to your RSC account, the RSC shell prompt appears (rsc>), and you can enter RSC shell commands. This chapter tells you how to log in to your RSC account and describes RSC command use and syntax.

The following table summarizes RSC shell commands. Each command is explained in greater detail in the following sections.

Table 4-1 RSC Shell Commands

Name 

Description 

environment

Displays current environmental information 
shownetwork

Displays the current network configuration 

console

Connects you to the server console 

break

Puts the server in debug mode 
xir

Generates an externally initiated reset to the server 

bootmode

Controls server firmware behavior, if followed by a server reset within 10 minutes (similar to L1-key combinations on Sun keyboards) 

reset

Resets the server immediately 

poweroff

Powers off the server 

poweron

Powers on the server 

loghistory

Displays the history of all events logged in the RSC event buffer 

consolehistory

Displays the history of all console messages logged in the buffer 
consolerestart

Makes the current boot and run console logs "original" 

set

Sets a configuration variable 

show

Displays one or more configuration variables 

date

Displays or sets the current time and date 

password

Changes your RSC password 
useradd

Adds an RSC user account 
userdel

Deletes an RSC user account 
usershow

Shows characteristics of an RSC user account 
userpassword

Sets or changes a user's password 
userperm

Sets the authorization for a user 

resetrsc

Resets RSC immediately 

help

Displays a list of RSC shell commands and a brief description of each 
version

Displays the RSC firmware version 

logout

Ends your current RSC shell session 

Note -

Some commands require a specific user permission level. See "userperm username [c][u][a][r]" for information about user permission levels.

More detailed descriptions of the commands are provided in the following sections.

Logging In to Your RSC Account

After RSC software is installed and configured and an account has been set up for you, you can connect to RSC and log in to your account using a Solaris workstation, Windows PC, standard ASCII character terminal, or a computer running ASCII terminal emulation software.

Follow these steps to log in to your RSC account:

  1. Connect to RSC using one of these five methods:

    1. Use point-to-point protocol (PPP) to connect to your company Ethernet, and then use the telnet command to connect to RSC.

      Ask your network administrator if you do not know the server's RSC name (it is usually servername-rsc).

    2. If you are already connected to your company Ethernet, use the telnet command to connect to RSC.

    3. Use PPP to connect to the RSC modem. To use this option, PPP must be enabled.

    4. If PPP is not enabled on the serial port, dial in to the RSC modem.

    5. Connect your client machine directly to the RSC serial port.

      To use this option, you must disable PPP by using the RSC shell or rscadm utility to set the ppp_enabled configuration variable to false, or by using the GUI.

      When connection is established, the following screen appears: 

      RSC version 1.0
Please login:
Please enter password:

  2. Enter your RSC login name.

  3. Enter your RSC password.

    Your password is not echoed on the screen. After you correctly enter your password, RSC displays this command prompt: 

    rsc>

    You can enter RSC shell commands at the rsc> prompt.

Logins are recorded in the RSC event log. In addition, RSC sends an alert if it detects five login failures within five minutes. You can also set RSC to disconnect a session connected to the serial port after ten minutes of inactivity; see "serial_hw_handshake".

Server Status and Control Commands

The following RSC commands show server status or control server operation:

environment

Use the environment command to display a snapshot of server environmental status, such as temperatures, power supply status, front panel LED status, keyswitch position, and so forth. The display uses similar format to that used for the UNIX command prtdiag(1m). For example:

rsc> environment
                

==================== Environmental Status ====================


System Temperatures (Celsius):
------------------------------
      CPU0    42
      CPU1    52
       MB0    33
       MB1    27
       PDB    29
      SCSI    25

=================================
Front Status Panel:
-------------------

Keyswitch position is in On mode.

System LED Status:  DISK ERROR      POWER 
                      [OFF]         [ ON]      
                POWER SUPPLY ERROR  ACTIVITY 
                      [OFF]         [ ON]      
                    GENERAL ERROR   THERMAL ERROR  
                      [OFF]         [OFF]      

=================================


Disk LED Status:    OK = GREEN  ERROR = YELLOW
        DISK  5: [EMPTY]    DISK  3: [EMPTY]    DISK  1:    [OK]
        DISK  4: [EMPTY]    DISK  2:    [OK]    DISK  0:    [OK]

=================================


Fan Bank:
---------

Bank      Speed     Status
         (0-255)    
----      -----     ------
 SYS       151        OK

=================================


Power Supplies:
---------------

Supply     Status
------     ------
  0          OK  
  1          OK  

=================================

rsc>

shownetwork

The shownetwork command displays the current network configuration, for example: 

rsc> shownetwork
RSC network configuration is:
DHCP server: 129.149.2.3
IP Address: 129.149.2.6
Gateway Address: 129.149.2.7, 129.149.2.8
Netmask: 255.255.255.0
Ethernet Address: ae:30:30:00:00:01
rsc>

console

Use the console command to enter RSC console mode and connect to the server console from the RSC shell. When you use this command, the system displays a standard Solaris login prompt. If RSC is not designated as the server console, nothing is displayed.

You must have C level user permission to use this command. An escape character sequence is used to return to the RSC prompt. The default escape sequence is ~. (tilde period). See "escape_char".

break

Use the break command to put the server into debug mode. You must have C level user permission to use this command. The server front panel keyswitch must not be in the Lock position, and the server serial port must be designated as the console (see Chapter 6, Using OpenBoot PROM Features That Support RSC). Debug mode can use either kadb or OBP.

xir

This command generates the equivalent of an externally initiated reset (XIR) of the server. You must have R level user permission to use this command. The server enters OBP mode and displays the ok prompt. This command is useful for driver or kernel debugging, as most of the contents of the server's memory and registers is preserved. To resume the system after using the xir command, you must reboot the server.

bootmode [-u] [normal|forth|reset_nvram|diag| skip_diag]

This command provides control over the server firmware behavior after a server reset. Functionality of this command is identical to that available on Sun keyboards using L1 key combinations. You must have R level user permission to use this command. If you use the bootmode command without arguments, RSC displays the current boot_mode.

The bootmode setting overrides the server's OBDiag diag-switch? setting immediately after the next reset only. If RSC does not detect a server reset within 10 minutes, the bootmode command is ignored. For example: 

rsc> bootmode forth
rsc> reset

To set the diag or skip_diag option, you must follow the bootmode command with the poweroff and poweron commands within 10 minutes. For example: 

rsc> bootmode skip_diag
rsc> poweroff
rsc> poweron

To force console input and output to RSC, use the -u option before specifying the boot mode.

The following table describes modes you can specify using the bootmode command.

Table 4-2 Modes Used With the bootmode Command

Mode 

Description 

-u

Force the server to direct the console to RSC; the -u option must precede any boot_mode you specify; requires server reset

normal

Normal boot; server runs low-level diagnostics; requires server reset 

forth

Enter Forth interpreter as soon as possible (equivalent to L1-F on keyboard); requires server reset 

reset_nvram

Reset all NVRAM variables to default values (equivalent to L1-N on keyboard); requires server reset 

diag

Force the server to run full diagnostics (equivalent to L1-D on keyboard); requires server power-off and power-on 

skip_diag

Force the server to skip diagnostics (equivalent to L1-S on the keyboard); requires server power-off and power-on 

Note -

The diag and skip_diag modes take effect only if you follow the bootmode command with the poweroff and poweron commands within 10 minutes.

reset

This command forcibly resets the server immediately. You must have R level user permission to use this command. The server reboots according to the server's designated boot_mode.

Note -

The default configuration of Sun Enterprise 250 firmware does not invoke POST when the server resets. However, you can change this behavior through NVRAM variable settings; for additional details, see Platform Notes: Sun Enterprise 250 Server.

poweroff

Use the poweroff command to power off the server. You must have R level user permission to use this command. This command has no effect if the server is already powered off. RSC remains available since it uses the server's standby power.

poweron

Use the poweron command to power on the server. You must have R level user permission to use this command. This command has no effect if any of the following is true:

RSC View Log Commands

Use the following RSC commands to work with RSC and console log files:

loghistory [index [+|-]n] [pause n]

Use the loghistory command without subcommands to display the history of all events logged in the RSC event buffer. These events include server reset events and all RSC commands that change the state of the system. You can also use the command abbreviation lhist.

Use the following subcommands to control loghistory display.

index [+|-]n

Use the index subcommand to designate a buffer position at which to begin the display, as follows:

The origin of counting is 1; that is, index +1 indicates the first line in the buffer, index -1 indicates the last. For example: 

rsc> loghistory index -30

This command prints the last 30 lines and any additional lines that were appended to the buffer between the time that the command began execution and the time that it terminated.

pause n

Use the pause subcommand to display n lines of the log at a time (similar to the more command). The value of n must be a decimal integer. The default is to display the entire RSC log without pausing.

Each event recorded in the log has the following format: 

$TIME $HOSTNAME $EVENTID $message

EVENTID is a unique identifier for the event, TIME is the time the event occurred (as measured by RSC time), and message is a user-friendly description of the event.

The following is an example event log entry: 

FRI JAN 01 07:33:03 1999 sst4828: 00060003: "RSC System booted"

consolehistory [boot|run|oboot|orun] [index [+|-]n] [pause n]

Use the consolehistory command to display console messages logged in RSC buffers. With no arguments, this command prints the entire contents of all non-empty console buffers. You can use the command abbreviation chist.

There are four console logs:

The boot and oboot buffers can contain up to 8 Kbytes of information, and the run and orun buffers can contain up to 16 Kbytes of information.

When the first power-on boot begins, RSC fills the original boot (oboot) buffer with data from the server's console. After that buffer fills up, it writes data to the original run (orun) log. When the orun log fills up, it overwrites old data in the orun log.

When RSC senses a server reset while in the orun log, it switches to the boot log. After that fills up, it switches to the run log. When the run log fills up, it overwrites old data in the run log.

When RSC senses a server reset while in the current run log, it switches to the current boot log again.

pause n

Use the pause subcommand to display n lines of the log at a time (similar to the more command). The value of n must be a decimal integer. The default is to display 10 lines of the log at a time.

See "loghistory [index [+|-]n] [pause n]" for a description of the index subcommand.

Note -

Time stamps recorded in console logs reflect server time. These time stamps may be offset from RSC time stamps recorded in the RSC event log. To find information on synchronizing RSC time with server time using the rscadm utility, see "date [-s] date [[mmdd]HHMM|mmddHHMM[cc]yy]][.SS]".

consolerestart

Use the consolerestart command to make the current boot and run logs the "original" logs (designated oboot and orun). This command copies the current boot and run buffers to the oboot and orun buffers, overwriting the previous contents. Then it clears the current boot and run buffers. You must have A level user permission to use this command.

After adding a hardware component to the server, reboot the server and then use the consolerestart command so that the new part will appear in the original console logs.

RSC Configuration Commands

Use the following RSC commands to set or show characteristics of the RSC or server configuration:

set variable value

Use the set command to set an RSC configuration variable. You must have A level user permission to use this command. See "RSC Configuration Variables" for descriptions of these variables.

Changes to some variables do not take effect until the SSP that RSC is running on is reset using the command resetrsc or rscadm resetrsc.

You can use the null string ("") to set a variable to null. To set a variable to a string that includes spaces, enclose the string in double quotes. For example: 

rsc> set page_info2 ""
rsc> set page_init1 "&F &E0"

show [variable]

Use the show command to display the value of RSC configuration variables. You can specify one variable only; if you do not specify a variable, RSC displays all configuration variables. See "RSC Configuration Variables" for descriptions of these variables.

date [[mmdd]HHMM|mmddHHMM[cc]yy][.SS]

Use the date command without arguments to show RSC's current date and time. If you have A level user permission, you can use the date command to set the current date and time. The following table describes components of the date format.

Table 4-3 Components of the date Command

Option 

Description 

mm

Month number 

dd

Day-of-the-month number 

HH

Hour number (24-hour system) 

MM

Minute number 

.SS

Second number 

cc

First two digits of year 

yy

Last two digits of year 

You may omit the month, day, and year; the current values are applied as defaults.

Examples: 

rsc> date 091521451998
rsc> date 09152145
rsc> date 2145

The first example sets the time to September 15, 9:45 p.m., 1998. The second example sets the time to September 15, 9:45 p.m. of the current year. The third example sets the time to 9:45 p.m. of the current month, day, and year.

Note -

Whenever the server boots, it sets the RSC current date and time. However, to keep RSC time in sync with server time, Sun Microsystems recommends that you implement a script that uses the command rscadm date -s to update RSC time periodically from the server time. The RSC shell date command cannot synchronize RSC time with the server time.

password

Use the password command to change the RSC password for the account to which you are logged in. This command behaves similarly to the UNIX passwd(1) command.

When used to change a password, RSC prompts for your current password, and if you enter it correctly, it prompts for the new password. RSC prompts again for the new password, and updates it if entered identically both times. For example: 

rsc> password
password: Changing password for username
Enter login password: 
Enter new password: 
Re-enter new password: 
rsc>

Passwords have the following restrictions:

useradd username

Adds an RSC user account. You must have U level user permission to use this command. The maximum number of RSC user accounts is four. Valid characters for username include:

The username field has a maximum length of eight characters, must contain at least one lowercase alphabetic character, and the first character must be alphabetic. If these restrictions are not met, the system issues a warning and the command fails.

userdel username

Deletes an RSC user account. You must have U level user permission to use this command.

usershow [username]

Shows RSC user accounts. You must have U level user permission to use this command. If no argument is supplied, all accounts are shown. Information displayed includes username, permissions, and whether a password is assigned. For example: 

rsc> usershow
Username Permissions Password?
setup    cuar        Assigned
msmith   c--r        None
rsc>

userpassword username

Sets or changes the password for the specified user account. You must have U level user permission to use this command. RSC does not prompt for an existing password. See the password command for details on password format and restrictions. For example: 

rsc> userpassword msmith
New password: 
Re-enter new password: 
rsc>

userperm username [c][u][a][r]

Sets or changes permission levels for a specified user account.

All RSC users can look at RSC information. The following arguments increase a user's authorization level:

You must have U level user permission to use this command. You can specify zero through four authorizations. The default authorization level for a new RSC account is none of the above.

If you do not specify authorization levels, RSC sets the permissions for username to read-only. However, the default user permission for the account you create during the installation procedure is cuar (full authorization).

A user with read-only permission can use the following commands only:

resetrsc

The resetrsc command performs a hard reset of RSC. This terminates all current RSC sessions. You must have A level user permission to use this command. You can also reset RSC by using the rscadm resetrsc command.

Other RSC Commands

help

The help command displays a list of all RSC shell commands and a brief description of each.

version [-v]

The version command displays the firmware version running on RSC. Use the -v option to display more verbose information. Examples: 

rsc> version
RSC Bootmon version: 0.23
RSC version: 0.23
rsc> version -v
RSC Bootmon version: 0.23
RSC Bootmon checksum: A91695A9
RSC version: 0.23
RSC firmware checksum: 4FF151DA
RSC firmware built Apr 28 1998, 12:31:15
rsc>

logout

The logout command ends your RSC session and closes your RSC connection.

RSC Configuration Variables

RSC has non-volatile configuration variables you can use to change RSC behavior. The installer sets most configuration variables during installation. After installation, you can use the GUI, RSC shell, or the rscadm set command to set or change configuration variables.

You must have A level user permission to set configuration variables from the GUI or RSC shell; you must log in to the server as root to use the rscadm set command.

Use the show command to show configuration variables, and use the set command to set a variable. Changes to variables take effect immediately except as noted.

You can use the null string ("") to set a variable to null. To set a variable to a string that includes spaces, enclose the string in double quotes.

Serial Port Variables

serial_baud

This variable sets the RSC serial port baud rate. Valid values are:

The default setting is 9600. Changes to this variable take effect on the next login connection over the RSC serial port.

If you change the serial baud rate after configuring the serial port modem, you must reconfigure the modem; see "Modem Reconfiguration Required After Changing RSC Serial Port Settings".

serial_parity

This variable sets the RSC serial port parity; valid values are none, odd, or even. The default setting is none. Changes to this variable take effect on the next login connection over the RSC serial port.

If you change the serial parity setting after configuring the serial port modem, you must reconfigure the modem; see "Modem Reconfiguration Required After Changing RSC Serial Port Settings".

serial_stop

This variable sets the number of RSC stop bits; valid values are 1 or 2. The default setting is 1. Changes to this variable take effect on the next login connection over the RSC serial port.

If you change the serial stop bits setting after configuring the serial port modem, you must reconfigure the modem; see "Modem Reconfiguration Required After Changing RSC Serial Port Settings".

serial_data

This variable sets the number of RSC data bits; valid values are 7 and 8. The default setting is 8. Changes to this variable take effect on the next login connection over the RSC serial port.

If you change the serial data bits setting after configuring the serial port modem, you must reconfigure the modem; see "Modem Reconfiguration Required After Changing RSC Serial Port Settings".

serial_hw_handshake

This variable controls whether RSC uses hardware handshaking on the serial port. Valid values are true and false; the default setting is true. If set to true, hardware flow control and modem control are enabled. If set to false, RSC disconnects a session connected to the serial port after 10 minutes of inactivity.

ppp_local_ip_addr

Use this variable to specify the Internet protocol (IP) address for RSC to use during a PPP session; use standard dot notation. If this variable is empty, RSC expects the remote node to set the Internet address dynamically. The default setting is 0.0.0.0 (empty). Changes to this variable take effect on the next PPP connection over the RSC serial port.

ppp_remote_ip_addr

Use this variable to specify the IP address for the remote node during a PPP session; use standard dot notation. If this variable is empty, RSC expects that the remote node already has an Internet address assigned for the PPP session. The default setting is 0.0.0.0 (empty). Changes to this variable take effect on the next PPP connection over the RSC serial port.

ppp_enabled

Use this variable to specify whether PPP is the default protocol on the RSC serial port. Valid values are true or false; the default is false. Changes to this variable take effect on the next login connection over the RSC serial port.

Alert Variables

page_enabled

Use this variable to specify whether paging is enabled for RSC alerts. Valid values are true or false; the default is false.

mail_enabled

Use this variable to specify whether an email message is enabled for RSC alerts. Valid values are true or false; the default is false.

page_info1

This variable contains the phone number and associated pager ID number for sending a TAP alert to a pager. Use the character @ to separate the telephone number and ID. Valid characters are:

If both the page_info1 and page_info2 variables are empty, or if the page_enabled variable is set false, no paging will occur. The default setting for page_info1 is empty. For example: 

rsc> set page_info1 18004420500@1234332

page_init1

This variable specifies a string consisting of attention (AT) commands used for configuring the RSC modem prior to sending an alert to pager 1.

page_password1

This variable contains the pager service password used to send an alert to pager 1. The password must be an alphanumeric string of six characters or fewer.

page_baud1

This variable specifies the serial port baud rate to use when sending an alert to pager 1. Valid values are 300, 1200, 2400, 4800, and 9600. After RSC sends the page alert, the baud setting reverts to the setting specified in the serial_baud variable.

page_data1

This variable specifies the number of RSC serial port data bits for sending an alert to pager 1. Valid values are 7 and 8. After RSC sends the page alert, the data bits revert to the setting specified in the serial_data variable.

page_parity1

This variable specifies the RSC serial parity for sending an alert to pager 1. Valid values are none, odd, and even. After RSC sends the page alert, the parity reverts to the setting specified in the serial_parity variable.

page_stop1

This variable specifies the number of RSC serial port stop bits for sending an alert to pager 1. Valid values are 1 and 2. After RSC sends the page alert, the stop bits revert to the setting specified in the serial_stop variable.

page_info2

This variable contains the phone number and associated pager ID number for sending a TAP alert to another pager. Use the character @ to separate the telephone number and ID. Valid characters are:

If both the page_info1 and page_info2 variables are empty, or if the page_enabled variable is set false, no paging will occur. The default setting for page_info2 is empty. For example: 

rsc> set page_info2 18004420596@4433444

page_init2

This variable specifies a string consisting of attention (AT) commands used for configuring the RSC modem prior to sending an alert to pager 2.

page_password2

This variable contains the pager service password used to send an alert to pager 2. The password must be an alphanumeric string of six characters or fewer.

page_baud2

This variable specifies the serial port baud rate to use when sending an alert to pager 2. Valid values are 300, 1200, 2400, 4800, and 9600. After RSC sends the page alert, the baud setting reverts to the setting specified in the serial_baud variable.

page_data2

This variable specifies the number of RSC serial port data bits for sending an alert to pager 2. Valid values are 7 and 8. After RSC sends the page alert, the data bits revert to the setting specified in the serial_data variable.

page_parity2

This variable specifies the RSC serial parity for sending an alert to pager 2. Valid values are none, odd, and even. After RSC sends the page alert, the parity reverts to the setting specified in the serial_parity variable.

page_stop2

This variable specifies the number of RSC serial port stop bits for sending an alert to pager 2. Valid values are 1 and 2. After RSC sends the page alert, the stop bits revert to the setting specified in the serial_stop variable.

customerinfo

This variable contains customer information used in the message generated for a pager or email alert, for instance, one of the following:

This string can be up to eight characters, including alphanumeric characters and hyphen (-). The default setting is empty.

hostname

This variable contains the name of the server connected directly to RSC; RSC includes this name in alert messages. This string can be up to eight characters, including alphanumeric characters and hyphen (-). The default setting is empty.

mailuser

This variable contains the address used for email alerts. The string has a 40-character limit; the default setting is empty. Although only a single mail address is permitted, you can notify several people that a problem has occurred by using an email alias.

mailhost

This variable contains a colon-separated list of Internet addresses to which RSC sends SMTP mail alerts. Each address is tried until the SMTP alert is successfully transmitted. Specify addresses using standard dot notation. For example: 

rsc> set mailhost 139.143.4.2:139.142.4.15

You can specify a maximum of two addresses. If this variable is empty, or if the mail_enabled variable is set to false, no email is sent. The default setting is empty.

Ethernet Port Variables

ip_mode

Use this variable to control how RSC configures the IP address for its local Ethernet port. Choose the ip_mode value according to the services available on the network to which RSC is connected. The following list describes the available values.

The default setting is dhcp. Changes to this variable take effect after the next RSC reset.

ip_addr

This variable is only used if the ip_mode variable is set to config. Specify the IP address in standard Internet dot notation; the default setting is 0.0.0.0 (empty). Changes to this variable take effect after the next RSC reset.

ip_netmask

This variable is only used if the ip_mode variable is set to config. Specify the subnet mask in standard Internet dot notation; the default setting is 0.0.0.0 (empty). Changes to this variable take effect after the next RSC reset.

ip_gateway

This variable is only used if the ip_mode variable is set to config. This is the default gateway to which RSC will send IP packets when the destination is not on the same subnet as RSC. Specify the IP address in standard Internet dot notation; the default setting is 0.0.0.0 (empty). Changes to this variable take effect after the next RSC reset.

Console Session Variable

escape_char

This variable sets the escape sequence character for ending a console session and returning to the RSC shell. The escape sequence applies to all RSC users for the server. The escape sequence consists of the escape character followed by a period. The default escape character is ~ (tilde).

The escape sequence character can be a single alphanumeric character. It can also be a control character. To enter a control character as the escape character, type "^" (Shift-6) to represent the Control key, followed by another character. If the second character is a question mark (?), the Delete key is selected; otherwise the second character is converted to a control character and used as the escape character. For example, if you enter ^y to set the escape character, users will use Control-y to end a console session.

RSC Shell Error Messages

This section provides additional information about error messages received at the rsc> prompt.

Usage Errors

Error messages 1 through 19 are usage error messages, displayed due to improper command syntax; see the description of the command in this chapter for the correct syntax.


Invalid command. Type 'help' for list of commands.


Usage: bootmode [-u] [normal|forth|reset_nvram|diag|skip_diag]


Usage: break


Usage: consolehistory [boot|run|oboot|orun] [index [+|-]<n>]


Usage: consolerestart


Usage: date [[mmdd]HHMM | mmddHHMM[cc]yy][.SS]


Usage: loghistory [index [+|-]<n>]


Usage: password


Usage: poweroff


Usage: poweron


Usage: reset


Usage: resetrsc


Usage: set <variable> <value>


Usage: shownetwork


Usage: useradd <username>


Usage: userdel <username>


Usage: userpassword <username>


Usage: userperm <username> [c][u][a][r]


Usage: version [-v]


Usage: xir

General Errors

RSC reports the following general errors.


Could not get username for user <username>

During execution of the userpassword command, a SEEPROM error occurred.


Error adding user <username>

An error occurred during execution of the useradd command; this message is followed by a more detailed message.


Error changing password for <username>

An error occurred during execution of the userpassword command; this message is followed by a more detailed message.


Error changing password for <username>

During execution of the userpassword command, a SEEPROM error occurred.


Error changing password for <username> - password must be at least three characters different from old password - password must not be based on username

You entered an invalid password.


Error deleting user <username>

An error occurred during execution of the userdel command; this message is followed by a more detailed message.


Error displaying user <username>

An error occurred during execution of the usershow command; this message is followed by a more detailed message.


Error setting permission for <username>

An error occurred during execution of the userperm command; this message is followed by a more detailed message.


ERROR: username did not start with letter or did not contain lowercase letter.

You entered an invalid username.


Failed to allocate buffer for console mode.

During execution of the console command, RSC could not allocate enough memory to connect to the console.


Failed to allocate memory!

During execution of the show command, RSC could not allocate enough memory to show the variable's value.


Failed to get password for <username>

During execution of the userpassword command, a SEEPROM error occurred.


Failed to set <variable> to <value>

During execution of the set command, RSC encountered a SEEPROM error.


Invalid login

Login attempt failed; this message appears at the login prompt.


Invalid password

You entered an illegal password with the userpassword command.


Invalid permission: <permission>

You entered an invalid user permission. Valid permissions are [c] [u] [a] [r]. See "userperm username [c][u][a][r]".


Malformed username

You specified a nonexistent user when entering the userpassword, userperm, or userdel command.


No free user slots

This error occurs if you try to add a user account when RSC already has four accounts configured. RSC supports only four user accounts; you must delete an account before you can add another.


Passwords don't match

The two entries for a new password did not match.


Permission denied

You attempted to execute a shell command for which you do not have the proper user permission level.


Sorry, wrong password

You entered an incorrect current password.


Unable to get value of variable <variable>

During execution of the show command, you used an invalid variable name.


User already registered

The user you are trying to add already has an RSC account on this server.


User does not exist

The username you specified is not associated with an RSC account on this server.