86 Posts

August 15th, 2012 07:00

Do you have any devices presented to the second (missing?) HBA?

Sam Claret

Technical Support Engineer III

Worldwide Technical Support – OSAPI Windows

Office Hours: Rotating shift, 7AM – 4PM GMT

Office #: +353 21 494 5981

1 Rookie

 • 

106 Posts

August 15th, 2012 07:00

Actually I found it, the HBA was disconnected from the storage group. I reconnected it and we’re good.

Thanks!

1 Rookie

 • 

106 Posts

August 16th, 2012 04:00

My guess is when they swapped HBAs the new HBA did not check into the storage group so I had to force a reconnect. Once I did that, problem solved.

4 Operator

 • 

5.7K Posts

August 16th, 2012 04:00

It must have been something like that. When an HBA has no LUNs Powerpath doesn't see the LUN.

Please mark the question as answered by marking the correct answer.

1 Rookie

 • 

106 Posts

August 16th, 2012 05:00

In summation:

DMX/VMAX > Clariion

Hah!

4 Operator

 • 

5.7K Posts

August 16th, 2012 05:00

True, because in Unisphere you can "administratively disable" an HBA, which happens by default when you change a defective HBA for a new one. In solutions enabler you do the masking on the new HBA and it works. Indeed

4 Operator

 • 

5.7K Posts

August 16th, 2012 05:00

Could be. If that was the case you should be able to see a 3rd HBA in the connectivity status (if they didn't remove the defective one)

1 Rookie

 • 

106 Posts

August 16th, 2012 05:00

They actually pulled the HBA and gave me the new WWN which I zoned in and connected to the host. I cleared the old WWN out of the host and thought it had registered with the storage group but that was not the case. I always thought PowerPath showed WWNs regardless and if there was no connection it would be X’d out. Guess that’s not true!

4 Operator

 • 

5.7K Posts

August 16th, 2012 05:00

And now you learned something new

1 Rookie

 • 

106 Posts

August 16th, 2012 05:00

True, lol! Never have this issue with DMX/VMAX arrays though ☺

No Events found!

Top