I have some hosts on CL1-A. This is one path. How can we find the another path for this host? Can anyone please explain how this front end ports architecture?
If you have HDLM in the host then it will tell you which ports any host is connected to.
If you use a naming system like "host_A" when you create a Host Group, then you can filter the Host Groups in alphabetical order and see all the "Host_A"'s and their ports.
Generally you will define an alternate path on the opposite port feature, so CL1_A will pair-up with CL2_A but this depends on the scheme you implement. Odd ports and even ports are on different halves of the system for resilience.
Thgank you for your kind reply.
I have one more query. The front end ports CL1-A and CL2-A are redundant. SO the Front end ports are available like as below...
Please correct me if I am wrong. This means odd and even are for redundant purpose. Plese help me understan the front end ports naming architecture.
In simple terms yes, The array is built with two resilient "clusters" with odd ports in one, and even ports in the other.
When you add a new set of front end ports (two boards, one in each cluster) you will get corresponding odd/even port numbers as per your example.
For good practice you would usually connect a server with two FC paths to the corresponding two ports, like CL1-A and CL2-A. Definitely use one odd-numbered Port and the other on an even-numbered Port.
In practice, it is not unusual to deviate from this scheme so you might want to spend some time understanding which ports are used by different servers, especially critical ones.
There's nothing to stop you connecting your 2nd FC path to a port on the same front end card as the 1st - like CL1-A and CL3-A - but this reduces your resilience in the event of a card failure or service attention.
Thank you Very much Glenn. Now I am able to understand.
Retrieving data ...