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, <IN> 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.

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.

To confirm this behaviour

root@solarisserver# eeprom local-mac-address?
local-mac-address?=false

The output “local-mac-address?=false” indicates that the factory-default Mac-Address is not being used and a system-wide MAC-Address is used.

To make the NICs use their factory default MAC-Address set the “local-mac-address?” value to true.

root@solarisserver# eeprom local-mac-address?=true

This requires a reboot for the changes to take effect and hence reboot the server.

root@solarisserver# init 6

When the system comes back online, an “ifconfig -a” should show the NICs having individual MAC-Addresses. These are the factory default unique mac-addresses than the system-wide mac-addresses.

If however, if you find more than one interface still have same MAC-Address then it indicates that the NIC does not have a factory-default mac-address and hence will still use the system-wide mac-address.

In my previous write up here, I wrote a brief description of the Sun VTS (Validation and Test Suite) which can help one to run tests on any Sun Supported hardware and hardware components and report the health status and identify faulty devices. Now, lets get installing and run Sun VTS in Solaris 10.

Download the most recent stable version of SUNWvts (SUNWvts6.4ps2 at the time of writing this article) for SPARC/x86 platforms from here

NOTE: Requires Sunsolve login to download.

Sun VTS requires the following packages installed to run properly.

Core SunVTS Framework

SUNWvts_VTS6.4ps2_sparc.tar.Z (SPARC)

SUNWvts_VTS6.4ps2_x86.tar.Z (x86)

Sun VTS Tests

SUNWvtsts_VTS6.4ps2_sparc.tar.Z (SPARC)

SUNWvtsts_VTS6.4ps2_x86.tar.Z (x86)

SunVTS Framework Configuration Files in Root partition (Optional/Recommended)

SUNWvtsr_VTS6.4ps2_sparc.tar.Z

SUNWvtsr_VTS6.4ps2_x86.tar.Z
 
Sun VTS Man Pages (Optional)
SUNWvtsmn_VTS6.4ps1_sparc.tar.Z (SPARC)

SUNWvtsmn_VTS6.4ps1_x86.tar.Z (x86)

Prior to installation, it is important that any previous version of the above mentioned Sun VTS packages are removed.

To check if previous versions are installed

solaris10# pkginfo -l | grep -i vts

If found uninstall them before proceeding with the procedure

solaris10# pkgrm SUNWvts SUNWvtsr SUNWvtsts SUNWvtsmn

Download and install the latest revision of Microtasking libraries (libmtsk) patch for Solaris 10 from the following Sun Solve website:

http://sunsolve.sun.com/show.do?target=patchpage

Solaris 10 SPARC – 120753 (120753-05)

Solaris 10 x86 – 120754 (120754-05)

Download unzip and install the patch:

SPARC

solaris10# unzip 120753-05.zip

solaris10# patchadd 120753-05

x86

solaris10# unzip 120754-05.zip

solaris10# patchadd 120754-05

Now, lets get installing the Sun VTS packages.

Install SunVTS Core Framework (SPARC & x86)

solaris10#pkgadd -d . SUNWvts

That installs the required Sun VTS Core Framework package.

Install the rest of the SunVTS packages
(SunVTS Tests,config files in root & Man pages)

solaris10# pkgadd -d . SUNWvtsts SUNWvtsr SUNWvtsmn

That completes the Sun VTS package installation.

Enable the rstatd daemon

rstatd daemon is disabled by default in Solaris 10.

solaris10# svcadm enable rstatd

Export Display to your PC (GUI only)

solaris10# export DISPLAY 192.168.0.2:0

Start Sun VTS

solaris10# /opt/SUNWvts/bin/sunvts &

This should start the Sun VTS software and export GUI to your PC (if display not exported then runs tty user interface on the terminal). Sun VTS will discover devices and list available tests for your server with dezcriptive information on the server.

OpenSSH is a free opensource version of the SSH connectivity tools. OpenSSH encrypts all traffic (including passwords) to effectively eliminate eavesdropping, connection hijacking, and other attacks unlike Telnet,rlogin or ftp where the data is not encrypted and transmitted in plain text. Additionally, OpenSSH provides secure tunneling capabilities and several authentication methods, and supports all SSH protocol versions.

The easiest way to install OpenSSH in Sun Solaris is to use the pre-compiled packages from sunfreeware.

The following are the packages that are required to be installed for OpenSSH to work properly in Solaris 9:

OpenSSL (Latest stable: openssl-0.9.8f)

ZLib (Latest stable: zlib-1.2.3)

GNU Compiler Collection (gcc Latest stable: libgcc-3.4.6)

TCPWrapper (Optional tcp_wrappers-7.6)

and OpenSSH itself (Latest Stable: openssh-4.7p1)

To start of, download the packages from the following sunfreeware.com links Solaris 9 SPARC:

gcc

ftp://ftp.sunfreeware.com/pub/freeware/sparc/9/libgcc-3.4.6-sol9-sparc-local.gz

Zlib

ftp://ftp.sunfreeware.com/pub/freeware/sparc/9/zlib-1.2.3-sol9-sparc-local.gz

OpenSSL

ftp://ftp.sunfreeware.com/pub/freeware/sparc/9/openssl-0.9.8f-sol9-sparc-local.gz

OpenSSH

ftp://ftp.sunfreeware.com/pub/freeware/sparc/9/openssh-4.7p1-sol9-sparc-local.gz

Once done, upload the files onto the server so we can start to unzip the files and install.

Unzip and install gcc

solaris9# gunzip libgcc-3.4.6-sol9-sparc-local.gz

solaris9# pkgadd -d libgcc-3.4.6-sol9-sparc-local

…
…
Installation of <SMCgcc> was successful.

Unzip and install zlib

solaris9# gunzip  zlib-1.2.3-sol9-sparc-local.gz

solaris9# pkgadd -d zlib-1.2.3-sol9-sparc-local

…
…
Installation of <SMCzlib> was successful.

Unzip and install OpenSSL

solaris9# gunzip openssl-0.9.8f-sol9-sparc-local.gz

solaris9# pkgadd -d openssl-0.9.8f-sol9-sparc-local
…
…
Installation of <SMCossl> was successful.

Unzip and install OpenSSH

solaris9# gunzip openssh-4.7p1-sol9-sparc-local.gz

solaris9# pkgadd -d openssh-4.7p1-sol9-sparc-local
…
…
Installation of <SMCossl> was successful.

The packages are now installed.

Create /var/empty directory

solaris9# mkdir /var/empty

Change directory ownership to Root user and sys group

solaris9# chown root:sys /var/empty

Change permissions

solaris9# chmod 755 /var/empty

Add sshd user & group

solaris9# groupadd ssh

solaris9# # useradd -g sshd -c ‘sshd privsep’ -d /var/empty -s /bin/false sshd

Edit the default /usr/local/sshd_config file and make the following changes:

Replace the line

Subsystem sftp /usr/libexec/sftp-server

with

Subsystem sftp /usr/local/libexec/sftp-server

Generate Keys for the server

solaris9# ssh-keygen -t rsa1 -f /usr/local/etc/ssh_host_key -N “”
solaris9# ssh-keygen -t dsa -f /usr/local/etc/ssh_host_dsa_key -N “”
solaris9# ssh-keygen -t rsa -f /usr/local/etc/ssh_host_rsa_key -N “”

sshd at Solaris startup

Add a startup script /etc/init.d/sshd as follows to enable the OpenSSH server daemon “sshd” at the startup

case “$1″ in
‘start’)
        if [ -x /usr/local/sbin/sshd ]; then
                echo “Starting the secure shell daemon”
                /usr/local/sbin/sshd &
        fi
        ;;

‘stop’)
        echo “Stopping the secure shell daemon ”
        pkill -TERM sshd
        ;;
*)
        echo “Usage: /etc/init.d/sshd { start | stop }”
        ;;
esac
exit 0

Change the ownership & permissions on the startup script

solaris9# chown root:sys /etc/init.d/sshd
solaris9# chmod 555 /etc/init.d/sshd

Create a Symlink to the startup script at /etc/rc2/d/S98sshd

# ln -s /etc/init.d/sshd /etc/rc2.d/S98sshd

That is it. All done and ready to go. Try connecting to the server using a ssh client like PUTTY.