the way it actually works is that the Clariion management ports are cabled into the internal but the control station proxy-arps for these addresses on its external port and forwards the packets back and forth.
for much older NS Integrated systems it depends on whether they have a FC enablement license - if they do they were setup similar - otherwise the Clariion not visible to the outside
In terms of username/password the default is that the nasadmin account and password is synced to the Clariion
discovery should be the same - its the same Flare and responds to navicli and other API's just like a standalone Clariion
Thanks for the reply. I need some more information on how the LUNs of the Clariion/Symmetrix array will be seen by Celerra Network Server. I am using Celerra XML APIs for collecting the information about Celerra. I am looking for answers for the following questions.
1) How do I find out which HBA port of a Data Mover is seeing the LUN through which port of the array?
The XML query "MoverHostQueryParams" gives the information on the HBA and HBA ports of the data movers. It also gives the "Fibre Channel Descriptor Aspect" that describes the back-end Fibre Channel connections of a Data Mover to the Symmetrix director ports or to Clariion Storage Processors. Here is how the XML API output looks like -
portWWN="5006048ad52cf14c" storage="1"/>
portWWN="50060482bfd00a1b" storage="2"/>
portWWN="50060482bfd00a12" storage="2"/>
portWWN="50060482bfd00a02" storage="2"/>
portWWN="5006048ad52cf143" storage="1"/>
portWWN="5006048ad52cf14d" storage="1"/>
portWWN="5006048ad52cf142" storage="1"/>
portWWN="50060482bfd00a1d" storage="2"/>
portWWN="50060482bfd00a14" storage="2"/>
portWWN="50060482bfd00a0b" storage="2"/>
In the above output for a few entries there are storage endpoints which include the director number and port wwn. This information seems to be about the Symmetrix director ports.
I would like to know how this information appears for a Clariion array? Isn't there any port or storage processor information given about the connectivity between the Clariion array and the HBA ports of the Data Mover?
2) If the LUNs from the array are visible through all the ports of all the data movers, how is the multipathing handled? Are the disk volumes that belong to the Celerra Network Server multipath devices. If so, where can i get the information about the sub paths of these disk volumes.
3) How do I link a disk volume on the Celerra Network Server to an appropriate LUN of the array. Should i use the lun number and storage systems attributes of a disk volume to arrive at the same. I would like to know if this logic works if the Celerra Network Server is seeing LUNs from multiple arrays (in case of Gateway models).
ral67_xyz
147 Posts
1
January 11th, 2010 05:00
sure - with all newer Celerra model certainly yes
when they get installed the integrated Clariion gets configured with external IP addresses
[nasadmin@NS20 ~]$ /nas/sbin/model
NS20FC
[nasadmin@NS20 ~]$ grep SP /etc/hosts
10.64.240.121 A_CK200073200587 SPA # CLARiiON SP
10.64.240.122 B_CK200073200587 SPB # CLARiiON SP
[nasadmin@NS20 ~]$ nas_storage -info -all | grep ip_address
ip_address = 10.64.240.121
ip_address = 10.64.240.122
the way it actually works is that the Clariion management ports are cabled into the internal but the control station proxy-arps for these addresses on its external port and forwards the packets back and forth.
for much older NS Integrated systems it depends on whether they have a FC enablement license - if they do they were setup similar - otherwise the Clariion not visible to the outside
In terms of username/password the default is that the nasadmin account and password is synced to the Clariion
discovery should be the same - its the same Flare and responds to navicli and other API's just like a standalone Clariion
Rainer
explore1
17 Posts
0
January 15th, 2010 02:00
Thanks for the reply. I need some more information on how the LUNs of the Clariion/Symmetrix array will be seen by Celerra Network Server. I am using Celerra XML APIs for collecting the information about Celerra. I am looking for answers for the following questions.
1) How do I find out which HBA port of a Data Mover is seeing the LUN through which port of the array?
The XML query "MoverHostQueryParams" gives the information on the HBA and HBA ports of the data movers. It also gives the "Fibre Channel Descriptor Aspect" that describes the back-end Fibre Channel connections of a Data Mover to the Symmetrix director ports or to Clariion Storage Processors. Here is how the XML API output looks like -
portWWN="5006048ad52cf14c" storage="1"/>
portWWN="50060482bfd00a1b" storage="2"/>
portWWN="50060482bfd00a12" storage="2"/>
portWWN="50060482bfd00a02" storage="2"/>
portWWN="5006048ad52cf143" storage="1"/>
portWWN="5006048ad52cf14d" storage="1"/>
portWWN="5006048ad52cf142" storage="1"/>
portWWN="50060482bfd00a1d" storage="2"/>
portWWN="50060482bfd00a14" storage="2"/>
portWWN="50060482bfd00a0b" storage="2"/>
In the above output for a few entries there are storage endpoints which include the director number and port wwn. This information seems to be about the Symmetrix director ports.
I would like to know how this information appears for a Clariion array? Isn't there any port or storage processor information given about the connectivity between the Clariion array and the HBA ports of the Data Mover?
2) If the LUNs from the array are visible through all the ports of all the data movers, how is the multipathing handled? Are the disk volumes that belong to the Celerra Network Server multipath devices. If so, where can i get the information about the sub paths of these disk volumes.
3) How do I link a disk volume on the Celerra Network Server to an appropriate LUN of the array. Should i use the lun number and storage systems attributes of a disk volume to arrive at the same. I would like to know if this logic works if the Celerra Network Server is seeing LUNs from multiple arrays (in case of Gateway models).