Accessing console through NET MGMT

[theniteowl]

We have a Solaris server that we can connect to through Lantronics and the Net MGMT port on the server.
When I connect though I get no text back from the server and do not know if it is responding to the connection.
I can enter #. to get to the ALOM login prompt but when I exit again I am back at a flashing cursor but get no response from the console session.

The server is up and running, I can attach to it from an SSH session and our applications are running.
Is this likely some configuration issue redirecting the console output to the Net MGMT port?

It is important that I get this working. The box is in another state and will be used for disaster recovery testing. When we last tried switching the box over to the isolated network for DR we lost contact with it and had a hard time walking someone through switching it back from the local console.

Ideas?

At my age I still learn something new every day, but I forget two others.

 

[KenCunningham]

Hi. Not sure about the Net Management side, but with the serial console, you usually have to 'wake up' the connection using Ctrl Break or (on our laptops) Fn Break. Sometimes it takes quite a time to wake up however!

Some days are diamonds, some days are rocks - make sure most are the former.

 

[theniteowl]

Hmm, tried issuing a break from Putty and came out with this:
Debugging requested; hardware watchdog disabled; reboot to re-enable.
Type 'go' to resume
{1} ok
SC Alert: SC Request to send Break to host.
{1} ok

It seems to actually stop the apps on the server but does not get me to a console prompt. Entering go gets me back to where I was.
When I tried ls to see if I could get a directory listing I received the message
Not at a device tree node. Use 'dev <device-pathname>'.
{1} ok
SC Alert: SC Request to send Break to host.


At my age I still learn something new every day, but I forget two others.

 

[KenCunningham]

Hmm. The ok prompt is where you would generally type boot to reboot the server to a login prompt.

Some days are diamonds, some days are rocks - make sure most are the former.

 

[theniteowl]

The server is already up and running. I can SSH into it fine and access the application that runs on it.
I think the OK prompt above is some kind of debug mode.

The only thing I can think of is that something is not configured for this since Lantronics is using the NET MGT port rather than the SER MGT port to get to the box and that the console is not setup to redirect for that port.


At my age I still learn something new every day, but I forget two others.

 

[KenCunningham]

You're probably right - sorry, as I said, I've no experience of the NET MGT stuff. I guess you get back from where you came with 'go' as above.

Some days are diamonds, some days are rocks - make sure most are the former.

 

[SamBones]

I think the OK prompt above is some kind of debug mode.

The ok prompt it the Open Boot PROM (OBP) prompt. It is the low level PROM level control of the machine. You got there by sending a Break on the console. It suspended the OS and took you to the OBP prompt ("ok").

If you want to get back to the OS, just enter "go". If you want to log onto the OS at the console, type "go", then hit enter a couple times to see if you get a login prompt. You should be at the console if you saw the OBP prompt when sending a Break.

More on OBP commands here...

http://it.toolbox.com/wiki/index.php/Open_Boot_PROM_-_OK_Prompt

 

[theniteowl]

It never reaches a logon prompt except when I enter ALOM.
I am not sure if the console is not directed to the NET MGT port or if the keyboard is working but not getting any display data back.


At my age I still learn something new every day, but I forget two others.