Cisco Cisco Content Delivery Engine 250 Guida All'Installazione
5 short beeps + 1 long beep, Memory error, No memory detected in the
system
system
The only known workaround once the system is in this POST Boot hung state is to remove
the power source from the power supplies, wait a few seconds for the power to settle out and
then restore power to the system.
the power source from the power supplies, wait a few seconds for the power to settle out and
then restore power to the system.
The root-cause is the SMBus receiving multiple requests simultaneously which can lock the
SMBus, which in turn can lock the memory bus from being accessed by the system during a
reboot.
Root cause from the Release notes for IPMI FW v2.05:
Synopsis: Improved SMBus performance.
Description: Reduce system resource usage and decrease the chan ce of SMBus conflict.
If the different sources access the SMBus (I2C) interface at the same time, it could cause
system to be hung since the SMBus cannot handle multiple simultaneous requests.
SMBus conflicts always produce system a hung on reboot.
If the different sources access the SMBus (I2C) interface at the same time, it could cause
system to be hung since the SMBus cannot handle multiple simultaneous requests.
SMBus conflicts always produce system a hung on reboot.
The following customer SR cases have been raised against this issue:
SR-624384961 – CDE250-K9-only pull out power supply, than can boot up
Application Lifecycle Management
Defect ID : 226
CDE-250 Vault did not recover from Init-6 reboot
CDS Release 3.2.1-es3 B2
Device : CDE-250.When provisioning SNMP on the new vault the services were
not starting so an Init-6 was attempted.
Defect ID : 226
CDE-250 Vault did not recover from Init-6 reboot
CDS Release 3.2.1-es3 B2
Device : CDE-250.When provisioning SNMP on the new vault the services were
not starting so an Init-6 was attempted.
ECO#: E113357 – This ECO is already in place to update the IPMI FW v1.33
with IPMI FW v2.05 in manufacturing
with IPMI FW v2.05 in manufacturing