ESXi server

[Cougar014]

Ah, ok! Thanks!

I will try to take a look into it and change them.

But what in dont get:
You have your vm network and your storage network both on the /24 subnet...

Shouldnt you have storage network on the /16 subnet?
I understood that a different subnet made sure that they couldn't reach eachother, and therefore are "seperate"

 

[Spearfoot]

Ah, ok! Thanks!

I will try to take a look into it and change them.

But what in dont get:
You have your vm network and your storage network both on the /24 subnet...

Shouldnt you have storage network on the /16 subnet?
I understood that a different subnet made sure that they couldn't reach eachother, and therefore are "seperate"

The /24 notation doesn't denote a network, as you seem to think it does, and it doesn't separate networks. It's just a shorthand way of specifying a network's subnet mask: /24 = 255.255.255.0

To define a network requires an IP address AND a subnet mask. The IP address specifies the base, so to speak, and the subnet mask specifies the allowable range of host IP address in the network. A network at IP address 192.168.1.0 with a /24 mask has 254 possible host IP addresses: 192.168.1.1 through 192.168.1.254

My LAN and Storage networks are on completely separate networks; they just happen to both be /24 networks, i.e., have the same number of possible host IP addresses. Those two reference links I posted earlier are great tools, and very enlightening if you play with 'em a little.

I'm trying to get you to set up the two networks as specified in Ben's original article; it's a networking scheme that works well for this particular application. Why veer from the recipe? It hasn't gained you anything.

 

[Cougar014]

I had no idea that it worked like this.
I thought that a subnet was like a different channel (like in Radio communications).
But i guess i was way off.

Thanks for pointing me in the right direction. I will take a look at the tools you mentioned. And will try to change them accordingly.:D

Many Thanks!

 

[Spearfoot]

Many Thanks!

You are very welcome!

 

[Cougar014]

Ah, ha! Your networking is malformed.

Class 'C' networks are of the form 192.168.x.x and may have subnet masks of /24, /25, /26, /27, /28, /29, or /30 - note that /24 just means you're using a subnet mask of 255.255.255.0

Your vSwitch0 VMkernel is configured at IP address 192.168.2.50 on a 192.168.2.0/24 network, which allows a host address range of 192.168.2.1 - 192.168.2.255 - so far, so good.

Your vSwitch1 VMkernel is configured at IP address 192.168.2.52 on a 192.168.0.0/16 network, not a valid class 'C' network, but which nonetheless allows a host range of 192.168.0.1 - 192.168.255.254 - a whopping huge number of hosts, and 'way more than you need for the storage network.

Do you see how they overlap? This is double-plus ungood. :)

You want the virtual machine and storage networks to be separate. I suggest designing the storage network as a class 'A' network, as Ben uses in his article. I use 10.0.59.0/24, which lets me use IP addresses between 10.0.59.1-10.0.59.254 on the storage network.

Here are some handy IP subnet calculators that I use all the time, and will make you into a network engineer, lickety-split! :D

http://www.subnet-calculator.com/
http://www.tuxgraphics.org/toolbox/network_address_calculator_add.html

Good luck!

I have got to thank you again.
It's fixed.

After changing all the connections on vswitch1 to a class A IP i got it working, without a physical nic attached to vswitch1!!!

 

[cezarq]

I want to use the follow hardware:
CPU: Intel Xeon 1230v5
Motherboard: Supermicro X11-SSL
RAM: 32GB ECC mem (16gb for each VM)
Drives: 2x WD Red for Freenas, 1 small SSD (~250gb) for other VM
HBA: IBM 25R8071 - LSI Logic SAS3444E

Olá Cougar014! Did you install VMWare and runned the Freenas with this HBA? If yes, did you have any problem?