Advanced OSPF Configuration in a Network Model

This section contains information about setting the preferences and parameters for more advanced OSPF studies and includes the following:

  • Reducing the OSPF Routing Table Size for Flow Analysis Studies
  • Configuring Advanced OSPF Parameters

Reducing the OSPF Routing Table Size for Flow Analysis Studies

If you have a rather large network model and want to study basic connectivity between loopback interfaces on given OSPF routers, use the following preference:

  • Advertise loopback interfaces only for IGP routing protocols—Specifies if IGP routing protocols will only advertise loopback interfaces during the process of routing table generation. Enabling this preference may improve analysis performance due to fewer prefixes being advertised, thereby keeping the routing tables small. By default, this preference is disabled.

Note: This preference affects Flow Analysis only.

Configuring Advanced OSPF Parameters

If you want to fully configure OSPF, or if you are using MANET in an OSPFv3 network, use the following procedure to configure each router’s OSPF Parameters.

Procedure 101: Configuring Advanced OSPF Parameters

  1. Assign addresses to connected router interfaces. You can use the Auto-Assign IP Addresses operation or you can manually assign the addresses. Chapter 14 “IP” on page 1 describes how to assign addresses for IPv4 interfaces, Chapter 17 “IPv6” on page 1 describes how to assign addresses for IPv6 interfaces.

  2. Partition the network into areas. This is a physical partitioning in the sense that an interface can belong to only one area. The distinct interfaces of the same router, may still belong to separate areas. However, interfaces belonging to the same subnetwork (that is, interfaces that are only separated by one hop, such as interfaces on the same Ethernet segment), must be within the same area.

    The definition of areas is accomplished in a distributed manner, by specifying area membership information on each router. This is most easily done using the Protocols > OSPF > Configure Areas menu operation. To use this operation, first select the links that are directly connected to the interfaces of a single OSPF area. Choose Configure Areas from the OSPF menu and specify an integer as the area ID that the interfaces belong to. Usually, these are small integers, but any integer number is acceptable. Zero, however, is reserved for the backbone of the network. This operation configures the IP Routing Protocols > OSPF Parameters > Interface Information > Area ID attribute. You could also edit this attribute manually, but this involves determining the interface connected to the link for each router interface in the area. Note that there is another OSPF attribute called Area Summarization. This attribute is provided not to define areas, but to specify route aggregation, which is discussed later.

  3. Configure routing costs. Cost is specified on a per interface basis and is used as the basis for the shortest path route calculation. Interface cost is a whole number specifying the cost of routing an outbound packet via this interface (inbound cost is taken to be the outbound cost on the other side of the link). Cost specification is done in the IP Routing Protocols > OSPF Parameters > Interface Information attribute of each router. You can manually edit this attribute for each router, or you can choose “Configure Interface Cost...” from the Protocols > OSPF menu. The second option allows you to configure the cost of all or selected interfaces in the network in a single operation. A third option is to use the default setting for configuring routing costs. This allows the model to automatically calculate the cost based on the reference bandwidth and the interface bandwidth.

    Note: If you select a single link and choose the “Asymmetric cost” checkbox in the OSPF Interface Cost Configuration dialog, you can specify different costs for each end of the link.

  4. Configure router priority. Router priority is also specified in the Interface Information attribute for each interface. The priority is used to perform designated router (DR) election. The protocol requires a single router on any broadcast network to be chosen as the DR. In general, this will be the router with the highest priority number (except if that router comes on line later than others). This step is only necessary if you have multiple routers on the same broadcast network and you wish to ensure that a particular router is the designated router (DR).

  5. Configure Interface Types. Interface types, also configured in the OSPF Interface Information table, relate to the type of technology used to transmit packets over a given interface. LAN technologies (Ethernet, FDDI, TR) are almost always set to “Broadcast”. Serial line interfaces, such as SLIP and PPP are “Point-to-Point” type interfaces. In general, these choices are already made for you by the model library and the pre-configured values can be left in place. However, circuit-oriented WAN technologies may be set to either “Broadcast,” “Non-Broadcast,” “Point to Multipoint,” or “MANET,” depending on how the routers are deployed. Therefore, if you are using Frame Relay (FR) or ATM in your OSPF network, you should understand the remainder of this step.

    Note: You must be running OSPFv3 to choose the “MANET” interface type. If you are running OSPFv2, the interface type defaults to “Point-to-Point.”

    Certain lower layers, such as Ethernet, provide an intrinsic broadcast capability to IP, allowing it to reach all other routers in the same subnet (neighbors). However, with a lower layer consisting of ATM or FR, broadcast capability consists of transmitting over virtual circuits (PVCs or SVCs) to all desired neighbors. In such a case, you may use the “Non-Broadcast” setting for the interface type only if the interface is fully meshed to all of its neighbors (that is, virtual circuits are in place between this interface and all desired neighbors). However, if this is not the case, you should use the “Point to Multipoint” setting for this interface. In either case, you must specify the neighboring interface addresses in the Neighbor List attribute.

  6. (MANET Only) Configure MANET Parameters using the compound attribute to specify peering parameters.

    Note: When running MANET in an OSPFv3 network model, disable the Access Point Functionality on all Wireless LAN interfaces in the network in the compound attribute Wireless LAN > Wireless LAN Parameters > Access Point Functionality.

  7. Configure OSPF Timers. The timer parameters are well known to OSPF practitioners. The Hello Interval attribute controls the time interval between hello packets sent from each interface. The Router Dead Interval is the threshold beyond which an interface not responding to hello packets will be considered inoperable. These two timers, Hello Interval and Router Dead Interval, must be the same across peer interfaces. Retransmission Interval is used by OSPF to reliably transmit advertisements to its neighbors. OSPF waits this many seconds for an acknowledgment. If it does not receive one, the interface retransmits the last packet transmitted. Finally, Interface Transmission Delay is used to age OSPF packets. Each interface traversed by a packet, contributes this amount of delay to an accumulator. In the face of a changing topology, with potentially inconsistent routing information during a transient period, this timing mechanism is used to choose more recent routing information, preferentially. In other words, older routing packets accumulate more transmission delay and are ignored in favor of newer packets. In practice, this parameter is rarely changed from its default value.

    Note: When you choose “MANET” as the interface type, in step 5, it is recommended that you set the Hello Interval timer to 2 seconds and the Router Dead Interval timer to 6 seconds.

  8. Configure Route Aggregation for each area. One of the primary benefits of the OSPF protocol is the control it offers with respect to limiting and aggregating routing advertisements that are sent across area boundaries in the network. To accomplish this, you must specify policies on each border router in the network. In absence of an applicable policy for a route, a border router will advertise the route individually to all of its neighbors in other areas. Routing policies are specified via the “Area Summarization” attribute of the router.

    You can view routing policies as being specified from the point of view of an area. For that area, you must specify zero, one, or more instructions to provide for either aggregation or filtering on a range of addresses. A range of addresses is specified in the standard form of a network address and a subnet mask for IPv4 interfaces or a network address and a prefix length for IPv6 interfaces. Since a single area may encompass disparate address ranges, you may need to use multiple instructions (that is, multiple lines in the table). This depends on how your addressing plan has been designed (clever addressing plans will maintain contiguous ranges in areas or in sub-areas that are to be treated uniformly) in order to simplify routing policies.

    For a given area and a range of addresses within it, you can specify an instruction to either “Advertise” or “Hide” the related routing advertisements. If you choose “Advertise”, then all routes to the given range of addresses will be advertised to the rest of the network using a single advertisement. If you choose “Hide”, then the address range of interest will remain hidden from the rest of the network, that is, no advertisement will be forwarded. Finally, if you do not specify any instructions for an address range, then all applicable advertisements will be forwarded individually.

  9. Specify External Routes. A possible choice in your routing architecture is to not run any dynamic routing protocol on certain portions of the network. This is achieved with the “IP Routing Parameters” attribute. This will obviously reduce or eliminate routing traffic in parts of your network; however, destinations within those parts may still need to be reachable by the rest of the network. In order to accomplish this, a router on the border of one or more subnets not running any routing protocol can learn about routes to destinations within those subnets via a static configuration. This static configuration is specified in the OSPF Parameter’s External Routes Information attribute. In turn, the router can then advertise routes to those destinations on other interfaces that run OSPF.

    The External Routes Information table provides routing parameters for each desired range of addresses, specified as a (network address, mask) pair. The cost parameter specifies the cost to route to the applicable addressees for use in outgoing routing advertisements. The Metric Type parameter controls whether the cost is used as an absolute number when advertised to other OSPF routers (type 2 metric), or if it should be added to the cost of reaching the intermediate router (type 1 metric).

    In practice, the External Routes Information attribute is only used to statically configure addresses that are one hop away from the router of interest. In so doing, the router becomes known as a proxy for those destinations in the rest of the network. To configure static routing for addresses beyond one hop away from the router, you should use the IP > IP Routing Parameters > Static Routing Table attribute. The route redistribution mechanism will automatically inject routes into the dynamic protocol(s) routing on other interfaces.

  10. Specify when OSPF routing tables are calculated. There are two different schemes for determining when the routing table is calculated: LSA-driven and periodic. You can specify the scheme used through the Protocols > OSPF > Configure SPF Calculation Parameters menu operation. This operation configures the SPF Calculation Parameters attribute on all or selected routers. Once calculated, the routing tables are transmitted across OSPF area boundaries. Typically, all routers use the same value for this attribute.

  11. Assign the Router ID for each router in the IP Routing Protocols > OSPF Parameters > Processes > Process Parameters attribute. This is used for identification purposes, primarily in reporting. It should be the address of one of the router’s interfaces entered in dotted quad notation. However, in most cases, you will want to use the default “Auto Assigned” value, which will take the address of one of the router’s interfaces.

  12. Configure the OSPF Sim Efficiency simulation attribute. This option lets you control whether OSPF remains active beyond a certain time in the simulation. Specifically, OSPF will no longer send hello packets after the time specified in the OSPF Stop Time simulation attribute, which is measured in seconds of simulated time. Hello packets are keep-alive packets used to determine if topology changes have occurred. If you anticipate no topological changes in your network (that is, you are not using node or link failures), then you should enable OSPF Sim Efficiency and set OSPF Stop Time to a reasonable time frame so that the distributed process of routing table calculation can converge.

End of Procedure 101

本站文档由 北京智网畅联科技有限公司 整理、翻译并提供 · Documentation compiled and provided by Beijing ZNetLink Technology Co., Ltd.

交流群 · QQ Group:OPNET/智网妙算网络仿真交流群(群号 486383494)

原文档 © 2017 Riverbed Technology · 本站为公益翻译,由 AI 辅助完成,请仔细甄别

Original documentation © 2017 Riverbed Technology. Community translation, AI-assisted. Contact: jiazequn@znetlink.com