I could not see the Adapters or disk in PowerPath

reboot your windows system ..Powerpath does not see the LUNs and unfortunately not capable of discovering them on the fly like it can on other platforms.

Are you managing the host via M$ Terminal Services ??

such command does not exist on Windows

When you say you can see the disk in Device Manager, do you mean "device manager" or "disk manager"? Eventually they will show up in both, but there will be a device in "device manager" for each path to the LUN while if PowerPath is working you will only see one disk appear in "disk manager". I have seen situations where PowerPath doesn't show me the adaptor or disk until I've actually written a signature on the drive in "disk manager". Have you done this step yet?

Hi,

Did u try running the powermt config command to make the powerpath see the devices?

HDUD

"Powermt check" does the same I think

Ah, all right then.... Never had to use the CLI to get devices working under PP. I always did a rescan in disk manager (or a reboot.... yeah, it's windows) and PP automatically picked up new devs.
You don't have to do a reboot each and every time you add new devs ! Unfortunately sometimes you do

i am going to have to disagree ..here are descriptions from PowerPath admin guide:

powermt check checks specified paths and, if desired, removes from
the PowerPath configuration any paths marked dead.

powermt config configures all detected Symmetrix and CLARiiON
logical devices as PowerPath devices and adds these devices to the
PowerPath configuration.

Have you licensed PowerPath?
Check from the PP GUI (Tools > Options > Licenses, or thereabouts)

yeah ..with windows the only reliable option for me has been rebooting. Like Forest Gump put it "Windowz is like a box of chocolates. You never know what you're gonna get"

ok ..slightly modified quote

I'm not M$ addicted .. But I have to say that sometimes Window$ isn't that bad ...

If you are managing your servers via Terminal Services, this specific product have a nasty behaviour. If your server discovers new devices, they will not work correctly untill you simply log off and log on again. In the past I used to reboot my windows servers but later I discovered that Terminal Services have some "specific undocumented features" (or bugs if you prefer) that prevents you from managing the devices discovered in the session you are using. You have to log off and log on (and obtain a new session) and the devices will become available as usual. No reboot required.
Another "feature" of MSDTS is that if you change an environment variable (let's say PATH) it won't work in the same session.. You'll have to log off and log on again to have the variable correctly working. You can see this "feature" while installing (via MSDTC) Networker or Solution Enabler. Right after installing the product, you open a CMD and issue a couple of CLI commands .. And they will not work! But if you log off and log on again (no reboot again) the path will be fine and the commands will work as expected.

Can someone please confirm this nasty behaviour ??

About this path behavior I mist disagree or at least explain in more detail:

When you open a dos window (command line) you get a certain set of environment variables, including the path variable. When you now change this in the GUI, this CLI set is not changed. If you open up a new CLI window, you DO get the new variable ! So you don't even need to logoff / logon again ! Simply open a new dos box. This goes for all variables AFAIK.
This is the same as on UNIX: the .profile is read when you logon. when you change your .profile your running set of vars isn't changed until you open a new telnet session (logoff / logon).

So in fact UNIX is even worse, since you actually do need to logoff and logon again to get a new variable working while in Windows all you need to do is open a new dos box.

Rob in my experience, with either W2K and W2K3, using MSDTC this will not work as you advertised. If I open a cmd after installing Networker or S.E. the new cmd (started AFTER the install) won't pick up the new PATH. YMMV

Message was edited by:
Stefano Del Corno

the problem you describe with disk not showing up until after you log off and log back in ...that's exactly what we were experiencing with WIN2K, but i have to admit MS did a better job with WIN2K3 ..when you rescan in Disk Management ..disks show up without having to log off/log back in ...if we could only get Powerpath to pick up devices on the fly ...that would be nice.

I'm not telling you nonsence. Of course I tried it before I wrote this down. Trust me: it works as I described.... On my servers with an RDP session (Terminal Services).