Power path not discovering new paths

Hi,
This SAN reconfiguration means that one port of CX500 will be moved from one switch to other. So some of the existing paths will remain, some will be deleted and new paths should be added.
Yes, NaviAgent is running. The server remains registered to the storage, but no new paths are discovered even after reboot.

Hi,

Could you describe a bit more what are your "SAN connections reconfiguration" ? Will the server see the same CX500 by other paths ?
If you are changing the zoning, then you should probably check the registration and so on. Are you running NaviAgent ?

Yes we are moving to another fabric.
The zoning has been commited. I'm not sure what exactly is in "Connectivity status" , because I'm not on site. Could you tell me your doubts, what could be wrong ?
If the status of Initiator WWN is not logged in and registered this means that it is registered, but not seen in the fabric. And if the status is logged in and not registered this means that it is seen in the fabric, but not registered to the storage. Am I right ? What should be done in both cases if powerpath does not see the new paths.

I have the same problem with CX3-20f storage. In "Connectivity status" initiator WWNs are shown as logged in and not registered. When running NaviAgent the host is not registered and no paths are shown in powerpath. When running Navisphere Server Utility and choose register "No paths to storage" is displayed. But when I manually register host from the storage it works ?!

OK and I guess you are moving it from a fabric to another.
Firstly could you check if the zoning has been commited (the effective configuration must the same as the defined configuration) ?
Secondly, even if the server remains registered, the new paths must be added in the registration. Could you tell us what you see exactly in "Connectivity status" ?

Well, I think it could be more a binding problem than a registration problem. I guess the SP port which is moved was previously seen by HBA1 and should now be seen by HBA2, as you said you are moving to another fabric.

To update the binding you should first check if the registration is good in Connectivity Status. If yes, the update the binding :
- Enable enginering mode in Navisphere
- Go to Storage Group Properties -> Hosts -> Advanced. Here you should see each one line for each Initiator and SP Port couple. Enable the new lines and disable old lines.
- Then you should see new paths in PowerPath (in some case you have to "rescan")




Yes I think so.

emc111684

Yes, the SP port that is moved is previously seen by HBA1 and how it should be seen by HBA2.
So I have to check bindings for each storage group.
How to enable engineering mode in Navisphete ?

Thanks, I checked emc111684. How about the issue with CX3-20f storage. In "connectivity status" the initiators are listed as logged in and not registered. When I run NaviAgent they are still not registered. When I run Navisphere Server Utility and check register - I get the message - no paths to storage found. Also in powerpath no paths are listed. But when i register the host manually throught the storage it works ! Could this be HBA drivers issue ?

Does your problem with CX3-20f storage concern Windows hosts too ? I had several problems with automatic registration on Solaris hosts but it was not serious.

Is your first problem resolved ?

Ques1... Are you able to see the disks at HBA level (HBAnywhere in case of Emulex, SanSurfer in case of Wlogic)

Ques 2: Why do you want to save the configuration? It is only recommended for Unix host and in case of Windows, if there are a lot of LUNS presented. Remove the powermt.customer file and reboot the host, host will scan for the LUNS and present it to OS.

Yes with CX3-20f the hosts are running Windows 2003 SP2 R2.
Your explanation of the first problem seems very reasonable. In order to be sure that this will resolve my problem I have to test it. Unfortunately I'm not on site and need permission to do it. I'll wright back when I try it.

Yes, the HBAs are Qlogic and SANSurfer shows that they are connected to the storage.