Copyright: ® CSG


Help Contents
Contents

Remote Console Manager Overview

What Is the Remote Console Monitor?

Which Systems Support the RCM?

Setting a Password for the First Time

Modem Usage

For More Information

Using the RCM Firmware Console

RCM Console Overview

Entering and Leaving Command Mode

Changing the Default Escape Sequence

RCM Firmware Console Commands

Commands Reference

Dial-Out Alerts

Troubleshooting

Resetting the RCM to Factory Defaults

Troubleshooting RCM on AlphaServer 4100

Troubleshooting RCM on AlphaServer 1000 or 2x00 Series

Modem Dialog Details

Phases of Modem Operation

KCRCM/Modem Interchange Overview

Modifying Initialization and Answer Strings

Initialization and Answer String Substitutions


What Is RCM
What Is the Remote Console Monitor?

The Remote Console Monitor (RCM) allows a system administrator to connect to a managed AlphaServer system through a modem, using a serial terminal emulator.

From the serial terminal emulator, the user invokes a special command interface consisting of firmware that resides on an independent microprocessor.  This firmware is not part of the SRM console firmware.  The user enters RCM console commands to monitor the power supplies, temperatures, and fans.  The user can also reset, halt, and power the system on or off from the RCM console.  No interaction with the SRM firmware or the operating system is required.

You can access the RCM through any terminal emulator, which can be launched out of the ServerWORKS Manager.  The following requirements must be met:

• 	The remote AlphaServer system must have RCM functionality installed.

• 	A Hayes-compatible modem is required.  Connections are only supported at

9600 baud.

• 	The phone number of the remote system is required.

• 	A password must be set and remote access to the modem port must be enabled on the remote

system.


Systems Supporting RCM
Which Systems Support the RCM?

The following AlphaServer systems support the Remote Console Monitor:

•	 AlphaServer 1000 and 1000A

• 	AlphaServer 2x00 series, which includes AlphaServer 2000, 2100, 2100 RM, 2100A, and 2100A RM

• 	AlphaServer 4100

The AlphaServer 4100 system has the RCM functionality built in.  You need a Hayes-compatible modem and the phone number of the remote AlphaServer 4100 system.  Also, a password for the managed server must be set and remote access to the modem port must be enabled on the managed server.  The modem connections are only supported at 9600 baud.

The AlphaServer 1000 series and 2x00 series systems support RCM functionality through an optional module, the KCRCM.  This module must be installed into an EISA/ISA slot on the managed system.  As part of the installation, the password of the managed server must be set and remote access to the modem port must be enabled on the managed server. To order a KCRCM module, call 1-800-DIGITAL or consult the Digital Systems and Options Catalog at the following Internet location:

http://www.digital.com/info/soc


Setting a Password
Setting a Password for the First Time

Before you can use the RCM to monitor a remote AlphaServer system, you must set a password and enable remote operation.  The initial loading of the password and enabling of remote operation must be done on the managed system.  You cannot enable remote operation or load the password initially from the ServerWORKS console.

For information on setting the password initially and enabling remote operation, refer to one of the following documents:

•	For AlphaServer 4100 systems, refer to AlphaServer 4100 System Drawer User's Guide

(EK-4100A-UG)

•	For AlphaServer 1000 series and AlphaServer 2x00 series, refer to KCRCM AlphaServer Remote

Console Module Installation and User's Guide (EK-KCRCM-IN), which comes with the KCRCM

module.


For More Information

Documentation for AlphaServer systems that support the RCM is listed below.  Some of these documents, including the KCRCM AlphaServer Remote Console Module Installation and User's Guide, are available in PostScript format from the Internet.  Go to:

http://www.digital.com/info/alphaserver/products.html

At the AlphaServer products page, select an AlphaServer system and click on the "Technical Resources" link.

Document Title	Part Number
KCRCM AlphaServer Remote Console Module Installation and User's Guide	EK-KCRCM-IN
AlphaServer 1000 Owners Guide	EK-DTLSV-OG
AlphaServer 1000A Owners Guide	EK-ALPSV-OG
AlphaServer 2000 Owners Guide	EK-400MP-IN
AlphaServer 2100 Owners Guide	EK-KN450-OP
AlphaServer 2100 RM Series Installation and Owners Guide	EK-KN450-RM
AlphaServer 2100A Owners Guide	EK-2100A-OP
AlphaServer 2100 A RM Series Installation and Owners Guide	EK-2100A-RM
AlphaServer 2000/2100/2100A Firmware Reference Guide	EK-AXPFW-RM
AlphaServer 4100 System Drawer User's Guide	EK-4100A-UG


