-
Operation of Broadcast Network Type on NBMA Networks
The broadcast network type operates differently on NBMA (Non-Broadcast Multi-Access) networks, such as DMVPN, and involves several important considerations:
-
Multicast Capability: To ensure the correct operation of the broadcast network type on NBMA networks, multicast capability must be provided in some form by the NBMA network configuration. This is essential for effective communication among routers.
-
Designated Router (DR): The DR of the NBMA network needs to be a router that has full-mesh OSPF adjacencies with all routers in the network topology. Any router lacking this should be configured to be ineligible to be a DR using the
ip ospf priority 0
interface-level command. This ensures proper coordination in the network. -
Partial-Mesh Hub-and-Spoke Networks: In partial-mesh hub-and-spoke NBMA networks, the spokes must have mappings to reach remote spoke next-hop addresses. Additionally, each spoke router should have a mapping associating the physical address to the NBMA address of the spoke, if this is the correct configuration. This mapping is crucial for establishing efficient connectivity within the network.
-
-
Point-to-Multipoint Network Type in OSPF
-
In the context of OSPF, the Point-to-Multipoint network type operates differently from other network types like broadcast or non-broadcast. It dispenses with the concept of a Designated Router (DR) or Backup Designated Router (BDR) responsible for creating a centralized network node for the segment.
-
Instead, in Point-to-Multipoint configurations, each router individually models direct links to every other router it can communicate with over the multi-access network. This modeling is accomplished through the exchange of multicast hello messages over the multi-access segment. Unlike broadcast and non-broadcast network types, where it's assumed that all devices on the multi-access segment can directly communicate with each other, Point-to-Multipoint treats each router separately.
-
Point-to-Multipoint networking doesn't make any assumptions about connectivity between routers on the multi-access segment. To account for situations where routers lack direct connectivity, the local router takes a proactive approach. It advertises its own IP address on the multi-access segment as a /32 host route. This /32 host route serves a crucial purpose – it allows routers that don't have direct connectivity with the local router to find a path to reach it by routing their traffic through another router on the network.
-
This feature makes Point-to-Multipoint network types particularly useful for implementing partial-mesh hub-and-spoke network topologies, such as Dynamic Multipoint Virtual Private Network (DMVPN) setups. The presence of the /32 host route permits spoke routers to communicate with each other through a central hub without requiring manual configuration of static Next-Hop Resolution Protocol (NHRP) mappings. To make this work seamlessly, Point-to-Multipoint configuration needs to be enabled on all routers within the DMVPN network.
-
Unicast Communication: In contrast to the regular point-to-multipoint type, the Point-to-Multipoint Non-Broadcast network type does not employ unicast hello or other protocol packets. This means that routers in this configuration do not individually address their protocol packets to specific neighbors.
-
Static Neighbor Commands: To establish OSPF adjacencies in the Point-to-Multipoint Non-Broadcast type, routers rely on static neighbor commands. This approach requires manual configuration of neighbor relationships rather than relying on dynamic neighbor discovery through hello packets.
-
Interface Configuration: On the tunnel interface, it is essential to issue the command: "ip ospf network point-to-multipoint non-broadcast." This specific network type designation is crucial to define the behavior of the interface within the OSPF network.
-
Neighbor Configuration: In router configuration mode, the "neighbor" command is used in conjunction with specifying the cost if a particular neighbor is preferred. This allows fine-grained control over the selection of preferred neighbors based on cost considerations.
-
-
Establishment of Adjacencies: Point-to-multipoint network types rely on the use of multicast hello messages for the establishment of adjacencies. This approach enables routers within the DMVPN network to identify and communicate with each other efficiently.
-
Hello/Dead Timer Defaults: By default, the hello timer is set to 30 seconds, with a corresponding dead timer of 120 seconds. These timers govern the frequency of hello messages and the duration allowed for receiving them. They play a crucial role in the network's stability and responsiveness.
-
No DR/BDR Election: In point-to-multipoint configurations, there is no need for the election of a Designated Router (DR) or Backup Designated Router (BDR). This differs from network types like broadcast or non-broadcast, where a centralized network node is responsible for routing. Point-to-multipoint models the actual underlying connectivity between routers, avoiding the assumption that all routers can communicate directly.
-
Next-Hop Configuration: The next-hop configuration points to the remote neighbor that should be used to reach a specific prefix. This ensures that traffic is directed through the most efficient path to reach its destination.
-
IP Address Assignment: Within the context of point-to-multipoint, the IP address assigned to the link is conceptualized as a /32 host route. This means that the IP address is treated as a distinct host on the network, allowing routers to route traffic to it directly.
Point-to-multipoint network types in DMVPN are designed to optimize connectivity and routing within the network. These configurations prioritize efficient communication between routers, simplify the routing process, and ensure that each router is treated as an individual entity, facilitating precise routing and minimizing assumptions about network connectivity. These features make point-to-multipoint network types a valuable choice in DMVPN and similar networking scenarios.