Feeds:
Posts
Comments

To find the current version of the ServeRAID device driver under Linux use the following.

Eg from IBM xSeries server

$ cat /proc/scsi/aacraid/0
Adaptec Raid Controller: 1.1-5[2434]custom-IBM
Vendor: IBM  Model: ServeRAID 8i
flags=SAI_READ_CAPACITY_16
kernel: 5.2-0[15421]
monitor: 5.2-0[15421]
bios: 5.2-0[15421]
serial: 83xxx

Use /usr/openv/volmgr/bin/scan command for tape drive details. Check the output to determine if all the drives are being reported correctly.

bash-3.00# /usr/openv/volmgr/bin/scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
————————————————————
Device Name  : “/dev/rmt/1cbn”
Passthru Name: “/dev/sg/c0tw500308c001611804l1”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : “IBM     ULTRIUM-TD2     5AT0”
Vendor ID  : “IBM     “
Product ID : “ULTRIUM-TD2     “
Product Rev: “5AT0”
Serial Number: “xxxxxxxxxx”
WWN          : “IBM     ULTRIUM-TD2     F00181100D”
WWN Id Type  : 1
Device Identifier: “IBM     ULTRIUM-TD2     F00181100D”
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
————————————————————
Device Name  : “/dev/rmt/0cbn”
Passthru Name: “/dev/sg/c0tw500308c001611804l2”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : “IBM     ULTRIUM-TD2     5AT0”
Vendor ID  : “IBM     “
Product ID : “ULTRIUM-TD2     “
Product Rev: “5AT0”
Serial Number: “xxxxxxxxxx”
WWN          : “IBM     ULTRIUM-TD2     F001811013”
WWN Id Type  : 1
Device Identifier: “IBM     ULTRIUM-TD2     F001811013”
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
————————————————————
Device Name  : “/dev/sg/c0tw500308c001611803l1”
Passthru Name: “/dev/sg/c0tw500308c001611803l1”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : “ADIC    Scalar i2000    402A”
Vendor ID  : “ADIC    “
Product ID : “Scalar i2000    “
Product Rev: “402A”
Serial Number: “ADIC205100785_LL0”
WWN          : “ADIC    205100785_LL0           “
WWN Id Type  : 1
Device Identifier: “ADIC    203100255_LL0           “
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 7
Number of Slots  : 72
Number of Media Access Ports: 12
Drive 1 Serial Number      : “xxxxxxxxx”
Drive 2 Serial Number      : “xxxxxxxxx”
Drive 3 Serial Number      : “xxxxxxxxx”
Flags : 0x0
Reason: 0x0
————————————————————
Device Name  : “/dev/rmt/3cbn”
Passthru Name: “/dev/sg/c0tw500308c001611803l2”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : “IBM     ULTRIUM-TD2     53Y2”
Vendor ID  : “IBM     “
Product ID : “ULTRIUM-TD2     “
Product Rev: “53Y2”
Serial Number: “xxxxxxxxxx”
WWN          : “IBM     ULTRIUM-TD2     F001811001”
WWN Id Type  : 1
Device Identifier: “IBM     ULTRIUM-TD2     F001811001”
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0

…truncated

Use /usr/openv/volmgr/bin/sgscan to detect tape drives

bash-3.00# /usr/openv/volmgr/bin/sgscan
#
#WARNING: detected StorEdge Network Foundation connected devices not in
#         SG configuration file:
#
#    Device World Wide Port Name 500000e01042ff61
#    Device World Wide Port Name 500000e0101fae61
#    Device World Wide Port Name 50800200001b7fa9
#
#    See /usr/openv/volmgr/MediaMgr_DeviceConfig_Guide.txt chapter
#    “Special configuration for “Sun StorEdge Network Foundation” HBA/Driver”
#    for information on how to use sg.build and sg.install to
#    configure these devices
#

/dev/sg/c0t6l0: Cdrom: “TOSHIBA DVD-ROM SD-M1401”
/dev/sg/c0tw500308c001611803l0: Array-controller: “ADIC    Scalar i2000”
/dev/sg/c0tw500308c001611803l1: Changer: “ADIC    Scalar i2000”
/dev/sg/c0tw500308c001611803l2: Tape (/dev/rmt/3): “IBM     ULTRIUM-TD2”
/dev/sg/c0tw500308c001611803l3: Tape (/dev/rmt/2): “IBM     ULTRIUM-TD2”
/dev/sg/c0tw500308c001611804l0: Array-controller: “ADIC    Scalar i2000”
/dev/sg/c0tw500308c001611804l1: Tape (/dev/rmt/1): “IBM     ULTRIUM-TD2”
/dev/sg/c0tw500308c001611804l2: Tape (/dev/rmt/0): “IBM     ULTRIUM-TD2”

