Failure to get VSMAgentID from NSX for Deep Security Virtual Appliance

- Updated:
- 26 Sep 2017
- Product/Version:
- Deep Security 10.0
- Deep Security 10.1
- Deep Security 9.5
- Deep Security 9.6
- Platform:
- N/A N/A

Summary

There are instances when NSX cannot get the VSMAgent-ID. The table entries for VSMAgentID remain blank in the Deep Security Manager database.

Details

To resolve the issue, update to the latest version of Deep Security.

Test Now

Rating:

Category:

Troubleshoot

Solution Id:

1118342

Feedback

Did this article help you?

Thank you for your feedback!

What was the problem with this article?

The image(s) in the article did not display properly.

The article did not provide detailed procedure.

The article is hard to understand and follow.

The video did not play properly.

The article did not resolve my issue.

Others. Please specify.

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:

We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

Thanks for voting.

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:

We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.