IMPORTANT: Raritan Serial Console (RSC) sessions are affected by the SX II Idle Timeout.
If you have not changed the SX II Idle Timeout setting from the default, your RSC session could be closed automatically if it exceeds the Idle Timeout period.
Change the defaultIdle Timeout setting and then launch the RSC. See Login Limitations for details on changing the Idle Timeout setting.
Access Emulator Options
Select the Emulator drop-down menu to display a list of options.
Settings
Note: An Administrator can set Terminal emulation settings using Setup > Port Configuration.
Choose Emulator > Settings. The Settings screen displays the General tab with the default settings.
The Main Menu Shortcut default is None; accept this, or choose one of the following from the Main Menu Shortcut drop-down menu:
F10
Alt
The Show Confirmation Dialog on Exit checkbox is selected by default, but you can deselect it based on preference.
The Terminal Size default is selected, or you can choose a different size from the drop-down menu.
The Backspace Sends default is ASCII DEL, or you can choose Control-H from the Backspace Sends drop-down menu.
The History Buffer Size default is 75. Type a value or use the arrows to change the buffer size.
The Cursor type default is Block Cursor, or you can select the Line Cursor radio button.
Click OK.
Display Settings
Choose Emulator > Settings and click the Display tab.
Click Default to accept the Default settings, and then click Ok to close the Display Settings window. To change the settings, follow these steps:
The Terminal Font Properties default is Arial, or you can choose a font from the Terminal Font Properties scrolling list.
Click the GUI Font Properties tab.
The default font property is Monospace, or you can choose a font from the GUI Font Properties scrolling list.
Note: For Simplified Chinese characters, RSC supports EUC-CN encoding system.
Choose the following from their respective drop-down menus:
Foreground Color
Background Color
Choose one of the following from the Encoding drop-down menu:
US-ASCII
ISO-8859-1
ISO-8859-15
UTF-8
Shift-JIS
EUC-CN
EUC-JP
EUC-KR
Choose one of the following from the Language drop-down menu:
English
Japanese
Korean
Chinese
Bulgarian
Click Ok to close the Display Settings window. If you changed the Language setting, the RSC changes to that language when the Display Settings window is closed.
Note: In case of unrecognized characters or blurry screens that might appear when RSC is launched, due to localization support, try changing the font to Courier New.
Get History
History information can be useful when debugging, troubleshooting, or administering a target device. The Get History feature:
Allows you to view the recent history of console sessions by displaying the console messages to and from the target device.
Displays up to 512KB of recent console message history. This allows a user to see target device events over time.
When the size limit is reached, the text wraps, overwriting the oldest data with the newest.
Notes: History data is displayed only to the user who requested the history.
To view the Session History, choose Emulator > Get History.
Clear History
To clear the history, choose Emulator > Clear History.
Get Write Access
Only users with permissions to the port get Write Access. The user with Write Access can send commands to the target device. Write Access can be transferred among users working in the RSC via the Get Write Access command.
To enable Write Access, choose Emulator > Click Get Write Access.
You now have Write Access to the target device.
When another user assumes Write Access from you:
The RSC displays a red block icon before Write Access in the status bar.
A message appears to the user who currently has Write Access, alerting that user that another user has taken over access to the console.
Get Write Lock
Write lock prevents other users from taking the write access while you are using it.
To get write lock, choose Emulator > Get Write Lock.
If Get Write Lock is not available, a request rejected message appears.
Write Unlock
To get Write Unlock, choose Emulator > Write Unlock.
Send Break
Some target systems such as Sun Solaris servers require the transmission of a null character (Break) to generate the OK prompt. This is equivalent to issuing a STOP-A from the Sun keyboard.
Only users with Write Access privileges can send a break.
To send an intentional “break” to a Sun Solaris server:
Verify that you have Write Access. If not, follow the instructions in the previous section to obtain write access.