Originally posted by: SystemAdmin

Hi,
i have a problem configuring VIOS MPIO (v. 5300-04 - ioslevel 1.2.1.4-FP-7.4) with EMC's disks on LPAR's client.
I installed and upgrade the new EMC ODM software on VIOS1:

EMC.Symmetrix.aix.rte 5.3.0.1 C F EMC Symmetrix AIX Support
EMC.Symmetrix.fcp.MPIO.rte 5.3.0.1 C F EMC Symmetrix FCP MPIO Support
and I have this mpio version on VIOS: devices.common.IBM.mpio.rte 5.3.0.42 A F MPIO Disk Path Control Module

This EMC upgrade need to riconfigure all disks, removing all the devices (vhost and hdisk) on VIOS.
All disks have the no_reserve parameter because I have another VIOS2 (v. 5300-04 - ioslevel 1.2.1.4-FP-7.4) with old EMC software
that manage the same disks with this version:

EMC.Symmetrix.aix.rte 5.2.0.4 C F EMC Symmetrix AIX Support
EMC.Symmetrix.fcp.MPIO.rte 5.2.0.4 C F EMC Symmetrix Fibre Channel

The problem is when I discover these disks on LPAR aix clients.
I do the mkvdev between disk and vhost (mkvdev -vdev hdisk$var -vadapter vhost15 -dev vhdisk$var) the LPar client I have in general 2 results:
1. the client aix doesn't see the disks but only the vscsi.
2. the client aix see the disks only with reboot but redundant (2 disks with the same pvid).
Ex.
--> hdisk2 00c81c1dd631d5cc vgdatPTS active
--> hdisk4 00c81c1dd631d5cc vgdatPTS active
hdisk5 00c81c1dd632a5d2 vgsapPTS active
hdisk6 00c81c1dd632a61a vgdatPTS active
hdisk7 00c81c1dd632a662 vgdatPTS active
hdisk8 00c81c1dd632a6aa vgoraPTS active
hdisk9 00c81c1dd632a6f2 vgdatPTS active
hdisk10 00c81c1dd632a73a vgdatPTS active
hdisk11 00c81c1dd632a782 vgarcPTS active
hdisk12 00c81c1dd632a7ca vgdatPTS active
hdisk13 00c81c1dd632a812 vgdatPTS active
hdisk14 00c81c1dd632a85a vgdatPTS active
hdisk15 00c81c1dd632a8a2 vgdatPTS active
hdisk16 00c81c1dd632a8ea vgdatPTS active
hdisk17 00c81c1dd632a932 vgdatPTS active
hdisk18 00c81c1dd632a97a vgdatPTS active
hdisk19 00c81c1dd632a9c2 vgdatPTS active
hdisk20 00c81c1dd632aa0a vgdatPTS active
hdisk21 00c81c1dd632aa52 vgdatPTS active
hdisk22 00c81c1dd632aa9a vgdatPTS active
hdisk23 00c81c1dd632aae2 vgdatPTS active
hdisk24 00c81c1dd632ab2a vgdatPTS active
hdisk25 00c81c1dd632ab72 vgdatPTS active
hdisk26 00c81c1dd632abba vgdatPTS active
hdisk3 00c81c1dd632a73a vgdatPTS active
hdisk27 00c81c1dd632a7ca vgdatPTS active
hdisk28 00c81c1dd632a812 vgdatPTS active
hdisk29 00c81c1dd632a662 vgdatPTS active
hdisk30 00c81c1dd632a6f2 vgdatPTS active
hdisk31 00c81c1dd632a61a vgdatPTS active

and this is the lspath (you can see that not all the disks pass with the vscsi0 - VIOS1)

Enabled hdisk4 vscsi1
Enabled hdisk5 vscsi1
Enabled hdisk6 vscsi1
Enabled hdisk7 vscsi1
Enabled hdisk8 vscsi1
Enabled hdisk9 vscsi1
Enabled hdisk10 vscsi1
Enabled hdisk11 vscsi1
Enabled hdisk12 vscsi1
Enabled hdisk13 vscsi1
Enabled hdisk14 vscsi1
Enabled hdisk15 vscsi1
Enabled hdisk16 vscsi1
Enabled hdisk17 vscsi1
Enabled hdisk18 vscsi1
Enabled hdisk19 vscsi1
Enabled hdisk20 vscsi1
Enabled hdisk21 vscsi1
Enabled hdisk22 vscsi1
Enabled hdisk23 vscsi1
Enabled hdisk24 vscsi1
Enabled hdisk25 vscsi1
Enabled hdisk26 vscsi1
Enabled hdisk2 vscsi0
Enabled hdisk3 vscsi0
Enabled hdisk27 vscsi0
Enabled hdisk28 vscsi0
Enabled hdisk29 vscsi0
Enabled hdisk30 vscsi0
Enabled hdisk31 vscsi0

This are the firmware version of fibre channel adapter:
lscfg -vpl fcs6

fcs6 U5791.001.99B01WP-P1-C05-T1 FC Adapter

Part Number.................80P4543
EC Level....................A
Serial Number...............1D511067BD
Manufacturer................001D
Feature Code/Marketing ID...280B
FRU Number.................. 80P4544
Device Specific.(ZM)........3
Network Address.............10000000C94901B1
ROS Level and ID............02881914
Device Specific.(Z0)........1001206D
Device Specific.(Z1)........00000000
Device Specific.(Z2)........00000000
Device Specific.(Z3)........03000909
Device Specific.(Z4)........FF801315
Device Specific.(Z5)........02881914
Device Specific.(Z6)........06831914
Device Specific.(Z7)........07831914
Device Specific.(Z8)........20000000C94901B1
Device Specific.(Z9)........TS1.90A4
Device Specific.(ZA)........T1D1.90A4
Device Specific.(ZB)........T2D1.90A4
Device Specific.(YL)........U5791.001.99B01WP-P1-C05-T1
PLATFORM SPECIFIC

Name: fibre-channel
Model: LP10000
Node: fibre-channel@1
Device Type: fcp
Physical Location: U5791.001.99B01WP-P1-C05-T1
fcs7 U5791.001.99B01WN-P1-C05-T1 FC Adapter

Part Number.................80P4543
EC Level....................A
Serial Number...............1D51106693
Manufacturer................001D
Feature Code/Marketing ID...280B
FRU Number.................. 80P4544
Device Specific.(ZM)........3
Network Address.............10000000C9490087
ROS Level and ID............02881914
Device Specific.(Z0)........1001206D
Device Specific.(Z1)........00000000
Device Specific.(Z2)........00000000
Device Specific.(Z3)........03000909
Device Specific.(Z4)........FF801315
Device Specific.(Z5)........02881914
Device Specific.(Z6)........06831914
Device Specific.(Z7)........07831914
Device Specific.(Z8)........20000000C9490087
Device Specific.(Z9)........TS1.90A4
Device Specific.(ZA)........T1D1.90A4
Device Specific.(ZB)........T2D1.90A4
Device Specific.(YL)........U5791.001.99B01WN-P1-C05-T1
PLATFORM SPECIFIC

Name: fibre-channel
Model: LP10000
Node: fibre-channel@1
Device Type: fcp
Physical Location: U5791.001.99B01WN-P1-C05-T1

I need your help because I don't know how to resolve this problem.
Thank you
#AIX-Forum

Originally posted by: SystemAdmin

Hi, i have some questions:

• Why dont you use powerpath on VIOS? Because of license cost?
• Are you using MPIO on VIO client (lpar)? I suppose the lpar disks are balanced through both VIOS
• Are you SURE your VIOS to lpar EMC mapping are the same on boths VIOS? Please post the following:

At client side:

• lscfg -vl hdisk* (for all EMC disks)

At both VIOS side:

• lsdev -slots (with padmin)
• confirm which vhost is assigned to your lpar (HMC)
• lsmap -vadapter vhostX

Its allways a best practice to have the latest stable version. So i'd do the following:

• update FC firmware to 1.91a5
• upgrade the VIOS version to 1.4.1.2
• upgrade the second MPIO VIOS to the same as the first (5.3)

Best regards
Igor Franco
#AIX-Forum

Originally posted by: SystemAdmin

We don't use powerpath, for a Client decision.
We use mpio (devices.common.IBM.mpio.rte 5.3.0.54 A F MPIO Disk Path Control Module) in the client too but not the EMC packages.
The LUN are balanced between the 2 VIOS.
The LUN are same (same SERIAL NUMBER).

These are the answers of your questions:

FROM CLIENT:

hdisk2 U9119.595.8381C1D-V12-C4-T1-L810000000000 Virtual SCSI Disk Drive
hdisk4 U9119.595.8381C1D-V12-C2-T1-L8f0000000000 Virtual SCSI Disk Drive
hdisk5 U9119.595.8381C1D-V12-C2-T1-L970000000000 Virtual SCSI Disk Drive
hdisk6 U9119.595.8381C1D-V12-C2-T1-L870000000000 Virtual SCSI Disk Drive
hdisk7 U9119.595.8381C1D-V12-C2-T1-L8b0000000000 Virtual SCSI Disk Drive
hdisk8 U9119.595.8381C1D-V12-C2-T1-L930000000000 Virtual SCSI Disk Drive
hdisk9 U9119.595.8381C1D-V12-C2-T1-L830000000000 Virtual SCSI Disk Drive
hdisk10 U9119.595.8381C1D-V12-C2-T1-L8d0000000000 Virtual SCSI Disk Drive
hdisk11 U9119.595.8381C1D-V12-C2-T1-L950000000000 Virtual SCSI Disk Drive
hdisk12 U9119.595.8381C1D-V12-C2-T1-L850000000000 Virtual SCSI Disk Drive
hdisk13 U9119.595.8381C1D-V12-C2-T1-L890000000000 Virtual SCSI Disk Drive
hdisk14 U9119.595.8381C1D-V12-C2-T1-L910000000000 Virtual SCSI Disk Drive
hdisk15 U9119.595.8381C1D-V12-C2-T1-L810000000000 Virtual SCSI Disk Drive
hdisk16 U9119.595.8381C1D-V12-C2-T1-L8e0000000000 Virtual SCSI Disk Drive
hdisk17 U9119.595.8381C1D-V12-C2-T1-L960000000000 Virtual SCSI Disk Drive
hdisk18 U9119.595.8381C1D-V12-C2-T1-L860000000000 Virtual SCSI Disk Drive
hdisk19 U9119.595.8381C1D-V12-C2-T1-L8a0000000000 Virtual SCSI Disk Drive
hdisk20 U9119.595.8381C1D-V12-C2-T1-L920000000000 Virtual SCSI Disk Drive
hdisk21 U9119.595.8381C1D-V12-C2-T1-L820000000000 Virtual SCSI Disk Drive
hdisk22 U9119.595.8381C1D-V12-C2-T1-L8c0000000000 Virtual SCSI Disk Drive
hdisk23 U9119.595.8381C1D-V12-C2-T1-L940000000000 Virtual SCSI Disk Drive
hdisk24 U9119.595.8381C1D-V12-C2-T1-L840000000000 Virtual SCSI Disk Drive
hdisk25 U9119.595.8381C1D-V12-C2-T1-L880000000000 Virtual SCSI Disk Drive
hdisk26 U9119.595.8381C1D-V12-C2-T1-L900000000000 Virtual SCSI Disk Drive
hdisk3 U9119.595.8381C1D-V12-C4-T1-L8e0000000000 Virtual SCSI Disk Drive
hdisk27 U9119.595.8381C1D-V12-C4-T1-L860000000000 Virtual SCSI Disk Drive
hdisk28 U9119.595.8381C1D-V12-C4-T1-L8a0000000000 Virtual SCSI Disk Drive
hdisk29 U9119.595.8381C1D-V12-C4-T1-L8c0000000000 Virtual SCSI Disk Drive
hdisk30 U9119.595.8381C1D-V12-C4-T1-L840000000000 Virtual SCSI Disk Drive
hdisk31 U9119.595.8381C1D-V12-C4-T1-L880000000000 Virtual SCSI Disk Drive
FROM VIOS

lsdev -slots

1. Slot Description Device(s)

