Showing posts with label OSPF. Show all posts
Showing posts with label OSPF. Show all posts

Thursday 3 November 2022

OSPF vs ISIS- Which Routing Protocol for your needs?

OSPF and ISIS are two popular link-state routing protocols used in large-scale networks. Both protocols have similarities and differences in terms of their design, features, and operation.

OSPF (Open Shortest Path First) is a well-established protocol that has been in use for over 30 years. It operates at the Internet layer (Layer 3) and uses a hierarchical design that partitions the network into areas. Each area has its own topology database, which reduces the size of the network's routing table and enhances scalability. OSPF also supports multiple paths to a destination, allowing for load balancing and redundancy.

ISIS (Intermediate System to Intermediate System) is a protocol that operates at the Network layer (Layer 2) and is used in large-scale Service Provider networks. It also uses a hierarchical design similar to OSPF, but instead of areas, it uses levels. Each level has its own link-state database, which reduces the size of the network's routing table and improves scalability. ISIS is also known for its fast convergence and support for large networks with high-speed links.

One significant difference between OSPF and ISIS is their underlying protocol. OSPF uses IP packets to exchange routing information, while ISIS uses a protocol called CLNS (Connectionless Network Service). This difference can impact the protocol's behavior and performance, depending on the network's architecture and requirements.

Another difference is the way they handle metric calculations. OSPF uses a metric called cost, which is based on the link's bandwidth. In contrast, ISIS uses a metric called metric value, which is based on the link's speed and delay. This difference can affect how the protocol selects the best path to a destination and can impact network performance and behavior.

Additionally, OSPF and ISIS have different default behavior for load balancing. OSPF supports equal-cost multipath (ECMP) by default, which allows for multiple paths to a destination with the same cost. In contrast, ISIS does not support ECMP by default, and network operators must configure it manually. This difference can impact how network operators design their network for load balancing and redundancy.

Furthermore, OSPF and ISIS have different mechanisms for network convergence. OSPF uses a process called Dijkstra's algorithm to calculate the shortest path to a destination, while ISIS uses a technique called SPF (Shortest Path First) calculation. Both mechanisms ensure network convergence and path selection, but their implementation and performance can vary based on network topology and traffic patterns.

In terms of security, both OSPF and ISIS support authentication to prevent unauthorized access and attacks. OSPF supports several types of authentication, including plaintext, MD5, and IPsec, while ISIS supports only plaintext authentication. This difference can impact network security and how network operators secure their network.

Finally, OSPF and ISIS have different deployment and support options. OSPF is widely supported by many vendors and is commonly used in enterprise networks, while ISIS is primarily used in Service Provider networks and is supported by fewer vendors. This difference can impact how network operators choose their routing protocol based on their network's architecture and requirements.

In conclusion, OSPF and ISIS are both link-state routing protocols that offer similar features and benefits but have significant differences in their design, behavior, and operation. Network operators must carefully evaluate their network's requirements and architecture to choose the best protocol for their needs.

Wednesday 12 June 2019

OSPF Series 11: Everything on Redistribution: Part 2- Redistribution into OSPF, Pitfall of Redistribution (Administrative Distance, Route Feedback)

Everything on Redistribution: Part 2- Redistribution into OSPF, Pitfall of Redistribution (Administrative Distance, Route Feedback)

 

Redistributing into OSPF

OSPF is a standardized Link-State routing protocol that uses cost (based on bandwidth) as its link-state metric. An OSPF router performing redistribution automatically becomes an ASBR

Wednesday 5 June 2019

OSPF Series 10: Everything on Redistribution: Part 1- Basics, RIP, IGRP, EIGRP, Static and Connected

Everything on Redistribution- Basics, RIP, IGRP, EIGRP, Static and Connected

Route Redistribution Basics

It is preferable to employ a single routing protocol in an internetwork environment, for simplicity and ease of management. Unfortunately, this is not always possible, making multi-protocol environments common.

Route Redistribution allows routes

Tuesday 28 May 2019

OSPF Series 9: Route Filtering and Route-Maps

Prefix-Lists

Prefix-lists are used to match routes as opposed to traffic. Two things are matched:

  • The prefix (the network itself)

  • The prefix-length

Wednesday 22 May 2019

OSPF Series 8: Prefix Lists

Prefix Lists

Example 1)

access-list 1 permit 1.2.3.0 0.0.0.255
ip prefix-list LIST permit 0.0.0.0/0 le 32
This means:

Check the first 0 bits of the prefix 0.0.0.0 The subnet mask must be less than or equal to 32

Thursday 16 May 2019

OSPF Series 7: Example of OSPF Path Preferences, Troubleshooting neighborship stuck in various OSPF States

SCENARIO: Path Preferences:

  • Configure Router-IDs on each router

  • COnfigure IP address of interfaces in each router and add them using network command of OSPF

  • Note: there is no need to configure static routes on MT708 as both the links are directly connected. MT708 doesn’t run OSPF.

  • (On MT704,

Wednesday 8 May 2019

OSPF Series 6: OSPF Areas, OSPF Redistribution, Type-3 LSA, Type-5 LSA, Prefix Lists, Administrative Distance and Metric in OSPF

OSPF AREAS:

  • It is specific to interface (given in the network command)

To make a router in OSPF as Autonomous System Border Router (ASBR) that connects it to another AS running static routing, then, use

  • #router ospf 1
  • #redistribute static //if the other external AS is using static routing

(OR)

#redistribute connected