Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1010563.1
Update Date:2011-03-29
Keywords:

Solution Type  Technical Instruction Sure

Solution  1010563.1 :   How To connect to LOM/ALOM [TM]SERIAL Management Port  


Related Items
  • Sun Fire V245 Server
  •  
  • Sun Fire V250 Server
  •  
  • Sun Fire V440 Server
  •  
  • Sun Fire V240 Server
  •  
  • Sun Fire V215 Server
  •  
  • Sun Fire V445 Server
  •  
  • Sun Fire V120 Server
  •  
  • Sun Fire V210 Server
  •  
  • Sun Fire V100 Server
  •  
  • Sun Netra 440 Server
  •  
  • Sun Fire V125 Server
  •  
  • Sun Fire V1280 Server
  •  
  • Sun Fire E2900 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Midrange V and Netra Servers
  •  
  • GCS>Sun Microsystems>Servers>Entry-Level Servers
  •  
  • GCS>Sun Microsystems>Servers>Midrange Servers
  •  

PreviouslyPublishedAs
214535


Description
This Technical Instruction will explain how to set up a connection to the LOM/ALOM SERIAL
MGT port on a:

SunFire[TM] V100/V120/V125/V210/V215/V240/V245/V250/V440/V445/V1280/E2900 or Netra[TM] 240/440 system.


Steps to Follow
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=%$:oe=^D:nt:hf:
pc1:\
:dv=/dev/cua/pc1:br#38400:el=^C^S^Q^U^D:ie=%$:oe=^D:nt:hf:
pc2:\
:dv=/dev/cua/pc2:br#38400:el=^C^S^Q^U^D:ie=%$:oe=^D:nt:hf:
pc3:\
:dv=/dev/cua/pc3:br#38400:el=^C^S^Q^U^D:ie=%$:oe=^D:nt:hf:
pc4:\
:dv=/dev/cua/pc4:br#38400:el=^C^S^Q^U^D:ie=%$:oe=^D:nt:hf:
pc5:\
:dv=/dev/cua/pc5:br#38400:el=^C^S^Q^U^D:ie=%$:oe=^D:nt:hf:
pc6:\
:dv=/dev/cua/pc6:br#38400:el=^C^S^Q^U^D:ie=%$:oe=^D:nt:hf:
pc7:\
:dv=/dev/cua/pc7:br#38400:el=^C^S^Q^U^D:ie=%$:oe=^D:nt:hf:
cuab:dv=/dev/cua/b:br#2400
dialup1|Dial-up system:\
:pn=2015551212:tc=UNIX-2400:
hardwire-a:\
:dv=/dev/ter
m/a:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^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=%$:oe=^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=#$%:oe=^D:br#300:tc=dialers:
UNIX-1200:\
:el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%:oe=^D:br#1200:tc=dialers:
UNIX-2400:\
:el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%:oe=^D:br#2400:tc=dialers:
UNIX-9600:\
:el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%:oe=^D:br#9600:tc=dialers:
UNIX-19200:\
:el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%:oe=^D:br#19200:tc=dialers:
VMS-300|TOPS20-300:\
:el=^Z^U^C^S^Q^O:du:at=hayes:ie=$@:oe=^Z:br#300:tc=dialers:
VMS-1200|TOPS20-1200:\
:el=^Z^U^C^S^Q^O:du:at=hayes:ie=$@:oe=^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/V215/V240/V245/V250/V440/V445 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][u][a][r]
password
showusers [-g lines]
logout
help [command]
sc>

FOR SunFire[TM] V100/V120/V1280/E2900 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] [u] [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


To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community, Midrange Servers.


Product
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
Sun Fire V1280 Server
Sun Fire E2900 Server
Sun Fire V445 Server
Sun Fire V125 Server

Internal Comments
Audited/updated 11/05/09 - Dencho.Kojucharov@Sun.COM, Entry Level SPARC Content Team Lead

ALOM, LOM, tip, v100 [TM], v120 [TM}, v210 [TM], v240 [TM], V250 [TM}, V440 [TM], console, hardwire
Previously Published As
72108

Change History
Date: 2007-11-05
User Name: 7058
Action: Approved
Date: 2007-11-05
User Name: 7058
Action: Accept
Comment:
Version: 0
Date: 2007-11-05
User Name: 35315


Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback