|
|
|
|
|
Frequently, remote access is used for troubleshooting purposes. If the IR system is experiencing problems, not all system functions may be available. The table that follows summarizes the effects of system states.
System states and causes |
System actions |
System availability |
Normal
|
SunVTS software monitors events and executes actions. |
Modem is available for platform use, for both placing and receiving calls. SunVTS responds to commands that reach SunVTS from the normal platform operating system. |
Panic Dialout
|
SunVTS:
|
Reflects system status before receipt of panic dialout command. Connection to a remote session is maintained. |
Built-in self-test
|
SunVTS performs a self-test and goes into the normal, impaired, or disabled state depending on the results. |
Reflects the system status after the self-test. |
Impaired Non-serious hardware error detected by the built in self-test. |
SunVTS operates to the fullest extent possible. |
Reflects the functions available in the impaired state. |
Disabled Self-test detected serious hardware error (severe or fatal problem with the processor complex or a problem that could degrade the host platform). |
SunVTS and its modem are shut down. |
No functions are available. |
Authentication Remote caller connects to RSC. |
SunVTS controls the modem and issues a login and password prompts. |
Reflects the current system status. |
Note:
Independent state does not apply to SunVTS. SunVTS does not run separately from the Sun Blade 150 operating system.
The platform performs a self-test of events when the platform is started or reset.
Remote users can manage panic dialout. They can:
Panic dialout messages queue, and the user is notified that they are being queued. Panic dialout is re-enabled when the remote session ends. Queued panic dialout messages are released at that time.
