<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Need bug id and url for velocloud Interface error issue in VeloCloud Discussions</title>
    <link>https://communities.vmware.com/t5/VeloCloud-Discussions/Need-bug-id-and-url-for-velocloud-Interface-error-issue/m-p/2916056#M17</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Need bug id and url for velocloud Interface error issue&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Symptoms&lt;/P&gt;&lt;P&gt;When you go to the remote diagnostic and hit on the Interfaces status you will get an error.&lt;/P&gt;&lt;P&gt;Cause&lt;/P&gt;&lt;P&gt;When you go to the remote diagnostic and hit on the Interfaces status you will get an error.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Impact/Risks&lt;/P&gt;&lt;P&gt;During any tshooting, Interace status won't show up which may delay in resolution&lt;/P&gt;&lt;P&gt;Resolution&lt;/P&gt;&lt;P&gt;A fix for issue included in 4.3 and above&lt;/P&gt;&lt;P&gt;Workaround&lt;/P&gt;&lt;P&gt;the workaround is to reboot the edges&lt;/P&gt;</description>
    <pubDate>Mon, 27 Jun 2022 07:44:47 GMT</pubDate>
    <dc:creator>mahendraparnami</dc:creator>
    <dc:date>2022-06-27T07:44:47Z</dc:date>
    <item>
      <title>Need bug id and url for velocloud Interface error issue</title>
      <link>https://communities.vmware.com/t5/VeloCloud-Discussions/Need-bug-id-and-url-for-velocloud-Interface-error-issue/m-p/2916056#M17</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Need bug id and url for velocloud Interface error issue&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Symptoms&lt;/P&gt;&lt;P&gt;When you go to the remote diagnostic and hit on the Interfaces status you will get an error.&lt;/P&gt;&lt;P&gt;Cause&lt;/P&gt;&lt;P&gt;When you go to the remote diagnostic and hit on the Interfaces status you will get an error.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Impact/Risks&lt;/P&gt;&lt;P&gt;During any tshooting, Interace status won't show up which may delay in resolution&lt;/P&gt;&lt;P&gt;Resolution&lt;/P&gt;&lt;P&gt;A fix for issue included in 4.3 and above&lt;/P&gt;&lt;P&gt;Workaround&lt;/P&gt;&lt;P&gt;the workaround is to reboot the edges&lt;/P&gt;</description>
      <pubDate>Mon, 27 Jun 2022 07:44:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VeloCloud-Discussions/Need-bug-id-and-url-for-velocloud-Interface-error-issue/m-p/2916056#M17</guid>
      <dc:creator>mahendraparnami</dc:creator>
      <dc:date>2022-06-27T07:44:47Z</dc:date>
    </item>
    <item>
      <title>Re: Need bug id and url for velocloud Interface error issue</title>
      <link>https://communities.vmware.com/t5/VeloCloud-Discussions/Need-bug-id-and-url-for-velocloud-Interface-error-issue/m-p/2916080#M18</link>
      <description>&lt;P&gt;Your thread has been reported to moderators, it needs moving since it is not about a vSphere security advisory.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Jun 2022 08:49:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VeloCloud-Discussions/Need-bug-id-and-url-for-velocloud-Interface-error-issue/m-p/2916080#M18</guid>
      <dc:creator>scott28tt</dc:creator>
      <dc:date>2022-06-27T08:49:25Z</dc:date>
    </item>
  </channel>
</rss>

