SpoofGuard failed tasks log spew with SpoofGuard disabled

Products

• VMware NSX

Issue/Introduction

• Multiple job with one failing task is generated every seconds by the NSX Manager.
• ARP snooping enable on all Cluster and Spoofguard is not enabled
• In vsm.log, you see errors similar to:

2017-02-22 18:08:50.806 CET INFO taskScheduler-4 SchedulerQueueServiceImpl:80 - The task AppNotificationHandler-162018 [id:task-973460] is added to the SchedulerQueue
2017-02-22 18:08:50.806 CET INFO pool-10-thread-1 ScheduleSynchronizer:48 - Start executing task: task-973460 and running executor threads 1
2017-02-22 18:08:50.809 CET INFO ViInventoryThread ViInventory:1329 - 2708/3596 objects published.
2017-02-22 18:08:50.811 CET INFO ViInventoryThread VimObjectBridge:954 - VimObjectBridge: Ending inventory update
2017-02-22 18:08:50.811 CET INFO ViInventoryThread VimObjectBridge:222 - Processing 1 updates and 0 deletions for this transaction
2017-02-22 18:08:50.813 CET INFO ViInventoryThread VimObjectBridge:227 - VimObjectBridge: Time taken to process transaction : 7
2017-02-22 18:08:50.813 CET INFO ViInventoryThread ViInventory:1692 - cleared the deleted objects set
2017-02-22 18:08:50.813 CET INFO ViInventoryThread ViInventory:1545 - Resolved, last version:154104 num vc objs:2278 num vimos:3596
2017-02-22 18:08:50.823 CET INFO TaskFrameworkExecutor-28 NotificationProcessor:406 - Processing Context domain-c19 : 0 rule updates, 0/0 container updates, 1 spoofguard updates.

Environment

VMware NSX Data Center for vSphere 6.x

Cause

This issue occurs when updates are being sent to the SpoofGuard but the task fails because SpoofGuard is not enabled.

Resolution

To resolve the issue, disable ARP Snooping or Enable SpoofGuard.

Note: The messages that are seen in logs are legitimate. If ARP Snooping is enabled, the new IPs would be discovered and Spoofguard message would be sent to the hypervisors. All the publishing messages are sent using the task framework.