Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
0Activity
0 of .
Results for:
No results containing your search query
P. 1
Access Logix

Access Logix

Ratings: (0)|Views: 3|Likes:
Published by Ravi Kiran

More info:

Published by: Ravi Kiran on Jun 18, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less

05/13/2014

pdf

text

original

 
 Access Logix
 
Access Logix, often referred to as ‘LUN Masking’, is the Clariion term for:
 1. Assigning LUNs to a particular Host2. Making sure that hosts cannot see every LUN in the Clariion
Let’s talk about making sure that every host cannot see every LUN in the Clariion first.
Access Logix is an enabler on the Clariion that allows hosts to connect to the Clariion,but not have the ability to just go out and take ownership of every LUN. Think of this
situation. You have ten Window’s Hosts attached to the Clariion, five Solaris Hosts, eightHP Hosts, etc… If all of the hosts were attached to the Clariion (zoning), and there was
no such thing as Access Logix, every host could potentially see every LUN after a rescan
or 17 reboots by Window’s. Probably not a good thing to have more than one host
writing to a LUN at a time, let alone different Operating Systems writing to the sameLUNs.
 
 Now, in order for a host to see a LUN, a few things must be done first in Navisphere.
1. For a Host, a Storage Group must be created. In the illustration above, the ‘StorageGroup’ is like a bucket.
 2. We have to Connect the host to the Storage Group
3. Finally, we have to add the LUNs to the Host’s Storage Gro
up we want the host tosee.
From the illustration above, let’s start with the Windows Host on the far left side. We
created a Storage Group for the Windows Host. You can name the Storage Groupwhatever you want in Navisphere. It would make sense to name the Storage Group thesame as the Host name. Second, we connected the host to the Storage Group. Finally,we added LUNs to the Storage Group. Now, the host has the ability to see the LUNs,after a rescan, or a reboot.However, in the Storage Group, when the LUNs are added to the Storage Group, there isa column on the bottom right-side of the Storage Group window that is labeled Host ID.You will notice that as the LUNs are placed into the Storage Group, Navisphere giveseach LUN a Host ID number. The host ID number starts at 0, and continues to 255. Wecan place up to 256 LUNs into a Storage Group. The reason for this, is that the Host hasno idea that the LUN is on a Clariion. The host believes that the LUN is a Local Disk. Forthe host, this is fine. In Windows, the host is going to rescan, and pick up the LUNs asthe next available disk. In the example above, the Windows Host picks up LUNs 6 and23, but to the host, after a rescan/reboot, the host is going to see the LUNs as Disk 4 andDisk 5, which we can now initialize, add a drive letter, format, create the partition, andmake the LUN visible through the host.
In the case of the Solaris Host’s Storage Group, when we added the LUNs to the Storage
Group, we changed LUN 9s host id to 9, and LUN 15s host id to 15. This allows the
Solaris host to see the Clariion LUN 9 as c_t_d 9, and LUN 15 as c_t_d 15. If we hadn’t
 changed the Host ID number for the LUNs however, Navisphere would have assignedLUN 9 with the Host ID of 0, and LUN 15 with the Host ID of 1. Then the host would seeLUN 9 as c_t_d 0 and LUN 15 as c_t_d 15.The last drawing is an example of a Clustered environment. The blue server is the ActiveNode of the cluster, and the orange server is the Standby/Passive Node of the cluster. Inthis example, we created a Storage Group in Navisphere for each host in the Cluster.Into the Active Node Storage Group, we place LUN 8. LUN 8 also went into the PassiveNode Storage Group. A LUN can belong to multiple storage groups. The reason for this,is if we only placed LUN 8 in to the Active Node Storage Group, not into the PassiveNode Storage Group, and the Cluster failed over to the Passive Node for some reason,
there would be no LUN to see. A host can only see what is in it’s storage group. That is
why LUN 8 is in both Storage Groups.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->