naveensingh43 ✭✭✭✭✭

Thanks @mariefab

super👌 @i_like_eggs

Thanks for update @bmrad

Yes, in SolarWinds, if you're monitoring BGP neighbor status using SNMP traps, you can automatically clear the alert when the BGP session is re-established, but it depends on how the alert is configured. Configure the alert with: Trigger Condition: BGP Neighbor State = Down (or trap indicating BGP Down) Reset Condition:…

Thanks, @mariefab. Looking forward to it.

Amazing work

Extremely good

For BGP monitoring in SolarWinds, the best practice is to use both Polling and Traps, but Polling should be the primary monitoring method. Traps are best used as a supplement for real-time notifications. Please flow the below document Network Routing Insights: Routing neighbors

Extremely good

Restart the SolarWinds Job Engine Service Check Polling Engine Load Balance Compare with other APEs. Verify node distribution. Ensure discoveries and polling assignments are balanced. Open support case with SolarWinds

Amazing @i_like_eggs

Impressive

Global Search does not search device serial numbers. To support serial number lookups, a Custom Query Table widget can be created to display device details along with their serial numbers.

Did you look the below link might be helpful for you. Cisco Meraki Secure SD-WAN SNMP or API-based monitoring for Meraki devices Cisco Meraki switches

if yes try restoring DB server first.

Did you take DB backup before upgrade?

If the existing account has sufficient privileges, there is no requirement to create a separate SQL user specifically for the installation. Once the environment is stable, configure the SQL MI Failover Group.

Verify all SolarWinds services are running. Try to restart them

Recommend opening a SolarWinds Support case for further investigation.

Registered and excited to be a part of it.

Registered and excited to be a part of it.

Happy August Mission Day! 😎

Awesome👏🏻

Could you check the Log Viewer and identify the SNMP trap generated for the Avamar backup failure? The document below can be used as a reference for configuring the corresponding alerts in SolarWinds. View logs and events with the Log Viewer

Warning: ≥ 80%, Critical: ≥ 90%

Thanks for keeping me informed.

When you're planning to reboot all the servers, please follow the recommended reboot sequence.

We experienced the same issue. However, after performing a manual reboot and following the recommended reboot sequence, the issue was resolved. We haven't encountered it again since then.

Try to reboot it manually.Ensure the reboot order is correct: SQL Server Main Poller Additional Polling Engines Web Server

Do the servers reboot automatically after the update?