Vrops

For those that weren’t aware, vRealize Infrastructure Navigator went End of Distribution (EOD) and End of Support Life (EOSL) at the end of September, 2017. Information on this is provided in another post. If you are not aware of what vRealize Infrastructure Navigator (VIN) was, it was a tool that was part of VMware’s vCloud Suite that discovered application dependencies and mapped network flow within a vSphere environment. VIN was deployed as a virtual appliance and then registered with vCenter Server. From there, VIN started mapping application dependencies using VMware Tools and the vCenter Server VIX API. ...

Blink and you will miss it! For those that weren’t aware, VMware disclosed a security vulnerability with the vCenter Server VIX API which has been patched, but this also impacted VMware Infrastructure Navigator (VIN) as it used the VIX API to build service mappings. As per the VMware KB article that announced this information, if you are running vSphere 5.5/6.0 you essentially have two options. Continue using VIN on an unpatched environment (not recommended), or use a new management pack for vROps that replaces VIN functionality called the Service Discovery Management Pack. If you are already on vSphere 6.5, VIN will not work so your only option is to use the SDMP. ...