Sun Storage Common Array Manager (CAM)
 
Sun Storage J4500 Array
 
Sun Storage J4400 Array
 
Sun Flash F5100 Array
 
Sun Storage J4200 Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: J4xxx JBOD
 
_Old GCS Categories>Sun Microsystems>Storage - Disk>JBOD Disk
 

This article documents Sun Storage J4000 Series and Sun Storage F5100 Series Arrays'  steps to validate In-Band Management.

In this Document

Goal

Solution

Applies to:

Goal

The goal of this document is to ensure that communication with Sun Storage J4000 and
F5100 Series arrays is operating properly using In Band management. In Band management is
defined as any user interface commands passed to the array to either monitor the status
of or change the configuration of a storage array by sending commands over the same path
that is used for data.

Solution

Please validate that each troubleshooting step below is true for your environment.
The steps will provide instructions or a link to a document, for validating the step
and taking corrective action as necessary. The steps are ordered in the most appropriate
sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

1. Identify the type of In-Band Management Layout you have.There are two basic layouts to this management infrastructure.

The types below will be listed in terms of Sun Storage Common Array Manager (CAM).

Type 1:

CAM on same host as data host --- Data Path to Array to manage--->Physical connection to Array

In this case JBOD management host and Data Host are the same.
Includes Full CAM installation.

Type 2:

CAM Server ----TCP/IP---->

Data Host with In-Band Proxy software ---Data Path to Array to manage--->Physical connection to Array

The CAM Server is where you use the management application to manage the disk array to present to the host for data access. 

In Band Proxy Host is the location of the Proxy Software.

 * If you have aType 1 Layout, open a shell or command prompt (Windows)
on your CAM Server, and continue to Step 6.
* If you have a Type 2 Layout, open a shell or command prompt on your
CAM Server, continue to Step 2.

2. Telnet to port 8653 on the In-Band Proxy Host:

    telnet IP-Address  8653

where is the IP-address of the In-Band Proxy Host (CAM Data Host).

-If the result is connection refused, go to Step 4.
-If the connection is established go to Step 5.
-If the connection states node name or service name not known, go to Step 3.

3.Use ping to Validate that the Management Server can route IP traffic to the In-Band Proxy Host.

    ping IP-address

-If ping fails, you have a network routing problem, or your IP address is incorrect.  Resolve the network issue or find the correct IP Address. Then return to the next step below.

Once ping succeeds, try to:

  telnet IP-Address 8653

-If ping succeeds, and the attempt to telnet above continues to fail, you will need to log  into the In-Band Proxy Host (the host connected to the array) as a user  with Administrative privileges, then:

telnet 127.0.0.1 8653

* If the result is connection refused, go to Step 4.
* If the connection is established, this indicates that the in-band agent is running 
on the In-Band Proxy Host, but there is some piece of network software
preventing the CAM Server from connecting on that port.  This typically indicates
that there is some type of  firewall software preventing this connection. 
Once the port traffic is opened repeat Step 2.

4. Check that the In-Band Proxy Agent is Listening on the network for port 8653:

For Solaris and Linux:
netstat -an | grep 8653

For Windows:
netstat -an  /p

Use the /p switch to pause the output to review for port 8653

    * If the port is not listening, go to Step 5.
    * If the port is listening, go to Step 6.

5. Enable remote control on the CAM Data Host, and create a password:

This will verify the CAM Data host has remote control access enabled.

For UNIX (Solaris and Linux):

Enable remote control access:

#/opt/SUNWsefms/sbin/proxycfg enable

sh-3.00# /opt/SUNWsefms/sbin/proxycfg enable

Agent configuration saved.
Hostname  : v4u-4800a-doma-fll03
Hostid    : 8307fcf0
IP        : 10.2.22.146
Frequency : 5
Active    : Y

You will see the following on a Solaris 10 system:

svc:/system/fmservice:default temporarily disabled.
svc:/system/fmservice:default enabled.


Restarting Sun Java(TM) Web Console Version 3.1 ...


The console is running

-If the error: "directory specified doesn't exist" is returned from fmservice, go to Step 7.
-If not enabled go to Step 6.
-If enabled go to Step 8.

