##
Storage Automated Diagnostic Environment
Graphical User Interface Guide
System Edition

Table of Content

-Introduction | Introduction
-Navigation | Navigation
Administration | Software Adminstration
-General Maintenance | General Software Maintenance
-Site Information | Used to enter site Information, address, contact names etc..
-Maintain Hosts | Used to configure Monitoring Agents
Update Master Configuration | Update Master Configuration
Sun StorEdge T3 MessageLog Monitoring | Sun StorEdge T3 MessageLog Monitoring
-Add Host | Add a Host/Agent manually.
-Update Host | Update Host agent information
-Maintain Devices | Maintain information about specific devices
Delete a Device | Delete a Device
Rename a Device | Rename a Device
Manually Update a Device | Manually Update a Device
-Local Notification (Email/Scripts) | Used to generate emails and scripts to local administrators and local systems.
-Add Local Notification Entry | Add a new Email Notification
-Remote Notification Providers | Used to control event notification to remote systems like SRS, NetConnect, etc..
SRS Provider | SRS Provider
SAE Provider | SAE Provider
NetConnect Provider | NetConnect Provider
SSRR Provider | SSRR Provider
SunMC Provider | SunMC Provider
Email Provider | Email Provider
SNMP Provider | SNMP Provider
-Start/Stop Agents | Used to selectively activate or deactivate the monitoring agents
-Start/Stop Devices | Used to selectively activate or deactivate the monitoring of storage devices.
-Admin Groups | Admin Groups
-Test email | test email
-Review Config | Verify the validity of the software configuration
-Config Options | Software Configuration Options
Setting your Browser Window | Setting your Browser Window
-Optimization/FSA | Monitoring Optimization / Fault Signature Analysis Options
-Event Filters | Event Filtering
-Topo. Maintenance | Topology maintenance: Add topos, merge topos, etc..
-Topology Snapshot | Request Topology Snapshots from each hosts .
Topology Snapshot | Topology Snapshot
-Topo history | Display archived Topology information of the selected host or previously configured selection of multiple hosts.
-System Utilities | System Utilities, logins, roles, etc..
-System TimeOuts | Allows to adjust the timeouts used by the monitoring agents
-Erase Cache | This function will erase the last report generated by instrumentation modules. Data will be lost permanently
-Run Agent | Used to run the monitoring agent manually.
-Email Config | Email a detailed monitoring report complete with a graphical topology.
-Run scripts | Run pre-selected scripts
-Root password | Used to changed the 'root' password of this software
-Login/Roles | Maintain Logins and Permissions
-Define Admin-Groups | Define Administration Groups
-Clear Login | Clear the current user and allow to re-login
Logging into the Web Browser | Logging into the Web Browser
-App. Launcher | Launch external browser-based software
Monitor | Storage Monitoring
-Monitor Devices | List of Monitored devices.
Monitor Device Tips | Monitor Device Tips
-Review Devices | Review device information: state, alerts, etc..
Device Summary | Device Summary
Graph Summary | Graph Summary
Health Report | Health Report
- Monitor Topology | Access device information from a topology graph.
Topology Feature Hints | Topology Feature Hints
Topology Footer Feature Hints | Topology Footer Feature Hints
Topology Icon Definitions | Topology Icon Definitions
Topology Health | Topology Health
Clear Alerts | Clear Alerts
MPxIO Link Errors | MPxIO Link Errors
Fibre Channel Errors | Fibre Channel Errors
-Monitor Log | Review Alert/Event/Error log files.
-Monitor Log | Review Alert/Event/Error log files.
-Messages | Review devices and hosts message log files.
-Event Log | Used to search the Event Log
Events, Alerts, and Alarms | Events, Alerts, and Alarms
-Alert Log | Used to search the Alert Log, note: alerts are actionable events
-Agent Errors | Displays all the system errors generated by the monitoring software
-Display Alerts | Display Alert Log
-Display Events | Display Event Log
-Utilities | Monitoring Utilities
-Clear Device Health | Clear Current Device errors/warnings and Link errors/warnings from the State database. This will only affect the current health status of the device.
-Solution Extract | Extract a snapshot of the configuration of this Sun Solution
Diagnose | Run Diagnostics
-Diagnostic Tests | Run Diagnostics Tests
-Test from Topo. | Execute test from the Site Topology
Graphical User Interface (GUI) Tests | Graphical User Interface (GUI) Tests
-Test from List | Execute test from a list of physical devices
Test Rules | Test Rules
-Test Manager | Review and control diagnostic tests
Delete Tests | Delete Tests
-Test Mgr.(popup) | Review and control diagnostic tests in a separate window
-Test Archive | Review the results of archived tests
-Run Test |
-Link Test | Link Test
-Revision Reports | Run Revision Checking report
-Revision Reports | Run Revision Checking report
-Run Report | Start Revision Checking on specific product categories
-Display Report | Review revision checking reports
-Display History | Review historical revision checking reports
-Utilities | Diagnostics Defaults
-Set Defaults | Set the default options for each available test
Verify the SAN | Verify the SAN
Manage | Storage Management
-Configuration | Storage Configuration
-Configure 3900/6900 | Configure Sun StorEdge 3900/6900 series
Configure Sun StorEdge T3 Arrays | Configure Sun StorEdge T3 Arrays
Configure the Sun StorEdge Network FC Switch | Configure the Sun StorEdge Network FC Switch
Configure the Virtualization Engine | Configure the Virtualization Engine
-Utilities | Utilities
-Continuous Volume Verify | Execute 'volume verify' continuously on arrays
Reports | Run Reports
-General Reports | Traffic, Fru and Event Reports
-Traffic Report | Display Inframes/Outframes for each port of the supported switches.
-Fru Reports | Display fru report
-FruReport History | Fru Report History and comparisons
-Exception Report | Run and display exception reports. Exceptions are defined in System/exception.conf (T3 only)
-Event Reports | Display Event report
-Device Health | Display all devices with health and alert information.
-Device Health Summary | Display all devices health
-Array Performance | Array Performance
-System Reports | System Reports, Event Mapping, etc..
-Agent Stats | Agent Execution Statistics
-Email/Events Maximums | Email/Events Maximums Statistics
-Thresholds List | Display the thresholds used to generate events
-Switch Data | Display Fibre Channel Counters as a report for all supported switches (expert only)
-Event/Severity Mapping | Policies used to generate events.
-Service Advisor | Service Advisor and Event Advisor (pdf)
-Event Advisor | List of all events with information, Probable Cause and Action
-Asc/ Ascq | Additional Sense Data
Help Section | Help System
-Help | Detailed help for each section of the GUI
-Architecture | Architecture Diagram
-Diagnostics | List of Diagnostics and Exercisors programs
-Utilities | List of Utilities
-Abbreviations | Abbreviations

Introduction | [ Top ]

### Welcome

The Storage Automated Diagnostic Environment (Storage A.D.E.) is a distributed online health and diagnostic monitoring tool for storage area network (SAN) devices. It can be configured to monitor on a 24-hour basis, collecting information that enhances the reliability, availability, and serviceability (RAS) of the storage devices it supports.

The Storage A.D.E. offers the following features:

- A common web-based user interface for device monitoring and diagnostics
- Distributed test invocation by means of lists or topology using the GUI or CLI
- Topology grouping for multi-level hosts and components
- Alternate master support for redundancy
- Revision checking
- Support for the Storage Service Processor components of Sun StorEdge series offerings
- Remote notification through various providers
- Encryption by way of a Secure Socket Layer (SSL) protocol

[ ROOT.about:overview ]

Navigation | [ Top ]
|  | Storage Automated Diagnostic Environment (StorEdge ) | Login | Help | Home
Administration |  | Monitor |  | Diagnose |  | Manage |  | Reports |
| ROOT | v[IP_NO]x
General Maintenance | | | Topo. Maintenance | | | System Utilities

[ GUI::Navigation::index ]

Navigation |

Navigation is controlled by tabs displayed at the top of each page. Tabs can be active, inactive or invisible.
An inactive tab indicated that the function is installed but is not available to the current user, usually because this user does not have the appropriate permissions.
To navigate the user interface, a tab must be selected, followed by a sub-tab. Most sub-tabs give access to a menu of functions. When 'frames' are active, the bottom part of the screen usually include a left frame where this menu is always available and a right frame when the functions are displayed.
With 'frames' off, the left frame is not available and is replaced by bread crumbs on the main function page.

[ ROOT.navigation:navigation ]

Administration > General Maintenance > Site Information | [ Top ]
Storage Automated Diagnostic Environment
Site Information | [ Help ]
Used to enter site Information, address, contact names etc..
Customer Information
Customer Name: | * Mandatory
Customer No: |
Contract No: |  | Stock Symbol: |
Site Information
Site Name: | *

Address:
City: *
State: Zip Code: *
Country: *
Contact: *
Phone No: Contact Email: *

[ GUI::Config::site ]

Site Information

Maintain Site Information |

From the General Maintenance window, select Site Information.

Note:

- The fields on this page must be completed before you proceed.
- The fields with an asterisk (*) are mandatory.

To update the master configuration, complete the following fields:

- Customer Name
- Customer Number
- Contract Number
- Stock Symbol
- Site Information
  - Site Name
  - Address and Phone Number
  - Contact email address

Click Submit. Your site information is updated.

See Also:

- 'Maintain Hosts

- 'Set Browser Window

[ admin.gen_maint.site_info:siteinfo ]

Administration > General Maintenance > Maintain Hosts | [ Top ]
Storage Automated Diagnostic Environment
Maintain Hosts | [ Help ]
This page contains the list of all monitoring hosts in this installation. [Add a new Slave] registers a new host with this installation. An agent must already be installed on this host prior to executing this function. [Ping Slaves] verifies that all slaves are available and retrieves their hostid and agent version. [Push Slave Configs] transmits the configuration (address, hosts, devices, emails) to all the Slave Hosts.
[ Update All Hosts ]
Existing Hosts | AdminGroup:
Host Name | Type | #Devs | Host IP | Active | Ping /Hostid | Admin Group
ccadieux.site | Master | 15 | [IP_NO] | Yes |  | gn
crashme41.site | Slave | 0 | [IP_NO] | No |  | gn
jeannot.site | Slave | 0 | [IP_NO] | No |  |

[ GUI::Hosts::list ]

Maintain Hosts

Maintain Hosts |

When the Storage Automated Diagnostic Environment package is installed on a host, it registers with the master agent and an entry is added to this page. For this automatic registration to work, you must first install and run the master agent. A 'Y' will appear in the Active field of the Maintain Hosts window. Once all hosts are installed, you can access this page to change the configuration of each host.

The three main functions of the Maintain Hosts window are:

- Add a New Slave - Use when the agent does not automatically register. This can occur if a previously-installed instance is temporarily deleted from the configuration. Note that the slave is not active if manually added.
- Ping Slaves - Verify that the agent at each host is running. The master will ping the slaves and request their hostid to verify that the host is running and that the Storage Automated Diagnostic Environment service is available.
- Push Slave Configurations - After all the slaves have been updated, you can push the new configurations to the respective master by using Push Slave Configs. Each instance of the Storage Automated Diagnostic Environment has identical copies of the configuration file, but the administration of the slaves is done from the master.

If N appears in the Active field, you can activate the host using the procedures in 'Start or Stop Agents.

Note:
Click the Update All Hosts link to access the Maintain Hosts: Update All Hosts window.
In addition, you can click the Update All Hosts link from the Maintain Hosts window to change the monitoring frequency setting for all hosts at one time.

See Also:

- 'Maintain Site Information
- 'Add a New Slave

[ admin.gen_maint.maintain_hosts:maintainhosts,masterconfig,t3monitoring ]

Update Master Configuration

Update Master Configuration |

From the Maintain Hosts window, click an existing Host Name link and update the fields as required.

Updatable fields include the following:

- Categories to Monitor

  Select from the available categories supported with this instance of the Storage Automated Diagnostic Environment. You must make at least one selection.
  Categories from which to choose include all devices supported by this version of Storage Automated Diagnostic Environment.

- Monitoring Frequency

  Select a variable between 5 and 120 minutes. The frequency variable affects how often the Storage Automated Diagnostic Environment executes. The default is 60 minutes.

- Monitor InBand Data Path

  Select this checkbox to enable monitoring of the in-band data path.

- Show Only Monitored Devices in Topology Graph

  When checked, Topology shows only the devices in the Topology graph. In addition, only devices monitored by that agent will be displayed in the agent's topology.

- Message Log

  The path for the message log. The default is `/var/adm/messages`, which displays the history of the status messages.

- Sun T3 Message Log

  Type the path for the host's Sun StorEdge T3, T3+, or 6120 array message log. The path should be the path to where the array logs are being sent. This field is used to tell the Storage Automated Diagnostic Environment where to look for the log files. It does not alter the location to where the Sun StorEdge T3, T3+, or 6120 array actually sends the log files.

Note:
You can check and verify the path by looking at the `/etc/syslog.conf` on the host.

See Also:

- 'Add a Device
- 'Maintain a Device
- 'Update a Device
- 'Delete a Device
- 'Rename a Device
- 'Start or Stop Devices

[ admin.gen_maint.maintain_hosts:maintainhosts,masterconfig,t3monitoring ]

Sun StorEdge T3 MessageLog Monitoring

Set Up Sun StorEdge Array Message Monitoring |

In order for the Storage Automatic Diagnostic Environment software to monitor messages from a Sun StorEdge array, you must mirror the Sun StorEdge array's `/syslog` to a host with the Storage Automated Diagnostic Environment installed and configured to monitor Sun StorEdge arrays.

1. Refer to the Sun StorEdge Installation and Configuration Manual for procedures on how to set up the Sun StorEdge array and the host to forward `syslog` messages.
2. Refer to 'Maintain Hosts section to configure each host with the name given to the array message log file.

[ admin.gen_maint.maintain_hosts:maintainhosts,masterconfig,t3monitoring ]

Administration > General Maintenance > Add Host | [ Top ]
Storage Automated Diagnostic Environment
Add Host | [ Help ]
Add a Host/Agent manually.
Enter Host Information
HostID: |
Host Name: |
Special Contract: |
Categories to Monitor Abbreviations |
: | Sun 3510
: | Sun 6120
: | Brocade Silkworm
: | Host
: | FC-Counters
: | Sun SVE2
: | Sun 2GB Switch
: | Sun Switch
: | Sun T3
: | Sun VE
Monitoring Frequency: |
Alternate Master: |
Monitor InBand DataPath: |
Show only monitored devices in topology graph.: |
Enter Logfiles Locations
Message Log: |
/var/adm/messages
Storage Array Message Log: |

[ GUI::Hosts::add ]

Add New Slave

Add a New Slave |

If a slave agent does not automatically register, you can add a new slave manually.

To access the Add Host window:

1. Click the Maintain Hosts link on the Storage Automated Diagnostic Environment window.
2. Click the Add a new Slave button on the Maintain Host window.

The Maintain Hosts: Add Host window is displayed.

Note: The Categories to Monitor choices indicate Sun Microsystem network storage devices that are supported with the Storage Automated Diagnostic Environment.

- Type an 8-digit, alphanumeric HostID, which is the same as the system ID, in the `/usr/sbin/hostid` directory. You can use the `hostid` command on the host to obtain a valid hostID.
- Type the name of the host (`hostname.domain`).
- Choose the devices the Storage Automated Diagnostic Environment will monitor. The categories you specify are supported with this instance of the Storage Automated Diagnostic Environment.
- From the Monitoring Frequency drop down menu, select a variable between five and 120 minutes. This frequency variable affects how frequently the cron executes the health monitoring agents. The default setting is 5 minutes.
Note:
By default, the Storage Automated Diagnostic Environment is activated by a cron every 5 minutes. The program automatically checks the last run, notes the current time, and compares this time to the last time the cron executed. If the time exceeds 60 minutes, it executes again.

- The alternate master checkbox is enabled the first time you add a new slave. For the slave to be an alternate master, you must disable this checkbox.
- Enable the Sun StorEdge 3900 and 6900 series button if the device or devices the Storage Automated Diagnostic Environment will monitor are part of a Sun StorEdge 3900 or 6900 series solution.
- Enable the Monitor In-Band Data Path button if you want to view devices on the topology of a host that are accessible in-band by that host.
- The default message log path is `/var/adm/messages`, which displays the history of the status messages.
- The T3 message log path is to where the Sun StorEdge T3 and T3+ array logs are sent. You can check and verify the path by looking at the `/etc/syslog.conf` on the host.

3. Click Add to add the new host.
Caution:If the system you are adding as a slave is currently a master, the following message is displayed: WARNING: System is currently configured as a master. Please use the Push Slave Configs section to change this system to a slave.

4. To automatically update the slave's configurations and to verify that all slaves agree with the master configurations, click Push Slave Configs from the Maintenance menu.

Notes:

- Enter an 8-digit hostID in the `/usr/sbin/hostid` directory. The Storage Automated Diagnostic Environment will not add a new slave without it.

  If you do not know the hostID, you can enter a dummy number and later correct it. Note, however, that the hostID cannot match any other previously-accepted hostID.

  The host you add as a slave must be accessible over the Ethernet from the master and must, at a minimum, be able to respond to a ping.

- If you manually enter a slave host, and no instance of the Storage Automated Diagnostic Environment is installed on that host, you must also manually enter the hostID for that slave host.

  Otherwise, the Categories to Monitor field will not have any devices selected, and the Storage Automated Diagnostic Environment will not be active.

  The Active state depends on the `rasagent.conf.push` slave configuration file in the `/var/opt/SUNWstade/DATA` directory, and also depends on whether the Active flag is set. If there is simply no slave configuration file (for example, if the host is a master), the Active state will be set to OFF.

See Also:

- 'Maintain Site Information
- 'Maintain Hosts
- 'Discovery

[ admin.gen_maint.add_hosts:addnewslave ]

Administration > General Maintenance > Update Host | [ Top ]
Storage Automated Diagnostic Environment
Maintain Hosts | [ Help ]
This page contains the list of all monitoring hosts in this installation. [Add a new Slave] registers a new host with this installation. An agent must already be installed on this host prior to executing this function. [Ping Slaves] verifies that all slaves are available and retrieves their hostid and agent version. [Push Slave Configs] transmits the configuration (address, hosts, devices, emails) to all the Slave Hosts.
[ Update All Hosts ]
Existing Hosts | AdminGroup:
Host Name | Type | #Devs | Host IP | Active | Ping /Hostid | Admin Group
ccadieux.site | Master | 15 | [IP_NO] | Yes |  | gn
crashme41.site | Slave | 0 | [IP_NO] | No |  | gn
jeannot.site | Slave | 0 | [IP_NO] | No |  |

[ GUI::Hosts::list ]

Maintain Hosts

Maintain Hosts |

When the Storage Automated Diagnostic Environment package is installed on a host, it registers with the master agent and an entry is added to this page. For this automatic registration to work, you must first install and run the master agent. A 'Y' will appear in the Active field of the Maintain Hosts window. Once all hosts are installed, you can access this page to change the configuration of each host.

The three main functions of the Maintain Hosts window are:

- Add a New Slave - Use when the agent does not automatically register. This can occur if a previously-installed instance is temporarily deleted from the configuration. Note that the slave is not active if manually added.
- Ping Slaves - Verify that the agent at each host is running. The master will ping the slaves and request their hostid to verify that the host is running and that the Storage Automated Diagnostic Environment service is available.
- Push Slave Configurations - After all the slaves have been updated, you can push the new configurations to the respective master by using Push Slave Configs. Each instance of the Storage Automated Diagnostic Environment has identical copies of the configuration file, but the administration of the slaves is done from the master.

If N appears in the Active field, you can activate the host using the procedures in 'Start or Stop Agents.

Note:
Click the Update All Hosts link to access the Maintain Hosts: Update All Hosts window.
In addition, you can click the Update All Hosts link from the Maintain Hosts window to change the monitoring frequency setting for all hosts at one time.

See Also:

- 'Maintain Site Information
- 'Add a New Slave

[ admin.gen_maint.maintain_host:maintainhosts ]

Administration > General Maintenance > Maintain Devices | [ Top ]
Storage Automated Diagnostic Environment
Maintain Devices | [ Help ]
This page displays all monitored devices. Update devices by clicking the appropriate link. Use the 'Info' link to add information and comments to this device. Select a specific host from the 'Host:' drop-down to display devices monitored by this host only. A device can be marked On/Off/Off if the device is active (first value) but the device category has never been checked in 'Maintain Hosts' (second value) and the Agent is not running (third value) .
List Existing Devices | Admin Group: Host: |
Monitoring Host | DeviceName (select to update) | Dev.Type | Info. | IP Address | WWN/Key | Monitor Dev/Cat/Agent | Admin Group | Delete
ccadieux | diag103 | t3 | Info | [IP_NO] | 50020f.. | On Off On |  |
ccadieux | diag183 | McDATA | Info | [IP_NO] | 100008.. | On Off On | gs |
ccadieux | diag111 | Switch2 | Info | [IP_NO] | 100000.. | On Off On |  |
ccadieux | diag208 | t3b | Info | [IP_NO] | 50020f.. | On Off On |  |
ccadieux | diag211 | t3 | Info | [IP_NO] | 50020f.. | On Off On |  |
ccadieux | diag187 | Switch1 | Info | [IP_NO] | 100000.. | On Off On | gs |
ccadieux | diag140 | Switch2 | Info | [IP_NO] | 100000.. | On Off On |  |
ccadieux | diag141 | Switch2 | Info | [IP_NO] | 100000.. | On Off On |  |
ccadieux | 013203 | d2 | Info |  | /dev/e.. | On Off On | gs |
ccadieux | DSQA2 | a5k | Info |  | 508002.. | On Off On | gs |
ccadieux | tape-475b | tape | Info |  | 500104.. | On Off On |  |
ccadieux | diag192 | Switch1 | Info | [IP_NO] | 100000.. | On Off On |  |
ccadieux | diag99 | Switch1 | Info | [IP_NO] | 100000.. | On Off On |  |
ccadieux | 3310-000034 | 3310 | Info | [IP_NO] | 206000.. | On Off On | gn |
ccadieux | diag210 | 6120 | Info | [IP_NO] | 200300.. | On On On | gs |

[ GUI::Devices::list ]

Maintain Devices

Maintain Devices |

Use the Maintain Devices window to configure the host to monitor each device. You can also use this window to change the name that the Storage Automated Diagnostic Environment will use as a reference to that device through its email notifications.

Be aware of the host's access method when making decisions about which devices the Storage Automated Diagnostic Environment will monitor.

- Monitor Sun StorEdge arrays from the host that has access to the t3 message log file and has an Ethernet connection on the subnet.
- Monitor Sun StorEdge 6320 series systems from the Storage Service Processor, which has an Ethernet connection to the Sun StorEdge array.

Note:

The Primary Host column lists the registered host that does the actual probing of the device.

See Also:

- 'Update a Device
- 'Delete a Device
- 'Rename a Device
- 'Start or Stop Devices
- 'Review Configurations

[ admin.gen_maint.maint_device:maintaindev,deletedevice,renamedevice,updatedevice ]

Delete a Device

Delete a Device |

You can delete an unwanted device after the device has been removed from the site, or if device monitoring is no longer needed.

Note:

