The table explains system event messages for the Fabric system events.

Event Code

Event Severity

Alarm Triggered

Event Message

Description

250000

Informational

No

Deployment unit old operational status was {#} , new operational status is {#} and old progress state was {#}, new progress state is {#}. Check alarm string for root cause.

Information-only event.

250001

Informational

No

A deployment unit has been created.

Information-only event.

250002

Informational

No

A deployment unit in NSX has been updated. Fabric services will be updated on the cluster.

Information-only event.

250003

Informational

No

A deployment unit has been deleted from NSX.

Information-only event.

250004

High

Yes

Failed to deploy service {#} on host {#} since datastore (#) is not connected to the host. Please verify that it is connected, or provide a different datastore.

The datastore where you store security virtual machines for the host could not be configured.

Action: Confirm the host can reach the datastore.

250005

High

Yes

Installation of deployment unit failed. Please confirm OVF/VIB URLs are accessible, DNS is configured, and required network ports are open.

ESXi host failed to access VIBs/OVFs from NSX during an NSX service installation on host. In the vCenter system events table, you see: Event Message:'Installation of deployment unit failed. Please confirm OVF/VIB URLs are accessible, DNS is configured, and required network ports are open.', Module:'Security Fabric'.

Action: Refer to NSX Troubleshooting Guide.

250006

Informational

No

The fabric agent for network fabric services installed successfully on a host.

Information-only event.

250007

Informational

No

The fabric agent was removed successfully from a host.

Information-only event.

250008

High

Yes

Location of OVF / VIB files has changed. Service must be redeployed.

NSX VIBs and OVFs are available via a URL which differs across NSX versions. To find the correct VIBs, you must go to https://<NSX-Manager-IP>/bin/vdn/nwfabric.properties. If the NSX Manager IP address changes, the NSX OVF or VIB may need to be redeployed.

Action: Click the Resolveoption on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.

250009

High

Yes

Upgrade of deployment unit failed. Please confirm OVF/VIB URLs are accessible, DNS is configured, and required network ports are open.

EAM has failed to access VIBs/OVFs from NSX during a host upgrade. In the vCenter system events table, you see: Event Message:'Upgrade of deployment unit failed. Please confirm OVF/VIB URLs are accessible, DNS is configured, and required network ports are open.', Module:'Security Fabric'.

Action: Refer to NSX Troubleshooting Guide.

250012

High

Yes

Following service(s) need to be installed successfully for Service {#} to function: {#}.

The service being installed is dependent on another service that has not been installed yet.

Action: Deploy the required service on the cluster.

250014

High

Yes

Error while notifying security solution before upgrade. The solution may not be reachable/responding. Ensure that solution urls are accessible from NSX. Use resolve API to resolve the Alarm. Service will be redeployed.

Error while notifying security solution before upgrade. The solution may not be reachable/responding.

Action: Ensure that solution URLs are accessible from NSX. Use the action=resolve parameter in the systemalarms API to resolve the alarm. Service will be redeployed.

250015

High

Yes

Did not receive callback from security solution for upgrade notification even after timeout. Ensure that solution urls are accessible from NSX, and NSX is reachable from the solution. Use resolve API to resolve the Alarm. Service will be redeployed.

Did not receive callback from security solution for upgrade notification even after timeout.

Action: Ensure that solution URLs are accessible from NSX, and NSX is reachable from the solution. Use the action=resolve parameter in the systemalarms API to resolve the alarm.

250016

High

No

Uninstallation of service failed. Ensure that solution urls are accessible from NSX, and NSX is reachable from the solution. Use resolve API to resolve the Alarm. Service will be removed.

Uninstallation of service failed.

Action: Ensure that solution URLs are accessible from NSX, and NSX is reachable from the solution. Use the action=resolve parameter in the systemalarms API to resolve the alarm.

250017

High

Yes

Error while notifying security solution before uninstall. Resolve to notify once again, or delete to uninstall without notification. Ensure that solution urls are accessible from NSX, and NSX is reachable from the solution. Use resolve API to resolve the Alarm. Service will be removed.

Error while notifying security solution before uninstall. Resolve to notify once again, or delete to uninstall without notification.

Action: Ensure that solution URLs are accessible from NSX, and NSX is reachable from the solution. Use the action=resolve parameter in the systemalarms API to resolve the alarm.

250018

High

Yes

Error while notifying security solution before uninstall.Resolve to notify once again, or delete to uninstall without notification. Ensure that solution urls are accessible from NSX, and NSX is reachable from the solution. Use resolve API to resolve the Alarm. Service will be removed.

Error while notifying security solution before uninstall. Resolve to notify once again, or delete to uninstall without notification.

Action: Ensure that solution URLs are accessible from NSX, and NSX is reachable from the solution. Use the action=resolve parameter in the systemalarms API to resolve the alarm.

250019

High

Yes

Server rebooted while security solution notification for uninstall was going on. Ensure that solution urls are accessible from NSX. Use resolve API to resolve the Alarm. Service will be uninstalled.

Server was rebooted while security solution notification for uninstall was in progress.

Action: Ensure that solution URLs are accessible from NSX. Use the action=resolve parameter in the systemalarms API to resolve the alarm. Service will be uninstalled.

250020

High

Yes

Server rebooted while security solution notification for upgrade was going on. Ensure that solution urls are accessible from NSX. Use resolve API to resolve the Alarm. Service will be redeployed.

Server was rebooted while security solution notification for upgrade was in progress.

Action: Ensure that solution URLs are accessible from NSX. Use the action=resolve parameter in the systemalarms API to resolve the alarm. Service will be redeployed.

250021

Critical

No

NSX Manager relies on the EAM service in vCenter for deploying/monitoring NSX vibs on ESX. The connection to this EAM service has gone down. This could be due to EAM service or vCenter restart/stop or an issue in the EAM service. Verify that vCenter is up, and the EAM service in vCenter is running. Further, we can look at EAM mob to verify that EAM is functioning as expected.

NSX Manager relies on the EAM service in vCenter for deploying/monitoring NSX VIBs on ESX. The connection to this EAM service is down. This could be due to EAM service or vCenter has restarted/stoped or an issue in the EAM service.

Action: Verify that vCenter is up and that the EAM service in vCenter is running. Verify that the EAM MOB URL http://{vCenter_IP}/eam/mob/ is accessible and EAM is functioning as expected. For more information, refer to "Infrastructure Preparation" in the NSX Troubleshooting Guide.

250022

Critical

No

NSX Manager relies on the EAM service in VC for deploying/monitoring NSX vibs on ESX. The connection to this EAM service has gone down. This could be due to EAM service or VC restart/stop or an issue in the EAM service. Verify that VC is up, and the EAM service in VC is running. Further, we can look at EAM mob to verify that EAM is functioning as expected.

NSX Manager relies on the EAM service in vCenter for deploying/monitoring NSX VIBs on ESX. The connection to this EAM service is down. This could be due to EAM service or vCenter has restarted/stoped or an issue in the EAM service.

Action: Verify that vCenter is up and that the EAM service in vCenter is running. Verify that the EAM MOB URL http://{vCenter_IP}/eam/mob/ is accessible and EAM is functioning as expected. For more information, refer to "Infrastructure Preparation" in the NSX Troubleshooting Guide.

250023

High

Yes

Pre Uninstall cleanup failed. Use resolve API to resolve the Alarm. Service will be removed.

Internal cleanup tasks prior to uninstallation failed to complete.

Action: Use the action=resolve parameter in the systemalarms API to resolve the alarm. Service will be removed.

250024

High

Yes

The backing EAM agency for this deployment unit could not be found. It is possible that the VC services may still be initializing. Please try to resolve the alarm to check existence of the agency. In case you have deleted the agency manually, please delete the deployment unit entry from NSX.

EAM deploys VIBs onto ESXi hosts. An EAM agency is installed on each NSX-prepared cluster. If this agency cannot be found, the vCenter Server services may be initializing or the agency was deleted manually in error.

250025

High

Yes

This event is generated when an attempt is made to upgrade or uninstall NSX vibs on stateless host using EAM. All stateless host should be prepared using the auto deploy feature. Fix configuration using auto deploy feature, and use the resolve API to resolve the alarm.

This event is generated when an attempt is made to upgrade or uninstall NSX VIBS on the stateless host using EAM. All stateless host should be prepared using the Auto Deploy feature.

Action: Fix configuration using the Auto Deploy feature, and use the action=resolve parameter in the systemalarms API to resolve the alarm.