6. Determine if we can see the SES (SCSI Enclosure Services) device for the array:

For Solaris:
prtpicl -v -c scsi

For Linux:
grep -i model /proc/scsi/scsi

For Windows:
Start->Administrative Tools->Computer Management->Device Manager
Look under Other Devices (the yellow "?") OR System Devices

For Solaris example:

prtpicl -v -c scsi|grep :inquiry-product-id
:inquiry-product-id    Storage J4500
:inquiry-product-id    Storage J4500
:inquiry-product-id    Storage F5100

If you can see the SES device, go to Step 8. If the SES device is not detected,
reseat the SAS cables connected to the HBA and array and recheck.

If SES device is still not detected go to Step 12
If SES device is detected go to Step 8.

7. Determine the Operating system versions then Validate that the In-Band Agent CAM software is installed on the CAM Data and Management Host:

For Solaris: Determine the version of Solaris and the package version

uname -a

  SunOS myserver  5.10 Generic_144489-05 i86pc i386 i86pc

pkginfo -l i SUNWsefms

  PKGINST:  SUNWsefms
  NAME:  Sun StorageTek(TM) Fault Management Services (Core)
  CATEGORY:  application
  ARCH:  all
  VERSION:  6.6.0,REV=2010.02.18.07.17.33
  BASEDIR:  /opt
  VENDOR:  Sun Microsystems, Inc.
  PSTAMP:  20100218-1917.11
  INSTDATE:  May 14 2010 14:16
  HOTLINE:  Please contact your local service provider
  STATUS:  completely installed
  FILES:      134 installed pathnames
                6 shared pathnames
               25 directories
               21 executables
            15184 blocks used (approx)

For Linux: Determine the version of Linux and the package version

uname -a

   Linux myserver 2.6.39-1.el6.x86_64 #1 SMP Date.... x86_64 x86_64 x86_64 GNU/Linux

rpm -qa | grep SUNWsefms

For Windows:
Start->Control Panel->Add/Remove Programs

If not installed, install latest version and then go to Step 4.
If already installed, go to Step 8.

8. Verify the FMS service status:

Check the status of FMS:

Solaris 10:
svcs svc:/system/fmservice:default

Solaris 8,9:
/opt/SUNWsefms/sbin/fmservice.sh status

Linux:
/opt/sun/cam/private/fms/sbin/fmservice.sh status

Windows:
Use Start->control panel->Administrative Tools->Services to check status of Sun_STK_FMS

Verify that FMS status is online.
If FMS services is running, go to Step 11.
If FMS services is not running, go to Step 9.

9.  Initialize CAM FMS Services and validate it is started:

For Solaris 10:
svcadm restart svc:/system/fmservice:default

For Solaris 8,9:
/opt/SUNWsefms/sbin/fmservice.sh restart

For Linux:
/opt/sun/cam/private/fms/sbin/fmservice.sh restart

Windows:
Use Start->control panel->Administrative Tools->Services

Use the process in Step 8 to verify FMS  is running.

10. Run agent and re-register array:

In the CAM BUI:

-At the General Health Monitoring Setup screen,
select the Run Agent button specifying the correct Array type.

-Then re-register (unregister first if array shows up):
At the Storage System Summary screen select the Register button from
the left side of the table.

If problem is not resolved then go to Step 12.

11: Check that the version of CAM is at least at 6.5 Revision:

Refer to Step 7 instructions for checking the SUNWsefms software package.
If below  version 6.5, upgrade CAM baseline and then go to Step 10.
If at version 6.5 or later, go to Step 12.

12. Data Collection:
Please collect and compile the following information and engage technical support:

   * The In-Band Layout Type from Step 1.
   * The IP addresses or at least the host names for reference identified in Step 1.
   * The Results of Step 2 for type 2.
   * The Results of Step 5 for type 2
   * The output of netstat -an for type 2.
   * The output showing the SES device or a lack of one from Step 6.
   * The Results of Step 8.
   * The output result of Step 11.
   * The host OS for the In-Band Proxy Host.
   * The host OS for the Management Server.
   * The array model that requires management.

This solution has no attachment