A minimum two FC paths is required for SAN disks. Once you see the new LUN, make sure that you also see all FC paths. If you are still not able to see the new FC/SAN LUNS, then, as a last resort, reboot the server and try again. If everything seems to be working, then issue the forcelip command to the other controller as well. Make sure disks didn't loose any SAN paths after the HBA reset. Verify the controller status using cfgadm -al.Reset the HBA using forcelip luxadm -e forcelip forcelip command can be issued to the controller names as cfgadm -al -o show_FCP_dev |grep fc-fabricĬ4 fc-fabric connected configured luxadm -e forcelip /dev/cfg/c2.(Do not try this in critical servers unless you are confident that multipathing is correctly configured) If you are still unable to see the new LUN/DISK, then, if you have multipathing enabled, you can try to reset the HBA. If you see any controller port WWN shown as “unconfigured," then you can initiate FC session using below mentioned cfgadm -c configure cfgadm -c configure c4::50080e8008cfb814. Zoning can be verified using the below cfgadm -al -o show_FCP_dev c2 c4.In the same way you can find the other controller information as well. HBA Port WWN: You can also find the WWN using luxadm command, if HBA is already connected to the FC luxadm -e dump_map /dev/cfg/c4 Verify FC ports are connected and cfgadm -al -o show_FCP_dev |grep fc-fabricĬ2 fc-fabric connected configured unknownĬ4 fc-fabric connected configured To find the HBA’s World Wide Node number (WWN), use the fcinfo fcinfo hba-port |grep Port.List the connected luxadm -e port |grep CONNECTED.The following commands are useful for general SAN stack fact-finding on Solaris: Understanding How FC is Configured on a Solaris Host
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |