<?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 800-Series Inband Management Fails or is Unreliable in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/800-series-inband-management-fails-or-is-unreliable/m-p/40769#M20</link>
    <description>Article ID: 15043 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
800-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Deploying an 800-Series switch within a network which already contains at least one 800-Series switch. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Can't contact the host IP address. &lt;BR /&gt;
Switch host does not respond to inband communication, or initially responds and then hangs. &lt;BR /&gt;
Inband host management protocols (e.g. Webview (aka Web User Interface or WEB UI), Telnet, SSH, SNMP, PING) are nonfunctional or unreliable. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
This product is configured with default IP address 192.168.10.1, using default subnet mask 255.255.255.0. &lt;BR /&gt;
&lt;BR /&gt;
As such, it requires no serial management session before it may be managed inband. Simply connect a managing device (having a unique IP address within the 192.168.10.x subnet) via one of the ethernet ports, then open the host management session. &lt;BR /&gt;
&lt;BR /&gt;
&lt;I&gt;However&lt;/I&gt;, if such a unit is placed into a network which already contains at least one unit of the same IP address, then management of all such units in this environment will be problematic due to the presence of duplicate IP addresses. This is the root cause of the observed symptoms. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Functions as Designed (FAD). &lt;BR /&gt;
&lt;BR /&gt;
Default IP address 192.168.10.1 is for initial IP contact with the switch host. This IP address should be changed to a more suitable unique value as soon as possible, to avoid the possiblity of duplicate IP addresses as multiple units are deployed now or in the future. &lt;BR /&gt;
&lt;BR /&gt;
It is expected that the immediate result of such a change will be loss of the current inband connection ("Destination Host Unreachable" or "Request timed out")(&lt;A href="http://bit.ly/1Cvc3Zq" target="_blank" rel="nofollow noreferrer noopener"&gt;5621&lt;/A&gt;). Simply change the managing device's IP address to match the switch's new IP subnet (though not its full IP address), or set up a default gateway in order to connect to it from a different subnet. In either case, inband communication should again be supported. &lt;BR /&gt;
&lt;BR /&gt;
Also see this 800-Series &lt;A href="https://www.youtube.com/watch?v=bVHsEs_noVQ&amp;amp;#38;list=PLvQMiI4QwvHTFYkDRLl_8NUE8Ijp5Zm8n&amp;amp;#38;index=37" target="_blank" rel="nofollow noreferrer noopener"&gt;HowTo Video&lt;/A&gt; which demonstrates the configuration of a management IP address. &lt;BR /&gt;
Also see this 800-Series &lt;A href="https://www.youtube.com/watch?v=fbopokg27fg&amp;amp;#38;list=PLvQMiI4QwvHTFYkDRLl_8NUE8Ijp5Zm8n&amp;amp;#38;index=35" target="_blank" rel="nofollow noreferrer noopener"&gt;HowTo Video&lt;/A&gt; which demonstrates how to enable SSH, not enabled by default.</description>
    <pubDate>Wed, 06 Nov 2013 00:05:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-06T00:05:00Z</dc:date>
    <item>
      <title>800-Series Inband Management Fails or is Unreliable</title>
      <link>https://community.extremenetworks.com/t5/faqs/800-series-inband-management-fails-or-is-unreliable/m-p/40769#M20</link>
      <description>Article ID: 15043 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
800-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Deploying an 800-Series switch within a network which already contains at least one 800-Series switch. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Can't contact the host IP address. &lt;BR /&gt;
Switch host does not respond to inband communication, or initially responds and then hangs. &lt;BR /&gt;
Inband host management protocols (e.g. Webview (aka Web User Interface or WEB UI), Telnet, SSH, SNMP, PING) are nonfunctional or unreliable. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
This product is configured with default IP address 192.168.10.1, using default subnet mask 255.255.255.0. &lt;BR /&gt;
&lt;BR /&gt;
As such, it requires no serial management session before it may be managed inband. Simply connect a managing device (having a unique IP address within the 192.168.10.x subnet) via one of the ethernet ports, then open the host management session. &lt;BR /&gt;
&lt;BR /&gt;
&lt;I&gt;However&lt;/I&gt;, if such a unit is placed into a network which already contains at least one unit of the same IP address, then management of all such units in this environment will be problematic due to the presence of duplicate IP addresses. This is the root cause of the observed symptoms. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Functions as Designed (FAD). &lt;BR /&gt;
&lt;BR /&gt;
Default IP address 192.168.10.1 is for initial IP contact with the switch host. This IP address should be changed to a more suitable unique value as soon as possible, to avoid the possiblity of duplicate IP addresses as multiple units are deployed now or in the future. &lt;BR /&gt;
&lt;BR /&gt;
It is expected that the immediate result of such a change will be loss of the current inband connection ("Destination Host Unreachable" or "Request timed out")(&lt;A href="http://bit.ly/1Cvc3Zq" target="_blank" rel="nofollow noreferrer noopener"&gt;5621&lt;/A&gt;). Simply change the managing device's IP address to match the switch's new IP subnet (though not its full IP address), or set up a default gateway in order to connect to it from a different subnet. In either case, inband communication should again be supported. &lt;BR /&gt;
&lt;BR /&gt;
Also see this 800-Series &lt;A href="https://www.youtube.com/watch?v=bVHsEs_noVQ&amp;amp;#38;list=PLvQMiI4QwvHTFYkDRLl_8NUE8Ijp5Zm8n&amp;amp;#38;index=37" target="_blank" rel="nofollow noreferrer noopener"&gt;HowTo Video&lt;/A&gt; which demonstrates the configuration of a management IP address. &lt;BR /&gt;
Also see this 800-Series &lt;A href="https://www.youtube.com/watch?v=fbopokg27fg&amp;amp;#38;list=PLvQMiI4QwvHTFYkDRLl_8NUE8Ijp5Zm8n&amp;amp;#38;index=35" target="_blank" rel="nofollow noreferrer noopener"&gt;HowTo Video&lt;/A&gt; which demonstrates how to enable SSH, not enabled by default.</description>
      <pubDate>Wed, 06 Nov 2013 00:05:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/800-series-inband-management-fails-or-is-unreliable/m-p/40769#M20</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-06T00:05:00Z</dc:date>
    </item>
  </channel>
</rss>

