Exchange of Routing Protocol-Specific Parameters
The decision-making process and the information sent within the protocols might be incompatible and not easily exchanged, leading to errors and complex configuration. Each routing protocol maintains parameters specific to that protocol—including route metrics. Part of the function of route redistribution is to manage the transformation of these parameters between routing protocols in a meaningful way. For example, redistributing into OSPF requires translating ..
Comparison of PIM-DM and PIM-SM
One of the most confusing parts of the PIM-DM and PIM-SM designs is that it appears that if sources keep sending, and receivers keep listening, there is no difference between the end results of the end-user multicast packet flow using these two options. Once PIM-SM completes its more complicated processes, the routers near the receivers have all joined the SPT to the source, and the most efficient forwarding paths are used for each (S,G) tree. Although its underlying operatio..
WAN Aggregator/Branch Router Handoff Considerations
A final consideration in campus Qos design is the campus-to-WAN (or VPN) handoff. In the case of a branch, this equates to a handoff from the branch switch to the branch router. In either case, a major speed mismatch is impending because Gigabit Ethernet/Fast Ethernet campus networks are connecting to WAN links that might be only a few megabits (if that). Granted, the WAN aggregation routers and branch routers have advanced QoS mechanisms to prioritize traffic on their link..
Although two OSPF routers can form an adjacency (that is, become neighbors) through the exchange of Hello packets, the following parameters in the Hello packets must match: ■ Hello timer: This timer defaults to 10 seconds for broadcast and point-to-point networ types. The default is 30 seconds for nonbroadcast and point-to-multipoint networ types. ■ Dead timer: This timer defaults to 40 seconds for broadcast and point-to-point networ types. The default is 120 seconds fo..
Congestion Indication Support in FRF.8.1
For FRF.8.1, Cisco supports the bidirectional mapping of FECN and EFCI bits outlined in Table 8-5. Table 8-5. Table 8-5. EFCI and FECN Mapping for FRF.8.1 Frame Relay to ATM Direction Default The EFCI field in the ATM cell header is set to 1 if the FECN field in the Frame Relay headers is set. User configurable The EFCI field in the ATM cell header is set to a constant 0. ATM ..