RCM Console Overview

The RCM firmware resides on an independent microprocessor.  It is not part of the SRM console that resides in the flash ROM.  The RCM firmware has its own command interface that allows the user to perform the tasks that are usually done from the system's console terminal.  RCM console commands are used to reset, halt, and power the system on or off, regardless of the operating system or hardware state.  The RCM console commands are also used to monitor the power supplies, temperature, and fans.

To enter the RCM console remotely, you dial in through a modem, enter a password, and then type a special escape sequence that invokes RCM command mode.  Once in command mode, you enter commands to control and monitor the system.

The RCM also provides an autonomous dial-out capability that can be triggered when the managed server loses primary power due to either one of the following conditions:

•	A loss of line power due to automatic shutdown of the system because of a serious fault condition

•	A loss of power due to manual shutdown of the system by turning off the server power switch

When triggered, the RCM dials a paging service at 30-minute intervals until the administrator clears the alert within the RCM.


Modem Configuration
Modem Usage

Modem Selection

Dialing In to the RCM Modem Port

Terminating a Remote Console (Modem) Session


Modem Selection

The RCM requires a Hayes-compatible modem.  Connections are only supported at 9600 baud.  The controls that the RCM sends to the modem have been selected to be acceptable to a wide selection of modems.  The modems that have been tested and qualified include:

• 	Motorola LifeStyle Series 28.8

•	AT&T DATAPORT 14.4/FAX

•	Zoom Model 360

The U.S. Robotics Sportster DATA/FAX MODEM is also supported, but requires some modification of the modem initialization and answer strings.


Dialing In to the RCM Modem Port

1.	Dial the modem connected to the RCM.  The RCM answers the call and after a few seconds prompts for a password with a "#" character.

2.	Enter the password that was loaded on the server to be managed. The user has three tries to correctly enter the password.  On the third unsuccessful attempt, the connection is terminated, and as a security precaution, the modem is not answered again for 5 minutes.

On successful entry of the password, the RCM banner message "RCM V1.0" is displayed, and  the user is connected to the system COM1 port.  At this point the terminal keyboard local to the managed server is disabled except for entering the RCM console firmware.  The terminal displays all the terminal traffic going out to the modem.

3.	To connect to the RCM firmware console, type the RCM escape sequence .  A sample dial-in dialog would look similar to the following:

ATQ0V1E1S0=0 OK ATDT30167 CONNECT 9600	When modem dial-in connection is made, a screen display similar to this appears.
#	Enter password at this prompt.
RCM V1.0	RCM banner is displayed.
	Enter the escape sequence, ^]^]rcm, after the banner is displayed.  The escape sequence is not echoed on the terminal.
RCM>	After the escape sequence is entered, the RCM prompt is displayed.  RCM commands can be entered.


Terminating a Remote Console (Modem) Session

Terminate the modem session by executing a hangup command from the RCM console firmware.  This will cleanly terminate the modem connection.

If the modem connection is terminated without using the hangup command, or if the line is dropped due to phone line problems, the RCM will detect carrier loss and initiate an internal hangup command.  This process can take a minute or more, and the terminal local to the managed server will be locked out until the auto hangup process completes.

If the modem link is idle for more than 20 minutes, the RCM initiates an auto hangup.


Entering and Leaving Command Mode

Use the default escape sequence shown below to enter RCM command mode.  You can enter RCM command mode from the SRM console level, the operating system level, or an application.

^]^]rcm

The character string "^]" is created by simultaneously holding down the Ctrl key and pressing the ] key (right square bracket).  The firmware prompt, RCM>, should now be displayed.

The RCM quit command reconnects the terminal to the system console port.


Changing the Default Escape Sequence

The escape sequence used to enter the RCM firmware console command mode can be changed by the user.  To change the sequence, use the setesc command.

NOTE:  If you change the escape sequence, be sure to record the new sequence.  Although the module factory defaults can be restored if the user has forgotten the escape sequence, this involves accessing the KCRCM module and moving a jumper.


RCM Firmware Console Commands

Command Conventions

The following commands are used to remotely monitor an AlphaServer system.

Command	Function
alert_clr	Clears alert flag, stopping dial-out alert cycle
alert_dis	Disables the KCRCM dial-out alert function
alert_ena	Enables the KCRCM dial-out alert function
disable	Disables remote access to the modem port
enable	Enables remote access to the modem port
hangup	Terminates the modem connection
halt	Halts server
help or ?	Displays the list of commands
poweroff	Turns off power to server
poweron	Turns on power to server
quit	Exits console mode and returns to system console port
reset	Resets the server
setesc	Changes the escape sequence for entering command mode
setpass	Changes the modem access password
status	Displays server's status and sensors


 Command Conventions

•	Commands are not case sensitive.

•	A command must be entered in full.

•	If a command is entered that is not valid, the command fails with the message:

*** ERROR - unknown command ***

Enter a valid command.


Commands Reference

alert_clr

alert_dis

alert_ena

disable

enable

hangup

halt

help or ?

poweroff

poweron

quit

reset

setesc

setpass

status


alert_clr

The alert_clr command clears an alert condition within the RCM.  The alert enable condition remains active, and the RCM will again enter the alert condition when it detects a system power failure.  Refer to Dial-Out Alerts.

RCM>alert_clr


alert_dis

The alert_dis command disables RCM dial-out capability. It also clears any outstanding alerts.  Refer to Dial-Out Alerts.

The alert disable state is nonvolatile.  Dial-out capability remains disabled until the alert_enable command is issued.

RCM>alert_dis


alert_ena

The alert_ena command enables the RCM to automatically dial out when it detects a power failure within the system.  The RCM repeats the dial-out alert at 30-minute intervals until the alert is cleared.  The alert enable state is nonvolatile.  Dial-out capability remains enabled until the alert_disable command is issued.

RCM>alert_ena

In order for the alert_enable command to work, two conditions must be met:

•	A modem dial-out string must be entered with the system console.

•	Remote access to the RCM modem port must be enabled with the enable command.

If the alert_enable command is entered when remote access is disabled, an error message is returned:


disable

The disable command disables remote access to the RCM modem port.

RCM>disable

The module's remote access default state is DISABLED.  The modem enable state is nonvolatile.  When the modem is disabled, it remains disabled until the enable command is issued.  If a modem connection is in progress, entering the disable command terminates it.


enable

The enable command enables remote access to the RCM modem port.  It can take up to 10 seconds for the enable command to be executed.

RCM>enable

The module's remote access default state is DISABLED.

The modem enable state is nonvolatile. When the modem is enabled, it remains enabled until the disable command is issued.

The enable command can fail for two reasons:

•	There is no modem access password configured.

•	The modem is not connected or is not working properly.

If the enable command fails, the following message is displayed:

*** ERROR - enable failed ***


hangup

The hangup command terminates the modem session.  When this command is issued, the remote user is disconnected from the server.  This command can be issued from either the remote console or the console terminal local to the managed server.

RCM>hangup


halt

The halt command attempts to halt the managed system.  It is functionally equivalent to pressing the Halt button on the system operator control panel to the "in" position and then releasing it to the "out" position.  The RCM console firmware exits command mode and reconnects the user's terminal to the system console port.

RCM>halt

Focus returned to COM port

NOTE:  Pressing the Halt button has no effect on systems running Windows NT.


help or ?

The help or ? command displays the RCM firmware command set.


poweroff

The poweroff command requests the RCM module to power off the system  It is functionally equivalent to turning off the system power from the operator control panel.

RCM>poweroff

If the system is already powered off, this command has no effect.

The external power to the RCM must be connected in order to power off the system from the RCM firmware console.  If the external power supply is not connected, the command will not power the system down, and displays the message:

*** ERROR ***


poweron

The poweron command requests the RCM module to power on the system.  For the system power to come on, the following conditions must be met:

•	AC power must be present at the power supply inputs.

•	The On/Off button must be in the "on" position.

•	All system interlocks must be set correctly.

The RCM firmware console exits command mode and reconnects the user's terminal to the system console port.

RCM>poweron

Focus returned to COM port

NOTE:  If the system is powered off with the On/Off button, the system will not power up.  The RCM will not override the "off" state of the On/Off button.

If the system is already powered on, the poweron command has no effect.


quit

The quit command exits the user from command mode and reconnects the user's terminal to the system console port.  The following message is displayed:

Focus returned to COM port

The next display you see depends on what the system was doing when you invoked the RCM.  For example, if you invoked the RCM from the SRM console prompt, you will get the console prompt when you enter a carriage return.  Or, if you invoked the RCM from the operating system prompt, you will get the operating system prompt when you enter a carriage return.


reset

The reset command requests the RCM module to perform a hardware reset.  It is functionally equivalent to pressing the Reset button on the system operator control panel.

RCM>reset

Focus returned to COM port

The following events occur when the reset command is executed:

•	The system restarts and the system console firmware reinitializes.

•	The console exits RCM command mode and reconnects the user's terminal to the server's COM1 serial port.

•	The power-up messages are displayed, and then the console prompt is displayed or the operating system boot messages are displayed, depending on the state of the Halt button.


setesc

The setesc command allows the user to reset the default escape sequence for entering console mode.  The escape sequence can be any character string.  A typical sequence consists of 2 or more characters, to a maximum of 15 characters.  The escape sequence is stored in the module's on-board NVRAM.

NOTE:  If you change the escape sequence, be sure to record the new sequence.  Although the module factory defaults can be restored if the user has forgotten the escape sequence, this involves accessing the KCRCM module and moving a jumper.

The following sample escape sequence consists of five instances of the Ctrl key and the letter "o".

RCM>setesc

^o^o^o^o^o

RCM>

If the escape sequence entered exceeds 15 characters, the command fails with an error message.

When changing the default escape sequence, avoid using special characters that are used by the system's terminal emulator or applications.

Control characters are not echoed when entering the escape sequence.  To verify the complete escape sequence, use the status command.

If you forget the escape sequence, the module factory defaults can be restored.


setpass

The setpass command allows the user to change the modem access password that is prompted for at the beginning of a modem session.  The password is stored in the module's on-board NVRAM.

RCM>setpass

new pass>*********

RCM>

The maximum password length is 15 characters.  If the password entered exceeds 15 characters, the command fails with an error message:

The minimum password length is one character, followed by a carriage return.  If only a carriage return is entered, the command fails with an "illegal password" error message:

If the user has forgotten the password, a new password can be entered.


status

The status command displays the current state of the server's sensors, as well as the current escape sequence and alarm information.

RCM>status

Firmware Rev: V1.0

Escape Sequence: ^]^]RCM

Remote Access: ENABLE/DISABLE

Alerts: ENABLE/DISABLE

Alert Pending: YES/NO

Temp (C): 26.0

RCM Power Control: ON/OFF

External Power: ON

Server Power: OFF

PS 1:

PS 2:

R_Mode:

Fans:

RCM>

NOTE:  On the AlphaServer 4100 system, the last four status fields are not displayed.

Click here for an explanation of the status fields.


Status Fields

Field	Description
Firmware Rev:	Revision of RCM firmware.
Escape Sequence:	Current Escape sequence to enter RCM firmware console.
Remote Access:	Modem remote access state. (ENABLE/DISABLE)
Alerts:	Alert dial-out state. (ENABLE/DISABLE)
Alert Pending:	Alert condition triggered. (YES/NO)
Temp (C):	Current system temperature in degrees Celsius.
RCM Power Control:	Current state of RCM system power control.  (ON/OFF)
External Power:	Current state of power from external RCM power supply. (ON/OFF)
Server Power:	Current state of system power. (ON/OFF)
PS 1: and PS 2:	Current status of the power supplies in the server.
R_Mode:	Current state of the redundant power jumper in the system.  (ON/OFF)
Fans:	Current state of fans in system.  (OK)

NOTE:  The PS 1:, PS 2:, R_Mode:, and Fans: states are blank if the system power is off.  Two power supplies are always shown.  If the system has only one supply, the second supply would usually be displayed as OFF.


Dial-Out Alerts

The RCM can be configured to automatically dial out through the modem (usually to a paging service) when the managed server loses primary power due to either one of the following conditions:

•	A loss of line power due to automatic shutdown of the system because of a serious fault condition

•	A loss of power due to manual shutdown of the system by turning off the server power switch

These are the only conditions that can trigger automatic paging by the RCM.

When a dial-out alert is triggered, the RCM initializes the modem for dial-out, sends the dial-out string, hangs up the modem, and reconfigures the modem for dial-in.

The RCM and modem must continue to be powered, and the phone line must remain active, for the dial-out alert function to operate.

