As suggested by one of our friends on this forum, Lee, i have installed SF for Windows 5.1 on by windows 2008 virtual machine.
i have provisioned couple of iSCSI luns from my NetApp Filer.
everything went fine as far as disk discovery on the server.
my problem is when i run the #vxdisk list command, it shows that the disks are not initialized. i think i cant go forward with out doing that.
but the good side is, i can able to see the disks in the VEA GUI and i am able to initialize the disks, create disk groups, volumes and so on...
i am curious to know how to initialize the disks using command line.......coz after that i can use other good commands to create the disk groups, volume and so on....
is there any difference between how VERITAS sees SCSI disks and iSCSI disks?
Note: If the disks do not have a signature, you will actually have to include "(No Signature)." In Windows 2008, it is necessary to bring the disks online before they can be used. This was not necessary in 2003.
Additionally, once the disks are brought online, you can write a signature to the disks through the CLI by using the following command:
vxdisk sig <Harddisk#>
SFW should see no difference in the way a disk is managed, when comparing iSCSI to Fibre accessible SAN storage.
While, SFW 5.1 does have the iSCSI information displayed in the VEA GUI, the software should manage the disks in a similar fashion.
Mike, I have searched the CLI section of the SF Admin Guide - vxdisk online is not mentioned at all.
Is there perhaps a separate CLI manual available? I have searched sfdoccentral (http://sfdoccentral.symantec.com/Storage_Foundation_HA_51SP1_Windows.html).
I just tested this in my lab using the information provided by Mike and confirmed it works properly.
1. In VEA, I have a disk that is offline and when viewed under 'Disks' in the left pane, I see it listed as follows: Harddisk 11 (No Signature)
2. I ran: vxdisk online "harddisk11 (No Signature)"
3. Command completed successfully and the disk was then online, but still didn't have a signature (as expected).
As EJameson pointed out, you would then need to write a signature to the disk before it would be available to add to a disk group or add a basic volume; however, the command provided will not work. The actual proper command (using harddisk11 from the example above) would be:
vxdisk sig \Device\harddisk11 diskstyle=MBR
vxdisk sig \Device\harddisk11 diskstyle=GPT
* The difference being whether you want the disk formatted as MBR or GPT
As with any sfw command, you can simply type vxdisk -? to provide all available options. In addtion, you can also get further syntax assistance on a specific operation by providing the specific operation followed by -?, for example: vxdisk sig -? or vxdisk online -?
I hope this helps -- If the command still fails, can you paste the command and failure message directly from your command prompt to confirm your syntax is correct and so that we have the entire details of the error?
I just checked the 5.1 SP1 guide and did not see it there either.
I think this is a relatively new addition. Manually onlining disks was not necessary prior to 2008. It's possible that it just hasn't been added to the documentation yet. I will bring this to the attention of the people that update the documentation.