NSX Intelligence - Recommendations are not being sent for IPV6 traffic
Article ID: 317746
Updated On:
Products
VMware NSX
Issue/Introduction
Symptoms:
- After updating IP discovery profile for a network segment to include IPV6 addresses, the recommendation service doesn't send recommendations for IPV6 traffic.
- Recommendation service is not be able to send recommendations for newly discovered IP addresses even when ND Snooping, DHCP Snooping - IPv6, VMware Tools - IPv6 are enabled.
- After updating IP discovery profile for a network segment to include IPV6 addresses, the recommendation service doesn't send recommendations for IPV6 traffic.
- Recommendation service is not be able to send recommendations for newly discovered IP addresses even when ND Snooping, DHCP Snooping - IPv6, VMware Tools - IPv6 are enabled.
Cause
nsx-pace agent runs as part of NSX manager nodes responsible for forwarding any discovered IPs from VM update messages to Intelligence streams.
These update messages are cached internally. For any subsequent update, the current VM update message is compared with the cached VM update message which was previously streamed to Intelligence. To perform this check, all fields of the current VM update message are compared with the corresponding fields in the cached data.
The Discovered IP field of VM update messages was not being considered during this comparison, so updates for discovered IPs were being ignored.
These update messages are cached internally. For any subsequent update, the current VM update message is compared with the cached VM update message which was previously streamed to Intelligence. To perform this check, all fields of the current VM update message are compared with the corresponding fields in the cached data.
The Discovered IP field of VM update messages was not being considered during this comparison, so updates for discovered IPs were being ignored.
Resolution
The issue has been fixed in NSX 4.1.0. Upgrading NSX version to 4.1.0 will resolve this problem.
Workaround:
Restart the proton service on NSX Manager nodes (which nsx-pace agent is part of) will push all current states of VMs, including discovered IPs, without performing any comparison with cached data. This can be used as a workaround for this problem. It has to be noted that a restart will only synchronize current state of NSX with Intelligence. After performing the restart, any further update in discovered IPs may not be streamed to Intelligence.
Use the following command on NSX manager nodes to restart the proton service:
systemctl restart proton
Workaround:
Restart the proton service on NSX Manager nodes (which nsx-pace agent is part of) will push all current states of VMs, including discovered IPs, without performing any comparison with cached data. This can be used as a workaround for this problem. It has to be noted that a restart will only synchronize current state of NSX with Intelligence. After performing the restart, any further update in discovered IPs may not be streamed to Intelligence.
Use the following command on NSX manager nodes to restart the proton service:
systemctl restart proton
Additional Information
Impact/Risks:
The Recommendation Service of NSX Intelligence will not be able to send recommendations for IPV6 IPs even if the IP Discovery profile is updated to include IPV6 addresses and ND Snooping, DHCP Snooping - IPv6, VMware Tools - IPv6 are enabled.
The Recommendation Service of NSX Intelligence will not be able to send recommendations for IPV6 IPs even if the IP Discovery profile is updated to include IPV6 addresses and ND Snooping, DHCP Snooping - IPv6, VMware Tools - IPv6 are enabled.
Feedback
Yes
No
Powered by
