<?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 S-Series f/w 7.71.01.0010 logs CBond Nvram error in Syslog in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/s-series-f-w-7-71-01-0010-logs-cbond-nvram-error-in-syslog/m-p/44181#M237</link>
    <description>Article ID: 14586 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series, firmware 7.62.01.0009 and higher &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Booting the system onto v7.6x or higher firmware for the first time. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Seeing a "CBondNvram: Bad NVRAM csum" error in Syslog and Message Log ('show support'); for example:&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;==============================================================================&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Message&lt;/PRE&gt;&lt;/DIV&gt;     &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;5/70&lt;/PRE&gt;&lt;/DIV&gt;      &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Syslog Message&lt;/PRE&gt;&lt;/DIV&gt;            &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;07.71.01.0010&lt;/PRE&gt;&lt;/DIV&gt;     &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;04/04/2012 18:03:57&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
       &amp;lt;&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;3&lt;/PRE&gt;&lt;/DIV&gt;&amp;gt;&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Bond[4.tusrAppInit]CBondNvram: Bad NVRAM csum 00; 00:01:00:00 - 00:00&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
       &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;:00:00:00:00&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
This is due to the Virtual Chassis/Switch Bonding (VSB) area of NVRAM being found uninitialized, expected upon the first use of a VSB-aware firmware image. It may occur regardless of actual VSB configuration. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
This message is harmless, requiring no user action, if seen under the stated conditions.</description>
    <pubDate>Tue, 17 Dec 2013 20:46:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-12-17T20:46:00Z</dc:date>
    <item>
      <title>S-Series f/w 7.71.01.0010 logs CBond Nvram error in Syslog</title>
      <link>https://community.extremenetworks.com/t5/faqs/s-series-f-w-7-71-01-0010-logs-cbond-nvram-error-in-syslog/m-p/44181#M237</link>
      <description>Article ID: 14586 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series, firmware 7.62.01.0009 and higher &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Booting the system onto v7.6x or higher firmware for the first time. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Seeing a "CBondNvram: Bad NVRAM csum" error in Syslog and Message Log ('show support'); for example:&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;==============================================================================&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Message&lt;/PRE&gt;&lt;/DIV&gt;     &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;5/70&lt;/PRE&gt;&lt;/DIV&gt;      &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Syslog Message&lt;/PRE&gt;&lt;/DIV&gt;            &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;07.71.01.0010&lt;/PRE&gt;&lt;/DIV&gt;     &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;04/04/2012 18:03:57&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
       &amp;lt;&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;3&lt;/PRE&gt;&lt;/DIV&gt;&amp;gt;&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Bond[4.tusrAppInit]CBondNvram: Bad NVRAM csum 00; 00:01:00:00 - 00:00&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
       &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;:00:00:00:00&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
This is due to the Virtual Chassis/Switch Bonding (VSB) area of NVRAM being found uninitialized, expected upon the first use of a VSB-aware firmware image. It may occur regardless of actual VSB configuration. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
This message is harmless, requiring no user action, if seen under the stated conditions.</description>
      <pubDate>Tue, 17 Dec 2013 20:46:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/s-series-f-w-7-71-01-0010-logs-cbond-nvram-error-in-syslog/m-p/44181#M237</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-12-17T20:46:00Z</dc:date>
    </item>
  </channel>
</rss>

