- I have a UCS-FI-6248UP with firmware version 4.1(3b) installed.
- Initially, it was set up in standalone mode.
- I switched it to cluster mode, but I did not connect the second fabric. I had to reboot it because the svc_sam_controller service wouldn’t start (this is a known bug that I found, and it hasn’t been fixed in my firmware version). After the reboot, I had to connect via SSH and manually specify that the fabric is primary.
- After that, I tried to access the IP address I had assigned to the cluster, but I couldn’t log in via SSH. So, I checked the web interface on the same address and discovered that it was running version 3.1(3c). I was also unable to log in.
- The web interface on the fabric IP is running version 4.1(3b), and I can log in there as both a local user and an LDAP user.
Unfortunately, during the reboot, I wasn’t connected to the fabric console and didn’t see what happened during the boot process.
Here’s my question:
If I activate the required firmware version via Firmware Management, will the fabric interconnect reboot? Or will only UCS Manager with the cluster IP address restart?
