<?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: Procurve 2610_24 not holding config in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-2610-24-not-holding-config/m-p/4322918#M16815</link>
    <description>This is a problem in an older software release. Upgrade the software to at least R11.09:&lt;BR /&gt;&lt;BR /&gt;â &amp;nbsp;Config (1000790501) â   When any supported transceiver is present in a mini-GBIC port, &lt;BR /&gt;the configuration (including port-VLAN assignment) is not maintained across a reboot.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Sun, 14 Dec 2008 07:24:45 GMT</pubDate>
    <dc:creator>Marco Wessel</dc:creator>
    <dc:date>2008-12-14T07:24:45Z</dc:date>
    <item>
      <title>Procurve 2610_24 not holding config</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-2610-24-not-holding-config/m-p/4322917#M16814</link>
      <description>I am currently working an install and having a wierd issue with one of my 2610_24 switches..  each switch has 2 J4859C SFP-LX GBICs installed in it..  Noted those are ports 27 and 28..&lt;BR /&gt;&lt;BR /&gt;I have about 13 VLANS on the switch and of course the ports 27,28 are the uplink ports...&lt;BR /&gt;&lt;BR /&gt;I can go into either command line or menu and config the ports as normal VLAN membership.. such as:&lt;BR /&gt;config&lt;BR /&gt;vlan 30&lt;BR /&gt;tagged 27,28&lt;BR /&gt;vlan 20&lt;BR /&gt;tagged 27,28&lt;BR /&gt;vlan 1&lt;BR /&gt;no untagged 27,28&lt;BR /&gt;wr mem&lt;BR /&gt;logout&lt;BR /&gt;ok and if I do a show vlan 20, or 30 etc i will see these ports as members and data communication will commence...&lt;BR /&gt;&lt;BR /&gt;now...  if I power cycle the switch ports 27,28 will go back to being untagged on vlan 1 (default)..  and yes I do my write mem.... those are the ONLY 2 ports that have this issue... I can config VLAN on any other port and it will hokd over a power cycle...&lt;BR /&gt;is there a problem using two J4859C GBIC modules in each switch?&lt;BR /&gt;-Christopher</description>
      <pubDate>Sun, 14 Dec 2008 04:10:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-2610-24-not-holding-config/m-p/4322917#M16814</guid>
      <dc:creator>cadillackid</dc:creator>
      <dc:date>2008-12-14T04:10:27Z</dc:date>
    </item>
    <item>
      <title>Re: Procurve 2610_24 not holding config</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-2610-24-not-holding-config/m-p/4322918#M16815</link>
      <description>This is a problem in an older software release. Upgrade the software to at least R11.09:&lt;BR /&gt;&lt;BR /&gt;â &amp;nbsp;Config (1000790501) â   When any supported transceiver is present in a mini-GBIC port, &lt;BR /&gt;the configuration (including port-VLAN assignment) is not maintained across a reboot.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 14 Dec 2008 07:24:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-2610-24-not-holding-config/m-p/4322918#M16815</guid>
      <dc:creator>Marco Wessel</dc:creator>
      <dc:date>2008-12-14T07:24:45Z</dc:date>
    </item>
  </channel>
</rss>

