Increased Network Traffic Noticed after Running the AMAdmin_SetPrimaryMS Knowledge Script (NETIQKB3139)

  • 7703139
  • 02-Feb-2007
  • 11-Nov-2010

Environment

AppManager 6.x
AppManager 7.0.x
No Secondary Management Server Configured for the AppManager Agent
AMAdmin_SetPrimaryMS Knowledge Script

Situation

Increased Network Traffic Noticed after Running the AMAdmin_SetPrimaryMS Knowledge Script

Resolution

To clear the Local Repository of the multiple entries in the CMComm table, cold start the NetIQ Services.

NOTE: Use -oa in place of -o for the NetIQ AppManager Client Communications Manager Service.

To correctly deploy the AMAdmin_SetPrimaryMS knowledge script in a multiple AppManager Management Server environment for "fail-over":

  • Primary Management Server:
    • New Primary Host Name: Specify the name of the primary AppManager Management Server.
    • MS to Change: Specify 1 to only change the primary AppManager Management Server.
  • Secondary Management Server:
    • New Backup MS Host Name: Specify the name of the secondary AppManager Management Server.
    • MS to Change: Specify 2 to only change the secondary AppManager Management Server.
  • Primary and Secondary Management Servers:
    • New Primary Host Name: Specify the name of the primary AppManager Management Server.
    • New Backup MS Host Name: Specify the name of the secondary AppManager Management Server.
    • MS to Change: Specify 3 to change both AppManager Management Servers.

Cause

AMAdmin_SetPrimaryMS has been run on some or all AppManager Agents in the site with the "MS to Change" value set to 2 but no secondary Management Server specified.
A blank value is inserted into the CMComm table on the Local Repository of the AppManager Managed Client (or Agent) if there is no secondary AppManager Management Server specified and the value for "MS to Change" is set to 2 in the AMAdmin_SetPrimaryMS knowledge script. This causes the AppManager Managed Client to attempt to communicate to the unspecified secondary AppManager Management Server when communications are down with the primary AppManager Management Server resulting in increased network traffic.

Additional Information

Formerly known as NETIQKB3139

After executing the AMAdmin_SetPrimaryMS knowledge script with the correct values for both the Primary and Secondary AppManager Management Servers, the AppManager Managed Clients will poll both AppManager Management Servers to verify their availability.

If the primary Management Server is not available, the AppManager Managed Client will communicate with the secondary Management Server until the primary Management Server becomes available.