<?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 C3/B3-Series has OSPF Errors and Won't Boot after Upgrade from pre-6.03 to 6.61 Firmware in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/c3-b3-series-has-ospf-errors-and-won-t-boot-after-upgrade-from/m-p/48349#M520</link>
    <description>Article ID: 14942 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
C3-Series&lt;BR /&gt;
B3-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Upgraded from pre-6.03 firmware (in the range of 1.00.78 through 1.02.06.0004) &lt;I&gt;directly&lt;/I&gt; to firmware 6.61.02.0007 or higher. &lt;BR /&gt;
&lt;BR /&gt;
Though release notes, KB &lt;A href="http://bit.ly/1rViaUk" target="_blank" rel="nofollow noreferrer noopener"&gt;14480&lt;/A&gt;, and KB &lt;A href="http://bit.ly/I7AmoT" target="_blank" rel="nofollow noreferrer noopener"&gt;14711&lt;/A&gt; recommend against this, the only expected symptom is possible configuration loss.&lt;BR /&gt;
But in addition, such a direct upgrade could leave the unit unable to boot, as explained further below. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
The upgraded uniit will no longer fully boot up.&lt;BR /&gt;
It continually reboots. &lt;BR /&gt;
&lt;BR /&gt;
Pre-diagnosis, while the unit is still failing to boot, an error sequence similar to what is shown below may be seen in a serial console session. Details will vary, but the common elements citing task "OSPF mapping Task" and "File:ospf_migrate.c Line:236 Component:27" should be present. The issue has nothing to do with whether or not OSPF is actually configured. &lt;BR /&gt;
osapiFree_track(2627):LOG_ERROR(0)&lt;BR /&gt;
--------------&lt;BR /&gt;
Task ID: 0xc10d470&lt;BR /&gt;
Task Name: OSPF mapping Task&lt;BR /&gt;
PC: 0x1305924&lt;BR /&gt;
PendQ: 0xc0fbcc4&lt;BR /&gt;
SP: 0xc10ce90&lt;BR /&gt;
 &lt;BR /&gt;
