This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088
for more information about troubleshooting BMC products in containers.
In 7.6.04 you can apply SP5 which resolves the issue.
Versions 8.0 and 8.1 do not have fixes as of today. The architecture of the AIS plugin has changed in these versions, shitfing from a regular plugin to an ARDBC plugin. This means the plugin has a local cache, if the user logs into server 1 and starts a simulation, and later on he tried to add a new CI to the simulation, but this time server 2 got the request, the server 2 plugin will not know how to process the request.
To work-around this limitation in AIS you need to reconfigure your AIS plugin entries in the ar.cfg files of all your servers in the group so that they all point to the same server, then only one server in the server group will handle the AIS actions:
In 7.6.04SP4 or below:
Server-Plugin-Alias: AIS.FILTERAPI AIS.FILTERAPI <OnlyServerTakingAISRequests>:9556
So for ex. if I have a Server Group with Server 1 and Server 2. I chose Server 2 to take all AIS requests.
As such I edit the ar.cfg in server 1 and modify the line to look like this:
Server-Plugin-Alias: AIS.FILTERAPI AIS.FILTERAPI SERVER2:9556
In 8.x or above the plugin alias looks like this:
Server-Plugin-Alias: BMC.ARDBC.ATRIUM.AIS BMC.ARDBC.ATRIUM.AIS <OnlyServerTakingAISRequests>:9556
- BMC Atrium CMDB Suite