Device Discovery

Use this function function to probe the environments for the device types shown on the Device Discovery window:

- Discover the Sun StorEdge A5000 arrays, the Sun StorEdge A3500-FC Raid Controllers, the Sun Fire V880 Disk, the Sun StorEdge D2 array, Internal Fibre Channel Disk, and Fibre Channel Tape devices on the physical data path attachments to the Host.
- Automatically discovers the Sun StorEdge network FC switch-8 and switch-16 switches by reading the `/etc/deviceIP.conf` file (the format is similar to `etc/hosts`). 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.
- 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.
- Discovers the Sun StorEdge 3900 and 6900 series using the `/etc/host` file of the Storage Service Processor.
- Inband discovery uses 'luxadm' to discover a5k,tape,v880disk and internal disks.

/etc/deviceIP.conf example:

    # device_ip  device_name [device_type]  # comments
    # The device_type is optional but required for devices that do not support snmp
    # like the 3310/3510 devices.

    10.0.0.1 t3-1a
    10.0.0.2 minnow1  3310
    10.0.0.3 indy1    se

Note:

As long as there are valid Sun StorEdge T3 and T3+ array entries in this log file, the auto-discovery will find them and add them. You can avoid adding older, unwanted Sun StorEdge T3 and T3+ arrays 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 (that is, the local switch) needs to be in the `/etc/deviceIP.conf` file. The agent will discover the cascaded switch when the first switch is discovered.

You must manually add Brocade Silkworm switches, or search the LAN for a Brocade Silkworm switch and then manually delete the unwanted devices which were discovered elsewhere on the specified LAN.

Discover a Sun StorEdge 3900 or 6900 Series Cabinet |

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 cabinet. The IP address or name of the service processor in the Sun StorEdge 3900 or 6900 series cabinet should be selected. The master will then query locally or the slave address selected for the 3900/6900 subsystem.

1. Select the host from the Run on Host menu.
2. Enable the Turn Monitoring On toggle button.
3. Click Confirm 3900/6900 Discovery.

Note:

The discovery of Sun StorEdge 3900 and 6900 Series subsystems is dependent on the existence of the Solution.golden configuration file which resides in the SUNWstade /var/opt/SUNWstade/DATA directory. This file is created by running the Storage Automated Diagnostic Environment config_solution(1M) utility which is located in the SUNWstade /bin directory. This utility should always be run during manufacture, upgrades and component replacements.

Note:

The Storage Automated Diagnostic Environment employs a direct Ethernet connection (out-of-band) to the Sun StorEdge T3 and T3+ arrays, virtualization engines, Sun StorEdge network FC switch-8 and switch-16 switch devices, and Brocade Silkworm switches.

Search the LAN for Sun StorEdge Devices using Subnet |

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.