FatMin

More Console Fun with the Lantronix 3200

Ah, the good old console server. Can't say that I get a lot of chances to work on one, and I will tell you that when I do get a chance I can never remember how to get them setup without referring to my notes.

One of the things that I find most annoying is the command structure and how incredibly user-unfriendly the command line is.

No matter how old and antiquated you consider the console server to be I am sure that you have at least one around somewhere, and I cannot say that they are the worst thing to have at your desk for quick console access to a Sun box.

First thing that you need to know is the difference between the set and the define command.

set    # Immediate but not permanent (effective only until reboot).
define # Permanent but not immediate (effective only after reboot).

Then you need to know save, show, and list

save   # Transform a setting made with 'set' into a permanent setting.
show   # Displays current settings, both temporary and permanent.
list   # Displays settings scheduled to take effect after next reboot.

You are also going to need to know how to delete settings.
clear  # Deletes temporary settings immediately.
purge  # Deletes permanent settings, effective upon next reboot.

Basic Commands:

This will clear the label on a port, this is useful when you are changing the device connected to a port.

set service "service name" port <#> enable
Replace the port number with the port that you are working on, remember to use set so that the change is immediate. Then save your changes to make them permanent with the command , save service all

show port all/show port <port #>
The first command will let you see all your ports, while the second command allows you to view the settings of just one port.

set port <port #> access remote
Use this when setting up a port for remote access. Common on your Sun servers

set port <port #> flow none
Use the command above to set flow control to off

misc. commands
--------------
Local_33>> logout
Local_33>> logout port 2
Local_33>> finger # Good brief overview of all ports and status.
Local_33>> show ports all status # Verbose finger.
Local_33>> set port menu enable # Return to menu (from whence you came.)
Local_33> broadcast scsman "test ms"

Configure ALOM on the v210 from the OS

I was recently tasked to re-ip a v210 that was using a terminal server for console connectivity.I was actually pleased to find out the the V210 has an SC.

The scadm command is located here : /usr/platform/SUNW,Sun-Fire-V240/sbin

This should not be a surprise for those who have used the command before. You can use the command to show the config for the SC.

bash-2.03# ./scadm shownetwork
IP Address: 0.0.0.0
Gateway address: 0.0.0.0
Netmask: 255.255.255.0
Ethernet address: 00:03:ba:41:51:00

Use the "scadm set" command to setup the ALOM, using the format below.
#scadm set if_network true
#scadm set netsc_tpelinktest true
#scadm set netsc_dhcp false
#scadm set netsc_ipaddr x.x.x.x
#scadm set netsc_ipnetmask x.x.x.x
#scadm set netsc_ipgateway x.x.x.x

Note that you must reset the SC for the new settings to take affect.

SCS4805 System Configuration

I have had several opportunities as of late work with these Lantronix terminal servers. Usually I am connecting older Sun boxes... those without an SC. In this instance I am connecting to a LOM port on a SUN v120 using a straight through Ethernet cable.

First of log into the SCS480 using the sysadmin user id and its password. In this instance I am connected to port 23.

Typing help will show you a list of commands.

Typing direct and then the port number will connect you directly to the port, <ESC>A will disconnect you.

 Entering Direct mode...Server = DEVICE_23
(enter '<ESC>A' to exit, enter '<ESC>B' to generate a break.)

Type listdev to see all the ports, and their names. You should set the name so it corresponds with the server.

Type devices 23 to see how port 23 is configured.

sysadmin-DEVICE_23>devices 23
Enter accepts present value
D23: Enter device name                      | NAME: DEVICE_23>
D23: 0=2400 1=4800, 2=9600, 3=19200,
     4=38400, 5=57600, 6=115200             | BAUD RATE: 9600>
D23: 1=1, 2=2                               | STOP BITS: 1>
D23: 0=None, 1=Odd, 2=Even, 3=Mark, 4=Space | PARITY: NONE>
D23: 6=6, 7=7, 8=8                          | DATA BITS: 8>
D23: 0=OFF, 1=DCE, 2=DTE                    | EQUIP PORT TYPE: DTE>
D23: 0=XON/OFF, 1=RTS/CTS                   | FLOW CONTROL: XON/XOFF>
D23: 0=No, 1=Yes                            | INHIBIT BUFFERING IN DIRECT: No>

