A warning message is logged every 30 seconds "CM plugin status not found for <CM UUID>, plugin may not be running on this node." on 2 Manager node
search cancel

A warning message is logged every 30 seconds "CM plugin status not found for <CM UUID>, plugin may not be running on this node." on 2 Manager node

book

Article ID: 384007

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • You configure 3 node Manager cluster.
  • On 2 Manager nodes out of 3, you see a warning message is logged every 30 seconds.

    /var/log/cm-inventory/cm-inventory.log
    <Timestamp>  WARN inventoryTasksScheduler4 CmInventoryService 84750 FABRIC [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="cm-inventory"] CM plugin status not found for <CM UUID>, plugin may not be running on this node.

    /var/log/syslog
    <Timestamp> <Hostname> NSX 84750 FABRIC [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="cm-inventory"] CM plugin status not found for <CM UUID>, plugin may not be running on this node.

  • If you have multiple compute managers configured, the warning is logged for each compute manager on 2 Manager node.
    • The nodes may vary by compute manager.

Environment

VMware NSX 4.x

Cause

It is the current design that the warning is logged every 30 seconds on 2 Manager nodes out of 3.

For each compute manager, one NSX Manager is assigned to fetch inventory information.
The warning is logged on the other 2 nodes.

The assigned Manager nodes may vary by compute manager and can change as sharding changes.

Resolution

If the warning for a specific compute manager is logged on 2 Manager nodes out of 3, it's harmless and can be ignored.

Additional Information

Please contact Broadcom support in cases below which are unexpected.

  • The warning is logged for a specific compute manager on all the Manager nodes at the same time.
  • The warning is NOT logged for a specific compute manager on 2 or more Manager nodes at the same time.
    • It's fine that the warning for different compute managers are logged on different 2 Manager nodes.