Subneting calculate, ip range

July 27, 2012 at 01:31:53
Specs: Windows 7
Hello

I need help with subnet calculate.
We have a lot of vlans in our copmany, some department are out of ip's, we want to mix 3 vlans and make them 1 big vlan, but i cant find the proper subnet mask.

these are the vlans:
vlan0 10.7.0.1 255.255.252.0
vlan1 10.7.4.1 255.255.252.0
vlan2 10.7.8.1 255.255.252.0
vlan3 10.7.12.1 255.255.252.0
vlan4 10.7.16.1 255.255.252.0
(we have more vlans but i gave you the relevant)
We want to mix vlan1,2,3 together, there is possible? and what subnet do i need?
We want to do vlan from 10.7.4.1 to 10.7.15.254, it is possible?

Thank you!


See More: Subneting calculate, ip range

Report •


#1
July 27, 2012 at 03:56:59
vlan(1-3) 10.7.4.0 / 255.255.240.0

Network-Address: 10.7.4.0
Subnet-Mask: 255.255.240.0
first IP: 10.7.4.1
last IP: 10.7.15.254
Broadcast: 10.7.15.255


Report •

#2
July 27, 2012 at 04:14:51
Thanks, but this also takes vlan0(10.7.4.0/255.255.252.0)
I don't want to use vlan0, just 3 other vlan's.

In your exapmle you strating from 10.7.4.0 until 10.7.15.
I want from 10.7.4.0 until 10.7.15.254


Report •

#3
July 27, 2012 at 04:17:36
You wrote:
We want to do vlan from 10.7.4.1 to 10.7.15.254, it is possible?

And that's exactly, what it does.


Report •

Related Solutions

#4
July 27, 2012 at 04:25:54
but when i put the ip and the subnet in this ip calculate website: http://jodies.de/ipcalc?host=10.7.4...

I got these result:
Address: 10.7.4.1 00001010.00000111.0000 0100.00000001
Netmask: 255.255.240.0 = 20 11111111.11111111.1111 0000.00000000
Wildcard: 0.0.15.255 00000000.00000000.0000 1111.11111111
=>
Network: 10.7.0.0/20 00001010.00000111.0000 0000.00000000 (Class A)
Broadcast: 10.7.15.255 00001010.00000111.0000 1111.11111111
HostMin: 10.7.0.1 00001010.00000111.0000 0000.00000001
HostMax: 10.7.15.254 00001010.00000111.0000 1111.11111110
Hosts/Net: 4094 (Private Internet)


And like you see, vlan 10.7.0 it inisde the sbunet.
10.7.4.1/255.255.240.0 give us range from 10.7.0..0 to 10.7.15.254, whats wrong here?

thanke you


Report •

#5
July 27, 2012 at 04:40:05
Ah, sorry, my fault.
Right, network address is 10.7.0.0 and therefore, you're right and in addition, you can't mix these 3 subnets as you wanted to do.

Report •

#6
July 27, 2012 at 05:07:45
I see..we are in serious problems with the ip's, we have vlan for each department and now some department geting bigger then we thought and now we must find solution..
the easy solution is to take other subnet make new vlan, but we have sometthing like 1500 devices in currnet vlan and we can tranfer them to new vlan, we need to fine solution with the currnet vlan.

Doe's anybody known about option to take few separated subnets and make them 1 logical VLAN?
For example, taking 10.7.4.0/255.255.252.0 amd 10.7.40.0/255.255.252.0 and make them 1 VLAN?


thanks you very much.


Report •

#7
July 27, 2012 at 07:22:52
I think you're looking at this the wrong way.

Since you need more IP's, why not just create some new subnets and associated VLAN's and then start using them for more client connections? You don't need bigger subnets in each VLAN when you can create new ones and allow them to communicate with each other via routing.

I've never heard of anybody using VLAN0

VLAN1 should always, and only be used for your management VLAN. Which is to say, all network appliances should be on their own separate subnet/VLAN from all the rest of your equipment.

We use many VLAN's here where I work. Here is an idea of our setup:

VLAN1 = management VLAN (as per above, ONLY network appliances like switches, routers, firewalls, etc are allowed on this VLAN)

VLAN 2 = printer VLAN

VLAN 3 through 12 = clients only

VLAN 13 through 20 = servers only

VLAN 200 throug 250 = DMZ (outward facing)

Each VLAN is it's own xxx.xxx.0.0/24 subnet.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#8
July 27, 2012 at 07:53:59
Hello

You are right, new subnet is the best solution, but we have problem with adding Other subnet to the department that need more ip's, the problen is because the department is QA team, and they have a lot of servers and chassis(with blad servers), They switching, replacing, mixing and changing location of servers and switches all the time, they need To be able to take for example, HP blad from some chassis and connect it to other Chassis and it should work without problem, therefore we need to put them all in 1 Big vlan, without changing the vlans in the switches all the time.
Did you understand me or i should explain my self better?
Thanks!


Report •

#9
July 27, 2012 at 08:16:53
Ok I hate to say this but, why is a Q&A team allowed in your datacenter? Why are they allowed to touch hardware? Why are they allowed to move it?

Servers should be placed, and set on a network and left alone. If a server needs a subnet change (happens here regularly) then I make the change. Usually by changing the VLAN assignment of the port the server plugs into on the switch stack. They (web department, Q&A, database, finance, etc) aren't allowed to touch the servers. If they tried to physically move one, I'd remove it from the datacenter and they could shove it where the sun doesn't shine and I'd win the argument because THEY HAVE NO BUSINESS BEING IN THE DATACENTER MUCH LESS TOUCHING HARDWARE.

We use remote access KVM switches in our server room that allow console type access from a remote PC. You can even remotely reboot a server and go into it's BIOS if you have to..........from your desk. Other than initial operating system install, those guys are not allowed to touch hardware and aren't allowed in the datacenter unescorted at any time.........period, end of story.

Instead of moving blades around, these guys you work with should discover Virtual servers and try them. It's a lot easier to move a virtual server to another physical box than it is to move a blade.

Well, all I can say is, you have my sincerest sympathy and good luck.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#10
July 27, 2012 at 09:13:59
You just need to renumber your ip plan.

vlan1 10.7.0.0 - 10.7.7.255 subnet mask 255.255.248.0 results in 2046 ips

vlan 2 10.7.8.0 - 10.7.15.255 subnet mask 255.255.248.0 results in 2046 ips

vlan 3 10.7.16.0 - 10.7.23.255 subnet mask 255.255.248.0 results in 2046 ips

vlan 4 10.7.24.0 - 10.7.31.255 subnet mask 255.255.248.0 results in 2046 ips

etc.. you get the idea.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#11
July 28, 2012 at 11:52:01
Curt R -- this is not our Datacenter, this is QA lab :)
We are company of network cards and switches so QA team allways working with Servers, you know, installing cards, geting new servers for drivers and performance checking and etc..

Report •

#12
July 30, 2012 at 08:49:28
You understand that your issue is your ip plan?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Ask Question