This content has been marked as final. Show 5 replies
I assume you're on Ops Center 11g Update 3? If the Agent on the system with the LUNs has been running for awhile, Ops Center should have found any LUNs available to allow you to autopopulate the FC Library. Or at least you should be able to add individual LUNs to the Library for testing.
Does "mpathadm list LU" on the Agent system show the LUNs? If so, when you run "mpathadm show LU <disk>" on one of them (i.e. "mpathadm show LU /dev/rdsk/c0t60000230000192700384523030454352d0s2") what does it show for the "Name" of the disk? It should be a full IEEE 32-char disk name (like "60000230000192700384523030454352" from the previous example). If you see a shortened name (i.e 16-chars) then it's not going to work: perhaps you're using something like EMC PowerPath for redundancy and not Solaris MPxIO? MPxIO is required for Ops Center 11g to manage LUNs in a FC library.
Once you can get OC to see the LUNs... everything else should "just work" :)
Yep, that's what I did - manually added it, and it worked. But it doesn't seem to give me the functionality that I had expected. It seems like it allows me to create more zfs file systems for the zone ("Add File System"), not a raw disk map to the zone like I wanted. From the zone I should be able to run format and see the disk...
Do you know if it's possible to do this from Ops Center, or do I need to do it the old fashioned way and use "device match" in /etc/zones/zonename.xml ?
Thanks for your help.