Beta Draft Confidential
G-41/19/05 ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000
OSPF Name Aggregation
Using OSPF Name Aggregation
Switch-level Name Aggregation
OSPF name aggregation can also work at the switch level through the use of node
prefixes. Node prefixes let you aggregate multiple port prefixes into one OSPF
node-prefix name for remote switches.
In the sample network (Figure G-1), Switch #1 has two UNI ports. All of the
addresses at each UNI port start with 978. As described in the preceding section, you
could use name aggregation at the port level to provision two port prefixes (978555
and 978666). This solution would accommodate the routing requirements of both
ports. However, the OSPF names associated with both local ports would be shared
with, and consume memory on, all the other switches in the network.
Using switch-level name aggregation is a better solution when, for example, a network
has hundreds of port prefixes on a switch and many switches throughout the network.
OSPF name aggregation at the switch level minimizes the size of the name database
by aggregating groups of multiple port prefixes into individual OSPF node-prefix
names for remote switches, thereby reducing memory consumption in switch cards for
all switches in the network.
In the sample network (Figure G-1), you could use switch-level name aggregation to
provision a node prefix of 978 at Switch #1. This provision would aggregate all node
prefixes starting with 978 into one OSPF name at remote switches. At the local host
switch, OSPF names would still exist for the individual prefixes and the names would
consume the required memory on the local switch cards. However, this solution would
save significant memory at remote switches, which would have a single (instead of
multiple) OSPF name.
To Next Page
Loading...
Need help?
General
