MID Server pause The MID server can be put into a Paused state to temporarily prevent it from polling the ECC Queue for work or sending Discovery results back to the instance. You might want to pause the MID Server when your network infrastructure is undergoing changes. This prevents applications like Discovery from throwing errors during a particular maintenance window. A paused MID Server continues processing commands that it had already retrieved before it was paused. When you resume the MID Server, the MID Server starts retrieving new commands to process. Note: Discovery continues to assign jobs to MID Servers that are Paused. MID Servers that are Down are not assigned jobs. Unlike stopping the MID Server from the Windows or Linux server command line on the MID Server machine, pausing the MID server is something that you can do from the instance. The MID Server pause feature is available starting with the Istanbul release. Note: You can only pause validated MID Servers. You can still perform these actions when the MID Server is paused: Access the MID Server logs and delete log entries. View MID server statistics. While the MID Server is in the Paused state it stops generating statistics. But you can still view the statistics generated before you paused the MID Server. Retrieve the MID Server thread dump. Make and save configuration changes and property changes to the server. The changes take effect after the MID Server is resumed. Clear the ECC queue. The MID server heartbeat continues to function while the MID Server is in the Paused state. If the MID Server is upgraded while it is in the Paused state, the MID Server state automatically changes to Up after successful upgrade. It does not return to the Paused state. During MID Server selection, paused MID Server can still be selected but are prioritized below MID Servers that are not paused. Events that occur during MID Server pause The vCenter and SNMP event collectors, continue to run and process events when you pause the MID Server. These events are not part of the normal synchronous communication that the MID Server has with the instance that you see in the ECC queue. Events are still relayed to the instance and can even trigger actions on records in the instance, such as a CI update. For example, if vCenter detects that a virtual machine goes down or is deleted, a vCenter event makes a change to the status of the corresponding CI record for that virtual machine. To prevent these events from being processed, stop the extensions from running. See: Configure and run the vCenter event collector Configure the SNMP Trap Collector Extension Pause the MID ServerPause the MID Server to temporarily prevent it from polling the ECC Queue for work or sending Discovery results back to the instance.