language-icon Old Web
English
Sign In

Supernetwork

A supernetwork, or supernet, is an Internet Protocol (IP) network that is formed, for routing purposes, from the combination of two or more networks (or subnets) into a larger network. The new routing prefix for the combined network represents the constituent networks in a single routing table entry. The process of forming a supernet is called supernetting, prefix aggregation, route aggregation, or route summarization. A supernetwork, or supernet, is an Internet Protocol (IP) network that is formed, for routing purposes, from the combination of two or more networks (or subnets) into a larger network. The new routing prefix for the combined network represents the constituent networks in a single routing table entry. The process of forming a supernet is called supernetting, prefix aggregation, route aggregation, or route summarization. Supernetting within the Internet serves as a strategy to avoid topological fragmentation of the IP address space by using a hierarchical allocation system that delegates control of segments of address space to regional network service providers. This method facilitates regional route aggregation. The benefits of supernetting are conservation of address space and efficiencies gained in routers in terms of memory storage of route information and processing overhead when matching routes. Supernetting, however, can introduce interoperability issues and other risks. In Internet networking terminology, a supernet is a block of contiguous subnetworks addressed as a single subnet from the perspective of the larger network. Supernets are always larger than their component networks. Supernetting is the process of aggregating routes to multiple smaller networks, thus saving storage space in the routing table and simplifying routing decisions and reducing routing advertisements to neighboring gateways. Supernetting has helped address the increasing size of routing tables as the Internet has expanded. Supernetting in large, complex networks can isolate topology changes from other routers. This can improve the stability of the network by limiting the propagation of routing traffic in the event of a network link failure. For example, if a router only advertises a summary route to the next router, then it does not need advertise any changes to specific subnets within the summarized range. This can significantly reduce any unnecessary routing updates following a topology change. Hence, it increases the speed of convergence resulting in a more stable environment. Supernetting requires the use of routing protocols that support Classless Inter-Domain Routing (CIDR). Interior Gateway Routing Protocol, Exterior Gateway Protocol and version 1 of the Routing Information Protocol (RIPv1) assume classful addressing, and therefore cannot transmit the subnet mask information required for supernetting. Enhanced Interior Gateway Routing Protocol (EIGRP) is a classless routing protocol capable of support for CIDR. By default, EIGRP summarizes the routes within the routing table and forwards these summarized routes to its peers. This may have adverse impact within heterogeneous routing environments with discontiguous subnets. The family of classless routing protocols are RIPv2, Open Shortest Path First, EIGRP, IS-IS and Border Gateway Protocol. A company that operates 150 accounting services in each of 50 districts has a router in each office connected with a Frame Relay link to its corporate headquarters. Without supernetting, the routing table on any given router might have to account for 150 routers in each of the 50 districts, or 7500 different networks. However, if a hierarchical addressing system is implemented with supernetting, then each district has a centralized site as interconnection point. Each route is summarized before being advertised to other districts. Each router now only recognizes its own subnet and the other 49 summarized routes.

[ "Dynamic Source Routing", "Wireless Routing Protocol", "Link-state routing protocol", "Optimized Link State Routing Protocol", "Static routing" ]
Parent Topic
Child Topic
    No Parent Topic