Here's a link to the pinouts, in case they are wrong...
Here are some notes from a class I attended long ago...
The terminal input Command (tip)
The tip hardwire command establishes a full-duplex terminal connection to a remote host. It provides a way to use a serial input/output device for troubleshooting purposes (such as viewing POST) when an ASCII terminal is not available.
A. The tip command establishes a connection to a remote host, either through a modem or null modem cable. This technique of troubleshooting is valuable in reviewing a remote system’s POST, boot, and error messages when you do not have a dumb terminal.
B. The faulty system must have diagnostic mode enabled. You can do this by typing diag-switch?=true command or by pressing the stop-d key sequence.
Input/output must be directed to ttya. This is achieved in one of several ways:
A. Pulling the keyboard cable from the system
B. Pressing stop-f key sequence
C. Typing setenv output-device ttya at the ok prompt.
A null modem cable is connected from the faulty system to the healthy system. The pin configurations for creating your own null modem cable are listed on the web and in Sun Field Engineer Handbook.
HANDOUT of PINOUTS
Website
serial-pinouts/
The healthy system (host) must be booted and running a graphical user interface such as CDE. The tip hardwire command is enabled in a shell or terminal window.
At the ok prompt of the bad system (client) enter printenv command with the ttya option to determine how serial port A on your system is configured:
{1} ok printenv ttya-mode
ttya-mode = 9600,8,n,1,-
Serial Values are as follows:
A. Baud rate = 9600
B. Data bits = 8
C. Parity = none
D. Stop bit = 1
E. Handshaking = -(none)
If the settings are not as shown as in the list above, use the setenv command to change the NVRAM properties for serial port A
{1} ok setenv ttya-mode ttya 9600,8,n,1,-
Below is a list of tip commands:
{1} ok ~?
~! shell
~< receive file from remote host
~> send file to remote host
~t take file from remote UNIX
~p put file to remote UNIX
~| pipe remote file
~C connect program to remote host
~c change directory
~. exit from tip
~^D exit from tip
~$ pipe local command to remote host
~^Y suspend tip (local only)
~^Z suspend tip (local+remote)
~s set variable
~? get this summary
~# send break
Never exit a tip window by quitting the shell tool window or by halting the processes
(this can hang the tip session). Do not press Stop-A key sequence to abort the faulty system because the Stop-A key sequence aborts the healthy system instead (brings system down to the ok prompt).
For more information on tip do a man tip from the Solaris Operating Environment.
Good luck...
Burt
