Storage Automated Diagnostic Environment> for the first time, or to make changes, to ensure proper monitoring and notification.
Once you have configured the master and slave hosts, you should use the Maintenance section only occasionally to update email notifications or to update the monitored devices.
You can use the Maintain Hosts window to maintain a list of hosts from where the Storage Automated Diagnostic Environment> is running. When the SUNWstade> 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 the master agent. Once all hosts are installed, you can access this page to change the configuration of each host.
The three main functions of this window are:
- Add a New Slave - Use when an agent does not automatically register.
- Ping Slaves - Verify that the agent at each host is up and running. The master will ping the slaves and request their hostid to verify that the host is up and that the Storage Automated Diagnostic Environment> service is available.
- Push Slave Configurations - Once all the slaves have been updated, you can push the new configurations to the respective master by using Push Slave Configs. Each agent includes its own configuration file, but you must perform the administration of the slaves from one centralized location.
Maintain Site Information
| [ Up ] |
To access the Maintain Site Information window, click on a hostname from the Host Maintenance
window.
The fields are listed below.
- Customer Name
Enter your company name
- Customer No.
Enter your company's customer number
- Contract No.
Enter your company's contract number
- Stock Ticket
Enter your company's stock market symbol so that the company name can be tracked accurately.
- Site Information
Enter your site name and address. Include a contact person's name and email address.
If a slave agent does not automatically register, you can add a new slave manually.
Caution: If the system is currently a master and you wish to change it to a slave follow the procedure below, then push the slave configs. From the push slave configs screen you can specify a new master.
To access the Maintain Hosts: Add New Slave window:
- Click the Maintenance link on the Storage Automated Diagnostic Environment> window.
- Click the Maintain Hosts link from the Maintenance menu.
- Click the Add New Slave button.
Note: The Categories to Monitor choices indicate Sun Microsystem network storage
devices that are supported with this instance of the Storage Automated Diagnostic Environment>.
The fields for the Add New Slave window follow.
- Host ID
Type the 8-digit alphanumeric host ID, which is the same as the system ID (for example, 123x45y6). You can use the hostid command on the host to obtain a valid Host ID.
If the Host ID is not available, you can enter a "dummy" number and correct it later. Note, however, that the Host ID cannot match any other previously-accepted Host ID.
- Host Name
Type the name of the host (hostname.domain).
- Categories to Monitor
Choose the devices to monitor. The Categories to Monitor choices indicate Sun Microsystem network storage devices that are supported with this instance of the Storage Automated Diagnostic Environment>.
- Monitoring Frequency
Select a variable between five and 120 minutes. This frequency variable affects how often the monitoring cronjob will execute.
Note: The cronjob continues to run every five minutes, but it checks this frequency setting before loading any modules.
- Sun 3900/6900 Series
Select the Sun 3900/6900 Series button if the device or devices to be monitored are part of a Solution.
- Message Log
Type the path for the message log (for example, /var/adm/messages), which displays the history of the status messages.
- Sun T3 Message Log
Type the path for the Sun T3 message log as it appears in the /etc/syslog.conf file on the host server you are configuring.
Notes:
- Enter an 8-digit HostID (for example, 12345678) 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 number. 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.
This function will query all configured hosts for devices of the requested type. This process may take a few moments, depending on the size of the monitored configuration. - Sun StorEdge A5000, Sun StorEdge A3500FC and Fibre Channel Tape devices are discovered using the datapath attachments to the host.
- Sun StorEdge network FC switch-8 and switch-16 are automatically found by reading the /etc/fcswitch.conf file (format is similar to /etc/hosts). Additionally, the Subnet button will ask for an ip network prefix to scan for switches answering to SNMP queries.
- Sun StorEdge T3 and T3+ arrays are automatically found by scanning the T3 logfile on all hosts. Entries that contain a valid ip name or address are added to the configuration.
- The Sun StorEdge 3900/6900 button discovers devices using the /etc/host file of the Service Processor.
- Subnet Discovery uses snmp to query a subnet and can discover switches and Sun StorEdge T3 and T3+ arrays.
Use the Device Discovery function to request the Storage Automated Diagnostic Environment> to probe the environments for the desired device types.
You can request the Storage Automated Diagnostic Environment> to probe the environments for the device types shown on the Device Discovery window.
- The Storage Automated Diagnostic Environment> discovers the Sun StorEdge A5000 arrays and Sun StorEdge A3500FC Raid Controllers on the data paths of the host to which they are physically attached.
- The Storage Automated Diagnostic Environment> discovers the Sun StorEdge SAN Release 3.0 switch devices by parsing the IP address from the /etc/fcswitch.conf file.
- The Storage Automated Diagnostic Environment> discovers the Sun StorEdge T3 arrays by filtering the Sun T3 message log file (pre-configured in the host configuration window) for valid Sun StorEdge T3 array IP addresses.
Note:
As long as there are valid Sun T3 entries in this log file, the auto-discovery will find them and add them.
You can avoid adding older, unwanted Sun T3s by rolling over the log file, much the same way the system log rolls over.
Reference the scripts /usr/lib/newsyslog and /etc/cron.d/logchecker.
In a cascaded switch-configured SAN, only the switch with the host attachment needs to be in the /etc/fcswitch.conf file. The Storage Automated Diagnostic Environment> will discover the cascaded switch when the first switch is discovered.
If a switch is not in the /etc/fcswitch.conf file, you can manually add it. Be aware, however, that the SAN topology will display the name you give to the switch and not necessarily the switch's official trademarked name.
Note:
Once you have added a switch to the /etc/fcswitch.conf file, you must go to the Maintenance, Discovery window and select SWITCH. A new toplogy must also be created.
Discover a Sun StorEdge 3900/6900 Series Solution Cabinet
| [ 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 internals of the subsystems, but they do have full utilization of its storage
functionality.
Use the Solution button from the Device Discovery window to query for a Solution cabinet.
This function uses the local /etc/hosts file for discovery on the service processor.
- Select the host from the Run on Host menu.
- Enable the Turn Monitoring On toggle button.
- Select a host from the Data Path Host pull down menu. This host may be the same as, or different from, your local host.
- Click Confirm Sun 3900/6900 Series Discovery.
Note:
The Storage Automated Diagnostic Environment> utilizes the ethernet connection (out-of-band) to the Sun StorEdge T3 arrays, virtualization engines (VE), and Sun StorEdge Network FC Switch-8 and Switch-16
switch devices.
Search the LAN for Sun StorEdge Devices using Subnet
| [ Up ] |
Use the Subnet button to search the LAN for Sun StorEdge SAN Release 3.0 switch devices and Sun StorEdge T3 arrays.
- Enter the address of the subnet you want searched.
- Enter the prefix to call the name of the device.
The Subnet functionality can search two subnets at a time (for example, Subnet 10.1.0 and Prefix 10.1Net, with Subnet 10.2.0 and Prefix 10.2Net).
All discovery results are sent back to the master agent, which stores them in the main configuration file.
Set Up Sun StorEdge T3 Array Message Monitoring
| [ Up ] |
In order for the agent to monitor messages from a Sun StorEdge T3 array, you must mirror the
Sun StorEdge T3 array's /syslog to a host with the Storage Automated Diagnostic Environment> installed and
configured to monitor Sun StorEdge T3 arrays.
- Refer to the Sun StorEdge T3 Disk Tray Installation, Operation, and Service Manual for
procedures on how to set up the Sun StorEdge T3 array and the host to forward syslog messages.
- Refer to Maintain Hosts section to configure each host with the name given to the T3 message
log file.
Use the Maintain Devices window to configure the host to monitor each agent 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.
NOTE: This will not affect the naming of the device from the perspective of the host's operating system.
Be aware of the host's access method when making decisions about
which devices the Storage Automated Diagnostic Environment> will monitor.
- Monitor Sun StorEdge A3500FC arrays from a host that has a direct
attachment through the Fibre Channel cables and can run the Sun StorEdge
RAIDManager commands.
- Monitor Sun StorEdge A5000 arrays from the host that has a direct
attachment through the Fibre Channel cables.
- Monitor the Sun StorEdge Network FC Switch-8 and Switch-16 switch on any
host on the subnet, because the probing is done over the network.
- Monitor Sun StorEdge T3 arrays from the host that has access to the
t3 message log file.
- Monitor Sun StorEdge FC Tape from the host that has an attachment through
the Fibre Channel cables.
- Monitor Sun StorEdge Solutions cabinets from a host that has direct attachment through Fibre Channel
cables to Sun StorEdge T3 arrays and Sun StorEdge SAN Release 3.0 switches.
Note:
The Primary Host column lists the registered host that will do
the actual device probing. The buttons indicate Sun Network Storage
devices that are supported with this instance of the Storage Automated Diagnostic Environment>.
- From the Maintain Devices window, select the device you want to update from the
Existing Devices list.
- Once you have corrected the necessary fields, click Update.
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 device. Storage Automated Diagnostic Environment will display a message
that the previous device has been removed. Topology will not, however,
display the deleted device until you manually add and discover the device.
You can delete a device once the device has been removed from the site or if device monitoring is no longer needed.
To delete a device:
- Click the Maintenance link in the main window.
- Click the Maintain Devices link from the Maintenance menu.
The Maintain Devices window is displayed.
- From the Maintain Devices window, select the device you want to delete from the Existing Device list.
The Maintain Host: Update Host window is displayed.
- Click Delete.
Deleting a device from the configuration will not remove the access to the device instrumentation in cache immediately. This will, however, be cleared the next time the agent runs. State information for that device will also be 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 execute the Storage Automated Diagnostic Environment>.
- To temporarily deactivate a device from sending alerts to local notification(s), refer to
"Deactivate Monitoring on a Device-by-Device Basis."
From the Add a New Device section of the Maintain Devices window, select the type of device you want to add to the Storage Automated Diagnostic Environment>.
Complete the fields using the descriptions that follow.
- Device Name
Type the name the Storage Automated Diagnostic Environment> will use to identify the device. This is the
name used to reference the device in all alert notifications.
- Telnet Password (optional)
Type the telnet password. This field applies only to the Sun StorEdge T3 array and is
optional. For a more detailed analysis, enter the root password for the Sun StorEdge T3
array (this enables a higher level of accessibility to the Sun StorEdge T3 array).
- Primary Host
Select the agent's primary host that will perform the actual monitoring
of the device.
Note:
The default is the host that automatically discovered the device.
- Data Path Host
Select the host to which the Fibre Channel cables are physically connected. This
field applies only to the Sun StorEdge T3 array.
- IP Name/Address
Type the 10-digit IP address that identifies the host to the network (for example,
123.45.67.890). This field applies only to the Sun StorEdge Network FC Switch-8
and Switch-16 switch and the Sun StorEdge T3 array.
Once you have entered the required information and the configuration has been pushed to all agents, the Storage Automated Diagnostic Environment> begins to monitor the devices.
Note:
To get the device name for the Sun StorEdge A3500FC array,
use the RM6 command drivutil -l devName, where devName is derived
from the RM6 command /usr/lib/osa/bin/lad.
Local 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,
administrators who are interested only in high-priority alerts coming
from Sun StorEdge T3 arrays 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 types:
- specific device types
- event types
- alert severity
- pager number
Note:
The local notification feature is optional and does not affect the main transmission functions of the Storage Automated Diagnostic Environment>. The master is the only instance of the agent generating emails based on local notifications. Slave instances of the agent 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 Administrator who would like to be notified of the Storage Automated Diagnostic Environment> findings.
You can restrict the findings by Event Priority, Device Category, and Event Type. Multiple events can be selected and sent to an email or a pager. This flexibility allows for a customized alert notification scheme.
To add a new entry:
- Click an email link to update or delete an existing email address.
- Click the Add Notification button to add new email addresses to the notification list.
In addition to sending the 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 via email.
Send a Customizable Subset of Event-Driven Messages from the Host
| [ Up ] |
- Enter one or more email addresses into the Email Address/Filename textbox.
- 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. This is the highest priority.
- Category list
- Event Type list
- 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.
The Storage Automated Diagnostic Environment> supports six providers: HTTP, NSM, NetConnect, SRS, SNMP and RSS. The provider's main function is to relay events generated by health monitors. The providers do this either by pulling the events from the Persistent Data Manager (PDM) or by registering them with the PDM for a certain type of event.
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 used internally only, can support a
Proxy server, and does not communicate through the Internet.
- The NSM provider is used to send actionable events to the Network Storage Management console.
- NetConnect is a common information model (CIM) provider, which is an independent program. It requests information from the PDM, converts the information to the appropriate format, and relays it to NetConnect.
- NetConnect is a common information model (CIM) provider, which is an independent program. It requests information from the PDM, converts the information to the appropriate format, and relays it to NetConnect.
Note:
The host with the Master agent must be the same host that is configured as the relay in a NetConnect Provider configuration.
The master agent has additional functions that enable it to work as a collection point for all the events generated by the slave agents. Periodically, the master polls each slave to ask for messages that need to be transported.
- The SRS/NetConnect Relay Configuration periodically polls the master agent for messages to be transported, encrypted, and sent back to Sun via the Internet.
Note:
You must enter an IP address for the SRS Provider.
- The SNMP provider is used to send actionable events to external Management systems.
- The RSS Provider enables the transfer of agent events to the RSS infrastructure using
Unix-to-Unix Communication Protocol (UUCP). RSS software is required on the host and is
intended to access the modem. It must be configured accordingly.
The RSS software is delivered with the Service Processor software bundle. The intended
audience for this software and for this provider are those customers who have purchased a
remote support service offering and are supplying phone lines to make use of the
modem phone home capability.
Note:
If the RSS Provider is selected, but the RSS software is not installed or is not configured properly, expect to see the following error message:
***ERR: Cannot find Machine name in Permissions file.
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 agent's cron
from running on a selected host. You can also use this window to avoid creating email notifications on false errors when a device is being tested and when faults are injected intentionally.
- Using this 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.
- It would be wiser to use the Start/Stop Devices to control email notifications for specific devices.
NOTES:
- To deselect a device category and to stop monitoring for multiple types of
devices on the host, see Maintain Hosts.
- To control email notifications for specific devices, see Deactivate Monitoring on a Device-by-Device basis.
- To automatically update the slave's configurations and to verify that all slaves agree
with the master configurations, select Push Configs from the Maintenance menu.
Start/Stop Device Monitoring
| [ Up ] |
The Start/Stop Device Monitoring window allows you to deactivate monitoring on a device-by-device basis.
- 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.
- Once you have clicked Submit Changes, the configuration files are updated on all the Slave hosts configured with this Master.
- Use the [Push Configs] option in the Maintenance section to accomplish this.
- 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. 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 via the Providers, but not via email notification.
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.
- Type your email address into the Email Address text box.
- Type a brief comment into the Message text box.
If you leave the Message text box blank, the test email contains a canned message with
the words Test Message in the subject line.
NOTE:
If you place a carriage return in the message field, you cannot enter text.
To restart, click in the Message text box and enter some text.
Review
Configuration | [ Up ] |
Once you have completed your configuration, select the Review Configuration link to verify all settings. If necessary, follow the displayed instructions for those that you might have missed or for those that you need to correct.