Enabling Dial-Out Alerts

Composing a Modem Dial-Out String


Enabling Dial-Out Alerts

Enable the dial-out alert function as follows:

1.	Enter the SRM system console command, set rcm_dialout, followed by a dial-out alert string, from the system console (P00>>> or >>> prompt).  The command takes the form:

>>>set rcm_dialout "ATDTstring#;"

The string is a modem dial-out character string, not to exceed 47 characters, that is used by the RCM when dialing out through the modem.

2.	Enter the RCM firmware console and enter the enable command to enable remote access dial-in.  The RCM firmware status command should display "Remote Access: Enable."

RCM>enable

RCM>status

.

.

Remote Access:  Enable

.

.

.

3.	Enter the RCM firmware alert_ena command to enable outgoing alerts.

RCM>alert_ena


Composing a Modem Dial-Out String

The modem dial-out string emulates a user dialing an automatic paging service.  Typically, the user dials the pager phone number, waits for a tone, and then enters a series of numbers.  The RCM dial-out string has the following requirements:

•	The entire string following the SRM console command set rcm_dialout must be enclosed by quotation marks.

•	The characters ATDT must be entered after the opening quotation marks.  Do not mix case.  Enter the characters either in all uppercase or all lowercase.

•	Enter the character X if the line to be used also carries voice mail.  Refer to the example that follows.

•	A semicolon (;) is required to terminate the string.

•	The valid characters for the dial-out string are the characters on a phone keypad:  0-9, *, and #.  In addition, a comma (,) requests that the modem pause for 2 seconds.

A typical set rcm_dialout command string would be similar to the following:

>>>set rcm_dialout "ATXDT9,15085553333,,,,,,5085553332#;"

ATXDT	AT = Attention X = Forces the modem to dial "blindly" (not look for a dial tone).  Enter this character if the dial-out line modifies its dial tone when used for services such as voice mail. D = Dial T = Tone (for touch-tone) ,  =  Pause for 2 seconds.
9,	In the example, "9" gets an outside line.  Enter the number for an outside line if your system requires it.
15085553333	Dial the paging service.
,,,,,,	Pause for 12 seconds for paging service to answer
5085553332#	"Message," usually a call-back number for the paging service.
;	Return to console command mode.  Must be entered to terminate string.

Use the SRM show command to verify the RCM dial-out string:

>>>show rcm_dialout

rcm_dialout       ATXDT9,15085553333,,,,,,5085553332#;


Resetting the RCM to Factory Defaults

Resetting RCM on AlphaServer 4100 System

Resetting RCM on AlphaServer 1000 or 2x00 Series System


Resetting the RCM on AlphaServer 1000 or 2x00
Resetting RCM on AlphaServer 1000 or 2x00

If the escape sequence has been forgotten, you can reset the controller on the managed system to factory settings as follows:

NOTE:  Refer to the KCRCM AlphaServer Remote Console Module Installation and User's Guide for hardware diagrams.

1.	Power down the server and remove panels or covers to access the EISA/ISA bus on which the RCM has been installed.

2.	Unplug all external cables to the RCM and remove the module from the system.

3.	Locate jumper J8 on the RCM.  Move the jumper so that it is sitting on both pins.

4.	Replace any panels or covers so you can power up the system. Press the Halt button and then  power up the system to the P00>>> or >>> console prompt.  Powering up with the J8 jumper in place resets the escape sequence, password, and modem enable states to the factory default.

5.	When the console prompt is displayed, power down the system and move jumper J8 back onto the single pin.

6.	Replace any panels or covers that you removed earlier and power up the system to the console prompt.

7.	Type the default escape sequence to enter RCM command mode:

^]^]rcm

8.	Use the setesc command to reset the escape sequence.  Reset the password and modem enable states in order to enable remote access.


Resetting the RCM on AlphaServer 4100
Resetting RCM on AlphaServer 4100

If the escape sequence has been forgotten, you can reset the controller on the managed system to factory settings as follows:

NOTE:  Refer to the AlphaServer 4100 System Drawer User's Guide for hardware diagrams.

Power down the server and access the server control module, as follows:

1.	Expose the PCI bus card cage.  Remove three Phillips head screws holding the cover in place and slide it off the drawer.  If necessary, remove several PCI and EISA options from the bottom of the PCI card cage until you have enough space to access the server control module.

