dladm is the admin utility for Data-Link Interface which helps to display informarthe like Link Status (UP/DOWN), Speed, Duplex, MTU, VLAN Tagged and crucially statistics of network traffic on each of the interfaces historically as well as in real time. dladm can also configure and admin Link Aggregation on multiple NICs which we will not focus here.

Show Link Status/Speed/Duplex

# dladm show-dev
nxge0           link: down      speed: 0     Mbps       duplex: unknown
nxge1           link: down      speed: 0     Mbps       duplex: unknown
nxge2           link: up        speed: 1000  Mbps       duplex: full
nxge3           link: up        speed: 1000  Mbps       duplex: full

As you can see above the “show-dev” option lists all the network interfaces with Link Status (UP/DOWN), current speed in Mbps and Duplex (Half/Full)

Show Link Status

# dladm show-link
nxge0           type: non-vlan  mtu: 1500       device: nxge0
nxge1           type: non-vlan  mtu: 1500       device: nxge1
nxge2           type: non-vlan  mtu: 1500       device: nxge2
nxge3           type: non-vlan  mtu: 1500       device: nxge3

Here “show-link” option reveals the MTU and the VLAN tagging detail on each of the interfaces on the system.

Show Stats of all Interfaces for all time

# dladm show-dev -s
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge0           0         0           0       0         0           0
nxge1           0         0           0       0         0           0
nxge2           179625752557169463759657      581104982 3964684165410
nxge3           22240891  1834257868  0       5198483   395084708   0

The “-s” option along with “show-dev” or “show-link” displays network traffic statistics including Input/Output packets, input/output errors.

Stats in real-time

To show the stats of a particular interface in real-time use the “-i” option which is the interval in seconds. The first line shows again historic stats and later on the real-time information for every “n” seconds (5 seconds in our example)

# dladm show-link -s -i 5 nxge2
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge2           179637824757173944575957      581119516 3964706801670
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge2           961       319105             0       150       17874       0
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge2           887       263850             0       117       16505       0

If we fail to mention the interface then it takes the default interface (1st in the list). As you can see from the example below, we see stats for nxge0 which is not connected.

# dladm show-link -s -i 5
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge0           0         0           0       0         0           0
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge0           0         0           0       0         0           0

Display Serial Number

To simply display the serial number run sneep with no arguements

# sneep
0011223344

To display the serial number and its associated tag in the EEPROM and infact all stored Tag/Value pairs.

# sneep -T
“ChassisSerialNumber”   “0011223344″

Store Information in EEPROM

To store information into the EEPROM like the asset tag use the “-t” to set the tag name and the “-s” option to set its value as below:

# sneep -t “AssetTag” -s 001234

To display all information

# sneep -T
“AssetTag”  “001234″
“ChassisSerialNumber”   “0011223344″

Install Sneep

Sneep is not installed by default in Solaris. Click here to download the latest version of Sneep utility. (requires a sunsolve account)

Install as follows from the directory where the sneep package (SUNWsneep) is downloaded to:

# uncompress SUNWsneep2.6.tar.Z
# tar -xvf SUNWsneep2.6.tar
# pkgadd -d . SUNWsneep

To confirm the installation

# pkginfo -l SUNWsneep
PKGINST:  SUNWsneep
NAME:  Serial Number in EEPROM
CATEGORY:  service
ARCH:  sparc,i386
VERSION:  2.6
BASEDIR:  /opt/SUNWsneep
VENDOR:  Sun Microsystems, Inc.
DESC:  Persistent, software-accesible storage of Chassis Serial Number (CSN) across OS and application changes. Works on all Sun platforms. Can also store and retrieve arbitrary other values in EEPROM.
PSTAMP:  cvs-sustain-build20080930010154
INSTDATE:  Jun 04 2009 17:22
HOTLINE:  Support provided through normal Sun support channels
EMAIL:  sneep-support@sun.com
STATUS:  completely installed
FILES:       25 installed pathnames
5 directories
3 executables
1315 blocks used (approx)

If you didn’t accept to create a link file in /usr/sbin during the pkgadd, add a symbolic link as follows;

# ln -s /opt/SUNWsneep/bin/sneep .

To check the man page

# man -M /opt/SUNWsneep/man  sneep

For command help

# sneep -h

Save and retrieve Chassis Serial Number  ( CSN ) using EEPROM.

usage:

sneep [-aFhlTvVx] [-t tag] [-s setting ] [-P ds1:ds2...] \
[-d default] [-o separator]
setcsn -c serialnumber
showplatform -p csn

-h              This help message
For detailed information, consult the man page. Try
man -M /opt/SUNWsneep/man  sneep

