I've a SunFire v210 in our lab for which we require a console
connection (no video console).  I see the RJ45 and DB9 connections on
the back.   Tried hooking up a Wyse terminal, 9600,8,N,1, and wasn't
able to get a prompt.  "eeprom" shows:

ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttyb-mode=9600,8,n,1,-
ttya-mode=9600,8,n,1,-
output-device=ttya
input-device=ttya

It's been such a long time since I've worked with Solaris (!)... I
reviewed some of the online docs on sun.com, and wasn't able to get to
what I needed.

I want to determine if the serial console is enabled (which I believe
it is), and I see the comm parameters (above).

Seems like I should be able to serial in from a Linux system to the DB9
port and get a console, using minicom. ?

Can someone point me in the right direction.


Thanks!

On 8 Jan 2007 10:04:58 -0800
"forrie@gmail.com" <forrie@gmail.com> wrote:

> I've a SunFire v210 in our lab for which we require a console
> connection (no video console).  I see the RJ45 and DB9 connections on
> the back.   Tried hooking up a Wyse terminal, 9600,8,N,1, and wasn't
> able to get a prompt.  "eeprom" shows:
>=20
> ttyb-rts-dtr-off=3Dfalse
> ttyb-ignore-cd=3Dtrue
> ttya-rts-dtr-off=3Dfalse
> ttya-ignore-cd=3Dtrue
> ttyb-mode=3D9600,8,n,1,-
> ttya-mode=3D9600,8,n,1,-
> output-device=3Dttya
> input-device=3Dttya
>=20
> It's been such a long time since I've worked with Solaris (!)... I
> reviewed some of the online docs on sun.com, and wasn't able to get to
> what I needed.
>=20
> I want to determine if the serial console is enabled (which I believe
> it is), and I see the comm parameters (above).
>=20
> Seems like I should be able to serial in from a Linux system to the
> DB9 port and get a console, using minicom. ?
>=20
> Can someone point me in the right direction.
>=20
>=20
> Thanks!
>=20
Hi
That's the lights out management interface, have a look here;

http://en.wikipedia.org/wiki/LOM_port

--=20
Cheers Malcolm =C2=B0=C2=BF=C2=B0 (Linux Counter #276890)
SLED 10.0 x86_64 Kernel 2.6.16.27-0.6-smp
up 1 day 19:38, 2 users, load average: 0.16, 0.15, 0.05

I see only a "net mgmt" port, and then the RJ45 and standard serial
ports... no LOM.  Unless I'm mistaken about something.

The impression I got from the Sun docs was that LOM modifcation or
whatever requires the system brought down, which I can't do (production
system).   I would "think" that the console is, by default, set to the
serial port.  The eeprom settings seem to suggest that, but perhaps the
SAF has since been modified and ttymon isn't listening.   I'm not sure
;-)


Thanks,

Forrest


Malcolm wrote:
>
> Hi
> That's the lights out management interface, have a look here;
>
> http://en.wikipedia.org/wiki/LOM_port
>
> --
> Cheers Malcolm =B0=BF=B0 (Linux Counter #276890)
> SLED 10.0 x86_64 Kernel 2.6.16.27-0.6-smp
> up 1 day 19:38, 2 users, load average: 0.16, 0.15, 0.05

In <1168285352.423286.291970@51g2000cwl.googlegroups.com> "forrie@gmail.com" <forrie@gmail.com> writes:

>I see only a "net mgmt" port, and then the RJ45 and standard serial
>ports... no LOM.  Unless I'm mistaken about something.

The RJ45 is also a management port, serial in this case.  It's
connected to the console by default, but you can escape from that
to the ALOM.

>The impression I got from the Sun docs was that LOM modifcation or
>whatever requires the system brought down, which I can't do (production
>system).   I would "think" that the console is, by default, set to the
>serial port.  The eeprom settings seem to suggest that, but perhaps the
>SAF has since been modified and ttymon isn't listening.   I'm not sure

