Network Management
Engine shows a critical status on the HA deployment summary
This article covers what to check for if one of your servers is showing a critical status on the HA summary page.
First published date
4/30/2020 3:38 PM
Last published date
2/11/2025 12:50 AM
Overview
After an upgrade, you may notice that server shows a critical status but is still updating the database. This can occur even if you have not configured HA Pools.
Product section
Network Performance Monitor
Cause
There may be multiple potential causes:
- Required ports for HA are not open on Firewall
- Issues updating DNS
- Issues updating NIC (assigning Virtual IP address) - Add manually the VIP IP on the Tcp IP Properties on the Active Server
Resolution
1. Please check SolarWinds High Availability requirements especially validate the Network and Port requirements.
2. Verify the required ports are open in all your firewall policies that are in place (for example public and domain).
3. If the requirements are fulfilled then check the HA logs (c:\ProgramData\SolarWinds\Logs\HighAvailability\HighAvailability.Service.log) for errors/warnings on the member server that has critical status on the page and apply the fix or check other logs. Some example errors are shown below:
An instance when some Orion services are failing - this requires further investigation and checking of relevant logs, in this case, Syslog and Traps services logs.
An instance when Virtual IP address (VIP) can not be assigned to the NIC - this requires the system/server administrator to check the issue as it is external to the Orion and only identified by Orion HA.
2. Verify the required ports are open in all your firewall policies that are in place (for example public and domain).
3. If the requirements are fulfilled then check the HA logs (c:\ProgramData\SolarWinds\Logs\HighAvailability\HighAvailability.Service.log) for errors/warnings on the member server that has critical status on the page and apply the fix or check other logs. Some example errors are shown below:
An instance when some Orion services are failing - this requires further investigation and checking of relevant logs, in this case, Syslog and Traps services logs.
', UserFriendlyMessage='Orion engine resource is critical due to unexpected engine services status. Service 'SolarWindsSyslogService' has expected status Running but the real is Stopped Service 'SolarWindsTrapService' has expected status Running but the real is Stopped ' }
An instance when Virtual IP address (VIP) can not be assigned to the NIC - this requires the system/server administrator to check the issue as it is external to the Orion and only identified by Orion HA.
LOCAL POOL SNAPSHOT:
[..]
PoolMembers:
NAME-1-AdditionalPoller, Status: Critical, PreferredStatus: Up/Rev:1/Timestamp:11-11-2021 01:02:03.123, ReasonOfFail: ResourceFail/Rev:3, StatusMessage: 'The IP address x.x.x.x is not present on the member.'
[..]
Resources:
Local resources:
HA.VirtualIpResource.x.x.x.x, CurrentStatus: NotRunning/Rev:1, PrefferedStatus: Up/Rev:1, LocalCurrentStatus:NotRunning, LocalPreferredStatus:Up