Sun Solaris System Admin

Install Sybase Perl module in Solaris 10

admin — Thu, 15 Oct 2009 22:01:53 +0000

Installing Perl modules in Sun Solaris is not as straight forward but is not very difficult as well. Perl module installations in Sun Solaris needs GNU Make rather than the default make tool installed. And, requires using perlgcc to build the Makefile.PL than the default perl binary.

Installing Sybase Perl Module requires the following preinstalled

1. Sybase Server/Client already installed on your server
2. GNU Make

Install GNU Make

Assuming you have already installed Sybase Server/Client on your system, lets download and install GNU Make.

GNU Make package can be downloaded from sunfreeware.com website. At the time of writing, the version available for download is Make 3.81

Download GNU Make for Solaris 10 (SPARC)

Download Make for Solaris 10 (x86)

Unzip and Install GNU Make

From the directory where the file is downloaded

# gunzip make-3.81-sol10-x86-local.gz
# pkgadd -d make-3.81-sol10-x86-local

This should install “make” under /usr/local/bin

# which make
/usr/local/bin/make

Download Perl Modules from www.cpan.org. The modules we are interested in are

1. DBI (Database Independent Interface for Perl)

2. DBD::Sybase (Sybase database Driver for the DBI module)

NOTE: I find in Solaris 10 Update 6, DBI module is already installed which means we only need to install DBD::Sybase module.

To verify either of the modules is already installed on the system,

For DBI, file DBI.pm should exist under

x86

/usr/perl5/vendor_perl/5.8.4/i86pc-solaris-64int/DBI.pm

SPARC

/usr/perl5/site_perl/5.8.4/sun4-solaris-64int/DBI.pm

For DBD::Sybase

x86

/usr/perl5/site_perl/5.8.4/i86pc-solaris-64int/DBD/Sybase.pm

SPARC

/usr/perl5/site_perl/5.8.4/sun4-solaris-64int/DBD/Sybase.pm

Now, assuming both these modules are not installed

Install Perl DBI Module

Download the DBI Module from here

From the download directory,

# gunzip DBI-1.609.tar.gz
# tar -xvf DBI-1.609.tar
# cd DBI-1.609

The above steps should (g)unzip, untar the downloaded source files.

Export $SYBASE & $LD_LIBRARY_PATH environment variables. We have the Sybase client installed under

/opt/sybase/oc15.0-EBF16084/OCS-15_0

which means the libraries exist under

/opt/sybase/oc15.0-EBF16084/OCS-15_0/lib

# export SYBASE=/opt/sybase/oc15.0-EBF16084/OCS-15_0
# export LD_LIBRARY_PATH=/opt/sybase/oc15.0-EBF16084/OCS-15_0/lib:$LD_LIBRARY_PATH

If this step is skipped, the following error comes up in the next step:

Can’t find the lib directory under /export/home/sybase! at Makefile.PL line 118, line 44.

Now comes the tricky bit, use /usr/perl5/bin/perlgcc instead of default perl as follows:

# /usr/perl5/bin/perlgcc Makefile.PL

Let’s now compile and install using GNU Make from source directory

# /usr/local/bin/make
# /usr/local/bin/make test
# /usr/local/bin/make install

To make sure the install compelted successfully. Check if the DBI.pm file exists as shown earlier.

Install Perl DBD::Sybase module

Download DBD::Sybase perl module from here.

From the downloaded directory:

# gunzip DBD-Sybase-1.09.tar.gz
# tar -xvf DBD-Sybase-1.09.tar
# cd DBD-Sybase-1.09

The above should (g)unzip, untar the downloaded file and change into the source directory.

Export the $SYBASE & $LD_LIBRARY_PATH environment variables if you have already not done so.

# export SYBASE=/opt/sybase/oc15.0-EBF16084/OCS-15_0
# export LD_LIBRARY_PATH=/opt/sybase/oc15.0-EBF16084/OCS-15_0/lib:$LD_LIBRARY_PATH

Run perlgcc against the Makefile.PL as follows:

# /usr/perl5/bin/perlgcc Makefile.PL

Select the default CHAIN mode or modify as required, then enter the Sybase Server, a Sybase Username and password and a Database as and when promted. This will allow the installation test connection. Make sure this DB connection is updated in the Sybase “interfaces” file.

NOTE: Once the installation is completed. Either the PWD file created by this procedure or the entire Source directory should be deleted as the PWD file will contain these DB access details. Also, it is advisable to provide a test DB access detail rather than a live environment.

Let’s now compile and install using GNU Make from source directory

# /usr/local/bin/make

Now, re-export $SYBASE as follows:

# export SYBASE=/opt/sybase/oc15.0-EBF16084

[NOTE: This may vary in your environment]

# /usr/local/bin/make test
# /usr/local/bin/make install

This should install the Sybase Perl module. To confirm the installation was successful, look for Sybase.pm as explained earlier.

How to find the package which installed a file

admin — Tue, 25 Aug 2009 17:25:35 +0000

If you have a file and need to know the package that installed the file on the system then the following procedure using “pkgchk” should help.

Let’s look at the “which” utility in Solaris and find which package installed the file.

The file path for which is /usr/bin/which

# which which
/usr/bin/which

To find the package which installed it use the “pkgchk” command with the “-l” “and -p” options and the full file path of the file as follows,

