Unsolved
This post is more than 5 years old
10 Posts
1
18046
Need explanation of ODM components and when to use them
Hello:
Will someone please explain the purpose of each ODM component, and when (the host environment scenario) to use it?
- EMC Symmetrix/CLARiiON AIX Support Software
- EMC Symmetrix/CLARiiON FCP MPIO Support Software
- EMC Symmetrix/CLARiiON FCP PowerPath MPIO Support Software
- EMC Symmetrix/CLARiiON FCP Support Software
- EMC Symmetrix/CLARiiON HA Concurrent Support
- EMC Symmetrix/CLARiiON iSCSI Support Software
For example:
#1) Basic device driver to enable AIX to use LUNs from a specific SAN system.
#5) Additional support for when HACMP or other highly available software is n use.
#6) Additional support for use with iSCSI connections.
I'm a bit confused with the FCPs (#2-4) on when I should use which. For example, on my VIO server, if I have 2 HBAs and my LUN is presented to my VIO server and I use PowerPath, what do I use? I assume #1 and #3? And if that LUN is presented to a VIO client machine, what do I need to install?
Any help in this regard will be greatly appreciated. Thanks!
Conor
341 Posts
2
January 4th, 2011 02:00
Hi John,
I believe that Primus emc144918 will answer most of the below questions…
Q: For example, on my VIO server, if I have 2 HBAs and my LUN is presented to my VIO server and I use PowerPath, what do I use?
A: You will need 1. EMC Symmetrix/CLARiiON AIX Support Software and 4. Symmetrix/CLARiiON FCP Support Software
Q, And if that LUN is presented to a VIO client machine, what do I need to install?
A. Same rules apply for either VIOS or VIOC, wherever the LUN is physically presented, the ODM or PP requirements are the same.
Conor
341 Posts
0
January 4th, 2011 03:00
Here is the content from the previously mentioned Primus solution...
This document is intended to provide a description, requirements and contents of every fileset available with the EMC ODM 5.3.0.x package.
Fileset name
Description / Requirements / Contents
EMC.CLARiiON.aix.rte
Description: CLARiiON AIX Support Software
Content: This fileset contains the following control files and utilities:
/usr/lpp/EMC/CLARiiON/bin/emc_cfgmgr
/usr/lpp/EMC/CLARiiON/bin/inq.aix64_43
/usr/lpp/EMC/CLARiiON/bin/inq.aix64_51
/usr/lpp/EMC/CLARiiON/bin/emcgrab_AIX_v3.7_1.tar
/usr/lpp/EMC/CLARiiON/bin/PP_lun_reset_spt.add
/usr/lpp/EMC/CLARiiON/bin/PP_lun_reset_spt.del
/usr/lpp/EMC/CLARiiON/bin/emcpowerreset
/usr/lib/methods/clar.cat
/usr/lib/nls/msg/en_US/clar.cat
-->> See note below for details on utilities.
EMC.CLARiiON.fcp.MPIO.rte
Description: CLARiiON Fibre Channel MPIO Support Software
Requirements: IBM MPIO default PCM. please see emc75601 for details on implementation requirements.
Contents: Predefined entries for CLARiiON MPIO device types and models
EMC.CLARiiON.fcp.PowerMPIO.rte
Description: CLARiiON Fibre Channel PowerPath MPIO Support Software
Requirements: PowerPath version which supports IBM MPIO custom PCM. This fileset is currently (December 2010) not supported.
Contents: Predefined entries for CLARiiON PowerPath MPIO device types and models
EMC.CLARiiON.fcp.rte
Description: CLARiiON Fibre Channel Support Software
Contents: Predefined entries for CLARiiON device types and models
EMC.CLARiiON.ha.rte
Description: CLARiiON HA Concurrent Support
Requirements: This fileset requires HACMP CLVM feature
Contents: This fileset provides a utility called `symcurrent` to add and delete CLARiiON device types into the clconraid.dat configuration file.
EMC.CLARiiON.iscsi.rte
Description: CLARiiON iSCSI support software
Requirements: Listed in the EMC Support Matrix. Only certain configurations are supported currently (December 2010).
Contents: Predefined entries for CLARiiON iSCSI device types and models
EMC.INVISTA.aix.rte
Description: INVISTA AIX Support Software
Contents: This fileset contains the following control files and utilities:
/usr/lib/methods/invista.cat
/usr/lib/nls/msg/en_US/invista.cat
/usr/lpp/EMC/INVISTA/bin/emc_cfgmgr
/usr/lpp/EMC/INVISTA/bin/inq.aix64_43
/usr/lpp/EMC/INVISTA/bin/inq.aix64_51
/usr/lpp/EMC/INVISTA/bin/emcgrab_AIX_v3.7_1.tar
/usr/lpp/EMC/INVISTA/bin/emcpowerreset
-->> See note below for details on utilities.
EMC.INVISTA.fcp.rte
Description: INVISTA Fibre Channel support software
Requirements: Listed in the EMC Support Matrix.
Contents: Predefined entries for INVISTA device types and models
EMC.Symmetrix.aix.rte
Description: EMC Symmetrix AIX Support Software
Contents: Predefined entries for Symmetrix SCSI device types and models. In addition, this fileset contains the following control files and utilities:
/usr/lpp/EMC/Symmetrix/bin/emc_cfgmgr
/usr/lpp/EMC/Symmetrix/bin/mkbcv
/usr/lpp/EMC/Symmetrix/bin/rmbcv
/usr/lpp/EMC/Symmetrix/bin/bcvfcp.tar
/usr/lpp/EMC/Symmetrix/bin/boot_change.tar
/usr/lpp/EMC/Symmetrix/bin/inq.aix64_43
/usr/lpp/EMC/Symmetrix/bin/inq.aix64_51
/usr/lpp/EMC/Symmetrix/bin/emcgrab_AIX_v3.7_1.tar
/usr/lpp/EMC/Symmetrix/bin/emc_odmupdate.tar
/usr/lpp/EMC/Symmetrix/bin/PP_lun_reset_spt.add
/usr/lpp/EMC/Symmetrix/bin/PP_lun_reset_spt.del
/usr/lpp/EMC/Symmetrix/bin/emcpowerreset
/usr/lpp/EMC/Symmetrix/bin/rdfg.tar
/usr/lpp/EMC/Symmetrix/bin/emc_odmupdate_uniqueid.tar
/usr/lib/methods/sym.cat
/usr/lib/nls/msg/en_US/sym.cat
-->> See note below for details on utilities.
EMC.Symmetrix.fcp.MPIO.rte
Description: Symmetrix Fibre Channel MPIO Support Software
Requirements: IBM MPIO default PCM.
Contents: Predefined entries for Symmetrix Fibre Channel MPIO device types and models
EMC.Symmetrix.fcp.PowerMPIO.rte
Description: Symmetrix Fibre Channel PowerPath MPIO Support Software
Requirements: PowerPath version which supports IBM MPIO custom PCM. This fileset is currently (December 2010) not supported.
Contents: Predefined entries for Symmetrix PowerPath MPIO device types and models
EMC.Symmetrix.fcp.rte
Description: Symmetrix Fibre Channel Support Software
Contents: Predefined entries for Symmetrix Fibre Channel device types and models
EMC.Symmetrix.ha.rte
Description: Symmetrix HA Concurrent Support
Requirements: This fileset requires HACMP CLVM feature
Contents: This fileset provides a utility called `symcurrent` to add and delete Symmetrix device types into the clconraid.dat configuration file.
EMC.Symmetrix.iscsi.rte
Description: Symmetrix iSCSI support software
Requirements: Supported as of the January 2007 ESM
Contents: Predefined entries for Symmetrix iSCSI device types and models
Some ODM filesets provide utilities. The below table explains the purpose of each utility:
Utility
Description
emc_cfgmgr
Directed Configuration for EMC storage devices. This utility also supports Symmetrix TimeFinder devices, meaning that BCVs are brought to an Available state.
mkbcv
Configure BCVs to an Available state (including hdiskpower devices if they exist).
rmbcv
Change BCVs to a Defined state (including hdiskpower devices if they exist)
bcvfcp.tar
The two shell scripts included in this tar file converts BCV ODM entries in the PdDv object class to a configurable (bcvfcpavail.sh) or non-configurable (bcvfcpunavail.sh) state.
boot_change.tar
The shell script included in this tar file (boot_change.sh) converts existing configured Symmetrix SCSI and FCP device entries in the CuDv ODM object class to osdisk. This change is required in order to allow the migration from Symmetrix filesets when the AIX system is booting off a Symmetrix device.
inq.aix64_43
inq utility
inq.aix64_51
inq utility
emc_odmupdate.tar
The shell script included in this tar file (emc_odmupdate) alters the ww_name field of all existing EMC devices so that they can only be displayed (update not allowed). The script should be used when a change of the ww_name field for configured devices, including rootvg when it resides on external EMC storage, is needed.
Note: In a earlier rev of the ODM package the ww_name attribute "generic = DU" value was set to Displayable and Updatable. It is supposed to only be Displayable. This is just a carryover script from an earlier ODM package in which most customers will not need to run.
emcpowerreset
The utility is used to reset a device reservation with HACMP for PowerPath 3.0.3, 3.0.4, 4.X and higher.
rdfg.tar
The shell script included in this tar file (rdfg.sh) alters the ODM to change all Symmetrix RDF FCP (RDF1 and/or RFD2) devices so that they show up as RDFG "Generic" device types.
emc_odmupdate_uniqueid.tar
The shell script included in this tar file (emc_odmupdate_uniqueid.sh) alters the unique_id field in the predefined PdAt of the MPIO Symmetrix objects (in ODM) to support addresses above 0xfff.
johnho1
10 Posts
0
January 5th, 2011 02:00
Hi Connor,
Thanks for the insightful information! However, I do have a follow up question...
If I have LUN X presented to VIO-Server's two HBAs (hdisk10 and hdisk11), and I have a pseudo device on the VIO-Server for this LUN as hdiskpower1, and I present hdiskpower1 as a PV to a VIO-Client via vscsi. In this case, on the VIO-Client lpar, I still need ODMs 1 and 4?
Now, let's make things even more interesting. Now, I want to have VIO-Server redundancy inside my physical machine, so now I have VIOS1 and VIOS2, and each VIOS has HBA redundancy (2 hbas to separate fabrics). So now I have LUN X presented to a total of 4 WWNs (2 per VIOS). On both my VIOS1 and VIOS2, I will install 1. EMC Symm/CLAR AIX Support and 4. Symm/CLAR FCP Support software. Additionally, I will install EMC PP. But for my VIO-Client, what software should I use? Since it's vscsi, should I still need to install 1 and 4? Or just 1? Or 1 and one of the MPIO software? And furthermore, are there any kind of special attributes I need to set for the devices on each level (VIOS and VIOC)?
Below is a rough and quick drawing representing what I would like to architect.
| |
| VIO-CLIENT |
| |
| ? | <-- what should I use for multipathing?
| / \ |
|__hd0(vscsi0)__hd1(vscsi1)_| <-- whole pseudo device presented to
/ \ client by virtual scsi adapter.
______/_____ ____\_______
| hdpwr1 | | hdpwr1 | <-- pseudo device from the 2 paths.
| | | |
| VIOS1 | | VIOS2 |
| | | |
|_hd0 hd1__| |__hd0 hd1__| <-- hdiskX as a path from an HBA.
\ \ / /
A \ \ B A / / B <-- Fabric A or B.
\ \ / /
| LUN X |
I hope this makes sense. =)
John
Conor
341 Posts
1
January 5th, 2011 04:00
1. In this case, on the VIO-Client lpar, I still need ODMs 1 and 4?
>> No since the LUN is being presented from the VIOS it is not physically connected to the VIOC. You only need EMC ODM's and PP where the LUNs are physically presented to the VIOC. (No virtualization layer)
2. In the case where you have dual VIOS with PowerPath and ODM's installed, presenting the vscsi LUN to the VIOC, the answer is the same, no need for any EMC SW in the VIOC. The default MPIO software in the VIOS detects the multiple paths to the vscsi devices and configures them automatically.
Regarding the device attributes, please ensure that the device identification method uses UDID, this requirement is discussed in the attached Host Connectivity guide p123. This section has information that covers most VIOS questions. Let me know if you have any other queries.
Conor
1 Attachment
AIX Host connectivity.pdf
johnho1
10 Posts
0
January 5th, 2011 05:00
Great help, Connor! I suspected the default AIX MPIO drivers would be sufficient, but when I looked at the lpp of the EMC ODM driver, the words "MPIO" in 2 of the components like below may have caused me to think perhaps I do need one of them in the VIOC layer.
3. EMC Symmetrix/CLARiiON FCP MPIO Support Software
4. EMC Symmetrix/CLARiiON FCP PowerPath MPIO Support Software
This is good to know. So I'm just confused as to when I would use any of the above components, or why they're even there to confuse me. =)
Final follow up question... If my VIOS1 has an NPIV_HBA1, and VIOS2 has an NPIV_HBA2, and I create a virtual FC adapter in my VIOC from each VIOS, what components will I have to install on each layer?
Many apologies for asking you this instead of reading the attached doc, as I just went through a downtime upgrading 4 AIX servers, and it's easier to use this forum than reading the doc.
| |
| VIO-CLIENT |
| |
| ? | <-- what should I use for multipathing?
| / \ |
|__ virthba0__virthba1 _| <-- virt HBAs w/ virt WWN
/ \
______/_____ ____\_______
| virthba | | virthba | <-- these are the virthba connectors
| | | |
| VIOS1 | | VIOS2 |
| | | |
|_hba0 __| |_hba0 __| <-- NPIV HBAs
\ /
A \ A / <-- LUN masked to virtWWN, not physical
\ /
| LUN X |
Conor
341 Posts
0
January 6th, 2011 07:00
I'm gonna hold my hand up and say that question is beyond my experience, I haven't worked with NPIV environments on VIOS!
I'll see if I can reach out and get somone to get an answer for you...