The PCP script works on Solaris 10/9/8 and can be downloaded from here. Simply save the pcp.txt file to your Solaris Server as a Shell scripts (say pcp.sh) and change permissions to execute.

# chmod 755 pcp.sh

PIDs for TCP Port

Run PCP with “-p” option to show the PIDs of processes having a TCP port (say Port 22)

For instance, to find PIDs opening TCP port 22.

TCP Ports open by PIDs

Run PCP with “-P” option to show the TCP ports open by specific PID

For instance, here I try to find the TCP ports open by PID 18805

All PIDs for all open TCP Ports

Use the “-a” option to list all TCP ports open with all the PIDs

Talking about the WWN names, there are also

World Wide port Name (WWpN), a WWN assigned to a port on a Fabric which is what you would be looking for most of the time.

World Wide node Name (WWnN), a WWN assigned to a node/device on a Fibre Channel fabric.

To find the WWN numbers of your HBA card in Sun Solaris, you can use one the following procedures

Using fcinfo (Solaris 10 only)

This is probably the easiest way to find the WWN numbers on your HBA card. Here you can see the HBA Port WWN (WWpN) and the Node WWN (WWnN) of the two ports on the installed Qlogic HAB card.

This is also useful in finding the Model number, Firmwar version FCode, supported and current speeds and the port status of the HBA card/port.

root@ sunserver:/root# fcinfo hba-port | grep WWN
HBA Port WWN: 2100001b32xxxxxx
Node WWN: 2000001b32xxxxxx
HBA Port WWN: 2101001b32yyyyyy
Node WWN: 2001001b32yyyyyy

For detailed info including Make & model number, Firmware, Fcode and current status and supported/current speeds then

root@ sunserver:/root# fcinfo hba-port
HBA Port WWN: 2100001b32xxxxxx
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 4.04.01
FCode/BIOS Version:  BIOS: 1.24; fcode: 1.24; EFI: 1.8;
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 2000001b32xxxxxx
HBA Port WWN: 2101001b32yyyyyy
OS Device Name: /dev/cfg/c3
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 4.04.01
FCode/BIOS Version:  BIOS: 1.24; fcode: 1.24; EFI: 1.8;
Type: unknown
State: offline
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: not established
Node WWN: 2001001b32yyyyyy

Using scli

root@ sunserver:/root# scli -i | egrep “Node Name|Port Name”
Node Name                  : 20-00-00-1B-32-XX-XX-XX
Port Name                  : 21-00-00-1B-32-XX-XX-XX
Node Name                  : 20-01-00-1B-32-YY-YY-YY
Port Name                  : 21-01-00-1B-32-YY-YY-YY

For more detailed info on the HBA Cards run as follows: Similar to fcinfo but also provides Model Name and serial number.

root@ sunserver:/root# scli -i
——————————————————————————
Host Name                  : sunserver
HBA Model                  : QLE2462
HBA Alias                  :
Port                       : 1
Port Alias                 :
Node Name                  : 20-00-00-1B-32-XX-XX-XX
Port Name                  : 21-00-00-1B-32-XX-XX-XX
Port ID                    : 11-22-33
Serial Number              : AAAAAAA-bbbbbbbbbb
Driver Version             : qlc-20080514-2.28
FCode Version              : 1.24
Firmware Version           : 4.04.01
HBA Instance               : 2
OS Instance                : 2
HBA ID                     : 2-QLE2462
OptionROM BIOS Version     : 1.24
OptionROM FCode Version    : 1.24
OptionROM EFI Version      : 1.08
OptionROM Firmware Version : 4.00.26
Actual Connection Mode     : Point to Point
Actual Data Rate           : 2 Gbps
PortType (Topology)        : NPort
Total Number of Devices    : 2
HBA Status                 : Online
——————————————————————————
Host Name                  : sunserver
HBA Model                  : QLE2462
HBA Alias                  :
Port                       : 2
Port Alias                 :
Node Name                  : 20-01-00-1B-32-YY-YY-YY
Port Name                  : 21-01-00-1B-32-YY-YY-YY
Port ID                    : 00-00-00
Serial Number              : AAAAAAA-bbbbbbbbbb
Driver Version             : qlc-20080514-2.28
FCode Version              : 1.24
Firmware Version           : 4.04.01
HBA Instance               : 3
OS Instance                : 3
HBA ID                     : 3-QLE2462
OptionROM BIOS Version     : 1.24
OptionROM FCode Version    : 1.24
OptionROM EFI Version      : 1.08
OptionROM Firmware Version : 4.00.26
Actual Connection Mode     : Unknown
Actual Data Rate           : Unknown
PortType (Topology)        : Unidentified
Total Number of Devices    : 0
HBA Status                 : Loop down

