nt1330 unit 1
Unit 1. Exercise 1. IP Addressing Scenario
There are many factors involved in this scenario. For example, the building may lend itself to certain network designs. You may have multiple floors or a single floor, Multiple data closets or just one. You may have virtualized servers or desktops. You will want to accommodate all these into your design. 50% may seem like too much now, but realistically, 200 or 300% might be more accurate.
A simple design you can consider is 1 floor with a single data closet serving 150 users. You need:
A core network:
Networks for your firewall, dmz, remote vpn clients, etc switch mgmt network server network voice network wireless network networks for other services you have not yet identified, like security, cameras, fire, door, video, etc
You should have multiple domain servers and dhcp servers
While you can get away with using high end switches for dhcp, a couple windows servers will do the trick and give more insight when you are troubleshooting
Most systems can get along with dhcp, so that is fine, (some older systems still need host files) but there are support benefits to statically assigned addresses. In any case, you will want reserved space in these networks for your network devices, ie. vlans, redundant or clustered systems, etc.
For you design, you could use the 10.1.0.0 address space using /21 (10.1.0.1 - 10.1.7.254)
Your netmask on the devices will be 255.255.255.0
Reserve the first and last 20 or so addresses in each dhcp scope for statically assigned addresses and network devices / gateway addresses.
10.1.0.0/24 for servers-all static
10.1.1.0/24 for pc's printers- usable for dhcp 10.1.1.21 - 10.1.1.230
10.1.2.0/24 for wireless - usable for dhcp 10.1.2.21-10.1.2.230
10.1.3.0/24 for voip - usable for dhcp 10.1.3.21 - 10.1.3.230
10.1.4.0 - 10.1.7.254 for future use
While you can cut back each network to a /25 giving 126 hosts per network, you may find yourself changing this sooner than
There are many factors involved in this scenario. For example, the building may lend itself to certain network designs. You may have multiple floors or a single floor, Multiple data closets or just one. You may have virtualized servers or desktops. You will want to accommodate all these into your design. 50% may seem like too much now, but realistically, 200 or 300% might be more accurate.
A simple design you can consider is 1 floor with a single data closet serving 150 users. You need:
A core network:
Networks for your firewall, dmz, remote vpn clients, etc switch mgmt network server network voice network wireless network networks for other services you have not yet identified, like security, cameras, fire, door, video, etc
You should have multiple domain servers and dhcp servers
While you can get away with using high end switches for dhcp, a couple windows servers will do the trick and give more insight when you are troubleshooting
Most systems can get along with dhcp, so that is fine, (some older systems still need host files) but there are support benefits to statically assigned addresses. In any case, you will want reserved space in these networks for your network devices, ie. vlans, redundant or clustered systems, etc.
For you design, you could use the 10.1.0.0 address space using /21 (10.1.0.1 - 10.1.7.254)
Your netmask on the devices will be 255.255.255.0
Reserve the first and last 20 or so addresses in each dhcp scope for statically assigned addresses and network devices / gateway addresses.
10.1.0.0/24 for servers-all static
10.1.1.0/24 for pc's printers- usable for dhcp 10.1.1.21 - 10.1.1.230
10.1.2.0/24 for wireless - usable for dhcp 10.1.2.21-10.1.2.230
10.1.3.0/24 for voip - usable for dhcp 10.1.3.21 - 10.1.3.230
10.1.4.0 - 10.1.7.254 for future use
While you can cut back each network to a /25 giving 126 hosts per network, you may find yourself changing this sooner than