System Controller on new server

[iain99]

Hi I need help. Just got a new Sun V245 box and am trying to get into the system controller on the box but have not succeeded.
I have tried a connection from a terminal server without any luck, I then tried sticking a Sun Graphics console into the server and again nothing when power leads added. I have also tried a "tip hardwire" from another server but again I only get the "connected" message and no other response.
I'd appreciate any pointers, am I missing somethin real basic?
Thanks.
Iain

 

[dandan123]

If the V245 is similar to the V240 then you would have to get the console (serial port) working by using tip or connecting a terminal or terminal server and get it going.

Once you have that you can type #. to get into the alom or sc.

Terminal server connection should work fine, check the cable connecting the serial port to the terminal server, some cables have pins 2 and 3 reversed.

 

[dandan123]

The 245 and 240 should be very similar, so based on my 240 knowledge, there are two management ports - serial and ethernet, have you perhaps connected your serial connection to the ethernet or network port ?

Both ports can be used as console but the network port needs to be configured with an ip address etc so you would have to use the serial port to get in and then configure the network port.

They are marked serial mgmt and network mgmt or something similar.

 

[iain99]

Doh. Thanks for the response. Still no luck - silly question but what type of cables should I be using then?
Iain

 

[KenCunningham]

Hi Iain. You'll probably need a null-modem cable to connect via hyperterminal.

 

[iain99]

Thanks - the server doesnt have ports that would take a null modem cable....stumped. Why wouldnt a graphics console just work? Dont understand.

 

[dandan123]

You have to use a regular ethernet cable and plug that into your serial mgmt port, then plug that into the terminal server, most terminal servers take this kind of cable, if not you would need an adapter on the terminal server side, where I work the networking guys take care of the terminal server side.

 

[iain99]

Those are the kind of cables I am using but no success.
Thinking it might be a dead box or some problem with it...
Thanks for your help.

Iain

 

[dandan123]

Regading cables and pinouts this site has great info -

http://www.sunhelp.org/unix-serial-port-resources/serial-pinouts/

 

[coffeysm]

If you can get a hold of your network guys ask them for a cable they use to console into the switches. Also, make sure your /etc/remote file is setup correctly. If you are trying to use the tip command. The graphics card probably is not working because the OBP is set for input/output to goto the serial port.

 

[tuka]

Document Audience: SPECTRUM
Document ID: 72108 This is also used for the V245--see sunsolve
Title: How To connect to LOM/ALOM SERIAL Management Port
Copyright Notice: Copyright © 2006 Sun Microsystems, Inc. All Rights Reserved
Update Date: Fri Nov 24 00:00:00 MST 2006
Products: Sun Fire V240 Server, Sun Fire V210 Server, Netra 440 Server, Netra 440 (AC) Server, Netra 240 Server, Netra 240 Server (AC), Sun Fire V440R Server, Sun Fire V440 Server, Sun Fire V250 Server, Sun Fire V120 Server, Sun Fire V100 Server, Sun Fire V245 Server, Sun Fire V215 Server
Technical Areas: Serial Port, Input Device

--------------------------------------------------------------------------------


--------------------------------------------------------------------------------

Keyword(s):ALOM, LOM, tip, v100, v120, v210, v240, V250, V440, console, hardwire

Description: Top

This InfoDoc will explain how to set up a connection to the LOM/ALOM SERIAL
MGT port on a SunFire[TM] V100/V120/V210/V240/V250/V440 or Netra[TM] 240/440
system.

Document Body: Top

The hardware set up involves connecting a system running Solaris[TM] to the
SERIAL MGT port(RJ45) via the running system's serial port A or B or Microsoft
Windows system via its serial port.

1- For the Solaris[TM] system, the /etc/remote file on the running system will
have to be checked for the correct settings.The example below shows the correct
settings.The lines of interest are the "hardwire" and "hardwire-a" lines.


