ASGAUR

You can to use the /usr/contrib/Q4/bin/q4 utility.

cd /var/adm/crash/crash.0

# /usr/contrib/Q4/bin/q4 -p .
(note the "dot" at the end of the command)

At the q4> prompt,

type:q4> run Analyze AU > ana.out q4> run WhatHappened -HANG > what.out

NOTE:  ctrl-c can interrupt these two commands,

which may take several minutes to process.

To exit q4:q4> exit

A quick guide to extend an LVM with a VXFS Filesystem.

1. Verify OnLineJFS is installed
# swlist -l product | grep -i vxfs
# swlist -l product | grep -i online
Look for OnlineJFS or AdvJournalFS

2. It is a good practice to defrag the filesystem first before extending
# fsadm -d - D -e - E /mountpoint

3. Determine the Logical Volume where the filesystem is mounted.
# bdf /mountpoint
Example:

[root@gmhpux02:/root]
# bdf /var/adm/crash
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lv_crash 5357568 2266637 2897770 44% /var/adm/crash

4. Obtain the current size of the Logical Volume (Mbytes)
# lvdisplay /dev/volumegroup/logicalvolume
Example:

[root@gmhpux02:/root]
# lvdisplay /dev/vg00/lv_crash
--- Logical volumes ---
LV Name /dev/vg00/lv_crash
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 5232
Current LE 327
Allocated PE 654
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

5. Our current size is 5232 Mbytes. Let us say that we will extend the filesystem by 100 Mbytes. Get the sum of the current size and the size to be added. This will add to 5332 Mbytes. Take note of this.

6. Adjust the size of the Logical Volume.
# lvextend -L new_size_in_mbytes
Example:
[root@gmhpux02:/root]
# lvextend -L 5332 /dev/vg00/lv_crash
Logical volume "/dev/vg00/lv_crash" has been successfully extended.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf

7. Adjust the size of the Filesystem
# fsadm -b new_sizem /mountpoint
Example:
[root@gmhpux02:/root]
# fsadm -b 5332m /dev/vg00/rlv_crash
fsadm: /etc/default/fs is used for determining the file system type
UX:vxfs fsadm: INFO: V-3-23585: /dev/vg00/rlv_crash is currently 524288 sectors - size will be increased

8. Verify new size of the filesystem
# bdf /mountpoint

A World Wide Name (WWN) or World Wide Identifier (WWID) is a unique identifier which identifies a particular Fibre Channel, Advanced Technology Attachment (ATA) or Serial Attached SCSI (SAS) target. Each WWN is an 8 byte number derived from an IEEE OUI and vendor-supplied information.

There are two formats of WWN defined by the IEEE:

