How does a change in the IP address of the console affect data transfer and data collection? Are there any steps that need to be done in advance of the change to ensure smooth operation over the IP address or machine transition?
This document was originally published as Solution SLN000000221086.
Changing the IP address of the console has no negative impact on Manager in BMC Perform. Data collection and data transfer should work properly on all days, including the day the IP address of the console is changed.
There are a few areas where a console IP address change will have some impact. These include:
Changing the IP address of the console has no negative impact on Manager in BMC Perform. Data collection requests made before the IP address change will successfully transfer data to the console after the IP address change since the console initiates the transfer request to the remote agent. For the most part there should be no impact on Manager or normal data collection and data transfer if the IP address of the console is changed.
By default Manager issues collection requests at 11:30 PM (30 minutes before the specified start time of data collection on the remote node). That means the new IP address should be set by that time. Also, the IP address of the console should not be changed during the Transfer Duration (the period of time when Manager will be transferring data).
The primary concern in Investigate is that the IP Address of the console is used as an 'Access Control' for who can deactive an active policy on a remote node. That means that all Investigate policies should be deactivated before the console IP address is changed. If there are active policies on a remote node running under the old IP address they would be difficult to deactivate after the IP address of the console was changed since it would require manual intervention on the remote nodes themselves.
Better handling of a console IP address change in Investigate has been requested in Request #502978.
When the IP address changes old policy files would no longer have their status icons updated (they would remain in the last state before the IP address change). Also open Investigate drill down and graphs would stop updating.
The Perform Agent on the remote node will attempt to send status messages to the Perform Console if there is a change in the status of data collection on the remote node. The status messages are sent to the last console to issue a collection request to the remote node. During the transition period of the console IP address the remote agent may try to send a status message back to the Perform console. This will fail (because the IP address has changed) so the Perform Agent will queue that message request and retry again later. This will repeat until the message is accepted by the console at that IP address (which is impossible because the console IP has changed) or until the Perform Agent is stopped and restarted.
This can cause some minor issues such as:
Generally these messages are harmless but they may occur when the console IP address changes.
To resolve this issue simply stop and restart the Perform Agent on the remote nodes that are still trying to communicate with the console.
The IP address of the console is used as an 'Access Control' for who can stop an active data collection request. On the day that the IP address changes it will not be possible to stop a running collection request from the console. This is typically an infrequent occurrence anyway so its unlikely this will present a problem. Once the new collection request has been sent under the new console IP address the console will once again be able to stop running collection requests before their expected end time by a manual stop request.