X4200 and hyperthreading

Q. Does the X4200 support hyperthreading

Y. Yes – with the AMD opteron chips

Q. Can I monitor this with my windows system.

A. Why you took a perfectly good system and destroyed it with windows is beyond me, but AMD has a utility that will monitor the CPU(s)


AMD CPUInfo – This Windows® application executes and displays the return data from the CPUID instruction set and displays HyperTransport™ technology information if the processor supports it. This application also shows the maximum speed of the processor.

Q. Can you turn hyperthreading on or off?

A. Yes, in the bios . Advanced settings, under southbridge

ALOM Shell Commands

Command Description
Displays a list of all ALOM commands with their syntax and a brief description of how each command works.

resetsc [-y]
Reboots ALOM. The -y option allows you to skip the confirmation question.

reset [-y] [-x]
Generates a hardware reset on the host server. The -x option generates the equivalent of an XIR (externally initiated reset) on the server. The -y option allows you to skip the confirmation question.

poweroff [-y] [-f]
Removes the main power from the host server. The -y option allows you to skip the confirmation question. The -f option forces an immediate shutdown.

Applies the main power to the host server or FRU.

Updates the ALOM firmware. This command downloads main and bootmon firmware images to ALOM.

removefru [-y] [FRU]
Prepares a FRU (for example, a power supply) for removal, and illuminates the host server’s OK-to-Remove LED. The -y option allows you to skip the confirmation question.

Sets the specified ALOM parameter to the assigned value.

Runs the interactive configuration script. This script configures the ALOM configuration variables.

Sets the date and time, when the managed operating system is not running.

setdefaults [-y][-a]
Resets all ALOM configuration parameters to their default values. The -y option allows you to skip the confirmation question. The -a option resets the user information to the factory default (one admin account only).

setlocator [on/off]
Turns the Locator LED on the server on or off. This function is available only on host servers that have a Locator LED.

Displays the current state of the Locator LED as either on or off. This function is available only on host servers that have a Locator LED.

showplatform [-v]
Displays information about the host server’s hardware configuration, and whether the hardware is providing service.

Displays the environmental status of the host server. This information includes system temperatures, power supply status, front panel LED status, hard disk drive status, fan status, voltage and current sensor status, and keyswitch position.

Displays information about the FRUs (field-replaceable units) in a host server.

showusers [-g]lines
Displays a list of users currently logged in to ALOM. The display for this command has a similar format to that of the UNIX command who. The -g option pauses the display after the number of lines you specify for lines.

shownetwork [-v]
Displays the current network configuration information. The -v option shows additional information about your network, including information about your DHCP server.

showsc [-v]
Displays the current NVRAM configuration parameters. The -v option is needed for full version information.

showlogs [-v]
Displays the history of all events logged in the ALOM event buffer.

Displays the ALOM set date. The Solaris operating environment and ALOM time are synchronized, but ALOM time is expressed in UTC (Coordinated Universal Time) rather than local time.

Displays a list of all user accounts, permission levels, and whether passwords are assigned.

Adds a user account to ALOM.

userdel [-y]
Deletes a user account from ALOM. The -y option allows you to skip the confirmation question.

Sets or changes a user password.

Sets the permission level for a user account.

Changes the login password of the current user.

console [-f]
Connects to the host system console. The -f option forces the console write lock from one user to another.

break [-y]
Drops the host server from running the Solaris operating environment into OpenBoot PROM or kadb. The -y option allows you to skip the confirmation question.

bootmode [skipdiag | diag | reset_nvram | normal | bootscript="string"]
Controls the host server OpenBoot PROM firmware method of booting.

Logs out from an ALOM shell session.

consolehistory [-v] [boot | run]
Displays the host system console output buffers. The -v option displays the entire contents of the specified log.

EMC storage array reports strange results


# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d0 41667715 8145442 33105596 20% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
swap 31859696 32 31859664 1% /var/run
swap 31865528 5864 31859664 1% /tmp
/dev/dsk/emcpower16g 61669084 233254 60819140 1% /e02
/dev/dsk/emcpower1g 61669084 18446744073707502995 63101015 30214612180004% /a03
/dev/dsk/emcpower8g 257899827 240137193 15183636 95% /b02
/dev/dsk/emcpower0g 41025571 11059824 29555492 28% /e01
/dev/dsk/emcpower7g 23474934 11961283 11278902 52% /a02
/dev/dsk/emcpower10g 61669084 4964481 56087913 9% /a04
/dev/dsk/emcpower4g 61669084 48375421 12676973 80% /a06
/dev/dsk/emcpower6g 1826145 9 1771352 1% /a08
/dev/dsk/emcpower5g 1826145 860731 910630 49% /a07
/dev/dsk/emcpower15g 23474934 65709 23174476 1% /y02
/dev/dsk/emcpower3g 61669084 44166756 16885638 73% /y03
/dev/dsk/emcpower2g 61669084 41919149 19133245 69% /y04
/dev/dsk/emcpower11g 61669084 9945 61042449 1% /y06
/dev/dsk/emcpower14g 1826145 9 1771352 1% /y07
/dev/dsk/emcpower9g 61669084 18446744073707037177 63566833 30214612180003% /a05
/dev/dsk/emcpower13g 1826145 860731 910630 49% /y08
/export/home/bng 41667715 8145442 33105596 20% /home/bng

