SUMMARY: Can't get past LOM message to connect to system ("Console is not shared" error)

Ahha, I did not google the *exact* phrase "Console is not shared" before
- I should have done that!



BTW, I found an old Sun Manager mailing list message with the same error
(but no solution mentioned):
http://www.sunmanagers.org/pipermail/sunmanagers/2004-April/029776.html



No SUMMARY in the mailing list archives ... sidebar: I have not been on
this list in a long time, but have people fallen out of the habit of
posting a SUMMARY when they fix something? It is always useful to send
the fix along for others to search for later!



Anyway, I was able to (a) get past the "Console is not shared" message
and (b) determine what is wrong with the system. Thanks to this site
info: http://blogs.sun.com/fintanr/entry/workaround_for_console_is_not



Of course, now I know the drive is faulty ... means a plane trip to that
site unfortunately. Argh! :(



Here is what did the trick (even a "break" was not working - forgot to
mention that before, although I had tried it). Note that I had to wait a
bit till the system actually reset - the "console" command did not work
initially for a bit of time.





lom>break

Console is not shared

lom>break -f

Console is not shared

lom>console

Console is not shared

lom>console -f

Console is not shared

lom>bootmode reset_nvram

lom>reset

lom>

LOM event: +492d+18h2m52s host reset

lom>console

Console is not shared

lom>console

Console is not shared

lom>console

Drive not ready

Can't read disk label.

Can't open disk label package



Can't open boot device



#.

lom>break

ok setenv boot-device disk

ok probe-scsi

Target 1

  Unit 0   Disk     FUJITSU MAN3367M SUN36G 1502

ok boot disk0:a

Boot device: /pci@1f,0/pci@1/scsi@8/disk@0,0:a  File and args:

Drive not ready

Can't read disk label.

Can't open disk label package



Can't open boot device



ok





Anyway, I reset the eeprom parameters to what I needed them to be. But,
of course, the drive is not functional - so plane flight time ...



An interesting sidebar: On a system with an LOM (has the LOMlite
functionality), typing "break" also does the equivalent of a "console"
as well ... on an Advanced LOM (ALOM), it just sends the break, so if
you need to do more than one (depending on where it is in the boot
sequence), you don't have to keep entering a "#." to get back to the
ALOM prompt for the multiple breaks!



Also, if you log out of the LOM, make darn sure that you reset the
password first to something that you can use to get back in. :)



Thanks to the couple of people who offered suggestions.



Z



From: Syed Zaeem Hosain (Syed.Hosain@aeris.net)
Sent: Friday, September 11, 2009 9:46 PM
To: 'sunmanagers@sunmanagers.org'
Subject: Can't get past LOM message to connect to system



Hi, all.



I have a remote system that I am trying to reboot and am having
difficulty. We have a console server that I can get to the serial port
on the system. This allows me to get to the LOM luckily.



But, I am unable to get to the ok> prompt. Here is the screen capture of
some information from the LOM:



lom>version

LOM version:            v3.12

LOM checksum:           6a3e

LOM firmware part#      258-7871-18

Microcontroller:        H8/3437S

LOM firmware build      Feb 21 2002 13:57:04

Configuration rev.      v1.3

lom>show

model                   Netra T1 200

hostname                ns22po1-002-node-106

power-on-decline        off

power-on-delay          off

ip-address              not set

ip-netmask              not set

ip-gateway              not set

bootmode                normal

rsc-security            on

event-reporting         on

Time since last boot:   +492d+6h31m30s



But, when  I try to get to the boot prom, here is what happens:



lom>console

Console is not shared

lom>



Needless to say, attempts to "reset", "poweroff" followed by "poweron"
have not brought the system up. It responds to a "ping", but will not
give me any response to telnet or rlogin. Meaning that the OS is not
really running ... :(



So ... how do I get past this "console is not shared" failure to check
out things from the ok> boot prompt (like disk or other hardware
failures)? A google search has been fruitless, and nothing on
www.sun.com or sunsolve.sun.com appears to be relevant.



Thanks for any help you all can give me here! The system is a plane
flight away, so it is not possible for me to get to it easily.



Z
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers