<?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 5406zl - core pair stops working, when configuring empty spaces in VLAN Names in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/5406zl-core-pair-stops-working-when-configuring-empty-spaces-in/m-p/5526681#M30459</link>
    <description>&lt;P&gt;I have a pair of 5406zl&amp;nbsp; running firmware 15.05.0006. I know there is a newer Version availiable 15.06.0008, but I can't update so quickly.&lt;/P&gt;&lt;P&gt;we run about 20&amp;nbsp;distributed trunks on CU Modules.&lt;/P&gt;&lt;P&gt;I have a reproducable error, and maybe someone could confirm&amp;nbsp;it in a test-environment :&lt;/P&gt;&lt;P&gt;1. configure a vlan3, called "Server"&lt;/P&gt;&lt;P&gt;2. configure a vlan4, called "Server PROD"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ( With entering this both&amp;nbsp;switches stop working, console is lost. console to second core is lost too : Big network outage ;-((&lt;/P&gt;&lt;P&gt;You can recover from this error , by&amp;nbsp;cold booting the 1st&amp;nbsp; configured core.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is no problem in step2 using "Server_PROD" , it is always a crash&amp;nbsp;when using an already existing VLAN Name + &amp;nbsp;followed by an empty character.&lt;/P&gt;&lt;P&gt;Should have known not to use spaces since the old DOS days , but VLAN names are exspected to be simple strings, right?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 02 Feb 2012 16:26:27 GMT</pubDate>
    <dc:creator>rquack</dc:creator>
    <dc:date>2012-02-02T16:26:27Z</dc:date>
    <item>
      <title>5406zl - core pair stops working, when configuring empty spaces in VLAN Names</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/5406zl-core-pair-stops-working-when-configuring-empty-spaces-in/m-p/5526681#M30459</link>
      <description>&lt;P&gt;I have a pair of 5406zl&amp;nbsp; running firmware 15.05.0006. I know there is a newer Version availiable 15.06.0008, but I can't update so quickly.&lt;/P&gt;&lt;P&gt;we run about 20&amp;nbsp;distributed trunks on CU Modules.&lt;/P&gt;&lt;P&gt;I have a reproducable error, and maybe someone could confirm&amp;nbsp;it in a test-environment :&lt;/P&gt;&lt;P&gt;1. configure a vlan3, called "Server"&lt;/P&gt;&lt;P&gt;2. configure a vlan4, called "Server PROD"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ( With entering this both&amp;nbsp;switches stop working, console is lost. console to second core is lost too : Big network outage ;-((&lt;/P&gt;&lt;P&gt;You can recover from this error , by&amp;nbsp;cold booting the 1st&amp;nbsp; configured core.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is no problem in step2 using "Server_PROD" , it is always a crash&amp;nbsp;when using an already existing VLAN Name + &amp;nbsp;followed by an empty character.&lt;/P&gt;&lt;P&gt;Should have known not to use spaces since the old DOS days , but VLAN names are exspected to be simple strings, right?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2012 16:26:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/5406zl-core-pair-stops-working-when-configuring-empty-spaces-in/m-p/5526681#M30459</guid>
      <dc:creator>rquack</dc:creator>
      <dc:date>2012-02-02T16:26:27Z</dc:date>
    </item>
  </channel>
</rss>

