Notifications

29 views

Description

After a Clone, a Discovery Schedule for a Specific MID Server, which does not exist in the target instance and so is now a broken reference, will still run in a random MID Server.
The MID Server field of the Discovery Schedule record will contain a value, although it is a broken reference due to all MID Servers having unique sys_ids and being specific to instances.

This causes cause performance problems on sub-prod instances where Discovery will be run in MID Servers that are not set up or intended for Discovery, or cause performance issues on the network/target devices due to unwanted discoveries running.

Steps to Reproduce

  1. Install Discovery and a MID Server, in the instance that is to be the source of the clone (usually Production)
  2. Create a scheduled daily Discovery Schedule, set to run with the above Specific MID Server
  3. Clone that instance to another instance (usually Dev).
  4. That schedule will have been copied during the clone. It will run, and pick a random MID Server, even though the schedule is set to only run in the specified MID Server.

The expected behaviour is that the Discovery starts and immediately completes without launching Shazzam, because the specified MID Server does not exist.

Workaround

This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

The workaround to guarantee the issue does not happen after a clone is to shut down all clone target MID Servers before the clone. Discovery Schedules can be made inactive immediately after the clone, or configured to use equivalent clone target instance MID Servers.


Related Problem: PRB1311068

Seen In

Kingston Patch 7
SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - Audit Management PA Content - Madrid 2019 Q1
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Policy and Compliance PA Content - Madrid 2019 Q1
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - Risk Management PA Content - Madrid 2019 Q1
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Security Incident Response UI Patch - London 2019 Q2 v.6.2.3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - SIR - Threat intelligence - New York 2019 Q3
SR - VR - Solution Management Madrid Q2
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Fixed In

New York

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-12-10 01:20:59
Published:2019-12-10