U5791.001.99B01X8-P1-C01 Logical I/O Slot pci18 fcs0
U5791.001.99B01X6-P1-C01 Logical I/O Slot pci28 fcs4
U5791.001.99B01X8-P1-C02 Logical I/O Slot pci19 fcs1
U5791.001.99B01X6-P1-C02 Logical I/O Slot pci29 ent6
U5791.001.99B01X8-P1-C03 Logical I/O Slot pci20 ent1 ent2
U5791.001.99B01X6-P1-C03 Logical I/O Slot pci30 ent29
U5791.001.99B01WP-P1-C03 Logical I/O Slot pci36 ent33
U5791.001.99B01X6-P1-C04 Logical I/O Slot pci31 ent30 ent31
U5791.001.99B01X8-P1-C05 Logical I/O Slot pci22 fcs2
U5791.001.99B01X6-P1-C05 Logical I/O Slot pci32 fcs5
U5791.001.99B01WP-P1-C05 Logical I/O Slot pci38 fcs6
U5791.001.99B01WN-P1-C05 Logical I/O Slot pci44 fcs7
U5791.001.99B01X8-P1-C06 Logical I/O Slot pci23 ent3
U5791.001.99B01X6-P1-C06 Logical I/O Slot pci33 ent7 ent8
U5791.001.99B01WP-P1-C06 Logical I/O Slot pci39 ent9 ent10
U5791.001.99B01WN-P1-C06 Logical I/O Slot pci45 ent11
U5791.001.99B01WM-P1-C06 Logical I/O Slot pci53 ent13
U5791.001.99B01X6-P1-C07 Logical I/O Slot pci34 ent32
U5791.001.99B01X8-P1-C08 Logical I/O Slot pci16 ent0
U5791.001.99B01X6-P1-C08 Logical I/O Slot pci25 fcs3
U5791.001.99B01X6-P1-C09 Logical I/O Slot pci26 ent4 ent5
U5791.001.99B01WM-P1-C09 Logical I/O Slot pci47 ent12
U5791.001.99B01X8-P1-C10 Logical I/O Slot pci55 sisscsia0
U5791.001.99B01X6-P1-C10 Logical I/O Slot pci27 ent28
U5791.001.99B01WM-P1-T5 Logical I/O Slot pci51 scsi0
U5791.001.99B01X8-P2-C10 Logical I/O Slot pci67 sisscsia1
U9119.595.8381C1D-V200-C0 Virtual I/O Slot vsa0
U9119.595.8381C1D-V200-C2 Virtual I/O Slot vhost0
U9119.595.8381C1D-V200-C3 Virtual I/O Slot vhost1
U9119.595.8381C1D-V200-C4 Virtual I/O Slot vhost2
U9119.595.8381C1D-V200-C5 Virtual I/O Slot vhost3
U9119.595.8381C1D-V200-C6 Virtual I/O Slot ent36
--> U9119.595.8381C1D-V200-C7 Virtual I/O Slot vhost4
U9119.595.8381C1D-V200-C9 Virtual I/O Slot vhost5
U9119.595.8381C1D-V200-C10 Virtual I/O Slot vhost6
U9119.595.8381C1D-V200-C11 Virtual I/O Slot vhost7
U9119.595.8381C1D-V200-C12 Virtual I/O Slot vhost8
U9119.595.8381C1D-V200-C13 Virtual I/O Slot vhost9
U9119.595.8381C1D-V200-C14 Virtual I/O Slot vhost10
U9119.595.8381C1D-V200-C15 Virtual I/O Slot vhost11
U9119.595.8381C1D-V200-C17 Virtual I/O Slot vhost12
U9119.595.8381C1D-V200-C18 Virtual I/O Slot vhost13
U9119.595.8381C1D-V200-C19 Virtual I/O Slot vhost14
U9119.595.8381C1D-V200-C20 Virtual I/O Slot ent14
U9119.595.8381C1D-V200-C21 Virtual I/O Slot ent15
U9119.595.8381C1D-V200-C22 Virtual I/O Slot ent16
U9119.595.8381C1D-V200-C23 Virtual I/O Slot ent17
U9119.595.8381C1D-V200-C25 Virtual I/O Slot vhost15
U9119.595.8381C1D-V200-C26 Virtual I/O Slot vhost16
U9119.595.8381C1D-V200-C27 Virtual I/O Slot vhost17

I installed now the last firmware microcode for fibre channel adapter

fcs6 U5791.001.99B01WP-P1-C05-T1 FC Adapter

Part Number.................80P4543
EC Level....................A
Serial Number...............1D511067BD
Manufacturer................001D
Feature Code/Marketing ID...280B
FRU Number.................. 80P4544
Device Specific.(ZM)........3
Network Address.............10000000C94901B1
ROS Level and ID............02881955
Device Specific.(Z0)........1001206D
Device Specific.(Z1)........00000000
Device Specific.(Z2)........00000000
Device Specific.(Z3)........03000909
Device Specific.(Z4)........FF801413
Device Specific.(Z5)........02881955
Device Specific.(Z6)........06831955
Device Specific.(Z7)........07831955
Device Specific.(Z8)........20000000C94901B1
Device Specific.(Z9)........TS1.91A5
Device Specific.(ZA)........T1D1.91A5
Device Specific.(ZB)........T2D1.91A5
Device Specific.(YL)........U5791.001.99B01WP-P1-C05-T1
PLATFORM SPECIFIC

Name: fibre-channel
Model: LP10000
Node: fibre-channel@1
Device Type: fcp
Physical Location: U5791.001.99B01WP-P1-C05-T1
lsmap -vadapter vhost4
SVSA Physloc Client Partition ID
<hr />
--------------------------------------------<hr />
vhost4 U9119.595.8381C1D-V200-C7 0x0000000c

VTD vhdisk33
LUN 0x8100000000000000
Backing device hdisk33
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L7B000000000000

VTD vhdisk42
LUN 0x8200000000000000
Backing device hdisk42
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L7C000000000000

VTD vhdisk48
LUN 0x8300000000000000
Backing device hdisk48
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L7D000000000000

VTD vhdisk49
LUN 0x8400000000000000
Backing device hdisk49
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L7E000000000000

VTD vhdisk50
LUN 0x8500000000000000
Backing device hdisk50
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L7F000000000000

VTD vhdisk51
LUN 0x8600000000000000
Backing device hdisk51
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L80000000000000

VTD vhdisk52
LUN 0x8700000000000000
Backing device hdisk52
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L81000000000000

VTD vhdisk53
LUN 0x8800000000000000
Backing device hdisk53
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L82000000000000

VTD vhdisk54
LUN 0x8900000000000000
Backing device hdisk54
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L83000000000000

VTD vhdisk55
LUN 0x8a00000000000000
Backing device hdisk55
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L84000000000000

VTD vhdisk56
LUN 0x8b00000000000000
Backing device hdisk56
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L85000000000000

VTD vhdisk57
LUN 0x8c00000000000000
Backing device hdisk57
Physloc U5791.001.99B01WP-P1-C05-T1-W5006048441DC3ED5-L6E000000000000

VTD vhdisk58
LUN 0x8d00000000000000
Backing device hdisk58
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L87000000000000

VTD vhdisk59
LUN 0x8e00000000000000
Backing device hdisk59
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L88000000000000

VTD vhdisk60
LUN 0x8f00000000000000
Backing device hdisk60
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L89000000000000

VTD vhdisk61
LUN 0x9000000000000000
Backing device hdisk61
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L8A000000000000

VTD vhdisk62
LUN 0x9100000000000000
Backing device hdisk62
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L8B000000000000

VTD vhdisk63
LUN 0x9200000000000000
Backing device hdisk63
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L8C000000000000

VTD vhdisk64
LUN 0x9300000000000000
Backing device hdisk64
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L8D000000000000

VTD vhdisk65
LUN 0x9400000000000000
Backing device hdisk65
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L8E000000000000

VTD vhdisk66
LUN 0x9500000000000000
Backing device hdisk66
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L8F000000000000

VTD vhdisk67
LUN 0x9600000000000000
Backing device hdisk67
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L90000000000000

VTD vhdisk68
LUN 0x9700000000000000
Backing device hdisk68
Physloc U5791.001.99B01WN-P1-C05-T1-W5006048441DC3EFA-L91000000000000

Thank U,
Daniele
#AIX-Forum

Originally posted by: SystemAdmin

Hi Daniele!
1 - Do you have no_reserve on hdisk under both VIOS?
2 - Why dont you upgrade MPIO version on VIOS 2 ?
3 - To solve the problem with lspath (vscsi0 and vscsi1) you have to varyoffvgs, exportvgs, remove hdisks, cfgmgr, check with lspath and importvgs. Maybe this is causing the problem!!
4 - You didnt post the info about the second VIOS, but i think you configured the same disks. Please check it.

Sorry my english ...
Were are you from?

regards
#AIX-Forum

Originally posted by: niella

See ETA emc178925: PowerPath, CLARiiON: CLARiiON devices can no longer be seen on AIX after EMC CLARiiON FCP PowerMPIO support software file set installation.

Niel
#AIX-Forum

Originally posted by: SystemAdmin

Where I can find this document?
#AIX-Forum

Originally posted by: niella

I'm sorry, somehow the link did not work. Here is the write-up, it's from EMC's PowerLink website.

Question: ETA emc178925: PowerPath, CLARiiON: CLARiiON devices can no longer be seen on AIX after EMC CLARiiON FCP PowerMPIO support software file set installation

Environment: EMC Technical Advisory
Environment: OS: IBM AIX 5.x
Environment: EMC SW: AIX ODM 5.3.0
Environment: EMC SW: AIX ODM 5.3.1
Environment: The EMC CLARiiON FCP PowerMPIO support software file set was installed and removed.
Problem: CLARiiON devices will no longer configure into AIX.
Problem:
lsdev -Cc disk no longer shows any CLARiiON devices.
Change: Installation and subsequent removal of EMC CLARiiON FCP PowerMPIO support software.

Fix: Any time EMC CLARiiON FCP PowerMPIO support software is to be uninstalled, to be replaced by the EMC CLARiiON FCP support software file set, the following manual procedure must be performed:
odmdelete -q "uniquetype LIKE disk/fcp/EMCLAR*" -o PdAt
At this point, if the EMC CLARiiON FCP support software file set and EMC CLARiiON AIX support software file set are not installed, install them and run cfgmgr. If these file sets are already installed, running cfgmgr should result in CLARiiON devices being properly configured.
Also make sure failover mode is is set to 3,for this command to work correctly.

Notes: At the time of the writing of this article neither of the two MPIO CLARiiON file sets are supported. The issue described in this article is generally caused by accidental EMC CLARiiON FCP PowerMPIO support software installation, which is subsequently removed to install the correctly supported EMC CLARiiON FCP support software file set.
<hr />
Regards,
Niel
#AIX-Forum

Originally posted by: SystemAdmin

Thank U niella for support.
Now I want to investigate with EMC support about this problem because it's very strange.
I think that the problem is due to ODM EMC.
Today I have done a test in the same mode and I have (after a LPAR reboot) 2 situations:

1. Only 1 double hdisk.
So I remove this disk but I discover that the hdisk are different between VG association!!!
(ex. before I have hdisk2 associated to vgsapSEQ, now hdisk2 is for vgoraSEQ!!!)
So I exportvg - importvg all and I have now the 2° situation.

2. Double hdisk of all!!

(ex.
hdisk2 00c81c1db6a6f997 vgsapSEQ active
hdisk3 00c81c1db6a837af vgarcSEQ active
hdisk4 00c81c1db6a8ac2b vgdatSEQ active
hdisk5 00c81c1db6a8acd7 vgdatSEQ active
hdisk6 00c81c1db6a77504 vgoraSEQ active
hdisk7 00c81c1db6a77504 vgoraSEQ active
hdisk8 00c81c1db6a8ac2b vgdatSEQ active
hdisk9 00c81c1db6a837af vgarcSEQ active
hdisk10 00c81c1db6a8acd7 vgdatSEQ active
hdisk11 00c81c1db6a6f997 vgsapSEQ active )

What is it possible?
Thanks
#AIX-Forum

Originally posted by: IBMFORUMS

I have AIX machine connected to EMC SAN and I received a recommendation from EMC to upgrade the AIX 5.3 to TL7.
I suggest that you consult EMC.

Message was edited by: IBMFORUMS
#AIX-Forum

Originally posted by: SystemAdmin

Do you think the upgrade AIX is necessary for the VIOS too?
#AIX-Forum