06-27-2010 06:02 PM
EMC CE was onsite to upgrade the switch from 5.3.0-->5.3.2. After the fw upgrade, CP in slot 5 reported as fault and the CE replaced it and then loaded the 5.3.2 code on it. Then blade is slot 3 reported as faulted and the CE reseated it to see if it would clear the error and then replaced it. Then blade in port 10 fault and the reseated and replaced it. Now the new CP in slot 5 is reporting as faulty. CE then called into the lab and I saw that from the supportsave hadump reported both CPs as ok, just hadisabled. Slotshow reported is as faulty with rsn: 21. From this I saw that the CP failed some internal port initialization (just info messages though). I had the CE do an haenable, CPs ended up being sync'ed up but slotshow reported it as faulty. I had the CE poweron/poweroff the blade to see where it was failing. But still is showing faulty
06-28-2010 02:49 AM
I was going through the release notes and one bug that has been fixed in 5.3.1 seems to be very close to what you describe.
Although you are on 5.3.2 and should not be affected by this, maybe its a good idea to compare your problem with the bug description.