![\"VLSM\"](\"\/wp-content\/themes\/learncisco\/assets\/images\/ccna\/16-vlsm.jpg\" "\\"VLSM\\"")
<\/p>\nVLSM occurs when more than one mask is used in a single Class A, B, or C network. Although route summarization causes more than one mask to be used, requiring support for VLSM, you can also simply design a network to use multiple subnet masks. By using VLSM, you can reduce the number of wasted IP addresses in each subnet, allow for more subnets, and avoid having to obtain another registered IP network number from the NIC.<\/p>\n
The following schematic depicts the same familiar network with two different subnet masks (255.255.0.0 and 255.255.255.0) used in network 10.0.0.0.<\/p>\n
<\/p>\n
This figure shows a typical choice of using a \/30 prefix (mask 255.255.255.252) on point-topoint serial links, with some other mask (255.255.255.0 in this example) on the LAN subnets. The only real requirements for VLSM are that the subnets do not overlap and that the routing protocol supports VLSM. Subnets overlap when the range of IP addresses in one subnet includes some addresses in the range of valid addresses in another subnet. When using a single mask in a single Class A, B, or C network, you can usually avoid overlapping subnets easily. However, with VLSM, you can more easily overlook cases in which you assign subnets that overlap.<\/span><\/p>\n To create VLSMs quickly and efficiently, you need to understand how block sizes and charts work together to create the VLSM masks. The following table shows you the block sizes used when creating VLSMs with Class C networks. For example, if you need 25 hosts, then you’ll need a block size of 32. If you need 11 hosts, you’ll use a block size of 16. Need 43 hosts? Then you’ll need a block of 64. You cannot just make up block sizes – they’ve got to be the block sizes shown in the table. So memorize the block sizes in this table – it’s easy. They’re the same numbers we used with subnetting!<\/p>\n