<?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: unexpected restart JL381A in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7061004#M34075</link>
    <description>&lt;P&gt;OK, firmware upgraded.&lt;/P&gt;&lt;P&gt;thanks you for the support&lt;/P&gt;</description>
    <pubDate>Wed, 04 Sep 2019 15:45:13 GMT</pubDate>
    <dc:creator>LauroP</dc:creator>
    <dc:date>2019-09-04T15:45:13Z</dc:date>
    <item>
      <title>unexpected restart JL381A</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7060928#M34071</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Today after over 4 uptime months my switch JL381A was rebooted after&amp;nbsp;unexpected restart.&lt;/P&gt;&lt;P&gt;No power loss (we have another JL381A in the same rack and this one work fine).&lt;/P&gt;&lt;P&gt;The rack is on a&amp;nbsp; air-conditioned rooms&lt;/P&gt;&lt;P&gt;After the autoreboot the switch is working and i get this crash report:&lt;/P&gt;&lt;P&gt;***************************************************&lt;BR /&gt;* Start FASTPATH Stack Information *&lt;BR /&gt;***************************************************&lt;BR /&gt;pid: 1133&lt;BR /&gt;TID: 0xb622b4c0&lt;BR /&gt;Task Name: bcmRX&lt;BR /&gt;si_signo: 11&lt;BR /&gt;si_errno: 0&lt;BR /&gt;si_code: 1&lt;BR /&gt;si_addr: 0x3d&lt;BR /&gt;Date/Time: 9/4/2019 9:18:49&lt;BR /&gt;SW ver: PD.02.06&lt;/P&gt;&lt;P&gt;------------ CALL STACK INFO ------------&lt;BR /&gt;$00055ef0$ hapiBroadReceive + 0x1d8&lt;BR /&gt;$011cabb8$ rx_process_packet + 0x390&lt;BR /&gt;$011cb31c$ rx_thread_pkts_process + 0x264&lt;BR /&gt;$011cc7b0$ rx_pkt_thread + 0xd4&lt;BR /&gt;$006412dc$ osapi_task_wrapper + 0x168&lt;BR /&gt;/lib/libpthread.so.0 [0xb6f497e8]&lt;BR /&gt;-----------------------------------------&lt;BR /&gt;Stack Size: 36864 Bytes&lt;BR /&gt;Stack Base Address: 0xB6223000&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;***************************************************&lt;BR /&gt;* End FASTPATH Stack Information *&lt;BR /&gt;***************************************************&lt;/P&gt;</description>
      <pubDate>Wed, 04 Sep 2019 09:51:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7060928#M34071</guid>
      <dc:creator>LauroP</dc:creator>
      <dc:date>2019-09-04T09:51:51Z</dc:date>
    </item>
    <item>
      <title>Re: unexpected restart JL381A</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7060940#M34072</link>
      <description>&lt;P&gt;Given that &lt;A href="https://support.hpe.com/hpsc/doc/public/display?docId=a00056664en_us" target="_blank" rel="noopener"&gt;PD.02.06&lt;/A&gt; is, as of now, almost one Year old I strongly suggest you to update to &lt;A href="https://support.hpe.com/hpsc/doc/public/display?docId=a00085197en_us" target="_blank" rel="noopener"&gt;PD.02.10&lt;/A&gt;&amp;nbsp;which was recently released (few days ago) since two "reset" related bugs were fixed along the way.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Sep 2019 10:34:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7060940#M34072</guid>
      <dc:creator>parnassus</dc:creator>
      <dc:date>2019-09-04T10:34:50Z</dc:date>
    </item>
    <item>
      <title>Re: unexpected restart JL381A</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7060948#M34073</link>
      <description>Hi, Thank you for the answer. I will try, one last question: With the update procedure the actual configuration is lost?</description>
      <pubDate>Wed, 04 Sep 2019 10:59:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7060948#M34073</guid>
      <dc:creator>LauroP</dc:creator>
      <dc:date>2019-09-04T10:59:04Z</dc:date>
    </item>
    <item>
      <title>Re: unexpected restart JL381A</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7060960#M34074</link>
      <description>AFAIK no, the update process preserves the configuration (it can alter the configuration...)...generally is a good practice to perform a pre-update/pre-upgrade backup of the Switch running configuration and save on a safe place (check manual) and ensure that your startup configuration matches your actual running configuration (check manual).</description>
      <pubDate>Wed, 04 Sep 2019 12:05:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7060960#M34074</guid>
      <dc:creator>parnassus</dc:creator>
      <dc:date>2019-09-04T12:05:30Z</dc:date>
    </item>
    <item>
      <title>Re: unexpected restart JL381A</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7061004#M34075</link>
      <description>&lt;P&gt;OK, firmware upgraded.&lt;/P&gt;&lt;P&gt;thanks you for the support&lt;/P&gt;</description>
      <pubDate>Wed, 04 Sep 2019 15:45:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/unexpected-restart-jl381a/m-p/7061004#M34075</guid>
      <dc:creator>LauroP</dc:creator>
      <dc:date>2019-09-04T15:45:13Z</dc:date>
    </item>
  </channel>
</rss>

