Category: Hardware

  • 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 additional hard disks. Lo and Behold two 40gb Maxtors, and an external drive enclosure. With all the correct cables, would you believe. 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 enough 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

    Managementilomelomimpiloginscreen
    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/Javatrademark 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

    Sun_fire_v490_server
    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 and ILOM How To

    solaris_logo

    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 and then type:

    -> reset /SYS

    Accessing the Console from ILOM

    start /SP/console

    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

    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