Juniper JN0-280 Practice Test - Questions Answers, Page 6

In legacy hierarchical network design, three key layers are used to create a scalable and structured network:

Step-by-Step Breakdown:

Access Layer:

The access layer is where end devices, such as computers and IP phones, connect to the network. It typically involves switches that provide connectivity for devices at the edge of the network.

Aggregation Layer (Distribution Layer):

The aggregation layer (also called the distribution layer) aggregates traffic from multiple access layer devices and applies policies such as filtering and QoS. It also provides redundancy and load balancing.

Core Layer:

The core layer provides high-speed connectivity between aggregation layer devices and facilitates traffic within the data center or between different network segments.

Juniper

Reference:

Legacy Hierarchical Design: Juniper networks often follow the traditional three-layer design (Access, Aggregation, and Core) to ensure scalability and high performance.

In a spine-leaf fabric architecture, which is commonly used in data center designs, each device has a distinct role to ensure efficient and scalable network traffic flow.

Step-by-Step Breakdown:

Spine Nodes:

The spine nodes form the backbone of the fabric and are responsible for transit traffic between leaf nodes. They connect to every leaf switch and provide multiple paths for traffic between leaf nodes, ensuring redundancy and load balancing.

Leaf Nodes:

The leaf nodes are used for host connectivity. These switches connect to servers, storage, or edge routers. They also connect to the spine switches to reach other leaf switches.

Juniper

Reference:

Spine-Leaf Architecture: In Juniper's IP fabric designs, spine switches handle inter-leaf communication, while leaf switches manage host and endpoint connectivity.

The BGP session in the exhibit shows the state as Connect, which indicates that the TCP session between the BGP peers has not been fully established.

Step-by-Step Breakdown:

BGP State 'Connect':

The Connect state is the second stage in the BGP finite state machine (FSM). At this stage, BGP is trying to establish a TCP session with the peer, but the session has not yet been successfully established.

A successful TCP three-way handshake (SYN, SYN-ACK, ACK) is required before BGP can progress to the OpenSent state, where the peers exchange BGP Open messages.

Possible Causes:

A firewall blocking TCP port 179.

Incorrect IP addresses or network connectivity issues between the BGP peers.

Juniper

Reference:

BGP Troubleshooting: In Junos, if a BGP session is stuck in the Connect state, the issue is likely due to a failure in establishing the underlying TCP connection.

In Junos, the default export policy for OSPF is to reject all routes from being exported.

Step-by-Step Breakdown:

Default Export Policy:

By default, OSPF in Junos does not export any routes to other routing protocols or neighbors. This is a safety mechanism to prevent unintended route advertisements.

Custom Export Policies:

If you need to export routes, you must create a custom export policy that explicitly defines which routes to advertise.

Example: You can create an export policy to redistribute static or connected routes into OSPF.

Juniper

Reference:

OSPF Export Behavior: In Juniper devices, the default policy for OSPF is to reject route advertisements unless explicitly configured otherwise through custom policies.

In the exhibit, R2 receives the same OSPF update from both R1 and R3. OSPF has mechanisms to prevent unnecessary processing of duplicate LSAs (Link-State Advertisements).

Step-by-Step Breakdown:

OSPF LSA Processing:

OSPF uses LSAs to exchange link-state information between routers. When a router receives an LSA, it checks if it already has a copy of the LSA in its Link-State Database (LSDB).

Duplicate LSAs:

If R2 has already received and processed the update from R1, it will ignore the update from R3 because it already has the same LSA in its database. OSPF uses the concept of flooding, but it does not reprocess LSAs that it already knows about.

R2 Behavior:

R2 will keep the update from R1 (the first one it received) and will ignore the same LSA from R3, as it is already in the LSDB.

Juniper

Reference:

OSPF LSA Processing: Junos adheres to OSPF standards, ensuring that duplicate LSAs are not processed multiple times to avoid unnecessary recalculations.

A trunk interface on a switch is used to carry traffic for multiple VLANs between switches or between a switch and another network device, like a router. Trunk interfaces use 802.1Q tagging to identify which VLAN the traffic belongs to.

Step-by-Step Breakdown:

Trunk Ports:

Trunk ports are typically used for inter-switch links or switch-to-router links where multiple VLANs need to be carried over the same physical connection.

VLAN traffic is tagged with a VLAN ID to ensure that it is properly identified as it crosses the trunk link.

802.1Q VLAN Tagging:

Trunk ports use 802.1Q to tag Ethernet frames with the VLAN ID. This ensures that frames are correctly forwarded to the appropriate VLANs on the other side of the trunk.

Juniper

Reference:

Trunk Interface Configuration: In Juniper switches, trunk ports are configured to carry tagged traffic for multiple VLANs, which is essential for interconnecting multiple network segments.

The configuration in the exhibit shows the persistent-learning feature enabled on interface ge-0/0/1.0.

Step-by-Step Breakdown:

Persistent Learning:

Persistent-learning ensures that the MAC addresses learned on the interface are retained in the Ethernet-switching table, even after a device reboot. This prevents the need to re-learn MAC addresses after the device restarts, improving stability and reducing downtime.

Use Case:

This feature is particularly useful in environments where the re-learning of MAC addresses could cause temporary disruptions or delays in communication, such as in critical Layer 2 network segments.

Command Example:

set switch-options interface ge-0/0/1.0 persistent-learning

Juniper

Reference:

Persistent MAC Learning: In Junos, enabling persistent-learning ensures that learned MAC addresses are not lost during reboots, contributing to smoother network operations in environments where stability is crucial.

In BGP (Border Gateway Protocol), when evaluating multiple routes to the same destination, the first attribute that is considered is the local preference value. The local preference is a BGP attribute used to influence outbound routing decisions within an Autonomous System (AS).

Step-by-Step Breakdown:

Local Preference:

The local preference attribute is used to determine which path is preferred for traffic leaving the AS. The higher the local preference value, the more preferred the route.

BGP Path Selection:

The BGP path selection process evaluates the following attributes in this order:

Local Preference (higher is preferred)

AS Path (shorter is preferred)

Origin (IGP > EGP > incomplete)

MED (Multi-Exit Discriminator) (lower is preferred)

Juniper

Reference:

BGP Path Selection: In Junos, the local preference attribute is the first to be evaluated when determining the best path for outbound traffic.

In Junos OS, the default route preference for a static route is 5. Route preference values are used to determine which route should be installed in the routing table when multiple routes to the same destination are available.

Step-by-Step Breakdown:

Static Route Preference:

A static route, by default, has a preference of 5, making it a highly preferred route. Lower preference values are more preferred in Junos, meaning static routes take precedence over most dynamic routing protocol routes, such as OSPF (preference 10) or BGP (preference 170).

Route Preference:

Route preference is a key factor in the Junos routing decision process. Routes with lower preference values are preferred and installed in the forwarding table.

Juniper

Reference:

Static Routes: In Junos, the default preference for static routes is 5, making them more preferred than most dynamic routes.