We have our own MCPC in the lab. We ugraded scckit to 18.104.22.168 after diligently following the instructions in the HowTo. We came all they way to Step 20 - sccBmc, SccReset and sccBoot seem to be proceed perfectly fine. We get the message that the cores should now be reachable via ping. After that all hell breaks loose. The MCPC either hangs, reboots or some other similar measure. The SCC worked perfectly fine with SCCKit 1.3. We are somewhat stuck and can not think of what is wrong. I was wondering whether any one else has faced a similar problem.
To resolve the situation, I tried to back off to 22.214.171.124 and disabled all the configuration steps taken to enable EMAC (following one of the earlier guides). Even after that, the machine simply reboots. The point to to note here is that the MCPC reboots only after sccBoot -l is done (that is the cores are activated).
I will try to remove the Switch now (the switch was still connected) with the downgrade. Any suggestions? I can post the config files but I do not know where to begin. Any asisstance will be greatly appreciated!
Are you doing OK now? Did you file an SCC Bugzilla on this? If so what is the bug number?
There is essentially no difference between 126.96.36.199 and 188.8.131.52. The only difference is a fix to the sccProductiontest program, which external users hardly ever use. Don't use 184.108.40.206 or 220.127.116.11 because they are unstable.
If your problem still persists and you have a bug number, we can continue the discussion on Bugzilla.