You must be looking at RSC documentation.  ALOM is completely
different.  No, the serial port is not the console.  You don't need to
change any eeprom settings.  The ALOM can be used and configured
without affecting the running system.

-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

Hey Gary, long time no see.

I just tried hooking up the RJ45 to the Serial *and* Net Mgmt ports,
with no luck.  I'm pretty sure the COMMs parameters on the Wyse are
correct.

If I remember correctly, the SAF is responsible for spawning the getty
on the port... in the inittab, I only see this:

co:234:respawn:/usr/lib/saf/ttymon -g -h -p "`uname -n` console login:
" -T vt100 -d /dev/console -l console -m ldterm,ttcompat

/dev/console points to:

crw--w----   1 root     tty        0,  0 Jan  8 15:40
/devices/pseudo/cn@0:console

I have some serial cables here, but they aren't marked null-modem, so
perhaps those won't work with a system-to-system (via minicom)
connection.

Are there other settings I can poll to see what the console is set to,
etc.

Thanks!



Gary Mills wrote:
> In <1168285352.423286.291970@51g2000cwl.googlegroups.com> "forrie@gmail.com" <forrie@gmail.com> writes:
>
> >I see only a "net mgmt" port, and then the RJ45 and standard serial
> >ports... no LOM.  Unless I'm mistaken about something.
>
> The RJ45 is also a management port, serial in this case.  It's
> connected to the console by default, but you can escape from that
> to the ALOM.
>
> >The impression I got from the Sun docs was that LOM modifcation or
> >whatever requires the system brought down, which I can't do (production
> >system).   I would "think" that the console is, by default, set to the
> >serial port.  The eeprom settings seem to suggest that, but perhaps the
> >SAF has since been modified and ttymon isn't listening.   I'm not sure
>
> You must be looking at RSC documentation.  ALOM is completely
> different.  No, the serial port is not the console.  You don't need to
> change any eeprom settings.  The ALOM can be used and configured
> without affecting the running system.
>
> --
> -Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

forrie@gmail.com wrote:

> Hey Gary, long time no see.
> 
> I just tried hooking up the RJ45 to the Serial *and* Net Mgmt ports,
> with no luck.  I'm pretty sure the COMMs parameters on the Wyse are
> correct.
> 
> If I remember correctly, the SAF is responsible for spawning the getty
> on the port... in the inittab, I only see this:
> 
> co:234:respawn:/usr/lib/saf/ttymon -g -h -p "`uname -n` console login:
> " -T vt100 -d /dev/console -l console -m ldterm,ttcompat
> 
> /dev/console points to:
> 
> crw--w----   1 root     tty        0,  0 Jan  8 15:40
> /devices/pseudo/cn@0:console
> 
> I have some serial cables here, but they aren't marked null-modem, so
> perhaps those won't work with a system-to-system (via minicom)
> connection.
> 
> Are there other settings I can poll to see what the console is set to,
> etc.
> 
> Thanks!
> 
> 
> 
> Gary Mills wrote:
>> In <1168285352.423286.291970@51g2000cwl.googlegroups.com>
>> "forrie@gmail.com" <forrie@gmail.com> writes:
>>
>> >I see only a "net mgmt" port, and then the RJ45 and standard serial
>> >ports... no LOM.  Unless I'm mistaken about something.
>>
>> The RJ45 is also a management port, serial in this case.  It's
>> connected to the console by default, but you can escape from that
>> to the ALOM.
>>
>> >The impression I got from the Sun docs was that LOM modifcation or
>> >whatever requires the system brought down, which I can't do (production
>> >system).   I would "think" that the console is, by default, set to the
>> >serial port.  The eeprom settings seem to suggest that, but perhaps the
>> >SAF has since been modified and ttymon isn't listening.   I'm not sure
>>
>> You must be looking at RSC documentation.  ALOM is completely
>> different.  No, the serial port is not the console.  You don't need to
>> change any eeprom settings.  The ALOM can be used and configured
>> without affecting the running system.
>>
>> --
>> -Gary Mills-    -Unix Support-    -U of M Academic Computing and
>> Networking-
Hi
On the documentation cdrom look at 816-4825-11.PDF page 25 for the
pinout details RJ-45 to DB9 or DB25 and ALOMHELP.PDF for the rest of
the information.

