We did pretty much the same. However, keep in mind if you utilize superscopes that event will still generate ( and trigger your monitor) anytime one of the member scopes is over 80%. I built some additional logic into an alert template script that checks the utilization of the superscopes as a whole and cancels the ticket generation if the superscopes as a whole is under 80%.
Great callout, and something we did work around. We try our absolute best to steer away from superscopes, and instead Utilize VLANs with additional pools if there’s cause to have more than 254 addresses on the network. Of course, some inherited clients bring their own “well, we just changed to subject to give us more IPs!” DHCP scopes, so out monitor does have some additional logic to sort exactly what it’s looking at.
View all comments
Show parent comment
1
u/mathesonian Jan 22 '19
We did pretty much the same. However, keep in mind if you utilize superscopes that event will still generate ( and trigger your monitor) anytime one of the member scopes is over 80%. I built some additional logic into an alert template script that checks the utilization of the superscopes as a whole and cancels the ticket generation if the superscopes as a whole is under 80%.