Use the Discovery_MSCS Knowledge Script to discover Microsoft Cluster Server (MSCS) configuration and resources. You can run this script on any node in the cluster. Only discover actual cluster nodes. You should not attempt to add or discover virtual servers
Every time you add a new node to the cluster, you must install the AppManager agent on the new node and run the Discovery_MSCS Knowledge Script to discover it. After you discover the new cluster node, the new node appears in the TreeView pane of the Operator Console or in the Control Center Console.
Run Discovery_MSCS on MSCS server objects. By default, this script runs once for each computer.
Set the Values tab parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Raise event when discovery succeeds? (y/n) |
This script always raises an event when the job fails for any reason. In addition, you can set this parameter to y to raise an event when the job succeeds. The default is n. |
|
Event severity when discovery succeeds |
Set the event severity level, from 1 to 40, to reflect the importance of an event in which discovery succeeds. The default is 25 (blue event indicator). |
|
Event severity when discovery fails |
Set the event severity level, from 1 to 40, to reflect the importance of an event in which discovery fails. The default is 5 (red event indicator). |
|
Event severity when discovery partially succeeds |
Set the event severity level, from 1 to 40, to reflect the importance of an event in which discovery returns some data but also generates warning messages. The default is 10 (red event indicator). |
|
Event severity when discovery is not applicable |
Set the event severity level, from 1 to 40, to reflect the importance of an event in which the target computer does not have MSCS installed. The default is 15 (yellow event indicator). |
If you discover multiple nodes that are part of the same cluster, you may see what appear to be duplicate entries in the application view. For example, assume you have a SQL Server cluster with the computers LOBO1 and LOBO2. Both of these computers are displayed in the Master view. After you run the SQL discovery to discover the cluster, LOBO1 and LOBO2 display the resource object SQL Server:LOSLOBOS_SQL in the Master view. LOSLOBOS_SQL represents the virtual server.
When you discover clustered applications such as Exchange and SQL Server, the discovered objects use the virtual server name, for example, LOSLOBOS_SQL. When you run Discovery_MSCS, the discovered objects use the physical node name. For example, after running Discovery_MSCS on the physical nodes and virtual server names described in this example, the Master view should display MSCS Server:LOBO1 under LOBO1, and MSCS Server:LOBO2 under LOBO2.