To configure the port I need to change the device name and change the EQUIP PORT TYPE to DCE. Click here for more info on DCE/DTE.

Using the devices command you can configure the port. See syntax below

devices --name=devname n
  Set name of device n to devname
 devices --baud=2400|4800|9600|19200|38400|57600|115200 n
  Set baudrate of device n to 2400, 4800, 9600, 19200, 38400, 57600,
              or 115200
 devices --baud=0|1|2|3|4|5|6 n
  Set baudrate of device n to 0=2400 1=4800, 2=9600, 3=19200,
              4=38400, 5=57600, or 6=115200
 devices --stop=1|2 n
  Set stop bits of device n to 1=1, 2=2
 devices --parity=None|Odd|Even|Mark|Space n
  Set parity of device n to None, Odd, Even, Mark, or Space
 devices --parity=0|1|2|3|4 n
  Set parity of device n to 0=None, 1=Odd, 2=Even, 3=Mark, or 4=Space
 devices --data=6|7|8 n
  Set number of data bits of device n to 6, 7, or 8
 devices --type=OFF|DCE|DTE n
  Set port type of device n to OFF, DCE, or DTE
 devices --type=0|1|2 n
  Set port type of device n to 0=OFF, 1=DCE, or 2=DTE
 devices --flow=XON|RTS n
  Set flow control of device n to XON/OFF, or RTS/CTS
 devices --flow=0|1 n
  Set flow control of device n to 0=XON/OFF, or 1=RTS/CTS
 devices --inhibitbuffer=No|Yes n
  Set inhibit buffering of device n to No, or Yes
 devices --inhibitbuffer=0|1 n
  Set inhibit buffering of device n to 0=No, or 1=Yes

Using this info I can now configure my port

sysadmin-DEVICE_23>devices --name=myserver 24
alaudpnc004
Config files have been updated.
Updating hardware, please wait....  port: 24
Hardware has been updated.
sysadmin-DEVICE_23>devices --type=DCE 24
Config files have been updated.
Updating hardware, please wait....  port: 24
Hardware has been updated.

How to Change Root's Ilom Password

ILOM:

ILOM is the system Service Processor Sun includes with Sun x64 systems.ILOM, can also be accessed via an integrated HTTPS server, meaning that a user friendly graphical user interface is available. Currently the servers below use ILOM.

Sun Fire[TM]  X4100
Sun Fire[TM]  X4200
Sun Fire[TM]  X4500
Sun Fire[TM]  X4600
Sun Fire[TM]  X4100 M2
Sun Fire[TM]  X4200 M2
Sun Fire[TM]  X4600 M2
Sun Blade[TM] 6000
Sun Blade[TM] 8000
Sun Netra[TM] X4200 M2
Sun SPARC[TM] Enterprise T5120
Sun SPARC[TM] Enterprise T5220


The default root password for the ILOM is changeme. This is a Sun default and you should make sure that you modify this when you are setting up your new server.

Below is the procedure.

1. Connect and Login to your Serial Management port.
2. cd /SP/users
3. type "set /SP/users/root password", and voila

Changing password for user /SP/users/root...
Enter new password: ********
Enter new password again: ********
New password was successfully set for user /SP/users/root

More Sun ok> Prompt Commands

Courtesy of a Sun v120.

Use the following to determine the mac addresses of each interface
ok>devalias

The command above returns the following
rootdisk                 /pci@1f,0/pci@1/scsi@8/disk@0,0
lom                      /pci@1f,0/pci@1,1/ebus@c/SUNW,lomh@14,200000
dload                    /pci@1f,0/pci@1,1/network@c,1:,
net2                     /pci@1f,0/pci@1,1/network@5,1
net                      /pci@1f,0/pci@1,1/network@c,1
{truncate}

Then you can cd to the path for either net or net2 and run the following command
ok> .properties

This command returns the following for mac address
local-mac-address        00 03 ba 96 38 c0

In this case I was working to troubleshoot a jumpstart install, so I needed to see what mac address was being presented externally.

ok>printenv

printenv reveals that local mac address is set to true which means that each network interface presents it own mac. Being that I was plugged into nic 0 on this box i am also able to boot like so.