# pkgchk -l -p /usr/bin/which
Pathname: /usr/bin/which
Type: regular file
Expected mode: 0555
Expected owner: root
Expected group: bin
Expected file size (bytes): 1288
Expected sum(1) of contents: 25204
Expected last modification: Jan 21 23:32:39 2005
Referenced by the following packages:
SUNWcsu

You can see that the which utility is installed by the package “SUNWcsu”.

How to find list of files installed by a package

admin — Tue, 25 Aug 2009 17:20:32 +0000

“pkginfo” command can be useful in Solaris to give a detailed listing of a package including the details of number of installed files, pathnames, directories and executables as follows:

# pkginfo -l SUNWlibgcrypt
PKGINST: SUNWlibgcrypt
NAME: Libgcrypt – Cryptographic Library
CATEGORY: EVO146,application,JDS3
ARCH: sparc
VERSION: 1.1.12,REV=10.0.3.2004.12.15.17.57
BASEDIR: /usr
VENDOR: Sun Microsystems, Inc.
DESC: Libgcrypt – Cryptographic Library
PSTAMP: fire420041215175708
INSTDATE: Sep 15 2008 12:08
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 6 installed pathnames
2 shared pathnames
2 directories
2 executables
595 blocks used (approx)

But, if you want to see what those files and directories are then “pkgchk” should be your toy. The following should show the list of files and pathnames installed by the package:

# pkgchk -l SUNWlibgcrypt|egrep “Pathname|Type”
Pathname: /usr/bin
Type: directory
Pathname: /usr/bin/libgcrypt-config
Type: regular file
Pathname: /usr/lib
Type: directory
Pathname: /usr/lib/libgcrypt.so
Type: symbolic link
Pathname: /usr/lib/libgcrypt.so.1
Type: symbolic link
Pathname: /usr/lib/libgcrypt.so.1.5.1
Type: regular file

OBP Error: FATAL: system is not bootable, boot command is disabled

admin — Wed, 29 Jul 2009 19:03:32 +0000

When you run any boot command like “boot net” or “boot -s” from the OK prompt (OBP), you may end up with the error

FATAL: system is not bootable, boot command is disabled

Don’t panic!!!

This error indicates that interrupted the boot process prematurely, most likely when the memory checks were run with “STOP + A” or a break from console.

To resolve this problem simply Power OFF and power ON the system. Alternatively, you can perform a “reset-all” from the OK prompt.

This should help!

How to remove ^M characters from file in Unix/Solaris

admin — Tue, 21 Jul 2009 19:12:43 +0000

When you sometimes copy a file from Windows to UNIX/Solaris or even Linux systems, you can find these anooying ^M characters everywhere. This is because, the file from Windows is in DOS (ASCII) format and needs to be converted to ISO format.

There are many ways to do this. Let’s start with the easy one look at each of them

1. Use dos2unix utility

Solaris pre-installs dos2unix utility into the system to do this job for you. As the name says, it converts the file from DOS format to UNIX format. To do this the syntax is

# dos2unix

for instance

# dos2unix test.txt test2.txt

Where the test.txt is the file you want the ^M characters removed and test2.txt is the file stripped of the ^M characters.

You may also overwrite the existing file by mentioning the source and destination files as same:

# dos2unix test.txt test.txt

2. Using VI

Open the file with “vi” editor and type the following:

:%s/^M//g

NOTE: To get the ^M in there, you should type CTRL+V+M

3. Using “tr” utility

“tr” utility is used to translate characters. Using with “-d” deletes a listed string.

# tr -d ‘\r’ >

Alternatively, use its octel representation as follows:

# tr -d ‘\015′

dladm – Display Link status,speed,duplex,statistics,MTU

admin — Fri, 19 Jun 2009 18:45:10 +0000

In the past we have to mess around with the NDD commands and stats tools like kstat to find the network link status, speed, duplex information in Sun Solaris. With Solaris 10, this has become much easier with the dladm utility.

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

Find Chasis Serial Number using sneep

admin — Fri, 19 Jun 2009 18:32:29 +0000

sneep (Serial Number in EEPROM) is a cool utility for Solaris that can retreive the Chasis Serial Number (CSN) or the Product Serial Number (PSN). This comes real handy when taking inventory or when having to work with Sun Support. sneep can also store useful information like system Assett Tag or Location into the EEPROM which can be retreived later on.

Sneep searches for the serial number in several data sources, including the system eeprom, platform-specific hardware-based sources, the configuration      files for the Sun “explorer“ and “Configuration Service Tracker (CST)” tools, and its own backup file. This order of searched can be altered.

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

PCP script to find open TCP ports and PIDs related in Solaris

admin — Tue, 12 May 2009 22:35:00 +0000

PCP is a very useful security and adminitration script that can help you quickly find Processes (PIDs) having particular TCP Port(s) open, TCP ports open by specific PIDs or even list all the TCP Ports open by all PIDs running on your system.

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

How to find the WWN (World Wide Name) in Sun Solaris

admin — Tue, 10 Feb 2009 22:57:05 +0000

World Wide Name (WWN) are unique 8 byte (64-bit) identifiers in SCSI or fibre channel similar to that of MAC Addresses on a Network Interface Card (NIC).

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.

psrinfo – Find number of Physical & Virtual Processors in Solaris 10

admin — Sat, 03 Jan 2009 01:54:53 +0000

In Solaris 10, if you want to find the processor type and the number of physical processors installed on the system and the number of Virtual Processors available on the system then the psrinfo command does job for you.

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.