# more /etc/remote
# The next 17 lines are for the PCMCIA serial/modem cards.
#
pc0:\
:dv=/dev/cua/pc0:br#38400:el=^C^S^Q^U^D:ie=%$e=^D:nt:hf:
pc1:\
:dv=/dev/cua/pc1:br#38400:el=^C^S^Q^U^D:ie=%$e=^D:nt:hf:
pc2:\
:dv=/dev/cua/pc2:br#38400:el=^C^S^Q^U^D:ie=%$e=^D:nt:hf:
pc3:\
:dv=/dev/cua/pc3:br#38400:el=^C^S^Q^U^D:ie=%$e=^D:nt:hf:
pc4:\
:dv=/dev/cua/pc4:br#38400:el=^C^S^Q^U^D:ie=%$e=^D:nt:hf:
pc5:\
:dv=/dev/cua/pc5:br#38400:el=^C^S^Q^U^D:ie=%$e=^D:nt:hf:
pc6:\
:dv=/dev/cua/pc6:br#38400:el=^C^S^Q^U^D:ie=%$e=^D:nt:hf:
pc7:\
:dv=/dev/cua/pc7:br#38400:el=^C^S^Q^U^D:ie=%$e=^D:nt:hf:
cuab:dv=/dev/cua/b:br#2400
dialup1|Dial-up system:\
n=2015551212:tc=UNIX-2400:
hardwire-a:\
:dv=/dev/ter
m/a:br#9600:el=^C^S^Q^U^D:ie=%$e=^D: - Note: for
this example serial port A
hardwire:\ is
being used
:dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$e=^D: - Note: for
this example serial port B
tip300:tc=UNIX-300: is
being used
tip1200:tc=UNIX-1200:
tip0|tip2400:tc=UNIX-2400:
tip9600:tc=UNIX-9600:
tip19200:tc=UNIX-19200:
UNIX-300:\
:el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%e=^D:br#300:tc=dialers:
UNIX-1200:\
:el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%e=^D:br#1200:tc=dialers:
UNIX-2400:\
:el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%e=^D:br#2400:tc=dialers:
UNIX-9600:\
:el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%e=^D:br#9600:tc=dialers:
UNIX-19200:\
:el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%e=^D:br#19200:tc=dialers:
VMS-300|TOPS20-300:\
:el=^Z^U^C^S^Q^O:du:at=hayes:ie=$@e=^Z:br#300:tc=dialers:
VMS-1200|TOPS20-1200:\
:el=^Z^U^C^S^Q^O:du:at=hayes:ie=$@e=^Z:br#1200:tc=dialers:
dialers:\
:dv=/dev/cua/b:
--------------------------------------------------------------------
The attributes are:

dv device to use for the tty
el EOL marks (default is NULL)
du make a call flag (dial up)
pn phone numbers (@ =>'s search phones file; possibly taken from
PHONES environment variable)
at ACU type
ie input EOF marks (default is NULL)
oe output EOF string (default is NULL)
cu call unit (default is dv)
br baud rate (defaults to 300)
fs frame size (default is BUFSIZ) -- used in buffering writes
on receive operations
tc to continue a capability
#


Once you connect the cabling and determine the /etc/remote file is properly
configured, you can tip into the system.

# tip hardwire - to tip through serial port B

# tip hardwire-a - to tip through serial port A

# tip hardwire-a
connected
sc>

As an alternative to using a tip connection, the serial port may also be
connected to a serial console/terminal server, but may require a custom
RJ45-RJ45 cable depending on the pinout of terminal server ports. The pinout of
the ALOM serial port is provided in the ALOM Online User Guide. An alternative
to creating a custom cable, is to create a chain using the standard serial
adapters and cables that come with the ALOM server and the terminal server.
This chain may need gender changers and null-modem adapters included in the
middle.

2- For a Microsoft Windows system, open a hyperterminal connection and select
COM1 as the device. Click ok and then click "restore defaults". Finally click
"ok" .

FOR SunFire[TM] V210/V240/V250/V440 or NETRA[TM] 240/440 SYSTEMS
with an ALOM Port
--------------------------------------------------------------------------------
Once connected into the system the ALOM commands will be available:

sc> help
Available commands
------------------
poweron {FRU}
poweroff [-y] [-f]
removefru [-y] {FRU}
reset [-y] [-x]
break [-y]
bootmode [normal|reset_nvram|diag|skip_diag|bootscript="string"]
console [-f]
consolehistory [-b lines|-e lines] [-g lines] [-v] [boot|run]
showlogs [-b lines|-e lines] [-g lines] [-v]
setlocator [on|off]
showlocator
showenvironment
showfru
showplatform [-v]
showsc [-v] [param]
shownetwork [-v]
setsc [param] [value]
setupsc
showdate
setdate [[mmdd]HHMM | mmddHHMM[cc]yy][.SS]
resetsc [-y]
flashupdate [-s IPaddr -f pathname] [-v]
setdefaults [-y] [-a]
useradd <username>
userdel [-y] <username>
usershow [username]
userpassword <username>
userperm <username> [c][a][r]
password
showusers [-g lines]
logout
help [command]
sc>

FOR SunFire[TM] V100/V120 SYSTEMS with a LOM Port
-------------------------------------------------
Once connected into the system the ALOM commands will be available:

lom>help
The following commands are supported:
alarmon [n]
alarmoff [n]
check
console
environment
faulton
faultoff
help
poweron
poweroff
reset [-x]
shutdown
show [eventlog] [escape]
version
set
break
bootmode [-u] [normal|forth|reset_nvram|diag|skip_diag]
loghistory [index +/-n] [pause x] [level y]
showlogs
consolehistory
chist
date
showdate
logout
userpassword [username]
useradd [username]
userdel [username]
userperm [username] [c] [a] [r] [-]
usershow
lom>

===========================================================

Some of the basic commands are:

sc/lom>console - to go to the system console from ALOM

#. - to go to LOM/ALOM from the system console

sc/lom>break - similar to the old L1-A

 

[iain99]

Thanks a lot. I've checked the entry in the /etc/remote file before trying to tip in but still no luck.
Your advice is appreciated.
Iain