When replacing one of the controllers in eva5000 we had a new wwn and serial number thus making it very complex to update all secure path configurations. Does anyone know of an 'easy' way to do this?
Hi, it can be done online with the following conditions: a) off peak hours b) perform the SecurePath failover to the remaining controller before the "bad" controller replacement
not to forget on the step c) :-) c) if you have any single path hosts, which are connected only to the failed EVA controller, they should be shut down.
A new WWN? Did you reinitialize the EVA? The front-end WWPNs are a soft-item and should have been retained from the meta-data. Or did the controllers somehow swap them?
Some clarification: The replacement was done the standard way, shutdown controller B ( in this case ) and replace it. The problem we had was that the new controller had, of course, different serial number and WWPN's so we should have to rebuild the Secure Patch configuration files as they holds the old controllers data.
That shouldn't have happened... The WWN is stored on the disks rather than the controllers.
A controller replacement *should* be completely transparent to the connected hosts. I've done a couple and didn't have to change anything on the host side - although I was never using SecurePath...
Tend to agree with the above comments. Check out this HP website for how to replace a EVA5000 controller, of any EVA part for that matter [and anything else HP!]:
