03-08-2019 11:20 AM
Hello,
I am setting up 2 6248 FI's as a new cluster. I erased configuration on both units, completed initial config on A-unit, and it is fine. I complete the initial config on B-unity, and it is able to join the cluster OK. However, when the B-Unit is rebooted, it returns back to the initial configuration screen, seemingly with no config on it. Is there a bios setting that needs to be checked, or do I have hardware failure?
Thanks in advance!
Solved! Go to Solution.
03-08-2019 11:43 AM - edited 03-08-2019 11:52 AM
There may be an issue with one of the internal linux type file systems, specifically the /opt mount.
I have seen similar issues as yours when the /opt file system needs an e2fsck run on it.
You will need to open a case with TAC for them to check that, and will need a special debug plugin to get to the root level to force the file system check.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCut63966/?reffering_site=dumpcr
Kirk...
03-08-2019 11:43 AM - edited 03-08-2019 11:52 AM
There may be an issue with one of the internal linux type file systems, specifically the /opt mount.
I have seen similar issues as yours when the /opt file system needs an e2fsck run on it.
You will need to open a case with TAC for them to check that, and will need a special debug plugin to get to the root level to force the file system check.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCut63966/?reffering_site=dumpcr
Kirk...
03-08-2019 12:59 PM
Hmmm, ok. I was hoping that it was just stuck in some password recovery loop. Thanks for the link, I will open a case with TAC.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide