> Help Summary

Maintenance -> General
- General Maintenance | Set up the Storage Automated Diagnostic Environment Agents
- Site Information | Maintain customer and site information.(s)
- Maintain Hosts | Enter customer and device information and configure host(s)
- Add a Host | Add a new slave manually
- Discovery | Probe the environments for the device types.
- Discover a Solution Cabinet | Query for a Sun StorEdge 3900 or 6900 series cabinet
- Search the LAN | Search the LAN for Sun StorEdge devices using Subnet
- Set up Sun StorEdge T3 and T3+ Array Monitoring | Mirror the Sun StorEdge T3 array's `/syslog` to a host
- Add Devices | Add a new device to the Storage Automated Diagnostic Environment
- Maintain Devices | Add, delete, update, and rename device information
- Update Devices | Update the necessary fields for an existing device.
- Delete Devices | Remove the device once it is no longer needed.
- Rename a Device | Manually add the world wide name (WWN) into the configuration file.
- Email Notification | Customize the generation of local email to system administrators.
- Local Notification: Add New Entry | Create a notification record for system administrator
- Send a Message Subset | Send a customizable subset of event-driven messages from the host
- Notification Providers | Relay events generated by the health monitors
- Push Slaves | Update Slave Agent Configuration File
- Start/Stop Agents | Control Agent activity
- Start/Stop Devices | Deactivate monitoring on a device-by-device basis
- Test email | Test Email functions
- Review Config | Report results and make available pointers to areas that require review
- Configuration Options | Change configuration options.
- Application Launcher | Store URL bookmarks and launch management interface.

Maintenance | [ Up ]

The Maintenance section includes all the functions that are necessary for setting up the Storage Automated Diagnostic Environment for the first time, or to make changes, to ensure proper monitoring, notification, and diagnosis.

Once you have configured the Storage Automated Diagnostic Environment master and slave hosts, you should use the Maintenance section only to update email notifications or to update the monitored devices.

Maintain Site Information | [ Up ]

From the General Maintenance window, select Site Information. The fields on this page must be completed before you proceed. The fields with an asterisk (*) are mandatory. To update the master configuration, click an existing Host Name link from the Maintain Hosts window and update the fields as required, then click Submit.

Maintain Hosts | [ Up ]

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.

Add a New Slave | [ Up ]

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 default is 5 minutes.
Note: The `cron` continues to run every 5 minutes, but it checks the frequency setting before loading any modules.

- 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 slave 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.

Discovery | [ Up ]

You can request the Storage Automated Diagnostic Environment to probe the environments for the device types shown on the Discovery window.

The Storage Automated Diagnostic Environment discovers storage devices in two ways:

- Merged host-centric discovery views.
- Storage-centric topology.

The Storage Automated Diagnostic Environment discovers the following devices on the physical data path attachments to the host:

- Sun StorEdge A5000 arrays
- Sun StorEdge A3500-FC Raid Controllers
- Sun Fire V880 Disk
- Sun StorEdge D2 array
- Internal Fibre Channel Disk
- Fibre Channel Tape devices

The Storage Automated Diagnostic Environment automatically discovers the Sun StorEdge network FC switch-8 and switch-16 switches by reading the `/etc/fcswitch` file. Additionally, the Subnet functionality asks for an IP network prefix to scan for Sun StorEdge Network 2 Gb Switch-16 switches and Brocade Silkworm 1 Gb and 2 Gb switches answering to SNMP queries.

The Storage Automated Diagnostic Environment does not automatically discover Brocade Silkworm switches. The current workaround is to manually add the Brocade Silkworm switch's IP address to the `/etc/fcswitch` file.

The Storage Automated Diagnostic Environment automatically discovers the Sun StorEdge T3 and T3+ arrays by scanning the Sun StorEdge T3 and T3+ array logfile on all Hosts. Entries that contain a valid IP name or address are added to the configuration.

The Storage Automated Diagnostic Environment discovers the Sun StorEdge 3900 and 6900 series using the `/etc/host` file of the Storage Service Processor.

Discover a Sun StorEdge 3900 or 6900 Series System | [ Up ]

Sun StorEdge 3900 series storage systems for direct attach storage (DAS) environments, and Sun StorEdge 6900 series storage systems for Storage Area Network (SAN) environments, are complete, preconfigured storage solutions. End users have only restricted accessibility to the internal components of the subsystems, but they do have full utilization of its storage functionality.