2.	Unplug the external power supply to the server control module.

Locate the password and option reset jumper.  The jumper number, which is etched on the board, depends on the revision of the server control module.

NOTE:  If the RCM section of the server control module does not have an orange relay, the jumper number is J6.  If the RCM section of the server control module has an orange relay, the jumper number is J7.

3.	Move the jumper so that it is sitting on both pins.

4.	Replace any panels or covers as necessary so you can power up the system. Press the Halt button and then  power up the system to the SRM console prompt.  Powering up with the password and option reset jumper in place resets the escape sequence, password, and modem enable states to the factory default.

5.	When the console prompt is displayed, power down the system and move the password and option reset jumper back onto the single pin.

6.	Replace any PCI or EISA modules you removed and replace the PCI bus card cage cover.

7.	Power up the system to the SRM console prompt and type the default escape sequence to enter RCM command mode:

^]^]RCM

8.	Configure the module as desired.  You must reset the password and modem enable states in order to enable remote access.


Troubleshooting RCM on AlphaServer 1000 or 2x00

Symptom	Possible Cause	Suggested Solution
The terminal  local to the managed server will not communicate with the system or the RCM.	System and terminal baud rate set incorrectly. Cables not correctly installed.	Set the system and terminal baud rates to 9600 baud. Review external cable installation.
RCM will not answer when the modem is called.	Modem cables may be incorrectly installed. RCM remote access is disabled. RCM does not have a valid password set. The terminal local to the managed server is currently in the RCM console firmware. On power-up, the RCM defers initializing the modem for 30 seconds to allow the modem to complete its internal diagnostics and initialization.  Also, modem COM port data traffic is suspended during RCM initialization. Modem may have had power cycled since last being initialized or modem is not set up correctly.	Check modem phone lines and connections. Enable remote access. Set password and enable remote access. Issue a quit command on the local terminal. Wait 30 seconds after powering up the system and RCM before attempting to dial in. Enter enable command from RCM console.
After the system and the RCM are powered up, the COM port seems to hang and then starts working after a few seconds.	This delay is normal behavior.	Wait a few seconds for the COM port to start working.
RCM installation is complete, but system will not power up.	RCM Power Control: is set to DISABLE. Power control cable is not correctly installed.	Enter RCM console and issue the poweron command. Check installation of the power control cable that plugs into J6 of the RCM module.
New password, escape sequence, and modem enable state are forgotten when system and RCM module are powered down.	The password and option reset jumper, J8, is still installed.	After resetting RCM to factory defaults, move J8 so that it is sitting on only one pin.
The remote user sees a "+++" string on the screen.	The modem is confirming whether the modem has really lost carrier.  This occurs when the modem sees an idle time, followed by a "3," followed by a carriage return, with no subsequent traffic.  If the modem is still connected, it will remain so.	This is normal behavior.
The message "unknown command" is displayed when the user enters a carriage return by itself.	The terminal or terminal emulator is including a linefeed character with the carriage return.	Change the terminal or terminal emulator setting so that "new line" is not selected.
Cannot enable modem or modem will not answer.	The modem is not configured correctly to work with the RCM.	Modify the modem initialization and/or answer string.


Troubleshooting RCM on AlphaServer 4100

Symptom	Possible Cause	Suggested Solution
The terminal local to the managed server willl not communicate with the system or the RCM.	System and terminal baud rate set incorrectly. Cables not correctly installed.	Set the system and terminal baud rates to 9600 baud. Review external cable installation.
RCM will not answer when the modem is called.	Modem cables may be incorrectly installed. RCM remote access is disabled. RCM does not have a valid password set. The terminal local to the managed server is currently in the RCM console firmware. On power-up, the RCM defers initializing the modem for 30 seconds to allow the modem to complete its internal diagnostics and initialization. Modem may have had power cycled since last being initialized or modem is not set up correctly.	Check modem phone lines and connections. Enable remote access. Set password and enable remote access. Issue a quit command on the terminal local to the managed server. Wait 30 seconds after powering up the system and RCM before attempting to dial in. Enter enable command from RCM console.
After the system and RCM are powered up, the COM port seems to hang and then starts working after a few seconds.	This delay is normal behavior.	Wait a few seconds for the COM port to start working.
RCM installation is complete, but system will not power up.	RCM Power Control: is set to DISABLE.	Enter RCM console and issue the poweron command.
New password, escape sequence, and modem enable state are forgotten when system and RCM module are powered down.	The password and option reset jumper is still installed.  If the RCM section of the server control module does not have an orange relay, the jumper number is J6.  If it does have an orange relay, the number is J7.	After resetting RCM to factory defaults, move the jumper so that it is sitting on only one pin.
The remote user sees a +++ string on the screen.	The modem is confirming whether the modem has really lost carrier.  This occurs when the modem sees an idle time, followed by a 3, followed by a carriage return, with no subsequent traffic.  If the modem is still connected, it will remain so.	This is normal behavior.
The message unknown command is displayed when the user enters a carriage return by itself.	The terminal or terminal emulator is including a linefeed character with the carriage return.	Change the terminal or terminal emulator setting so that new line is not selected.


