Sun Fire [TM] SF3800/SF4800/SF4810/SF6800 - E4900/E6900: connecting to a domain shell console which is already in use

Asset ID:	1-71-1415160.1
Update Date:	2012-02-16
Keywords:

Solution Type Technical Instruction Sure

Solution 1415160.1 : Sun Fire [TM] SF3800/SF4800/SF4810/SF6800 - E4900/E6900: connecting to a domain shell console which is already in use

Applies to:

Sun Fire 6800 Server - Version: Not Applicable and later   [Release: N/A and later ]
Sun Fire E6900 Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Fire 4800 Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Fire E4900 Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Fire 3800 Server - Version: Not Applicable and later    [Release: N/A and later]
Information in this document applies to any platform.

Goal

Sometimes, someone or some thing else is connected to the console of an active domain to which console access in needed.

Here we attempt to gain access to the domain A console shell on an E6900 from the master system controller, but someone or something else is already connected.

System Controller 'e6900-sca11-a-sc0':

    Type  0  for Platform Shell

    Type  1  for domain A console
    Type  2  for domain B console
    Type  3  for domain C console
    Type  4  for domain D console

    Input: 1

Connection refused, console busy
Connection closed.

We then try to connect to the domain A console shell from the platform shell of the master SC but have the same result.

System Controller 'e6900-sca11-a-sc0':

    Type  0  for Platform Shell

    Type  1  for domain A console
    Type  2  for domain B console
    Type  3  for domain C console
    Type  4  for domain D console

    Input: 0

Platform Shell

e6900-sca11-a-sc0:SC> console a

Connection refused, console busy
Connection closed.
e6900-sca11-a-sc0:SC>

Solution

The first thing to do is identify what is currently connected to the domain A console shell. Here we see that the console shells for all four domains are in use by trojan.us.oracle.com.

e6900-sca11-a-sc0:SC> connections

ID  Hostname                      Idle Time Connected On   Connected To   
--- ----------------------------- --------- -------------- -------------- 
  3 trojan.us.oracle.com          -         Feb 10 21:31   Domain B       
  4 trojan.us.oracle.com          -         Feb 10 21:31   Domain C       
  5 trojan.us.oracle.com          -         Feb 10 21:31   Domain A       
  8 trojan.us.oracle.com          -         Feb 15 13:51   Domain D       
 10 Localhost                     -         Feb 15 13:52   Platform  

e6900-sca11-a-sc0:SC>

Then, from the platform shell of the master SC, we forcibly disconnect the domain A console shell from trojan.us.oracle.com and again attempt to connect to the domain A console shell from the platform shell of the master SC. This is usually all that is needed. Here, we fail.

e6900-sca11-a-sc0:SC> disconnect 5
e6900-sca11-a-sc0:SC> console a

Connection refused, console busy
Connection closed.
e6900-sca11-a-sc0:SC>

In this case, a script on trojan.us.oracle.com has been re-spawning a console logging session to the domain A console shell, and this is happening faster than we can type.

To usurp the domain A console shell from trojan.us.oracle.com, we need to use the semicolon ScApp command line separator to issue back to back commands. This will give us access to the domain A console shell, currently in use by Solaris, and if desired to the ScApp domain A command line interface and then to OBP and back.

e6900-sca11-a-sc0:SC> connections

ID  Hostname                      Idle Time Connected On   Connected To   
--- ----------------------------- --------- -------------- -------------- 
  3 trojan.us.oracle.com          -         Feb 10 21:31   Domain B       
  4 trojan.us.oracle.com          -         Feb 10 21:31   Domain C       
  8 trojan.us.oracle.com          -         Feb 15 13:51   Domain D       
 10 Localhost                     -         Feb 15 13:52   Platform       
 12 trojan.us.oracle.com          -         Feb 15 13:52   Domain A       

e6900-sca11-a-sc0:SC> disconnect 12;console a

Connected to Domain A


root@e6900-sca11-a-dom-a    [/var/adm]
# 
Domain Shell for Domain A - e6900-sca11-a-dom-a

e6900-sca11-a-sc0:A> break

This will suspend Solaris in domain A.
Do you want to continue? [no] yes

{217} ok 
{217} ok go


root@e6900-sca11-a-dom-a    [/var/adm]
#

References

<NOTE:1011930.1> - Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, and E6900 System Controller Application (ScApp) How To's.
<NOTE:1003150.1> - Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, and E6900: Navigating Between Shells on Sun Fire Mid-range Servers [Video]

Attachments

This solution has no attachment