<?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: I have received a few 'refurb' sr2148p switches.   After failing to connect to Hive in conventional means, I resorted to the CLI.  Still no connection.   Anybody able to help me find the problem? in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/i-have-received-a-few-refurb-sr2148p-switches-after-failing-to/m-p/64783#M2398</link>
    <description>&lt;P&gt;This guide reviews how to manually connect HiveOS devices to the HiveManager: &lt;A href="https://thehivecommunity.aerohive.com/s/article/CAPWAP-Guide-for-HiveManager-NG" alt="https://thehivecommunity.aerohive.com/s/article/CAPWAP-Guide-for-HiveManager-NG" target="_blank"&gt;https://thehivecommunity.aerohive.com/s/article/CAPWAP-Guide-for-HiveManager-NG&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since your device is showing connected securely, my best guess is that it has outdated information for the HiveManager address. The guide I've linked to reviews how find the HiveManager information for your instance and how to manually add that information to the AP via the CLI. It also reviews some troubleshooting steps to take if the device still will not connect for you. &lt;/P&gt;</description>
    <pubDate>Wed, 25 Sep 2019 21:15:16 GMT</pubDate>
    <dc:creator>samantha_lynn</dc:creator>
    <dc:date>2019-09-25T21:15:16Z</dc:date>
    <item>
      <title>I have received a few 'refurb' sr2148p switches.   After failing to connect to Hive in conventional means, I resorted to the CLI.  Still no connection.   Anybody able to help me find the problem?</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/i-have-received-a-few-refurb-sr2148p-switches-after-failing-to/m-p/64782#M2397</link>
      <description>&lt;P&gt;Here is the output from "Show capwap client"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CAPWAP client:&amp;nbsp;&amp;nbsp;Enabled&amp;nbsp;&lt;/P&gt;&lt;P&gt;CAPWAP transport mode:&amp;nbsp;UDP&lt;/P&gt;&lt;P&gt;RUN state: Connected securely to the CAPWAP server&amp;nbsp;&lt;/P&gt;&lt;P&gt;CAPWAP client IP:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;10.0.0.83&lt;/P&gt;&lt;P&gt;CAPWAP server IP:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;34.202.197.40&lt;/P&gt;&lt;P&gt;HiveManager Primary Name:cloud-va2-cws-8.aerohive.com&lt;/P&gt;&lt;P&gt;HiveManager Backup Name:&amp;nbsp;&lt;/P&gt;&lt;P&gt;CAPWAP Default Server Name: 34.202.197.40&lt;/P&gt;&lt;P&gt;Virtual HiveManager Name: XQCLFAXH&lt;/P&gt;&lt;P&gt;Server destination Port: 12222&lt;/P&gt;&lt;P&gt;CAPWAP send event:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Enabled&lt;/P&gt;&lt;P&gt;CAPWAP DTLS state:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Enabled&lt;/P&gt;&lt;P&gt;CAPWAP DTLS negotiation: Enabled&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;DTLS next connect status:&amp;nbsp;&amp;nbsp;Enable&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;DTLS always accept bootstrap passphrase: Enabled&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;DTLS session status: Connected&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;DTLS key type: passphrase&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;DTLS session cut interval:&amp;nbsp;&amp;nbsp;&amp;nbsp;5 seconds&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;DTLS handshake wait interval: 60 seconds&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;DTLS Max retry count:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;DTLS authorize failed:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;DTLS reconnect count:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;0&lt;/P&gt;&lt;P&gt;Discovery interval:&amp;nbsp;&amp;nbsp;&amp;nbsp;5 seconds&lt;/P&gt;&lt;P&gt;Heartbeat interval:&amp;nbsp;&amp;nbsp;&amp;nbsp;30 seconds&lt;/P&gt;&lt;P&gt;Max discovery interval: 10 seconds&lt;/P&gt;&lt;P&gt;Neighbor dead interval:105 seconds&lt;/P&gt;&lt;P&gt;Silent interval:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;15 seconds&lt;/P&gt;&lt;P&gt;Wait join interval:&amp;nbsp;&amp;nbsp;&amp;nbsp;60 seconds&lt;/P&gt;&lt;P&gt;Discovery count:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;0&lt;/P&gt;&lt;P&gt;Max discovery count:&amp;nbsp;&amp;nbsp;&amp;nbsp;3&lt;/P&gt;&lt;P&gt;Retransmit count:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;0&lt;/P&gt;&lt;P&gt;Max retransmit count:&amp;nbsp;&amp;nbsp;2&lt;/P&gt;&lt;P&gt;Primary server tries:&amp;nbsp;&amp;nbsp;0&lt;/P&gt;&lt;P&gt;Backup server tries:&amp;nbsp;&amp;nbsp;&amp;nbsp;0&lt;/P&gt;&lt;P&gt;Keepalives lost/sent:&amp;nbsp;&amp;nbsp;0/30788&lt;/P&gt;&lt;P&gt;Event packet drop due to buffer shortage: 0&lt;/P&gt;&lt;P&gt;Event packet drop due to loss connection: 23&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2019 19:09:55 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/i-have-received-a-few-refurb-sr2148p-switches-after-failing-to/m-p/64782#M2397</guid>
      <dc:creator>netadmin10</dc:creator>
      <dc:date>2019-09-25T19:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: I have received a few 'refurb' sr2148p switches.   After failing to connect to Hive in conventional means, I resorted to the CLI.  Still no connection.   Anybody able to help me find the problem?</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/i-have-received-a-few-refurb-sr2148p-switches-after-failing-to/m-p/64783#M2398</link>
      <description>&lt;P&gt;This guide reviews how to manually connect HiveOS devices to the HiveManager: &lt;A href="https://thehivecommunity.aerohive.com/s/article/CAPWAP-Guide-for-HiveManager-NG" alt="https://thehivecommunity.aerohive.com/s/article/CAPWAP-Guide-for-HiveManager-NG" target="_blank"&gt;https://thehivecommunity.aerohive.com/s/article/CAPWAP-Guide-for-HiveManager-NG&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since your device is showing connected securely, my best guess is that it has outdated information for the HiveManager address. The guide I've linked to reviews how find the HiveManager information for your instance and how to manually add that information to the AP via the CLI. It also reviews some troubleshooting steps to take if the device still will not connect for you. &lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2019 21:15:16 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/i-have-received-a-few-refurb-sr2148p-switches-after-failing-to/m-p/64783#M2398</guid>
      <dc:creator>samantha_lynn</dc:creator>
      <dc:date>2019-09-25T21:15:16Z</dc:date>
    </item>
  </channel>
</rss>

