Data Center Security

 View Only
  • 1.  DCS:S vCenter is not linked to vShield

    Posted Jan 29, 2016 01:57 AM

    Has anyone come across this issue?  I'm trying to add vCenter & vShield to the DCS UMC and I always get the error: "vCenter is not linked to vShield".

    Background:

    Data Center Security:Server 6.6.0.251
    vCenter 6-2776511
    vShield 5.5.4-2673026

    vShield Manager was registered with vCenter.  All objects appear in vShield Manager and vCenter thick client has vShield tabs and data.  Deployed vShield Endpoints to all ESXi Hosts via vShield Manager successfully.  No errors in vShield Manager.

    Able to log into DCS UMC and everything appears good.  License is installed as well.  Added self-generated root CA for UMC to my trusted root certificate authorities.  

    Tried adding vCenter/vShield to DCS with various username/passwords including using administrator@vsphere.local and vShield built in admin account.  Everytime I am able to authenticate to vCenter/vShield no problem but get the error "vCenter is not linked to vShield" which it clearly is.  

    Any suggestions on what I can look for?  I've had a ticket open with Symantec support for 12 days and don't seem to be getting any traction.

    Thanks!



  • 2.  RE: DCS:S vCenter is not linked to vShield

    Posted Feb 06, 2016 11:23 AM

    This sounds a little different issue than I had but, by chance do you have the SEP SVA Appliance installed on any of  these esxi hosts? In my environment, we had the SEP SVA installed on the hosts and we couldnt register the DCS SVA appliances. The fix was to uninstall the SEP SVA using their command line utility and then the DCS SVA installed successfully.

     

    Thanks,

      David Ramazetti

      dramazetti@novacoast.com

      Senior Engineer

      http://www.novacoast.com



  • 3.  RE: DCS:S vCenter is not linked to vShield

    Posted Feb 25, 2016 01:14 AM

    In vShield Manager, if you register the vCenter Server by hostname it gives this error. Because you have to register the devices via IP Address in UMC, it looks for a matching IP Address, not the hostname. If only there was a solution that resolved hostnames to IP addresses, then we could all use hostnames instead and it wouldn't matter if the IP address changed.