- Deleting a device from the configuration does not remove the access to the device instrumentation in the cache immediately. This will, however, be cleared the next time you manually run the agent.
- State information for that device is also maintained until the agent's next run. Therefore, a device can be removed from a configuration and still be viewed in the Topology and Instrumentation as a snapshot in time, until you once again take a new Topology snapshot.

See Also:

- 'Maintain a Device
- 'Update a Device
- 'Rename a Device

[ admin.gen_maint.maint_device:maintaindev,deletedevice,renamedevice,updatedevice ]

Rename a Device

Rename a Device |

If you rename a device and then execute the agent from the command line or from the GUI, the Storage Automated Diagnostic Environment displays a message that the previous device has been removed.

The Storage Automated Diagnostic Environment Topology will not, however, display the renamed device until you rediscover the device and take a new Topology snapshot.

You can avoid this problem by manually adding the world wide name (WWN) into the Storage Automated Diagnostic Environment configuration file, which is located in `/var/opt/SUNWstade/DATA/rasagent.conf`.

Note:

Unless you remove the SUNWstade directory and perform a new `ras_install`, the configuration file remains on the system between upgrades.

See Also:

- 'Maintain a Device
- 'Update a Device
- 'Delete a Device

[ admin.gen_maint.maint_device:maintaindev,deletedevice,renamedevice,updatedevice ]

Manually Update a Device

Manually Update a Device |

Changing the name of the device changes only the reference to that device within the Storage Automated Diagnostic Environment. It does not affect the access or reference to that device within the operating system.

If you change the configuration of a device, you must delete that unwanted device. The Storage Automated Diagnostic Environment displays a message stating that the previous device has been removed. Topology will not, however, display the deleted device until you manually add and discover the device.

After you have added a device or updated a device, click Re-Discover to refresh the system.

See Also:

- 'Maintain a Device
- 'Delete a Device
- 'Rename a Device
- 'Review Configurations

[ admin.gen_maint.maint_device:maintaindev,deletedevice,renamedevice,updatedevice ]

Administration > General Maintenance > Local Notification (Email/Scripts) | [ Top ]
Storage Automated Diagnostic Environment
Local Notification (Email/Scripts) | [ Help ]
Use [Add Notification] to add new email addresses. [Clear Email Maximums] reset the counters that are used to avoid sending too many emails about the same problem. Notification Add/Update Form: For Sun Solution, the Management-level can be selected. Select 'Components' to get device events (like t3,switch etc..). Select 'System' to get Solution-level events (like 3900/6900 etc..). Select Priority, Event Category and Event Type to filter events. 'Skip components of aggregated events' will decrease the number of events sent by only sending aggregated events. Aggregated events are generated by the 'Fault Signature Analysis' module.
Existing Local Notifications
Notification Type | Email/Script (Click to Update) | Event Categories | Event Type | Priority | Admin Groups
Script | /bin/cat -x | All | All Events | All | All
Script | /tmp/xx -d | All | All Events | All | All

[ GUI::Notifs::list ]

Email Notification

Email Notification |

You can use the Email Notification window to customize the generation of emails to yourself or to other administrators at their companies. For example, if you are interested in receiving only high-priority alerts coming from Sun StorEdge T3, T3+, or 6120 arrays, you can create a specialized notification for this instance only.

Alerts are sent only to valid email addresses that you have entered through the Email Notification function. Local notification does not send mail to the provider.

You can customize the following local notification information:

- Notification type
- Email address
- Category
- Event Type
- Priority

Note:

The local email/pager notifications feature is optional and does not affect the main transmission functions of the Storage Automated Diagnostic Environment. The master instance of the Storage Automated Diagnostic Environment is the only instance generating emails based on local notifications.

### Updating or Deleting Email Addresses

To update or delete an existing email address, click an existing email link from the Email notification window.

### Clear Maximum Emails

For events that produce frequent error messages, you can specify the number of times you are notified. If the maximum number is set to a value other than no maximum (the default), you can receive an email 5, 10, 20, or 50 times within an eight-hour period. The last email will indicate that this is the final notification you will receive within the eight-hour time period.

To clear a previously-set value, click Clear Email Maximums from the Email Notification window.

### Turn-Off Event Advisor

This option will exclude the Event Advisor information form the email. The probable cause and recommended action will not be printed as part of the email.

See Also:

- 'Add a New Entry
- 'Message Subset
- 'Providers

[ admin.gen_maint.email:notifications ]

Administration > General Maintenance > Add Local Notification Entry | [ Top ]
Storage Automated Diagnostic Environment Storage Automated Diagnostic Environment
Local Notification (Email/Scripts) : Add Email | [ Help ]
Use [Add Notification] to add new email addresses. [Clear Email Maximums] reset the counters that are used to avoid sending too many emails about the same problem. Notification Add/Update Form: For Sun Solution, the Management-level can be selected. Select 'Components' to get device events (like t3,switch etc..). Select 'System' to get Solution-level events (like 3900/6900 etc..). Select Priority, Event Category and Event Type to filter events. 'Skip components of aggregated events' will decrease the number of events sent by only sending aggregated events. Aggregated events are generated by the 'Fault Signature Analysis' module.
Enter Local Notification Information
Notification Type: | :Email :Pager :Script
Email Address: |
Run script: | [ Help ]
Management Level: |
Priority: |
Event Categories: |
Event Type: |
Admin Groups: |
Apply Event Filters: |
Skip components of aggregated events: |
Turn Off Event Advisor: |

[ GUI::Notifs::list ]

Add New Notification Entry

Local Notification: Add New Entry |

Create a notification record for each system administrator who wants to be notified of the Storage Automated Diagnostic Environment findings.

Restrict the findings by Priority, Event Category, and Event Type. Multiple events can be selected and sent to an email or pager address. This flexibility enables a customized alert notification scheme.

In addition to sending the reliability, availability, and serviceability (RAS) information collected by the Storage Automated Diagnostic Environment, you can send a customizable subset of the event-driven messages from the host (configured as master) directly to local system administrators at the customer's site by email.

Note: Email might not be sent if the system is not properly configured to send mail to the recipient. This is primarily evident in Storage Service Processor environments, where the Storage Service Processors are on a subnet, and there is no gateway to the intended recipient.

See Also:

- 'Notifications
- 'Message Subset

[ admin.gen_maint.add_email:addnewentry ]

Administration > General Maintenance > Remote Notification Providers | [ Top ]
Storage Automated Diagnostic Environment
Remote Notification Providers | [ Help ]
NetConnect (Off)
|  | DataHost (Off) |  |  | Email (On) |  |  | SAE (Off) |  |  | SRS (Off) |  |  | SSRR (Off) |  |  | SunMC (Off) |  |  | Trap (Off) |
The Net Connect Provider is the transport mechanism for RAS information collected by the Storage Automated Diagnostic Environment Agent. The Active checkbox indicates the current status of the Provider.
NetConnect Provider Information
Active : | Inactive
Max Size (Kbytes): |

[ GUI::Providers::display ]

Notification Providers

Notification Providers |

Storage Automated Diagnostic Environment providers encode data and interface with transport mechanisms, which transmit information to the NSCC about configured storage devices. A provider's main function is to relay events generated by health monitors.

The Storage Automated Diagnostic Environment supports seven providers: Email, SAE, Sun Remote Services (SRS), NetConnect, Simple Network Management Protocol (SNMP), Sun StorEdge Remote Response (SSRR), and SunMC.

See Also:

- 'Email Provider
- 'SAE Provider
- 'SRS Provider
- 'SRS Net Connect Provider
- 'SNMP Provider
- 'SSRR Provider
- 'SunMC Provider

[ admin.gen_maint.providers:providers,srs,sae,netconnect,ssrr,sunmc,email,snmp ]

SRS Provider

SRS Provider |

The Sun Remote Services (SRS) Provider supports the Storage Automated Diagnostic Environment in monitoring Sun storage devices. The Storage Automated Diagnostic Environment pulls the storage device events and channels them through a sender. The sender transmits the event data, written in XML, to the SRS station.

To set up the SRS Provider, complete the required fields:

- Enable the Active checkbox.
- Type the IP address of the SRS console.
- Type an optional second IP address. A second IP address is allowed if events need to be sent to a second notification provider, which must also accept the SRS XML format.

See Also:

- 'Email Provider
- 'SRS Net Connect Provider
- 'SNMP Provider
- 'SSRR Provider
- 'SAE Provider
- 'SunMC Provider

[ admin.gen_maint.providers:providers,srs,sae,netconnect,ssrr,sunmc,email,snmp ]

SAE Provider

SAE Provider |

The SAE Provider supports the Storage Automated Diagnostic Environment in sending events to the Sun StorEdge Diagnostic Expert.

To set up the SAE Provider, complete the required fields:

- Enable the Active checkbox.
- Type the IP address of the SSDE management console.

See Also:

- 'Email Provider
- 'SRS Net Connect Provider
- 'SNMP Provider
- 'SRS Provider
- 'SSRR Provider

[ admin.gen_maint.providers:providers,srs,sae,netconnect,ssrr,sunmc,email,snmp ]

NetConnect Provider

Net Connect Provider |

The NetConnect Provider is a part of the SRS family of products. NetConnect uses internet-based technology which avoids the need for additional dedicated network connections at the customer site. All available instrumentation, events, and topology information is sent to the Network Storage Command Center (NSCC).

Although the information extracted is used to improve products and service, the information is not monitored by Sun Service personnel. Currently, the storage information is not available by way of the NetConnect portal

To set up the NetConnect Provider, complete the required fields:

- Enable the Active checkbox.
- Type the maximum size, in Kbytes, of RAS information that the Storage Automated Diagnostic Environment agent will collect and transport.

See Also:

- 'Email Provider
- 'SNMP Provider
- 'SRS Provider
- 'SSRR Provider
- 'SAE Provider
- 'SunMC Provider

[ admin.gen_maint.providers:providers,srs,sae,netconnect,ssrr,sunmc,email,snmp ]

SSRR Provider

SSRR Provider |

The Sun StorEdge Remote Response (SSRR) Provider uses modem technology with UNIX-to-UNIX Communication Protocol (UUCP). SSRR software is required on the customer data host. The SSRR Provider is intended for customers who have purchased a remote support service offering and have supplied phone lines to enable the modem phone home capability. The Storage Automated Diagnostic Environment, which records events, resides on the Storage Service Processor.

After the Storage Automated Diagnostic Environment identifies the event:

1. The Storage Automated Diagnostic Environment logs the event and alerts Sun engineers by email or pager, if the data falls outside of pre-defined tolerances.

2. The Sun engineer, located behind a firewall, accesses the SSRR server and runs a script.
   The script initiates a call to the customer's modem and supplies logins and passwords to the client Network Terminal Concentrator (NTC) and the Storage Service Processor.

3. The script negotiates a secure point-to-point protocol (PPP) connection between the customer's Storage Service Processor and the SSRR Server and automatically logs the Sun engineer on to the customer's Storage Service Processor.

4. The Sun engineer can then access SAN components to remotely diagnose and perform a number of maintenance routines.

Note: If the Storage Automated Diagnostic Environment is run either manually or from the `cron`, and the SSRR Provider is selected but the SSRR software is not installed or is not configured properly, the following error message appears:

`***ERR: Cannot find Machine name in Permissions file.`

To set up the SSRR Provider, complete the required fields:

- Enable the Active checkbox.
- Select or deselect Use Proxy. The Proxy can be used when the modem is not set up.

See Also:

- 'Email Provider
- 'SRS Net Connect Provider
- 'SNMP Provider
- 'SRS Provider
- 'SAE Provider
- 'SunMC Provider

[ admin.gen_maint.providers:providers,srs,sae,netconnect,ssrr,sunmc,email,snmp ]

SunMC Provider

SunMC Provider |

The SunMC Provider enables the Storage Automated Diagnostic Environment to send actionable events and monitoring topologies to the SunMC Console, which displays the alarms and alert text. SunMC information is similar and compatible with Sun Remote Services (SRS). SunMC can send information to SRS, in which case the SRS Provider need not be activated in the Storage Automated Diagnostic Environment.

To set up the SunMC Provider, complete the required fields:

- Enable the Active checkbox.
- Type the SunMC console IP address.
- Specify the port number. The default is 162.
- Specify the number of hours for heartbeat frequency.

See Also:

- 'Email Provider
- 'SRS Net Connect Provider
- 'SNMP Provider
- 'SRS Provider
- 'SSRR Provider
- 'SAE Provider

[ admin.gen_maint.providers:providers,srs,sae,netconnect,ssrr,sunmc,email,snmp ]

Email Provider

Email Provider |

The Email Provider enables specific events to be emailed to local administrators. Events can also be summarized and sent to a pager's email address. This is an Intranet mechanism for transporting reliability, availability, and serviceability (RAS) information collected by the Storage Automated Diagnostic Environment agent. Although the information extracted is used to improve products and service, the information is not monitored by Sun Service personnel.

To set up the Email Provider, complete the required fields:

- Enable the Active checkbox.
- Type the email address to where the messages will be sent.

See Also:

- 'NetConnect Provider
- 'SNMP Provider
- 'SRS Provider
- 'SSRR Provider
- 'SAE Provider
- 'SunMC Provider

[ admin.gen_maint.providers:providers,srs,sae,netconnect,ssrr,sunmc,email,snmp ]

SNMP Provider

SNMP Provider |

The SNMP Traps Provider enables the Storage Automated Diagnostic Environment to send traps, for all actionable events that occur during monitoring, to external management systems.

When an alert occurs, it is sent to the SNMP transport as an SNMP trap. An SNMP trap listener can use the `StorAgent.mib SNMP MIB` file, which is included in the SUNWstade package to decode these alerts.

The alerts contain the following information:

- Storage Automated Diagnostic Environment Agent location
- Storage Automated Diagnostic Environment device to which the alert pertains
- Alert level
- Message content

To set up the SNMP Provider, complete the required fields:

- Enable the Active checkbox.
- Type the IP name and address that identifies the host to the network. You can provide up to five IP addresses.
- Specify the port number. The default is 162.
- Specify the minimum alert level: Warnings, Error, or Down.

See Also:

- 'Email Provider
- 'Net Connect Provider
- 'SRS Provider
- 'SSRR Provider
- 'SAE Provider
- 'SunMC Provider

[ admin.gen_maint.providers:providers,srs,sae,netconnect,ssrr,sunmc,email,snmp ]

Administration > General Maintenance > Start/Stop Agents | [ Top ]
Storage Automated Diagnostic Environment
Calling [IP_NO]... Calling [IP_NO]...
Start/Stop Agents | [ Help ]
Used to selectively activate or deactivate the monitoring agents
Hosts Current Monitoring State
HostName | Type | Host Id | Host IP | Monitoring | Start | Stop
ccadieux.site | Master | 80a3738d | [IP_NO] | On |  |
jeannot.site | Slave | 8089d4eb | [IP_NO] | Off |  |
crashme41.site | Slave | 80b43b26 | [IP_NO] | Off |  |

[ GUI::Start::Agents ]

Start Agents

Start Agents |

You can control agent activity to temporarily stop the Storage Automated Diagnostic Environment from running on a selected host. You can also avoid creating email notifications on false errors when a device is being tested and faults are injected intentionally.

Note:

By default, the master Monitoring function does not automatically default to On. You must manually enable Monitoring to On.

- Using the Start Agents function to avoid creating email notifications on false errors works only if you are monitoring a single device type, and all of the devices are monitored simultaneously, as in an upgrade.

See Also:

- 'Start or Stop Devices
- 'Review Configurations
- 'Configuration Options

[ admin.gen_maint.start_agent:ssagents ]

Administration > General Maintenance > Start/Stop Devices | [ Top ]
Start/Stop Devices | [ Help ]
Click on the hostname to expand this host and see it's devices. This page indicates if the device is turned on and if the Host has this device category active under 'Maintain Hosts'. When the status is 'On Off Off', it means that the device is active but it's category has never been selected and the agent is not running.
Start/Stop Device Monitoring
Primary Host | Name | Type | Address/WWN | Monitor Dev/Cat/Agent | Start | Stop
--- | --- | --- | --- | --- | --- | ---
+ diag230.site

[ GUI::Start::Devices ]

Start or Stop Devices

Start or Stop Device Monitoring |

The Start Device window enables you to deactivate monitoring on a device-by-device basis.

1. To start or stop devices, check the appropriate checkbox.

- When Monitoring is 'on,' the 'Stop' checkbox is available.
- When Monitoring is 'off,' the 'Start' checkbox is available.

2. The Storage Automated Diagnostic Environment must update the configuration files on all the slave hosts configured with this master. To accomplish this, use the 'Push Slave Configs option on the Maintenance menu.

3. If the device is being tested, or if faults are being injected into the device intentionally, you can temporarily stop the local notifications for a specific device using the Start/Stop Device Monitoring window.

Note:

Monitoring continues when the device is deactivated (turned off). However, email notifications will not occur for any faults that are detected while the device monitoring is in this state. Consequently, any errors that may have been detected will be logged and sent by means of the NetConnect Provider, but not by means of email notification.

See Also:

- 'Maintain a Device
- 'Update a Device
- 'Delete a Device
- 'Rename a Device
- 'Review Configurations

[ admin.gen_maint.start_device:ssdevices ]

Administration > General Maintenance > Admin Groups | [ Top ]
Storage Automated Diagnostic Environment
Admin Groups | [ Help ]
Administration Groups are used to group devices. These groups can be used to insure that administrators receive information about their devices only. Each device or host can be assigned a single admin-group. Admin Groups can be used when creating Local Emails.
Select devices to group
| Search: Sort:
Name
| Group
| Select
-crashme41 | gn |
-diag230 | gn |
3310-3310-000034 | gn |
6120-diag210 | gs |
a5k-DSQA2 | gs |
d2-013203 | gs |
mcdata-diag183 | gs |
switch-diag187 | gs |
switch-diag192 |  |
switch2-diag111 |  |
switch2-diag140 |  |
switch2-diag141 |  |
switch2-diag99 |  |
t3-diag103 |  |
t3-diag208 |  |
t3-diag211 |  |
tape-tape-475b |  |
-jeannot |  |

Group selected devices into:

[ Define more Admin-Groups ]

[ GUI::AdminGroup::list ]

Admin Groups |

Administration Groups are used to group devices. These groups usually represent areas of responsibilities that are divided between administrators. They can be used to insure that administrators receive information about their devices only.
Admin Group setup:

- Create admin groups in Admin -> System Utilities -> Define Admin-Groups.
- Assign these groups to each devices and host monitored by the agent. Devices and hosts can belong to only one admin-group.
- When creating Local Email in Admin -> General Maintenance -> Local Email, select one or many of these admin groups. This will insure that messages sent to these email addresses are only about devices included in the selectedadmin groups.

[ admin.gen_maint.adming:admin_groups ]

Administration > General Maintenance > Test email | [ Top ]
Storage Automated Diagnostic Environment
Test email | [ Help ]
Enter an Email Address and an optional Message to send a test email.
Email Address: |
Message: |

[ GUI::Email::test ]

Test Email

Test Email |

Use the Test Email window to send test emails and a message, and to verify that the mailing capability of the Storage Automated Diagnostic Environment is installed and working properly.

Notes:

- If you leave the Message text field blank, the test email contains a default message with the words Test Message in the subject line.
- If you place a carriage return in the Message text field, you cannot enter text. To restart, click in the Message text field and enter some text.

See Also:

- 'Notifications
- 'Add a New Entry
- 'Review Configurations

[ admin.gen_maint.test_email:testemail ]

Administration > General Maintenance > Review Config | [ Top ]
Storage Automated Diagnostic Environment
Review Config | [ Help ]
This program will verify the configuration of the master and each of the slaves. This may take a few minutes.

[ GUI::Review::run ]

Review Configurations

Review Configuration |

Use the Review Configurations window to verify system configuration settings.

Note:

Although some settings have a default, you can change the defaults on selected configuration options using the 'Configuration Options window.

Follow the displayed recommendations to correct settings that you might have missed or for those that you need to double-check.

See Also:

- 'Email Configuration
- 'Recover Configuration

[ admin.gen_maint.review:reviewconfig ]

Administration > General Maintenance > Config Options | [ Top ]
Storage Automated Diagnostic Environment
Config Options : Window Options | [ Help ]
Enter Configuration Options
Number of old (historical) topologies to save for comparison : |
Test Manager Refresh rate: | ( minimum is 5 secs. )
Max LogFile Size: | (Meg)
GUI Bandwidth: |
Create Hubs when appropriate: |
Is this a production Site?: |
|  | Is this site used for production or just for testing and development?
Session Time-Out: |
Enter email options
Sendmail from this Host/IP: | (Optional)
Email from: | (Optional)
Maximum number of emails about the same component in the same 8 hours period: | Emails per time period
Path to Email Program: |
Window Options : Config Options
Update Window
Select Big screen if your monitor is 1280x1024 and you want to display up to 3 frames across on the browser. Select Small screen for 1024x864 monitors and want only 2 frames. Select 'No Frames' if you don't want the application to use frames.
Select Browser Window: |
Color Scheme: |

[ GUI::Options::upd ]

Configuration Options

Change Configuration Options |

The Configuration Options window enables you to change the defaults on selected configuration options. Use the following information to update existing configuration options:

Note:

If the host is behind a firewall (for example, in a Storage Service Processor environment), e-mails cannot be sent unless the e-mail address is on the customer's LAN.

Configuration Options

- Number of old (historical) topologies to save for comparison.
  Type the number of topologies to save in Topology History for comparison. The default is 5.

- Test Manager Refresh Rate
  Specify the window refresh (re-load) rate, in seconds, for test output. The default is 30 seconds, and the minimum refresh rate is 5 seconds.

- Max Event File Size
  Specify, in megabytes, the maximum event file size. Used to limit data packet size to notification providers. The default is 2.

- GUI Bandwidth
  Specify the bandwidth for low and high speed local area network (LAN). The default is High Bandwidth.

- Create Hubs when appropriate
  Enable this checkbox if you want Hubs to be drawn in the Topology.

- Is this a production site?
  Specify whether this site is used for production (default when checked) or if it is used for testing and development.

Email Options

- Sendmail from this Host/IP
  Enter the Hostname from where you want email to be sent.

- Email From
  Enter the name that you would like to see in the From: in emails

- Maximum number of emails about the same component in the same 8-hour period.
  Specify the maximum number of emails that will be sent within an eight-hour period about a specific event. The default is 6. Options include 2, 4, 6, or 8.

- Path to Email Program
  Use to change the local email program.

Window Options

- Select Browser Window
  Use to configure the default GUI screen size.

  - Big Screen-displays three windows: the left frame window, the top window (with tracking links), and the main topic window.
  - Small Screen-displays three smaller windows, as with the Big Screen selection.
  - No Frames-displays the top window (with tracking links) and the main topic window only.
  - No Frames + Accessible-displays the top window (with tracking links) and the main topic window, as with No Frames, but enables the user to use keystroke combinations to perform tasks instead of using the mouse.

- Color Scheme
  Use to configure the default GUI screen color scheme.

[ admin.gen_maint.options:configoptions,setbrowser ]

Setting your Browser Window

Maintain Site Information |

You can configure your browser window's size and specify whether to show or hide the left frame menu. Using the 'Config Options functionality, you can select one of the following window options.

- Big Screen

  Displays three frames: the left frame table of contents, the top frame with tracking links, and the main topic window.

- Small Screen

  Displays three smaller frames: the left frame table of contents, the top frame with tracking links, and the main topic window.

