Juniper JN0-280 Exam With Confidence Using Practice Dumps

When an OSPF (Open Shortest Path First) neighborship is stuck in the ExStart state, it usually points to a mismatch in Maximum Transmission Unit (MTU) settings between two routers trying to establish the adjacency. The ExStart state is where OSPF routers negotiate the master-slave relationship and exchange DBD (Database Description) packets.

Step-by-Step Breakdown:

OSPF Neighbor States: OSPF goes through several states to establish an adjacency with a neighbor:

Down: No hello packets have been received.

Init: Hello packets are received, but bidirectional communication isn't confirmed.

2-Way: Bidirectional communication is established.

ExStart: The routers are negotiating who will be the master and who will be the slave, and begin to exchange DBD packets.

Exchange: The routers start exchanging the database information.

Loading: The routers process the Link-State Advertisements (LSAs).

Full: The adjacency is fully established.

MTU Mismatch Issue:During the ExStart state, both OSPF routers must agree on their MTU values. If there is an MTU mismatch between the two routers, OSPF neighbors will fail to move from the ExStart to the Exchange state. The router with the larger MTU setting will not accept DBD packets from the router with a smaller MTU because the packets may exceed the smaller MTU size.

In Juniper devices, this behavior can be identified by examining the MTU settings using the show interfaces command and ensuring both routers have matching MTU configurations. To resolve this issue, either match the MTU settings on both routers or configure OSPF to ignore MTU mismatches using the command set protocols ospf ignore-mtu.

Juniper Reference:

Junos Command: show ospf neighbor helps diagnose neighbor states.

MTU Adjustment: set interfaces mtu can be used to set the MTU values correctly.

AMAC address of FF-FF-FF-FF-FF-FFis the Ethernetbroadcast address. When a switch receives a frame with this destination MAC address, it is required to forward the frame to all interfaces except the one it was received on.

Step-by-Step Breakdown:

Broadcast Frame Handling:When a frame with the broadcast MAC address is received, the switch will flood it out of all active ports that belong to the same VLAN as the incoming frame. The broadcast frame is not sent back out of the ingress interface (the interface where the frame was originally received).

Purpose of Flooding:Broadcasting is used to ensure that the frame reaches all devices within the broadcast domain (all devices within the same VLAN), which may not have a specific entry for the MAC address in their MAC address table.

Juniper Reference:

Layer 2 Frame Forwarding: Juniper switches flood broadcast frames to all ports in the same VLAN, except the port the frame was received on.

Filter-Based Forwarding (FBF) in Junos OS allows traffic to be routed based on specific criteria such as source address, rather than just the destination address. This is useful in scenarios like policy routing or providing multiple paths for different types of traffic.

Step-by-Step Breakdown:

Instance-Type Forwarding:You must create aninstance-type forwardingrouting instance. This routing instance allows for different routing tables based on the incoming packet filter.

Command:

set routing-instances FBF-instance instance-type forwarding

Match Filter:You need to create afilterto match the traffic that will be forwarded according to your custom routing policy. This filter is applied to an interface to determine which traffic will use the custom forwarding instance.

Command Example:

set firewall family inet filter FBF-filter term 1 from source-address