Select the Sun 3900/6900 button on the Device Discovery window to instruct the Storage Automated Diagnostic Environment to query for a Sun StorEdge 3900 or 6900 series system. The IP address or name of the Storage Service Processor in the Sun StorEdge 3900 or 6900 series system should be selected. The master will then query locally or the slave address selected for the Sun StorEdge 3600 or 6900 series system.

1. From the Product/Discovery Method pull-down menu, select Sun 3900/6900.
2. From the Run on Host pull-down menu:

- If the master is a Sun StorEdge 3900 and 6900 series configuration, select Local from the Run on host pull-down menu.
- If the slave is a Sun StorEdge 3900 and 6900 series configuration, select the slave's Storage Service Processor from the Run on host pull-down menu.

This procedure is written with the assumption that the `Solution.golden` file was created on all Sun StorEdge 3900 and 6900 series configurations using the `config_solution`(1M) command.

The `Solution.golden` file is created during the manufacturing and upgrades of the Sun StorEdge 3900 and 6900 series, or when components are replaced.

3. Disable the Turn Monitoring Off checkbox.
4. Click Confirm Sun StorEdge 3900 and 6900 series Discovery.

This function uses the local /etc/hosts file for discovery on the Storage Service Processor.

Search the LAN for Sun StorEdge Devices using Subnet | [ Up ]

Use the Subnet button to search the LAN for Sun StorEdge network FC switch-8 and switch-16 switch devices, Brocade Silkworm switches, and Sun StorEdge T3 and T3+ arrays.

1. Enter the IP address of the subnet you want searched.
2. Enter the Subnet prefix for the search.

The Subnet functionality will search the subnet for valid devices.

The search results are sent back to the master agent. The master agent moves the recently discovered, valid devices that were previously in the subnet into the main configuration file.

Set Up Sun StorEdge T3 and T3+ Array Message Monitoring | [ Up ]

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

1. Refer to the Sun StorEdge T3 and T3+ Installation and Configuration Manual, part number 816-4769-10, for procedures on how to set up the Sun StorEdge T3 array and the host to forward `syslog` messages.
2. Refer to the Maintain Hosts section to configure each host with the name given to the T3 and T3+ array message log file.

Add a Device Manually | [ Up ]

To Add a Device Manually:

1. Click the Add Devices link on the General Maintenance Menu.
2. Complete the required fields:

Required Input

Sun StorEdge A3500FC array

- Type the device name the Storage Automated Diagnostic Environment will use to identify the device.
- Enter the serial number for the device.
- Select the Storage Automated Diagnostic Environment's primary host that will perform the actual monitoring of the device.

Sun StorEdge A5000 array

- Type the device name the Storage Automated Diagnostic Environment will use to identify the device.
- Select the Storage Automated Diagnostic Environment's primary host that will perform the actual monitoring of the device.

Brocade Silkworm switches

- Type the device name the Storage Automated Diagnostic Environment will use to identify the device.
- Select the Storage Automated Diagnostic Environment's primary host that will perform the actual monitoring of the device.
- Type the optional telnet password, which enables the Storage Automated Diagnostic Environment to log into the Brocade switch.
- Type the IP address that identifies the host to the network.

Sun StorEdge D2 array

- Type the device path with which the Storage Automated Diagnostic Environment will access the device.
- Select the Storage Automated Environment's primary host that will perform the actual monitoring of the device.
- Type the serial number of the Sun StorEdge D2 array, which will be used to identify the device to the host.

Internal FC Disk

- Select the Storage Automated Diagnostic Environment's primary host that will perform the actual monitoring of the device.

Sun StorEdge network FC switch-8 and switch-16 switches

- Type the device name the Storage Automated Diagnostic Environment will use to identify the device.
- Select the Storage Automated Diagnostic Environment's primary host that will perform the actual monitoring of the device.
- Type the optional admin/telnet password, which enables the Storage Automated Diagnostic Environment to log into the Sun switch.
- Type the IP address that identifies the host to the network.

Sun StorEdge T3 and T3+ Array

- Type the device name the Storage Automated Diagnostic Environment will use to identify the device.
- Type the optional telnet password, which enables the Storage Automated Diagnostic Environment to log into the Sun StorEdge T3 and T3+ array device. Note that the user is not authorized to change an existing Sun StorEdge T3 and T3+ array password.
- Select the Storage Automated Diagnostic Environment's primary host that will perform the actual monitoring of the device.
- Type the IP address that identifies the host to the network.

FC Tape

- Type the device name the Storage Automated Diagnostic Environment will use to identify the device.
- Select the Storage Automated Diagnostic Environment's primary host that will perform the actual monitoring of the device.

Sun Fire V880 FC-AL Disk

- Type the device name the Storage Automated Diagnostic Environment will use to identify the device.
- Select the Storage Automated Diagnostic Environment's primary host that will perform the actual monitoring of the device.

Virtualization Engine

- Select the Storage Automated Diagnostic Environment's primary host that will perform the actual monitoring of the device.
- Enable the Turn Monitoring On button.

3. After you have finished adding devices, click Update Selected Slaves using Push Slave Configs.

   The Update Selected Slaves functionality is required to update a slave's configuration after you have added or updated one or more devices.

Maintain Devices | [ Up ]

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 A3500-FC arrays from a host that has an attachment through the Fibre Channel cables and can run the Sun StorEdge RAID Manager commands.
- Monitor Sun StorEdge A5000 arrays, Sun Fire V880 Disk, and Sun StorEdge D2 arrays from the host that has a direct attachment through the Fibre Channel cables.
- Monitor Sun StorEdge network FC Switch-8 and Switch-16 switches on any host on the subnet, because the probing is done over the network.
- Monitor Brocade Silkworm switches on any host on the subnet, because the probing is done over the network.
- Monitor Sun StorEdge T3 and T3+ arrays from the host that has access to the t3 message log file and has an Ethernet connection on the subnet.
<
- Monitor Internal Fibre Channel Disk and Fibre Channel Tape devices from the host that has an attachment through the Fibre Channel cables.
- Monitor Sun StorEdge 3900 and 6900 series systems from the Storage Service Processor, which has an Ethernet connection to the Sun StorEdge T3 and T3+ array, the Sun StorEdge network FC switch-8 and switch-16 switches, and the virtualization engine.

Note:

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

Click the Info link from the Maintain Devices window to access the Comments screen. The Maintain Devices: Comments screen enables you to add additional information about a device. For example, you can enter the device's serial number, its location, or whether the device is associated with a Sun StorEdge 3900 or 6900 series solution.

Manually Update a Device | [ Up ]

1. Click the Admin link on the Storage Automated Diagnostic Environment main window.
2. Click the Maintain Devices link on the General Maintenance menu.
3. From the Maintain Devices window, select and click the device you want to update from the Device Name column.
4. Once you have corrected the necessary fields, click Update.
5. After you have added a device or updated a device, refresh the system by clicking Re-Discover.

Notes:

- 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 (for example, if you change the chassis ID of a switch), you must delete that unwanted device. 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.

Delete a Device | [ Up ]

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

Note:

You can delete a slave, but the only way you can delete a master is to remove the package.

To delete a device:

1. Click the Admin link on the Storage Automated Diagnostic Environment main window.

2. Click the Maintain Devices link on the Maintenance menu.
   The Maintain Devices window is displayed.

3. From the Maintain Devices window, select the device you want to delete from the Device Name column.
   The device's maintenance window is displayed.

4. Click Delete.
   - 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.

Rename a Device | [ Up ]

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 the file `/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.

Email Notification | [ Up ]

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 and T3+ 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. slave instances of the Storage Automated Diagnostic Environment send their alerts to the master, which filters them and forwards them to the providers, if selected, and to local system administrators, if configured.

Local Notification: Add New Entry | [ Up ]

Create a notification record for each system administrator who would like to be notified of the Storage Automated Diagnostic Environment findings. You can restrict the findings by Event Type, Priority, and Device Category. Multiple events can be selected and sent to an email or a pager. This flexibility enables a customized alert notification scheme.

To add a new entry:

1. Click an email link to update or delete an existing email address.
2. Click the Add Notification button to add new email addresses to the notification list.

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.

Send a Customizable Subset of Event-Driven Messages from the Host | [ Up ]

1. Enter one or more email addresses into the Email Address/Filename textbox.

2. For each address, choose from:
   - Priority list:
   - 0 = normal (green), information only. This is the lowest priority.
   - 1 = warning (yellow)
   - 2 = error (red)
   - 3 = down (red), the system is down.
   - warning + error + down
   - actionable only
   - Category list - Select from the current suite of storage products that are monitored by the Storage Automated Diagnostic Environment.
   - Event Type list - Select from a list of event types, categorized by device type.

3. Click Add.

The Storage Automated Diagnostic Environment sends the specific event type messages, by device type, to the email address(es) you specified.

Notification Providers | [ Up ]

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 several providers: HTTP, Email, SSTR, SRS, Net Connect, SunMC, SNMP Traps, and SSRR.

The types of providers are briefly described in the following sections:

- The HTTP Provider sends HTTP calls to an HTTP server and transfers CIM data in the appropriate format. This is an Intranet mechanism for transporting RAS information collected by the Storage Automated Diagnostic Environment agent and is currently internal to Sun only.

- 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.

- The SSTR Provider sends Storage Automated Diagnostic Environment events to the Sun StorEdge Topology Reporter (SSTR) console. The SSTR console enables you to:

- View hardware assets such as hosts, host bus adapters, switches, and storage devices, including a graphical view of your environment
- Manage users, alarms, and assets
- Configure user email notification and network host notification
- Manage asset reporting (also known as Discovery)
- Launch other web browser-based applications related to devices in a particular environment

- 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.

  The SRS provider enables a second IP address, in case the events need to be sent to a second notification provider that also accepts the SRS XML format.

- The SRS Net Connect Provider is a part of the SRS family of products. SRS Net Connect uses internet-based technology, which avoids the need for additional dedicated network connections at the customer site. SRS Net Connect can notify the user, through email or pager, when system activity exceeds set thresholds.

  Note: The host with the master agent must be the same host that is configured as the relay in a NetConnect Provider configuration.

- 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

- SSRR Provider

  The Sun StorEdge Remote Response 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. Once 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.`

- 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.

  Push Slave Configs | [ Up ]

  You will be prompted to push configurations whenever you change a configuration. The Review Configurations functionality lists settings that you might have missed or you need to correct.

  Note:

  The Push Configs functionality is very important. It synchronizes all slave instances under a master instance, with the instances of the master to ensure proper monitoring and notification.

  Start or Stop Agents | [ Up ]

  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/Stop Agent(s) 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.

Start/Stop Device Monitoring | [ Up ]

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. Click Submit Changes.

   The Storage Automated Diagnostic Environment must update the configuration files on all the slave hosts configured with this master.

- Use the [Push Slave Configs] option on the Maintenance menu to accomplish this.

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 SRS Net Connect or HTTP Providers, but not by means of email notification.

Test Email | [ Up ]

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.

To access the Test Email window:

1. Click the Admin link in the Storage Automated Diagnostic Environment main window.
2. Click the Test Email link on the General Maintenance menu.

   The Test Email window is displayed.

3. Type your email address into the Email Address text box.
4. Type a brief comment into the Message text field.

If you leave the Message text field blank, the test email contains a default message with the words Test Message in the subject line.

NOTE:

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.

Review Configuration | [ Up ]

1. Once you have completed your configuration and you want to verify all settings, select the Review Configuration link on the General Maintenance menu.
2. If necessary, follow the displayed instructions for settings that you might have missed or for those that you need to double-check.

Change Configuration Options | [ Up ]

The Configuration Options window enables you to change the defaults on selected configuration options. Use the following information to update existing 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.

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

- Minimum FC Monitoring Frequency (in minutes)
  Use to configure FC counter monitoring rate (in minutes). The default is zero.

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

- Screen Size
  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. Big Screen is recommended if your monitor size is 1280 x 1024.
  - Small Screen-displays three windows, as with the Big Screen selection, but is recommended if your monitor size is 1024 x 864.
  - 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.

Application Launcher | [ Up ]

The Application Launcher enables users to store URL bookmarks in the Storage Automated Diagnostic Environment on a device-by-device basis. Currently the devices for which URL bookmarks can be stored include the following:

- Sun StorEdge T3 and T3+ arrays
- Brocade Silkworm switches
- Sun StorEdge Network FC Switches
- Sun StorEdge 3900 and 6900 series
- Fibre Channel Tape devices
- Virtualization engines

Note:

The Application Launcher provides an easy way to launch the Brocade Silkworm Switch Management Interface directly from the Storage Automated Diagnostic Environment without having to open a new browser window and type the URL of the Brocade Silkworm switch manually.