If I wanted to convert an existing Host that is connected to my CX3-10c via iSCSI initiator and has several LUNs, could I just simply make the conversion, or would the Navisphere see it is as a totally new server and I'd have to decommision it and all that jazz before making the change??? Thx!
Hmmm, interesting. So you're P2V'ing this host ? Did it boot from local disks ? I'd assign a boot disk out of a VMFS volume of the ESX cluster it will reside on. The VM itself wil still have the iSCSI initiator software and will still be able to see the LUN's on the CX. The ESX doesn't have to know anything about this iSCSI traffic. As far as Navisphere's concerned nothing changes.
Thanks for the reply...YES I am Physical-2-Virtualing this machine (eventually) and am just trying to make sure I have my ducks in a row. We use Hyper-V and not VM-ware but I guess the principle is the same? This box does boot from local drives currently. I just wanted to specifically know, if I convert it to virtual, is there anything at all that must be done in the Navisphere, or can I leave the storage group and LUNS as they are and it will just work with no other action on my part required except making the conversion to virtual??? ORRR do I have to remove the existing physical host from the storage group in the navisphere and then treat it like a totally new host once it is converted to a irtual machine? thx
Okay well the LAN IP, machine name, iSCSI IP's will all stay the same...I do not know how to determine if the IQN will stay the same? Sounds to me like it might work though based on what you guys have said so far...has anyone else tired this before themselves?
When you convert from physical to virtual will the hostname and IP address stay the same?
On the clariion a host gets registered using the hostname, IP Address of the host LAN (not the iSCSI addresses), the WWN (in the case of fibre channel HBAs) or IQN (in the case of iSCSI). If any of these change, you'll probably need to de-register on the array the physical host and let the virtual host re-register.
if you are concerned, take a snapshot/clone of this LUN and presented to a test VM. You will see that the only thing you will need to do is to assign a drive letter to the LUN. On your original VM you won't even have to do that, as far as it's concerned nothing changed but the SCSI driver for the boot drive. In your "rollback" plan ..you can take a snapshot of the LUN, if something does happen after P2V ..the "go back" plan is easy: restore the snapshot and power on physical server.
well even better that the server's LAN IP address will remain the same after it is converted right? So in reading back on what I am trying to do, you guys are confident it will work? Sry to keep houding but I gotta be sure. thx a million.
Ahhh well you present a new challenge as I have not had to use the snap view feature yet. Somewhere along the way the vendor guy who deployed our SAN told us that it was difficult to use and discouraged me in some fashion so I never looked into it further. In looking at the options in the Navisphere, it seems pretty simple though?
Anyway, I do have a test physical box connected to the SAN and a test LUN. I was interested in doing the P2V on that one 1st, but then reverting back I was not sure of how it would work. I wanted to keep this test machine a physical host for now as long as I have other physical hosts connected to the SAN. But if I could convert it temporarily without consequence then I'd do it. I am actually a little ways off from converting the production box but I am in the information gathering phase, Since I am just a jack of all trades and master of none, I don't work with the SAN on a daily basis so I really appreciate the assistance.
Well that vendor guy probably didn't know how to properly deal with a 'PC Load Letter' problem either... ;-)
There are a few config pre-requisites to take care of before using snapshots, but it is all in the help file and is pretty straightfoward.
If you have the time and an old server I would perform a test migration using a test host first. That way you don't have to impact any production systems and can comfortably blow stuff up without worry.
RRR
6 Operator
•
5739 Posts
410
1
Posted May 11th, 2010 04:00
Hmmm, interesting. So you're P2V'ing this host ? Did it boot from local disks ? I'd assign a boot disk out of a VMFS volume of the ESX cluster it will reside on. The VM itself wil still have the iSCSI initiator software and will still be able to see the LUN's on the CX. The ESX doesn't have to know anything about this iSCSI traffic. As far as Navisphere's concerned nothing changes.