- No Frames

  Displays the top frame with tracking links and the main topic window only.

- No Frames + Accessible

  Displays the top frame with tracking links and the main topic window, as with No Frames, but enables the user to use keystroke combinations to perform tasks instead of using the mouse.

See Also:

- 'Maintain Hosts
- 'Site Information

[ admin.gen_maint.options:configoptions,setbrowser ]

Administration > General Maintenance > Optimization/FSA | [ Top ]
Storage Automated Diagnostic Environment
Optimization/FSA | [ Help ]
Fault Signature Analysis
| This module creates new aggregated events by grouping together events that share common 'suspect frus'. With FSA on, a one-probing-cycle delay is introduced to make sure that all slaves have reported their events to the master agent. When turned on, this module will delay the generating of events by one 'run' of the agent: This is done to ensure that all events have been generated before starting the correlation.
| Turn on Fault Signature Analysis?: |
Parallel monitoring
| Allow to probe more than 1 device at the same time. This can be used to accelerate the monitoring frequency and improve event timeliness.
| Number of switches to do at the same time: |
| Number of Sun T3/6120 to do at the same time: |
Sun T3/6120 Monitoring Optimization
| This options allows to minimize the probing of t3/6120 that appear to be healthy by relying on the message.t3 logfile and on 'ping'. Arrays will still be probed at least every 6 hours even when they appear healthy. If 'ping' fails or if there are new entries in the messages.t3 logfile, normal probing will immediately resume. This function should only be used when monitoring a large amount of arrays from the same agent (> 50). ***WARNING*** This function relies heavily of the messages.t3 logfile. Verify that all array's remote-logging is configured properly before turning this option on.
| Turn on T3/6120 Optimization: |

[ GUI::Optimization::upd ]

Fault Signature Analysis

Fault Signature Analysis |

Fault Signature Analysis (FSA) aggregates alerts that share common suspect FRUs. After a set of events is generated, but before these events are sent as email or to the NetConnect provider, the FSA module attempts to summarize into fewer and more specific and actionable events. The aggregation of events often points to a root cause of the problem, whereas events are merely symptoms of the problem.

See Also:

- 'Event Report
- 'Service Advisor

[ admin.gen_maint.optimization:fsa ]

Administration > General Maintenance > Event Filters | [ Top ]
Storage Automated Diagnostic Environment
Event Filters | [ Help ]
Enter an optional time-period, a device type, and one of 'Event-Code' or 'Description-Pattern' to create a filter. Then adjust the severity for your needs. This only applies to local email and local scripts if filtering is activated on the local email itself.
Event Filter List
# | Dev-Type | Event-Code | Day filter | Description Pattern | Severity | Del.
No Filter available!

[ GUI::Filters::list ]

Event Filters |

Event filters are used to customize the severity of events sent to Local-Email notification. This allows administrators to control more precisely the severity of events they receive. Event filtering aplies both to Email and scripts.
These severity changes do not affect the Remote Notification providers like SRS or NetConnect. Filtering can be done against a single event or a category of events using the following fields:

- Device Type: Select a device category.
- Event-Code: Enter a specific event code, like 5.20.16.
- Day filter: Filter only when events are generated during these time periods.
- Description Pattern: Use part of the event description to create a filter.
- Severity: Select a new severity for the event.

If a specific event-code is entered, then the filter will apply only to that event. If no event-code is entered and a combination of device-type and description pattern is entered, the filter will possible apply to a wide range of events.
A valid regular expression can be entered in the description pattern like:
u\dd\d+ : meaning u1d1 or u2d12
port.\d+ is 'offline # will match any offline port

[ admin.gen_maint.filters:filters ]

Administration > Topology Maintenance > Topology Snapshot | [ Top ]
Storage Automated Diagnostic Environment
Storage Automated Diagnostic Environment
Topology Snapshot | [ Help ]
This function is used to retrieve topologies from different hosts (master and slaves) and merge them into a Master Topology. - Select the host to retrieve and create a topology by placing a check in the "Select" column check box. - Click [Create Selected Topologies] to start discovery on the selected hosts. - Once all topologies are retrieved, the Status should say 'Done'. - The 'Last Snapshot' column contains the date of the last time a topology was extracted from this host. - The 'Last Master' column contains the date the last Master Topology was sent back to that host. - If a timeout-error occurs, you may need to increase the timeouts in System Timeouts Note: This function requires Solaris 8 4/01 or above to work.
Select Topology
Select | Topology | Last Snapshot | Last Master | Status | Error Details | Delete/Clear
--- | --- | --- | --- | --- | --- | ---
| diag230.site (Local) | 2003-04-02 09:57:40 | 2003-04-08 15:24:36 |  | Review |
| jeannot.site |  |  |  | Review |
| crashme41.site |  |  |  | Review |

[ GUI::SAN::snapshot ]

Topology Maintenance

Topology Maintenance |

The Storage Automated Diagnostic Environment's graphical storage area network (SAN) interface displays all fabric components and the state of those components. Fabric components include HBAs, switch ports, storage controllers, and disks, along with more specialized components such as fans, batteries, power, and volumes.

Note: Only HBAs connected to storage devices are displayed in Topology.

SAN agents collect counter information based on error messages and telemetry information. This information is then used in the Topology drawing to indicate link failures.

See Also:

- 'Topology Snapshot
- 'SnapShot History

[ admin.topo.snapshot:topomaint,toposnapshot ]

Topology Snapshot

Topology Snapshot |

Use this function to create and update the topology view from the host or to review error details.

Notes:

- This function requires Solaris 8 4/01 or higher.
  If using Solaris 8, the host must have the SUNWsan package installed, along with the latest `luxadm` patch.

- To view topologies in the Monitoring and Diagnostic windows, you must first create a snapshot.

- Before you create a Topology snapshot, make sure there are no failed over paths. If there are failed over paths, the Topology view will not properly display them.

1. From the Topology Maintenance window, click the Topology Snapshot link.
   The Topology Snapshot window is displayed.

2. Select the check box that corresponds to the topology and click Create Selected Topologies or Create Topologies.
   While the system creates the selected topology, the status is in one of two states:
   - Running--Discovery is running on the selected host and the system creates and retrieves the selected topology.
   - Done--The topology has been created and is ready for you to retrieve.
     - Click the Review link to review the error details, if applicable.
     - Click the Clear link in the Delete column to clear a selected topology.

3. Click Review in the Error Details column to launch a pop-up window that displays topology errors.
4. Verify the Topology view.

Note:

If a timeout occurs during the process, you may need to increase the timeout specifications. For information, see ' To Change System Time-Out Settings.

See Also:

- 'Topology Maintenance
- 'SnapShot History

[ admin.topo.snapshot:topomaint,toposnapshot ]

Administration > Topology Maintenance > Topo history | [ Top ]
Storage Automated Diagnostic Environment
Topo history | [ Help ]
Click a date link to see the topology diagram . Check 2 topologies and press [Compare Selected] to see a report of the changes between the topologies. [Delete Selected] will delete all checked topologies.
Available topologies
Host | Current | Date1 | Date2 | Date3
--- | --- | --- | --- | ---
diag230.site |  | 2003-04-01_07:42:56 | 2003-04-01_07:55:33 | 2003-04-01_14:11:36
|  | 2003-04-01_14:24:07

[ GUI::SAN::snapHistory ]

Snapshot History

Snapshot History |

With this function, you can compare and delete current Topology snapshots, or you can view, compare or delete previously stored Topology snapshots.

1. From the Topology Maintenance window, select Topology History.
2. To see a summary of the changes between two topologies, select two hosts and enable the corresponding checkbox, then click Compare Selected. The host must have at least two topologies to use the Compare Selected feature.
3. To delete a topology, select one or more topologies and enable the corresponding checkbox, then click Delete Selected.
4. To view a previously stored Topology snapshot, double click the date link from the Date1, Date2, or Date3 columns. The oldest snapshot is displayed first.
5. To compare or delete previously stored Topology snapshots, click the corresponding checkbox on the Date1, Date2, or Date3 columns.
   - To compare two or more previously stored snapshots, click Compare Selected.
   - To delete one or more previously stored snapshots, click Delete Selected.

See Also:

- 'Topology Maintenance
- 'Topology Snapshot

[ admin.topo.history:snapshothistory ]

Administration > System Utilities > System TimeOuts | [ Top ]
Storage Automated Diagnostic Environment
System TimeOuts | [ Help ]
Allows to adjust the timeouts used by the monitoring agents
System Time-outs (Seconds)
Ping : | Second(s)
Email : | Second(s)
Sun T3 tokens (Http) : | Second(s)
SNMP access : | Second(s)
Luxadm (Sun A5000) : | Second(s)
RM6 (Sun A3500FC) : | Second(s)
Discman (Discovery) : | Second(s)
Slicd (VE) : | Second(s)

[ GUI::Timeouts::upd ]

System Timeout Settings

System TimeOut Settings |

System timeouts are the values the Storage Automated Diagnostic Environment Agent uses to ensure it does not spend too much time waiting on a response for commands to return.

Categories and default settings are:

- Ping - The timeout used to perform a ping. The default is 10 seconds.

- Email - The timeout used when sending emails. The default is 30 seconds.

- Sun T3 Tokens (HTTP) - The timeout used when extracting token information from a Sun StorEdge T3, T3+, or 6120 array. The default is 60 seconds.

- SNMP access - The timeout used to query switches that support simple network management protocol (SNMP). The default is 20 seconds.

For more information, refer to the Sun StorEdge Series Reference and Service Guide.

[ admin.system.timeout:systemtimeouts ]

Administration > System Utilities > Erase Cache | [ Top ]
Erase Cache | [ Help ]
Use this section to erase the last report generated by instrumentation for a particular device and/or function. Doing this forces rediscovery of the device's instrumentation upon the next execution, since it will have no old report to compare to. The device will still be monitored. [Delete All Reports] deletes the last report generated by instrumentation for ALL listed Devices. [Delete Complete Database] remove most files in the DATA directory. Running rasagent after this will be like the first run after pkgadd. This function will not erase the config file. NOTE: There is NO WARNING and NO VERIFICATION for these actions.
Select Host: |
Devices:
Type | Device ID (Click to erase) | Name | Delete
3310 | 206000c0ff000034 | / 3310-000034 |
3310message | 206000c0ff000034 | / 3310-000034 |
6120 | 0x301.5016338.400386 | / diag210 |
a5k | 5080020000081838 | / DSQA2 |
backup | diag230.site | / diag230.site |
d2 | 013203 | / 013203 |
mcdata | 1000080088a0cade | / diag183 |
switch2 | 100000c0dd00bfa4 | / diag141 |
switch2 | 100000c0dd00c680 | / diag140 |
switch2 | 100000c0dd00cbb4 | / diag99 |
switch2 | 100000c0dd01a18d | / diag111 |
switch | 100000c0dd005732 | / diag192 |
switch | 100000c0dd006fad | / diag187 |
t3 | sci-sj.370-3990-01-e-d0.002487 | / diag208 |
t3 | slr-mi.370-3990-01-e-e1.002776 | / diag211 |
t3 | slr-mi.370-3990-01-e-f0.027877 | / diag103 |
t3message | 80a3738d | / diag230.site |
tape | 500104f0004b475b | / tape-475b |
topo | topo | / topo |

[ GUI::Cache::erase ]

Erase Cache

Erase Device Cache |

When you select an existing device, the last report in the cache for that device is erased. This forces the Storage Automated Diagnostic Environment Agent to regenerate events.

The Erase Device Cache function erases the cache of all the selected devices and the list is removed. Although the device's cache is erased, however, the device will still be monitored.

Caution: There are no safeguard questions for this function. Once you have selected a device, the instrumentation report for that device is immediately erased.

See Also:

- 'System Timeouts
- 'Run RAS
- 'Email Configuration
- 'Recover Configuration
- 'Run Scripts
- 'Change Password
- 'User Roles
- 'Clear Login
- 'Application Launcher

[ admin.system.erase_cache:erasecache ]

Administration > System Utilities > Run Agent | [ Top ]
Storage Automated Diagnostic Environment
Run Agent | [ Help ]
This option will run the agent program immediately unless it is already running. The agent is normally executed from the cron facility but this option allows you to run it manually. Select 'Audit all devices' to force the agent to re-discover the devices (AuditEvents). Select 'Ignore Email Maximums' to generate all events even if they were generated recently.
Select Host: |
Audit all devices: |
Ignore Email Maximums (send all events): |

[ GUI::RUNAgent::run ]

Run RAS

Manually Run the Storage Automated Diagnostic Environment Agent |

Although the Storage Automated Diagnostic Environment Agent is normally executed from the `cron` facility, the Run Agent option enables you to run the agent manually.

To run the agent manually:

1. Select a Host from the Select Host pull-down menu.
   Note:
   Select and run the slaves first. The master should be run manually last.

2. In the 'Config Options section, you can specify the maximum number of emails that will be sent within an 8-hour period about a specific event. The default is no maximum.
   If you check Ignore Email Maximums, the system overrides current specifications and sends all events. You can also clear the specified number of emails using the 'Notifications option.

3. On some devices, such as the Sun StorEdge A5000 device, the Storage Automated Diagnostic Environment automatically extracts revision information once a week.
   If you check Audit All Devices, you manually force the Storage Automated Diagnostic Environment to run an extensive probe of all devices, rather than having to wait until the next scheduled run.

4. After you have selected or deselected the options, click RUN.
A summary report displays the status of all the components that are running.

See Also:

- 'Config Options
- 'Notifications

[ admin.system.run_agent:runras ]

Administration > System Utilities > Email Config | [ Top ]
Email Config | [ Help ]
This function will email a detailed report of the configuration including a list of all devices being monitored, along with the last instrumentation report available on each host.
Email Configuration
Email Address: |
Comments: |

[ GUI::DumpConfig::dumpConfig ]

Email Configuration

Email Configuration |

Using the Email Configuration functionality, you can forward a detailed configuration report to specified email recipients. The configuration report includes a list of all monitored devices and the most recent instrumentation report available for each device. Topology information can also be forwarded using email.

The Email Configuration function enables Sun personnel to view customer information. Note, however, that in order to view the topology in an emailed configuration report, the browser must have access to Sun's Internal Wide Area Network (SWAN).

Note:

Email might not be sent if the system is not properly configured. This is primarily evident in Storage Service Processor environments where the Storage Service Processors are on a subnet and there is no gateway to the intended recipient. Refer to the Sun StorEdge Series Installation and Service Manual for more information.

See Also:

- 'System Timeouts
- 'Erase Cache
- 'Run RAS
- 'Recover Configuration
- 'Run Scripts
- 'Change Password
- 'User Roles
- 'Clear Login
- 'Application Launcher

[ admin.system.email_config:emailconfig ]

Administration > System Utilities > Run scripts | [ Top ]
Storage Automated Diagnostic Environment
Run scripts | [ Help ]
t3
Change array passwords | This command will change all array passwords for t3/6120
Run Commands on T3/6120 | Run command using telnet (fru list, fru stat etc..)
Retrieve tokens from a T3/6120 | Enter IP Address and a 0 or 1 for the first or second enclosure (Partner Group)
util
Create SE-Series snapshot | Create SE-Series snapshot
Run unix ps | Process Status

[ GUI::Rsh::list ]

Run Scripts

Run Scripts |

The Run Scripts window enables you to run several command line programs from the GUI.

A brief description of the scripts that are currently available for the Sun StorEdge T3, T3+, and 6120 array follows:

- Change T3, T3+, 6120 password
  This command changes the password of all Sun StorEdge 6120 arrays that are components of a Sun StorEdge 6320 or 6320 SL series system.

- Run commands on T3, T3+, or 6120
  This command enables you to run Sun StorEdge 6120 array commands, such as `fru list` and using Telnet. The argument field can be used to specify additional parameters for the selected command (ex. `fru stat` can take `u1l1` as an argument).

- Retrieve tokens from a T3, T3+, or 6120 array
  This script enables you to enter the IP Address and a 0 or 1 for the first or second enclosure.

[ admin.system.run_script:run_scripts ]

Administration > System Utilities > Root password | [ Top ]
Storage Automated Diagnostic Environment
Root password | [ Help ]
Used to changed the 'root' password of this software
Password Maintenance
User: | ras
Enter OLD password : |
Enter NEW password (min 4 chars.) : |

[ GUI::Password::run ]

Password Maintenance

Password Maintenance |

Use the Password Maintenance window to change the security password for the Storage Automated Diagnostic Environment GUI.

1. Click Root password in the System Utilities window.

Note:
You must know the current password. The default login and password after inititial installation are `ras` / `agent` (all lowercase).

2. Enter the OLD password.

3. Enter a new password, with a minimum of four characters.

4. Click Update.

The security password is changed.

[ admin.system.password:changepassword ]

Administration > System Utilities > Login/Roles | [ Top ]
Storage Automated Diagnostic Environment
Login/Roles | [ Help ]
Use this screen to add a new user to your system,check at least one privilege for each user. User names must start with one letter. Use 'Del.' and the [Add/Update] button to delete users.
Login / Roles maintenance
| Service
# | Del. | Login | NIS passwd | Password | Language | Window | Admin Group | User | Admin | Script | Diag | Expert
1 |  | chris |  |  |  |  |  |  |  |  |  |
2 |  | storade |  |  |  |  |  |  |  |  |  |
Add: |  |  |  |  |  |  |  |  |  |  |
Add: |  |  |  |  |  |  |  |  |  |  |
Add: |  |  |  |  |  |  |  |  |  |  |

[ GUI::Roles::update ]

User Roles

Update User Roles |

The Storage Automated Diagnostic Environment administrator can assign permission privileges for the categories listed below. In addition to assigning privileges, the administrator can add a new user, maintain passwords, and update or remove existing users.

### User Selections

- Del
  Selection to delete a user. Slect the 'Add/Update' button to apply change

- Login
  Deisred Username. Note: Use NIS username if NIS login is desired

- NIS passwd
  Use NIS password based on username selected. With this option selected, the authentication will use the locall /etc/passwd file or the NIS equivalent.

- Password
  Enter password if NIS was not selected

- Language
  Enter desired locale for this user. Note: Language can also be determined by the settings in your browser

- Window
  Select browser window style. The 'Big' selection will use three frames and is intended for high resolution displays. 'Small' will use two frames and is intended for lower resolution displays. 'NoFrame' will not use frames. 'Accessible' will not use frames or Java applets

- Admin Group
  Select the administrator group if groups were definded in 'System Utilities->Define Admin-Groups'

- Service
  Select the service types (Privileges) that this user will be allowed to access. Service types are defined below

### User (Services) Privileges

- user - Cannot make changes in the maintenance functions

- admin - Required to add, delete, or update in the Maintenance sections

- test - Required to run diagnostic tests

- script - Required to run scripts.

- expert - Required to use the FC Analysis section.

[ admin.system.roles:roles ]

Administration > System Utilities > Define Admin-Groups | [ Top ]
Storage Automated Diagnostic Environment
Define Admin-Groups | [ Help ]
Define Administration Groups
Enter Administration Groups (Clear code to delete entry)
# | Group Code | Description
1 |  |
2 |  |
3 |  |
4 |  |
5 |  |
6 |  |
7 |  |
8 |  |

[ GUI::Groups::update ]

Admin Groups |

Administration Groups are used to group devices. These groups usually represent areas of responsibilities that are divided between administrators. They can be used to insure that administrators receive information about their devices only.
Admin Group setup:

- Create admin groups in Admin -> System Utilities -> Define Admin-Groups.
- Assign these groups to each devices and host monitored by the agent. Devices and hosts can belong to only one admin-group.
- When creating Local Email in Admin -> General Maintenance -> Local Email, select one or many of these admin groups. This will insure that messages sent to these email addresses are only about devices included in the selectedadmin groups.

[ admin.system.device_groups:admin_groups ]

Administration > System Utilities > Clear Login | [ Top ]

Clear Login

Clear Login |

The Clear Login screen enables you to clear a current user and log in as another user without having to exit the browser.

To clear the login screen:

1. Click Cancel to the question "Authorization Failed. Retry?"
2. To return to the Login screen, reload the browser window.

[ admin.system.clear_login:clearlogin,browser ]

Web Browser Logging |

If you have successfully installed and started the software, log in through a Web browser.

1. Open a Web browser.
2. Type the following URL in the URL text field for an HTTP server:

   http://your-hostname:port

   where your-hostname is your machine's hostname and port is its port number you configured (the default is 7654).

[ admin.system.clear_login:clearlogin,browser ]

Administration > System Utilities > App. Launcher | [ Top ]
Storage Automated Diagnostic Environment
App. Launcher | [ Help ]
Use this form to associate each device-type to an external web-based application. These applications can be used to manage each type of device. The special symbol $ip and $wwn can be used in the url. Example: http://$ip to manage a switch by calling the switch's web-server directly. The symbol is used to launch these external systems.
Enter Application name and URL
Device Type | Application Name | Application URL
Sun T3 1: |  |
2: |  |
Brocade switch 1: |  |
2: |  |
Sun Switch 1: |  |
2: |  |
Sun Switch2 1: |  |
2: |  |
Sun 3900/6900 1: |  |
2: |  |
Sun 6320 1: |  |
2: |  |
FC-Tape 1: |  |
2: |  |
Vicom VE 1: |  |
2: |  |

[ GUI::UrlLaunch::update ]

Application Launcher

Application Launcher |

The Application Launcher screen enables a single click launch of selected web-based applications available to manage particular device types.

[ admin.system.url_launch:applauncher ]

Monitor > Monitor Devices | [ Top ]
Storage Automated Diagnostic Environment
Monitor Devices | [ Help ]
Host: | Admin Group: | Search: |
Host | Type | Name | Sev | Last Report
diag230 | d2 | 013203 |  | 04-02 19:55:22
diag230 | 3310 | 3310-000034 |  | 04-02 19:55:07
diag230 | a5k | DSQA2 |  | 04-02 19:55:20
diag230 | t3 | diag103 |  | 04-02 19:59:44
diag230 | Switch2 | diag111 |  | 04-02 19:56:37
diag230 | Switch2 | diag140 |  | 04-02 19:55:57
diag230 | Switch2 | diag141 |  | 04-02 19:56:16
diag230 | McDATA | diag183 |  | 04-02 19:55:27
diag230 | Switch1 | diag187 |  | 04-02 19:55:28
diag230 | Switch1 | diag192 |  | 04-02 19:55:29
diag230 | t3b | diag208 |  | 04-02 19:59:15
diag230 | 6120 | diag210 |  | 04-07 11:01:04
diag230 | t3 | diag211 |  | 04-02 19:59:39
diag230 | host | diag230. central.sun.com |  | 04-02 19:59:58
diag230 | Switch1 | diag99 |  | 04-02 19:55:37
diag230 | tape | tape-475b |  | 04-02 19:59:48
Use the 'Search' field to search for a specific device in the device list. Name Search Syntax: Enter a few or all letters of the device name. Wildcards are not supported Example: '192' will find device 'diag-192' and device '[IP_NO]'

[ GUI::Instr::frame ]

Monitor Devices

Monitor Devices |

Use the Monitor Devices window to review all FRU-level information and to access components of a selected device.

The Monitor Devices screen contains the following information:

- Host--Displays the host name associated with the monitored devices.
- Type--Displays the device type (for example, switch, host, or array)
- Name--Displays The IP name or IP address of the device type. By clicking a name, you can access the Summary page.
- Severity--Displays the condition of the device.
  - Red (error)
  - Yellow (warning)
  - Down (component is non-functional)
  By clicking a severity icon, you can access the Health page.
- Last Report--The report date on which health, log, graph, or report summaries were generated.

See Also:

- 'Alerts, Alarms, Events Description
- 'Monitoring Device Tips
- 'Summary Report
- 'Event Log Report
- 'Device Detail Report
- 'Graph Summary Report

[ monitor.devices:monitordevice,monitordevicetips ]

Monitor Device Tips

Monitor Device Tips |

- To narrow the list of devices, enter at least a portion of the device name or IP address to display specific devices.
  For example, if you enter '192,' the search will return both 'diag-192' and device '192.xx.xx.x'.
- Click on a device from the Name column to view a list of all of the device's components.
  The 'Summary Report is displayed.

  Note: You can also access the content of the Monitor Devices Report window using the Topology view by right-clicking an icon and clicking Report.

- Click on a component's corresponding Summary, Health, Log, Report, or Graph link.

Options from the Monitor Devices Report window include:

- A Summary page about the selected device. Refer to 'Summary Report.
- A Health page showing any problem with the selected device. Refer to 'Alerts Report.
- A Log page showing a summary of all events generated against the selected device. Refer to 'Event Log Report.
- A Report page showing, in detail, all monitored attributes for the selected device.
- A Graph summary, displaying a summary of the component in graphical format. Refer to 'Graph Summary Report.

See Also:

- 'Monitoring Devices

[ monitor.devices:monitordevice,monitordevicetips ]

Monitor > Review Devices | [ Top ]
Storage Automated Diagnostic Environment
Monitor Devices | [ Help ]
[ Summ. | Health | Log | Report | Graph ]
Graph of 6120 diag210 [IP_NO]
[ Connection Details ]
I
| volume.u1vol2 [ Advisor ] Act.
| 2005-04-01 07:44:44 The state of 'volume.u1vol2.volCacheMode' on diag206 is 'disabled'
Connection Details | [ Top ]
6120 'diag210' SUN StorEdge-6120-10000003ba27d516_qlc6
ctrl-1 | 20030003ba27d516 /devices/pci@4,2000/SUNW,qlc@2,1/fp@0,0
| Connected to host 'diag230.site' hba-7 [ LinkTest ]

[ GUI::Instr::rStart ]

Event Log Report

Event Log Report |

To access the Event Log Report, click the Log link from the Monitor Devices menu.

The Event Log contains the following information.

- Date and time the event occurred.
- Severity icon Note: Mouse over the severity icon to find the numerical value associated with each severity level:
  - 0 = green
  - 1 = yellow (warning)
  - 2 = red (error)
  - 3 = down (component is down)
- Event
- Description of the event

Click the Event's link to access the Event Grid.

The device's EventGrid Info screen is displayed.

The Event Grid, also known as the Service Advisor shows all of the actionable and non-actionable events the Storage Automated Diagnostic Environment generates. Refer to 'Service Advisor for more information.

See Also:

- 'Alerts, Alarms, Events Description
- 'Health Report
- 'Monitor Devices
- 'Summary Report
- 'Device Detail Report
- 'Graph Summary Report

[ monitor.devices_1:eventlogreport,devicereport,graphreport,health ]

Device Summary

Device Summary |

The 'Summary Report page provides detailed information about a selected device.

From the Summary Report page, you can gather very detailed information about each component of the device.
The information is nested for easy navigation.

To access the Device Report Summary page:

1. Click the Report link from the Summary Report page.
2. Click the plus (+) icon that corresponds to the component for which you need detailed information.
   The subtopics for that component are displayed.
3. Click the link on a subtopic.
   The details for the subtopic are displayed in a second window, below the menu window.

Topics and subtopics for the Sun StorEdge 6120 array include:

- Controller
- Disk
- ID
- Info
- Location
- Loopcard
- LUN
- Midplane
- Port
- Power
- Slice
- Sys
- System
- Unit
- Volume

See Also:

- 'Alerts, Alarms, Events Description
- 'Monitor Devices
- 'Health Report
- 'Event Log Report
- 'Summary Report
- 'Graph Summary Report

[ monitor.devices_1:eventlogreport,devicereport,graphreport,health ]

Graph Summary

Graph Summary |

The Graph Report page displays the status of the Sun StorEdge T3, T3+, and 6120 array in graphical format.

To access the Graph Summary page, click the Graph link from the Monitor Devices.
An illustration of the Sun StorEdge T3, T3+, and 6120 array is displayed, with the following detail:

- Volumes
- Data
- Ethernet

Mouse over the component to view more detailed information about each component.

See Also:

- 'Alerts, Alarms, Events Description
- 'Monitor Devices
- 'Health Report
- 'Event Log Report
- 'Summary Report
- 'Device Summary

[ monitor.devices_1:eventlogreport,devicereport,graphreport,health ]

Health Report

Health Report |

Access the Health Report page by clicking the Health link on the Monitor Devices menu.

A summary of the health of every FRU for the device is displayed, along with its severity level. If you want to delete the Health Summary, click Delete Health.

See Also:

- 'Alerts, Alarms, Events Description
- 'Monitoring Device Tips
- 'Summary Report
- 'Event Log Report
- 'Device Detail Report
- 'Graph Summary Report

[ monitor.devices_1:eventlogreport,devicereport,graphreport,health ]

Monitor > Monitor Topology | [ Top ]
Storage Automated Diagnostic Environment
Monitor Topology |  | [ Search | Print | Clear | Help ]

[ GUI::Graph::frame ]

View a Topology

Display a Host-Based Topology |

Use the Topology section to display a host-based topology and SAN-based topologies.

Before you view a topology, you must first do the following:

1. Execute the ras_install command to start the Storage Automated Diagnostic Environment services,
   which is part of the normal installation process.
2. After you have discovered a device, create a Topology snapshot. Refer to 'Topology Snapshot
   for instructions about how to create a topology snapshot.

Note:
If two hosts (one master host and one slave host) are connected to the same set of switches, always select the Master Topology from the Monitor Topology menu.
Whereas the Master Topology displays an accurate representation of a two-host topology, the slave topology inaccurately displays the devices as direct-attached.

See Also:

- 'Display Topology Feature Hints
- 'Topology Footer Help
- 'Topology Icon Definitions
- 'Topology SnapShot

[ monitor.topo:selecthost,topohints,footerhelp,topoicons,topoalerts,clearalerts,mpxioerrors,fcerrors ]

Topology Feature Hints

Topology Feature Hints |

After you have selected a topology, several functions are available in the graphical view:

- To narrow the size of the topology, select an address from the Filter pull-down menu and click GO.
- To zoom in closer, right click on the screen's white space.
  You can specify the zoom value, which varies depending on screen configuration, with the left mouse button.
- To display the status of the device in the footer status bar, click the middle of an object.
- To present a menu of functions available for an object, click the object with the right mouse button.
- To present a menu of functions available for a link, click the link with the right mouse button.
- To rearrange a topology, click a device with the right mouse button, hold it, and move the device or devices to the position of your choice.
  After the topology is rearranged, click "Save XY" from the Footer bar.

See Also:

- 'Topology Footer Help
- 'Topology Icon Definitions

[ monitor.topo:selecthost,topohints,footerhelp,topoicons,topoalerts,clearalerts,mpxioerrors,fcerrors ]

Topology Footer Feature Hints

Topology Footer Features |

After you have selected a topology, several functions are available from the Topology footer bar:

- Save XY--Saves the layout.
- Graphics On/Off--Displays actual illustrations of the devices, rather than the default conceptual drawings.
- [Layout]--Converts the topology layout to a Sun StorEdge series cabinet (Rack).
- Horizontal/Vertical--Changes the topology layout from horizontal (default) to vertical.
- Links On/Off--Displays the connections between devices (default).
  After the links are displayed, click the link with the right mouse button to display link errors. Alternatively, you can run Link Test.

See Also:

- 'Topology Help
- 'Topology Icon Definitions

[ monitor.topo:selecthost,topohints,footerhelp,topoicons,topoalerts,clearalerts,mpxioerrors,fcerrors ]

Topology Icon Definitions

Topology Icons |

The icons shown in Topology Help symbolize the various storage devices that monitors. Inside each storage device icon are boxes that represent disks inside the arrays, ports, and 'Other' components at the bottom of the device icons.

The 'Other' component category includes a variable set of boxes that represent components of the enclosures that are monitored:

- A = Alerts
- B = Backplane
- F = Fan
- K = Links
- l = loopcard (on Sun StorEdge T3+ array)
- L = LUN
- M = Midplane
- N = Network Terminal Concentrator (NTC)
- O = Other
- P = Power
- T = Temp
- V = Volume

Notes:

- Fibre Channel errors are represented by red links with the word 'fc' in re d. This means that CRC or ITW were found at either end of the link in red.
  Fibre Channel errors are usually intermittent and do no represent a hard failure. When a hard failure occurs, a switch port going offline for example, fibre channel counters are ignored.
- Links that are labeled 'mpxio' in the Topology could indicate one of the followin g:

- If a RED 'mpxio' label is displayed in the topology, a Sun StorEdge Traffic Manag er failover has occurred on this path.
- If a green 'mpxio' label is displayed in the topology, a Sun StorEdge Traffic Man ager failover has occurred on this path, but was later corrected.

- The Sun StorEdge D2 array unit has 12 slots for disk drives. These slots are accessed through the front door of the Sun StorEdge D2 array. In the topology view, these 12 slots are represented by two rows of squares:

- Row 0 represents the six disk drives on the left side of the unit.
- Row 1 represents the six disk drives on the right side of the unit.
- Row 1, slot 5 is the rightmost slot in the Sun StorEdge D2 array enclosure.

See Also:

- 'Topology Feature Hints
- 'Fibre Channel Errors

[ monitor.topo:selecthost,topohints,footerhelp,topoicons,topoalerts,clearalerts,mpxioerrors,fcerrors ]

Topology Health

Topology Alerts |

To Isolate a Faulty Enclosure Component

1. From the topology, click a component with the right mouse button.
   A pop-up menu is displayed.
2. From the pop-up menu, click Report.
   The Monitor Devices Report window is displayed in the right frame.

Refer to 'Alerts Report, 'Device Summary, 'Graph Report, or 'Summary Report.

Each of these reports display events, but vary in degree of detail.

Note:

- The 'Device Report contains the most detail.
- The 'Graph Report displays alerts for the Sun StorEdge 6120 array only.

See Also:

- 'Topology Icons
- 'Clear Topology Alerts
- 'Monitor Devices

[ monitor.topo:selecthost,topohints,footerhelp,topoicons,topoalerts,clearalerts,mpxioerrors,fcerrors ]

Clear Alerts

Clear Alerts |

To Clear Green Alerts

1. Select the Clear link in the upper right corner of the Topology view.
   A pop-up question is displayed: "Are you sure you want to clear all GREEN alerts?"
2. Click OK.
   All green alerts are removed from the topology.

To Clear Yellow or Red Alerts for a Device

Note:
Yellow or red alerts must be removed manually, but do not remove them until you are certain the faults have been corrected.
The condition that caused the alert still exists, but will not be displayed in the topology once it has been removed.

1. From the topology, click a device that has one or more yellow red alerts with the right mouse button.
2. From the pop-up menu, select Alerts.
   If alerts exist for that device, a list is displayed in the right frame.
3. Click Delete Alerts to clear all red and yellow alerts for that device.

To Clear Red and Yellow Alerts for a Link

1. Click the link with the right mouse button.
   Note: You can also run a link test from the Link pop-up menu.
2. From the pop-up menu, select Display Error.
   A Clear Link Errors button is displayed in the right frame.
3. Click Clear Link Errors.

See Also:

- 'Topology Icons
- 'Topology Health

[ monitor.topo:selecthost,topohints,footerhelp,topoicons,topoalerts,clearalerts,mpxioerrors,fcerrors ]

MPxIO Link Errors

MPxIO Link Errors |

Links that are labelled 'mpxio' in the Topology could indicate one of the following:

- If a RED 'mpxio' label is displayed in the topology, a Sun StorEdge Traffic Manager failover has occurred on this path.
- If a GREEN 'mpxio' label is displayed in the topology, a Sun StorEdge Traffic Manager failover has occurred on this path, but was later corrected.

See Also:

- 'Display Topology Feature Hints
- 'Fibre Channel Errors
- 'Topology Icons

[ monitor.topo:selecthost,topohints,footerhelp,topoicons,topoalerts,clearalerts,mpxioerrors,fcerrors ]

Fibre Channel Errors

Fibre Channel Errors |

Fibre Channel errors are represented by red links and the letters 'fc,' also in red. Fibre Channel errors indicate that CRC or ITW were found at either end of the link in red.

Fibre Channel errors are usually intermittent and do not represent a hard failure.
When a hard failure occurs, such as when a switch port has gone offline, fibre channel counters are ignored.

See Also:

- 'Display Topology Feature Hints
- 'MPxIO Errors
- 'Topology Icons

[ monitor.topo:selecthost,topohints,footerhelp,topoicons,topoalerts,clearalerts,mpxioerrors,fcerrors ]

Monitor > Monitor Log | [ Top ]

Monitoring Logs

Monitoring Logs |

Storage Automated Diagnostic Environment event and alert logs enable you to view various message files. In addition, you can specify criteria used to generate Event Logs an Alert Logs.

See Also:

- 'View the Most Recent Entries on a Host
- 'View Alert Logs
- 'View Event Logs
- 'Display Agent Errors

[ monitor.log:accesslog ]

Monitor > Monitor Log > Messages | [ Top ]
Storage Automated Diagnostic Environment
Messages | [ Help ]
View various message files on all agents. 'Sun T3 Log' shows messages.t3 and 'Trap' shows trap_messages in the /var/adm directory. Note: On slaves only the base message files are shown.
Host's log files
HostName | Log Type | Log
diag230.site / [IP_NO] | Message | messages
| Message | messages.1
| Message | messages.2
| Trap | trap_messages
| Array | messages.t300
| 3510 | messages.3310
jeannot.site / [IP_NO] | Message | messages
| Message | messages.1
| Message | messages.2
| 3510 | messages.3310
crashme41.site / [IP_NO] | Message | messages
| Message | messages.1
| Message | messages.2
| 3510 | messages.3310

[ GUI::MessageLog::list ]

View the Most Recent Entries on a Host

View the Most Recent Entries on a Host |

You can review the content of the `/var/adm/messages` and array message log files from a host. Log entries are displayed from the end of the file going back; the most recent entries are shown first. The Storage Automated Diagnostic Environment must be functioning properly on each host for the `/var/adm/messages` log file to display the entries correctly.

- Select a Host from the HostName column and click the corresponding `/messages link`.

The descending list of `/var/adm/messages` on the local host is displayed.

See Also:

- 'Access the Log Page
- 'View an Event Log for a Host
- 'View Alert Logs
- 'Display Agent Errors

[ monitor.log.messages:varadm ]

Monitor > Monitor Log > Event Log | [ Top ]
Storage Automated Diagnostic Environment
Event Log | [ Help ]
Used to search the Event Log
Agent Host: |
Category: |
Severity: |
Event: |
Event Type: |
Read the last X KBytes from LogFile: |
Filter1: |

[ GUI::EventLog::list ]

View an Event Log

View Event Log |

1. From the Monitor Log window, select Event Log.
2. Customize the report by using the following pull-down menus:

- Agent Host

- Category-All is the default.
  The device types supported by the current Storage Automated Diagnostic Environment version will be displayed in the pull-down menu.

- Severity-options include All (the default), System Down, Critical (error), Alert (warning), and Caution (information).
- Event-All is the default.
  The event types supported by the current Storage Automated Diagnostic Environment version will be displayed in the pull-down menu.

- Event Type-options include All (the default), System Component Events, and System Events.

- Read the last X Kbytes from LogFile-options include 25KB (the default), 50 KB, 75KB, 100KB.
- Filter1-Type the IP address for which you want to view the Event Log into the Filter1 text box.

After you have altered each field (or accepted All as the defaults), click Search Log to produce a customized Event Log.

See Also:

- 'Access the Log Page
- 'View the Most Recent Entries on a Host
- 'View an Alert Log for a Host
- 'Display Agent Errors

[ monitor.log.events:eventlog,alertsalarms ]

Events, Alerts, and Alarms

Events, Alerts, and Alarms |

The terms event, alert, and alarms are often mistakenly used interchangeably.

A definition of each term follows.

- An event is a notification that contains information about something that has happened on a device. There are many types of events and each type describes a different occurrence.

- An alert is a subtype of an event that requires user intervention. Often, the term actionable event describes an alert.
  For example, if a power supply failed, two events would be generated:
  - A StateChangeEvent, indicating that the power supply's state has changed from good to bad.
  - A StateChangeAlert, indicating that the power supply's state change from good to bad warrants the user's attention.

- An alarm is the user interface mechanism by which a user manages an alert. It is a warning of an existing or approaching alert.

See Also:

- 'Health Report
- 'Monitor Devices
- 'Summary Report
- 'Event Log Report
- 'Device Detail Report
- 'Graph Summary Report

[ monitor.log.events:eventlog,alertsalarms ]

Monitor > Monitor Log > Alert Log | [ Top ]
Storage Automated Diagnostic Environment
Alert Log | [ Help ]
Used to search the Alert Log, note: alerts are actionable events
Agent Host: |
Category: |
Severity: |
Event: |
Event Type: |
Read the last X KBytes from LogFile: |
Filter1: |

[ GUI::EventLog::alerts ]

View Alert Log |

Note:
Alerts are actionable events. The Alert log is considerably shorter than the Event Log.

1. From the Monitor Log window, select Alert Log.
2. Customize the report by using the following pull-down menus:

- Agent Host

- Category-All is the default.
  The device types supported by the current Storage Automated Diagnostic Environment version will be displayed in the pull-down menu.

- Severity-options include All (the default), System Down, Critical (error), Alert (warning), and Caution (information).
- Event-All is the default.
  The event types supported by the current Storage Automated Diagnostic Environment version will be displayed in the pull-down menu.

- Event Type-options include All (the default), System Component Events, and System Events.

- Read the last X Kbytes from LogFile-options include 25KB (the default), 50 KB, 75KB, 100KB.
- Filter1-Type the IP address for which you want to view the Event Log into the Filter1 text box.

After you have altered each field (or accepted All as the defaults), click Search Log to produce a customized Alert Log.

[ monitor.log.alerts:alertlog ]

Monitor > Monitor Log > Agent Errors | [ Top ]
Agent Errors | [ Help ]
This section displays system errors generated by the Storage Automated Diagnostic Environment Agent during execution. Select a host to see the system error log of the agent on that host. System Errors are usually related to a file security problem, perl execution errors and other system errors. The agent can usually recover from these errors but will have to skip a part of its normal execution.
Select an existing Host
Host | HostID | Location
--- | --- | ---
Master | 80a3738d |
jeannot.site | 8089d4eb | jeannot.site
crashme41.site | 80b43b26 | crashme41.site

[ GUI::Errlog::list ]

Display System Errors

Display System Errors |

The Storage Automated Diagnostic Environment System Errors window displays the 25 most recent system errors that have occurred on a host.

System errors may relate to security problems, execution errors, or other system errors.

To alter the default number of 25 errors, enter a number into the #Errors field and click Refresh.

See Also:

- 'Monitoring Log Page
- 'View the Most Recent Entries on a Host
- 'View an Event Log for a Host
- 'View Alert Logs

[ monitor.log.errors:raserrors ]

Monitor > Monitor Utilities > Clear Device Health | [ Top ]
Storage Automated Diagnostic Environment
Clear Device Health | [ Help ]
Clear Current Device errors/warnings and Link errors/warnings from the State database. This will only affect the current health status of the device.
Current Component State
Delete | Device | Component | Severity | Description
--- | --- | --- | --- | ---
| 6120:diag210 | volume.u1vol2 |  | 2005-04-01 07:44:44 The state of 'volume.u1vol2.volCacheMode' on diag206 is 'disabled'

[ GUI::State::clear ]

Clear Device Health

Clear Device Health |

Clear Device Health enables you to clear current device errors and warnings and link errors and warnings from the State database.

To clear health information:

1. From the Monitor Utilities window, click Clear Device Health.
2. Select the device component and click its corresponding Delete button.
   Scroll down to the bottom of the window to select the Delete option.
   - Delete Selected
   - Delete All Green
   - Delete All Warnings
   - Delete All Link Alerts
   - Delete All Alerts

[ monitor.utilities.errors:cleardevicehealth ]

Monitor > Monitor Utilities > Solution Extract | [ Top ]
Storage Automated Diagnostic Environment
Solution Extract | [ Help ]
This command will create a tar file that contains an 'explorer' like snapshot of the Sun Solution Configuration including Events, logfiles, configuration logs, storage array commands etc.. Review the Extract-log for more details.
Start Extract Command
Storage Array Password (optional, apply to all storage arrays in the rack): |
Download existing extract report (most recent first)
Download | File Size (k) | Extract Log
--- | --- | ---

[ Service::Extract::run ]

Sun Solution Extractor

Sun Solution Extractor |

This command will create a tar file that contains an 'explorer' like snapshot of the Sun Solution Configuration including Events, logfiles, configuration logs, storage array commands etc..
Review the Extract-log for more information about the script execution. Extract logs are located in the /opt/SUNWstade/DATA/Download/Solution/ directory.

Here is a sample extract log:

