How do I properly setup a cluster with 'AMAdmin_SetResDependency' to use Knowledge Script Groups? (NETIQKB42620)

  • 7742620
  • 02-Feb-2007
  • 17-Feb-2011

Environment

NetIQ AppManager 6.x

Situation

How do I properly setup a cluster with 'AMAdmin_SetResDependency' to use Knowledge Script Groups?
How do I properly setup a cluster with 'AMAdmin_SetResDependency' to use Monitoring Policies?

Resolution

Change in AppManager 6.0:

In AppManager 6.0, the need for the KSG Identifier number (ie. 2203) has been removed. Now, the requirement is the prefix of any script that will be used to monitor clustered resources.

Note:  In AppManager 6.0, the AMAdmin_SetResDependency has been changed to accept only one KS script category at a time.  Within the script's Values Tab parameters, the Description states:  "KS Script Category (sql,exchange...)", but this is not correct.  The script will not properly set a resource dependency with more than one KS script category entered.

AppManager 6.0 Example:

   KSG group name: TestKSG_MiscScripts

  KSG Group Identifier: 2203

  KS's included in this KSG: SQL_CPUUtil, IIS_HealthCheck, General_MachineDown

  Note:  AMAdmin_SetResDependency will need to be dropped three times for each KS Script Category to properly set the resource dependency.

 

AMAdmin_SetResDependency script #1 Values Tab:

   Knowledge Script Category: SQL

   Required Available Resources: e:  (Which  is not available on the agent)

 

AMAdmin_SetResDependency script #2 Values Tab:

   Knowledge Script Category: IIS

   Required Available Resources: e:  (Which  is not available on the agent)

 

AMAdmin_SetResDependency script #3 Values Tab:

   Knowledge Script Category: General

   Required Available Resources: e:  (Which  is not available on the agent)   

  1. Drop the KSG TestKSG_MiscScripts on the agent. 
  2. Open Netiqctrl from the Operator Console.
  3. Go to the Extensions menu and run the command: profile servername netiqmc.
  4. Jobs will display as: 2203:SQL_CPUUtil, 2203:IIS_HealthCheck, 2203:General_MachineDown.
  5. Job status will be Running (Inactive) since the resource, E: drive, is not available on the node that the scripts were dropped on.
  6. Open Netiqctrl and run the command:  listrsc servername netiqmc.  This will list all resources that have been set for the agent and what their status is (Active or Inactive).

Example:

NetIQctrl> listrsc sassafrass netiqmc

---------------------
     RSC Info
-----------------------

<RSC #1> :
        Name       =>  SQL
        JobCnt     =>  1
        Status     =>  Inactive
        ResDepend  =>  e:
        SvcDepend  =>

 

<RSC #2> :
        Name       =>  IIS
        JobCnt     =>  1
        Status     =>  Inactive
        ResDepend  =>  e:
        SvcDepend  =>

 

<RSC #3> :
        Name       =>  General
        JobCnt     =>  1
        Status     =>  Inactive
        ResDepend  =>  e:
        SvcDepend  =>


NetIQctrl>

What does this ultimately mean?

You no longer need to be concerned with setting the AMAdmin_SetResDependency with KSG Identifier numbers or names. You only need to set the Knowledge Script Category parameter to script prefixes of scripts that are inside the KSG (ie. IIS, SQL, NT , or a Prefix created by copying scripts.

Additional Information

Formerly known as NETIQKB42620

AMAdmin_SetResDependency is used primarily on clustered servers. It tells the agents on the two (or more) nodes of the cluster which particular resources (drive letter or service name) must be availableto actively run a specific group of scripts.