edit by bakunin: you seem to have found about every tag available in the editor - with the notable exception of the only one you really should use: the CODE-tag. I have edited it in for you now, but i suggest you do it yourself from now on. Thank you!
Unfortunately I was right - you have different PVIDs in lspv output - 0006b23f7962b123 and in VGDA - 000b63ca2e698c7b. As for me it seems to be a reason, why you couldn't import the VG.
You have to do the following:
Open a call at IBM. Just write - we want to import a vg from a disk, it doesn't work. If you have a support contract, they should help you now. It is very important to open the call, because all the following actions can be destructive and you can loose your data.
Make a snapshot or some other sort of backup from your LUN. Just because you can loose your data.
After you have made backup and opened a call at IBM, there are three options:
change PVID in VGDA manually, using dd and/or shell. It is an expert option and I wouldn't recommend it to do, if IBM support doesn't say the same.
recreate volume group using recreatevg command. It will change your VGDA and it can make your VG completely unavailable. That's why it is important to have a snapshot from the LUN. But if it works, it is the fastest and easiest option.
restore from the last backup if you have any. It is the most time-consuming option, but the most sure for your data.
A few words from the moderator, some of them of possibly general interest:
@jhudson12: please heed the advice i left when editing your posts. When you agreed to the terms of service you agreed to use CODE-tags to further the readability of your posts. It might look petty to insist on it, but we try to make the threads we produce here of as much lasting value as is possible. Readability contributes to that goal a considerable amount. COLOR-, FONT- and similar tags make posts less readable on some devices which is why we try to avoid them as much as possible.
Normally we have an infraction system for the neglect to use proper formatting but i think the audience here is mature enough to understand why the rule is in place and willing to follow it once the reasoning is properly explained. Am i mistaken?
@agent.kgb: I kindly ask you to take a nights sleeping and read your words again:
Quote:
I like people, who mark wrong answers with "thanks".
I know you are one of the most capable experts (if not the most capable one of us all) here and you know that - seemingly - too. But i ask you to consider this: will it make your light shine brighter when you make the light of others look dimmer?
I do not suggest to forego XrAys hazardous suggestion and you are perfectly entitled to point out why and how it is hazardous. And you could do so and be the admired hero of this board for your unfailing expertise - instead you choose the form guaranteed to make the majority here accept your undisputed technical prowess through gnashed teeth. In my humble opinion this is a great loss for all involved, regardless of the outcome. And what drives me crazy is the thought that it would take such a minimal change to turn a lose-lose-lose situation into a win-win-win-situation.
Frankly, life is too short and i am too old for unavoidable tragic. Do an old man a favour and capitalize on the great work you do here. I like to think of here as my virtual living room and it aggrieves me to see unnecessary hardships here.
Finally, i have a few technical observations too, in addition to agent.kgbs posting:
Quote:
The existence of the LUNZ-device tells me there is something amiss with either the zoning, the FC-adapter or - generally - with the something inbetween the SAN and the LPAR. My suggestion is to remove all the devices hierarchy: pathes to the disk, fcnet and so on, down to the FC-adapter-device, then run cfgmgr again to make sure the configuration is accurate. It might be worthwile to check the integrity of the ODM and remove any artefacts before the cfgmgr run, but this is also advanced work and needs knowledge of AIX.
As far as i remember the CLARiiON there is a (Windows) GUI where you can create copies of the LUNs. I am not sure about snapshots, though, you might have to create a complete copy of the SAN volume. In any case, snapshots and/or copies, create at least one such fallback device before you proceed. It is better to have to throw away a copy you haven't needed than to bemoan the need of an additional copy you have not made while it was possible.
A last thing, because the powermt command is not in the PATH: do an
and see what comes up. powermt should be in one of the filesets listed, so do a
for each fileset until you find it. Add the path it is in to your PATH variable.
we build another server to make sure we didn't have conflict, go same error... unfortunately we can not copy or backup the LUN... I will be calling IBM unless someone else has a suggestion for a solution.
I apologize for not following your rules, first time every using this site, for all furture questions I will make sure I do the right thing.
I apologize for not following your rules, first time every using this site, for all furture questions I will make sure I do the right thing.
Hey, no big deal. Everything is good.
Quote:
Originally Posted by jhudson12
I will be calling IBM unless someone else has a suggestion for a solution.
Indeed i think i still have a few ideas. First, you need to locate the powermt command. I am quite sure you have it on the system, it is perhaps not in your PATH. i suggest to do a
and grep the output for powermt. Then put the path the command resides in into your PATH variable.
Then, after you have found it, do a
and look what comes up. We have no CLARiiON any more since a few years but if i remember correctly the CLARiiON LUNs are named the same way as the VMAX LUNs: hdiskpowerXX. You cannot use the hdisk-devices, because they represent only single paths to the LUN, you need to use the hdiskpower-pseudodevice.
I guess your hdiskpower-device is missing. I suggest to delete all the devices down to the FC-adapters, then run cfgmgr to rebuild the device hierarchy again. A hdiskpower0 should come up. Then you may try an importvg from this device, not a hdisk-device.
Still the warning of agent.kgb is correct: this might damage the LUNs content. Create a backup copy (or snapshot, but i think there is no snapshot functionality in the CLARiiON) and only then try this.
Then this:
Is not looking all too kosher to me. There seems to be trouble in the connection between LUN and system. It might be the zoning, it might be something else, but otherwise there should be no failed path.
Hi Experts , I want to start migrating our AIX 6.1 to AIX 7.1 . I am planning to use alt_disk_migration . Chris gibson has awesome documentation in the internet. However I am running into an issue with EMC odm filesets . So my current OS is AIX 6.1. and I have this :
lslpp -l | grep EMC
... (7 Replies)
Hello all!
I have not so much experience with AIX
We have test p5 server. On server was deployed VIOS + 3 LPAR + AIX6.1
There is a test HACMP cluster of two nodes, the cluster is identical to production cluster (all clusters and hosts have been configured by specialist of integrator company and... (3 Replies)
Hello all,
i try to allocate the same LUN to two server (or more in the future)
i use solaris 10, vxvm (vxfs) for data and solaris zones and EMC DMX-4, i try to migrate solaris zones between servers in case of problem.
and this is what i want to do
- affect LUN to srv00124 and srv10155
-... (5 Replies)
Hello guys, I'm going crazy over here with a problem with a LUN created on a EMC CX3.
I did sucessfully managed to create the LUN on the Storage (the LUN is named DBLNX25EC_TST), after doing the following process:
echo "1" > /sys/class/fc_host/host<n>/issue_lip
and
echo "- - -" >... (10 Replies)
I have seen a few threads / posts on the forum's but nothing specific to what Iam after. So Iam hoping you can help.
Issue : Iam hoping to remove unused emc luns from my solaris servers , T2000 (5.10 Generic_142900-02). I have a list of the process I have followed for the removal of the luns.... (3 Replies)
Hi All..
On to a new implementation with AIX 7.1 san boot from EMC disks (Using NPIV). Anyone played with this recently?
Wondering if we need PowerPath on the AIX clients or has native MPIO matured to replace it. Thoughts?
Thanks
Mr B (6 Replies)
Hi all,
I hope I'm putting my first post at this site into the right forum. I need help finding the EMC disk driver for AIX version 5.3. I have some new EMC disk presented to a backup server of mine, and right now the EMC hdisks show up looking like this in an lsdev:
hdisk495 Available... (2 Replies)
This may sound like an absolute rookie question, and it is.
I have been working on Migrating our HP and Solaris servers to the new EMC SAN and know the routines backwards.
Now we've suddenly got a new IBM server and I don't even know how to check if it is connected to the switch.
Can someone... (1 Reply)
We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)