Comments
 
posted on September 25th 2015, at 11:56
by lunarg

Assuming you have not configured that specific port as an L-Port, this can happen where the HBA did not completely log on to the fabric. This issue has been known to happen on Emulex HBAs.

To resolve, simply disable and re-enable the port on the SAN switch:

portdisable <port-number>
portenable <port-number>
 
 
« June 2025»
SunMonTueWedThuFriSat
1234567
891011121314
15161718192021
22232425262728
2930     
 
Links
 
Quote
« Have you tried turning it off and on again? »
The IT Crowd