ok boot /pci@1f,0/pci@1,1/network@c,1:dhcp - install

Being specific in this way, I am taking any way chance that I have the mac address incorrect, or am plugged into the correct ethernet port.

I can verify which port has my link by doing the following from the ok prompt

ok watch-net
Internal loopback test -- succeeded.
Link is  -- up
Looking for Ethernet Packets.
'.' is a Good Packet.  'X' is a Bad Packet.
Type any key to stop.
............

If I try this on net2 is see that this link is down

ok watch-net2
Internal loopback test -- succeeded.
Link is  -- down

Configure Alom v240

The following post outlines how to configure the ALOM on a v240.

Option 1: Configure from serial console.

Configuring the ALOM from the serial console is probably the most common method of setting up the ALOM on a box. First connect to the box's serial port, using tip from solaris, minicom in linux, or hyperterm in windows.

Use the showsc command to print out the default ALOM variables to the screen.

sc> showsc
Advanced Lights Out Manager v1.0

parameter value
--------- -----
if_network true
if_modem false
if_snmp false
if_emailalerts false
sys_autorestart xir
netsc_tpelinktest true
netsc_dhcp false
netsc_ipaddr 0.0.0.0
netsc_ipnetmask 255.255.255.0
netsc_ipgateway 0.0.0.0
mgt_mailhost
mgt_mailalert
sc_customerinfo
sc_escapechars #.
sc_powerondelay false
sc_clipasswdecho true
sc_cliprompt sc
sc_clitimeout 0
sc_clieventlevel 2
sys_eventlevel 2
ser_baudrate 9600
ser_parity none
ser_stopbits 1
ser_data 8
netsc_enetaddr 00:03:ba:29:5e:34
sys_hostname
sys_enetaddr 00:03:ba:29:5e:2

Then use 'setsc' command to set the following 

sc> setsc if_network true

This command enables the NET MGT port.

sc> setsc netsc_tpelinktest true

This command enable/disables the link integrity test. 

sc> setsc netsc_dhcp false

This command should be set to false unless you want DHCP to obtain your network 
configuration, which is not part of this example.

sc> setsc netsc_ipaddr xxx.xx.xxx

This command sets the the unique IP address for the NET MGT port, 

sc> setsc netsc_ipnetmask 255.255.255.0

This command sets the netmask and will depend on the class of network. 

sc> setsc netsc_ipgateway 129.148.173.253

Now verify the settings with the "shownetwork" command.

sc> shownetwork
SC network configuration is:
IP Address:xxx.xxx.xxx.xxx
Gateway address: xxx.xxx.xxx.xxx
Netmask: 255.255.255.0
Ethernet address: 00:03:ba:29:5e:34

Option 2: Use the scadm command

Use scadm to configure your ALOM from inside a running Solaris OS.
I would think that this would be the better option for systems that are set 
to auto boot, and obviously already have a running OS installed and configured.
#scadm set if_network true

#scadm set netsc_tpelinktest true

#scadm set netsc_dhcp false

#scadm set netsc_ipaddr 129.148.173.27

#scadm set netsc_ipnetmask 255.255.255.0

#scadm set netsc_ipgateway 129.148.173.253

 

Linux Disk Utilities

For the last few days I have been thinking about taking a trip to Frys to pick myself up another external disk drive, so that I could have a bit of extra storage for the office, as my personal ISOs seem to be taking up way to much space on my already crowded desktop's harddrive. Plus I need addtional space if I am ever going to convert my running Windows desktop to a VM that I run inside Kubuntu. For some reason I had the idea to check my giant hardware bin to see if I could round up any additonal harddisks. Lo and Behold to 40gb Maxtors, and an external drive enclosure. WIth all the correct cables, would you belive. Well before I am going to put any of these tiny disks into service I am going to have to verify that both are healthy enought to use. So lets start scanning.

DIsk Utils:

fdisk /dev/hdc
Linux hard drive partitioning utility (DOS has a utility with the same name). Fdisk's output shoed that I had a linux partition, which I removed and created a FAT32 partition for use in the office.
                           
cfdisk /dev/hda
Hard drive partitioning utility, menu-based. Some find it easier to use then the plain-vanilla fdisk.
                           
