<?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 Re: SD-WAN Always On in DevNet Sandbox</title>
    <link>https://community.cisco.com/t5/devnet-sandbox/sd-wan-always-on/m-p/4039987#M4465</link>
    <description>Hey there, yes this can happen. The AO sandbox gets a lot of use and as such sometimes, things stop working for a brief moment. The ENG team has automation in place so that if the UI/API becomes unresponsive this is reset. For more reliable and consistent use i would use the reservable sd-wan sandbox or the one in the multi-ios virl sandbox.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.</description>
    <pubDate>Wed, 04 Mar 2020 09:09:44 GMT</pubDate>
    <dc:creator>bigevilbeard</dc:creator>
    <dc:date>2020-03-04T09:09:44Z</dc:date>
    <item>
      <title>SD-WAN Always On</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/sd-wan-always-on/m-p/4039691#M4460</link>
      <description>&lt;P&gt;I am receiving timeout errors when trying to access the always-on SD-WAN sandbox via the www frontend, api, or viptela sdk.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The same actions work fine if I use the reservable SD-WAN sandbox.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am also not connected to VPN while trying to access the always-on sandbox.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 22:06:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/sd-wan-always-on/m-p/4039691#M4460</guid>
      <dc:creator>jeffshively</dc:creator>
      <dc:date>2020-03-03T22:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: SD-WAN Always On</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/sd-wan-always-on/m-p/4039721#M4461</link>
      <description>&lt;P&gt;Update: The initial login page loads using port 8443:&amp;nbsp;&lt;A href="https://sandboxsdwan.cisco.com:8443/#/banner" target="_blank"&gt;https://sandboxsdwan.cisco.com:8443/#/banner&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, after I enter the credentials the next page is&amp;nbsp;&lt;A href="https://sandboxsdwan.cisco.com/index.html" target="_blank"&gt;https://sandboxsdwan.cisco.com/index.html&lt;/A&gt;&amp;nbsp;(notice the :8443 is gone).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I manually change the URL to&amp;nbsp;&lt;A href="https://sandboxsdwan.cisco.com:8443/index.html" target="_blank"&gt;https://sandboxsdwan.cisco.com:8443/index.html&lt;/A&gt;. It loads and everything is fine from there.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I am wondering if the initial redirection without the port 8443 is causing the issue with webpage and the sdk.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 22:37:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/sd-wan-always-on/m-p/4039721#M4461</guid>
      <dc:creator>jeffshively</dc:creator>
      <dc:date>2020-03-03T22:37:09Z</dc:date>
    </item>
    <item>
      <title>Re: SD-WAN Always On</title>
      <link>https://community.cisco.com/t5/devnet-sandbox/sd-wan-always-on/m-p/4039987#M4465</link>
      <description>Hey there, yes this can happen. The AO sandbox gets a lot of use and as such sometimes, things stop working for a brief moment. The ENG team has automation in place so that if the UI/API becomes unresponsive this is reset. For more reliable and consistent use i would use the reservable sd-wan sandbox or the one in the multi-ios virl sandbox.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.</description>
      <pubDate>Wed, 04 Mar 2020 09:09:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-sandbox/sd-wan-always-on/m-p/4039987#M4465</guid>
      <dc:creator>bigevilbeard</dc:creator>
      <dc:date>2020-03-04T09:09:44Z</dc:date>
    </item>
  </channel>
</rss>

