StorNext for Windows comes with many of the same commands that are available with Xsan on Mac OS X. Located by default in the c:Program FilesStorNextbin directory, you can use the cv* commands in much the same way as on a Mac. This can help with regards to troubleshooting. For example, if you are having problems getting a volume to mount, even though it shows up when you go to map the drive in Client Configuration, you can use cvlabel -l (assuming your working directory is the StorNext bin directory) to see the LUNs that are accessible by your host. If you cannot see your LUNs then you also cannot map a drive to those same LUNs (it will work in the Client Configuration utility but you will not be able to see the volumes in Windows Explorer or from a command prompt.
Once you have confirmed that you can see Xsan LUNs from StorNext and that you can communicate with the Metadata Controller go ahead and stop and start the FSS to see if the volume then appears in Windows Explorer.
If you’re using StorNext as actual Metadata Controllers then there are a number of other commands that you can leverage, again similarly to how you would do so with Xsan. For example, to start a volume, you would use the cvadmin command followed by start and then the name of the volume. For example, if your volume was named bighonkinvolume you would use the following:
cvadmin start bighonkinvolume
krypted May 27th, 2009
Posted In: Windows Server, Windows XP, Xsan
Command line, StorNext, windows, Xsan