Extract Logfile : 2002-11-17_144057

    -> MODULE: Sun Solution ..
        -> cp /etc/hosts      /opt/SUNWstade/DATA/Download/Solution/extract/Rack/etc_hosts ..
        -> /opt/SUNWsecfg/bin/getcabinet  ..
        -> cp /export/README.txt      /opt/SUNWstade/DATA/Download/Solution/extract/Rack/export_readme.txt ..
        -> tail -1000 /var/adm/log/SEcfglog  ..

    -> MODULE: Storade ..
        -> cp /opt/SUNWstade/DATA/rasagent.conf       /opt/SUNWstade/DATA/Download/Solution/extract/Storade/rasagent.conf ..
        -> cp /opt/SUNWstade/DATA/Events.log          /opt/SUNWstade/DATA/Download/Solution/extract/Storade/Events.log ..
        -> pkginfo -l SUNWstade  ..
        -> showrev -p|grep SUNWstade  ..
        -> /opt/SUNWstade/bin/ras_admin site_info  ..
        -> /opt/SUNWstade/bin/ras_admin device_list  ..
        -> /opt/SUNWstade/bin/ras_admin email_list  ..
        -> /opt/SUNWstade/bin/ras_admin provider_list  ..

    -> MODULE: SP
        -> cp /etc/services /opt/SUNWstade/DATA/Download/Solution/extract/Sp/service ..
        -> cp /etc/inetd.conf /opt/SUNWstade/DATA/Download/Solution/extract/Sp/inetd.conf ..
        -> ps -ef  ..
        -> df -k  ..
        -> tail -1000 /var/adm/messages       ..
        -> tail -1000 /var/adm/messages.t3    ..
        -> tail -1000 /var/adm/messages.t300  ..

    -> MODULE: Switch ..
      -> sw1 ..
        -> sanbox version -port 5003 [IP_NO]
        -> sanbox chassis_id -port 5003 [IP_NO]
        -> sanbox chassis_status -port 5003 [IP_NO]
        -> sanbox links -port 5003 [IP_NO]
        -> sanbox port_counts -port 5003 [IP_NO] all
        -> sanbox port_status -port 5003 [IP_NO] all
        -> sanbox port_state -port 5003 [IP_NO] all
        -> sanbox chassis_counters -port 5003 [IP_NO] all
        -> sanbox get_zone -port 5003 [IP_NO] hd all
        -> sanbox get_zone -port 5003 [IP_NO] sl all
        -> sanbox nameserver -port 5003 [IP_NO]

    -> MODULE: STORAGE ARRAY
      -> t3 t300-8..
        -> ver
        -> arp -a
        -> tzset
        -> date
        -> set
        -> .set
        -> .ep info
        -> sys list
        -> .sys list
        -> sys stat
        -> sys fc_topology
        -> fru list
        -> fru myuid
        -> fru stat
        -> fru statsys
        -> fru statistic
        -> vol list
        -> vol stat
        -> vol mode
        -> refresh -s
        -> route -r
        -> proc list
        -> port list
        -> port listmap
        -> .loop stat
        -> ntp
        -> ntp -v
        -> ntp stats
        -> ls -l
        -> ls -l etc
        -> ls -l web
        -> volslice list
        -> lun map list
        -> lun wwn list
        -> lun perm list
        -> hwwn list
        -> hwwn listgrp
        -> disk version u1d1-9
        -> disk version u2d1-9
        -> .disk pathstat u1d1-9
        -> .disk pathstat u2d1-9
        -> .disk softerr u1d1-9
        -> .disk softerr u2d1-9
        -> .disk harderr u1d1-9
        -> .disk softerr u2d1-9
        -> .disk linkstat u1d1-9
        -> .disk linkstat u2d1-9
      -> t3 diag208..
        -> ver
        -> arp -a
        -> tzset
        -> date
        -> set
        -> .set
        -> .ep info
        -> sys list
        -> .sys list
        -> sys stat
        -> sys fc_topology
        -> fru list
        -> fru myuid
        -> fru stat
        -> fru statsys
        -> fru statistic
        -> vol list
        -> vol stat
        -> vol mode
        -> refresh -s
        -> route -r
        -> proc list
        -> port list
        -> port listmap
        -> .loop stat
        -> ntp
        -> ntp -v
        -> ntp stats
        -> ls -l
        -> ls -l etc
        -> ls -l web
        -> volslice list
        -> lun map list
        -> lun wwn list
        -> lun perm list
        -> hwwn list
        -> hwwn listgrp
        -> disk version u1d1-9
        -> disk version u2d1-9
        -> .disk pathstat u1d1-9
        -> .disk pathstat u2d1-9
        -> .disk softerr u1d1-9
        -> .disk softerr u2d1-9
        -> .disk harderr u1d1-9
        -> .disk softerr u2d1-9
        -> .disk linkstat u1d1-9
        -> .disk linkstat u2d1-9

    -> MODULE: VE

    -> TAR..
        -> tar cf /opt/SUNWstade/DATA/Download/Solution/extract_2002-11-17_144057.tar extract ..
    [ monitor.utilities.extract:se_extract ]

              Diagnose > Diagnostic Tests > Test from Topo.[ Top ]

                        Storage Automated Diagnostic Environment

                 Monitor Topology

            [  Search | Print | Clear  |  Help ]
    [ GUI::Test::frame ]

    Test from Topology

     Test from Topology

    The Storage Automated Diagnostic Environment Graph view shows the
    physical topology of a system.
    Using the Topology view, you can select specific subtests and test options.
    The monitoring status of devices and links appears both in the Test
    from Topology view and in the Test from List view.
    Test from Topology Hints

    To narrow the size of the topology, select an address from the Filter
    pull-down menu and click GO.
    To zoom in closer, right click on the screen's white space.
    You can zoom by selecting the value with your left mouse button.
    To list test options, using your right mouse button, select the device.
    With your left mouse button, select the test you want to run on the device.

    The applicable test is displayed in the right pane.
    Select the Clear link in the Topology view to remove all the green links
    from the topology.  The red and yellow links remain in the topology until
    the faults have been corrected.
    While a test is running, you can access Test Manager to view the status
    of the test.
    After the test has completed its run, an email message is sent to the
    specified email recipient.

    Notes:

    The Storage Automated Diagnostic Environment Link Test enables FRU
    isolation for Fibre Channel devices.
    You can invoke the Link Test from the Topology view by selecting the
    link.
    You cannot run a veluntest(1M) on a host that
    is connected to a Sun StorEdge 6120 array.
    In-band tests can be run from the Test from Topology view with
    no restrictions.
    An out-of-band test (for example, t3ofdg or
    t3volverify) can be run from the Test from Topology
    view if it is run from the Monitoring Host view

    See Also:

    'Test Rules
    'Command Line Tests
    'GUI Tests
    'Run Tests from the GUI Test List
    'Test Manager
    'Test Defaults

    [ diagnose.test.topo_test:testfromtopo,guitests ]

    Graphical User Interface (GUI) Tests

     Running Diagnostic Tests from the GUI

    The diagnostic tests are designed to test the target FRU and operate on an
    in-band or out-of-band data path.  The Storage Automated Diagnostic Environment
    scheduler will dispatch the test to be run on the appropriate server (host).
    If you run the diagnostic test from the Storage Automated Diagnostic Environment main window,
    you can easily access test configuration, control, and results using the buttons in the
    dialog boxes.  The test parameter options, however, are unique for each test.
    With two exceptions, you can run Storage Automated Diagnostic Environment
    diagnostic tests from either Test from List or Test from Topology.

    You can invoke the Link Test by right-clicking on the box in the link
    displayed in the topology.  You cannot invoke the Link Test
    functionality using Test from List.
    Unconnected HBAs (HBAs that are not connected to any device) can only be
    tested using the Test from List option.

    See Also:

    'Test Rules
    'Command Line Tests
    'Run Tests from the GUI Topology
    'Run Tests from the GUI Test List
    'Test Manager
    'Delete Tests
    'Test Defaults
    'Test Archive

    [ diagnose.test.topo_test:testfromtopo,guitests ]

              Diagnose > Diagnostic Tests > Test from List[ Top ]

                Test from List
    [ Host List |  Help ]

             Host:
            Filter:

         + Device Component Status Run Test
     6120:diag210 lpath c18t60003BA27D516000  E64666400056BC9d0s2  comp 6120-LUN
     OutOfBand   6120-ofdg,  6120-loop,  6120-VolVerify
     a5k:DSQA2 port0   A5000-SES
     port1   A5000-SES
     All Disks   A5000-Disk
     d2:013203 All Disks   D2-Disk
     host:diag230 hba0 / soc0_0   SOCAL
     hba1 / soc0_1   SOCAL
     hba2 / soc1_0   SOCAL
     hba3 / soc1_1   SOCAL
     hba4 / qlc3   QLC
     hba5 / qlc4   QLC
     hba6 / qlc5   QLC
     hba7 / qlc6   QLC
     hba8 / qlc0   QLC
     hba9 / qlc1   QLC
     hba10 / qlc2   QLC
     hba11 / qlc7   QLC
     hba12 / qlc9   QLC
     hba13 / qlc8   QLC
     mcdata:diag183 All Ports  Mcdata-Test(s)
     switch2:diag141 All Ports  Switch2-Test(s)
     switch2:diag140 All Ports  Switch2-Test(s)
     switch2:diag99 All Ports  Switch2-Test(s)
     switch2:diag111 All Ports  Switch2-Test(s)
     switch:[IP_NO] All Ports  Switch-Test(s)
     switch:[IP_NO] All Ports  Switch-Test(s)
     t3:diag208 lpath c18t60020F20000009B7  DFDCF3700046D5Bd0s2   T3-LUN
     lpath c18t60020F20000009B7  DFDCF560007AA9Ed0s2   T3-LUN
     OutOfBand   T3-ofdg,  T3-VolVerify
     t3:diag211 lpath c18t60020F2000000AD8  BD90309000AC1FEd0s2   T3-LUN
     lpath c18t60020F2000000AD8  BD903490008E2F1d0s2   T3-LUN
     OutOfBand   T3-ofdg,  T3-VolVerify
     t3:diag103 lpath c18t60020F2000006CE5  E81B9E50007F39Ed0s2   T3-LUN
     OutOfBand   T3-ofdg,  T3-VolVerify
     tape:500104f0004b475b port0   FC-Tape

        Page: 1 of 1

      [ GUI::TopoList::list_frame ]

    Test from List

     Test from List

    Storage Automated Diagnostic Environment's implementation of diagnostic tests
    verifies the operation of all the user-selected components. Tests are selected from
    a list of physical devices.
    The Test from List view shows the devices and their associated tests.
    This list also includes warnings and errors reported by the monitoring agents.  In
    addition, Test from List displays all available host/HBA tests and not just the
    connected ports, as the Test from Topology view displays.
    Using Test from List, you can:

    Sort by host, device type, test type, and device status
    Select options for a specific device, for multiple devices, or for all
    devices
    Select the number of passes each test will run.

    To Invoke the Test Option Pane for a Particular Device

    Using the Test from List window, select the diagnostic test.
    Select a host from the Host pull-down menu.
    From the Filter pull-down menu, select a specific device, multiple devices, or
    click All to display all devices.
    Click GO.

    A list that is customized to your criteria is displayed.
    To run diagnostics, select the test name link in the Run Test column.

    The appropriate test window is displayed in the right frame.

    See Also:

    'Test Rules
    'Command Line Tests
    'GUI Tests
    'Run Tests from the GUI Topology
    'Test Manager

    [ diagnose.test.list_test:testfromlist,testrules ]

    Test Rules

     Diagnostics Test Rules

    Certain tests have limitations and cannot be run with other tests.  The following rules
    exist with Storage Automated Diagnostic Environment diagnostic tests:

    All tests are offline tests that can be used to verify and replace FRUs.
    All devices and paths must be quiesced prior to invocation of diagnostic tests.
    switchtest can run only on one port on a single switch instance at a time.
    linktest cannot be run with other tests, and can only be run using
    Test from Topology.  You cannot run linktest using Test from List.

    Note:
    Any attempts to ignore or circumvent diagnostic test rules will cause pop-up warnings to display.

    See Also:

    'Command Line Tests
    'GUI Tests
    'Test Defaults

    [ diagnose.test.list_test:testfromlist,testrules ]

              Diagnose > Diagnostic Tests > Test Manager[ Top ]

                Test Manager
    [ Running | All Tests  |  Help ]
    Review and control diagnostic testsTest Manager

         Host Process Command Target - Status Start Select
     diag230 ST-4031 qlctest diag230Done:ERROR 02-24 11:17:22
     sseqa-72 ST-4356 t3test qaencl92Done:OK 02-24 12:34:52

        Page: 1 of 1

         [ GUI::ProcMgr::list ]

    Test Manager

     Test Manager

    Storage Automated Diagnostic Environment's integration with diagnostic tests
    implements Test Manager to review and control the progress of a user-selected test.
    To display the Test Manager popup window, click a test in the Run Test
    column of Test from List.
    Note:

    For Sun StorEdge 6120 array tests, you may see the following message in a popup window:

    Sun StorEdge 6120-ofdg: This test will take a significant amount of
    time to complete.  Continue?
    Sun StorEdge 6120-VolVerify:  This test will take data off-line and
    may cause monitoring alerts in other components of your SAN while running.
    This test cannot be stopped once started.  Continue?

    For test processes, the states can be:

    Running - the test is running successfully.
    Waiting - user intervention is required for the test to continue.  User intervention
    may involve answering a question or replacing the cables or the gigabit interface converters (GBICs)
    Done:OK - the test ran successfully with no errors
    Done:Error - the test failed and no longer continues to run
    Done:Aborted - the user manually stopped the test before it had finished running.

    Note:
    There is a system timeout associated with the waiting state.  You can adjust
    the system timeout settings using 'System Timeouts.

    See Also:

    'Test Rules
    'Command Line Tests
    'GUI Tests
    'Run Tests from the GUI Topology
    'Run Tests from the GUI Test List

    [ diagnose.test.test_mgr:testmanager,deletetests ]

    Delete Tests

     Archive or Delete Tests

    Storage Automated Diagnostic Environment's implementation of diagnostic tests enables you to view archived diagnostic logs saved by Test Manager.

    To delete a single test, click the test's link.

    A Test Detail popup window is displayed.  Scroll to the bottom of the
    Test Detail and click Delete Test.
    To delete all tests, click the Delete-All button.
    To view a list of archived tests, click the Test Archive link from the Diagnostic Tests menu.

    See Also:

    'Test Rules
    'Command Line Tests
    'GUI Tests
    'Run Tests from the GUI Topology
    'Run Tests from the GUI Test List
    'Test Manager
    'Test Defaults
    'Test Archive

    [ diagnose.test.test_mgr:testmanager,deletetests ]

Diagnose > Diagnostic Tests > Test Mgr.(popup) | [ Top ]

Test Manager

Test Manager |

Storage Automated Diagnostic Environment's integration with diagnostic tests implements Test Manager to review and control the progress of a user-selected test.

To display the Test Manager popup window, click a test in the Run Test column of Test from List.

Note:
For Sun StorEdge 6120 array tests, you may see the following message in a popup window:

- Sun StorEdge 6120-ofdg: This test will take a significant amount of time to complete. Continue?
- Sun StorEdge 6120-VolVerify: This test will take data off-line and may cause monitoring alerts in other components of your SAN while running. This test cannot be stopped once started. Continue?

For test processes, the states can be:

- Running - the test is running successfully.
- Waiting - user intervention is required for the test to continue. User intervention may involve answering a question or replacing the cables or the gigabit interface converters (GBICs)
- Done:OK - the test ran successfully with no errors
- Done:Error - the test failed and no longer continues to run
- Done:Aborted - the user manually stopped the test before it had finished running.

Note:

There is a system timeout associated with the waiting state. You can adjust the system timeout settings using 'System Timeouts.

See Also:

- 'Test Rules
- 'Command Line Tests
- 'GUI Tests
- 'Run Tests from the GUI Topology
- 'Run Tests from the GUI Test List

[ diagnose.test.test_mgr2:testmanager ]

Diagnose > Diagnostic Tests > Test Archive | [ Top ]
Storage Automated Diagnostic Environment
Test Archive | [ Help ]
Review the results of archived tests
| Look back: Days
Host
Test
System
| Comp |
- Started
| Result |
Archived
Pid
| Select
Page: 1 of 1 |  |

[ GUI::ProcMgr::archive ]

Test Archive

Test Archive |

Use the Test Archive functionality to view tests that have previously run on a host, or to delete an archived test.
A summary of the test is displayed, along with recommended actions you can take to run a more successful test.

Note:

The same functionality can be found using 'Test Manager.

See Also:

- 'Test Rules
- 'Command Line Tests
- 'GUI Tests

[ diagnose.test.archive:testarchive ]

Diagnose > Revision Checking | [ Top ]

Revision Checking

Revision Checking |

Storage Automated Diagnostic Environment's implementation of Revision Checking checks the software, hardware, and firmware revisons of all the user-selected components.

Revision checking is based on an updatable matrix, which is generated using the PatchPro database. The matrix provides distributed revision checking across the system. Solaris versions and component firmware versions are verified against the matrix.

To Run the Revision Checking Report

1. Select a host from the pulldown window and click GO.

   The window reloads and returns updated information for the specified host.

2. Select a configuration matrix from the pulldown menu.

   The matrices are sorted by revision level and date, the most recent matrix first.

3. Deselect a device or devices from the Select Module list. All of the devices are checked by default.
4. In the email text box, type an email address or addresses to where the Revision Checking results will be sent.
5. Click Run Revision Checking.

See Also:

- 'Fibre Channel Counters Check
- 'Fibre Channel Counters Check Report
- 'Display Revision Checking Report
- 'Display Revision Checking History

[ diagnose.revision:run_report ]

Diagnose > Revision Checking > Run Report | [ Top ]
Run Report | [ Help ]
Select options to run Revision Checking
Select Host: |
Select Matrix: |
Select Module: |
: Sun StorEdge 6120 array firmware/disk/loop/pcu
: Sun StorEdge A5000 array Patches and Disk Firmware
: Sun StorEdge D2
: Host Patches
: HBA Patches
: McData Switch Firmware
: Solstice Software
: Sun StorEdge network FC switch-8 and switch-16
: Sun StorEdge network 2Gb FC switch-8 and switch-16
: Sun StorEdge T3 and T3+ array firmware/disk/loop/pcu
: Sun FC-Tape Firmware
: Veritas Software
Email: |

[ GUI::Revision::run ]

Run Revision Checking

Revision Checking checks the software, hardware, and firmware revisions of all the user-selected components.

Revision checking is based on an updatable matrix, which is generated using the PatchPro database. The matrix provides distributed revision checking across the system. Solaris versions and component firmware versions are verified against the matrix.

To Run Revision Checking Report

1. Click Revision Checking from the Diagnose page.
2. Click Run Report.

   The Run Report window is displayed.

3. Select a host from the pulldown window and click GO.

   The window reloads and returns updated information for the specified host.

4. Select a configuration matrix from the pulldown menu.

   The matrices are sorted by revision level and date, the most recent matrix first.

5. Deselect a device or devices from the Select Module list. All of the devices are checked by default.
6. In the email text box, type an email address or addresses to where the Revision Checking results will be sent.
7. Click Run Revision Checking.

[ diagnose.revision.run:revisionrun ]

Diagnose > Revision Checking > Display Report | [ Top ]
Storage Automated Diagnostic Environment
Display Report | [ Help ]
Review revision checking reports
Monitor Revision Report
Host | Last Report | Status | Report List
--- | --- | --- | ---
Local | Display Report | Done / Wed Apr 2 14:37:24 MST 2003 |
jeannot.site | No Report | Not running |
crashme41.site | No Report | Not running |

[ GUI::Process::list ]

Run Revision Checking

Revision Checking checks the software, hardware, and firmware revisions of all the user-selected components.

Revision checking is based on an updatable matrix, which is generated using the PatchPro database. The matrix provides distributed revision checking across the system. Solaris versions and component firmware versions are verified against the matrix.

To Run Revision Checking Report

1. Click Revision Checking from the Diagnose page.
2. Click Run Report.

   The Run Report window is displayed.

3. Select a host from the pulldown window and click GO.

   The window reloads and returns updated information for the specified host.

4. Select a configuration matrix from the pulldown menu.

   The matrices are sorted by revision level and date, the most recent matrix first.

5. Deselect a device or devices from the Select Module list. All of the devices are checked by default.
6. In the email text box, type an email address or addresses to where the Revision Checking results will be sent.
7. Click Run Revision Checking.

[ diagnose.revision.report:revisionrun ]

Diagnose > Revision Checking > Display History | [ Top ]
Storage Automated Diagnostic Environment
Display History : Revision | [ Help ]
Report List
Host | Report | Report List
--- | --- | ---
No historical report available!

[ GUI::Process::history ]

Run Revision Checking

Revision Checking checks the software, hardware, and firmware revisions of all the user-selected components.

Revision checking is based on an updatable matrix, which is generated using the PatchPro database. The matrix provides distributed revision checking across the system. Solaris versions and component firmware versions are verified against the matrix.

To Run Revision Checking Report

1. Click Revision Checking from the Diagnose page.
2. Click Run Report.

   The Run Report window is displayed.

3. Select a host from the pulldown window and click GO.

   The window reloads and returns updated information for the specified host.

4. Select a configuration matrix from the pulldown menu.

   The matrices are sorted by revision level and date, the most recent matrix first.

5. Deselect a device or devices from the Select Module list. All of the devices are checked by default.
6. In the email text box, type an email address or addresses to where the Revision Checking results will be sent.
7. Click Run Revision Checking.

[ diagnose.revision.history:revisionrun ]

Diagnose > Diagnostic Utilities > Set Defaults | [ Top ]
Set Defaults | [ Help ]
Set the default options for each available test
Set Defaults to selected Diagnostic Test
Select Test: |
Default Options: | Variable Name:
Verbose Mode: |  | -v
Send Results to Email: |  | #EMAIL

[ GUI::Test::defaults ]

Test Defaults

Test Defaults |

Storage Automated Diagnostic Environment's implementation of diagnostics enables you to set default options to be applied to the user-selected tests.

Default Options

- Verbose Mode -v
Runs the test in verbose mode and displays messages with more detailed information about the testing process. The default is ON.

- Send Results to Email
Enter email addresses to where the test results will be sent. An entry in Send Results to Email from the Default Options screen sends the results of all tests. To send results to email recipients on an individual test, access that test's Default Option screen.

Note:

Email might not be sent if the system is not properly configured to send mail to the recipient. This is primarily evident in Storage Service Processor environments, where the Storage Service Processors are on a subnet and there is no gateway to the intended recipient. Please refer to the Sun StorEdge Series Reference and Service Guide for more information.

See Also:

- 'Test Rules
- 'Command Line Tests
- 'GUI Tests
- 'Test Manager

[ diagnose.tools.defaults:testdefaults,verifysan ]

Verify the SAN

Installation Verification |

To verify a recently-added component of a SAN, or to verify the entire SAN, use the `ras_revcheck`(1M) test and the `stresstest`(1M) test with FC_CHECK enabled.

By running `ras_revcheck`(1M), you can determine that your firmware and software are up to date.

By running `stresstest`(1M), you can:

- Apply a load to your system for a specified period of time
- Monitor the data path for retry and other errors

Note:

Both `ras_revcheck`(1M) and `stresstest`(1M) are available only through the command line interface (CLI) at this time. They cannot be accessed through the Storage Automated Diagnostic Environment GUI.

To Verify a SAN Component

Type:
`# /opt/SUNWstade/bin/ras_revcheck -M "T3"`
`# /opt/SUNWstade/Diags/bin/stresstest -M "T3 | FC_CHECK" -T "180"`

To Verify the Entire SAN

Type:
`# /opt/SUNWstade/bin/ras_revcheck -M "ALL"`
`# /opt/SUNWstade/Diags/bin/stresstest -M "ALL" -T "600"`

See Also:

- 'Topology Maintenance
- 'Topology Snapshot
- 'Snapshot History

[ diagnose.tools.defaults:testdefaults,verifysan ]

