Very Computer

I have myself in a predicament.

I have an Ultra 60 with Solaris 9 that has been up and happy for many
months.  I physically attached a SCSI external tape drive, bounced it,
and now I can not connect to it.  I do not have access to it via its
framebuffer.  So I am trying to hook up using a Win box and cross-over
cat-5 cable.

I know the ip address it thinks it was before I restarted the machine.
I used to be able to ssh or telnet to it.  Let's call the ip address:

65.112.8.23

After setting my Win box to 65.112.8.24 and linking the cross-over
cable, I can successfully ping the Sun box at the address above.  But if
I try to telnet or ssh to 65.112.8.23, I get:

"Connecting To 65.112.8.23...Could not open connection to the host, on
port 22: Connect failed."

I have tried various ports, and no love....same error message, but with
a different port number at the end.  What else could I try in order to
get a shell into this box and fix the network configuration?

Thanks,
Rob

Sounds like the machine isn't fully up and running daemons yet.

Your best option is to serial console in and watch the boot
sequence. Sounds like you don't have a keyboard plugged in, but if you
do, unplug it to make sure the console output comes out ttya instead
of on the frame buffer. Should be easy to fix after you are in via
serial console.

Could someone give me a hand with that process?  I have gone through a
Serial Management port on a v210, Netra, etc, before, but not an Ultra.
  Here's what I have tried:

0) disconnected the keyboard

1) Took an RJ-45 cable I have used before to connect to a v210

2) On one end I have a 9-pin serial converter and connect to my Win box

3) The other end has a 25-pin converter (I received with a v210, with
only 7 pins in use) and connect that to the "A" serial port of my Ultra60

4) I fired up a HyperTerminal session in Windows and (guessing here) used:

COM 1 (which I know to be my 9-pin on the Win box)
Bits Per Second = 9600
Data Bits = 8
Parity = none
Stop Bit = 1
Flow Control = Xon/Xoff

I was hoping for some kind of reponse at this point, but nothing.  I
hard-booted the Ultra60 as a shot in the dark, nothing.  Tried serial
port "B" on the Ultra60, nothing.

I also tried, on the Ultra60 side, to go in via the ethernet jack.  At
that point on my HyperTerminal I could see the charaters I was typing,
but no response from the Ultra60.

There is something I am not doing right...
Rob

Use a standard PC to modem cable with a Radio Shack 26-264 Null Modem
between COM1 on your PC to TTY-A on the U60.  Or construct a null modem
cable - see Google.

Robert Mazur wrote on 2005-09-16 21:52:

Do you have another Ultra around? I use Ultra 10s and do this all the
time: Connect the serial ports between the Ultras with a *null-modem*
cable, and then use "tip console" to connect (I added the console entry
to /etc/remote, this is a copy of the hardwire entry, I just changed the
port from /dev/term/b to /dev/term/a). After disconnecting the keyboard
and rebooting the target machine, the serial port will be used.

I have V120 as well, for this one I use tip as described but this time
with the cable that comes with the V120, which seems to be special.
Maybe you just have a cable problem? Try a regular null-modem cable.

--
- Erlend Leganger