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>
Add a new comment
 
Your name:
Your e-mail:
Your comment:
 
Basic BBcode is supported.
Captcha:
Type the letters and numbers as shown.
/get/captcha/1734845757
Not readable? Get another.