Solved

vlan and vswitch

Posted on 2015-02-06
6
132 Views
Last Modified: 2015-02-12
This is morein to design question than troubleshooting. Hope someone give some idea.
We have Esxi environments with class c ip scheme.
We are now running out of IP for servers.
Either we have to come up with another class c IP scheme and create multiple port group in single vswitch or change the ip address to class B.

What is the best option you would recomend to accommodate more servers?
0
Comment
Question by:sara2000
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 120
ID: 40594198
Running out of IP Addresses for VMware ESXi servers, or virtual machines?

Create a class B.
0
 
LVL 12

Expert Comment

by:Bryant Schaper
ID: 40594471
Before you do that you may also want to consider what is on the C and if you are better server with multiple C subnets to create barriers, this will require intervlan routing however so that network 192.168.0.x can talk to machines on 192.168.1.x
0
 
LVL 6

Expert Comment

by:rgorman
ID: 40594490
If it is just one or a few subnets you need to adjust you can supernet the class C addresses to combine multiple class C ranges into a single logical subnet.  You would need adjacent class C subnets not in use to make it work and you would likely need to know a bit about subnetting your addresses.

For example, if you were using 192.168.2.0/24 and you needed twice as many addresses you could do 192.168.2.0/23 which would consume the adjacent 192.168.3.0/24 subnet and make one range of 192.168.2.0-192.168.3.255.  You would need to possibly adjust some routing on your network but it should be fairly simple, as long as you have that adjacent IP range, and it falls within the same range when you adjust the mask (for example, my previous example of a /23 mask wouldn't work for 192.168.1.0 and 192.168.2.0 to combine them).  If you don't understand that concept you might need to read up on subnetting.
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 

Author Comment

by:sara2000
ID: 40601292
i am running out of vms ip address . Right now my vms ip are 192.168.1.*/24 and my iscsi storage ips are 192.168.2.*.

suppernetting 192.168.1.*/23 is not going to help since the adjacent 192.168.2.*/24 is being used by iscsi.
my network admin suggested me to create another port group in the existing vswitch (192.168.1.*/24) .
and name this as lan2 and give ip address for the server in the network 192.168.3.*/24).
Creating a port group is not an issue for me, but what else i have to do to make sure that servers will talk, is that right approach?
i am willing to change the ip from class c to class b, this can be lot of problem . down time and changing nat ip etc.
Bryant:
You mentioned about inter vlan , is it something in the vmware or the network guy will do that?
0
 
LVL 120

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 200 total points
ID: 40601345
You mentioned about inter vlan , is it something in the vmware or the network guy will do that?

both, you need to configure the physical switches, and also the virtual switches, to use VLAN Tags.
0
 
LVL 6

Accepted Solution

by:
rgorman earned 300 total points
ID: 40601498
You can combine 192.168.0.0 and 192.168.1.0 into one logical subnet with a mask of 255.255.254.0 assuming you aren't already using 192.168.0.0 for something else.

Your port groups will just reference a VLAN ID and that just needs to match the VLAN ID on our switches.  You shouldn't need to change any of that.  You just need to adjust the addressing on that subnet.  All the hosts would need to be updated with the new subnet mask and the router interface on that subnet would need to get the new mask as well.  If you have a DHCP scope for that subnet you will also need to recreate it since I don't think you can adjust the mask on an existing scope.  

The only other option would be to leave what you have alone, then create a new port group and VLAN ID on your network switches and use the 192.168.0.0/24 address range and do the intervlan routing just like you do now with the subnets you have.
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Will try to explain how to use the VMware feature TAGs in the VMs and create Veeam Backup Jobs using TAGs. Since this article is too long, I will create second article for the Veeam tasks.
Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…
Advanced tutorial on how to run the esxtop command to capture a batch file in csv format in order to export the file and use it for performance analysis. He demonstrates how to download the file using a vSphere web client (or vSphere client) and exp…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question