-- 
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10.0 x86_64 Kernel 2.6.16.27-0.6-smp
up 1 day 21:31, 2 users, load average: 0.36, 0.24, 0.12

forrie@gmail.com wrote:
> I've a SunFire v210 in our lab for which we require a console
> connection (no video console).  I see the RJ45 and DB9 connections on
> the back.   Tried hooking up a Wyse terminal, 9600,8,N,1, and wasn't
> able to get a prompt.  "eeprom" shows:
>
> ttyb-rts-dtr-off=false
> ttyb-ignore-cd=true
> ttya-rts-dtr-off=false
> ttya-ignore-cd=true
> ttyb-mode=9600,8,n,1,-
> ttya-mode=9600,8,n,1,-
> output-device=ttya
> input-device=ttya

Your parameters are fine.  We have v240 which is very close to yours. I
use RJ45/DB9 in SERIAL MGT. I used both HyperTerminal (COM1 port
properties (Restore Defaults)) and TeraTerm. They all work fine.

What is your ALOM version? -- /usr/platform/`uname -i`/sbin/scadm
version
Victor

In <1168288960.255820.234320@q40g2000cwq.googlegroups.com> "forrie@gmail.com" <forrie@gmail.com> writes:

>I just tried hooking up the RJ45 to the Serial *and* Net Mgmt ports,
>with no luck.  I'm pretty sure the COMMs parameters on the Wyse are
>correct.

The network management port is ethernet.  The serial management port
is serial, using the Cisco cable format.  If you have a cable that
works on a Cisco router, it will work on the V210/V240.

-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

On 2007-01-08, Gary Mills <mills@cc.umanitoba.ca> wrote:
> In <1168288960.255820.234320@q40g2000cwq.googlegroups.com> "forrie@gmail.com" <forrie@gmail.com> writes:
>
>>I just tried hooking up the RJ45 to the Serial *and* Net Mgmt ports,
>>with no luck.  I'm pretty sure the COMMs parameters on the Wyse are
>>correct.
>
> The network management port is ethernet.  The serial management port
> is serial, using the Cisco cable format.  If you have a cable that
> works on a Cisco router, it will work on the V210/V240.

And if you still see nothing, hit #. to break to the SC.

Ceri
-- 
That must be wonderful!  I don't understand it at all.
                                                  -- Moliere

forrie@gmail.com <forrie@gmail.com> wrote:
> Hey Gary, long time no see.

> I just tried hooking up the RJ45 to the Serial *and* Net Mgmt ports,
> with no luck.  I'm pretty sure the COMMs parameters on the Wyse are
> correct.

Do you have a null modem connector in there?  Both a PC running netcom
and a physical terminal are wired DTE, same as the sun.  It'll require a
null modem.

Even if the "console" wasn't working, you should still be able to
communicate with the LOM.

The 'Net Mgmt' port is ethernet, not serial.  

> If I remember correctly, the SAF is responsible for spawning the getty
> on the port... in the inittab, I only see this:

That is incorrect.  SAC/SAF stuff is usually used for additional gettys
on serial ports, not for the console.

> co:234:respawn:/usr/lib/saf/ttymon -g -h -p "`uname -n` console login:
> " -T vt100 -d /dev/console -l console -m ldterm,ttcompat

Right.  That's the console invocation.

> /dev/console points to:

> crw--w----   1 root     tty        0,  0 Jan  8 15:40
> /devices/pseudo/cn@0:console

Which is a device managed by the OBP.  It can direct that where it
wants, but on LOM hardware, it probably goes to the LOM.