0x1305924: semCTake (0x13057a0) + 0x184&lt;BR /&gt;
0x130659c: semTake (0x1306424) + 0x178&lt;BR /&gt;
0x6e65260 (Cnfgr_Thread &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; memPartFree: invalid block 0xdc34820 in partition 0x22243f0&lt;BR /&gt;
0xbfad2e0 (ipMapProcessingTask): memPartFree: invalid block 0xdc34820 in partition 0x22243f0&lt;BR /&gt;
0x6e65260 (Cnfgr_Thread &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; memPartFree: invalid block 0xdc34820 in partition 0x22243f0&lt;BR /&gt;
&amp;lt;160&amp;gt;Aug 1 14:34:05 172.16.6.11-1 OSAPI[202429552]: osapi.c(2636) 181 %File:ospf_migrate.c Line:236 Component:27&lt;BR /&gt;
&amp;lt;160&amp;gt;Aug 1 14:34:05 172.16.6.11-1 SIM[202429552]: osapi.c(2637) 182 % Error(0xdc27c74)&lt;BR /&gt;
Last switch reset caused by osapi.c(2637): Error code 0x0dc27c74, after 123 second&lt;BR /&gt;
l7_prepareSystemDump(1370): Task OSPF mapping Task(0xc10d470) is suspended with error 2Post-diagnosis, after the unit has been recovered and is again operating properly, the current.log (&lt;A href="http://bit.ly/1pOU3VK" target="_blank" rel="nofollow noreferrer noopener"&gt;5487&lt;/A&gt;) will contain a diagnostic sequence similar to what is shown below. Note that the two examples are taken from different units. &lt;BR /&gt;
&amp;lt;57&amp;gt; OCT 26 04:47:05 2012 STK1 BOOT[268430848]: bootos.c(689) 123 %%&lt;BR /&gt;
 Start of Code - Build:01.01.01.0049 Date:Tue Feb 12 16:08:47 2008&lt;BR /&gt;
&amp;lt;110&amp;gt; OCT 26 05:05:07 2012 STK1 BOOT[197169680]: edb_bxs_api.c(352) 127 %%&lt;BR /&gt;
 Last switch reset caused by power cycle&lt;BR /&gt;
&amp;lt;57&amp;gt; OCT 26 05:27:21 2012 STK1 BOOT[268430624]: loadapp.c(771) 65 %%&lt;BR /&gt;
 Boot Flash updated from version 01.00.40 to 01.00.53&lt;BR /&gt;
&amp;lt;57&amp;gt; OCT 26 05:27:59 2012 STK1 BOOT[268430624]: bootos.c(1360) 66 %%&lt;BR /&gt;
 Start of Code - Build:06.61.06.0009 Date:Wed Jul 25 18:46:35 2012&lt;BR /&gt;
&amp;lt;160&amp;gt;Oct 26 05:28:38 172.16.24.59-1 OSAPI[197060928]: osapi.c(2668) 69 %%&lt;BR /&gt;
 File:ospf_migrate.c Line:236 Component:27&lt;BR /&gt;
&amp;lt;160&amp;gt;Oct 26 05:28:38 172.16.24.59-1 SIM[197060928]: osapi.c(2669) 70 %% Error(0xd72f57c)&lt;BR /&gt;
&amp;lt;110&amp;gt; OCT 26 05:29:02 2012 STK1 BOOT[135896664]: edb_bxs_api.c(778) 70 %%&lt;BR /&gt;
 User initiated last switch reset on unit 1, after 1414 seconds&lt;BR /&gt;
Task OSPF mapping Task(0xbbee940) is suspended with error 2, creating file sysDmp1Oct2612.z&lt;BR /&gt;
&amp;lt;57&amp;gt; OCT 26 05:29:51 2012 STK1 BOOT[268430624]: bootos.c(1360) 72 %%&lt;BR /&gt;
 Start of Code - Build:06.61.06.0009 Date:Wed Jul 25 18:46:35 2012&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Use serial management to enter the boot menu, and restore the unit's configuration to factory defaults (see the solution in &lt;A href="http://bit.ly/IhlNPr" target="_blank" rel="nofollow noreferrer noopener"&gt;9673&lt;/A&gt;).&lt;BR /&gt;
Then, if a 6.61 configuration is not available as a new starting point, any desired configuration will need to be re-entered manually.</description>
    <pubDate>Fri, 22 Nov 2013 05:20:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-22T05:20:00Z</dc:date>
    <item>
      <title>C3/B3-Series has OSPF Errors and Won't Boot after Upgrade from pre-6.03 to 6.61 Firmware</title>
      <link>https://community.extremenetworks.com/t5/faqs/c3-b3-series-has-ospf-errors-and-won-t-boot-after-upgrade-from/m-p/48349#M520</link>
      <description>Article ID: 14942 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
C3-Series&lt;BR /&gt;
B3-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Upgraded from pre-6.03 firmware (in the range of 1.00.78 through 1.02.06.0004) &lt;I&gt;directly&lt;/I&gt; to firmware 6.61.02.0007 or higher. &lt;BR /&gt;
&lt;BR /&gt;
Though release notes, KB &lt;A href="http://bit.ly/1rViaUk" target="_blank" rel="nofollow noreferrer noopener"&gt;14480&lt;/A&gt;, and KB &lt;A href="http://bit.ly/I7AmoT" target="_blank" rel="nofollow noreferrer noopener"&gt;14711&lt;/A&gt; recommend against this, the only expected symptom is possible configuration loss.&lt;BR /&gt;
But in addition, such a direct upgrade could leave the unit unable to boot, as explained further below. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
The upgraded uniit will no longer fully boot up.&lt;BR /&gt;
It continually reboots. &lt;BR /&gt;
&lt;BR /&gt;
Pre-diagnosis, while the unit is still failing to boot, an error sequence similar to what is shown below may be seen in a serial console session. Details will vary, but the common elements citing task "OSPF mapping Task" and "File:ospf_migrate.c Line:236 Component:27" should be present. The issue has nothing to do with whether or not OSPF is actually configured. &lt;BR /&gt;
osapiFree_track(2627):LOG_ERROR(0)&lt;BR /&gt;
--------------&lt;BR /&gt;
Task ID: 0xc10d470&lt;BR /&gt;
Task Name: OSPF mapping Task&lt;BR /&gt;
PC: 0x1305924&lt;BR /&gt;
PendQ: 0xc0fbcc4&lt;BR /&gt;
SP: 0xc10ce90&lt;BR /&gt;
 &lt;BR /&gt;
0x1305924: semCTake (0x13057a0) + 0x184&lt;BR /&gt;
0x130659c: semTake (0x1306424) + 0x178&lt;BR /&gt;
0x6e65260 (Cnfgr_Thread &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; memPartFree: invalid block 0xdc34820 in partition 0x22243f0&lt;BR /&gt;
0xbfad2e0 (ipMapProcessingTask): memPartFree: invalid block 0xdc34820 in partition 0x22243f0&lt;BR /&gt;
0x6e65260 (Cnfgr_Thread &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; memPartFree: invalid block 0xdc34820 in partition 0x22243f0&lt;BR /&gt;
&amp;lt;160&amp;gt;Aug 1 14:34:05 172.16.6.11-1 OSAPI[202429552]: osapi.c(2636) 181 %File:ospf_migrate.c Line:236 Component:27&lt;BR /&gt;
&amp;lt;160&amp;gt;Aug 1 14:34:05 172.16.6.11-1 SIM[202429552]: osapi.c(2637) 182 % Error(0xdc27c74)&lt;BR /&gt;
Last switch reset caused by osapi.c(2637): Error code 0x0dc27c74, after 123 second&lt;BR /&gt;
l7_prepareSystemDump(1370): Task OSPF mapping Task(0xc10d470) is suspended with error 2Post-diagnosis, after the unit has been recovered and is again operating properly, the current.log (&lt;A href="http://bit.ly/1pOU3VK" target="_blank" rel="nofollow noreferrer noopener"&gt;5487&lt;/A&gt;) will contain a diagnostic sequence similar to what is shown below. Note that the two examples are taken from different units. &lt;BR /&gt;
&amp;lt;57&amp;gt; OCT 26 04:47:05 2012 STK1 BOOT[268430848]: bootos.c(689) 123 %%&lt;BR /&gt;
 Start of Code - Build:01.01.01.0049 Date:Tue Feb 12 16:08:47 2008&lt;BR /&gt;
&amp;lt;110&amp;gt; OCT 26 05:05:07 2012 STK1 BOOT[197169680]: edb_bxs_api.c(352) 127 %%&lt;BR /&gt;
 Last switch reset caused by power cycle&lt;BR /&gt;
&amp;lt;57&amp;gt; OCT 26 05:27:21 2012 STK1 BOOT[268430624]: loadapp.c(771) 65 %%&lt;BR /&gt;
 Boot Flash updated from version 01.00.40 to 01.00.53&lt;BR /&gt;
&amp;lt;57&amp;gt; OCT 26 05:27:59 2012 STK1 BOOT[268430624]: bootos.c(1360) 66 %%&lt;BR /&gt;
 Start of Code - Build:06.61.06.0009 Date:Wed Jul 25 18:46:35 2012&lt;BR /&gt;
&amp;lt;160&amp;gt;Oct 26 05:28:38 172.16.24.59-1 OSAPI[197060928]: osapi.c(2668) 69 %%&lt;BR /&gt;
 File:ospf_migrate.c Line:236 Component:27&lt;BR /&gt;
&amp;lt;160&amp;gt;Oct 26 05:28:38 172.16.24.59-1 SIM[197060928]: osapi.c(2669) 70 %% Error(0xd72f57c)&lt;BR /&gt;
&amp;lt;110&amp;gt; OCT 26 05:29:02 2012 STK1 BOOT[135896664]: edb_bxs_api.c(778) 70 %%&lt;BR /&gt;
 User initiated last switch reset on unit 1, after 1414 seconds&lt;BR /&gt;
Task OSPF mapping Task(0xbbee940) is suspended with error 2, creating file sysDmp1Oct2612.z&lt;BR /&gt;
&amp;lt;57&amp;gt; OCT 26 05:29:51 2012 STK1 BOOT[268430624]: bootos.c(1360) 72 %%&lt;BR /&gt;
 Start of Code - Build:06.61.06.0009 Date:Wed Jul 25 18:46:35 2012&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Use serial management to enter the boot menu, and restore the unit's configuration to factory defaults (see the solution in &lt;A href="http://bit.ly/IhlNPr" target="_blank" rel="nofollow noreferrer noopener"&gt;9673&lt;/A&gt;).&lt;BR /&gt;
Then, if a 6.61 configuration is not available as a new starting point, any desired configuration will need to be re-entered manually.</description>
      <pubDate>Fri, 22 Nov 2013 05:20:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/c3-b3-series-has-ospf-errors-and-won-t-boot-after-upgrade-from/m-p/48349#M520</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-22T05:20:00Z</dc:date>
    </item>
  </channel>
</rss>

