| Sun Storage Automated Diagnostic Environment Enterprise Edition Release Notes |     |
| Sun Storage Automated Diagnostic Environment Enterprise Edition Release Notes | |
|
Storage Automated Diagnostic Environment Enterprise EditionRelease Notes |
This document contains important information about the Sun Storage Automated Diagnostic Environment Enterprise Edition that was not available at the time the product documentation was published. Read this document so that you are aware of issues or requirements that can impact the installation and operation of the Storage Automated Diagnostic Environment Enterprise Edition.
The Release Notes consists of the following sections:
The information in this release note applies to the Storage Automated Diagnostic Environment Enterprise Edition when it is obtained as a standalone product from the Sun web site or from a CD.
Refer to the release notes for the device or system with which you obtained the Storage Automated Diagnostic Environment Enterprise Edition for additional information on this product.
|
Note - Command Line Instruction (CLI) procedures in this release note apply to the Storage Automated Diagnostic Environment Enterprise Edition it is obtained as a standalone product only. |
The Storage Automated Diagnostic Environment Enterprise Edition product is used for the fault management of Sun storage devices. It provides full-time device monitoring, local and remote notification, diagnostics, revision analysis, reports, and integration with appropriate device management software.
The Agents supplied by the Enterprise Edition can be used to collect data and analyze the condition of Sun StorEdge devices. The Diagnostics can be used to verify the condition of a system, identify failing FRUs, and verify FRU replacement.
The Storage Automated Diagnostic Environment Enterprise Edition is for use by system administrators and support personnel who are familiar with Sun's disk array and SAN products.
The Storage Automated Diagnostic Environment Enterprise Edition consists of two components:
The SUNWstade is the base product package containing all product functions except the web browser-based management station. The base package contains a command line interface (CLI) for product configuration and use.
The optional SUNWstadm package adds a web browser-based graphical user interface (GUI) to the Storage Automated Diagnostic Environment Enterprise Edition. Additional management station packages are available to produce localization versions of the management station.
Each product component is installed and configured separately.
The following are the main features of the base component (SUNWstade) of the Storage Automated Diagnostic Environment Enterprise Edition:
Refer to the following file for a listing of all possible generated events:
/opt/SUNWstade/System/EGrid/EventGrid2.pdf.
Queries the SAM-QFS 4.2 Fault Management API for Asset and Health attributes of the hardware devices (tape drives and libraries) included in the SAM-QFS configuration. Examples of device asset attributes are those which remain static such as device product name, vendor and serial number. Examples of device health attributes are "state" (on, idle, off or down) and "attention" (user intervention required). When a health attribute changes to a bad state, Storage Automated Diagnostic Environment Enterprise Edition issues an alarm which provides a detailed description and identifies the device in question.
Storage Automated Diagnostic Environment Enterprise Edition uses the SAM-QFS 4.2 Fault Management API in order to retrieve the current firmware revisions of 4 Sun branded tape libraries and 11 Sun branded tape drives qualified to operate with SAM-QFS. A revision report indicates whether the firmware revisions of the installed devices are up to date with what Sun has currently released.
Storage Automated Diagnostic Environment Enterprise Edition reads the sam-log every 5 minutes, processing only those entries made since the last polling cycle. If Storage Automated Diagnostic Environment Enterprise Edition finds sam-log entries that are of severity "warning" or higher, it posts alarms whose description contains the hardware device or process name and a description contained in the log entry. Note that in order for this feature to be effective, the SAM-QFS sam-log must be enabled by entries in the /etc/opt/SUNWsamfs/defaults.conf and /etc/syslog.conf files. See the SAM-QFS documentation for details.
This section lists the changes and enhancements in the this release and the last release of the product
This section describes the requirements for the Storage Automated Diagnostic Environment Enterprise Edition.
You can use the Sun Storage Automated Diagnostic Environment Enterprise Edition on the following platforms and operating systems:
The following platforms are qualified for the Storage Automated Diagnostic Environment Enterprise Edition.
Reference the Best Practices for Deploying Storage the Sun Storage Automated Diagnostic Environment Utility (817-5205-10) at http://www.sun.com/blueprints
5.005 through 5.8.3 is mandatory. Use the following URL to download the proper version if necessary http://www.perl.com/pub/language/info/software.html
If a supported version already exists on your system, create a symbolic link of the executable to /usr/bin/perl.
This section identifies the SUNWstade requirements of the product.
To restart, issue the following command:
/opt/SUNWstade/rasserv/bin/restart
/opt/SUNWstade/bin/rasagent -d2
The Storage Automated Diagnostic Environment Enterprise Edition is a device monitoring tool that probes devices on the ethernet and, for direct attached storage devices, accesses the device in the data path (Fibre Channel).
|
Note - For most storage arrays, it is important to stop all monitoring during upgrade operations. |
Use the following information that best suits your site for stopping the agent from monitoring:
There are several ways to accomplish the task of stopping monitoring agents from probing a storage array during an upgrade.
One way would be to use the management station, if installed, to disable the specific agent from executing. This would allow for the continuing of the monitoring of other types of devices.
One method to prevent the agent from monitoring is to manually remove the cron entry (See crontab(1M)). The entry for the rasagent executable would need to be removed from the root crontab.
Execute ras_install and select "P" to postpone the execution of rasagent from cron. This will remove the cron entry that starts the agent every 5 minutes.
|
Note - This will not immediately stop an existing execution of the agent. Use the ps command to ensure all agent activity has ended: ps -ef | grep ras |
The following information applies to firmware upgrades:
Follow the instructions in this section to prepare for software installation and install the SUNWstade base package and, optionally, the SUNWstadm management station package.
The Storage Automatic Diagnostic Environment does not support an automatic upgrade to version 2.4 from earlier versions. You must remove any existing version before installing SUNWstade version 2.4.
1. Run ras_install with the -p option to shut down the cron.
# /opt/SUNWstade/bin/ras_install -p
2. Determine what version of the Storage Automatic Diagnostic Environment is installed.
The system responds with the installed version number:
3. Remove the SUNWstade package and any installed patches.
4. Remove any files left under the /opt/SUNWstade directory and the /opt/SUNWstade directory itself.
After SUNWstade patches are installed they are typically removed by pkgrm of the SUNWstade package, but there are instances when some files are left under the /opt/SUNWstade directory.
5. If the installed version of the Storage Automatic Diagnostic Environment was prior to version 2.3, move the /var/opt/SUNWstade/DATA directory to a backup.
# mv /var/opt/SUNWstade/DATA /var/opt/SUNWstade/DATA.bak
You can remove this directory at a later date if you choose.
Follow the instructions below to install the SUNWstade base package:
|
Note - You must be logged in as superuser to install these packages and patches. |
Find and download any of the packages and patches in the following procedure using the Sun Download Center (SDLC) web site:
http://wwws.sun.com/software/download
To install the SUNWstade package:
1. If it is not currently installed, download and install Java Runtime Environment (JRE) revision 1.4 or later following its installation instructions.
|
Note - If you plan to install the management station package, SUNWstadm, download and install the Java Developer's Kit (JDK) instead. The JDK includes the required JRE. |
The Java Runtime Environment (JRE) revision 1.4 or later is required by the SUNWstade Enterprise Edition package and must be installed in /usr/j2se or /usr/java. The JRE is a subset of the SDK so installation of the SDK satisfies this requirement.
2. If they are not installed, download and install the following SUNWsan package and patches before installing SUNWstade.
The SUNWsan package is a requirement for installation on Solaris Data hosts. The SUNWsan package is a component of the San Foundation Software (SFS) kit (www.sun.com/storage/san). There are separate kits for each of Solaris 8 and 9. In addition to the SFS kit, the luxadm patches required are:
To install Storage Automated Diagnostic Environment Enterprise Edition package, SUNWstade, from the Sun Sunsolve web site download site:
|
Note - You must use /opt/SUNWstade as the package base directory. |
a. Download the compressed SUNWstade tar image to /tmp.
c. # uncompress SUNWstade.tar.Z
d. # tar xvf /tmp/SUNWstade.tar
To install Storage Automated Diagnostic Environment Enterprise Edition package, SUNWstade, from an installation CD:
a. # cd /cdrom/cdrom0/product/packages
c. Select the SUNWstade package and press Return
4. Locate, download, and install potential patches for the Storage Automated Diagnostic Environment Enterprise Edition on Sun's Sunsolve web site using the Patch Portal at http://sunsolve.sun.com:
Patch Portal -> PatchFinder -> 117650
5. After installation, set the environment variables PATH and MANPATH to include the directories /opt/SUNWstade/bin and /opt/SUNWstade/man.
To verify that the MANPATH is correct:
Follow the instructions below to install the optional SUNWstadm management station package:
If you intend to install only the English Language management station package, complete the following procedure only:
Installing the English Language Package
If you intend to install one or more localized management station packages, complete the following procedure also:
Installing One or More Localized Packages
Follow the instructions below to install the english language management station package:
|
Note - You must be logged in as superuser to install these packages and patches. |
Find and download any of the following packages and patches using the Sun Download Center (SDLC) web site:
http://wwws.sun.com/software/download
To install the SUNWstadm package:
1. If you haven't done so, install the SUNWstade base package. Refer to Installing the SUNWstade Package.
2. The Sun (TM) Management Console (Lockhart) revision 2.1.1 or later is required by the SUNWstadm Management Station package.
The Java Software Development Kit (SDK) revision 1.4.2_04 or later is required by the Sun (TM) Management Console (Lockhart) and is provided in the Sun (TM) Management Console download when it is not located on the system.
On Solaris 8 systems, patches 110380-04 and 110934-16 or later must be installed in order to install the Sun (TM) Management Console (Lockhart).
If they are not installed, download and install the above packages and patches before installing SUNWstadm.
To install Storage Automated Diagnostic Environment Enterprise Edition management station package, SUNWstadm, from the Sun Sunsolve web site download site:
a. Download the compressed SUNWstadm tar image to /tmp.
c. # uncompress SUNWstadm.tar.Z
d. # tar xvf /tmp/SUNWstadm.tar
To install age the Diagnostic Environment Enterprise Edition management station package, SUNWstadm, from an installation CD:
a. # cd /cdrom/cdrom0/product/packages
c. Select SUNWstadm and press Return.
4. The /opt/SUNWstade/bin/ras_install is run during the SUNWstade package installation. If you need to change the default settings of Master, Cron enabled, or the default locale; rerun ras_install program and choose the desired settings:
# /opt/SUNWstade/bin/ras_install
|
Note - Steps 4, 5, and 6 are unnecessary if you performed them during installation of the base package, SUNWstade. |
5. Locate, download, and install potential patches for the Storage Automated Diagnostic Environment Enterprise Edition management station on Sun's Sunsolve web site using the Patch Portal at http://sunsolve.sun.com:
Patch Portal -> PatchFinder -> 117650
6. Set the environment variables PATH and MANPATH to include the directories /opt/SUNWstade/bin and /opt/SUNWstade/man.
To verify the MANPATH: # man ras_install
7. Define the sa_admin role and administrative users
Users can log into the Storage Automated Diagnostic Environment Enterprise Edition management station using their standard UNIX account, but they will be limited in what they are permitted to do unless they have the assigned role of sa_admin.
Discovery, management of remote devices, and running diagnostics are restricted operations that are only permitted for users associated with the sa_admin role.
The following example creates the sa_admin role and assigns the password "diags" to that role:
a. # roleadd -c "SA Role" -s /bin/pfcsh -A "solaris.*" -P "All" sa_admin
b. # passwd sa_admin ### Use password diags
The following example creates a user named admin, also with password "diags," and assigns the user the sa_admin role:
a. # useradd -c "SA Admin" -s /bin/csh -R sa_admin -A
"solaris.*" admin
b. # passwd admin ### Use password diags
The following example assigns the sa_admin role to an existing user named olduser and verifies the user's role:
a. # usermod -c "SA Admin" -R sa_admin -A "solaris.*"
olduser
Refer to roleadd(1M), rolemod(1M), roledel(1M), and roles(1M) for more information on role management. Refer to useradd(1M), usermod(1M), and userdel(1M) for information on user login management.
Follow the instructions below to install one or more localized management station package:
|
Note - You must be logged in as superuser to install these packages and patches. |
Find and download any of the required packages and patches using the Sun Download Center (SDLC) web site:
http://wwws.sun.com/software/download
Or get the CD that contains Storage Automated Diagnostic Environment Enterprise Edition localized software.
This release of Storage Automated Diagnostic Environment Enterprise Edition software supports English, French, Japanese, Korean, Simplified Chinese and Traditional Chinese locales.
|
Note - Man pages are available only in English and Japanese. Release notes are available in English, French, Japanese, Korean, Simplified Chinese and Traditional Chinese. |
The software package names of the supported locales are listed below:
|
Note - Any combination of the five localized packages can be installed in your system. |
To install a localized version of the Storage Automated Diagnostic Environment Enterprise Edition:
1. Stop the agent from polling: # /opt/SUNWstade/bin/ras_install -p
2. Remove any package currently installed using one of the following commands:
3. If you haven't done so, install the English language version of the Storage Automated Diagnostic Environment Enterprise Edition. Refer to the Storage Automated Diagnostic Environment Enterprise Edition Release Notes for instructions.
4. If you haven't done so, install the English language version of the Storage Automated Diagnostic Environment management station. Refer to Installing the English Language Package for instructions.
a. Download the compressed tar image for the package to /tmp.
c. # uncompress <packagename>.tar.Z
d. # tar xvf /tmp/<packagename>.tar
e. # pkgadd -d . <packagename>
where packagename is the name of the localized package you are installing.
a. # cd /cdrom/cdrom0/product/L10N
where packagename is the name of the localized package you are installing.
If you installed the SUNWstade base package only, use the following CLI-based procedure to complete initial set up requirements:
Setting Up the Software With the CLI
If you installed the SUNWstadm management station package, you have the option to use the following GUI-based procedure to complete initial set up requirements:
Setting Up the Software With GUI
|
Note - If you obtained Storage Automated Diagnostic Environment Enterprise Edition bundled with a device-specific or system specific software package, this section does not apply to you. Refer to Setting Up the Software With GUI or refer to the device-specific or system specific release notes for setup procedures. |
The following procedure allows the user to set up Storage Automated Diagnostic Environment Enterprise Edition on a host server that does not have the GUI management package installed (SUNWstadm). This procedure will guide the user through the steps necessary to properly initialize the product using Command Line Interface (CLI) commands.
To set up the Storage Automated Diagnostic Environment Enterprise Edition from the CLI:
|
Note - In the example procedures that follow, the name of the host where the Storage Automated Diagnostic Environment Enterprise Edition is installed is referred to as acmetw4. |
a. Change to the /opt/SUNWstade/bin directory:
# root@acmetw4 cd /opt/SUNWstade/bin
b. Execute the ras_admin command specifying the function argument site_info_upd.
# root@acmetw4 ./ras_admin site_info_upd
c. Follow the prompts to supply the information requested.
|
Note - Prompts marked with an asterisk (*) are required fields. |
A typical set of Site Information prompts is shown below.
Enter Customer* : ACME Tools and Die Inc.
Enter Site name* : ACME Tool Works Site #4
Enter Site address : 123 Anystreet Blvd.
Enter Site contact* : John Smith
Enter Site contact phone : (888) 555-9876
Enter Site email* : john.smith@acme.com
Do you want to save these values [y=yes, n=no, q=quit]: y
a. Enter y to save the specified Site Information.
You can discover devices in one or more of three ways:
The device configuration file is /etc/deviceIP.conf. It looks a great deal like a hosts definition file. The/etc/deviceIP.conf file may be utilized for discovery of all supported fibre channel devices that have ethernet connectivity and whose IP address and device types are known.
To use this method, you must specify the device names as they are defined in the /etc/hosts file or specify IP addresses to discretely discover those devices. An alternative is to blindly search the subnet - but this takes much longer and may add devices that are not part of this systems configuration (requiring you to manually remove them later).
Some devices do not provide out-of-band management paths, discovery must use the in-band path to find the device. Typically, devices such as HBAs, and JBOD arrays without out-of-band management must be discovered this way.
|
Note - This method is not required if you choose one of the previous methods to discover your devices, it will not add any new information about those devices. |
To discover devices using the a device configuration file:
a. Change your directory to the /etc directory:
b. Use a text editor to open the /etc/deviceIP.conf file.
# root@acmetw4 vi deviceIP.conf
c. For each device to be discovered, specify the device IP, device name, device type, and comments using the following syntax:
device_ip device_name [device_type] #comments
The device_name will be used if the device name cannot be retrieved from the device itself.
The device_type is required for devices that do not support SNMP, including Sun StorEdge 3xx0 devices such as the Sun StorEdge 3510/3310 devices, and SAM-QFS.
Some examples of device entries follow.
10.0.0.2 fc3510 # My SE-3510 (uses SNMP for discovery)
10.0.0.3 3900 se # My SE-3910 array
Valid device type entries are:
d. Save the updated device configuration file.
e. Change your directory to the /opt/SUNWstade/bin directory:
# root@acmetw4 cd /opt/SUNWstade/bin
f. Execute the ras_admin command specifying the function argument discover_deviceIP to use the /etc/deviceIP.conf file:
# root@acmetw4 ./ras_admin discover_deviceIP
The following is a typical execution of the discovery process using /etc/deviceIP.conf:
Reading deviceIP: 172.20.35.175 acmetw4-480a # Test Host
Start Discover::fromIP on 172.20.35.175
- snmp sysDesc is Sun SNMP Agent, Sun-Fire-480R
- found 1 device(s) using Discover::6130
Reading deviceIP: 172.20.35.32 etw4-lsi8 # Single SE-6130 Array Tray
Start Discover::fromIP on 172.20.35.32
- found 1 device(s) using Discover::6130
Reading deviceIP: 172.20.35.102 etw4-sw102 # 2Gb 16 port Qlogic Switch
Start Discover::fromIP on 172.20.35.102
- snmp sysDesc is QLogic SANBox2 FC Switch
- found 1 device(s) on Discover::Switch
Reading deviceIP: 172.20.35.192 acmetw4-sw192 # 1Gb 8 port Qlogic Switch
Start Discover::fromIP on 172.20.35.192
- found 1 device(s) on Discover::Switch
Adding devices from deviceIP.local to configuration:
adding device : acmetw4-480a/200600a0b816f5f4/ip=172.20.35.32
merging device : acmetw4-lsi8/200600a0b816f5f4/ip=172.20.35.32
adding device : acmetw4-sw102/100000c0dd00bfda/ip=172.20.35.102
adding device : acmetw4-sw192/100000c0dd005732/ip=172.20.35.192
To discover devices using the search subnet method:
a. Change your directory to the /opt/SUNWstade/bin directory
# root@acmetw4 cd /opt/SUNWstade/bin
b. Execute the ras_admin command specifying the function argument discover_subnet with the argument -I ipaddr,ipaddr...ipaddr
# root@acmetw4 ./ras_admin discover_subnet -I 'acmetw4-480a,172.20.35.32,acmetw4-sw102,acmetw4-sw192'
A typical discovery process using the subnet method follows.
Start Discover::fromIP on 172.20.35.175
- snmp sysDesc is system.sysDescr.0 = Sun SNMP Agent, Sun-Fire-480R
- found 1 device(s) using Discover::6130
Start Discover::fromIP on 172.20.35.32
- found 1 device(s) using Discover::6130
Start Discover::fromIP on 172.20.35.102
- snmp sysDesc is system.sysDescr.0 = QLogic SANBox2 FC Switch
- found 1 device(s) on Discover::Switch
Start Discover::fromIP on 172.20.35.192
- snmp sysDesc is system.sysDescr.0 = SANbox1-8
- found 1 device(s) on Discover::Switch
Adding devices from subnet.local to configuration:
adding device : acmetw4-480a/200600a0b816f5f4/ip=172.20.35.32
adding device : acmetw4-sw102/100000c0dd00bfda/ip=172.20.35.102
adding device : acmetw4-sw192/100000c0dd005732/ip=172.20.35.192
merging device : acmetw4-lsi8/200600a0b816f5f4/ip=172.20.35.32
device : acmetw4-lsi8/200600a0b816f5f4/ip=172.20.35.32
a. Change your directory to the /opt/SUNWstade/bin directory
# root@acmetw4 cd /opt/SUNWstade/bin
b. Execute the ras_admin command specifying the function argument discover_inband:
# root@acmetw4 ./ras_admin discover_inband
A typical discovery process using the inband method follows:
Discover::inband: trying Discover::3310
Discover::inband: trying Discover::6130
- found 1 device(s) using Discover::6130
Discover::inband: trying Discover::A3500FC
Discover::inband: trying Discover::Luxadm
Discover::inband: trying Discover::HBAApi
Start Discover::fromIP on 172.20.35.102
- snmp sysDesc is QLogic SANBox2 FC Switch
- found 1 device(s) on Discover::Switch
Start Discover::fromIP on 172.20.35.192
- found 1 device(s) on Discover::Switch
- found 2 device(s) using Discover::HBAApi
Adding devices from inband.local to configuration:
adding device : acmetw4-sw102/100000c0dd00bfda/ip=172.20.35.102
adding device : acmetw4-sw192/100000c0dd005732/ip=172.20.35.192
merging device : acmetw4-lsi8/200600a0b816f5f4/ip=172.20.35.32
3. Initialize all agents to report in to the Storage Automated Diagnostic Environment Enterprise Edition. This step is required to be run on all slave hosts that will report into the master agent.
example: # /opt/SUNWstade/bin/ras_install -s <hostname>
where hostname is the IP name or IP address of the host on which the master agent is installed.
4. Setup Notification Providers
Notification setup is required to ensure that should something adverse occur to your storage network, the Storage Automated Diagnostic Environment Enterprise Edition can notify someone about the problem. There are two classes of notification providers: local notification and remote notification. Local notification methods include local Email, SNMP traps, and SunMC. Remote notification methods are specifically targeted at Sun Service and include NSCC email and Net Connect.
To set up local Local Email notification:
a. Change your directory to the /opt/SUNWstade/bin directory
# root@acmetw4 cd /opt/SUNWstade/bin
b. Execute the ras_admin command specifying the function argument email_add with the argument -e <email address of user>
# root@acmetw4-480a ./ras_admin email_add -e employee1@acmetw2.com
c. Repeat Step b. for each email notification recipient you want to add.
A list of the current email notification recipients is displayed.
Entry Email/Events Type Device Priority Events
------ ----------------------------- ---------- ---------- --------- --
1 employee1@acmetw4.com Email All All All
2 employee2@acmetw2.com Email All All All
a. Change your directory to the /opt/SUNWstade/bin directory
# root@acmetw4 cd /opt/SUNWstade/bin
b. Execute the ras_admin command specifying the function argument provider_on with the argument -p sunmc -f <report frequency> -i <sunmc server address>.
In the following example, the SunMC host is acmetw4-sunmc and the reporting frequency is 1 hour.
# root@acmetw4-480a ./ras_admin provider_on -p sunmc -f 1 -i acmetw4-sunmc
To set up an SNMP Trap notification recipient:
a. Change your directory to the /opt/SUNWstade/bin directory
# root@acmetw4 cd /opt/SUNWstade/bin
b. Execute the ras_admin command specifying the function argument provider_on with the argument -p trap -i <SNMP receiver address> -o <SNMP port> -l <notification level> -t <trap slot number>.
In the following example, the SNMP trap receiver host is acmetw4-openview, the trap port number is 1992, the desired reporting level is 'error' and this is the first of five possible definitions in the SNMP traps table.
# root@acmetw4-480a ./ras_admin provider_on -p trap -i acmetw4-openview -o 1992 -l error -t 1
a. Change your directory to the /opt/SUNWstade/bin directory
# root@acmetw4 cd /opt/SUNWstade/bin
b. Execute the ras_admin command specifying the function argument provider_on with the argument -p nscc_email.
# root@acmetw4-480a ./ras_admin provider_on -p nscc_email
To enable Net Connect notification:
a. Change your directory to the /opt/SUNWstade/bin directory
# root@acmetw4 cd /opt/SUNWstade/bin
b. Execute the ras_admin command specifying the function argument provider_on with the argument -p netconnect.
# root@acmetw4-480a ./ras_admin provider_on -p netconnect
5. Check the revision of devices:
# root@acmetw4-480a ./ras_revcheck -h acmetw4-480a -M ALL -p
The following is a typical revision report display:
Type Name Status Curr_Ver Expect_Ver Curr_Patch Expect_Patch Comments
6130_Controller acmetw4-480a.firmrev DOWNREV 06.10.05.11 06.10.09.11 N/A no patch information available, please contact your sun representative
6130_NVSRAM_FW acmetw4-480a.nvsram. DOWNREV N2882-610843-010 N2882-610843-011 N/A no patch information available, please contact your sun representative
6130_DISK_FW acmetw4-480a.Tray.0.Drive.1 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.10 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.11 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.12 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.13 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.14 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.2 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.3 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.4 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.5 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.6 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.7 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.8 PASS 0307 0307
6130_DISK_FW acmetw4-480a.Tray.0.Drive.9 PASS 0307 0307
Driver DOWNREV 114478-04 114478-05 SNIA Sun Fibre Channel Host Bus Adapter Library
Driver PASS 113044-05 113044-05 cfgadm fp plug-in and required by Brocade switch. This patch requires the packages SUNWswan, SUNWcfpl and SUNWcfplx.
Driver PASS 113043-08 113043-08 MPxIO luxadm, liba5k and libg_fc patch. Required by Brocade switch
Driver PASS 111847-08 111847-08 SAN foundation kit patch
Driver PASS 113039-07 113039-07 leadville, Sun StorEdge Traffic Manager patch
Driver PASS 113040-09 113040-09 MPxIO fctl/fp/fcp/usoc driver patch and required by Brocade switch
Driver DOWNREV 113041-06 113041-07 MPxIO fcip driver and adb macros patch. Required by Brocade switch
Driver DOWNREV 114476-03 114476-04 fcsm driver patch
Driver PASS 114477-01 114477-01 Common Fibre Channel HBA API Library
Driver OWNREV 113277-24 113277-25 st driver for tape devices
Driver DOWNREV 113042-07 113042-08 MPxIO qlc driver patch and required by Brocade switch
HBA /devices/pci@8,600000/SUNW,qlc@1/fp@0,0:devctl PASS 1.14.09 1.14.09 114873-02 Gb HBA
HBA /devices/pci@8,600000/SUNW,qlc@2/fp@0,0:devctl PASS 1.14.09 1.14.09 111853-03 1Gb HBA
HBA /devices/pci@9,600000/SUNW,qlc@2/fp@0,0:devctl DOWNREV 1.14 1.14.09 111853-03 1Gb HBA
Switch diag192 PASS 40242 40242 112429-08 FC-SW2 compliant 1G switch
Switch diag102 UPREV V2.0.0.5-0 V1.3.60.00 112429-08 G switch
Once Storage Automated Diagnostic Environment Enterprise Edition is installed, a cron job is set up to run the agent automatically.
This optional step may be performed to force an agent run out of cycle, but is not required since the monitoring agent cron runs once every five minutes by default. Running the agent now will cause notification to occur from the previous setup steps.
# root@acmetw4-480a ./rasagent -d2
Agent running /opt/SUNWstade/DATA/rasagent.conf on 09-24 11:02:01, MASTER acmetw4-480a
7. Examine the Topology details (Optional)
Review your topology details by first getting the name of the topology to view using topo_list argument to ras_admin then displaying the details of that topology using ras_admin topo -t <topo_name>.
In the following example, we view the topology for our newly installed system, acmetw4-480a.
# root@acmetw4-480a ./ras_admin topo_list
------------------------------ -------------------------------
acmetw4-480a 2004-09-24 11:15:03
MERGE-MASTER 2004-09-24 11:15:04
# root@acmetw4-480a ./ras_admin topo -t acmetw4-480a.
host 'acmetw4-480a' SUNW,Sun-Fire-480R
hba-0: 210000e08b19edcb /devices/pci@8,600000/SUNW,qlc@1/fp@0,0:devctl
Connected to acmetw4-sw102 port-2
hba-1: 210000e08b032701 /devices/pci@8,600000/SUNW,qlc@2/fp@0,0:devctl
Connected to acmetw4-sw192 port-1
hba-2: 21000003ba7b104e /devices/pci@9,600000/SUNW,qlc@2/fp@0,0:devctl
Connected to 500000e0109404d0 port-0
switch2 'acmetw4-sw102/' Switch2-16
port-0: 200700a0b816f5f5 F_Port
Connected to acmetw4-480a port-2
port-2: 210000e08b19edcb F_Port
Connected to host 'acmetw4-480a. ' hba-0
switch2 'acmetw4-sw192/' Switch1-8
port-1: 210000e08b032701 F_Port
Connected to host 'acmetw4-480a. ' hba-1
port-3: 200600a0b816f5f5 F_Port
Connected to acmetw4-480a port-0
6130 'acmetw4-480a' SUN Sun 6130
Connected to acmetw4-sw192 port-3
Connected to acmetw4-sw102 port-0
hbastorage '500000e0109404d0' FUJITSU MAP3735F SUN72G
port-0: 500000e0109404d1 /devices/pci@9,600000/SUNW,qlc@2/fp@0,0:devctl
Connected to host 'acmetw4-480a. ' hba-2
Follow the instructions in this section to get started setting up the Storage Automated Diagnostic Environment using the GUI.
|
Note - After logging in, refer to the online help for more information on the steps in this section. |
1. From a web browser, log in the Sun Web Console using URL https://<hostname>:6789.
a. Enter the User Name that was defined in the Installation Instructions, Step 7.
b. Enter the Password that was defined in the Installation Instructions, Step 7.
c. Select the sa_admin role from the pull-down list.
d. Enter the Password that was defined for the sa_admin role in the Installation Instructions, Step 7.
2. Click Storage Automated Diagnostic Environment
3. Enter your Site Information
a. Click Storage Automated Diagnostic Environment.
b. Complete the required fields on the Site Information page.
|
Note - Fields marked with a red asterisk are mandatory. You will be unable to continue until this page is completed and saved successfully. |
b. Verify that host information is entered correctly and that all expected hosts are present.
Three methods of device discovery are available:
To discover devices using the In-Band method:
a. Select the Inventory Tab -> Discovery.
b. Select the appropriate agent or All Agents from pull-down list. (Note: The selected agents must have in-band access to the desired devices.)
c. Select Inband from the Discovery Mechanism pull-down list.
d. Optionally, choose a device-naming convention by making a Prefix selection.
e. Accept the remaining defaults and click Start Discovery.
To discover devices using the Out-of-Band (IP) method:
a. Select the Inventory Tab -> Discovery.
b. Select the appropriate agent or All Agents from pull-down list. (Note: The selected agents must have intranet access to the desired devices.)
c. Select IP from the Discovery Mechanism pull-down list.
d. Specify the IP addresses to be discovered.
e. Optionally, choose a device-naming convention by making a Prefix selection.
f. Accept the remaining defaults and click Start Discovery.
To discover devices using the Out-of-Band (File) method:
a. Enter the desired devices into the selected agents /etc/deviceIP.conf file.
b. Select the Inventory Tab -> Discovery.
c. Select the appropriate agent or All Agents from pull-down list. (Note: The selected agents must have intranet to the desired devices.)
d. Select File from the Discovery Mechanism pull-down list.
Revision Analysis should be run after installation and whenever new components are added to the system. Updating all firmware and software components to the current revisions ensures that the devices have the capabilities required to be discovered, monitored and diagnosed properly.
a. Select the Administration tab.
b. From the Actions pull-down list, select Run Revision Analysis.
c. Select the Host on which Revision Analysis is to run, the Revision Matrix to be used for revision checking, All modules, and, if desired, enter an email address to which the results will be sent.
You can configure a number of methods for generating notification of alarm conditions:
To configure Email recipients:
a. Select Administration -> Notification -> Setup.
b. To enable Local email, add the desired SMTP server under the Email Notification Setup section called "Use this SMTP server for Email".
|
Note - If the host running this software has the sendmail daemon running, you can enter localhost or the name of this host in this field. |
c. Click Save to verify the email configuration.
e. Enter one or more email addresses for local notification. Specified addresses receive email notifications when events occur. Emails can be customized to specific severity, event-type, or product type.
To configure SNMP trap recipients:
a. Select Administration -> Notification -> Setup.
b. In the Remote Notification Setup section, check SNMP Trap.
e. For each SNMP recipient you want to add, specify the name or IP Address of the recipient, the port on which to send traps, and, optionally, the minimum alert level for which you want SNMP notification, and click OK.
To configure remote notification recipients:
a. Select Administration -> Notification -> Setup.
b. Check the box next to each Remote Notification provider you want to enable.
c. Complete the setup parameters for any remote notification recipient that you enable.
You can manually run the monitoring agents.
a. Select the Administration Tab -> Agents.
b. Click the check box for the agent you want to run.
|
Note - If you do not click Run Agent, the selected agents will automatically run after 5 minutes. |
d. Repeast steps b and c for each agent.
f. Display the topology from each agent as well as a master view.
This section provides general and device- and product-specific information for using the product.
The following information applies to localization of the product.
You can select your choice of font size in Netscape or Mozilla browser by: selecting an appropriate "Minimum font size" in the Edit -> Preferences -> Appearance -> Fonts menu of your browser. For example, you can select "12" or "14" as "Minimum font size".
Or you can select an appropriate "Text Zoom" choice in the browser's View menu.
To display the man pages in Japanese using the man page command, you must use ja locale and update your MANPATH variable with one of the following procedures.
To update your MANPATH Variable in a Bourne or Korn Shell:
i. Update your .profile file MANPATH statement to include /opt/SUNWstade/man and make sure your MANPATH is exported.
# MANPATH=$MANPATH:/opt/SUNWstade/man
ii. Save this file and exit the editor.
iii. Reload your .profile file for your shell session.
To update Your MANPATH Variable in a C Shell:
i. Add /opt/SUNWstade/man to your MANPATH statement in your .login file:
setenv MANPATH $MANPATH:/opt/SUNWstade/man
ii. Save this file and exit the editor.
iii. Reload your .login file for your shell session.
Otherwise, notification messages are received with garbled characters in place of the site information fields. If you are not sure if your Email system supports UTF-8 encoding, enter and save only ASCII characters in the Site Information text fields.
Use this procedure for setting up the SE 5210 device to send SNMP traps to the Storage Automated Diagnostic Environment Enterprise Edition host:
1. Start up the SE 5210 device Web Admin application by entering the IP address of the device in your web browser and pressing Return.
2. Enter the device password and click Apply.
3. From the Web Admin sidebar, select Monitoring and Notification -> Configure SNMP.
4. Check the Enable SNMP check box.
5. Enter "public" in the Server SNMP Community Field.
6. Enter the IP address of the Storage Automated Diagnostic Environment Enterprise Edition host in the Destination IP address column.
7. Enter "1162" in the corresponding Port # column. Port 1162 is the port on which the Storage Automated Diagnostic Environment Enterprise Edition listens for SNMP traps.
8. Enter "2" in the Version column.
9. Enter "public" in the Community column.
10. Check the Enable check box.
This release provides limited password support for 3310, 3510 and 3511 devices. You can monitor the 3310/3510/3511 devices with password setup but be aware of the following:
# /opt/SUNWstade/bin/ras_admin password_change -i <ipaddress> -p <password>
where ipaddress is the IP address of the device and password is the password you are assigning to the device.
Brocade FC Switch configurations using QuickLoop ports can be monitored and diagnosed but the topology views will not show connections between devices.
The following information applies to the SAM-FS/QFS product.
i. /opt/SUNWsamfs/sbin/samd stop
ii. /opt/SUNWsamfs/sbin/samd config
iii. /opt/SUNWsamfs/sbin/samd start
Change TRAP_DESTINATION to read:
TRAP_DESTINATION=`hostname`:1162
Example: TRAP_DESTINATION=172.20.35.00:1162
or: TRAP_DESTINATION=Fido:1162
Sets the trap destination to the NIS named host "Fido" port 1162.
or: TRAP_DESTINATION=`hostname`:1162
Sets the trap destination to the local host port 1162.
If the Solaris host that the Master is installed on uses 'compat' in the /etc/nsswitch.conf file, the Administrator must manually set the User Password. Checking the "NIS Password" box does not work in conjunction with 'compat'.
In order to monitor HDS, the monitoring host must be given SNMP access to the HDS array.
If you had JNI HBA cards installed with the previous version of SUNWstade, you will need to run topology discovery again in order for this release to see the JNI HBA cards.
This section identifies known issues with the SUNWstade and SUNWstadm product components.
This section identifies known issues with the SUNWstade base package.
Reference BugId: 5044120 "3310/3120 JBOD - Not displaying disk information"
No adverse conditions or errors will occur, however the Storage Automated Diagnostic Environment Enterprise Edition would never receive an SNMP trap or post an alarm for that instance of SAM-QFS.
This section identifies known issues with the SUNWstadm management station package.
Workaround: Remove the /usr/bin/true entry from the /etc/passwd with the following command:
Workaround: Modify the permissions on the root directory so that "others" (noaccess) have both read and execute permissions.
# tail -2 /var/log/webconsole/console_debug_log
Error occurred during initialization of VM
java.lang.Error: Properties init: Could not determine current
working directory.
Workaround: Modify the permissions on the root directory so that "others" (noaccess) have both read and execute permissions.
Once the workaround is applied start the Sun(TM) Web Console using the following command:
# /usr/sadm/bin/smcwebserver start
Reference BugId: 5109055 Web Console startup fails when the root directory restricts other access
java.io.IOException: Illegal to flush within a custom tag
If this occurs you will need to upgrade Tomcat to version 4.0.3 or later.
If this occurs, inspect Lockhart's java.home setting using the Lockhart smreg(1M) command as follows:
# /usr/sbin/smreg list -p | grep java.home
If it does not point to the SDK location or if it incorrectly references the JRE or an earlier version of the SDK, update it using smreg(1M) and restart the Sun (TM) Management Console using the smcwebserver(1M) command as follows:
# /usr/sbin/smreg add -p -c java.home=/usr/j2se
# /usr/sadm/bin/smcwebserver restart
The following table lists the issues that have been resolved with the product.
This section lists the documentation provided with this product and lists other related documentation.
The product includes online help for all functions and the following Man Page documentation is delivered with this product:
The following table lists all related documentation.
If you need help installing or using this product, go to:
http://www.sun.com/service/contacting
| Sun Storage Automated Diagnostic Environment Enterprise Edition Release Notes | 819-0432-10 | |
Copyright © 2004, Sun Microsystems, Inc. All Rights Reserved.