Editing Scanco Administration (section)

====Crash of XtremeCT II workstation computer====

For a non-responsive monitor and/or a mouse and/or a keyboard of the XtremeCT II workstation (sometimes caused by a lost of connection to server, or an internet outage):

:*1. The first thing to do is to check system logs for any indication of the cause of the issue, if you have the "Administrator" user privilege.
:*2. The next thing to do is to soft-reboot by remote-login and using command line to reboot the workstation, if you have the "system" user privilege.
:*3. If no success, try hard-reboot by pressing the power button as indicated below.
:*4. If no success, try hard-reboot by unplugging both power cords as indicated below.
:*5. If still no success, contact Scanco immediately.
:*6. The last thing to do is to record the issue and any possible reasons.

1.  Checking system logs:
 
:*1) Remotely log into the iLO (the management console of the workstation) using SSH as user "Administrator" with the system password. 
Both user/pw are case sensitive. For XtremeCT II workstation (James) it is SSH to 10.148.64.231. For others, consult the network diagram. 

A trick: This connection only succeeds through a MAC or PC (via putty) direct login, not through an OpenVMS or Scanco system.
   $ ssh -l Administrator 10.148.64.231
:*2) Then you get to a   MP>   prompt here:

   MP MAIN MENU:
         CO: Console
        VFP: Virtual Front Panel
         CM: Command Menu
         CL: Console Log
         SL: Show Event Logs
         HE: Main Help Menu
          X: Exit Connection
   [sc3401-mp]</> hpiLO->

:*3) Type in 'SL' to show event logs, then you could choose 'E' for system event:

   [sc3401-mp]</> hpiLO-> SL
     Event Log Viewer Menu:
       Log Name            Entries    % Full      Latest Timestamped Entry
  -------------------------------------------------------------------------------
   E - System Event          1661       58 %        13 Sep 2018 11:17:43
   F - Forward Progress     20000      100 %        13 Sep 2018 11:17:43
   I - iLO Event              500      100 %        18 Sep 2018 07:46:42
   C - Clear SEL and FPL
   L - Live Events

   Enter menu item or [Ctrl-B] to Quit: E
       Log Name            Entries    % Full      Latest Timestamped Entry
  -------------------------------------------------------------------------------
   E - System Event          1661       58 %        13 Sep 2018 11:17:43
     Event Log Navigation Help:
   +       View next block     (forward in time,  e.g. from 3 to 4)
   -       View previous block (backward in time, e.g. from 3 to 2)
   <CR>    Continue to the next or previous block
   D       Dump the entire log
   F       First entry
   L       Last entry
   J       Jump to entry number
   H       View mode configuration - Hex
   K       View mode configuration - Keyword
   T       View mode configuration - Text
   A       Alert Level Filter options
   U       Alert Level Unfiltered
   ?       Display this Help menu
   Q       Quit and return to the Event Log Viewer Menu
   Ctrl-B  Exit command, and return to the MP Main Menu

:*4) From here you can use -  and  +  to go through the log history back and forth. Not all logs do make a lot of sense though, as they are mainly meant for HPE engineers. 
:*5) When finished, use  CTRL + b to get back to the main MP> prompt.
:*6) Use  MP> co   to get to the console, where you see at what stage the booting process is, in case it does not boot properly.
:*7) When finished, use  CTRL + b to get back to the main MP> prompt.
:*8) Use  MP> x   to end the connection.

2. Soft-reboot by remote login:

If a workstation becomes unresponsive, it may be possible to shut it down remotely from another workstation or personal computer, which is preferable over doing a hard-reboot.  These instructions were provided by Mark Blanchard.

:*2.A) Remote shutdown from another micro-ct workstation.  MAY NOT WORK FOR CLUSTER SERVER

Login as the system user.
   $ set host 0
   user:  system
   password:

Start the system manager.
   $ mcr sysman

Set the environment to the workstation to be shutdown (e.g., thomas) using its node name (e.g., sc3309).
   SYSMAN>< set env/node=sc3309

Issue the shutdown command.  Add a time delay, e.g., 5 min, if you want to give users time to disconnect and the automatic reboot flag if you want to restart.
   SYSMAN> shutdown node /min=5 /automatic_reboot

You need to remain logged into the session running the shutdown until the other node has been shutdown completely!!!

:*2.B) Remote shutdown from a personal computer.
Begin a remote session to the workstation and login as the system user.

Create a detached terminal.
   $ create/terminal/detach
 
On the PC, port 6000 needs to be accessible to the micro-ct workstation and in the X-server's configuration (e.g., in file X0.hosts for Xming).  

Issue the shutdown command.
   $ shutdown

3. Hard-reboot by power button:

:*1) Hold the power button until it turns yellow.
:*2) Wait a minutes or two, then press the power button only once and shortly. You will not see anything for a while. Pressing the power button again during this time will turn off the workstation again !
:*3) After about 10~15 min, the workstation would boot up properly. 
  
4. Hard-reboot by unplugging both power cords:

:*1) Hard-reboot by unplugging both the power cords. This will reset the console and controllers.
:*2) Wait for 5~10 minutes, then press the power button only once and shortly. You will not see anything for a while. Pressing the power button again during this time will turn off the workstation again !
:*3) After about 10~15 min, the workstation would boot up properly.


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]