Manage > Configuration > Configure 3900/6900 | [ Top ]
Storage Automated Diagnostic Environment
Configure 3900/6900 | [ Help ]
Select Host: |
Sun StorEdge 3910 System
Sun StorEdge T3+ Array View/Configure
| Display Config | Display Sun StorEdge T3+ Array Configuration
| Save Config | Save Sun StorEdge T3+ Array Configuration
| Configure | Configure Sun StorEdge T3+ Array(s)
| Modify Parameters | Modify Sun StorEdge T3+ Array System Parameters
| Restore | Restore Sun StorEdge T3+ Array Configuration
| Verify | Verify Sun StorEdge T3+ Array Configuration
| Configuration Status | Display Sun StorEdge T3+ Array Configuration Status
| Manage LUN Slicing | Create/Remove/List/Enable Sun StorEdge T3+ Slice (only on 3900 series)
| Manage LUN Masking | Sun StorEdge T3+ Lun Masking (only on 3900 series)
| Manage Password | Store/Clear Persisted Sun StorEdge T3+ Array Password
Switch View/Configure
| Display Config | Display Switch Configuration
| Verify | Verify Switch Configuration
| Set Config | Set Switch Configuration
| Save Config | Save Sun StorEdge network FC switch Configuration
| Restore Config | Restore Sun StorEdge network FC switch Configuration
| Set Switch Port SL Mode | Set Switch Port SL Mode Per Sun StorEdge T3+ Array (StorEdge 3900 Series Only)
| Set Switch Port TL Mode | Set Switch Port TL Mode (StorEdge 3900 Series Only)
| Set Switch Port F Mode | Set Switch Port F Mode (StorEdge 3900 Series Only)
| Modify Switch Zones | Modify Switch Zones
| Download Firmware | Download Switch Firmware
| Manage Password | Store/Clear Persisted Switch login Password
Log Functions and Sun StorEdge Series Maintenance
| View Log | View Sun StorEdge Series Log File
| View Errors | View Sun StorEdge Series Errors
| Remove Locks | Remove Lock Files
| Show all | Show all Component's details on this system

[ GUI::SE::index ]

Sun StorEdge 3900 and 6900 Series Maintenance

Maintain the log functions of the Sun StorEdge 3900 and 6900 series storage subsystems |

The View Log option from the GUI enables you to look at all the logs for each of the commands executed. Additionally, runsecfg menu enables the user to view the most recent 50 lines and errors encountered for a specific date. The logs contain messages about the configuration actions taken.

- Show All - This option displays the detailed configuration of all components found in the cabinet.

See Also:

- 'Sun StorEdge T3 array configuration
- 'Sun StorEdge network FC switch configuration
- 'Virtualization Engine configuration

[ manage.configure.conf_se:se_maintenance,t3_configure,switch_configure,ve_configure ]

Configure Sun StorEdge T3 Arrays

Configure the Sun StorEdge T3+ Array |

The Sun StorEdge T3+ array menu presents the following options:

- Display Config - Reads and displays configuration information for the specified Sun StorEdge T3+ array partner group. It includes output from the following Sun StorEdge T3+ array commands:

- version
- sys list
- vol list
- vol stat
- port list
- port listmap

- Save Config - Updates the Sun StorEdge T3+ array snapshot file after reading the array configuration. This information is saved to be reused if needed.

- Modify Parameters - Modify a Sun StorEdge T3+ array's system parameters.

- Configure - Steps you through a series of submenus that enable you to reconfigure Sun StorEdge T3+ arrays. After successful update of the configuration, the information is saved to the snapshot file. Support RAID types include:

- RAID 1
- RAID 5
- RAID 1 and RAID 5

In the RAID 1/RAID 5 mixed RAID types, each Sun StorEdge T3+ array will have a RAID 1 device consisting of three physical drives and a RAID 5 device consisting of five physical drives, plus a spare.

- Restore - Restores the Sun StorEdge T3+ array configuration with the static saved configuration from the snapshot file. This is a function that may be needed in the event you lose a LUN or you must replace a Sun StorEdge T3+ array.

- Verify - Checks and verifies that the current Sun StorEdge T3+ array configuration is the same as the most recently-saved version of the configuration in the snapshot file.

- Display Busy - Displays the name of the Sun StorEdge T3+ arrays that are being configured or restored.

- Validate Password - Validates the T3 telnet password.

- Manage T3+ LUN Slicing -- Enables you to create and remove T3+ slices. The options in the submenus include:

- Create T3+ Lun Slice - This options enables you to create slices on T3+ volumes. You are presented with a listing of the available volumes. Once you make a selection you will enter the number, size (in 1 gb increments) and name of the slices you want to create.
- Remove T3+ Lun Slice - This option enables you to remove LUN slices that have been created on a T3+ volume.
- Display T3+ Lun Slice Info - Displays the current LUN configuration on the specified T3+.You may choose to display either slice information, LUN map information or LUN permission information.
- Enable T3+ Volume Slicing - This option allows you to set the appropriate T3+ system parameter to enable volume slicing on the specified T3+ Sun StorEdge array.

- Manage T3+ LUN Masking -- Enables you to create T3+ groups for specific WWNs and set LUN permissions. The options in the submenus include:

- Create T3+ Group - This option enables you to create a T3+ group, which can then be used to set/mask LUN permissions. After selecting a T3+ Sun StorEdge array, you must enter the WWN to be associated with the new group. You may also add an initial LUN into this group and set permissions on it.
- Remove T3+ Group - This option enables you to remove one or all groups on a T3+ Sun StorEdge array.
- Add to T3+ Group - Using this option you can add additional WWNs into an existing group.
- Delete from T3+ Group - Using this option you can delete WWNs from an existing group.
- Set T3+ LUN Permissions - This option allows you to set/mask LUN permissions to read-write (rw), read-only(ro) or none for an individual LUN or all LUNs on a specified Sun StorEdge T3+ array. You may set LUN permissions on an individual WWN or group basis.

See Also:

- 'Sun StorEdge network FC switch configuration
- 'Virtualization Engine configuration
- 'Sun StorEdge 3900 and 6900 series maintenance

[ manage.configure.conf_se:se_maintenance,t3_configure,switch_configure,ve_configure ]

Configure the Sun StorEdge Network FC Switch

Configure the Sun StorEdge Network FC Switch-8 and Switch-16 Switches |

The Sun StorEdge switch menu presents the following options:

- Display Config - Displays the specified switch's configuration, including the following:

- IP address configuration
- number of ports
- version information
- port status and type
- zones

- Verify - Verifies that the configuration of the specified switch matches the predefined static configuration for that switch, based on the cabinet type (Sun StorEdge 3900 series or Sun StorEdge 6900 series).

- Set Config - Configures the specified switch to a predefined static configuration based on cabinet type and location (top or bottom switch for Sun StorEdge 6900 series).

- Save Config - Saves the current configuration of the specified switch to a restorable map file.

- Restore Config - Restores the saved switch configuration from the map file.

- Download Firmware - Downloads and resets the flash code to the Sun StorEdge network FC switch-8 or switch-16 switch. This command can also be used to upgrade 1 Gbit switchs to 2 Gbit compatible firmware or the downgrade of the same by selecting the new alternate flash file at the prompt. Default flash file is based on number of ports and current switch revision. The flash files are located in the following directories:
  - /usr/opt/SUNWsmgr/flash (1Gbit switch)
  - /usr/opt/SUNWsmgr2/firmware/SANbox1 (2 Gbit compatible mode)
  - /usr/opt/SUNWsmgr2/firmware/SANbox2 (2 Gbit switch)

- Set Switch Port SL Mode - Sets/Unsets the switch port SL mode associated with the specified Sun StorEdge T3+ Array. If "on" is selected, it will set all ports in the corresponding zone on each switch to SL mode. If "off" is selected, it clears the SL mode and sets the ports back to the predefined configuration as defined below.

- Set Switch Port TL Mode - Sets/Unsets the switch port TL mode on the specified switch(es). If "on" is selected, it will set all ports in the specified port list on each switch to TL mode. If "off" is selected, it clears the TL mode and sets the ports back to the predefined configuration as defined below.
  NOTE : This feature is available for DAS configurations only (Sun StorEdge 3900 series systems) and is especially useful for SOC+ connections on Solaris 2.6.

- Set Switch Port Fabric Mode - Sets/Unsets the switch port fabric (F type) mode on the specified switch(es). If "on" is selected, it will set all ports in the specified port list on each switch to fabric mode. If "off" is selected, it clears the fabric mode and sets the ports back to the predefined configuration as defined below.
  NOTE: This feature is available for DAS configurations only (Sun StorEdge 3900 series systems) and is especially useful for full fabric configurations to set T3+ device-side ports to type F (fabric).

- Modify Switch Zones - Modifies the port list in each hard zone on a front-end switch. The user will be prompted for hard zone id(s) and then a port list for each. This command supports systems using the 2 Gbit (compatibility) switches including zone sets and zone names. The command also supports WWN zoning on 2 Gbit switches. Users can add or remove a single WWN without modifying the entire switch zone configuration.
  NOTE : This feature is available for DAS configurations only (Sun StorEdge 3900 series systems) and is especially useful for 4-node cluster support.

- Manage Password - This function prompts users for both a login ID and password. This command is necessary when the system is using the 2 Gbit (compatibility) switches.

See Also:

- 'Sun StorEdge T3 array configuration
- 'Virtualization Engine configuration
- 'Sun StorEdge 3900 and 6900 series maintenance

[ manage.configure.conf_se:se_maintenance,t3_configure,switch_configure,ve_configure ]

Configure the Virtualization Engine

Configure the Virtualization Engine | [ 'Top ]

The virtualization engine (VE) configuration menus present the following options:

- Manage Disk Pools

- Create Diskpools - Creates disk pools that map to physical LUNs on the specified Sun StorEdge T3+ array. These are the physical LUNs that can be used to create VLUNs.
- Remove Diskpools - Removes disk pools and all VLUNs in the disk pool for the specified Sun StorEdge T3+ array LUNs. This command is typically used when you are performing a reconfiguration of the Sun StorEdge T3+ array. The command is automatically called by modfiyt3config .

- Manage VLuns - Enables you to create and remove virtual LUNs

- Create VLuns - This option enables you to create VLUNs on either a single disk pool or on multiple disk pools with a single batch execution. You are presented with a listing of the available virtualization engine pairs. Once you make a selection you will enter the number and size (in 1 gb increments) of VLUNs you want to create. You may also choose to add the new VLUNs into zones as well.
- Remove VLUNs - This option enables you to remove VLUNs that have been created on the virtualization engine pairs.
- View Virtualization Engine Map - Displays the current saved configuration map of the specified virtualization engine.

- Manage Zones - Presents the following options:

- Create virtualization engine zones - This option enables you to create a single virtualization zone or multiple zones with a single batch execution. You are presented with a listing of the available virtualization engine pairs, initiators and WWNs and then asked to enter a zone and HBA alias name.
- Add components to virtualization engine zones - Using this option you can add additional VLUNs or HBAs to existing virtualization engine zone(s). You are presented with a listing of the available virtualization engine pairs and zones.
- Delete components from virtualization zones - This option enables you to remove VLUNs or HBAs from existing virtualization engine zone(s). You are presented with a listing of the available virtualization engine pairs and zones.
- Remove virtualization engine zones - You can remove the entire virtualization engine zone using this option

- Manage Config Files - Gives you the following options:

- View virtualization engine map - Displays the current configuration of the specified virtualization engine from either the map file or from polling live.
- Save virtualization engine map - Saves the current configuration of the specified virtualization engine.
- Restore virtualization engine map - Restores the current configuration of the specified virtualization engine.
- Verify virtualization engine map - Verifies that the live configuration of the specified virtualization engine matches the saved configuration.

- Manage Hosts - Manages the virtualization engine hosts

- View Map - Displays the current configuration of the specified virtualization engine.

- Managed slicd Daemon - Manage the virtualization engine daemon

- Set/Clear Password - Set or clear the virtualization engine password

See Also:

- 'Sun StorEdge T3 array configuration
- 'Sun StorEdge network FC switch configuration
- 'Sun StorEdge 3900 and 6900 series maintenance

[ manage.configure.conf_se:se_maintenance,t3_configure,switch_configure,ve_configure ]

Manage > Utilities > Continuous Volume Verify | [ Top ]
Storage Automated Diagnostic Environment
Continuous Volume Verify : Start | [ Help ]
This page is used to start volume verification on Sun T3 and Sun 6120 storage arrays. This option will execute volume verify continuously on all arrays at the selected rate. Volumes are verified one at a time on a rotation basis. 'Kill Verify' can be used to abort these operations on each array. The 'Device Summary' page displays each monitored array with information about 'vol verify'. The execution rate for the volume verification determines the impact on I/O access to the array. Selecting level 1 will take longer to verify the volume but will have little effect on I/O.
Start Volume Verify
|  | Kill Verify |  |  | Device Summary |
Warning: Using the 'fix' option on vol verify may fix parity on bad blocks. Consult your Service Representative for details.
Vol-Verify maintenance
Run 'vol verify' continuously: |
Run with 'fix' option: |
Start volVerify only in these time periods: |
Execution Rate: |
Default Array Password: |

[ GUI::VolVerify::run ]

Storage Automated Diagnostic Environment
Continuous Volume Verify : Kill | [ Help ]
This page is used to start volume verification on Sun T3 and Sun 6120 storage arrays. This option will execute volume verify continuously on all arrays at the selected rate. Volumes are verified one at a time on a rotation basis. 'Kill Verify' can be used to abort these operations on each array. The 'Device Summary' page displays each monitored array with information about 'vol verify'. The execution rate for the volume verification determines the impact on I/O access to the array. Selecting level 1 will take longer to verify the volume but will have little effect on I/O.
| Start Volume Verify |  |
Kill Verify
|  | Device Summary |
Kill All Vol-Verify processes on monitored devices
Status: | Done / Mon Apr 7 10:59:23 MDT 2003
Log: | [ Display Process-Kill Log ]

[ GUI::VolVerify::run ]

Storage Automated Diagnostic Environment
Continuous Volume Verify : Report | [ Help ]
This page is used to start volume verification on Sun T3 and Sun 6120 storage arrays. This option will execute volume verify continuously on all arrays at the selected rate. Volumes are verified one at a time on a rotation basis. 'Kill Verify' can be used to abort these operations on each array. The 'Device Summary' page displays each monitored array with information about 'vol verify'. The execution rate for the volume verification determines the impact on I/O access to the array. Selecting level 1 will take longer to verify the volume but will have little effect on I/O.
| Start Volume Verify |  |  | Kill Verify |  |
Device Summary
Vol-Verify Summary Report
Host | Device | Verify | Last Volume | Start | Status
--- | --- | --- | --- | --- | ---
diag230.site | diag210 / [IP_NO] | Y |  |  |
| diag208 / [IP_NO] | N |  |  |
| diag211 / [IP_NO] | N |  |  |
| diag103 / [IP_NO] | N |  |  |

[ GUI::VolVerify::run ]

Volume Verify |

This option will execute volume verify continuously on all arrays at the selected rate. Volumes are verified one at a time on a rotation basis. Events are generated when this operation fails.
This option applies only to T3 and 6120.
Volume verify can also be turned on or off on a device by device basis in General Maintenance -> Maintain Device. The 'Default Array Password' is used when there is no password entered in Administration -> General Maintenance -> Maintain Device for a specific array.
This option is not considered a diagnostic from StorADE point of view and does not impact monitoring coverage. Green and yellow disk led will be lit when this oparation is running.
Warning: Using the 'fix' option on vol verify may fix parity on bad blocks. This can sometimes hide corrupted data blocks.

Use 'Kill Verify' to kill 'vol verify' on the arrays that are monitored and where vol verify was started by Storage A.D.E.

The 'Device Summary' displays each monitored array with the following fields:

- Verify: Is the continuous 'vol-verify' option turned-on for this device.
- Last Volume: The last or current volume being verified.
- Start: Start date of the last 'vol-verify'.
- Status: The progress of vol-verify or the word 'Start' or 'KILL'.

[ manage.util.volverify:volverify ]

Report > General Reports > Traffic Report | [ Top ]
Storage Automated Diagnostic Environment
Traffic Report | [ Help ]
Summary:
Switch | IP | Port | Traffic (K)
diag192 | [IP_NO] | 2 | 954817.6
diag192 | [IP_NO] | 3 | 40001.1
diag192 | [IP_NO] | 4 | 986173.6
diag187 | [IP_NO] | 14 | 2993825.8
diag187 | [IP_NO] | 15 | 2990624.4
diag187 | [IP_NO] | 5 | 3489720.7
diag187 | [IP_NO] | 6 | 951178.8
diag187 | [IP_NO] | 7 | 39998.4
diag187 | [IP_NO] | 8 | 1792393.2
Total: | 14238733.6

[ GUI::Traffic::run ]

Traffic Report

Traffic Report |

Using the SAN Traffic Report, you can display the status of each port on every switch. SAN monitoring must be active and the Storage Automated Diagnostic Environment must have run at least once for port and switch traffic information to display.

See Also:

- 'FRU Reports

- 'Event Report
- 'Service Advisor
- 'Array Performance Report

[ report.general.fc_traffic:traffic_report ]

Report > General Reports > Fru Reports | [ Top ]
Storage Automated Diagnostic Environment
Fru Reports | [ Help ]
This function extract fru information from all existing instrumentation-reports both on master and slave agents and produce a flexible report that can be sorted and filtered in a variety of ways. This can be used to review fru information for a whole site. This report does not probe any device and can only be used after the agents ran at least once. Use [Run New Report] to regenerated the report. Use [Display Current Report] to display the last available report.
Report-Set Status
Report Status:
| Done / pid=20369
Select a report to display or Email | Select for Email
Detailed Fru Report | [ Display ] |
Fru Summary (Health Concerns) | [ Display ] |
Fru-Model Summary (by DeviceName) | [ Display ] |
Fru-Model Summary (by DeviceType) | [ Display ] |
Battery days left | [ Display ] |
Temperature Report | [ Display ] |
Temperature Summary (frus above UCL) | [ Display ] |
Email Selected Reports
Enter Email: |

[ GUI::FruReport::frus ]

Storage Automated Diagnostic Environment
Fru Reports | [ 2003-05-13 15:03:41 | Help ]
Fru-Model Summary (by DeviceName)
+ Name
Device
FruType
Vendor
Model
Revision
Count
3310-000034 | 3310 | disk | SEAGATE | ST336607LSUN36G | 0207 | 4
| 3310 | disk | SUN | StorEdge 3110 A | X106 | 1
DSQA2 | a5k | backplane | N/A | N/A | rev-03 | 3
| a5k | disk | SEAGATE | ST39103FCSUN9.0G | 114B | 22
| a5k | fan | N/A | N/A | rev-04 | 2
d2-013203 | d2 | disk | FUJITSU | MAN3367M-SUN36G | 1502 | 12
| d2 | esm_card | SUN | 540-5016-01 | 3034 | 1
| d2 | midplane | SUN | 3753049-01 | N/A | 1
diag103 | t3 | controller | SLR-MI | 375-0084-02-JJ11 | 0210/011800 | 1
| t3 | disk | SEAGATE | ST173404FSUN72G | A727 | 9
| t3 | loopcard | SLR-MI | 375-0085-01-G-G1 | 5.02 Flash | 2
| t3 | midplane | SLR-MI | 370-3990-01-E-F0 | 0000 | 1
| t3 | port | N/A | N/A |  | 2
| t3 | power | TECTROL-CAN | 300-1454-01(50) | 0000 | 2
| t3 | power.battery | N/A | N/A | N/A | 2
| t3 | unit | N/A | N/A |  | 2
diag111 | switch | switch | Qlogic | SANbox2-64 FC Switch | V[IP_NO]-0 | 1
diag140 | switch | switch | Qlogic | QLogic SANBox2 FC Switch | V[IP_NO]-0 | 1
diag141 | switch | switch | Qlogic | QLogic SANBox2 FC Switch | V[IP_NO]-0 | 1
diag187 | switch | switch | Qlogic | Qlogic-16 | 30300-30462-a03 | 1
diag192 | switch | switch | Qlogic | Qlogic-8 | 30200-30462-a03 | 1
diag208 | t3 | controller | 0301 | 501-5710-02(51) | 0200/020101 | 2
| t3 | disk | FUJITSU | MAN3735F SUN73G | 5E03 | 10
| t3 | disk | SEAGATE | ST318203FSUN18G | D94A | 8
| t3 | loopcard | SCI-SJ | 375-0085-01-e-e2 | 5.02 Flash | 4
| t3 | midplane | N/A | N/A |  | 1
| t3 | midplane | SCI-SJ | 370-3990-01-E-D0 | 0000 | 1
| t3 | port | N/A | N/A |  | 6
| t3 | power | N/A | N/A |  | 2
| t3 | power | TECTROL-CAN | 300-1454-01(50) | tony | 2
| t3 | power.battery | N/A | N/A | N/A | 4
| t3 | unit | N/A | N/A |  | 2
diag210 | 6120 | controller | 0x301 | 5405559 | 01 | 1
| 6120 | disk | N/A | N/A |  | 7
| 6120 | disk | SEAGATE | ST336752FSUN36G | A205 | 7
| 6120 | loopcard | 0x301 | 5405384 | 02 | 2
| 6120 | midplane | 0x301 | 5016338 | 01 | 1
| 6120 | port | N/A | N/A |  | 1
| 6120 | power | 0x3AD | 3001562 | 16 | 2
| 6120 | power.battery | 0x076 | 3704861 | 01 | 2
diag211 | t3 | controller | SCI-SJ | 375-0084-01-j-j6 | 0210/011800 | 2
| t3 | disk | SEAGATE | ST318203FSUN18G | D94A | 18
| t3 | loopcard | SCI-SJ | 375-0085-01-e-e2 | 5.02 Flash | 4
| t3 | midplane | SLR-MI | 370-3990-01-E-E1 | 0000 | 2
| t3 | port | N/A | N/A |  | 6
| t3 | power | TECTROL-CAN | 300-1454-01(50) | 0000 | 4
| t3 | power.battery | N/A | N/A | N/A | 4
| t3 | unit | N/A | N/A |  | 2
diag99 | switch | switch | Qlogic | Sun SANbox-8 | 3.03.00-04.02.33 | 1
tape-475b | tape | tape | STK | T9840B | N/A | 1

[ GUI::FruReport::summ1 ]

Storage Automated Diagnostic Environment
Fru Reports | [ 2003-05-13 15:03:42 | Help ]
Fru-Model Summary (by DeviceType)
+ Device
FruType
Vendor
Model
Revision
Count
3310 | disk | SEAGATE | ST336607LSUN36G | 0207 | 4
| disk | SUN | StorEdge 3110 A | X106 | 1
6120 | controller | 0x301 | 5405559 | 01 | 1
| disk | N/A | N/A |  | 7
| disk | SEAGATE | ST336752FSUN36G | A205 | 7
| loopcard | 0x301 | 5405384 | 02 | 2
| midplane | 0x301 | 5016338 | 01 | 1
| port | N/A | N/A |  | 1
| power | 0x3AD | 3001562 | 16 | 2
| power.battery | 0x076 | 3704861 | 01 | 2
a5k | backplane | N/A | N/A | rev-03 | 3
| disk | SEAGATE | ST39103FCSUN9.0G | 114B | 22
| fan | N/A | N/A | rev-04 | 2
d2 | disk | FUJITSU | MAN3367M-SUN36G | 1502 | 12
| esm_card | SUN | 540-5016-01 | 3034 | 1
| midplane | SUN | 3753049-01 | N/A | 1
switch | switch | Qlogic | QLogic SANBox2 FC Switch | V[IP_NO]-0 | 2
| switch | Qlogic | Qlogic-16 | 30300-30462-a03 | 1
| switch | Qlogic | Qlogic-8 | 30200-30462-a03 | 1
| switch | Qlogic | SANbox2-64 FC Switch | V[IP_NO]-0 | 1
| switch | Qlogic | Sun SANbox-8 | 3.03.00-04.02.33 | 1
t3 | controller | 0301 | 501-5710-02(51) | 0200/020101 | 2
| controller | SCI-SJ | 375-0084-01-j-j6 | 0210/011800 | 2
| controller | SLR-MI | 375-0084-02-JJ11 | 0210/011800 | 1
| disk | FUJITSU | MAN3735F SUN73G | 5E03 | 10
| disk | SEAGATE | ST173404FSUN72G | A727 | 9
| disk | SEAGATE | ST318203FSUN18G | D94A | 26
| loopcard | SCI-SJ | 375-0085-01-e-e2 | 5.02 Flash | 8
| loopcard | SLR-MI | 375-0085-01-G-G1 | 5.02 Flash | 2
| midplane | N/A | N/A |  | 1
| midplane | SCI-SJ | 370-3990-01-E-D0 | 0000 | 1
| midplane | SLR-MI | 370-3990-01-E-E1 | 0000 | 2
| midplane | SLR-MI | 370-3990-01-E-F0 | 0000 | 1
| port | N/A | N/A |  | 14
| power | N/A | N/A |  | 2
| power | TECTROL-CAN | 300-1454-01(50) | 0000 | 6
| power | TECTROL-CAN | 300-1454-01(50) | tony | 2
| power.battery | N/A | N/A | N/A | 10
| unit | N/A | N/A |  | 6
tape | tape | STK | T9840B | N/A | 1
Total: | 181

[ GUI::FruReport::summ2 ]

FRU Report |

### To Generate a Customized FRU Report

From the General Reports menu, click FRU Reports.

1. Click New Report.
2. Enter an email address in the Email text field.
3. Select one report and click Display.

- Detailed Report--displays a detailed list of FRU identifiers.
  From the detailed FRU report, you can filter the FRU report using [device type] and [FRU type] filters.

FRU Identifier | Description
--- | ---
Name | Host name
Device | Device type
FruType | Component FRU ( for example, controller, disk, loopcard)
Fru | FRU identifier number
Vendor | FRU vendor (for example, Seagate for disks)
Model | Model number
Serial | Serial number
Revision | SUNWstads package
Status | Current device status

4. Fru Summary (Health Concerns) This report only displays the frus that are not in a normal state.
5. Fru-Model Summary (by Device Name)
   Displays the FRU type, vendor name, model number, revision number, and number of FRUs per FRU type for a selected device name (for example, sp-87-t400).

6. Fru-Model Summary (by DeviceType)
   Displays the FRU type, vendor name, model number, revision number, and number of FRUs per FRU type for a selected device (for example, 6120).
7. Battery days left This reports displays all batteries sorted by the number of days before the battery needs to be replaces. This report works only on Sun T3 and Sun 6120 at the moment.
8. Temperature Report This report displays the fru temperature distribution. It can be used to isolate hot frus. The Lower and Upper Control Limit is shown to help isolation. Lower and Upper Control Limit is defined as 3 standatd deviations from the median.
9. Temperature Suppary (frus above UCL) This is a summary of the Temperature report displaying only hot frus as defined by the UCL.

See Also:

- 'Traffic Report

- 'Event Report
- 'Service Advisor
- 'Array Performance Report

[ report.general.fru_report:fru_reports ]

Report > General Reports > FruReport History | [ Top ]
Storage Automated Diagnostic Environment
FruReport History | [ Help ]
This function extract fru information from all existing instrumentation-reports both on master and slave agents and produce a flexible report that can be sorted and filtered in a variety of ways. This can be used to review fru information for a whole site. This report does not probe any device and can only be used after the agents ran at least once. Use [Run New Report] to regenerated the report. Use [Display Current Report] to display the last available report.
Fru Report History
Creation Date | Select
No Archived report available!

[ GUI::FruReport::history ]

FRU Report |

### To Generate a Customized FRU Report

From the General Reports menu, click FRU Reports.

1. Click New Report.
2. Enter an email address in the Email text field.
3. Select one report and click Display.

- Detailed Report--displays a detailed list of FRU identifiers.
  From the detailed FRU report, you can filter the FRU report using [device type] and [FRU type] filters.

FRU Identifier | Description
--- | ---
Name | Host name
Device | Device type
FruType | Component FRU ( for example, controller, disk, loopcard)
Fru | FRU identifier number
Vendor | FRU vendor (for example, Seagate for disks)
Model | Model number
Serial | Serial number
Revision | SUNWstads package
Status | Current device status

4. Fru Summary (Health Concerns) This report only displays the frus that are not in a normal state.
5. Fru-Model Summary (by Device Name)
   Displays the FRU type, vendor name, model number, revision number, and number of FRUs per FRU type for a selected device name (for example, sp-87-t400).

6. Fru-Model Summary (by DeviceType)
   Displays the FRU type, vendor name, model number, revision number, and number of FRUs per FRU type for a selected device (for example, 6120).
7. Battery days left This reports displays all batteries sorted by the number of days before the battery needs to be replaces. This report works only on Sun T3 and Sun 6120 at the moment.
8. Temperature Report This report displays the fru temperature distribution. It can be used to isolate hot frus. The Lower and Upper Control Limit is shown to help isolation. Lower and Upper Control Limit is defined as 3 standatd deviations from the median.
9. Temperature Suppary (frus above UCL) This is a summary of the Temperature report displaying only hot frus as defined by the UCL.

See Also:

- 'Traffic Report

- 'Event Report
- 'Service Advisor
- 'Array Performance Report

[ report.general.fru_hist:fru_reports ]

Report > General Reports > Exception Report | [ Top ]
Storage Automated Diagnostic Environment
Exception Report | [ Help ]
Run and display exception reports. Exceptions are defined in System/exception.conf (T3 only)
Report-Set Status
Last Run: |
Report Status:
| Not running
Select a report to display or Email | Select for Email
T3 Configuration Exception |  |
Email Selected Reports
Enter Email: |

[ GUI::ExceptionReport::list ]

Exception Report |

This function generate an exception report against devices, frus and volumes that are not configured correctly based on a pre-defined list of normal values.
The normal values are stored in System/exception.conf and can be adjusted by the customer on a case by case basis in DATA/exception.conf. When the report runs, the values in DATA/exception.conf will take precedence over the ones in System/exception.conf.
Example: To change the default Cache Mode for Sun T3 from 'auto' to 'off', simply add the system.sysCacheMode entry from the file System/exception.conf into the file DATA/exception.conf and change the field 'value' from 'auto' to 'off'. The file DATA/exception.conf should look as follow:

    [t3]
    id=system.sysCacheMode
    name=Cache Mode
    value=off

Entries in DATA/exception.conf should be adjusted until the exception report is very short and report only exceptions to the standard site configuration.

[ report.general.ex:exception_reports ]

Report > General Reports > Event Reports | [ Top ]
Storage Automated Diagnostic Environment
Event Reports | [ Help ]
This function reads all events in the DATA directory and produce a flexible report that can be sorted and filtered in a variety of ways. This can be used to review event distribution by month, week etc.. Use [Run New Report] to regenerated the report.
Create New Report
Actionable Events Only: |
Last Run: | 2003-04-01 11:34:59
Select a report to display or Email | Select for Email
Event Report (by DeviceType / Month) | [ Display ] |
Event Report (by DeviceType / Week) | [ Display ] |
Event Report (by DeviceType / DayOfWeek) | [ Display ] |
Email Selected Reports
Enter Email: |

[ GUI::EventReport::events ]

Storage Automated Diagnostic Environment
Event Reports | [ 2003-05-13 15:03:42 | Help ]
Event Report by DeviceType/ Year-Month (Actionable Events Only)
+ Device-Type
Year-Month
Info
Warning
Error
Down
StorEdge 6120 | 2003-04 |  |  | 4 |
Sun Server | 2003-04 |  | 1 | 1 |
Sun T3 | 2003-04 |  | 2 | 7 |
Total: | 0 | 3 | 12 | 0
Page: 1 of 1 |

[ GUI::EventReport::eventsYmd ]

Event Reports

Event Reports |

### To Generate a Customized Event Report

1. From the General Reports menu, click Event Reports.
2. Click New Report.
3. Click the Actionable Only checkbox if you want to display only events that are actionable.
4. Enter an email address in the Email text field.
5. Select one report and click Display.
6. Event Report (by DeviceType / Month)--displays a summary of events sorted by:

- Device-Type
- Year-Month (for example, 2002-11)
- Info--Click the number link in the Info column to launch a pop-up window with a summary of information available for that device. The summary includes the date, event type, topic, and description.
- Severity level--Warning, Error, Down--click the number think in a severity column to launch a pop-up window with a summary that particular severity level. The summary includes the date, event type, topic, description, and severity.

Event Report (by DeviceType / Week)--displays a summary of events sorted by:

- Device-Type
- Year-Week (for example, 2002-11-03)
- Info--Click the number link in the Info column to launch a pop-up window with a summary of information available for that device. The summary includes the date, event type, topic, and description.
- Severity level (Warning, Error, Down)--click the number think in a severity column to launch a pop-up window with a summary that particular severity level. The summary includes the date, event type, topic, description, and severity.

Event Report (by DayOfWeek)--displays a summary of events sorted by:

- Device-Type
- DayOfWeek (for example, 1 Mon)
- Info--Click the number link in the Info column to launch a pop-up window with a summary of information available for that device. The summary includes the date, event type, topic, and description.
- Severity level (Warning, Error, Down)--click the number think in a severity column to launch a pop-up window with a summary that particular severity level. The summary includes the date, event type, topic, description, and severity.

See Also:

- 'Traffic Report

- 'FRU Reports
- 'Service Advisor
- 'Array Performance Report

[ report.general.event_report:event_reports ]

Report > General Reports > Device Health | [ Top ]
Storage Automated Diagnostic Environment
Device Health Summary | [ Help ]
Summary Report (Health Only) | [ Health Only | Detail ]
+ Type
Name
Health
IP
Key
Monitoring
6120 | diag210 |  | [IP_NO] | 0x301.5016338.400386 | On
Switch(es): 7, Storage(s): 8, Host(s): 0 |

[ GUI::DeviceReport::run ]

General Reports

General Reports |

When viewing reports, The titles of the columns can be selected to sort the report on that column. Click the same colums again to alternate the sorting. Ascending is marked with a '+', descending with a '-' before the name of the field.
A detailed and a summary mode is also often available.

[ report.general.dev_report2:gen_report ]

Report > General Reports > Device Health Summary | [ Top ]
Storage Automated Diagnostic Environment
Device Health Summary | [ Help ]
| [ Health Only | Detail ]
+ Type
Name
Health
IP
Key
Monitoring
3310 | 3310-000034 |  | [IP_NO] | 206000c0ff000034 | On
6120 | diag210 |  | [IP_NO] | 0x301.5016338.400386 | On
| 2005-04-01 07:44:44 The state of 'volume.u1vol2.volCacheMode' on diag206 is 'disabled'
McDATA | diag183 |  | [IP_NO] | 1000080088a0cade | On
Switch1 | diag187 |  | [IP_NO] | 100000c0dd006fad | On
Switch1 | diag192 |  | [IP_NO] | 100000c0dd005732 | On
Switch1 | diag99 |  | [IP_NO] | 100000c0dd00cbb4 | On
Switch2 | diag140 |  | [IP_NO] | 100000c0dd00c680 | On
Switch2 | diag141 |  | [IP_NO] | 100000c0dd00bfa4 | On
Switch2 | diag111 |  | [IP_NO] | 100000c0dd01a18d | On
a5k | DSQA2 |  |  | 5080020000081838 | On
d2 | 013203 |  |  | 013203 | On
host | diag230.site |  | [IP_NO] | diag230.site | On
host | jeannot.site |  | [IP_NO] | jeannot.site | On
host | crashme41.site |  | [IP_NO] | crashme41.site | On
t3 | diag211 |  | [IP_NO] | slr-mi.370-3990-01-e-e1.002776 | On
t3 | diag103 |  | [IP_NO] | slr-mi.370-3990-01-e-f0.027877 | On
t3b | diag208 |  | [IP_NO] | sci-sj.370-3990-01-e-d0.002487 | On
tape | tape-475b |  |  | 500104f0004b475b | On
Switch(es): 7, Storage(s): 8, Host(s): 3 |

[ GUI::DeviceReport::run ]

General Reports

General Reports |

When viewing reports, The titles of the columns can be selected to sort the report on that column. Click the same colums again to alternate the sorting. Ascending is marked with a '+', descending with a '-' before the name of the field.
A detailed and a summary mode is also often available.

[ report.general.dev_report:gen_report ]

Report > General Reports > Array Performance | [ Top ]
Storage Automated Diagnostic Environment
Array Performance : I/O Summary per Second | [ Help ]
Report: Array: | 2003-05-13 15:03:42
| Volume |  |  |

[ GUI::Perf::array ]

Array Performance Report

Array Performance Report |

The Array Performance Report tracks and reports the I/O of specified arrays. Performance reports are available after the agent ran at least twice. To improve the accuracy of the Real-Time option, the program 'sbin/perf' can be used in the background. Once started, the 'perf' program will runs continuously and probe arrays at fixed interval.

To Generate an Array Performance Report

1. From the General Reports menu, click Array Performance.

The Array Performance Report displays an I/O Summary sorted by:

- I/O Summary Report:

- I/O Hourly Summary
- I/O Daily Summary
- Real Time (I/O that is occurring now)

- Array

- An individual array
- Combined arrays

2. Click GO to generate the customized Array Performance report.

See Also:

- 'Traffic Report

- 'Event Report
- 'Service Advisor
- 'Array Performance Report

[ report.general.parray:array_report ]

Report > System Reports > Agent Stats | [ Top ]
Calling jeannot.site.. Calling crashme41.site..
Agent Stats | [ Help ]
This report displays, for each agent, the average time required to run the main modules. It can help find bottlenecks in the agent functions. This information is generated and accumulated on every run of the agents on each host.
Agent Execution time by Host / Module (Mins:Secs) | [ Clear Statistics ]
Host | Device | #Runs | Minimum | Maximums | Average
diag230.site
| Sun 3310 | 181 | 00:02 | 00:10 | 00:02
| StorEdge 6120 | 200 | 00:02 | 00:33 | 00:05
| Sun A3500FC | 33 | 00:01 | 00:01 |
| Sun A5000 | 181 | 00:01 | 02:01 | 00:03
| Sun Server | 181 | 00:01 | 09:09 | 00:12
| McData switch | 181 | 00:04 | 00:07 | 00:04
| LogFile | 203 | 00:01 | 00:02 |
| Sun Switch | 181 | 00:01 | 00:04 | 00:02
| Sun Switch2 | 181 | 01:06 | 01:54 | 01:10
| Sun T3 | 182 | 00:27 | 09:31 | 01:45
| T3MESSAGEAgent | 201 | 00:01 | 00:02 |
| FC-Tape | 181 | 00:01 | 02:49 | 00:02
jeannot.site
| Sun 3310 | 4003 | 00:01 | 00:01 |
| Sun 3510 | 4003 | 00:01 | 00:01 |
| StorEdge 6120 | 4003 | 00:01 | 00:01 |
| Sun A3500FC | 4003 | 00:01 | 00:01 |
| Sun A5000 | 4003 | 00:01 | 00:01 |
| Brocade switch | 4003 | 00:01 | 00:01 |
| DATAHOST | 4003 | 00:01 | 00:01 |
| Sun Server | 4003 | 00:01 | 00:15 |
| INTERNAL | 4003 | 00:01 | 00:01 |
| McData switch | 4003 | 00:01 | 00:01 |
| LogFile | 4003 | 00:01 | 00:01 |
| Sun 3900/6900 | 4003 | 00:01 | 00:01 |
| Sun 6320 | 4003 | 00:01 | 00:01 |
| Sun Switch | 4003 | 00:01 | 00:01 |
| Sun Switch2 | 4003 | 00:01 | 00:01 |
| Sun T3 | 4003 | 00:11 | 01:58 | 01:08
| T3MESSAGEAgent | 4003 | 00:01 | 00:01 |
| FC-Tape | 4003 | 00:01 | 00:01 |
| Sun V880 Disk | 4003 | 00:01 | 00:01 |
| Vicom VE | 4003 | 00:01 | 00:01 |
All Hosts
| Sun 3310 | 4184 |  | 00:10 |
| Sun 3510 | 4003 |  | 00:01 |
| StorEdge 6120 | 4203 |  | 00:33 |
| Sun A3500FC | 4036 |  | 00:01 |
| Sun A5000 | 4184 |  | 02:01 |
| Brocade switch | 4003 |  | 00:01 |
| DATAHOST | 4003 |  | 00:01 |
| Sun Server | 4184 |  | 09:09 |
| INTERNAL | 4003 |  | 00:01 |
| McData switch | 4184 |  | 00:07 |
| LogFile | 4206 |  | 00:02 |
| Sun 3900/6900 | 4003 |  | 00:01 |
| Sun 6320 | 4003 |  | 00:01 |
| Sun Switch | 4184 |  | 00:04 |
| Sun Switch2 | 4184 |  | 01:54 | 00:03
| Sun T3 | 4185 |  | 09:31 | 01:09
| T3MESSAGEAgent | 4204 |  | 00:02 |
| FC-Tape | 4184 |  | 02:49 |
| Sun V880 Disk | 4003 |  | 00:01 |
| Vicom VE | 4003 |  | 00:01 |

[ GUI::Stats::agent ]

Agent Statistics

Agent Statistics |

Using the Agent Stats functionality, you can determine the average time required to run the modules. The information is generated on every run of Storage Automated Diagnostic Environment's host.

To Check Storage Automated Diagnostic Environment Statistics

1. Click Agent Stats in the System Reports window.
2. Click an existing host.

The execution time for each agent, measured in minutes and seconds, is displayed.

See Also:

- 'Thresholds

- 'Switch Graph
- 'Switch Data
- 'Device Policies
- 'Service Advisor

[ report.system.agent_stats:agent_stats ]

Report > System Reports > Email/Events Maximums | [ Top ]
Storage Automated Diagnostic Environment
Email/Events Maximums | [ Help ]
This page displays a database used to keep track of the number of emails/events sent in the last 8 hours per device-component.
Events Maximums (Max=8)
Device ID | User | Name | Component/Topic | Last Events | Events(s) not sent
--- | --- | --- | --- | --- | ---
No device reached the maximum yet!
Email Maximums (Max=6)
Device ID | User | Name | Component/Topic | Last Email | Email(s) not sent
--- | --- | --- | --- | --- | ---
No device reached the maximum yet!

[ GUI::Stats::email ]

Event Filters |

This page displays a database used to keep track of the number of emails/events sent in the last 8 hours per device-component.
The 'email' maximum can be adjusted in Admin->General_Maintenance->Config-Options.
The 'event' maximum cannot be adjusted and is always 8.
After 8 events are generated about the same component of the same device, events are counted using this database but are not sent anymore. The date-time of the last event generated is also kept in this database.
The same logic applies to email but the maximum cannot be adjusted.
Actionable and non-actionable events are accumulated separately to avoid the problem of never sending an actionable event against a certain device because 8 non-actionable events were already sent against that same device (thus sending nothing at all to SRS who only receives actionable events).
Clearing the database with [Clear Email maximums] or [Clear Events maximums] will reset all counters and events/email generation will start again.

[ report.system.email_stats:email_stats ]

Report > System Reports > Thresholds List | [ Top ]
Thresholds List | [ Help ]
This page lists all threshold rules. The 'Frequency' is the number of alerts/hours required to generate a new message/email. The 'Quiet' value refers to the quiet time in between messages, used to avoid sending too many emails. Text in blue gives information about last message date or about the current number of alerts found against a specific threshold key. This text will appear only after Storage Automated Diagnostic Environment ran for a while.
[ Reset Thresholds ]
Thresholds
Name | Frequency | Quiet | Type | Description
driver
driver.SF_OFFLINE | 10 | / 24hours | 1hours | Warning | socal/ifp Offline
driver.SF_OFFLALERT | 15 | / 24hours | 1hours | Error | socal/ifp Offline
driver.SCSI_TRAN_FAILED | 10 | / 4hours | 1hours | Warning | SCSI transport failed
driver.SCSI_ASC | 10 | / 4hours | 1hours | Warning | scsi
driver.SCSI_TR_READ | 10 | / 4hours | 1hours | Warning | scsi READ
driver.SCSI_TR_WRITE | 10 | / 4hours | 1hours | Warning | scsi WRITE
driver.SSD_WARN | 5 | / 24hours | 1hours | Warning | SSD Warning
driver.SSD_ALERT | 20 | / 24hours | 1hours | Error | SSD Alert
driver.PFA | 1 | / 24hours | 1hours | Error | Predictive Failure
driver.SF_CRC_WARN | 10 | / 24hours | 1hours | Warning | CRC Warning
sf0: | Received 2 since 2003-04-02 14:50:00
driver.SF_CRC_ALERT | 15 | / 24hours | 1hours | Error | CRC Alert
sf0: | Received 2 since 2003-04-02 14:50:00
driver.SFOFFTOWARN | 5 | / 24hours | 1hours | Warning | Offline Timeouts
driver.SF_DMA_WARN | 1 | / 24hours | 1hours | Warning | SF DMA Warning
driver.SF_RESET | 10 | / 24hours | 1hours | Warning | SF Reset
driver.ELS_RETRY | 10 | / 24hours | 1hours | Warning | ESL retries
driver.SF_RETRY | 10 | / 24hours | 1hours | Warning | SF Retries
driver.TOELS | 10 | / 24hours | 1hours | Warning | ELS Timeouts
driver.SFTOELS | 10 | / 24hours | 1hours | Warning | SFTOELS Timeouts
driver.DDOFFL | 10 | / 24hours | 1hours | Warning | Offlines
driver.LOOP_OFFLINE | 1 | / 5mins | 1hours | Error | Loop Offline
driver.LOOP_ONLINE | 1 | / 5mins | 1hours | Error | Loop Online
driver.QLC_LOOP_OFFLINE | 1 | / 5mins | 1hours | Error | Loop Offline
driver.QLC_LOOP_ONLINE | 1 | / 5mins | 1hours | Error | Loop Online
driver.VM_SF_OFFLINE | 10 | / 24hours | 1hours | Warning | socal/ifp Offline
driver.VM_SF_OFFLALERT | 15 | / 24hours | 1hours | Error | socal/ifp Offline
driver.VM_SCSI_TRAN_FAILED | 10 | / 4hours | 1hours | Warning | SCSI transport failed
driver.VM_SCSI_ASC | 10 | / 4hours | 1hours | Warning | scsi
driver.VM_SCSI_TR_READ | 10 | / 4hours | 1hours | Warning | scsi READ
driver.VM_SCSI_TR_WRITE | 10 | / 4hours | 1hours | Warning | scsi WRITE
driver.VM_SSD_WARN | 100 | / 24hours | 1hours | Warning | SSD Warning
driver.VM_SSD_ALERT | 1 | / 24hours | 1hours | Error | SSD Alert
driver.VM_PFA | 1 | / 24hours | 1hours | Error | Predictive Failure
driver.VM_SF_CRC_WARN | 100 | / 24hours | 1hours | Warning | CRC Warning
driver.VM_SF_CRC_ALERT | 1 | / 24hours | 1hours | Error | CRC Alert
driver.VM_SFOFFTOWARN | 5 | / 24hours | 1hours | Warning | Offline Timeouts
driver.VM_SF_DMA_WARN | 1 | / 24hours | 1hours | Warning | SF DMA Warning
driver.VM_SF_RESET | 1 | / 24hours | 1hours | Warning | SF Reset
driver.VM_ELS_RETRY | 1 | / 24hours | 1hours | Warning | ESL retries
driver.VM_SF_RETRY | 1 | / 24hours | 1hours | Warning | SF Retries
driver.VM_TOELS | 1 | / 24hours | 1hours | Warning | ELS Timeouts
driver.VM_SFTOELS | 1 | / 24hours | 1hours | Warning | SFTOELS Timeouts
driver.VM_DDOFFL | 1 | / 24hours | 1hours | Warning | Offlines
driver.VM_LOOP_OFFLINE | 2 | / 5mins | 1hours | Error | Loop Offline
driver.VM_LOOP_ONLINE | 2 | / 5mins | 1hours | Error | Loop Online
a3500
a3500.CTRL_FIRM | 1 | / 24hours | 24hours | Warning | Controller firmware version error
vicom
vicom.crc | 200 | / 50mins | 10mins | Error | CRC
vicom.itw | 200 | / 50mins | 10mins | Error | Invalid Transmit words
vicom.link | 200 | / 50mins | 10mins | Error | Link fails
vicom.proto | 200 | / 50mins | 10mins | Error |

Note: The complete report can be seen using the StorA.D.E. GUI.

[ GUI::Thresholds::th ]

Thresholds

Thresholds |

The Thresholds window displays the thresholds that are used to monitor entries related to I/O interfaces in the /var/adm/messages file.

- Frequency is the number of alerts and hours required to generate a new message.
- Quiet is the quiet time in between messages, which is used to avoid sending too many messages at once.

See Also:

- 'Agent Statistics

- 'Switch Graph
- 'Switch Data
- 'Device Policies
- 'Service Advisor

[ report.system.thresholds:thresholds ]

Report > System Reports > Switch Data | [ Top ]
Storage Automated Diagnostic Environment
Switch Data | [ Help ]
Select a Switch to see the values of all 6 Fibre Channel Counters. Use [Set-Baseline] to reset the counters (software reset only). Use [Total] to go back to the actual values. When [Set-Baseline] is selected , the report will display the starting date/time and will display in bold any increase since that moment (10/100).
Select Switch: |
Nothing selected!

[ GUI::SWITCHUtil::fc_data ]

Switch Data

Switch Data |

Use the Switch Data functionality to view the values of Fibre Channel counters in a report format.

1. Click Switch Data in the General Reports window.

2. Select a switch from the Select Switch pull-down menu and click Display.

   After you have set the Set-Baseline field, the Switch FC Data report will display counter increments and the start time and the duration of the baseline.

3. Click Total to erase the values saved by Set-Baseline and to display the total Fibre Channel counters.

See Also:

- 'Agent Statistics

- 'Thresholds
- 'Switch Graph
- 'Device Policies
- 'Service Advisor

[ report.system.switch_data:switch_data ]

Report > System Reports > Event/Severity Mapping | [ Top ]
Storage Automated Diagnostic Environment
Event/Severity Mapping | [ Help ]
This report shows all the attributes that the agents are looking for when monitoring devices along with the severity of the events generated. This section only applies to Alarm and StateChange Events, use the Event Advisor to review other events. Severities are: Notice => Warning/NonActionable => Error/NonActionable => Warning/Actionable => Error/Actionable => Critical/Down
[ Summary | Detail ]
Device | Attribute Name | Value | Severity | Actionable
+A5k | Sun A5000
a5k | backplane.status | Failed | Error | Yes
|  | OK | Notice | No
| disk.status | OK-NotInstalled | Error | Yes
|  | OK-NotInstalled (FIRST_REPORT) | Notice | No
|  | OK-On | Notice | No
| fan.status | NotInstalled | Warning | No
|  | NotInstalled (FIRST_REPORT) | Notice | No
|  | OK | Notice | No
|  | non_critical_failure | Warning | No
| gbic.status | Failed | Error | Yes
|  | Not Installed | Warning | No
|  | Not Installed (FIRST_REPORT) | Notice | No
|  | OK | Notice | No
| interface_board.status | Failed | Error | Yes
|  | Not Installed | Warning | No
|  | OK | Notice | No
| mpx.state | OFFLINE | Error | Yes
|  | ONLINE | Notice | No
| power.status | Failed | Error | Yes
|  | Not Installed | Warning | No
|  | OK | Notice | No
| status | OK | Notice | No

[ GUI::Policy::list ]

Device Policies

Device Policies |

Use the Device Policies report to display every device attribute the agents search for when monitoring the devices.

- The Device Policies Summary report displays the monitored devices on which you can click to gather policy details.

- The Device Policies Detail report displays the severity of the generated event, such as Error, Warning, and Notice, and whether or not the event is actionable (Y/N).

For more detailed information about events and recommended action, refer to 'Service Advisor

See Also:

- 'Agent Statistics
- 'Thresholds
- 'Switch Graph
- 'Switch Data

[ report.system.policy:device_policies,event_mapping ]

Event and Severity Mapping

Event and Severity Mapping |

Use the Event and Severity Mapping Report to display every device attribute the agents search for when monitoring the devices.

- The Event and Severity Mapping Report displays the monitored devices on which you can click to gather policy details.

- The Event and Severity Mapping Report displays the severity of the generated event, such as Error, Warning, and Notice, and whether or not the event is actionable (Y/N).

For more detailed information about events and recommended action, refer to 'Service Advisor

See Also:

- 'Agent Statistics
- 'Thresholds
- 'Switch Graph
- 'Switch Data

[ report.system.policy:device_policies,event_mapping ]

Report > Service Advisor > Event Advisor | [ Top ]
Storage Automated Diagnostic Environment
StorADE 2 Event Advisor | [ Help ]
Select a Category/Component/EventType and type [GO] to limit the report. Click on the Columns headers to change the sort. Check [ReportFormat] to display a Report format. Click Info/Action to Review.
Search: |  | Category: |  | Report Format
Component: |  | EventType: |  |
+ Cat
| Code |
Comp.
EventType
Sev.
Act.
| Description
a5k | 3.5.3 | backplane | AlarmEvent- | Warning | Y | [ Info/Action ]
a5k | 3.5.4 | backplane.fan | AlarmEvent- | Error | Y | [ Info/Action ]
a5k | 3.5.13 | disk | AlarmEvent- | Warning | Y |
a5k | 3.5.22 | interface.gbic | AlarmEvent- | Error | Y |
a5k | 3.5.23 | interface.iboard | AlarmEvent- | Error | Y |
a5k | 3.10.16 | enclosure | AuditEvent | Notice |  | [ Info ]
a5k | 3.11.21 | ib | Comm_Established | Notice |  |
a5k | 3.12.21 | ib | Comm_LostEvent | Err/Critical | Y | [ Info/Action ]
a5k | 3.34.71 | aggregate | DeviceLostEvent | Err/Critical | Y | [ Info ]
a5k | 3.13.303 | a5ksestest | DiagnosticTest- | Error |  |
a5k | 3.13.304 | a5ktest | DiagnosticTest- | Error |  |
a5k | 3.14.16 | enclosure | DiscoveryEvent | Notice |  | [ Info ]
a5k | 3.40.13 | disk | ComponentInsert | Notice |  |
a5k | 3.19.16 | enclosure | LocationChange | Notice |  |
a5k | 3.41.13 | disk | ComponentRemove | Error | Y | [ Info/Action ]
a5k | 3.25.13 | disk | StateChange+ | Notice |  |
a5k | 3.25.23 | interface.iboard | StateChange+ | Notice |  |
a5k | 3.25.37 | power | StateChange+ | Notice |  |
a5k | 3.26.13 | disk | StateChange- | Error | Y | [ Info/Action ]
a5k | 3.26.23 | interface.iboard | StateChange- | Error | Y | [ Info/Action ]
a5k | 3.26.37 | power | StateChange- | Error | Y | [ Info/Action ]
a5k | 3.32.15 | driver | logEvent | Warning |  |
Page: 1 of 1 |
21 Events Sev: Severity of the event (Warning -> Error -> Down) Action: This event is Actionable and will be sent to RSS/SRS. SubComp: SubComponent

[ GUI::Grid::Events ]

Service Advisor

Service Advisor |

The Service Advisor shows all the actionable and non-actionable events the Storage Automated Diagnostic Environment generates. It enables you to customize the event grid by selecting device type, FRU-level components, event type, and the type of output (report, grid, or .pdf format).

In all cases, the following information is displayed:

- Category (device type)
- Component (FRU-level)
- Event Type
- Severity Level

- green--an error has occurred
- yellow--A serious error has occurred.
- red--A serious error has occurred that requires your immediate attention.
- down--A fatal, nonrecoverable error has occurred and the device is offline or unreachable.

- Diagnostic information and recommended action, if applicable.

1. You can view the events at a device-type level by selecting from the Category menu.
2. Select a component to isolate events to component level (for example, `backplane'). `All' is the default.
3. Select an event type to narrow your event list. `All' is the default.
4. Select the ReportFormat checkbox to view your events in a detailed report format.
5. To obtain more information, click the [Info/Action] link from the Description field on the Event Advisor. A pop-up menu displays the information for that event and the action recommended for problem resolution.

The Storage Automated Diagnostic Environment Event Advisor is intended to be used interactively, but it is also printable. To see all details about each event, run the Event Advisor with the ReportFormat checkbox enabled.

If you do not run the Event Advisor with the ReportFormat checkbox enabled, you must click the [Info/Action] details link, one event at a time.

See Also:

- 'Agent Statistics

- 'Thresholds
- 'Switch Graph
- 'Switch Data
- 'Device Policies

[ report.service.grid:event_advisor ]

No help file available for this page: report.service.grid_pdf

Report > Service Advisor > Asc/ Ascq | [ Top ]
Storage Automated Diagnostic Environment
Asc/ Ascq | [ Help ]
Additional Sense Data
Additional Sense Key Info
ASC
ASCQ
Description
Applies to
+ Group
00 | 17 | CLEANING REQUESTED | DTLWRSOMAEBK | A
01 | 00 | NO INDEX/SECTOR SIGNAL | DWOBK | D
02 | 00 | NO SEEK COMPLETE | DWROMBK | D
03 | 00 | PERIPHERAL DEVICE WRITE FAULT | DTLWSOBK | D
00 | 01 | FILEMARK DETECTED | T | T
00 | 02 | END-OF-PARTITION/MEDIUM DETECTED | TS | T
00 | 03 | SETMARK DETECTED | T | T
00 | 04 | BEGINNING-OF-PARTITION/MEDIUM DETECTED | TS | T
00 | 05 | END-OF-DATA DETECTED | TLS | T
00 | 18 | ERASE OPERATION IN PROGRESS | T | T
00 | 19 | LOCATE OPERATION IN PROGRESS | T | T
00 | 1A | REWIND OPERATION IN PROGRESS | T | T
00 | 1B | SET CAPACITY OPERATION IN PROGRESS | T | T
00 | 1C | VERIFY OPERATION IN PROGRESS | T | T
00 | 00 | NO ADDITIONAL SENSE INFORMATION |  | Z
00 | 06 | I/O PROCESS TERMINATED |  | Z
00 | 11 | AUDIO PLAY OPERATION IN PROGRESS | R | Z
00 | 12 | AUDIO PLAY OPERATION PAUSED | R | Z
00 | 13 | AUDIO PLAY OPERATION SUCCESSFULLY COMPLETED | R | Z
00 | 14 | AUDIO PLAY OPERATION STOPPED DUE TO ERROR | R | Z
00 | 15 | NO CURRENT AUDIO STATUS TO RETURN | R | Z
00 | 16 | OPERATION IN PROGRESS |  | Z
Note: The complete report can be seen using the StorA.D.E. GUI.
Page: 1 of 1
Applies to
O | OPTICAL MEMORY DEVICE (SBC-2)
P | PROCESSOR DEVICE (SPC)
A | STORAGE ARRAY DEVICE (SCC)
R | CD DEVICE (MMC)
B | SIMPLIFIED DIRECT-ACCESS DEVICE (RBC)
S | SCANNER DEVICE (SCSI-2)
C | COMMUNICATION DEVICE (SCSI-2)
D | DIRECT ACCESS DEVICE (SBC-2)
T | SEQUENTIAL ACCESS DEVICE (SSC)
E | ENCLOSURE SERVICES DEVICE (SES)
W | WRITE ONCE READ MULTIPLE DEVICE (SBC-2)
K | OPTICAL CARD READER/WRITER DEVICE (OCRW)
L | PRINTER DEVICE (SSC)
M | MEDIA CHANGER DEVICE (SMC)

[ GUI::SenseKey::asc ]

Additional Sense Key Data. |

This report displays all aditional sense key codes along with their description and the kind of hardware/software they apply to.
This information can be used to understand error messages coming from storade devices like Sun T3 and Sun 6120.

[ report.service.ascq:ascq ]

Help Content > Help | [ Top ]

About

## Storage Automated Diagnostic Environment

## Version 2.2

Copyright © 2003 Sun Microsystems, Inc.
All Rights Reserved
Copyright © 2003 Sun Microsystems, Inc.
Etats-Unis. Tous droits réservés.

[ help_sys.help_page:about,../copyright ]

Copyright © 2003 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Portions may be derived from Berkeley BSD systems, licensed from U. of CA. Sun, Sun Microsystems, the Sun logo and Sun StorEdge are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Federal Acquisitions: Commercial Software - Government Users Subject to Standard License Terms and Conditions. Copyright © 2003 Sun Microsystems, Inc. Tous droits réservés. Distribué par des licences qui en restreignent l'utilisation. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun. Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie. Sun, Sun Microsystems, le logo Sun et Sun StorEdge sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.

[ help_sys.help_page:about,../copyright ]

Help Content > Architecture | [ Top ]
Storage Automated Diagnostic Environment
Architecture | [ Help ]

[ GUI::Navigation::file ]

Architecture

Architecture |

The architecture page contains a diagram of the primary software component of Storage A.D.E.

[ help_sys.arch:arch_storade ]

Help Content > Diagnostics | [ Top ]
Storage Automated Diagnostic Environment
Diagnostics | [ Help ]
## Storage Automated Diagnostic Environment Diagnostic Guide
6120ofdg | 6120ofdg - tests the functionality of the Sun StorEdge 6120 array
6120ondg | 6120ondg - tests the Fibre Channel loops inside and outside the Sun StorEdge 6120 array.
6120volverify | 6120volverify - Runs manual parity checks on Sun StorEdge 6120 array volumes
a3500fctest | a3500fctest - verifies functionality of Sun StorEdge A3500FC disk tray
a5ksestest | a5ksestest - tests Sun StorEdge A5000 and A5200 arrays
a5ktest | a5ktest - tests the functionality of disks in the Sun StorEdge A5000 and A5200 array
brocadetest | brocadetest - diagnose Brocade Silkworm Fibre Channel switches
checkcron | checkcron - check crontab entries
clearcache | clearcache -clears Storage Automated Diagnostic Environment cache files
config_solution | config_solution - creates a configuration snapshot during the manufacturing and upgrading of Sun StorEdge 3900 and 6900 series and Sun StorEdge 6320 and 6320SL system solu- tions.
d2disktest | d2disktest - tests the functionality of the Internal Sun StorEdge D2 Array disk
daksestest | daksestest - tests Sun Fire V880 FC-AL disk backplanes
daktest | daktest - tests the Sun Fire V880 FC-AL disk
dex | dex - Device Exerciser for Sun StorEdge arrays
discman | discman - discovery manager
disk_inquiry | disk_inquiry - disk-only version of the inquiry program
disktest | disktest - tests the functionality of fibre channel disks
fcdisktest | fcdisktest - tests the functionality of internal fibre chan- nel disk
fctapetest | fctapetest - tests the functionality of Fibre Channel tape drives
ifptest | ifptest - tests functionality of the PCI FC-100 Fibre Channel-Arbitrated loops (FC-AL) card
lbf | lbf - A loop back frame diagnostic utility program that tests Fibre Channel-Arbitrated loops (FC-AL)
linktest | linktest - diagnose Sun StorEdge network passive Fibre Chan- nel components
qlctest | qlctest - tests the functions of the Sun StorEdge 1 Gbyte and 2 Gbyte PCI and cPCI Fibre Channel Network Adapter boards.
ras_admin | ras_admin - command line interface to Storage Automated Diagnostic Environment
ras_discover | ras_discover - discovers devices and updates the configura- tion file on the slave and the master.
ras_install | ras_install - executes the ras_install command to start the Storage Automated Diagnostic Environment services.
ras_patchlist | ras_patchlist - executes PatchPro software and creates a list of devices and required patches.
ras_remote | ras_remote - executes Storage Automated Diagnostic Environ- ment commands remotely.
ras_revcheck | ras_revcheck - checks the software, hardware, and firmware revision levels.
ras_upgrade | ras_upgrade - upgrades a set of devices using PatchPro.
rasagent | rasagent - monitors, collects, and reports information about Sun storage products.
sanbox | sanbox - access the SANbox switch diagnostic facilities
save_password | save_password - change the Storage Automated Diagnostic Environment admin password
se2_configcheck | se2_configcheck - Verify the configuration of a Sun StorEdge Solution System
se_configcheck | se_configcheck - Verify the configuration of a Sun StorEdge Solution System
snapshot | snapshot - take snapshot of configuration
socaltest | socaltest - tests the SOC+ host adapter card
stresstest | stresstest - Checks for possible SAN errors.
switch2test | switch2test - diagnose Sun StorEdge Network FC switch-8 and switch-16 2 Gbyte Fibre Channel switches
switchtest | switchtest - diagnose Sun StorEdge Network Fibre Channel switch-8 and switch-16 switches
t3ofdg | t3ofdg - tests the functionality of the Sun StorEdge T3 array
t3test | t3test - tests the functionality of the Sun StorEdge T3 and T3+ array LUNs
testt3 | testt3 - retrieve tokens from a Sun StorEdge T3 array
vediag | vediag - Runs virtualization engine diagnostics through SLICD
veluntest | veluntest - tests the functionality of the virtualization engine by accessing the VLUNs.
volverify | volverify - Runs manual parity checks on Sun StorEdge T3, T3+, and 6120 array volumes
volverifytest | volverify - Runs manual parity checks on Sun StorEdge T3, T3+, and 6120 array volumes

[ GUI::Navigation::doc ]

List of Diagnostics and Exercisors programs.
All diagnostics are located in /opt/SUNWstade/Diags/bin, refer to the man pages for more details.

[ help_sys.diag:diag_list ]

Help Content > Utilities | [ Top ]
Storage Automated Diagnostic Environment
Utilities | [ Help ]
All utilities are located in /opt/SUNWstade, see the man pages for more details
Program | Description
--- | ---
bin/checkcron | If executed from the command line, this executable program verifies that the executable program "rasagent" is entered in the `crontab(1M)` file. Note: You must be root to run this program.
bin/clearcache | If executed from the command line, this executable program will remove the instrumentation information for all the configured devices from the CACHE. This is typically used during testing purposes so that a DiscoveryEvent can be forced to occur upon the next execution of the Storage Automated Diagnostic Environment Agent.
disk_inquiry | Used by Storage Automated Diagnostic Environment to discover devices on the data-path that are using SCSI commands.
bin/ras_admin | performs common Storage Automated Diagnostic Environment administrative tasks from the command line interface (CLI).
bin/ras_install | This program will set-up the HTTP service, add a cron and register with the master Storage Automated Diagnostic Environment Agent in the case of a slave install. It must be run manually upon completing the 'pkgadd'. This program can be executed anytime after the initial execution and setup when a modification to the cron is desired or to change the Master/Slave title of a Host agent. Refer to the User's Guide before making changes.
bin/ras_revcheck | Checks the software, hardware, and firmware revision levels of all user-selected modules. The report displays the current revision, the expected revision, and upgrade information.
bin/ras_fccheck | Utility is used to provide a check of available Fibre Channel counters to verify link integrity. ras_fccheck utility probes the device counters and creates an initial baseline for comparison. After a short period of time, the ras_fccheck utility again compares the device counters and compares them to the baseline to determine if problems exist.
bin/rasagent | This is the executable program that calls the modules for the different Network Storage Devices supported by this monitoring agent. It is executed automatically by cron or can be run manually from the command line. Keep in mid however, if run from the command line, rasagent will first check that another process for rasagent is not already running.
bin/save_password | Utility used by the system administrator to change the password to Storage Automated Diagnostic Environment's graphical user interface. Changing the password can also be performed in the GUI itself. However this utility would be used from the command line when the administrator forgot the password. Usage: save_password <password>
bin/sanbox | Utility used by Storage Automated Diagnostic Environment to gather Fibre Channel Switch information.
bin/testt3 | Verify that the tokens of a specific T3 are working. T3 token files elemprop.html and sysprop.html must be available for the Storage Automated Diagnostic Environment probing capabilities to work properly. Running this utility from the command will require that the IP Address of the T3 being probed is known. Usage: testt3 <ip_address>

[ GUI::Navigation::file ]

All utilities are located in /opt/SUNWstade, see the man pages for more details

[ help_sys.utility:utility_list ]

Help Content > Abbreviations | [ Top ]
Storage Automated Diagnostic Environment
Abbreviations | [ Help ]
For readability purposes, some Sun products are referred to by an abbreviation. The following is a list of product names used in this software and their abbreviation.
Product Name | Abbreviation | a.k.a.
Sun Internal Fibre Channel Disk | Sun FC-Disk | disk
Sun Server | Sun Server | server
Sun StorEdge A5000 and A5200 | Sun A5000 | A5K
Sun StorEdge 9900 | Sun 9900 | 9900
Sun StorEdge A3500FC | Sun A3500FC | A3500FC
Sun StorEdge A1000 | Sun A1000 | A1000
Sun StorEdge 3310 | Sun 3310 | 3310
Sun StorEdge 3510 | Sun 3510 | 3510
Sun StorEdge D2 | Sun D2 | D2
Sun StorEdge T3 and T3+ | Sun T3 | T3
Sun StorEdge 6320 array | Sun 6320 Array | array
Sun StorEdge 6120 array | StorEdge 6120 | 6120
Fibre Channel Tape | FC-Tape | tape
Sun Fire V880 Disk | Sun V880 Disk | daktari
LogFile messages | LogFile | Message
Sun StorEdge network FC switch-8 and switch-16 | Sun Switch | Qlogic Switch
Sun StorEdge network FC 2Gig switch | Sun Switch2 | Qlogic Switch
Brocade SilkWorm FC Switch | Brocade switch | Brocade
McData ED6064 FC Switch | McData switch | McData
Virtualization Engine | Vicom VE | VE
Sun Data Service Processor | Sun DSP | SVE
Sun StorEdge 3900/6900 Series | Sun 3900/6900 | SE
Sun StorEdge 6320 Series | Sun 6320 | SE2
SAN links | SAN links | SE2
Sun StorEdge 3900 and 6900 Series | Sun 3900/6900 | Solution
Sun StorEdge PCI FC-100 Host Bus Adapter | Sun PCI FC-100 HBA | ifp
Sun StorEdge Dual Fibre Channel Host Bus Adapter | Sun PCI Dual FC HBA | Qlogic 2200
Sun StorEdge SBus FC-100 Host Bus Adapter | Sun SBus FC-100 HBA | soc+

[ GUI::Navigation::file ]

For readability purposes, some Sun products are referred to by an abbreviation. The following is a list of product names used in this software and their abbreviation.

[ help_sys.abbrev:abbreviations ]