Below are some of the OSPF edges/pros as compared to contemporary protocols of the same age:
- No hop count limitations as in other contemporary protocols
- OSPF allows summarization with almost all possible scenarios
- Recognizes VLSMs (variable-length subnet masks)
- No Broadcasts … OSPF uses multicasts 224.0.0.5, 224.0.0.6
- OSPF converges much faster than RIP, because OSPF propagates changes immediately.
- Load balancing up to 6x equal cost paths
- OSPF is a Secure Protocol (Multiple authentication options available)
- OSPF allows for tagging of external routes injected by other AS
- OSPF is CPU/Memory intensive especially in multi-area and multi-process scenarios
- Summarization can be done only on ABR & ASBR router not on all routers
- OSPF is heirarchical, using area 0 as the top as the hierarchy
- OSPF provides fast convergence with triggered, incremental updates via LSAs
- OSPF is a classless protocol and allows for a hierarchical design with VLSM and route summarization
- OSPF requires more memory to hold the adjacency (list of OSPF neighbors), topology and routing tables
Excellent post!!
and Thanks for your answers to all questions.
OSPF is Destination based or Source based Protocol?
OSPF is a Destination based Protocol.
OSPF routes IP packets based solely on the destination IP address found in the IP packet header. IP packets are not encapsulated in any further protocol headers as they transit the AS. OSPF uses Port IP Port 89 for Transport. It uses its own transport, not TCP/UDP.
what is the diff in case of dr/bdr?
There are 2 problems for OSPF on by multiaccess networks:
i. Multiple adjacencies
ii. Extensive LSA flooding
If OSPF is heavier on Router resources then how it uses less Bandwidth?
Why is OSPF heavier as compared to other protocols?
OSPF is resource intensive Protocol. The OSPF protocol is based on link-state or SPF technology. It uses Dijkstra’s algorithm to calculate the shortest paths between nodes which is a heavy protocol & requires a lot of mathematical calculations.
OSPF doesn’t need a lot of Bandwidth because it uses only triggered updates.