• Original format: addresses are assigned to manufacturers by the IEEE standards committee, and are built into the device at build time, similar to an Ethernet MAC address. First 2 bytes are either hex 10:00 or 2x:xx (where the x's are vendor-specified) followed by the 3-byte vendor identifier and 3 bytes for a vendor-specified serial number
• New addressing schema: first nibble is either hex 5 or 6 followed by a 3-byte vendor identifier and 36 bits for a vendor-specified serial number

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@ Solaris:/root# fcinfo hba-port | grep WWN
HBA Port WWN: 4800001b32xxxxxx
Node WWN: 2000001b32xxxxxx
HBA Port WWN: 4801001b32yyyyyy
Node WWN: 2001001b32yyyyyy

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

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

Using scli

root@ Solaris:/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@ Solaris:/root# scli -i
——————————————————————————
Host Name                  : Solaris
HBA Model                  : QLE2460
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              : 2.0
Firmware Version           : 4.04.01
HBA Instance               : 2
OS Instance                : 2
HBA ID                     : 2-QLE2460
OptionROM BIOS Version     : 2.0
OptionROM FCode Version    : 2.0
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                  : Solaris
HBA Model                  : QLE2460
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              : 2.0
Firmware Version           : 4.04.01
HBA Instance               : 3
OS Instance                : 3
HBA ID                     : 3-QLE2460
OptionROM BIOS Version     : 2.0
OptionROM FCode Version    : 2.0
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@ Solaris:/root# prtconf -vp | grep -i wwn
port-wwn:  4800001b.32xxxxxx
node-wwn:  2000001b.32xxxxxx
port-wwn:  4801001b.32yyyyyy
node-wwn:  2001001b.32yyyyyy

Using prtpicl

root@ Solaris:/root# prtpicl -v | grep wwn
:node-wwn  20  00  00  1b  32  xx  xx  xx
ort-wwn  21  00  00  1b  32  xx  xx  xx
:node-wwn  20  01  00  1b  32  yy  yy  yy
ort-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@ Solaris:/root$ luxadm -e port
/devices/pci@200/pci@0/pci@9/SUNW,qlc@0/fp@0,0:devctl              CONNECTED
/devices/pci@200/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@ Solaris:/root$ luxadm -e dump_map /devices/pci@200/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         4800001b32xxxxxx 2000001b32xxxxxx 0×1f (Unknown Type,Host Bus Adapter)

POLICY DOMAIN - This is a container for policy and scheduling info
*BACKRETention* is a fallback value for any files which
have been backed up under the specified policy domain,
but for which there is now a lack of an active policy
set.
*ARCHRETention* is a fallback value for any files which
have been archived under the specified policy domain,
but for which there is now a lack of an active policy
set.

POLICY SET - This is a set of management classes within a POLICY
DOMAIN.
Only the active version has any effect.  The active
version is created by issuing ACTIVATE POLICYSET
<set-name-you-made>.
After activating, you may edit the original set without
affecting the active copy.

MANAGEMENT CLASS - This is a classification for particular sets
of objects.  Minimal set to be bound is an entire
archive for archiving (ARCHMC option) or a single file,
directory,  filespace or everything for a backup
(INCLUDE option).
There can be many management classes per policy set,
but only ones in the active policy set may be
referenced
**The additional parameters for this structure are used
only for HSM migration.

BACKUP COPYGROUP - This is the structure which defines
retention of backup data.  These settings are the most
confusing because their operation overlaps and may
require some to be set to "NOLIMIT" to attain the
desired effect.

*VERSIONS DATA EXISTS* - This value specifies the maximum
number of versions of a file which may be retained.
If this is exceeded by additional backups or imports,
then the next expiration run on the server will remove
the oldest versions until there are only this many
left.
**This may be "NOLIMIT" or a whole number.

*RETAIN EXTRA VERSIONS* - This value specifies the maximum
number of days to retain an inactive copy when there is
an active copy in the database.
**This may be "NOLIMIT" or a whole number.

*RETAIN ONLY VERSION* - This value specifies the maximum
number of days to retain the only inactive version of
a file once there are no active versions.
**This may be "NOLIMIT" or a while number.
**This does not affect active copies which are always
retained.

*VERSIONS DATA DELETED* - This is the maximum number of
inactive versions of a file to retain once the file no
longer has an active version.

*DESTINATION* - This specifies the storage pool to which
newly backed up data will go if it is bound to this
management class during backup.
**Rebound data will not move to a new pool
automatically.
**Data may be moved from this pool through migration or
MOVE DATA commands.

Archive Copygroup - This is the structure which defines
retention of archive data.

*RETAIN VERSION* - This is the only retention parameter
for archives, and is the number of days that the entire
archive will be kept.

*DESTINATION* - This specifies the storage pool to which
newly archived data will go if it is bound to this
management class during archive operation.
**Rebound data will not move to a new pool
automatically.
**Data may be moved from this pool through migration or
MOVE DATA commands.

Schedule - This is a time/date/frequency setting for when commands
may be automatically run by the tsm server either on the
tsm server (administrative) or on the tsm client (client).

Client Association - a separate entity that binds clients to schedules.

Node - A separate entity which defines a client and allows access.




-------
CAVEATS
-------

NOTE: Once an archive is made, it may not be rebound.  In otherwords,
you may not specify a different management class for it. It IS possible
to change the copy-group retention period for this management class, and
then re-activate the policyset.  This will change it's retention;
however, be cautious with this, as you will affect ANY data in the same
management class.

NOTE: Management classes with the same name but which are within a
different policy domain will NOT conflict with eachother.

NOTE: Changes to a policy set will NOT have ANY effect unless that
policy set is copied into the active policy set with ACTIVATE POLICYSET.
Only the active policyset, and not it's source policyset or any other,
will have an effect.

NOTE: Active versions are converted to inactive only by the client,
through client-side expiration.  See the particular client code manual
for details. This may happen during a backup with an exclude list, or
during a backup with missing files, or through an API call to expire the
object.

NOTE: There are other parameters for all of these structures.  Please
see the ADSM/TSM Administrator's Reference Guide for details.



-------
EXAMPLE
-------

Backup copygroup is set as follows:
VDE = 3
VDD = 1
RETEX = 100
RETO = 1

Explaination:
- Versions 1 through three are kept up to 100 days FROM WHEN THEY
WERE BACKED UP.
- Any versions past 3 will be expired immediately upon the next
server-side EXPIRE INVENTORY process.
- NOTE: NO MORE THAN THREE VERSIONS WILL BE KEPT AFTER EXPIRE
INVENTORY, REGARDLESS OF THE NUMBER OF DAYS SPECIFIED IN
RETAIN-EXTRA AND RETAIN-ONLY!
- If the active version is made inactive (client side expiration),
then only the most recent copy will be kept, and it will only
be kept for one day FROM WHEN IT WAS BACKED UP.

-------
EXAMPLE
-------

Backup copygroup is set as follows:
VDE = NOLIMIT
VDD = NOLIMIT
RETEX = 14
RETO = 20

Explaination:
- All versions will be kept for 14 days FROM WHEN THEY ARE BACKED UP.
- When no active version remains (client-side expiration), the last
inactive version will be kept for 20 days FROM WHEN BACKED UP.


-------
EXAMPLE
-------

Backup copygroup is set as follows:
VDE = 5
VDD = 0
RETEX = NOLIMIT
RETO = NOLIMIT

Explaination:
- 5 versions will be kept while an active copy exists.
- Files will not expire by age.
- When the active version is made inactive, the next EXPIRE INVENTORY
will remove ALL versions of the file.

How to Check Solaris Kernel bit (32 bit/64 bit)

To check if Solaris kernel is running in 32 bit mode or 64 bit from command line run the following:

# /usr/bin/isainfo –kv

64-bit sparcv9 kernel modules

The output "64 bit sparcv9" indicates that Solaris kernel is running in 64 bit mode. Here is the output of Solaris kernel running in 32 bit:

# /usr/bin/isainfo –kv

32-bit sparcv9 kernel modules

How to check Solaris kernel on x86 (Intel) platform :

# uname –m

i86pc

# /usr/bin/isainfo -kv

32-bit i386 kernel modules

In the example above Solaris Kernel is running in 32 bit on intel platform, printed as "32-bit" in the output.

How to check if Solaris kernel is configured to boot in 32 bit or 64:

The system is configured to boot the 64-bit kernel if the output from the eeprom command is either:

# /usr/sbin/eeprom | grep boot-file

boot-file: data not available

or

boot-file=kernel/sparcv9/unix

else if Solaris system is configured to boot using 32-bit kernel, the output from the eeprom command comes back as:

kernel/unix