IP Forwarding

1) Classless and Classful Routing :

Classless routing and classful routing relate to the logic used to match the routing table, specifically for when the default route is used. Classless routingWhen a default route exists, and no specific match is made when comparing the destination of the packet and the routing table, the default route is used. Classful routingWhen a default route exists, and the class A, B, or C network for the destination IP address does not exist at all in the routing table, the default route is used. If any part of that classful network exists in the routing table, but the packet does not match any of the existing subnets of that classful network, the router does not use the default route and thus discards the packet.

2) Optimized Edge Routing and Performance Routing :

OER was created to extend the capability of routers to more optimally route traffic than routing protocols can provide on their own. To do this, OER takes into account the following information: Packet loss Response time Path availability Traffic load distribution By adding this information into the routing decision process, OER can influence routing to avoid links with unacceptable latency, packet loss, or network problems severe enough to cause serious application performance problems, but not severe enough to trigger routing changes by the routing protocols in use. OER uses a five-phase operational model: ProfileLearn the flows of traffic that have high latency or high throughput. MeasurePassively/actively collect traffic performance metrics.

 Apply policyCreate low and high thresholds to define in-policy and out-of-policy (OOP) performance categories. ControlInfluence traffic by manipulating routing or by routing in conjunction with PBR. VerifyMeasure OOP event performance and adjust policy to bring performance in-policy OER and PfR influence traffic by collecting information and then injecting new routes into the routing table with the appropriate routing information, tags, and other attributes (for BGP routes) to steer traffic in a desired direction. The new routes are redistributed into the IGP. As conditions change, these new routes may be removed, or more may be added. PfR learns about network performance using the IP SLA and NetFlow features (one or both) in Cisco IOS. PfR has the following requirements and conditions: CEF must be enabled. IGP/BGP routing must be configured and working. PfR does not support Multiprotocol Label Switching Provider Edge - Customer (MPLS PECE) or any traffic within the MPLS network, because PfR does not recognize MPLS headers. PfR uses redistribution of static routes into the routing table, with a tag to facilitate control. 3)