I did see this article, but this is basically just a different way of working around the problem instead of using that emcpadm tool which gives you a more direct way to rename devices. Looks like that emcpadm utility was only introduced in later version of PowerPath 4.x.
I'm looking more for ways to get more consistent results without having to juggle around the configuration file.
This is aimed mostly at clustering, but also been a problem with some software updates. Meaning LUN 0 presented will translate into emcpowerA, while LUN 1 will translate into emcpowerB, etc.
On upgrades have had cases were going from version say 4.x to 5.x a device that was emcpowerA is now emcpowerC because (I'm speculating) the rules changed.
i see. We had the same issue with our RAC servers, system admins had to manually rename them back to what they were before the upgrade, they were not too happy but then we don't upgrade PP too often ..sorry don't have any tips for ya.
I'm looking more for ways to get more consistent results without having to juggle around the configuration file.
Bonardg if I understand what the primus said, it's impossible by design.
PowerPath numbers its pseudo's based on first availability or in other words as the O/S has built the device tree based on device creation of the native devices. It is not based on the Host LUN presentation of the storage groups.
Please have a look at the other primus ... they both explain (even if with different with a different accent) that each and every host will give its own name to the devices ... and that it's up to you to work around the "issue" and have the same names on both hosts ..
good article, but in my case PP was not skipping names, they would simply show up in different order from RAC node to another node. Not a big deal to rename them ..but sure is annoying.
xe2sdc
4 Operator
•
2.8K Posts
0
February 11th, 2008 06:00
bodnarg
2 Intern
•
385 Posts
0
February 11th, 2008 06:00
I'm looking more for ways to get more consistent results without having to juggle around the configuration file.
xe2sdc
4 Operator
•
2.8K Posts
0
February 11th, 2008 06:00
Have a look at emc112571 that talks about Clariion but tells the truth about emcpower devices
bodnarg
2 Intern
•
385 Posts
0
February 11th, 2008 06:00
On upgrades have had cases were going from version say 4.x to 5.x a device that was emcpowerA is now emcpowerC because (I'm speculating) the rules changed.
dynamox
9 Legend
•
20.4K Posts
0
February 11th, 2008 06:00
dynamox
9 Legend
•
20.4K Posts
0
February 11th, 2008 06:00
xe2sdc
4 Operator
•
2.8K Posts
0
February 11th, 2008 07:00
results without having to juggle around the
configuration file.
Bonardg if I understand what the primus said, it's impossible by design.
PowerPath numbers its pseudo's based on first availability or in other words as the O/S has built the device tree based on device creation of the native devices. It is not based on the Host LUN presentation of the storage groups.
dynamox
9 Legend
•
20.4K Posts
0
February 11th, 2008 07:00
xe2sdc
4 Operator
•
2.8K Posts
0
February 11th, 2008 07:00
xe2sdc
4 Operator
•
2.8K Posts
0
February 11th, 2008 07:00
issue man
closer to you then he is to us
Hmmm I don't really think that Linus is still in Finland ..
As per www.cs.helsinki.fi/u/torvalds/ it looks like he is in Santa Clara .. not that far from Chicago
But let me know if I have to ask my manager to set up a meeting with Linus and -hopefully- you
Maybe I can convert some of the points earned in the forums .. and pay me the flight
xe2sdc
4 Operator
•
2.8K Posts
0
February 11th, 2008 07:00
dynamox
9 Legend
•
20.4K Posts
0
February 11th, 2008 07:00
dynamox
9 Legend
•
20.4K Posts
0
February 11th, 2008 07:00
xe2sdc
4 Operator
•
2.8K Posts
0
February 11th, 2008 07:00
dynamox
9 Legend
•
20.4K Posts
0
February 11th, 2008 07:00