18.04.2014 Views

Networking Lab Class #6 VLSM & Route Summarization - EdLab

Networking Lab Class #6 VLSM & Route Summarization - EdLab

Networking Lab Class #6 VLSM & Route Summarization - EdLab

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Networking</strong> <strong>Lab</strong><br />

<strong>Class</strong> <strong>#6</strong><br />

<strong>VLSM</strong> & <strong>Route</strong> <strong>Summarization</strong><br />

Parviz Kermani<br />

Spring 2012<br />

UMasss Amherst


Acknowledgement<br />

• Wendel Odom: CCNA ICND2 : Official Exam<br />

Certification Guide (Second Edition)-<br />

Ciscopress.com<br />

2


This <strong>Class</strong><br />

• <strong>VLSM</strong><br />

• <strong>Route</strong> <strong>Summarization</strong><br />

3


<strong>VLSM</strong> (Variable Length Subnet Mask)<br />

• Using more than one mask in a single classful<br />

network<br />

• Benefits:<br />

Reduce number of wasted IP addresses<br />

Conserve the address space<br />

Mask: 255.255.255.0<br />

4


<strong>VLSM</strong><br />

• Note: using more than one mask does not<br />

constitute <strong>VLSM</strong> by itself<br />

But using more than one mask in a single classful<br />

network does!<br />

5


Support for <strong>VLSM</strong><br />

• To be able to use <strong>VLSM</strong>, an IP routing protocol<br />

should advertise subnet number as well as<br />

subnet mask<br />

• <strong>Class</strong>less routing protocols:<br />

Advertise mask information for each subnet<br />

Support <strong>VLSM</strong> (Variable Length Subnet Mask)<br />

<strong>Route</strong> summarization<br />

• An inherent property of a routing protocol<br />

Not configurable<br />

6


Support for <strong>VLSM</strong><br />

7


Without <strong>VLSM</strong> Support (RIP V1)<br />

Albuquerque#show ip route<br />

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP<br />

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area<br />

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP<br />

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default<br />

U - per-user static route<br />

Gateway of last resort is not set<br />

172.16.0.0/24 is subnetted, 3 subnets<br />

C 172.16.2.0 is directly connected, Serial0/0<br />

C 172.16.3.0 is directly connected, Serial0/1<br />

C 172.16.1.0 is directly connected, FastEthernet0/0<br />

R 10.0.0.0 [120/1] via 172.16.3.2, 00:03:21, Serial0/1<br />

(Bosom NetSim)<br />

8


With <strong>VLSM</strong> Support (RIP V2)<br />

Albuquerque(config-router)#no auto-summary<br />

Albuquerque#show ip rout<br />

….<br />

Gateway of last resort is not set<br />

C<br />

C<br />

C<br />

R<br />

R<br />

R<br />

R<br />

R<br />

R<br />

172.16.0.0/24 is subnetted, 3 subnets<br />

172.16.2.0 is directly connected, Serial0/0<br />

172.16.3.0 is directly connected, Serial0/1<br />

172.16.1.0 is directly connected, FastEthernet0/0<br />

10.0.0.0/24 is subnetted, 6 subnets<br />

10.2.1.0 [120/1] via 172.16.2.2, 00:06:42, Serial0/0<br />

10.2.2.0 [120/1] via 172.16.2.2, 00:05:15, Serial0/0<br />

10.2.3.0 [120/1] via 172.16.2.2, 00:07:19, Serial0/0<br />

10.3.4.0 [120/1] via 172.16.3.2, 00:08:31, Serial0/1<br />

10.3.5.0 [120/1] via 172.16.3.2, 00:02:44, Serial0/1<br />

10.3.6.0 [120/1] via 172.16.3.2, 00:04:17, Serial0/1<br />

9


Overlapping <strong>VLSM</strong> Subnets<br />

• Subnet should not have overlapping addresses<br />

Easy to detect in a single mask network<br />

Very subtle and difficult to detect with <strong>VLSM</strong><br />

• With overlapping addresses subnets<br />

<strong>Route</strong>rs’ behavior unpredictable<br />

Some host reachable only from particular parts of<br />

the internet<br />

WRONG DESIGN<br />

10


Dealing with <strong>VLSM</strong> Subnets<br />

• Two types of problems engineers faced with<br />

• Analyze:<br />

Analyze a design to detect overlaps<br />

• Design<br />

Choose/add new <strong>VLSM</strong> subnet avoiding overlap<br />

• Analyze<br />

Calculate range of addresses for each subnet<br />

Check for overlap<br />

11


Analyzing an existing design<br />

Overlap!<br />

To correct: change 172.16.4.0/23 172.16.4.0/24<br />

12


Design: Addressing Scheme With Single Mask<br />

• Determine number of subnet & host bits in<br />

the largest subnets to meet the requirements<br />

• Choose a subnet mask<br />

• For the mask, Identify all subnets of the<br />

network<br />

• Choose pick the actual sunet.<br />

13


Design: Addressing Scheme With Single Mask<br />

Example:<br />

• Requirements<br />

<strong>Class</strong> B network 172.16.0.0<br />

At least 10 subnets<br />

Largest subnet 200 hosts<br />

Choose a design with the largest number of subnets<br />

Choose the 3 rd subnet<br />

• Design<br />

At least 4 subnet bit; At least 8 host bits<br />

Mask: 255.255.255.0; 256 subnet, 254 hosts<br />

Choose 172.16.2.0/24 net<br />

14


Designing a <strong>VLSM</strong> Subnetting Scheme<br />

• Analyze the requirement to determine design<br />

goals.<br />

• Design goals:<br />

Use <strong>Class</strong> B network 172.16.0.0<br />

Three subnets with mask/24 (255.255.255.0)<br />

Three subnets with mask /26 (255.255.255.192)<br />

Four subnets with mask /30 (255.255.255.253)<br />

• Point-to-point links<br />

• Compare it with a classful and/or no <strong>VLSM</strong> design<br />

goal<br />

15


Designing a <strong>VLSM</strong> Subnetting Scheme<br />

Step 1: Design goals<br />

Step 2: Use the shortest prefix (largest # of hosts) to<br />

identify subnets of the classful network<br />

<br />

Apply to all identified networks<br />

Step 3: Identify the next numeric subnet number<br />

using the same mask<br />

Step 4: Identify the next-longest prefix<br />

<br />

Complete the number with that size<br />

Step 5: Repeat step 3 & 4 until complete<br />

16


Designing a <strong>VLSM</strong> Subnetting- Example<br />

• Step 2: The shortest prefix is /24 (longest host)<br />

Use the first 3 subnets of 172.16.0.0<br />

• Three subnets with mask/24<br />

172.16.0.0/24: Range 182.16.0.1-172.16.0.254<br />

172.16.1.0/24: Range 182.16.1.1-172.16.1.254<br />

172.16.2.0/24: Range 182.16.2.1-172.16.2.254<br />

• Step 3: the next numeric subnet (same mask)<br />

172.16.3.0/24<br />

• Three subnets with mask /26<br />

17


Designing a <strong>VLSM</strong> Subnetting- Example<br />

• Step 4: start with the unallocated subnet number of<br />

step 3<br />

• Use the nest longer prefix (/26, mask<br />

255.255.255.192)<br />

The first subnet is the one found in step 3<br />

172.16.3.0/26: range 172.16.3.1-172.16.3.62<br />

172.16.3.62/26: range 172.16.3.65-172.16.3.126<br />

172.16.3.128/26: range 172.16.3.129-172.16.3.190<br />

18


Designing a <strong>VLSM</strong> Subnetting- Example<br />

• Step 4<br />

19


Designing a <strong>VLSM</strong> Subnetting- Example<br />

• Step 5: Repeat Steps 3 & 4 until done<br />

Step 3: The next subnet, using /26, is 172.16.3.192/26<br />

Step 4: The next longest prefix is /30 (255.255.255.252)<br />

• Resulting scheme:<br />

172.16.3.192/30: Range 172.16.3.193-172.16.3.194<br />

172.16.3.196/30: Range 172.16.3.197-172.16.3.198<br />

172.16.3.200/30: Range 172.16.3.201-172.16.3.202<br />

172.16.3.204/30: Range 172.16.3.205-172.16.3.206<br />

20


<strong>VLSM</strong> Design II<br />

• Adding a new subnet to an existing design<br />

Refer to Wendell Odom’s book<br />

21


<strong>VLSM</strong> Configuration<br />

• An inherent feature of routing protocol (IP)<br />

No configuration command on routers<br />

A side effect of ip address command<br />

• <strong>Route</strong>rs configure <strong>VLSM</strong> by virtue of at least 2<br />

router interfaces<br />

On the same router or among all routers<br />

IP addresses in the same classful network but<br />

different mask<br />

• R3,Fa0/0 (255.255.255.0) &<br />

S/0/01 (255.255.255.252)<br />

172.16.4.1/24<br />

22


<strong>VLSM</strong> Configuration<br />

172.16.4.1/24<br />

R3#configure terminal<br />

R3(config)#interface Fa0/0<br />

R3(config)#ip address 172.16.5.1 255.255.255.0<br />

R3(config)#interface S0/0/1<br />

R3(config)#ip address 172.16.9.6 255.255.255.252<br />

23


<strong>Route</strong> <strong>Summarization</strong><br />

• <strong>Route</strong>rs have many routes in their tables<br />

Some Internet routers have more than 100,000!<br />

• Routing tables become too large in large nets<br />

Consume more memory<br />

Take more time to route packets<br />

Large table more time needed to troubleshoot!<br />

• <strong>Route</strong> summarization reduces size of routing<br />

tables while maintaining all routes<br />

Reduced convergence time<br />

No need to announce changes to the status of<br />

individual subnets<br />

24


<strong>Route</strong> <strong>Summarization</strong> Concepts<br />

• Number of more-specific routes to be<br />

replaced with a single route<br />

Includes all IP addresses covered by subnets in the<br />

original routes<br />

• Routing protocol advertises just the summary<br />

route, as opposed to the original route<br />

Must be configured by the network engineer<br />

• Concept similar to static route<br />

Same basic information<br />

25


<strong>Route</strong> <strong>Summarization</strong> Concepts<br />

• Works better if network is designed with<br />

summarization in mind<br />

• Example of a good design<br />

26


Routing Table Without <strong>Summarization</strong><br />

27


Routing Table With <strong>Summarization</strong><br />

28


Effect of (manual) <strong>Summarization</strong><br />

Syntax is protocol<br />

dependent<br />

Discards<br />

unwanted packets<br />

29


Effect of (manual) <strong>Summarization</strong><br />

Syntax is protocol<br />

dependent<br />

Discards<br />

unwanted packets<br />

30


(Manual) <strong>Route</strong> <strong>Summarization</strong> Strategies<br />

• Best summarization<br />

Should include all desired subnets with as few<br />

other addresses, if possible!<br />

• Example (Yosemite):<br />

Subnets 10.2.1.0, 10.2.2.0, 10.2.3.0, 10.2.4.0 (/24)<br />

summarized into 12.2.0.0/16<br />

Summary includes a lot of IP addresses no in the<br />

four subnets<br />

Correct, but not good!<br />

31


(Manual) <strong>Route</strong> <strong>Summarization</strong> Strategies<br />

Step 1: List all to-be-summarized subnets in binary<br />

Step 2: Find the left N common bits (in-common<br />

part)<br />

Step 3: Summary subnet number: in-common part<br />

followed by all binary “0”<br />

Convert back to decimal<br />

Step 4: Summary subnet mask: N binary “1”s<br />

followed by 32-N binary “0”s<br />

Convert back to decimal<br />

Step 5: Check the result by finding the range!<br />

32


Example Best Summary on Seville<br />

Subnets: 10.3.4.0, 10.3.5.0, 10.3.6.0, 10.3.7.0<br />

Step 1: List in binary<br />

10.3.4.0 : 0000 1010 0000 0011 0000 0100 0000 0000<br />

10.3.5.0 : 0000 1010 0000 0011 0000 0101 0000 0000<br />

10.3.6.0 : 0000 1010 0000 0011 0000 0110 0000 0000<br />

10.3.7.0 : 0000 1010 0000 0011 0000 0111 0000 0000<br />

Step 2: Find in-common bits, and N<br />

in-common: 0000 1010 0000 0011 0000 01, N=22<br />

Step 3: (summary) Subnet Number:<br />

0000 1010 0000 0011 0000 0100 0000 0000<br />

10 . 3 . 4 . 0<br />

Step 4: (summary) Subnet Mask:<br />

1111 1111 1111 1111 1111 1100 0000 0000<br />

255 . 255 . 252 . 0<br />

Step 5: Range<br />

10.3.4.0/22 (255.255.252.0): 10.3.4.1 – 10.3.7.254 (Bcast 10.3.7.255) Perfect!<br />

33


Example Best Summary on Yosemite<br />

Subnets: 10.2.1.0, 10.2.2.0, 10.2.3.0, 10.2.4.0<br />

Step 1: List in binary<br />

10.2.1.0 : 0000 1010 0000 0010 0000 0001 0000 0000<br />

10.2.2.0 : 0000 1010 0000 0010 0000 0010 0000 0000<br />

10.2.3.0 : 0000 1010 0000 0010 0000 0011 0000 0000<br />

10.2.4.0 : 0000 1010 0000 0010 0000 0100 0000 0000<br />

Step 2: Find in-common bits, and N<br />

in-common: 0000 1010 0000 0010 0000 0, N=21<br />

Step 3: (summary) Subnet Number:<br />

0000 1010 0000 0010 0000 0000 0000 0000<br />

10 . 2 . 0 . 0<br />

Step 4: (summary) Subnet Mask:<br />

1111 1111 1111 1111 1111 1000 0000 0000<br />

255 . 255 . 248 . 0<br />

Step 5: Range<br />

10.2.0.0/21 (255.255.248.0): 10.2.0.1 – 10.2.7.254 The best, but not so perfect!<br />

Summary route summarizes a larger address set<br />

34


Autosummarization<br />

• No advertisement of mask in classful routing<br />

protocols<br />

Needed mask information in address class (A, B, C)<br />

Throughout the inter-network<br />

Static-Length subnet mask<br />

• If R1 & R2 have connected network to the same<br />

single <strong>Class</strong> A (or B, or C)<br />

R2 received update from R1<br />

R2 assumes routes described in R1’s update use the<br />

same mask as R2 uses<br />

35


Autosummarization<br />

When advertized on an interface whose IP address is<br />

not in network X, routes related to subnets in<br />

network X are summarized and advertized as one<br />

route. That route is for the entire class A, B, or C<br />

network X.<br />

36


Autosummarization Example<br />

<strong>Class</strong>ful RIP-1<br />

protocol in effect<br />

Note: Albuquerque do<br />

not have any interface<br />

in 10.0.0.0, so it<br />

assumes the mask used<br />

with 10.0.0.0 (<strong>Class</strong> A) is<br />

255.0.0.0.0<br />

37


Discontiguous <strong>Class</strong>ful Networks<br />

• Autosummarization works as long as summarized<br />

networks are contiguous<br />

• Contiguous Newark<br />

A classful network in which packets sent between every<br />

pair of subnets can pass only through subnets of that same<br />

classful network. without having to pass through subnets<br />

of any other classful network.<br />

• Discontiguous Network<br />

A classful network in which packets sent between at least<br />

one pair of subnets pass through subnets of a different<br />

classful network<br />

38


Discontiguous <strong>Class</strong>ful Networks<br />

Autosummarization prevents an<br />

internetwork with a discontiguous<br />

network from working properly<br />

39


Discontiguous <strong>Class</strong>ful Networks<br />

Solution:<br />

Disable Autosummarization<br />

Autosummarization disabled<br />

on Yosemite and Seville<br />

40


Autosummarization Support<br />

• <strong>Class</strong>ful routing protocols must use<br />

autosummarization.<br />

• Some classless routing protocols support<br />

autosummarization<br />

Default configuration<br />

Can be disabled<br />

• OSPF (classless) DOES NOT support<br />

autosummarization<br />

41


Autosummarization Support<br />

42


Support for <strong>VLSM</strong><br />

43

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!