IP Addressing Question
All,
We have run out of IP Addresses on our network and we need to add IP address with as little disruption as possible. I would really like to segment my network with different IP Schemes for instance:
0.0 - Workstations
1.0 - Servers
2.0 - Phones
3.0 - Printers
4.0 - Wifi Traffic
To do so would I need a router to handle all this traffic, or would it be as simple as changing my subnet mask to something that would see all these subnets? Like 255.255.248.0.
Thank you in advance for your help.
We have run out of IP Addresses on our network and we need to add IP address with as little disruption as possible. I would really like to segment my network with different IP Schemes for instance:
0.0 - Workstations
1.0 - Servers
2.0 - Phones
3.0 - Printers
4.0 - Wifi Traffic
To do so would I need a router to handle all this traffic, or would it be as simple as changing my subnet mask to something that would see all these subnets? Like 255.255.248.0.
Thank you in advance for your help.
You need to provide a little more information first.
What is your primary subnet? 192.168.x.x or 172.x.x.x or 10.x.x.x?
Do you have any managed switches?
What is your primary subnet? 192.168.x.x or 172.x.x.x or 10.x.x.x?
Do you have any managed switches?
ASKER
My primary subnet is 10.172.0.0
ASKER
And I have cisco managed switches
When you say: "segment the network", do you mean:
- assigning blocks of IP addresses for various purposes within the same subnet?
- set up separate subnets for each purpose and then route between them?
The first approach is simpler but may have traffic issues. It depends on how many devices total, whether there are smart switches (most all are these days), etc.
The second approach will confine broadcast traffic to each subnet but is it worth the routing implementation work and maintenance?
When I say the first approach is simpler, it may be a LOT simpler for you. So don't reject it out of hand. It's very easy to increase the size of a subnet. It's a lot more to segregate into multiple subnets when all is considered. So, start with a large-enough subnet and see how it goes.
If everything is already on one subnet and there are no real traffic problems then there's the answer to that question.
- assigning blocks of IP addresses for various purposes within the same subnet?
- set up separate subnets for each purpose and then route between them?
The first approach is simpler but may have traffic issues. It depends on how many devices total, whether there are smart switches (most all are these days), etc.
The second approach will confine broadcast traffic to each subnet but is it worth the routing implementation work and maintenance?
When I say the first approach is simpler, it may be a LOT simpler for you. So don't reject it out of hand. It's very easy to increase the size of a subnet. It's a lot more to segregate into multiple subnets when all is considered. So, start with a large-enough subnet and see how it goes.
If everything is already on one subnet and there are no real traffic problems then there's the answer to that question.
Ok. What is the mask? /8 or /16 or /24
If /16 you have plenty of IP's
I would put voice on unique subnet and VLAN.
Everything else can be changed as you described as long as mask is /16 (255.255.0.0)
If /16 you have plenty of IP's
I would put voice on unique subnet and VLAN.
Everything else can be changed as you described as long as mask is /16 (255.255.0.0)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank all you for all your assistance
1.0 Servers and Network equipment
2.0 Phones
etc.