> I have some serial cables here, but they aren't marked null-modem, so
> perhaps those won't work with a system-to-system (via minicom)
> connection.

That would be my first guess.

> Are there other settings I can poll to see what the console is set to,
> etc.

It's unlikely to be set to anything other than 9600 8/N/1.  I don't know
how to poll LOM settings from the host.

Here's the ALOM doc.
http://www.sun.com/products-n-solutions/hardware/docs/pdf/819-2445-11.pdf

Also the v210 admin guide, with sections 1.4 and 3.4 showing how you
command the OS from the ALOM port.

http://www.sun.com/products-n-solutions/hardware/docs/pdf/819-4208-10.pdf

-- 
Darren Dunham                                           ddunham@taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

I had the fortunate opportunity of opening a new Sunfire box today -
where I promptly took the adapter and cable and tested it against the
(old) Wyse terminal... and walla.

Turns out the cable/adapter or whatever I had was wrong.

Now:  I'm at an "ok" prompt, and I can't remember how to get out of
that and back to the "login" prompt....


Thanks!

Oh duh.  "boot".

However: if the system goes down every time you plug in the serial
cable -- question is, would it be more beneficial to connect the serial
cable to another system to have a permanent connection?  Obviously,
when we need to get to the console prompt, we don't want the system
coming down each time.


Thanks.

I found this reference on the Sun forums:

If you SHUT OFF YOUR TERMINAL, while it is connected to a running Sun
machine, you send a "break" signal via the serial line and the Sun will
jump back into the OK prompt, halting the OS. This can cause
considerable confusion.

This is what I'm referring to... I have our system running now, but if
I disconnect the Wyse terminal, it sounds like the system will halt
again.  Not what we want to happen, of course.

I'm ordering some null modem cables for a direct connection from ttyb
to another system - but that won't be the "console" proper in the case
of a single-user mode scenario.   But it will be a login,
none-the-less.


Thanks.

forrie@gmail.com wrote:

> I had the fortunate opportunity of opening a new Sunfire box today -
> where I promptly took the adapter and cable and tested it against the
> (old) Wyse terminal... and walla.
> 
> Turns out the cable/adapter or whatever I had was wrong.
> 
> Now:  I'm at an "ok" prompt, and I can't remember how to get out of
> that and back to the "login" prompt....
> 
> 
> Thanks!
> 

continue

You may also choose to use NET port if you do not want to disable the
key "Break".

Victor

forrie@gmail.com <forrie@gmail.com> wrote:
> Oh duh.  "boot".

> However: if the system goes down every time you plug in the serial
> cable -- question is, would it be more beneficial to connect the serial
> cable to another system to have a permanent connection?  Obviously,
> when we need to get to the console prompt, we don't want the system
> coming down each time.

Assuming you're running Solaris, see the kbd man page.  You can set an
alternate break signal that will not be generated by connecting or
powering off equipment.

-- 
Darren Dunham                                           ddunham@taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

forrie@gmail.com wrote:
> I found this reference on the Sun forums:
> 
> If you SHUT OFF YOUR TERMINAL, while it is connected to a running Sun
> machine, you send a "break" signal via the serial line and the Sun will
> jump back into the OK prompt, halting the OS. This can cause
> considerable confusion.
> 
> This is what I'm referring to... I have our system running now, but if
> I disconnect the Wyse terminal, it sounds like the system will halt
> again.  Not what we want to happen, of course.
> 
> I'm ordering some null modem cables for a direct connection from ttyb
> to another system - but that won't be the "console" proper in the case
> of a single-user mode scenario.   But it will be a login,
> none-the-less.
> 
> 
> Thanks.
> 

Typing 'go' at the ok prompt will resume operation.  If you need to 
prevent the system from halting when disconnecting (and who wouldn't!), 
change /etc/default/kbd KEYBOARD_ABORT to reflect what you want (man kbd).

Kevin