VMware Cloud Community
gbihc
Contributor
Contributor

Error "failed to send request to vix agent" publishing rule

We're running vShield Edge v5 and have found now getting the following error when attempting to publish new rules:

"failed to send request to vix agent"

From the research I've done, I can't find any trace of what the root reason for this error to how to address it. Has anyone else?

5 Replies
Texiwill
Leadership
Leadership

Hello,

There may be a problem with your per VM hardening settings. Did you disable VIX for the firewalls? That is an isolation setting. You may also need to reboot the Edge.

Best regards,
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009-2016

Author of the books 'VMWare ESX and ESXi in the Enterprise: Planning Deployment Virtualization Servers', Copyright 2011 Pearson Education. 'VMware vSphere and Virtual Infrastructure Security: Securing the Virtual Environment', Copyright 2009 Pearson Education.

Virtualization and Cloud Security Analyst: The Virtualization Practice, LLC -- vSphere Upgrade Saga -- Virtualization Security Round Table Podcast

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
tjurgens
Enthusiast
Enthusiast

Do you mean the error listed here:

https://kb.vmware.com/kb/2060542

You will need to go through those steps outlined there.  I have a Sev 1 ticket opened with VMware about this, as it happened to me again yesterday.  I am looking for a more permanent fix.

gbihc
Contributor
Contributor

Thanks for the suggestion, but turned out that rebooting the vShield Manager as well as the Edge resolved this.

Reply
0 Kudos
gbihc
Contributor
Contributor

Thanks for that, but no. Was simply a case as it turns out of rebooting the Edge as well as the Manager appliance/VM

Reply
0 Kudos
tjurgens
Enthusiast
Enthusiast

Lucky.  Sometimes you can get around it by editing your vCenter Server connection in the Configuration -> General tab and entering the password again. 


There is often multiple ways to tackle this kind of sync loss, but the nuclear option is that KB I linked above.


FYI - This is fixed in NSX 6.1.3+.

Reply
0 Kudos