Use /usr/openv/volmgr/bin/tpautoconf -report_disc command to report discrepancies between detected devices and the EMM database.

tpautoconf is normally used by the Device Configuration wizard to automatically discover and configure devices. The wizard calls tpautoconf with a different set of options.

#/usr/openv/volmgr/bin/tpautoconf -report_disc

=========== Missing Device or no local control path (Robot) ===========
Defined as robotic TLD(0)
Inquiry = “ADIC    Scalar i2000    402A”
Serial Number = ADIC204100621_LL0
Robot Control Host = host1
Drive = 18, Drive Name = drive18, Serial Number = F0016FE057
Drive = 19, Drive Name = drive19, Serial Number = F0016FE07D
Drive = 20, Drive Name = drive20, Serial Number = F0016FE023

Hosts configured for this device:
  Host = host2
  Host = host1
======================= Missing Device (Drive) =======================
Drive Name = drive20
Drive Path = /dev/rmt/0cbn
Inquiry = “IBM     ULTRIUM-TD2     5AT0”
Serial Number = F0016FE057
TLD(0) definition Drive = 20
Hosts configured for this device:
  Host = host2
======================= Missing Device (Drive) =======================
Drive Name = drive19
Drive Path = /dev/rmt/1cbn
Inquiry = “IBM     ULTRIUM-TD2     5AT0”
Serial Number =F0016FE07D
TLD(0) definition Drive = 19
Hosts configured for this device:
  Host = host2
======================= Missing Device (Drive) =======================
Drive Name = drive18
Drive Path = /dev/rmt/2cbn
Inquiry = “IBM     ULTRIUM-TD2     5AT0”
Serial Number =F0016FE057
TLD(0) definition Drive = 18
Hosts configured for this device:
  Host = host2

luxadm performs a variety of control and query tasks depending on the command line arguments and options used. The following option finds and displays information of individual FC_AL devices including the logical pathname, the WWNs and enclosure names.

bash-3.00# luxadm probe
Found Enclosure:
SUNWGS INT FCBPL   Name:FCloop   Node WWN:50200400051b1fa9   Logical Path:/dev/es/ses0

Found Fibre Channel device(s):
  Node WWN:500308c001637402  Device Type:Tape device
    Logical Path:/dev/rmt/0n
    Logical Path:/dev/rmt/3n
  Node WWN:500308c001637402  Device Type:Tape device
    Logical Path:/dev/rmt/1n
  Node WWN:500308c001637402  Device Type:Tape device
    Logical Path:/dev/rmt/2n
  Node WWN:500308c001637409  Device Type:Tape device
    Logical Path:/dev/rmt/4n
  Node WWN:500308c001637409  Device Type:Tape device
    Logical Path:/dev/rmt/5n
  Node WWN:500308c001637409  Device Type:Tape device
    Logical Path:/dev/rmt/6n

fcinfo command appeared only from Solaris 10 u1  ( Solaris 10 1/06).

If you have it missing, that chances are you have the old Solaris 10 version.

bash-3.00# cat /etc/release
                         Solaris 10 3/05 s10_74L2a SPARC
           Copyright 2005 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                            Assembled 22 January 2005

fcinfo command is provided by SUNWfcprt package.

bash-3.00# pkgchk -l -p /usr/sbin/fcinfo
Pathname: /usr/sbin/fcinfo
Type: regular file
Expected mode: 0555
Expected owner: root
Expected group: bin
Expected file size (bytes): 44424
Expected sum(1) of contents: 55871
Expected last modification: Aug 10 20:34:53 2005
Referenced by the following packages:
        SUNWfcprt
Current status: installed

Ether you can patch the server and bring it to the existing level or just install SUNWfcprt package from current Solaris 10 image.

Just happened on couple of SLES 9 servers after installing the followings 
the server just came back with postfix plugin.

perl-Net-Server-0.87-29.4.i586.rpm
munin-node-1.2.4-1.sles9.rpm

 
But by default munin plugins are
cpu entropy forks if_eth0 iostat memory mysql_slowqueries  open_files processes df exim_mailqueue
if_err_eth0  if_eth1 irqstats mysql_bytes mysql_threads open_inodes
swap df_inode  exim_mailstats if_err_eth1 interrupts load mysql_queries 
netstat postfix_mailvolume vmstat

