Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

server cannot see bootlun on controllerA but can on controllerB

I got one brocade fc switch that both netapp contollers are connected to


its one fabric switch and 4 ports from the netapp is connected to 4 fc ports.


when I create vol/lun on controller A, the server cannot see the boot lun



but when i create vol/lun on controllerB the sever can see it


any idea?



On the FC switch, I verified both the initiators are zoned in correctly and also on the san


any idea?



Could it be the sanboot policy or the order? 

  • Unified Computing
New Member

Are both controllers

Are both controllers connected to both fabrics?

From your description it doesn't sounds like it matters if you go over fabric A vs B, it's which controller creates the LUN that seems to make the difference here.

The usual stuff to check is the active zoneset and make sure that both initiators (one for A and one for B) are allowed to hit the respective ports for the A and B controllers on the Netapp.


If the blades are supposed to boot from these luns then you can SSH to the UCSM address and after a reboot run the following to get a report from the option ROMs that should tell you more about what's wrong:

connect adapter x/y/z (chassis / blade / adapter)






What is going on on the controller side?

What do you get if you run "igroup show -v"?

This widget could not be displayed.