<?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: HPE 1950 change management VLAN in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/hpe-1950-change-management-vlan/m-p/7059521#M34067</link>
    <description>&lt;P&gt;AFAIK the HPE OfficeConnect 1950 Switch Series hasn't a dedicated Management VLAN (where with Management VLAN I mean a VLAN that is used for Management, it is not routeable and it is generally identified by - that's default - the Primary VLAN of the switch...which is, by default, equal to VLAN id 1)...as it is usual to find on ArubaOS-Switch based Switch Series.&lt;/P&gt;&lt;P&gt;So (a) the default&amp;nbsp;&lt;STRONG&gt;VLAN through which you manage the Switch&lt;/STRONG&gt; is (pardon: by default) the VLAN id 1...and, at the same time, any (b) other VLAN id with an assigned IP Address (a SVI) and reacheable should be able to be used as the VLAN through which you manage the Switch (that highligth the fact there isn't a VLAN ids which is really "dedicated")...clearly you should be able to gain access locally if you connect to an access port member of that specific VLAN id or if, remotely, there is a trunk port (here trunk means a port that carry several tagged VLAN ids) on which that VLAN id is transported (permitted)..&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 22 Aug 2019 13:05:48 GMT</pubDate>
    <dc:creator>parnassus</dc:creator>
    <dc:date>2019-08-22T13:05:48Z</dc:date>
    <item>
      <title>HPE 1950 change management VLAN</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hpe-1950-change-management-vlan/m-p/7059489#M34066</link>
      <description>&lt;P&gt;Hi all, we have two HPE OfficeConnect 1950 12XGT 4SFP+ Switch&amp;nbsp; (JH295A) Switches and i want to change the management vlan. I can't find any related topic on the manual. Is this possible? How to achive it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance, George&lt;/P&gt;</description>
      <pubDate>Thu, 22 Aug 2019 09:14:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hpe-1950-change-management-vlan/m-p/7059489#M34066</guid>
      <dc:creator>George Mandiliotis</dc:creator>
      <dc:date>2019-08-22T09:14:24Z</dc:date>
    </item>
    <item>
      <title>Re: HPE 1950 change management VLAN</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hpe-1950-change-management-vlan/m-p/7059521#M34067</link>
      <description>&lt;P&gt;AFAIK the HPE OfficeConnect 1950 Switch Series hasn't a dedicated Management VLAN (where with Management VLAN I mean a VLAN that is used for Management, it is not routeable and it is generally identified by - that's default - the Primary VLAN of the switch...which is, by default, equal to VLAN id 1)...as it is usual to find on ArubaOS-Switch based Switch Series.&lt;/P&gt;&lt;P&gt;So (a) the default&amp;nbsp;&lt;STRONG&gt;VLAN through which you manage the Switch&lt;/STRONG&gt; is (pardon: by default) the VLAN id 1...and, at the same time, any (b) other VLAN id with an assigned IP Address (a SVI) and reacheable should be able to be used as the VLAN through which you manage the Switch (that highligth the fact there isn't a VLAN ids which is really "dedicated")...clearly you should be able to gain access locally if you connect to an access port member of that specific VLAN id or if, remotely, there is a trunk port (here trunk means a port that carry several tagged VLAN ids) on which that VLAN id is transported (permitted)..&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Aug 2019 13:05:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hpe-1950-change-management-vlan/m-p/7059521#M34067</guid>
      <dc:creator>parnassus</dc:creator>
      <dc:date>2019-08-22T13:05:48Z</dc:date>
    </item>
  </channel>
</rss>

