<?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: Management addresses are not available in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/management-addresses-are-not-available/m-p/7116397#M34447</link>
    <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think more information would be helpful to better understand the configuration.&lt;/P&gt;&lt;P&gt;First of all you are not mentioning the switch model. Assuming that it is ArubaOS resp ProCurve switch but please provide exact model and firmware revision.&lt;/P&gt;&lt;P&gt;VLAN 1 is the management VLAN. Did you specify it as management VLAN with the CLI command management-vlan like this.&lt;/P&gt;&lt;PRE&gt;HP Switch (config)#: management-vlan 1&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I understand correctly both the core switch and the access switch have IPs in all VLANs, 1, 10, 11 and 12. Which switch is configured to do the inter VLAN routing? The core switch? Or the access switch is also routing? (show ip will show you if&amp;nbsp; IP routing is enabled or not)&lt;/P&gt;&lt;P&gt;If the access switch is not routing what is purpose of having IP addresses in all the VLANs. This is a bit unusual.&lt;/P&gt;&lt;P&gt;Depending on the answer of the previous question, the access switch should have an ip default-gateway or a static default route. ( show ip will show you the default gateway, show ip route will show you all the routes). Please provide information which VLAN is the outbound interface for the default gateway/route!&amp;nbsp;&lt;/P&gt;&lt;P&gt;In which VLAN is located the PC from which you are trying to reach the switch IP addresses? Is it in VLAN 1, 10, 11, 12? Or it is some VLAN/ip subnet which is not directly connected to the switches?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 07 Jan 2021 08:17:15 GMT</pubDate>
    <dc:creator>Emil_G</dc:creator>
    <dc:date>2021-01-07T08:17:15Z</dc:date>
    <item>
      <title>Management addresses are not available</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/management-addresses-are-not-available/m-p/7116198#M34443</link>
      <description>&lt;P&gt;&lt;SPAN class="grammar correction"&gt;I&lt;/SPAN&gt; think it is not a problem, more missing knowledge.&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;My situation&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;I &lt;SPAN class="grammar correction"&gt;have&lt;/SPAN&gt; a &lt;SPAN class="misspelling correction"&gt;core switch&lt;/SPAN&gt; with some &lt;SPAN class="error misspelling"&gt;vlans&lt;/SPAN&gt;. &lt;SPAN class="grammar correction"&gt;We&lt;/SPAN&gt; are using default &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt; 1 as management &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt;. &lt;SPAN class="error grammar"&gt;vlan&lt;/SPAN&gt; 1 is untagged on every &lt;SPAN class="error misspelling"&gt;uplinkport&lt;/SPAN&gt; to every &lt;SPAN class="misspelling correction"&gt;access switch&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;My config&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="misspelling correction"&gt;core switch&lt;/SPAN&gt; uplink: untagged: &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt; 1 &lt;SPAN class="error grammar"&gt;-&lt;/SPAN&gt; tagged: &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt; 10, 11, 12&lt;/P&gt;&lt;P&gt;access-switch: untagged: &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt; 1 &lt;SPAN class="error grammar"&gt;-&lt;/SPAN&gt; tagged: &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt; 10, 11, 12 &lt;SPAN class="error grammar"&gt;-&lt;/SPAN&gt; management &lt;SPAN class="error misspelling"&gt;ip&lt;/SPAN&gt; is active on every &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt; (DHCP)&lt;/P&gt;&lt;P&gt;&lt;SPAN class="error grammar"&gt;The&lt;/SPAN&gt; access-switch has 4 ip-addresses (one per &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt;), &lt;SPAN class="error grammar"&gt;i&lt;/SPAN&gt; can connect to every single ip-address until &lt;SPAN class="error grammar"&gt;i&lt;/SPAN&gt; remove the untagged &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt; 1 on one site of the connection. &lt;SPAN class="error grammar"&gt;in&lt;/SPAN&gt; that case, no &lt;SPAN class="error misspelling"&gt;ip-adress&lt;/SPAN&gt; is reachable. &lt;SPAN class="error grammar"&gt;all&lt;/SPAN&gt; clients behind the access-switch are still online, only the management-addresses from the switch are not longer available. &lt;SPAN class="grammar correction"&gt;When&lt;/SPAN&gt; &lt;SPAN class="error grammar"&gt;i&lt;/SPAN&gt; set &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt; 1 untagged again, all 4 &lt;SPAN class="misspelling correction"&gt;addresses&lt;/SPAN&gt; are directly available.&lt;/P&gt;&lt;P&gt;&lt;SPAN class="grammar correction"&gt;Im&lt;/SPAN&gt; wondering that all addresses are not available if &lt;SPAN class="error grammar"&gt;i&lt;/SPAN&gt; remove the untagged &lt;SPAN class="error misspelling"&gt;vlan&lt;/SPAN&gt; 1 and use only tagged &lt;SPAN class="error misspelling"&gt;vlans&lt;/SPAN&gt; on the &lt;SPAN class="error misspelling"&gt;uplinkport&lt;/SPAN&gt;. &lt;SPAN class="grammar correction"&gt;I&lt;/SPAN&gt; would expect that the other addresses are still online.&lt;/P&gt;&lt;P&gt;BTW: if &lt;SPAN class="error grammar"&gt;i&lt;/SPAN&gt; reboot the access-switch, it still receives on all 3 tagged &lt;SPAN class="error misspelling"&gt;vlans&lt;/SPAN&gt; &lt;SPAN class="grammar correction"&gt;an&lt;/SPAN&gt; address. My client is connected to the &lt;SPAN class="misspelling correction"&gt;core switch&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;Is that normal? &lt;SPAN class="grammar correction"&gt;Can&lt;/SPAN&gt; someone please explain &lt;SPAN class="grammar correction"&gt;to me&lt;/SPAN&gt; why this works like that?&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jan 2021 23:43:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/management-addresses-are-not-available/m-p/7116198#M34443</guid>
      <dc:creator>fghfgcdxfg</dc:creator>
      <dc:date>2021-01-05T23:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: Management addresses are not available</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/management-addresses-are-not-available/m-p/7116397#M34447</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think more information would be helpful to better understand the configuration.&lt;/P&gt;&lt;P&gt;First of all you are not mentioning the switch model. Assuming that it is ArubaOS resp ProCurve switch but please provide exact model and firmware revision.&lt;/P&gt;&lt;P&gt;VLAN 1 is the management VLAN. Did you specify it as management VLAN with the CLI command management-vlan like this.&lt;/P&gt;&lt;PRE&gt;HP Switch (config)#: management-vlan 1&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I understand correctly both the core switch and the access switch have IPs in all VLANs, 1, 10, 11 and 12. Which switch is configured to do the inter VLAN routing? The core switch? Or the access switch is also routing? (show ip will show you if&amp;nbsp; IP routing is enabled or not)&lt;/P&gt;&lt;P&gt;If the access switch is not routing what is purpose of having IP addresses in all the VLANs. This is a bit unusual.&lt;/P&gt;&lt;P&gt;Depending on the answer of the previous question, the access switch should have an ip default-gateway or a static default route. ( show ip will show you the default gateway, show ip route will show you all the routes). Please provide information which VLAN is the outbound interface for the default gateway/route!&amp;nbsp;&lt;/P&gt;&lt;P&gt;In which VLAN is located the PC from which you are trying to reach the switch IP addresses? Is it in VLAN 1, 10, 11, 12? Or it is some VLAN/ip subnet which is not directly connected to the switches?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2021 08:17:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/management-addresses-are-not-available/m-p/7116397#M34447</guid>
      <dc:creator>Emil_G</dc:creator>
      <dc:date>2021-01-07T08:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: Management addresses are not available</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/management-addresses-are-not-available/m-p/7118058#M34461</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2030436"&gt;@fghfgcdxfg&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;WIthout the information I asked for it would be difficult to give you a correct answer. I suspect that access switches are configured without IP routing and using a default-gateway in VLAN 1. The switch will use its default gateway for return traffic to hosts which are not in the management VLAN or any of the connected VLANs. If VLAN 1 is down the default-gateway is also not reachable.&lt;/P&gt;&lt;P&gt;Another possible scenario is that you have configured "management-vlan 1" which this command the switch restricts management access only to ports member of this VLAN. If you remove this VLAN the switch doesnt have ports which are members of the management VLAN and will block management access.&lt;/P&gt;&lt;P&gt;Please, if you still have the same issue, provide answers to my questions. If you were able to identify what is causing it and have fixed it, please share the solution for the benefit of the community users.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2021 08:51:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/management-addresses-are-not-available/m-p/7118058#M34461</guid>
      <dc:creator>Emil_G</dc:creator>
      <dc:date>2021-01-21T08:51:18Z</dc:date>
    </item>
  </channel>
</rss>

