Past week i did an implementation of VMware vShield with Kaspersky Security for Virtualization 3.0 Agentless Service Pack 1.
During deployment i ran into an issue where i kept an error on the SVM saying that it’s unable to create a connection between the ESX Module and the Kaspersky SVM appliances.
a connection between the esx module and the vshield endpoint solution, kaspersky security virtualization 3.0 agentless, failed.
This also only happend when you put a “protected” VM on that specific host.
All network pings from and to the KSV appliance went just right so it was getting even stranger..
From the KSV i could ping fine to the vShield Appliance and network.
After digging around i found out that the vmservice-vmnic-pg network defaults on 169.254.1.1 was in the same segment as the vMotion network was configured.
So what happend was that all ping and most of the communication worked fine but when the appliance wanted to communicate it went out via the vMotion NIC instead of staying local within vmservice-vmnic-pg network…
After changing the vMotion network on all hosts to 169.254.2.* all the appliances popped online and worked like a charm.
Did you ended up changed the seconds NIC to look at vmotion NIC instead?
Changing the second NIC, which was vmservice-vminc-pg to vmotion NIC?
Nah just changed the complete vmotion ip range of all hosts.