- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2017 01:56 PM
Hello,
Quick question regarding Discovery schedule.
Scenario : I have configured a discovery schedule, left 'Behavior' field blank, Updated 'Mid Server' filed with 'PROD MID SERVER1' which is up and running.
Findings : When I ran this discovery schedule, I verified ECC Queue, interestingly I found PROD MID SERVER1 AND PROD MID SERVER2 are showing up in agents list.
Question : When I specify only 'PROD MID SERVER1' for 'Mid Server' field in Discovery schedule, how come PROD MID SERVER2 also participated ?
Thank you
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2017 10:35 AM
The Cluster is the top level, any discovery setup to run by a single cluster member will use all MIDs in that cluster for that discovery. Scheduled Discoveries don't really see the cluster, so it makes it easier in my opinion to setup a large discovery schedule just by picking out one MID from the cluster.
I have 3 hosts with 9 MIDs so I've striped 3 load balanced clusters across the 3 hosts.
Host1 - MID1, MID2, MID3
Host2 - MID4, MID5, MID6
Host3 - MID7, MID8, MID9
Cluster1 - MID1, MID4, MID7
Cluster2 - MID2, MID5, MID8
Cluster3 - MID3, MID6, MID9
This setup gives me redundancy against host issues so that scheduled discoveries still have a chance to complete if 1 host is down. All discoveries are setup to use the 1st MID in the cluster.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2017 02:13 PM
Interesting, so you didn't setup MID Clusters?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2017 07:26 AM
I did Mid Servers clustered, But in Discovery schedule, I just specified server1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2017 07:40 AM
That is expected behavior for a load balanced MID cluster. You can test it by breaking the cluster and running your discovery again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2017 09:24 AM
Hi Jeff,
Thank you for info,
Cluster 1 - Server 1 & 2
Cluster 2 - Server 3 and 4
All four Mid servers associated with capabilities.
Scenario 1 : If I configure Discovery Schedule with 'Server 1' and ran the discovery schedule, what are all clusters and associated mid servers will be involved in Discovery ? How Discovery schedule related to which cluster?
Thanks
Ravi
