sfouant@p1# run show route 168.10.32.0/22
inet.0: 28 destinations, 28 routes (28 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
168.10.32.1/32 *[OSPF/10] 8w4d 19:04:48, metric 1
> to 168.10.60.2 via ge-0/0/0.0
168.10.32.2/32 *[OSPF/10] 8w4d 19:04:48, metric 1
> to 168.10.60.2 via ge-0/0/0.0
168.10.32.3/32 *[OSPF/10] 8w4d 19:04:43, metric 1
to 168.10.48.10 via ge-0/0/1.0
> to 168.10.60.10 via ge-0/0/1.0
168.10.32.4/32 *[OSPF/10] 8w4d 19:04:43, metric 1
> to 168.10.48.10 via ge-0/0/1.0
to 168.10.60.10 via ge-0/0/1.0
Note: We can do this on any router within Area 1 since the Link-State Database is the same on all devices, but I prefer to perform the work on the ABR since this is where I will be performing the aggregation. Also, the ABR may have other local and/or direct routes (or perhaps routes from other protocol sources) so we want to see things from the perspective of the ABR.
sfouant@p1# run show route 168.10.32.0/21
inet.0: 28 destinations, 28 routes (28 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
168.10.32.1/32 *[OSPF/10] 8w4d 19:04:50, metric 1
> to 168.10.60.2 via ge-0/0/0.0
168.10.32.2/32 *[OSPF/10] 8w4d 19:04:50, metric 1
> to 168.10.60.2 via ge-0/0/0.0
168.10.32.3/32 *[OSPF/10] 8w4d 19:04:45, metric 1
to 168.10.48.10 via ge-0/0/1.0
> to 168.10.60.10 via ge-0/0/1.0
168.10.32.4/32 *[OSPF/10] 8w4d 19:04:45, metric 1
> to 168.10.48.10 via ge-0/0/1.0
to 168.10.60.10 via ge-0/0/1.0
Not quite. Let's keep trying:
sfouant@p1# run show route 168.10.32.0/20
inet.0: 28 destinations, 28 routes (28 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
168.10.32.1/32 *[OSPF/10] 8w4d 19:04:55, metric 1
> to 168.10.60.2 via ge-0/0/0.0
168.10.32.2/32 *[OSPF/10] 8w4d 19:04:55, metric 1
> to 168.10.60.2 via ge-0/0/0.0
168.10.32.3/32 *[OSPF/10] 8w4d 19:04:50, metric 1
to 168.10.48.10 via ge-0/0/1.0
> to 168.10.60.10 via ge-0/0/1.0
168.10.32.4/32 *[OSPF/10] 8w4d 19:04:50, metric 1
> to 168.10.48.10 via ge-0/0/1.0
to 168.10.60.10 via ge-0/0/1.0
Nope, still not there yet. Let's try again:
sfouant@p1# run show route 168.10.32.0/19
inet.0: 28 destinations, 28 routes (28 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
168.10.32.1/32 *[OSPF/10] 8w4d 19:04:58, metric 1
> to 168.10.60.2 via ge-0/0/0.0
168.10.32.2/32 *[OSPF/10] 8w4d 19:04:58, metric 1
> to 168.10.60.2 via ge-0/0/0.0
168.10.32.3/32 *[OSPF/10] 8w4d 19:04:53, metric 1
to 168.10.48.10 via ge-0/0/1.0
> to 168.10.60.10 via ge-0/0/1.0
168.10.32.4/32 *[OSPF/10] 8w4d 19:04:53, metric 1
> to 168.10.48.10 via ge-0/0/1.0
to 168.10.60.10 via ge-0/0/1.0
168.10.48.4/30 *[OSPF/10] 00:36:26, metric 2
to 168.10.48.10 via ge-0/0/1.0
> to 168.10.60.10 via ge-0/0/1.0
to 168.10.60.2 via ge-0/0/0.0
168.10.48.8/30 *[Direct/0] 8w4d 19:36:13
> via ge-0/0/1.0
168.10.48.9/32 *[Local/0] 8w4d 19:36:13
Local via ge-0/0/1.0
168.10.60.0/30 *[Direct/0] 8w4d 19:51:31
> via ge-0/0/0.0
168.10.60.1/32 *[Local/0] 8w4d 19:51:31
Local via ge-0/0/0.0
168.10.60.4/30 *[OSPF/10] 00:36:26, metric 2
to 168.10.48.10 via ge-0/0/1.0
> to 168.10.60.10 via ge-0/0/1.0
to 168.10.60.2 via ge-0/0/0.0
168.10.60.8/30 *[Direct/0] 8w4d 19:36:13
> via ge-0/0/1.0
168.10.60.9/32 *[Local/0] 8w4d 19:36:13
Local via ge-0/0/1.0
Ok, this looks more like it. Here we can see we have all the Gigabit Ethernet links connecting all devices, as well as the loopback addresses. This might be a suitable summary. Let's keep going to see what happens:
sfouant@p1# run show route 168.10.32.0/18
inet.0: 28 destinations, 28 routes (28 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
168.10.0.1/32 *[Direct/0] 8w4d 19:51:37
> via lo0.0
168.10.0.2/32 *[Direct/0] 8w4d 19:36:19
> via lo0.0
168.10.0.3/32 *[OSPF/10] 00:28:41, metric 1
> to 168.10.18.2 via fe-0/0/2.0
to 168.10.26.2 via fe-0/0/2.0
168.10.0.4/32 *[OSPF/10] 00:28:41, metric 1
> to 168.10.18.2 via fe-0/0/2.0
to 168.10.26.2 via fe-0/0/2.0
168.10.18.0/30 *[Direct/0] 8w4d 19:05:28
> via fe-0/0/2.0
168.10.18.1/32 *[Local/0] 8w4d 19:05:28
Local via fe-0/0/2.0
168.10.26.0/30 *[Direct/0] 8w4d 19:05:28
> via fe-0/0/2.0
168.10.26.1/32 *[Local/0] 8w4d 19:05:28
Local via fe-0/0/2.0
168.10.32.1/32 *[OSPF/10] 8w4d 19:05:04, metric 1
> to 168.10.60.2 via ge-0/0/0.0
168.10.32.2/32 *[OSPF/10] 8w4d 19:05:04, metric 1
> to 168.10.60.2 via ge-0/0/0.0
168.10.32.3/32 *[OSPF/10] 8w4d 19:04:59, metric 1
to 168.10.48.10 via ge-0/0/1.0
> to 168.10.60.10 via ge-0/0/1.0
168.10.32.4/32 *[OSPF/10] 8w4d 19:04:59, metric 1
> to 168.10.48.10 via ge-0/0/1.0
to 168.10.60.10 via ge-0/0/1.0
168.10.48.4/30 *[OSPF/10] 00:36:32, metric 2
to 168.10.48.10 via ge-0/0/1.0
> to 168.10.60.10 via ge-0/0/1.0
to 168.10.60.2 via ge-0/0/0.0
168.10.48.8/30 *[Direct/0] 8w4d 19:36:19
> via ge-0/0/1.0
168.10.48.9/32 *[Local/0] 8w4d 19:36:19
Local via ge-0/0/1.0
168.10.60.0/30 *[Direct/0] 8w4d 19:51:37
> via ge-0/0/0.0
168.10.60.1/32 *[Local/0] 8w4d 19:51:37
Local via ge-0/0/0.0
168.10.60.4/30 *[OSPF/10] 00:36:32, metric 2
to 168.10.48.10 via ge-0/0/1.0
> to 168.10.60.10 via ge-0/0/1.0
to 168.10.60.2 via ge-0/0/0.0
168.10.60.8/30 *[Direct/0] 8w4d 19:36:19
> via ge-0/0/1.0
168.10.60.9/32 *[Local/0] 8w4d 19:36:19
Local via ge-0/0/1.0
Clearly from this command, we can see we have now gone beyond what might be considered a suitable summary because we are now encompassing routes that exist within the backbone Area 0. So it should be clear from this simple set of commands that the 168.10.32.0/19 would be a suitable address to use for our summary.
sfouant@p2# run show route 168.10.96.0/19
inet.0: 27 destinations, 27 routes (27 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
168.10.96.1/32 *[OSPF/10] 01:00:57, metric 1
to 168.10.112.2 via fe-0/0/3.0
> to 168.10.118.2 via fe-0/0/3.0
168.10.96.2/32 *[OSPF/10] 01:00:57, metric 1
> to 168.10.112.2 via fe-0/0/3.0
to 168.10.118.2 via fe-0/0/3.0
168.10.112.0/30 *[Direct/0] 01:13:48
> via fe-0/0/3.0
168.10.112.1/32 *[Local/0] 01:13:48
Local via fe-0/0/3.0
168.10.118.0/30 *[Direct/0] 01:13:48
> via fe-0/0/3.0
168.10.118.1/32 *[Local/0] 01:13:48
Local via fe-0/0/3.0
And there you have it! As you can see it's really quite simple and if you haven't stumbled upon this already you may be saying to yourself, "Why didn't I think of that before?". I hear from many candidates that they spend considerable time the old fashioned way to determine summaries and I always ask myself why. As you can see, there is an easier way!