1. umount the EMC file system:
2. fsck the file system until it reports no errors
3. mount the file system
4. df -k


Sun Fire V20z and V40z Servers Option Card drivers

Sun Fire V20z and V40z Servers Option Cards and their drivers for

Solaris 10 x86 U2

Solaris 9 4/04 x86

Solaris 9 9/04 x86

Red Hat RHEL 3.0 (32 bit)

Red Hat RHEL 3.0 (64 bit)

Red Hat RHEL 4.0 (64 bit)

Novell SUSE SLES 8 (64 bit)

Novell SUSE SLES 9 (64 bit)

Windows 2003 (32 bit)

Windows 2003 (64 bit)


X4100 OS installation

NOTE: on the X4100 the SP card will not talk to RedHat or Windows until the correct drivers are installed.

You must have a USB keyboard & mouse and VGA monitor to install.

See install doc 819-1158

How to Install Red Hat Enterprise Linux From Distribution Media

Red Hat Enterprise Linux provides both a text mode and an easy-to-use graphical interface for installing and configuring the operating system. You can select the interface that you want to use from the boot prompt, and both options are shown later in this section.
Before You Begin

Installing Red Hat Enterprise Linux software from CDs consists of the following procedures:

If you are using RHEL 4 Update 2 or later version, you do not need to create a Driver CD. Proceed to Step 2:

1. If necessary, create the Enterprise Driver CD or use the Sun Installation Assistant CD.

See the How to Create a Red Hat Enterprise Linux Driver CD or How to Use the Sun Installation Assistant.

2. Install the Red Hat Enterprise Linux software.

3. Update the Red Hat Enterprise Linux software.

See How to Update the Red Hat Enterprise Linux Operating System and Drivers.
Required Items

Installation from distribution media requires the following items:

* Sun Fire X4100 or Sun Fire X4200 server equipped with:

o DVD-ROM drive

o USB keyboard and mouse

o Monitor

* Red Hat Enterprise Linux media CD set

* Driver CD

You create this yourself. See the Help topic about how to create a Red Hat Enterprise Linux Driver CD.

What patch is installed?

showrev -a

will give you a complete list.

