The table explains system event messages related to messaging of major, critical, or high severity.

Event Code

Event Severity

Alarm Triggered

Event Message

Description

390001

High

Yes

Host messaging configuration failed.

The NSX message bus is set up after host preparation once ESX Agent Manager (EAM) has notified NSX that NSX VIBs have been successfully installed on an ESXi host. This event indicates that the message bus setup on the host failed. Starting with NSX 6.2.3, a red error icon is shown next to the affected host on the Installation > Host Preparation tab.

Action: For troubleshooting steps, refer to NSX Troubleshooting Guide.

390002

High

Yes

Host messaging connection reconfiguration failed.

In certain situations where NSX finds the RMQ broker details have changed, NSX tries to send the latest RMQ broker information to the host. If NSX fails to send the information, this alarm is raised.

Action: For troubleshooting steps, refer to NSX Troubleshooting Guide.

390003

High

Yes

Host messaging configuration failed and notifications were skipped.

NSX will try to set up messaging channel again when a prepared host connects back to vCenter Server. This event indicates that setup failed and that other NSX modules dependent on the messaging channel were not notified.

Action: For troubleshooting steps, refer to NSX Troubleshooting Guide.

391002

Critical

No

Messaging infrastructure down on host.

Two or more heartbeat messages between NSX Manager and an NSX host were missed.

Action: For troubleshooting steps, refer to NSX Troubleshooting Guide.

321100

Critical

No

Disabling messaging account {account #}. Password has expired.

An ESXi host, NSX Edge VM, or USVM acting as a message bus client has not changed its rabbit MQ password within the expected period of two hours after initial deployment or host preparation.

Action: Investigate a communication issue between NSX Manager and the message bus client. Verify the client is running. Before performing a re-sync or redeploy, collect the appropriate logs. For troubleshooting steps, refer to NSX Troubleshooting Guide.