You should reserve separate subnets for LANs using IP phones. IP phones are normally placed in a VLAN that is in a logical segment separate from that of the user workstations. Separating voice and data on different subnets or VLANs also aids in providing QoS for voice traffic with regard to classifying, queuing, and buffering. This design rule also facilitates troubleshooting.
Table 1-23 shows an example of allocating IP addresses for a small network for a company located within three buildings. Notice that separate VLANs are used for the VoIP devices.
Table 1-23 IP Address Allocation for VoIP Networks
Building Floor/Function | VLAN Number | IP Subnet |
First-floor data | VLAN 11 | 172.16.11.0/24 |
Second-floor data | VLAN 12 | 172.16.12.0/24 |
Third-floor data | VLAN 13 | 172.16.13.0/24 |
First-floor VoIP | VLAN 111 | 172.16.111.0/24 |
Second-floor VoIP | VLAN 112 | 172.16.112.0/24 |
Third-floor VoIP | VLAN 113 | 172.16.113.0/24 |
Overlay subnets can be used where IP subnets have already been allocated and no spare subnets are available. A different class of private address can be used. This approach solves the scalability issues with the addressing plan. Table 1-24 shows an example similar to that in Table 1-23 but using overlay subnets.
Table 1-24 Overlay IP Address Allocation for VoIP Networks
Building Floor/Function | VLAN Number | IP Subnet |
First-floor data | VLAN 11 | 172.16.11.0/24 |
Second-floor data | VLAN 12 | 172.16.12.0/24 |
Third-floor data | VLAN 13 | 172.16.13.0/24 |
First-floor VoIP | VLAN 111 | 10.16.11.0/24 |
Second-floor VoIP | VLAN 112 | 10.16.12.0/24 |
Third-floor VoIP | VLAN 113 | 10.16.13.0/24 |
VLSM Address Assignment: Example 2
Because this topic is important, here is another example of a VLSM design, this time involving network 10.0.0.0/8, which companies commonly use in their internal networks because this is private IP address space.
Global companies divide this address space into continental regions for the Americas, Europe/Middle East, Africa, and Asia/Pacific. An example is shown in Table 1-25, where the address space has been divided into four major blocks:
- 10.0.0.0 to 10.63.0.0 is reserved.
- 10.64.0.0 to 10.127.0.0 is for the Americas.
- 10.128.0.0 to 10.191.0.0 is for Europe, Middle East, and Africa.
- 10.192.0.0 to 10.254.0.0 is for Asia Pacific.
Table 1-25 Global IP Address Allocation
Region | Network |
Reserved | 10.0.0.0/10 |
Americas | 10.64.0.0/10 |
South America | 10.96.0.0/11 *part of the Americas network above |
Europe/Middle East | 10.128.0.0/10 |
Africa | 10.160.0.0/11 *part of the Europe/Middle East network above |
Asia Pacific | 10.192.0.0/10 |
From each of these regions, address blocks can be allocated to company sites. Large sites may require 4, 8, or 16 Class C equivalent (/24) subnets to assign to data, voice, wireless, and management VLANs. Table 1-26 shows an example. The large site is allocated network 10.64.16.0/20. The first four /24 subnets are assigned for data VLANs, the second four /24 subnets are assigned for voice VLANs, and the third four /24 subnets are assigned for wireless VLANs. Other subnets are used for router and switch interfaces, point-to-point links, and network management devices.
Table 1-26 IP Address Allocation in a Large Site
Function | IP Subnet |
Data VLAN 1 | 10.64.16.0/24 |
Data VLAN 2 | 10.64.17.0/24 |
Data VLAN 3 | 10.64.18.0/24 |
Data VLAN 4 | 10.64.19.0.24 |
Voice VLAN 1 | 10.64.20.0/24 |
Voice VLAN 2 | 10.64.21.0/24 |
Voice VLAN 3 | 10.64.22.0/24 |
Voice VLAN 4 | 10.64.23.0/24 |
Wireless VLAN 1 | 10.64.24.0/24 |
Wireless VLAN 2 | 10.64.25.0/24 |
Wireless VLAN 3 | 10.64.26.0/24 |
Wireless VLAN 4 | 10.64.27.0/24 |
Reserved | 10.64.28.0/24 |
Reserved | 10.64.29.0/24 |
Router/switch loopbacks | 10.64.30.0/24 |
P2P links, misc. | 10.64.31.0/24 |