Appears the discovery utility can only see 1 of the controllers, not sure if that would stop initialisation?

Hi jon1628,

Are there any lights on the controller that is not working? You may want to reseat that controller. Page 97 https://dell.to/34PhtCL Let us know if you have any additional questions.

Yes it could possibly be

We fixed the issue with the 2nd controller, error in the network config.

So its now seeing both controllers but still refusing to initialise, screen shot attached.

It's in a data centre, we will have someone onsite on Weds who will go through the steps if we haven't resolve the issue.

Did you do the steps in my previous post?

We reseated the controllers and added a DHCP server and everything appeared ok - both controllers and the management all picked up IP addresses from DHCP. I was able to start the initialisation. However, once I set the static IP address for management and top controller I was locked out again. I suspect this is because I re-used the DHCP IP's for the static IP's and there was a conflict.

I've changed the DHCP range, restarted the san and I'm now able to logon to / access on the management IP through the client and the command line utility. The command line utility is showing only 1 controller present, this is marked as leader. I'm unable to connect to this controller through the client, response is "error setting up connection".

Not sure what to try next.

Is the Dell storage manager service running?

I'm running the virtual appliance, that link seems to be for the Windows Server install.

In Unisphere Central, it sees the SCv3020 but says initial configuration needs to be completed. I believe that has to be completed with the client, which isn't able to connect directly to the controller - only the management IP.

Two IPs showing in DHCP, one name starts SN and the other is the service tag. The client can connect to the service tag ip but says you need to connect to the leader controller IP. It won't connect to the SN ip - "error setting up connection".