Use this Knowledge Script to set or change the primary or secondary management server for version 8.1.0.11 or earlier UNIX agents, or to change the port number of the primary or secondary management server.
To change the management server designation for a version 7.5 UNIX agent, use NetIQ UNIX agent Manager. For more information, see the UNIX Agent Manager online Help.
This Knowledge Script allows you to explicitly designate a primary and a secondary management server and therefore explicitly control the communication between the managed UNIX clients and the management servers authorized to communicate with those managed clients. This Knowledge Script allows you to specifically assign a single primary management server for specified UNIX agents. Once you have identified a primary management server, the UNIX agent sends all information to that computer.
To help ensure communication is maintained even if the primary management server goes down, you can also use this Knowledge Script to explicitly designate a secondary or backup management server for the managed client. If the primary management server for the managed client fails, the backup management server takes over communication with the managed client until communication with the primary management server is restored.
If the target UNIX agent computer does not have the specified management server defined in the configuration file (NqmComms.xml), the agent adds it to the configuration file and then sets the flags according to the value you set for the Select the management server operation to perform parameter.
If you run the job from a management server computer, be aware that the job can only set a primary or backup management server when the specified management server is associated with the same repository. For example, Management Server A for Repository 1 cannot specify that Management Server B for Repository 2 should now become the primary or backup management server for Repository 1.
NOTE:When you install the UNIX agent, you implicitly establish a primary management server and can use this Knowledge Script to change the primary management server or designate a secondary management server. We recommend, however, that you explicitly designate the primary and secondary management servers by running this Knowledge Script twice.
The first time you run the job, you should identify the primary management server. After you receive notification that setting the management server has been successful, you can run the script a second time to set the secondary management server. You can also use this Knowledge Script to remove a management server for a target UNIX agent.
UNIX computer icon
By default, this script is only run once for each computer.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Event if job succeeds? (y/n) |
Set to y to raise events that indicate whether the management server configuration succeeded. The default is y. |
|
Event if job fails? (y/n) |
Set to y to raise events that indicate whether the management server configuration was not successful. When this parameter is enabled, a failure in the configuration of the management server raises a severe event. The default is y. |
|
Management server hostname or IP address |
Enter the name or IP address of the management server you want to set as a primary or secondary management server or that you want to remove for a UNIX agent. Keep in mind that you should set the primary management server first, then rerun this script to set the secondary management server or to make any changes to either the primary or secondary management server. NOTE:Although you can specify the management server by hostname or IP address, based on how you have your site configured, the event detail message always identifies the computer by IP address. |
|
Management server operation to perform |
Select the appropriate option for the management server you have specified.
NOTE:If the target computer does not have the specified management server defined in its configuration file (NqmComms.xml), the UNIX agent adds it to the configuration file and then sets the flags according to the value you set here. The default is Set primary. |
|
Port number for the management server |
Type the port number you want to use on the management server for communications from UNIX agents. The port number should be the same port you specified when you installed the management server or the port number you have set for the UNIX port in the management server registry. NOTE:If you have changed the port number for UNIX agents in the management server registry, run this script to set the new port number on your UNIX agents, then restart the management server to restore communication. The default is 9001. |
|
Event severity when job succeeds |
Set the event severity level, from 1 to 40, to indicate the importance of the event when setting the management server succeeds. The default severity level is 25. |
|
Event severity when job fails |
Set the event severity level, from 1 to 40, to indicate the importance of the event when setting the management server fails. The default severity level is 5. |
When you establish a primary management server for a managed client, that management server becomes the only management server that the managed client communicates with for a single repository/management server configuration. A secondary or backup management server can also be defined for each managed client in case the primary management server fails. The secondary management server only communicates with the managed client when the primary management server is unavailable. When communication with the primary management server resumes, the managed client resumes exclusive communication with the primary management server.
Because a multiple management server environment is chiefly intended for failover functionality (to provide an alternative management server if the primary management server fails), each managed client can have one primary management server and one backup management server for each repository.