I bet it is exactly as you had theorized. This server was part of a multiple server order with several identical configurations. I checked the SN# associations on the disk set and server 3 times, and absolutely assured I had the proper set. Still, on first boot, it indicated that all the disks previously configured were missing. I powered down the server and re-checked all the physical drive members to ensure they were seated properly in the enclosure. On a second boot, I was informed that a Foreign disk configuration was detected and whether or not to import it. At this point, I was pretty much resigned to the fact that I may have to re-image the server for reasons unknown, so I figured... hey, why not import it and see what happens? Next boot... SLES loads up no issue. Only thing that seemed off were the "ghost adapters" and the ETH interface numbering being offset as a result.
I agree, it's not a difficult fix, but unless you know where to look, a person could burn a lot of time trying to figure out WTH was going on. At least we have it in a searchable forum now ;-)
Bulletproof Solutions Inc.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...