当使用copy running-config startup-config时,日志中会有KERN-3-SYSTEM_MSG: biosinfo checksum failed expected b Got 11 kernel报错。
Symptom: After running the "copy running-config" command on a Nexus 3524 or 3548 switch, syslogs similar to the following may be observed:
switch# copy running-config startup-config [########################################] 99% 2017 May 30 06:16:35 MTC_2 %$ VDC-1 %$ May 30 06:16:34 %KERN-3-SYSTEM_MSG: [ 665.549884] biosinfo checksum failed expected b Got 11 - kernel 2017 May 30 06:16:35 MTC_2 %$ VDC-1 %$ May 30 06:16:34 %KERN-3-SYSTEM_MSG: [ 665.549889] read_from_biosinfo: No Valid biosinfo - kernel
The specific "expected" and "Got" values in the syslog may vary. This example shows an "expected" value of "b" and a "Got" value of "11", but these specific values could change from one switch to another. These syslogs may appear even if the switch is running an NX-OS software release that contains the fix for this software defect. See the "Further Problem Description" section of this enclosure for a more detailed explanation surrounding why this is the case. Conditions: This issue may be observed under the following conditions: 1. Switch is a Nexus 3524 or 3548 model switch 2. Syslogs similar to the following are observed after the "copy running-config startup-config" command is run:
2017 May 30 06:16:35 MTC_2 %$ VDC-1 %$ May 30 06:16:34 %KERN-3-SYSTEM_MSG: [ 665.549884] biosinfo checksum failed expected b Got 11 - kernel 2017 May 30 06:16:35 MTC_2 %$ VDC-1 %$ May 30 06:16:34 %KERN-3-SYSTEM_MSG: [ 665.549889] read_from_biosinfo: No Valid biosinfo - kernel
解决方案:
switch# configure terminal switch(config)# fan speed set 60 switch(config)# fan speed default switch(config)# end switch#
Note that the "fan speed" commands are hidden commands. This means that these commands will not appear in the CLI's context-sensitive help if you try to use the Tab key to auto-complete them or the ? key to view information about them. You will need to type these commands exactly as shown for them to work as expected. This workaround can be used on NX-OS software releases that contain the fix for this software defect. See the "Further Problem Description" section of this enclosure for a more detailed explanation surrounding why this is the case. Further Problem Description: On Nexus 3524 and 3548 model switches, fan speed values are stored in the BIOS of the switch. Whenever the speed of fans needs to be adjusted, a section of the BIOS must be updated with the new fan speed values. Prior to NX-OS software release 7.0(3)I7(2), the checksum for this section of the BIOS was incorrectly updated whenever fan speed values needed to change. Starting with NX-OS software release 7.0(3)I7(2) and later, the checksum for this section of the BIOS is correctly updated. However, an incorrect checksum in this section of the BIOS is not proactively fixed as a result of an NX-OS software upgrade. In other words, if a Nexus 3548 switch is running NX-OS 7.0(3)I7(1) and these syslogs are observed, an NX-OS software upgrade to 7.0(3)I7(2) or later will not correct the checksum in the BIOS. As a result, it is possible to see the syslogs documented in the "Symptoms" section of this enclosure while running an NX-OS software release that contains the fix for this software defect. For this reason, applying the workaround documented in the "Workaround" section of this enclosure is needed to resolve this issue, even if the switch is running an NX-OS software release that contains the fix for this software defect.