News, tips, partners, and perspectives for the Oracle Solaris operating system

Solaris CAT 5.1 Release

As promised, we'll be releasing Solaris Crash Analysis Tool updates every six months or so.  Yes!  The final release process for Solaris CAT 5.1 is reaching its end and you'll soon be able to download the latest and greatest bits. Come back here on Feb 15th and you'll likely see the release announcement.

Though this release mostly addresses bugs and added functionality to support the latest changes in the Nevada/OpenSolaris kernel there are a few new features.  Here's the release notes:


Solaris 2.4, 2.5, and 2.5.1 Support

This version of Solaris CAT no longer supports Solaris 2.4, 2.5, or 2.5.1.
Please use the 5.0 version of the tool if support for those Solaris
releases is required.

FMRI Reporting

In Solaris Nevada/OpenSolaris build 86 and up, the FMRI string for the SMF
service is maintained with each proc.
Therefore, the FRMI string for that service is now
displayed with the command name for all threads and procs.

Solaris Volume Manager Scans for Active Data Set

On Solaris 9 and up, the svm command now scans for a MD set that has active devices.
This means that the command increments the set it is using until it finds a set that contains metadevices.
The command will start with the set defined, 0 by default. The command displays a message when the set number is changed.
For example:

SolarisCAT(vmcore.14/10U)> svm
Solaris Volume Manager Status (md_status):
MD_GBL_DAEMONS_LIVE (Master daemon has been started)
MD_GBL_OPEN (Administration is open)
Active Metadata Set(s):
Set Address Name Status
SVM's md_set 0 is empty, trying set 1 instead.
d0 (ms_unit @ 0x6001468c8c8) (md_set 1) Concat/Stripe
actual # blocks: 113207296 (53.9G)
Unit Status: Okay
Stripe 0:
Device Starting Block State
239(did),96 0 Okay

New Commands



This new command displays the cyclic at the address specified. That
address is sometimes referred to as a cyclic_id.

This command ONLY works on Solaris 9+.



This new command displays kernel list_t linked lists and the
structures linked by them. The address provided needs to be the address of a
list_t structure. This is often embedded in other structures.
In those cases, the offset into the structure of the list_t should be added
to the structure address for printing.

This command ONLY works with CTF data.

Interface Changes


This command was substantially changed in its command-line interface for
consistency, and consistency with the kernel code.

By default, all tables are displayed. Instead of the rt and
ts options, there are now the flags -r for selecting
the realtime callouts and -n for selecting the normal callouts.

Options were added to include relevant structure addresses (-a),
to decode the callout's argument into the thread or process it represents
(-t) or to display only expired callouts (-e).

Finally, an option was added to display only a specified callout. The
callout is selected using its XID.

scat --sanity_checks

The new command line argument --sanity_checks can be used to run a quick
check of a running system or crash dump file. The intent is to allow easy access to
these extensive checks without having to run Solaris CAT interactively.

scat --scat_explore

In release 5.1, one can now run scat_explore in a quasi standalone mode
using the --scat_explore option to scat.
For customers who open a Sun Service Request, crash data can now be gathered and transmitted
to Sun using the send_scat_explore command.
The syntax for send_scat_explore is:

send_scat_explore [-n service_number] [-e email_address] [unix.x] vmcore.x


  • -n service_number - sets the Sun Service Request number to assign to the crash data
  • -e email_address - sets the reply-to email address that Sun should used to acknowledge
    the receipt of the data.
  • [unix.x] vmcore.x -the crash dump from which crash data should be gathered.
    Please note that unix.X need not be supplied and the core number, X, can be specified with
    or without the vmcore. prefix.

If the above -n and -e options are not specified
the user is promted for them at run time.

If the system in question is not configured to send email directly to Sun, the crash data can be collected manually
using scat --scat_explore. The scat_explore feature will print the name
of the dirctory in which the data was placed and will also place in that directory a compressed
tar archive of the crash data.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.