VSM6 or VLE - Node(s) are missing JBOD devices in ras_admin device

Asset ID:	1-72-2131533.1
Update Date:	2016-05-09
Keywords:

Solution Type Problem Resolution Sure

Solution 2131533.1 : VSM6 or VLE - Node(s) are missing JBOD devices in ras_admin device_list

Applies to:

Sun Virtual Library Extension (VLE) - Version 1.0 to 1.5 [Release 1.0]
StorageTek Virtual Storage Manager System 6 (VSM6) - Version All Versions to All Versions [Release All Releases]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

Missing JBOD devices in ras_admin device_list

JBOD devices in ras_admin device_list incorrect

Changes

New install

Code upgrade

Added storage capacity

Cause

Devices need to be rediscovered.

Devices were not discovered for the ras_admin device_list for JBOD device monitoring.

Solution

The following missing JBODs or devices would normally be found while performing a VSM6 or VLE health check or upon reviewing the health check log in the system_logfiles directory in the file vsm_HealthCheck.log.txt or vle_HealthCheck.log.txt. The missing JBOD devices does not affect production but the monitoring of failure events by CAM. In the event these devices are missing and a failure event occurred within the JBOD, CAM would not report the event and an ASR would not be created.

Action plan for VSM6 to update the ras_admin device_list for all Just a Bunch of Disks (JBOD) devices. A VLE node would have the same action plan.

Obtain the most recent support file bundle (SFB) and review the ras_admin device_list as shown in the system_logfiles directory vsm_HealthCheck.log.txt log. Below is an example of Node 1 having the JBOD devices listed and Node has only 2 JBODs devices listed.

Node 1

## ras_admin device_list
Monitored On Device Type IP Address Unique Identifier Active ASR
------------ ------------ ------- ------------ ----------------- ------ ---
vsmpriv1 1408NMT05G de2-24c 192.168.84.1 50800200018f74be Y Y
vsmpriv1 vsmpriv1 host 127.0.0.1 864646f0 Y N
vsmpriv1 1547NMT023 de2-24c 192.168.84.1 5080020001e8ab7e Y Y
vsmpriv1 1549NMT03B de2-24c 192.168.84.1 5080020001ecec7e Y Y
vsmpriv1 1408NMT05F de2-24c 192.168.84.1 50800200018f743e Y Y
vsmpriv1 1549NMT03A de2-24c 192.168.84.1 5080020001f23dbe Y Y
vsmpriv1 1511NMT0BA de2-24c 192.168.84.1 5080020001cfb77e Y Y
vsmpriv1 vsmpriv1_vsm vsm 192.168.84.1 Y Y

Node 2

## ras_admin device_list
Monitored On Device Type IP Address Unique Identifier Active ASR
------------ ------------ ------- ------------ ----------------- ------ ---
vsmpriv2 1408NMT05G de2-24c 192.168.84.2 50800200018278fe Y Y
vsmpriv2 vsmpriv2 host 127.0.0.1 86464c9a Y Y
vsmpriv2 1408NMT05F de2-24c 192.168.84.2 50800200018f743e Y Y
vsmpriv2 vsmpriv2_vsm vsm 192.168.84.2 Y Y

1. Check the current device list.

sudo /opt/SUNWsefms/bin/ras_admin device_list

2. Run this command to rediscover the devices.

sudo /opt/SUNWsefms/bin/ras_admin discover_inband -l 1 -v

3. Run this command again and the output should show all the JBODs as Node 1.

sudo /opt/SUNWsefms/bin/ras_admin device_list

4. If the above does not work then run the asr_sfb.pl script as described in the most recent ASRandSupportFileConfigGuide for the VSM6 or VLE. From the JBOD utility, select "Rediscover devices". Do NOT select Discover devices unless directed by engineering!

5. Run this command again and the output should show all the JBODs as Node 1.

sudo /opt/SUNWsefms/bin/ras_admin device_list

Attachments

This solution has no attachment