<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>SDMP on Matt Allford</title><link>https://www.mattallford.com/tags/sdmp/</link><description>Recent content in SDMP on Matt Allford</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 30 Oct 2017 11:23:45 +0000</lastBuildDate><atom:link href="https://www.mattallford.com/tags/sdmp/index.xml" rel="self" type="application/rss+xml"/><item><title>vRealize Operations Service Discovery Management Pack</title><link>https://www.mattallford.com/vrealize-operations-service-discovery-management-pack/</link><pubDate>Mon, 30 Oct 2017 11:23:45 +0000</pubDate><guid>https://www.mattallford.com/vrealize-operations-service-discovery-management-pack/</guid><description>&lt;p&gt;For those that weren&amp;rsquo;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 &lt;a href="https://virtualtassie.com/2017/vmware-infrastructure-navigator-end-of-support/"&gt;another post&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If you are not aware of what vRealize Infrastructure Navigator (VIN) was, it was a tool that was part of VMware&amp;rsquo;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.&lt;/p&gt;</description></item><item><title>VMware Infrastructure Navigator End of Support</title><link>https://www.mattallford.com/vmware-infrastructure-navigator-end-of-support/</link><pubDate>Mon, 30 Oct 2017 11:21:25 +0000</pubDate><guid>https://www.mattallford.com/vmware-infrastructure-navigator-end-of-support/</guid><description>&lt;p&gt;Blink and you will miss it! For those that weren&amp;rsquo;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.&lt;/p&gt;
&lt;p&gt;As per the &lt;a href="https://kb.vmware.com/s/article/2151075?language=en_US"&gt;VMware KB article&lt;/a&gt; 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 &lt;a href="https://marketplace.vmware.com/vsx/solutions/vrealize-operations-service-discovery-management-pack"&gt;Service Discovery Management Pack&lt;/a&gt;. If you are already on vSphere 6.5, VIN will not work so your only option is to use the SDMP.&lt;/p&gt;</description></item></channel></rss>