sfdisk -l -x |more
(as root) List the partition tables (including extended partitions) for all drives on my system.
                           
parted /dev/hda
A partition manipulation utility for Linux (ext2), and DOS (FAT and FAT32) hard drive partition. It is for creation, destroying, moving, copying, shrinking, and extending partitions. You should really like to backup your data and carefully read info parted before using it.
                           
fsck
Use this one to run filesystem check, which I did on my newly created FAT32 partition

fsck -v /dev/sdc1
fsck 1.40.8 (13-Mar-2008)
dosfsck 2.11 (12 Mar 2005)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkdosfs"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
     16384 bytes per cluster
        32 reserved sectors
First FAT starts at byte 16384 (sector 32)
         2 FATs, 32 bit entries
  10031616 bytes per FAT (= 19593 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 20079616 (sector 39218)
   2507893 data clusters (41089318912 bytes)
32 sectors/track, 64 heads
         0 hidden sectors
  80291808 sectors total
Checking for unused clusters.
Checking free cluster summary.
/dev/sdc1: 0 files, 1/2507893 clusters

badblocks: 
Used to check for bad blocks and display the results on the screen. Similar to SCANDISK in DOS/Windows.

/var/log$ badblocks -v /dev/sdc
Checking blocks 0 to 40146623
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found.

hdparm:
Installed to /sbin/hdparm on my system. hdparm is the utility that is used to control the settings of your hard drive, both in the kernel and in the drive itself. Its got a nice man page, so check it out. Below are most of the command line options.

Options:
-a   get/set fs readahead
-A   get/set the drive look-ahead flag (0/1)
-b   get/set bus state (0 == off, 1 == on, 2 == tristate)
-B   set Advanced Power Management setting (1-255)
-c   get/set IDE 32-bit IO setting
-C   check drive power mode status
-d   get/set using_dma flag
-D   enable/disable drive defect management
-E   set cd-rom drive speed
-f   flush buffer cache for device on exit
-F   flush drive write cache
-g   display drive geometry
-h   display terse usage information
-H   read temperature from drive (Hitachi only)
-i   display drive identification
-I   detailed/current information directly from drive
-k   get/set keep_settings_over_reset flag (0/1)
-K   set drive keep_features_over_reset flag (0/1)
-L   set drive doorlock (0/1) (removable harddisks only)
-M   get/set acoustic management (0-254, 128: quiet, 254: fast)
-m   get/set multiple sector count
-N   get/set max visible number of sectors (HPA) (VERY DANGEROUS)
-n   get/set ignore-write-errors flag (0/1)
-p   set PIO mode on IDE interface chipset (0,1,2,3,4,...)
-P   set drive prefetch count
-q   change next setting quietly
-Q   get/set DMA tagged-queuing depth (if supported)
-r   get/set device  readonly flag (DANGEROUS to set)
-R   register an IDE interface (DANGEROUS)
-s   set power-up in standby flag (0/1) (DANGEROUS)
-S   set standby (spindown) timeout
-t   perform device read timings
-T   perform cache read timings
-u   get/set unmaskirq flag (0/1)
-U   un-register an IDE interface (DANGEROUS)
-v   defaults; same as -acdgkmur for IDE drives
-V   display program version and exit immediately
-w   perform device reset (DANGEROUS)
-W   get/set drive write-caching flag (0/1)
-x   tristate device for hotswap (0/1) (DANGEROUS)
-X   set IDE xfer mode (DANGEROUS)
-y   put drive in standby mode
-Y   put drive to sleep
-Z   disable Seagate auto-power

Alom, Ilom, & Elom Part I

Introduction:If you are anything like me, and you have not been a knee deep in Sun hardware for the last 10 years of your life, then you probably get pretty confused between the differences between using Sun's Alom, Ilom, or Elom. It seems every time I start to get familiar with how to manage one type of server, Sun comes up with something new. After a while, which command you should use where becomes an exercise in trial and Error. Hell, if that command does not work here, then try something else. Anyway, here are some notes that I put together to try to keep things straight.

What's What?

ILOM:

ILOM is the system Service Processor Sun includes with Sun x64 systems.ILOM, can also be accessed via an integrated HTTPS server, meaning that a user friendly graphical user interface is available.

ELOM:

This management system is comprised of a system on a chip that includes the following:

• Service processor (SP) -This is the hardware that consists of a dedicated processor that communicates through the system serial port. The SP can also communicate through an Ethernet port that is shared with the OS


• Embedded server management software - This is embedded software running on the SP.


• Command line interface (CLI) - The command-line interface is a dedicated software application that enables you to operate the SP and associated software using keyboard commands. You can use the command-line interface to send commands to the SP. You can connect a terminal or emulator directly to the system serial port or connect over the Ethernet using a Secure Shell (SSH).

• Web-based interface - The web-based interface provides a powerful, yet easy-to-use web browser interface that allows you to log in to the SP, and perform system management, monitoring, and certain IPMI tasks.
• Remote Console/Java Client - The Java Client supports the remote console functionality, which allows you to access your server’s graphical display remotely across the network, as if you were physically located there. It redirects the keyboard, mouse, and video screen, and can redirect input and output from the local machine’s CD and diskette drives. It can also redirect ISO images of the media for these devices; that is, it can create virtual devices based on media images.

ALOM:

The ALOM System Controller and ALOM firmware combine the features of RSC and LOM, as well as adding several new features. ALOM can only be run via telnet (insecure), SSH (secure), or a serial cable, and is therefore limited to the command line interface.

Whats Where?

LOM
Sun Netra[TM] X1
Sun Netra[TM] T1400/1405
Sun Netra[TM] T1 AC200
Sun Netra[TM] T1 DC200
Sun Fire[TM]  V100
Sun Fire[TM]  V120
Sun Fire[TM]  E2900
Sun Netra[TM] 20
Sun Fire[TM]  V1280

ALOM
Sun Fire[TM]  V125
Sun Fire[TM]  V210
Sun Fire[TM]  V215
Sun Fire[TM]  V240
Sun Fire[TM]  V245
Sun Fire[TM]  V250
Sun Fire[TM]  V440
Sun Fire[TM]  V445

ALOM4v
Sun Fire[TM]  T1000
Sun Fire[TM]  T2000
Sun SPARC[TM] Enterprise T1000
Sun SPARC[TM] Enterprise T2000
Sun Netra[TM] T2000

ILOM
Sun Fire[TM]  X4100
Sun Fire[TM]  X4200
Sun Fire[TM]  X4500
Sun Fire[TM]  X4600
Sun Fire[TM]  X4100 M2
Sun Fire[TM]  X4200 M2
Sun Fire[TM]  X4600 M2
Sun Blade[TM] 6000
Sun Blade[TM] 8000
Sun Netra[TM] X4200 M2
Sun SPARC[TM] Enterprise T5120
Sun SPARC[TM] Enterprise T5220

ELOM
Sun Fire[TM]  X2100 M2
Sun Fire[TM]  X2200 M2

RSC
Sun Fire[TM]  V890
Sun Fire[TM]  V490
Sun Fire[TM]  V880
Sun Fire[TM]  V480
Sun Fire[TM]  280R
Sun Enterprise[TM]  250

SP
Sun Fire[TM]  V20z
Sun Fire[TM]  V40z

Coming Soon Part II

Sun RSC Configuration for the v480 & v490

Introduction

This page describes how to setup and manage a Sun RSC (Remote Serial Console) on the v480 and v490, as well as the e250 and e450. I omitted the latter two as those systems are ancient.

Before You Begin

Assign an IP address, netmask and gateway to the server. You must download the RSC utilities version 2.2.3 or later to the server and run the utilities before you can configure the server's RSC.

Steps

• Log in as root to the V490 or V890 manageable server.
• Download the RSC version 1.2.3 utilities zip file.Go to http://www.sun.com/servers/rsc.html. Download the zip file appropriate for the Solaris operating system installed on the server:

Solaris 9 or later: rsc2.2.3_packages_s9.zip Solaris 8: rsc2.2.3_packages_s8.zip When the download has completed, unzip the file to a temporary directory, and then change directory to the temporary directory.

• Install the RSC version 2.2.3 packages on the manageable server.

Install the following packages on the server using the pkgadd command: SUNWrsc - the RSC base package for installation on the host machine SUNWrscd - the RSC documentation package SUNWrscj - the RSC GUI package to display the RSC GUI

If you are asked whether to install conflicting files, type Y to override the existing version.

Redirecting the Console to the RSC

After RSC software is installed and configured, the system console is still available as on any normal Sun machine. To enable RSC as the system console device instead, you must access the server console, shut down the system, and type the following commands at the ok prompt:

ok diag-console rsc

ok setenv input-device rsc-console

ok setenv output-device rsc-console

RSC Commands

The RSC commands are located in the following path:
/usr/platform/SUNW,Sun-Fire-V490/rsc

rsc-config /usr/platform/SUNW,Sun-Fire-V490/rsc/rsc-config

The command above can be used to configure the RSC.

The rscadm command has many options see below.

rscadm - COMMAND DETAILS
  rscadm help => this message
  rscadm date [-s] | [[mmdd]HHMM | mmddHHMM[cc]yy][.SS] => print or set date
  rscadm set <variable> <value> => set variable to value
  rscadm show [variable] => show variable(s)
  rscadm resetrsc [-s] => reset RSC (-s soft reset)
  rscadm download [boot] <file> => program firmware or [boot] monitor
  rscadm send_event [-c] "message" => send message as event (-c CRITICAL)
  rscadm useradd <username> => add RSC user account
  rscadm userdel <username> => delete RSC user account
  rscadm usershow [username] => show user details
  rscadm userpassword <username> => set user password
  rscadm userperm <username> [cuar] => set user permissions
  rscadm shownetwork => show network configuration
  rscadm loghistory => show RSC event log
  rscadm version => show RSC version

Below is the SHOW option

mail_enabled="false"
ip_mode="config"
ppp_enabled="false"
tpe_link_test="true"
serial_baud="9600"
serial_parity="none"
serial_stop="1"
serial_data="8"
customerinfo=""
ip_addr="xxx.xx.xxx.xxx"
ip_netmask="255.255.xxx.x"
ip_gateway="0.0.0.0"
mailhost=""
mailuser=""
ppp_local_ip_addr="0.0.0.0"
ppp_remote_ip_addr="0.0.0.0"
hostname="xxxxxx"
escape_char="~"

 

 

Sun 5220 Console & ILOM How to

Introduction

As far as I know this documentation is specific to Sun T5150s and Sun
T5250s. However some of the information below may also pertain to other
Sun systems running ILOM.







ILOM Commands

    * To power on the host, type:

start /SYS


    * To power off the host, type:

stop /SYS


    * To reset the host, type:

reset /SYS


    * How to set the system not to auto boot the OS 

Example:

 -> set /HOST/bootmode script="setenv auto-boot? false"

Press Enter.

then type:

-> reset /SYS 

    * Accessing the Console from ILOM 

start /SP/console


Ways of Accessing the ok Prompt

   1. Graceful shutdown of the Solaris OS> 

From a shell or command tool window, issue an appropriate command (for
example, the shutdown or init command) as described in Solaris system
administration documentation.

   1. Break key> 

From an alphanumeric terminal configured to access the system console,
press the Break key.

   1. ILOM commands> 

From the -> prompt, type the

 set /HOST send_break_action=break command 

.. Then issue the start /SP/console command, provided the operating
system software is not running and the server is already under OpenBoot
firmware control.


Configuring a Static IP Address Using CLI and Ethernet

    * Log in to the ILOM using Secure Shell (SSH) over the network, or
by connecting 

a terminal to the serial port. To establish a Secure Shell (SSH)
connection to the CLI, type the appropriate connection command in the
SSH application. For example, to connect to the ILOM with an IP address
of 129.144.82.20, type the following command:

# ssh -l root 129.144.82.20

Use the IP address you obtained from QIP

    * Type the following command to set the working directory. 

cd /SP/network

    * Type the following commands to specify a static Ethernet
configuration. 

Note - The following values are samples only. You must specify the IP
address, netmask, and gateway appropriate for your ILOM and network
configuration. set pendingipaddress=129.144.82.26
set pendingipnetmask=255.255.255.0
set pendingipgateway=129.144.82.254
set pendingipdiscovery=static
set commitpending=true