The following information applies to version 6 of the Discover Components application.
Do you need to install or update Discover Components? See Manage Applications for instructions about the App Store.
The Discover Components application is a fundamental component of StorNext Connect. StorNext Connect cannot work without it. The application relies on one or more name servers as a starting point to look up hostnames of clients and volumes (file systems) (it does not scan client IP addresses and ports). From there, Discover Components works to identify the topology of the StorNext environment. You use this application to discover StorNext components and assign them to StorNext environments.
Using the name server(s), Discover Components identifies the hosts of the workspace (cluster). Host is another name for the components or nodes that make up the workspace. Name servers, MDCs, and StorNext clients are all hosts.
The Discover Components application shows the following information about the hosts in the workspace.
Why did discovery not find a host or volume?
- The host is online and operational.
- The host's StorNext licensing is up-to-date.
- The volume is mounted.
- The MDC has at least one volume (mounted or owned).
Discovery is a point-in-time snapshot of the environment. The first discovery takes place during StorNext Connect installation. After making any changes to client systems (starting or stopping StorNext, adding clients, updating or downgrading StorNext client software, and so on), you must Rediscover. This ensures StorNext Connect recognizes clients by their current StorNext software version. Failure to do this may report the software revision that was on the client before the upgrade/downgrade. Similarly, without rediscovery after environment changes, StorNext Connect might not recognize all hosts in the StorNext Connect workspace, in which case data for those hosts will not appear in the monitoring applications.
- Open Discover Components.
- Click Rediscover.
- Verify the name server(s) for the workspace (cluster). If needed, add or edit the name server(s).
- Click Discover.
- After discovery completes, click Continue to return to the main page of Discover Components.
Discover Components Application Concepts
Hosts are discovered (and shown in Discover Components) if:
- StorNext is installed on the host
- The Connector is installed on the host
For each name server, StorNext Connect runs the snprobe command to identify the hosts and their volume (file system), disk array, and licensing information. For each host, StorNext Connect discovers additional details, such as the operating system and StorNext version. This detailed discovery requires the Connector to be installed.
Make sure the same (and latest) version of the Connector is installed on the StorNext Connect system and all hosts in the environment to ensure proper operation.
During the snprobe discovery, StorNext Connect identifies a host by its metadata IP address. If the metadata IP address changes, Discover Components identifies it as a different host. If an IP address other than the metadata IP address for the host changes, StorNext Connect recognizes the change and continues to monitor and manage the host seamlessly after rediscovery.
Note: StorNext Windows clients and Apple Xsan clients require manual updating to continue to be monitored by StorNext Connect if IP addresses or hostnames change.
The StorNext name service provides a means for StorNext clients to discover the location (IP address) of the File System Manager (FSM) and other similar services. The FSM registers with the name server(s) and provides the IP addresses by which it can be reached. These addresses are then forwarded to clients.
Name servers (also called "coordinators") are defined in the fsnameservers file.
Quantum does not recommend entering StorNext clients as a name server in the Discover Components application. However, StorNext Connect does not restrict this configuration. When adding name server values in the Discover Components application, only enter the values contained in the fsnameservers file on the StorNext MDC/Xcellis Workflow Director for the workspace (cluster) associated with that client.
In Discover Components, you will see a message similar to the following example at the bottom of the page.
The note indicates the shared volume (file system) is available only for use by the StorNext MDC/Workflow Director HA pair, and is not mountable by any StorNext client. In this example, shared-AV1442CKB00310 is the name of the HA shared volume. For appliances, this name is based on the serial number of the appliance. For customer-supplied HA systems with a shared volume, this could be a different identifier.
If a management capable Connector is installed on a host, discovery identifies all IP addresses for the host. For example, StorNext Connect recognizes if an MDC has both a public and private network IP address. Similarly, StorNext Connect recognizes a StorNext client by any of its IP addresses, whether metadata network, management network, NAS, or iSCSI.
During the detailed discovery of a host, StorNext Connect reads the /etc/fstab file to identify the volumes (file systems) that the host mounts. If you stop StorNext on the host, the Discover Components main page continues to list the volume even though the host is unable to mount the volume because StorNext is inactive.