Then I manually did symbolic links from /etc/munin/plugins to /usr/share/munin/plugins

beastie:/etc/munin/plugins # ln -s /usr/share/munin/plugins/cpu cpu
beastie:/etc/munin/plugins # ln -s /usr/share/munin/plugins/df df
beastie:/etc/munin/plugins # ln -s /usr/share/munin/plugins/df_inode df_inode
beastie:/etc/munin/plugins # ln -s /usr/share/munin/plugins/load load
beastie:/etc/munin/plugins # ln -s /usr/share/munin/plugins/memory memory
beastie:/etc/munin/plugins # ln -s /usr/share/munin/plugins/processes processes
beastie:/etc/munin/plugins # ln -s /usr/share/munin/plugins/if_eth0 if_eth0
beastie:/etc/munin/plugins # ln -s /usr/share/munin/plugins/if_err_eth0 if_err_eth0
beastie:/etc/munin/plugins # ln -s /usr/share/munin/plugins/if_eth1 if_eth1
beastie:/etc/munin/plugins # ln -s /usr/share/munin/plugins/if_err_eth1 if_err_eth1

Now after this the munin-node crashed and failed to show graph even for postfix.

While checking the log for munin in /var/log/munin/munin-node.log, I got the following error message

Can’t exec “/etc/munin/plugins/df”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:09:52 Plugin timeout: df config: Interrupted system call
(pid 16888)
2008/08/07-18:09:52 Server closing!
Can’t exec “/etc/munin/plugins/cpu”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:10:02 Plugin timeout: cpu config: Interrupted system call
(pid 16894)
2008/08/07-18:10:02 Server closing!
Can’t exec “/etc/munin/plugins/load”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:10:12 Plugin timeout: load config: Interrupted system call
(pid 16901)
2008/08/07-18:10:12 Server closing!
Can’t exec “/etc/munin/plugins/swap”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:10:22 Plugin timeout: swap config: Interrupted system call
(pid 16908)
2008/08/07-18:10:22 Server closing!
Can’t exec “/etc/munin/plugins/forks”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:10:32 Plugin timeout: forks config: Interrupted system call
(pid 16911)
2008/08/07-18:10:32 Server closing!
Can’t exec “/etc/munin/plugins/entropy”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:10:42 Plugin timeout: entropy config: Interrupted system call
(pid 16912)
2008/08/07-18:10:42 Server closing!
Can’t exec “/etc/munin/plugins/netstat”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:10:52 Plugin timeout: netstat config: Interrupted system call
(pid 16917)
2008/08/07-18:10:52 Server closing!
Can’t exec “/etc/munin/plugins/iostat”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:11:02 Plugin timeout: iostat config: Interrupted system call
(pid 16986)
Can’t exec “/etc/munin/plugins/df_inode”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:11:14 Plugin timeout: df_inode config: Interrupted system call
(pid 16991)
2008/08/07-18:11:14 Server closing!
Can’t exec “/etc/munin/plugins/memory”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:11:24 Plugin timeout: memory config: Interrupted system call
(pid 16997)
2008/08/07-18:11:24 Server closing!
Can’t exec “/etc/munin/plugins/vmstat”: Permission denied at /usr/sbin/munin-node line 562.
2008/08/07-18:11:34 Plugin timeout: vmstat config: Interrupted system call
(pid 17014)
2008/08/07-18:11:34 Server closing!
2008/08/07-18:14:33 CONNECT TCP Peer: “XX.XX.XX.7:52286” Local: “XX.XX.XX.145:4949”
Can’t exec “/etc/munin/plugins/df_inode”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 2.
Can’t exec “/etc/munin/plugins/entropy”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 3.
Can’t exec “/etc/munin/plugins/cpu”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 4.
Can’t exec “/etc/munin/plugins/postfix_mailvolume”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 5.
Can’t exec “/etc/munin/plugins/postfix_mailqueue”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 6.
Can’t exec “/etc/munin/plugins/forks”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 7.
Can’t exec “/etc/munin/plugins/iostat”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 8.
Can’t exec “/etc/munin/plugins/memory”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 9.
Can’t exec “/etc/munin/plugins/df”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 10.
Can’t exec “/etc/munin/plugins/netstat”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 11.
Can’t exec “/etc/munin/plugins/swap”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 12.
Can’t exec “/etc/munin/plugins/vmstat”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 13.
Can’t exec “/etc/munin/plugins/load”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 14.
Can’t exec “/etc/munin/plugins/cpu”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 15.
Can’t exec “/etc/munin/plugins/entropy”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 16.
Can’t exec “/etc/munin/plugins/df_inode”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 17.
Can’t exec “/etc/munin/plugins/postfix_mailqueue”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 18.
Can’t exec “/etc/munin/plugins/postfix_mailvolume”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 19.
Can’t exec “/etc/munin/plugins/forks”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 20.
Can’t exec “/etc/munin/plugins/iostat”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 21.
Can’t exec “/etc/munin/plugins/memory”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 22.
Can’t exec “/etc/munin/plugins/df”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 23.
Can’t exec “/etc/munin/plugins/netstat”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 24.
Can’t exec “/etc/munin/plugins/swap”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 25.
Can’t exec “/etc/munin/plugins/vmstat”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 26.
Can’t exec “/etc/munin/plugins/load”: Permission denied at /usr/sbin/munin-node line 562, <STDIN> line 27.
2008/08/07-18:14:33 Plugin “swap” exited with status 13. —-
2008/08/07-18:14:33 Plugin “netstat” exited with status 13. —-
2008/08/07-18:14:33 Plugin “df” exited with status 13. —-
2008/08/07-18:14:33 Plugin “memory” exited with status 13. —-
2008/08/07-18:14:33 Plugin “iostat” exited with status 13. —-
2008/08/07-18:14:33 Plugin “forks” exited with status 13. —-
2008/08/07-18:14:33 Plugin “postfix_mailvolume” exited with status 13. —-
2008/08/07-18:14:33 Plugin “postfix_mailqueue” exited with status 13. —-
2008/08/07-18:14:33 Plugin “df_inode” exited with status 13. —-
2008/08/07-18:14:33 Plugin “entropy” exited with status 13. —-
2008/08/07-18:14:33 Plugin “cpu” exited with status 13. —-
2008/08/07-18:14:33 Plugin “load” exited with status 13. —-
2008/08/07-18:14:33 Plugin “vmstat” exited with status 13. —-
2008/08/07-18:14:33 Plugin “swap” exited with status 13. —-
2008/08/07-18:14:33 Plugin “netstat” exited with status 13. —-
2008/08/07-18:14:33 Plugin “df” exited with status 13. —-
2008/08/07-18:14:33 Plugin “memory” exited with status 13. —-
2008/08/07-18:14:33 Plugin “iostat” exited with status 13. –
2008/08/07-18:14:33 Plugin “forks” exited with status 13. —-
2008/08/07-18:14:33 Plugin “postfix_mailqueue” exited with status 13. —-
2008/08/07-18:14:33 Plugin “postfix_mailvolume” exited with status 13. —-
2008/08/07-18:14:33 Plugin “cpu” exited with status 13. —-
2008/08/07-18:14:33 Plugin “entropy” exited with status 13. —-
2008/08/07-18:14:33 Plugin “df_inode” exited with status 13. —-

 

