<?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: APC products not accessible through HTTP / Telnet when moved to Meraki in Cloud Networking Platform</title>
    <link>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441444#M10272</link>
    <description>&lt;P&gt;No restrictions set on the APC interface. I have some sites where the APC's function properly after being moved to Meraki and some that don't. I'll identify current firmware and upgrade it to latest version and let everyone know what happens. &lt;/P&gt;</description>
    <pubDate>Sat, 01 Sep 2018 23:54:35 GMT</pubDate>
    <dc:creator>RobakaWoody</dc:creator>
    <dc:date>2018-09-01T23:54:35Z</dc:date>
    <item>
      <title>APC products not accessible through HTTP / Telnet when moved to Meraki</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441442#M10270</link>
      <description>&lt;P&gt;Has anyone ever encountered a problem accessing the APC UPS/PDU web interface after having moved the devices from a Cisco Catalyst environment onto Meraki? The IP addresses of the APC's were changed when moved to Meraki and the devices respond to PING requests but management capabilities are unavailable except for console access. Also, when I place the APC's back on the Catalyst switches with their old addresses they are once again accessible.&lt;/P&gt;&lt;P&gt;I'm thinking maybe APC firmware upgrade is in order but just thought I'd ask to see what kind of feedback i receive.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Sep 2018 22:48:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441442#M10270</guid>
      <dc:creator>RobakaWoody</dc:creator>
      <dc:date>2018-09-01T22:48:18Z</dc:date>
    </item>
    <item>
      <title>Re: APC products not accessible through HTTP / Telnet when moved to Meraki</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441443#M10271</link>
      <description>&lt;P&gt;Have you configured an IP address restriction in the APC interface?&lt;/P&gt;&lt;P&gt;I would be tempted to factory reset the APC management card and set it up again from scratch using the new IP addressing.  And yes, a firmware update wouldn't hurt.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Sep 2018 23:08:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441443#M10271</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2018-09-01T23:08:15Z</dc:date>
    </item>
    <item>
      <title>Re: APC products not accessible through HTTP / Telnet when moved to Meraki</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441444#M10272</link>
      <description>&lt;P&gt;No restrictions set on the APC interface. I have some sites where the APC's function properly after being moved to Meraki and some that don't. I'll identify current firmware and upgrade it to latest version and let everyone know what happens. &lt;/P&gt;</description>
      <pubDate>Sat, 01 Sep 2018 23:54:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441444#M10272</guid>
      <dc:creator>RobakaWoody</dc:creator>
      <dc:date>2018-09-01T23:54:35Z</dc:date>
    </item>
    <item>
      <title>Re: APC products not accessible through HTTP / Telnet when moved to Meraki</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441445#M10273</link>
      <description>&lt;P&gt;It might sound too obvious, but your default gateway is good/correct to route back and forth to wherever you are trying  to access it from? &lt;/P&gt;</description>
      <pubDate>Sun, 02 Sep 2018 03:42:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441445#M10273</guid>
      <dc:creator>Brandon Svec</dc:creator>
      <dc:date>2018-09-02T03:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: APC products not accessible through HTTP / Telnet when moved to Meraki</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441446#M10274</link>
      <description>&lt;P&gt;&lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/11654"&gt;@RobakaWoody&lt;/A&gt; you mentioned IP's have changed, this this because the network topology has changed? I suspect as mentioned your APC cards have IP filtering enabled for web access. If you can ping them its not an incorrect gateway otherwise you wouldn't get a response. &lt;/P&gt;&lt;P&gt;We use a bunch of these cards and haven't had any issues after we installed Meraki MS units, I would say something with your config change on the card hasn't gone to plan. &lt;/P&gt;&lt;P&gt;Use your console cable to login to the cards and confirm their settings, if they look right but are still not working as Phil mentioned I would factory reset them&lt;/P&gt;</description>
      <pubDate>Sun, 02 Sep 2018 21:54:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/apc-products-not-accessible-through-http-telnet-when-moved-to/m-p/5441446#M10274</guid>
      <dc:creator>BlakeRichardson</dc:creator>
      <dc:date>2018-09-02T21:54:19Z</dc:date>
    </item>
  </channel>
</rss>

