Agent ID on server and node mismatch

In the event that the agent ID on the server and the node do not match, you may see error messages that refer to "agent ID mismatch", and you will notice communication problems between the managed node and the management server. This can occur if you delete a node and then add it back again.

If you know the correct agent ID, open the Node Configuration Editor and type it in the Modify Agent ID box in the Advanced Configuration dialog box. If you do not know the agent ID, you can correct an agent ID mismatch with this procedure:

To correct an agent ID mismatch

1. As a user with administrative privileges, stop the agent using this command:

   opcagt -kill

2. On the managed node, delete the files:
   • On AIX: /var/lpp/OV/conf/OpC/agentid
     and if present: /var/lpp/OV/conf/OpC/managedNodeId.txt
   • On HP-UX, Linux, Sun Solaris, and Tru64 UNIX: /var/opt/OV/conf/OpC/agentid
     and if present: /var/opt/OV/conf/OpC/managedNodeId.txt
   • On Windows: %OvAgentDir%\conf\OpC\agentid
     and if present: %OvAgentDir%\conf\OpC\managedNodeId.txt
3. On the managed node, delete the OPC_AGENT_ID<agentGUID> from the nodeinfo file using a text editor. The nodeinfo file is located in conf/OpC/nodeinfo.

   For example, you would delete the text OPC_AGENT_ID617a0010g90f-71d7-0666-0f0899d4000 up to the carriage return symbol. Do not delete the OPC_NODE_TYPE that appears after the carriage return symbol or any text that follows the OPC_NODE_TYPE.

4. As a user with administrative privileges, restart the agent using this command:

   opcagt -start

5. On the management server, open the Node Configuration editor and select the node with the mismatched agent ID. Right-click the node and select Properties General Advanced Configuration. In the dialog box, select Modify Agent ID, then remove the agent ID.
6. Deploy any policy to the managed node. A new agent ID will be created.

Handling of messages with no or an empty agent ID

If the node name or IP address of the node matches a node that is known to the management server, messages are accepted even if they have no agent ID or if the agent ID is set to null. This may be the case if older versions of the agent are attempting to send messages to the management server. This behavior can be changed by modifying values in the Server Configuration dialog box.

In the console tree, right-click Operations Manager, and then click ConfigureServer.... The Server Configuration dialog box opens.

In the namespace Message Action Server Message Filter, you can change the following values:

• Discard messages with empty agent ID
  If this value is set to TRUE, all messages that come from an agent that does not yet have an agent ID assigned are discarded. The default value is FALSE.
• Discard messages with no agent ID
  If this value is set to TRUE, all messages that come from an old agent (for example VPO 5.x, VPO 6.x, VPW 6.x) that has no agent ID functionality are discarded. The default value is FALSE.
• Allow actions in messages with no agent ID
  If this value is set to TRUE, all messages coming from an old agent (for example VPO 5.x, VPO 6.x, VPW 6.x) are not preprocessed. That means, the operator-initiated and the automatic commands being part of the message will not be removed. The default value is FALSE.