If you ever get these kinds of errors don’t forget to add plugins and permissions in /etc/munin/plugin-conf.d/munin-node file.

$cat /etc/munin/plugin-conf.d/munin-node
#
# This file contains configuration options for the plugins. Three
# options are understood by munin-node itself:
#
#       user <user>         # Set the user to run the plugin as
#       group <group>       # Set the group to run the plugin as
#       command <command>   # Run <command> instead of the plugin. %c
#                             expands to what would normally be run.
#   env.<variable>      # Sets <variable> in the plugin’s environment, see the
#                         individual plugins to find out which variables they
#                         care about.
#
#

[mysql*]
#env.mysqlopts -u someuser

[exim*]
group mail

[cps*]
user root

[apt]
user root

[vlan*]
user root

[postfix*]
user root
env.logfile mail

[cpu*]
user root

[memory*]
user root

[load*]
user root

[if_*]
user root

[if_err_*]
user root

[df*]
user root

[process*]
user root

[dhcpd]
env.leasefile /var/lib/dhcp/db/dhcpd.leases

 

You have to do this only when you get those error messages ūüôā Cheers

Solaris 10 comes with Solaris Fault management Facility which defines error messages in a well-defined and explicit format.

Below is a sample of such error message


Use fmdump to find error memory module

bash-3.00# fmdump -v -u cle6c844-8789-ed25-b8b2-cc507318a20f
TIME                 UUID                                 SUNW-MSG-ID
Aug 04 13:41:20.6073 bde3afe6-3bb8-c6a2-fbb2-822b0b879b50 SUN4U-8000-35
95%  fault.memory.bank