Patching Tools (available at http://www.dracko.com/index.php?s=page&n=download or http://ist.uwaterloo.ca/security/howto/2000-12-04/patches.tar)

GetApplyPatch(8) and CheckPatches(8) are two Bourne shell scripts for Solaris patch management that we’ve developed with the help of colleagues on the net (CheckPatches(8) was originally a Perl script posted to Usenet by Bruce Barnett). The scripts rely on the vendor’s patch report to construct an incremental list of patches required. These tools have been peer reviewed, many thanks to Sean Boran of BORAN Consulting and other participants on the YASSP project, and can help you manage patches on your Solaris system. These tools are found at Waterloo in the optional solaris-harden package distributed by xhier (that package is under development and addresses many other issues in hardening a Solaris server); they’re also available to sites (here and elsewhere) that do not participate in xhier as a traditional Unix "tar" kit (see references below).

A quick introduction to these two tools:

1. CheckPatches(8) is a script that uses the vendor provided showrev(1m) command to see what patches are installed, compares this against the Solaris patch report, and makes a list of recommended, security and Y2K patches that need installation. It expects to find "SolarisX.PatchReport" in the current directory and will fetch a copy if none is found. You can use the "-f" option to fetch the most recent Patch report from the FTP site.

CheckPatches -f

A sample cron job to automate this process and email the results is provided as CheckPatches.cron. The recommendation is that the job be run twice a month shortly after the posting of patch reports.

2. GetApplyPatch(8) is a script to get and apply a patch. Arguments are a list of patch numbers. If run from the command line, it is interactive and will ask you to confirm the down load, show the patch documentation, install the patch and delete the temporary files it created.

GetApplyPatch 108875-07

Interactive mode gives you an opportunity to determine if the patch requires any special efforts or can be applied on the fly — most can be. The tool will run without prompting in "batch mode" and will apply every patch as instructed. That can be problematic if the patch requires that you bring the system to single user mode or reboot after installation.

3. Both scripts can be used together in a pipeline to fetch all required patches and install them (you are prompted through the installation of each patch and can abandon the process at any time).

CheckPatches | sort -u | GetApplyPatch

A sample cron job to automate this process and mail the results is provided as GetApplyPatch.cron. The recommendation is that the job be run twice a month shortly after the posting of patch reports.

Recommendation: But an emphatic beware — blindly applying patches to productions systems without first testing them in a non-production environment can cause very nasty problems!

These tools include support for the Solaris Intel platform (although we have no direct experience), FTP proxies may be configured, and you can down load from your local FTP mirror rather than SUNSOLVE. You should see the manual pages for each command to learn more about what they can do — see CheckPatches(8) and GetApplyPatch(8). The distribution kit comes with additional notes.

Finally, you could use the Patchdiag tool from SUNSOLVE along with the latest patchdiag.xref data to see what recommended and security patches are missing, then download and install the missing ones. The GetApplyPatch(8) tool will help with fetching and installing patches.

Service processor commands

SP commands:

Usage: sp add mount {-h|–help}
sp add snmp-destination {-h|–help}
sp create test events {-h|–help}
sp delete event {-h|–help}
sp delete mount {-h|–help}
sp delete snmp-destination {-h|–help}
sp disable dns {-h|–help}
sp disable ssl-required {-h|–help}
sp enable dns {-h|–help}
sp enable ssl-required {-h|–help}
sp get date {-h|–help}
sp get dns {-h|–help}
sp get events {-h|–help}
sp get hostname {-h|–help}
sp get mac {-h|–help}
sp get ip {-h|–help}
sp get locatelight {-h|–help}
sp get logfile {-h|–help}
sp get jnet {-h|–help}
sp get mounts {-h|–help}
sp get port80 {-h|–help}
sp get smtp server {-h|–help}
sp get smtp subscribers {-h|–help}
sp get snmp proxy community {-h|–help}
sp get snmp-destinations {-h|–help}
sp get ssl {-h|–help}
sp get status {-h|–help}
sp get tdulog {-h|–help}
sp reboot {-h|–help}
sp reset to default-settings {-h|–help}
sp set date {-h|–help}
sp set hostname {-h|–help}
sp set ip dhcp {-h|–help}
sp set ip static {-h|–help}
sp set jnet {-h|–help}
sp set locatelight {-h|–help}
sp set logfile {-h|–help}
sp set smtp server {-h|–help}
sp set snmp proxy community {-h|–help}
sp set ssl {-h|–help}
sp update diags {-h|–help}
sp update flash all {-h|–help}
sp update flash applications {-h|–help}
sp update flash pic {-h|–help}
sp update smtp subscriber {-h|–help}
sp load settings {-h|–help}

Very Simple Samba install


It is assumed that the server is fully installed and ready for installation and configuration of Samba 3.0.20 and any support files needed. All TCP/IP addresses have been hard-coded. In our case the IP address of the Samba server is and the netmask is The hostname of the server used is server.

Procedure 1.1. Samba Server Configuration


Download the Samba-3 RPM packages for Red Hat Fedora Core2 from the Samba FTP servers.

Install the RPM package using either the Red Hat Linux preferred GUI tool or the rpm:

root# rpm -Uvh samba-3.0.20-1.i386.rpm


Create a mount point for the file system that will be used to store all data files. You can create a directory called /plans:

root# mkdir /plans
root# chmod 755 /plans

The 755 permissions on this directory (mount point) permit the owner to read, write, and execute, and the group and everyone else to read and execute only.

Use Red Hat Linux system tools (refer to Red Hat instructions) to format the 160GB hard drive with a suitable file system. An Ext3 file system is suitable. Configure this drive to automatically mount using the /plans directory as the mount point.

Install the smb.conf file shown in ??? in the /etc/samba directory.

Example 1.1. Drafting Office smb.conf File
# Global Parameters
workgroup = MIDEARTH
security = SHARE
path = /plans
read only = Yes
guest ok = Yes


Verify that the /etc/hosts file contains the following entry: server


Use the standard system tool to start Samba and to configure it to restart automatically at every system reboot. For example,

root# chkconfig smb on
root# /etc/rc.d/init.d/smb restart

Procedure 1.2. Windows Client Configuration


Make certain that all clients are set to the same network address range as used for the Samba server. For example, one client might have an IP address

Ensure that the netmask used on the Windows clients matches that used for the Samba server. All clients must have the same netmask, such as

Set the workgroup name on all clients to MIDEARTH.

Verify on each client that the machine called SERVER is visible in the Network Neighborhood, that it is possible to connect to it and see the share Plans, and that it is possible to open that share to reveal its contents.


The first priority in validating the new Samba configuration should be to check that Samba answers on the loop-back interface. Then it is time to check that Samba answers its own name correctly. Last, check that a client can connect to the Samba server.


To check the ability to access the smbd daemon services, execute the following:

root# smbclient -L localhost -U%
Sharename Type Comment
——— —- ——-
Plans Disk
IPC$ IPC IPC Service (Samba 3.0.20)
ADMIN$ IPC IPC Service (Samba 3.0.20)

Server Comment
——— ——-
SERVER Samba 3.0.20

Workgroup Master
——— ——–

This indicates that Samba is able to respond on the loopback interface to a NULL connection. The -U% means send an empty username and an empty password. This command should be repeated after Samba has been running for 15 minutes.

Now verify that Samba correctly handles being passed a username and password, and that it answers its own name. Execute the following:

root# smbclient -L server -Uroot%password

The output should be identical to the previous response. Samba has been configured to ignore all usernames given; instead it uses the guest account for all connections.

From the Windows 9x/Me client, launch Windows Explorer: [Desktop: right-click] Network Neighborhood+Explore → [Left Panel] [+] Entire Network → [Left Panel] [+] Server → [Left Panel] [+] Plans. In the right panel you should see the files and directories (folders) that are in the Plans share.