Phases of Modem Operation

The RCM is programmed to expect specific responses from the modem during four phases of operation:  Initialization, Ring Detection, Answer, and Hang-Up.

The initialization and answer command strings are stored in the RCM NVRAM. The factory default strings are:

Initialization string:	AT&F0EVS0=0S12=50<cr>
Answer string	ATXA<cr>

NOTE:  All modem commands must be terminated with a <cr> character (0x0d hex).

Initialization

The RCM initializes the modem to the following configuration:

Factory defaults (&F0)

No Echo (E)

Numeric response codes (V)

No Auto Answer (S0=0)

Guard-band = 1 second (S12=50)

Fixed modem-to-KCRCM baud rate

Connect at highest possible reliability and speed

The RCM expects to receive a "0<cr>" (OK) in response to the initialization string.  If it does not, the enable command will fail.

This default initialization string works on a wide variety of modems. If your modem does not configure itself to these parameters, the initialization string will need to be modified.  See Modifying Initialization and Answer Strings.

Ring Detection

The RCM expects to be informed of an in-bound call by the modem signaling the RCM with the string, "2<cr>" (RING).

Answer

When the RCM receives the ring message from the modem, it responds with the answer string. The "X" command modifier used in the default answer string forces the modem to report simple connect, rather than connect at xxxx.  The RCM expects a simple connect message, "1<cr>" (CONNECTED).  If the modem responds with anything else, the RCM forces a hang-up and initializes the modem.

The default answer string is formatted to request the modem to provide only basic status.  If your modem does not provide the basic response, the answer string, and/or initialization string will need to be modified.  See Modifying Initialization and Answer Strings.

After receiving the "connect" status, the modem waits for 6 seconds, and then prompts the user for a password.

Hangup

When the RCM is requested to hang up the modem, it forces the modem into command mode and issues the hangup command to the modem.  This is done by pausing for a minimum of the guard time, sending the modem "+++". When the modem responds with  "0<cr>" (OK), the hang-up command string is sent. The modem should respond  with "3<cr>" (NO CARRIER).  After this interchange, the modem is reinitialized in preparation for the next dial-in session.


KCRCM/Modem Interchange Overview

Action	Data to Modem	Data from Modem
Initialization command	AT&F0EVS0=0S12=50<cr>
Initialization successful		0<cr>
Phone line ringing		2<cr>
RCM answering	ATXA<cr>
Modem successfully connected		1<cr>
Force modem into command mode	<guard_band>+++
Modem in command mode		0<cr>
Hangup	ATH<cr>
Successful hangup		3<cr>


Modifying Initialization and Answer Strings

The initialization and answer strings are stored in the RCM's NVRAM. They come pre-programmed to support a wide selection of modems. In the circumstance where the default initialization and answer strings do not set the modem into the desired mode, the following SRM system console set and show commands are provided to enable the user to define and examine the initialization and answer strings.

To replace the initialization string:

P00>>>set rcm_init " new_init_string"

To replace the answer string:

P00>>>set rcm_answer "new_answer_string"

To display all the RCM user settable strings:

P00>>>show rcm*

rcm_answer 	ATXA

rcm_dialout

rcm_init 	AT&F0EVS0=0S12=50

P00>>>


Initialization and Answer String Substitutions

The following modems have been identified as requiring modified initialization and/or answer strings.

Modem Model	Initialization String	Answer String
KCRCM Defaults	"AT&F0EVS0=0S12=50"	"ATXA"
U.S. Robotics Sportster 28,800 Data/Fax Modem	KCRCM default	"ATX0&B1&A0A"