Problem in: mem:///unum=Slot,A:J8100,J8101,J8201,J8200
Affects: mem:///unum=Slot,A:J8100,J8101,J8201,J8200
FRU: mem:///unum=Slot,A:J8100,J8101,J8201,J8200

The FRU line declares the part which needs to be replaced to return the system to a fully operational state.

fmdump from man page:

The fmdump utility ca be used to display the contents fo any of the log files associated with the Solaris Fault manager, fmd. The Fault Manager runs in the background on each Solaris system. It receives telemetry information relating to problems detected by the system software, diagnoses these problems, and initiates proactive self-healing activities such as disabling faulty components.

Sometimes Fault Management throws the wrong error messages, for an example the following error message from /var/adm/messages and will require to clear the faults detected within the FMA.

Aug  4 13:57:56 Sunv880 fmd: [ID 441519 daemon.error] SUNW-MSG-ID: PCI-8000-42, TYPE: Fault, VER: 1, SEVERITY: Critical
Aug  4 13:57:56 Sunv880 EVENT-TIME: Mon Aug  4 13:57:56 EDT 2008
Aug  4 13:57:56 Sunv880 PLATFORM: SUNW,Sun-Fire-880, CSN: -, HOSTNAME: Sunv880
Aug  4 13:57:56 Sunv880 SOURCE: eft, REV: 1.16
Aug  4 13:57:56 Sunv880 EVENT-ID: 8b31de79-a6a3-49bd-a24e-8f9bd4533190
Aug  4 13:57:56 Sunv880 DESC: A problem was detected in the SUNOS subsystem or controlling software.  Refer to http://sun.com/msg/PCI-8000-42 for more information.
Aug  4 13:57:56 Sunv880 AUTO-RESPONSE: One or more device instances may be disabled
Aug  4 13:57:56 Sunv880 IMPACT: Loss of services provided by the device instances associated with this fault
Aug  4 13:57:56 Sunv880 REC-ACTION: Ensure that the latest drivers and patches are installed, schedule a repair procedure to replace the affected device if necessary, or contact Sun for support.

# fmdump -v -u 8b31de79-a6a3-49bd-a24e-8f9bd4533190
TIME                 UUID                                 SUNW-MSG-ID
Aug 04 13:25:03.4539 8b31de79-a6a3-49bd-a24e-8f9bd4533190 PCI-8000-42
25%  defect.io.pci.driver

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=1/pcifn=0
Affects: –
FRU: –

25%  defect.io.pci.driver

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=2/pcifn=0
Affects: mod:///mod-name=qlc/mod-id=26
FRU: pkg:///SUNWqlc

25%  fault.io.pci.device

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=2/pcifn=0
Affects: dev:////pci@8,600000/SUNW,qlc@2
FRU: hc:///component=MB

25%  fault.io.pci.device

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=1/pcifn=0
Affects: dev:////pci@8,600000/network@1
FRU: hc:///component=MB

Aug 04 13:41:20.2781 8b31de79-a6a3-49bd-a24e-8f9bd4533190 PCI-8000-42
25%  fault.io.pci.device

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=1/pcifn=0
Affects: dev:////pci@8,600000/network@1
FRU: hc:///component=MB

25%  fault.io.pci.device

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=2/pcifn=0
Affects: dev:////pci@8,600000/SUNW,qlc@2
FRU: hc:///component=MB

25%  defect.io.pci.driver

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=2/pcifn=0
Affects: mod:///mod-name=qlc/mod-id=26
FRU: pkg:///SUNWqlc

25%  defect.io.pci.driver

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=1/pcifn=0
Affects: –
FRU: –

Aug 04 13:57:56.1241 8b31de79-a6a3-49bd-a24e-8f9bd4533190 PCI-8000-42
25%  fault.io.pci.device

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=1/pcifn=0
Affects: dev:////pci@8,600000/network@1
FRU: hc:///component=MB

25%  fault.io.pci.device

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=2/pcifn=0
Affects: dev:////pci@8,600000/SUNW,qlc@2
FRU: hc:///component=MB

25%  defect.io.pci.driver

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=2/pcifn=0
Affects: mod:///mod-name=qlc/mod-id=26
FRU: pkg:///SUNWqlc

25%  defect.io.pci.driver

Problem in: hc:///motherboard=0/hostbridge=0/pcibus=0/pcidev=1/pcifn=0
Affects: –
FRU: –

