[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 996
  • Last Modified:

VMWare ESX 4: How to connect the SAN?

Hi,

1) I have an HP server (360 DL) as follows:
-There are 2 Physical NIC
- There are 2 HD (mirror each other); each 140 GB
- There are another 2 HD (mirror each other); each 300 GB
-The RAM are installed in 3 channel; each channel has 3 slots (but max permissible used is 2 slots; "stupid rule?"); i have total 6 @ 4GB = 24 GB
2) I have just installed the ESX 4.0 (Enterprise edition) successfully
- The IP is "192.168.61.200"
-The SM: 255.255.255.0
-The Default Gateway: 192.168.61.1
- The DNS: 192.168.61.10
3) My planning: to install the VMmachines for 3 or 4 servers in the above HP server
4) I am still confused related to the SAN (We use the HP's SAN); How to RELATE or CONNECT these VMMachines with the SCSI SAN???
5) My Questions:
i) Should i have a SPECIAL switches for the VMmachines?
ii) The physical NICs are in the 192.168.61.0/24; how we RELATE or CONNECT these Physical NICS with the Virtual Nics? (What SUBNETS should we give to the Virtual Nics?)
iii) How to RELATE or CONNECT the VMmachines to the SCSI SAN??
6) The experts who have experienced designing and installing VMmachines (with ESX 4.0 host) would greatly help please (Please provide any suggestions or recommendation ,whatever you think, would provide better understanding related to this VMwares.
7) Thank you

tjie
0
tjie
Asked:
tjie
  • 3
  • 2
  • 2
4 Solutions
 
vmwarun - ArunCommented:
1.What type of Guest OS are you planning to install ? Windows or Linux ?
2.What is your iSCSI SAN Model and what is its storage capacity ? HP, Dell ?
3.Are you using VLANs or a single subnet in your network ?
4.Are you using vCenter to manage your ESX Hosts ?
5.On which Server Model (Dell, HP or IBM) have you installed ESX 4.0 ? Is it on the HP DL360 Server which you have mentioned ?
0
 
Paul SolovyovskySenior IT AdvisorCommented:
You should install at least at least 4 more nic ports (a single quad or 2 dual ports) for 6 total at min.

On the DL360 configure as follows

vswtich0 - 2 physical nic ports- service console and vmotion (if you get 8 nic ports you can segregate vmotion to it's own vswitch), the Service console will have an IP on your production network and you'll have an ip address for the vmotion port group

vswitch 1 - production network 2 nic ports, these will be in bridge mode with no ip since they'll connect to your networks, you will assign IPs to the virtual machines

vswitch 2 - iscsi network, the san should be on its own subnet with no routing to your production network, ESX servers will be connected to the SAN using the software iSCSI initiator on the ESX host.
0
 
tjieAuthor Commented:
arunraju,

1.What type of Guest OS are you planning to install ? Windows or Linux ?Answer: Windows

2.What is your iSCSI SAN Model and what is its storage capacity ? HP, Dell ?Answer: HP (The storage: should be enough)

3.Are you using VLANs or a single subnet in your network ? Answer: a single subnet; should i make a Vlan?

4.Are you using vCenter to manage your ESX Hosts ?Answer: What is vCenter? I will use the VI Client or VSphere Client

5.On which Server Model (Dell, HP or IBM) have you installed ESX 4.0 ? Is it on the HP DL360 Server which you have mentioned ? Answer: Yes, it was installed at HP DL 360

For Arunraju & Paulsolov:

1) This is just a TEST firstly (I just want to let Going with the existing condition) ...
2) Just provide the very minimum basic please ....
3) I just want to install a server (vmmachine) (maybe SQL) and a connection to the SAN .......
4) So per Paul: I need the iSCSI initiator? (Is it already in the ESX host or i have to download it?)
5) The idea: just let it going .....and later on i can remove, modify or add it ......i have to show it to management firtsly
6) Thank you

tjie
0
Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

 
Paul SolovyovskySenior IT AdvisorCommented:
1) This is just a TEST firstly (I just want to let Going with the existing condition) ...
2) Just provide the very minimum basic please ....

For test you can use the two nics and have your production network port group, service console port group, vmotion port group on one vswitch and iscsi port groupo on the second vswitch.  Attach 1 nic to each vswitch

3) I just want to install a server (vmmachine) (maybe SQL) and a connection to the SAN .......

No problem, just create a new VM and go at it

4) So per Paul: I need the iSCSI initiator? (Is it already in the ESX host or i have to download it?)

Part of ESX/ESXi

5) The idea: just let it going .....and later on i can remove, modify or add it ......i have to show it to
0
 
vmwarun - ArunCommented:
1.vCenter is used if you manage multiple ESX/ESXi hosts (not in your case though)
2.iSCSI Initiator would be the ESX 4 Host and the target would be the iSCSI SAN. You need to enable the same on the ESX 4 Host using vSphere Client (It is available under Configuration -> Security Profile -> iSCSI Client (Port 3260)
3.A single subnet would do if you are doing POC (proof of concept).
4. You can have 1 vSwitch (vSwitch0) for service console, 1 vSwitch for VMKernel Traffic and 1 vSwitch for Virtual machine traffic as paul has suggested.
0
 
tjieAuthor Commented:
1) Thank you arun and Paul
2) I will move on (for the time being) with only One Physical NIC ....
3) Please provide me any hint (if any) to move on with this only ONE physical NIC
4) I will close this discussion soon and will open others


tjie
0
 
vmwarun - ArunCommented:
If you are planning to go with 1 NIC, then there would be only 1 vSwitch (vSwitch0) which is created by default during the installation process.
Create 2 additional port groups (VMKernel for iSCSI Traffic and Virtual Machine for VM Traffic). You are done.
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now