add initiator to host

[Chanklish]

I redid everything 

now all looks good 

but is this normal (unoptimized) ? 

[Cali]

Yeah, well done.
1. The Server should only see the Storage and no other Server.
2. A Volume depend to Controller A or B. If you access the Volume on A by using Port on Controller B it must be routet internal to A (Proxy). This is not the optimized Path, but a possible.
You understand?
Cali

[Chanklish]

both servers are now able to see the volume ( they are part of a 2 nodes failover cluster )

failover is working normally as well 

ok so Path A to controller B is normally unoptimized .. understood

[Roelandvdb]

Hi, Sorry to bump this old topic but there is another solution that requires no redoing stuff:

Create a second host of the second initiator and map the necessary volumes.

Connect to the CLI (putty or serial) 

Delete both hosts. The mappings should remain.

Create a new host that contains both initiators and you are set.

The necessary CLI statements can be found in the MSA 1060/2060/2062 CLI reference guide.

Hope this helps others with this shortcoming in the GUI