To clear error logs within FMA use the following steps:

1) # fmadm faulty
STATE RESOURCE / UUID
——– ———————————————————————-
faulted cpu:///cpuid=1/serial=14D269010CD
03351534-e325-cf5d-81ae-e3fc8be83e5b
——– ———————————————————————-
degraded dev:////pci@8,600000/SUNW,qlc@2
8b31de79-a6a3-49bd-a24e-8f9bd4533190
——– ———————————————————————-
degraded mod:///mod-name=qlc/mod-id=26
8b31de79-a6a3-49bd-a24e-8f9bd4533190
——– ———————————————————————-

2) #fmadm repair <UUID>

# fmadm repair 03351534-e325-cf5d-81ae-e3fc8be83e5b

# fmadm repair 8b31de79-a6a3-49bd-a24e-8f9bd453319

# fmadm repair 8b31de79-a6a3-49bd-a24e-8f9bd4533190

3) # cd /var/fm/fmd

# rm  e* f* c*/eft/* r*/*   (rm errlog fltlog ckpt/eft/* rsrc/*)

4) # fmadm reset cpumem-diagnosis

5) # fmadm reset cpumem-retire

6) # fmadm reset eft

7) # fmadm reset io-retire

8) # init 6

After these steps check to see if problem still exit.

# fmadm faulty
STATE RESOURCE / UUID
——– ———————————————————————-

fmadm man page:

The fmadm utility can be used by administrators and  service
personnel to view and modify system configuration parameters
maintained  by  the  Solaris  Fault  Manager,  fmd(1M).  fmd
receives telemetry information relating to problems detected
by the system software, diagnoses these problems,  and  ini-
tiates  proactive  self-healing activities such as disabling
faulty components.

Ref:

Solaris 10 Predictive Self-Healing and Solaris Diagnostics

Sneep provides a persistent, software-accessible Chassis Serial Number (CSN) for virtually all Sun Solaris hardware platforms. Sneep uses the system EEPROM for storage of the Chassis Serial Number and any other important user-defined data such as asset, contract, or location information. The presence of the software-accessible serial number and other service-related information can significantly simplify activities related to system service and asset management.

Download SUNWsneep from

https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SNEEP-2.5R1.92-G-F@CDS-CDS_SMI

SNEEP FAQ

http://wikis.sun.com/display/sneep/SNEEP+FAQ

# /opt/SUNWsneep/bin/sneep -s <serial number>

And then later on, you can check the chassis serial number (CSN) with:

# /opt/SUNWsneep/bin/showplatform -p csn

This data is stored in NVRAM on SPARC and in a NVRAM-like file on x86.

bash-2.03# /opt/SUNWsneep/bin/sneep -a
ChassisSerialNumber from eeprom :
XXXXXXXXXXX
ChassisSerialNumber from backup : /etc/default/SUNWsneep :
XXXXXXXXXXX
ChassisSerialNumber from explorer :
XXXXXXXXXXX

bash-2.03# /opt/SUNWsneep/bin/sneep -T
“ChassisSerialNumber”¬†¬† “XXXXXXXXXX”
“ASSET_ID”¬†¬†¬†¬†¬† “unknown”
“BUS_AREA”¬†¬†¬†¬†¬† “unknown”
“BUS_CONTACT”¬†¬† “Somebody”
“CABINET”¬†¬†¬†¬†¬†¬† “Somecabinet”
“CC”¬†¬†¬† “unknown”
“CLUSTER_INFO”¬† “unknown”
“ENVIRONMENT”¬†¬† “unknown”
“FUNCTION”¬†¬†¬†¬†¬† “Technology Management”
“LOCATION”¬†¬†¬†¬†¬† “Out of Space”
“PDBA”¬† “unknown”
“PROJECT”¬†¬†¬†¬†¬†¬† “Consolidation”
“PSA”¬†¬† “unknown”
“SDBA”¬† “unknown”
“SSA”¬†¬† “unknown”

Here’s a simple method to add swap space in VxVM Volume

Creating a secondary swap device using “vxassist”

#vxassist -g rootdg -U swap make swapvol (size) rootdisk

Where,

rootdg = Volume group

swapvol = swap space name

(size) = swap size

rootdisk = disk name

 

Adding Swap space

# swap -a /dev/vx/dsk/rootdg/swapvol

Permanently add swap space in /etc/vfstab

/dev/vx/dsk/rootdg/swapvol – – swap – no –