Using prtconf

root@ sunserver:/root# prtconf -vp | grep -i wwn
port-wwn:  2100001b.32xxxxxx
node-wwn:  2000001b.32xxxxxx
port-wwn:  2101001b.32yyyyyy
node-wwn:  2001001b.32yyyyyy

Using prtpicl

root@ sunserver:/root# prtpicl -v | grep wwn
:node-wwn  20  00  00  1b  32  xx  xx  xx
:port-wwn  21  00  00  1b  32  xx  xx  xx
:node-wwn  20  01  00  1b  32  yy  yy  yy
:port-wwn  21  01  00  1b  32  yy  yy  yy

Using luxadm

Run the following command to obtain the physical path to the HBA Ports

root@ sunserver:/root$ luxadm -e port
/devices/pci@400/pci@0/pci@9/SUNW,qlc@0/fp@0,0:devctl              CONNECTED
/devices/pci@400/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0:devctl            NOT CONNECTED

With the physical path obtained from the above command, we can trace the WWN numbers as follows. here I use the physical path to the one that is connected:

root@ sunserver:/root$ luxadm -e dump_map /devices/pci@400/pci@0/pci@9/SUNW,qlc@0/fp@0,0:devctl
Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
0    123456  0         1111111111111111 2222222222222222 0×0  (Disk device)
1    789123  0         1111111111111111 2222222222222222 0×0  (Disk device)
2    453789  0         2100001b32xxxxxx 2000001b32xxxxxx 0×1f (Unknown Type,Host Bus Adapter)

Hope this helps. If you know of any more way then please feel free to post it to the comments and I shall amend it to the article.

To simply display the number of Physical processors, simply run the command with the -p option as follows:

root@sunserver # psrinfo -p
2

where 2 implies that there are 2 physical processors installed on the system.

If you would like to check the number of Virtual Processors on each of these Physical processors then type the command with the “-pv” arguement as follows:

root@ server:/root$ uname -a

SunOS server 5.10 Generic_137111-02 sun4v sparc SUNW,SPARC-Enterprise-T5120

root@server:/root$ psrinfo -pv

The physical processor has 32 virtual processors (0-31)

  UltraSPARC-T2 (cpuid 0 clock 1165 MHz)

The above indicates that there was only one physical processor (UltraSPARC-T2) on the T5120 server which has 32 Virtual processors. Each virtual processor is an entity with its own interrupt ID, capable of executing independent threads.

In simple terms, the number of Virtual Processors supported by a physical CPU is

“Number of Core” x “Number of threads”

For instance, the above is on a T5120 server with the UltraSPARC-T2. This CPU  has 4 cores and each core can support 8 threads and that gives us 32 Virtual processors.

The number of Virtual processors on a Server is simply the total Virtual processors supported on each of the physical processor.

In the following T5140 server there are 2 Physical UltraSPARC-T2+ processors with 6 cores, each supporting 8 threads which means we get 48 Virtual processors per Physical processor and hence a total of 96 Virtual processors (sum of VPs on individual processors) for the server:

root@ bserver:/root$ uname -a

SunOS bserver 5.10 Generic_137111-02 sun4v sparc SUNW,T5140

root@ bserver:/root$ psrinfo -pv

The physical processor has 48 virtual processors (0-23 32-55)

  UltraSPARC-T2+ (cpuid 0 clock 1167 MHz)

The physical processor has 48 virtual processors (64-71 80-119)

  UltraSPARC-T2+ (cpuid 64 clock 1167 MHz)

In earlier versions of Solaris, the -p arguement is not supported and hence wouldn’t provide this summarised output on the counts of the physical and Virtual CPUs.

For instance, in the following crontab file there is a blank line between the last two cron jobs.

root@sunsolaris# crontab -l
# The root crontab should be used to perform accounting data collection.
#
# The rtc command is run to adjust the real time clock if and when
# daylight savings time changes.
#
10 1 * * 0,4 /etc/cron.d/logchecker
10 2 * * 0  /usr/lib/newsyslog
15 3 * * 0 /usr/lib/fs/nfs/nfsfind

30 4 * * * /usr/local/bin/disk_check,sh
;;;;
;;;
;;
;

To resolve the problem edit the crontab file and look for the blank line and delete the line. In the above, after editing the crontab, it should look lie the follows:

root@sunsolaris# crontab -l
# The root crontab should be used to perform accounting data collection.
#
# The rtc command is run to adjust the real time clock if and when
# daylight savings time changes.
#
10 1 * * 0,4 /etc/cron.d/logchecker
10 2 * * 0  /usr/lib/newsyslog
15 3 * * 0 /usr/lib/fs/nfs/nfsfind
30 4 * * * /usr/local/bin/disk_check,sh
;;;
;;
;

