StarWind Software

Dear madmagi,

Please, try this sequence of steps:
1) Add SMI-S provider
2) Create new Logical Unit
3) Add iSCSI Array in Storage properties dialog of Hyper-V host
4) Allocate storage pools in "Allocate Capacity"
5) At this point you should be able to Add new disks to Hyper-V host in its Storage properties dialog.

Madmagi, post results here, please.

Yuri,

I added a logical unit, shows up under Classification, StoragePools and Logical Units:

Gold - Classification
ConcretPool_VMSAN_ThinProvisioned - Storage Pool
YTest - Logical Unit (points to VMSAN with SMI-S Driver, which points to StarWind System)

Shows up as a logical unit, 25GB total capacity, 0 available, Assigned -No, Type - Fixed

In StarWind the new image shows up as a IBV type of file, not an IMG like the screenshots. I have no idea how it changed.

Then it gets weird, i have 5 servers named HYPERV01 - HYPERV05; all configured the same, same local accout, domain account, policies, etc.
All of them are 2012 Servers

all 5 of them only give the option to add storage of "file".

So i am stuck again. - Ideas?

madmagi,

Could you provide screenshots for every step?
This will help us to understand your problem.
Thank you!

Yuri,

Sorry i have to add the screenshots 3 at a time, cant upload them all as a zip, too big. Cant upload more than 3 per post. So multiple posts

Here they are in order

Next 3

ANd the next three

next

And the rest.

I hope this helps you figure out what is going on.

Thanks Yuri!

Madmagi

Madmagi,

Please, check that you have created empty Target using StarWind Console on StarWind iSCSI Service.
After creating that target you should do Rescan of provider and do Refresh of Hyper-V hosts.

Please, read manual carefully
("Using SW SMI-S Agent with SC VMM 2012 SP1" - http://www.starwindsoftware.com/using-s ... m-2012-sp1):
Configuring StarWind iSCSI SAN
Before configuring StarWind SMI-S Agent, you need first to configure StarWind iSCSI SAN Service.
Use StarWind Management Console to connect to StarWind Service and then create an empty iSCSI
target (Figure 1 and Figure 2). Let's give it the name «empty».

Yuri,

I am sorry, was tired and just missed that step while going through it again. Will redo and update thread.

Acutally i have that target, even called it empty like the guide.

I just didnt get a screenshot of it.

Thank You

madmagi

Yuri,

So the empty target was there, What i did to put the screenshots together was delete everything in VMM, re-add step by step while taking screenshots. The whole time the empty target was in place.

Do you want me to clear everything again, delete the empty target and then walk through again, screen shot and post?

If i understand correctly the result should be exactly the same.

I can move the SMI-S back to the storage host (where StarWind iSCSI software is running), keep it on the seperate machine (VMSAN) or even try another possibility if you suggest one. I really want to get this working. Let me know what you would like me to do next.

Thank You

Madmagi (aka Lester)

Yuri,

I have completly rebuilt my storage machine, reinstalled the iSCSI software, the SMI-S provider and walked very carefully through the guide. Same result.

I am guessing it is something with my environment.

Thank You for your help.

madmagi

madmagi,

Sorry for late reply.

Please, try to add discovery portal (address of the host where StarWind service is running) to iSCSI initiators on HyperV hosts manually. Check that "empty" (in not connected status) target exists in the available targets list in iSCSI Initiators.
After that:

• Refresh HyperV host in VMM
• Rescan provider
• Try to allocate pools

Yuri,

Sorry my turn to be away - i was at TechEd, said hi to the people at your booth.

Will give this a go as soon as i can get some time and i will let you know how it works.

Will i have any issue using SP2 when it is out later this month?