You can see the  blank line removed from the crontab file.

Following procedure should help you mount an ISO image in Sun Solaris

Attach a Block Device

sunsolaris# lofiadm -a /export/software/iso_image.iso
/dev/lofi/1

Mount the ISO Image block device

sunsolaris# mount -F hsfs -o ro /dev/lofi/1 /mnt

Where /mnt is the mount point.

This should mount the ISO image.

To confirm, change directory to /mnt and do a “ls” to lis the files

sunsolaris# cd /mnt

sunsolaris# ls

if at anytime, you want to look at these block devices simply type “lofiadm” command with no arguement.

sunsolaris# lofiadm
Block Device File
/dev/lofi/1 /export/software/iso_image.iso

When we are done with the files on the mounted ISO, we can unmount and detach the Block device we attached earlier:

sunsolaris# umount /mnt

sunsolaris# lofiadm -d /dev/lofi/1

For instructions on how to mount an ISO image in Linux, click here

There are also more convenient tools to make a Screenshot. You should use more reliable import (part of ImageMagick package) instead of xwd.

To Take Screenshot of a Frame

When logged onto the CDE, open a terminal session and run the command as follows:

sunsolaris# xwd -frame > screenshot.xwd

This will prompt you to select a window (the cursor becomes a +), then it will take a picture of the window (as it appears on the screen), the “-frame” options will have it also include the window managers decorative borders, then the file is converted to png.

Fullscreen Screenshot

A full screen screenshot can be done without any frame being set

sunsolaris# xwd -root > screenshot.xwd

Screenshot and Convert togethor

sunsolaris# xwd -frame | convert xwd:- screenshot.png

Screenshot after “n” seconds

Now, comes the interesting bit, you can take screenshots after a delay time (say 10 seconds). All you do is to use a sleep command as follows

sunsolaris# sleep 10; xwd -root -out screenshot.xwd

To print the image captured using Laserjet

xpr -device ljet /tmp/myimage | lp -d printer

where “printer” is the installed printer.

This file can now be converted to PNG, JPG,GIF using GIMP or any other image editing software.

Sun Solaris has the psradm utility which allows enabling or disabling a Processor on the system. The psradm utility changes the operational status of processors. The legal states for the processor are on-line, offline, spare, Faulted, and no-intr. An online processor processes LWPs (lightweight  processes) and can be interrupted by I/O devices in the system.

To enable or disable a processor on the system we need to know the Processor ID. This can be found using the psrinfo utility as follows:

sunsolaris# psrinfo
0       on-line   since 05/09/2008 19:41:32

where 0 is the processor ID.

To know the path of the psradm command

sunsolaris# which psradm
/usr/sbin/psradm

To disable a processor

sunsolaris# psradm -f 0

where ‘0′ is the processor ID and ‘-f’ indicates the processor is taken offline (disable)

To enable a processor

sunsolaris# psradm -n 0

where ‘0′ is the processor ID and ‘-n’ indicates the processor is brought online (enable)

Using psrinfo

psrinfo displays more detailed information of the Processors including the number of Physical processors on the system and the number of virtual processors on the system. Each virtual processor is in its own a seperate entity.

Run psrinfo as root without arguments gives a quick summary of the processors with its IDs and the time since online.

# which psrinfo
/usr/sbin/psrinfo

sunsolaris# psrinfo
0       on-line   since 05/09/2008 19:41:32

For a more detailed output use the verbose option. This gives much more detailed information including processor type, operating speed etc for every available processor.

sunsolaris# psrinfo -v
Status of virtual processor 0 as of: 05/09/2008 20:05:34
  on-line since 05/09/2008 19:41:32.
  The i386 processor operates at 2000 MHz,
        and has an i387 compatible floating point processor.
       
Using prtiag

This can once again give a summarised information on the processor version and its ID.

sunsolaris# which prtdiag
/usr/sbin/prtdiag

sunsolaris# prtdiag
System Configuration: VMware, Inc. VMware Virtual Platform
BIOS Configuration: Phoenix Technologies LTD 6.00 04/17/2006

==== Processor Sockets ====================================

Version                          Location Tag
——————————– ————————–
Pentium(R) Pro                   CPU socket #0

…..
….

Using prtconf

Based on the installed drivers, you can find the information on the CPUs on the system.

sunsolaris# which prtconf
/usr/sbin/prtconf

sunsolaris#prtconf
System Configuration:  Sun Microsystems  i86pc
Memory size: 512 Megabytes
System Peripherals (Software Nodes):
…
..
…
cpus (driver not attached)
      cpu, instance #0 (driver not attached)

Not much information on my solaris 10 system running on a virtual server.