JN0-105 Questions and Answers

The show | compare command in Junos OS is used to display the differences between the candidate configuration and the active configuration. If no output is shown when you issue this command, it means that there are no changes between the candidate configuration and the active configuration. This indicates that the candidate configuration is identical to the active configuration, and thus no differences are displayed.

Routing policies in Junos OS are crucial for controlling route advertisements and path selection. The correct answers are B and C. An import routing policy for BGP determines which received prefix advertisements are placed in the routing information base (RIB), and policy terms are evaluated from top to bottom, with action taken on the first match found. This sequential evaluation allows for precise control over routing decisions.

In the OSI model, the Data Link Layer is responsible for node-to-node delivery of data. It frames the packets received from the Network Layer and prepares them for physical transmission. The Protocol Data Unit (PDU) for the Data Link Layer is called a "frame." Frames encapsulate the network layer packets, adding a header and a trailer that include the hardware addresses of the source and destination, among other things, facilitating the data link layer services like frame synchronization, flow control, and error checking.

When creating a new policy to accept and redistribute routes into your Interior Gateway Protocol (IGP), the route-filter match criteria is used to identify the route prefixes to select. The route-filter statement specifies which prefixes should be matched in a policy. This allows for precise control over which routes are accepted and redistributed, facilitating efficient and secure routing policies within the network.

References:

"show | display set | match ge-0/0/2" indicating command examples and match criteria from Useful Juniper Commands.txt​​.

Juniper official documentation: Routing Policy and Firewall Filters Configuration Guide.

For the users in the 10.1.1.0/24 subnet and the server in the 10.1.2.0/24 subnet to communicate with each other, they need to route packets through the router that connects these two subnets. Each user and the server need to have their default gateway set to the IP address of the router interface on their respective subnet (.254). This ensures that packets destined for other subnets are sent to the router, which then routes them to the correct destination subnet.

References:

Juniper official documentation: Configuring Basic Routing.

General networking principles.

In Junos OS, the # prompt indicates that you are in configuration mode. This mode is used for making changes to the configuration of the device.

Referring to the firewall filter configuration in the exhibit, when a packet matches the specified term limit-icmp, two actions are defined in the then statement: count count-icmp and discard. The count count-icmp action means that each time a packet matches this term, a counter named count-icmp will be incremented, providing a tally of how many packets have matched the term. The discard action means that the packet will be dropped and not forwarded through the device. This effectively prevents the packet from reaching its intended destination. There is no action specified that would cause an ICMP destination unreachable message to be returned, nor is there any action that would allow the packet to be forwarded.

If you've committed a configuration and then need to revert to the previous configuration, the rollback command is used. Since the incorrect IP address has not been committed, as indicated by the commit check command being successful, issuing rollback 1 will undo the changes made in the current session, which includes the accidental entry of the IP address.

The error message in the exhibit indicates that the root-authentication statement is missing, which is mandatory for committing the configuration. In Junos OS, it is required to set a password for the root account to commit any configuration changes. This is a security measure to ensure that unauthorized users cannot access the device's configuration mode. To solve the error shown in the exhibit, configuring a password for the root account is necessary. This can be done by using the set system root-authentication plain-text-password command, after which the user will be prompted to enter a new password for the root account.

The Address Resolution Protocol (ARP) is responsible for mapping an IPv4 address to a machine's MAC address. ARP operates at Layer 2 of the OSI model and is used to find the MAC address of a host given its IPv4 address. When a device wants to communicate with another device on the same local network, it uses ARP to discover the recipient's MAC address.

References:

Juniper official documentation: ARP.

Networking standards: RFC 826.

Firewall filters in Junos OS are stateless, meaning they process each packet individually without regard to the state of a connection or sequence of packets. These filters can match various packet attributes, including those at Layer 4, such as TCP and UDP port numbers. This allows for granular control over traffic based on the type of service or application. Unlike stateless filters, stateful firewalls keep track of the state of active connections and make decisions based on the context of the traffic flow, which is not a capability of Junos firewall filters. Additionally, Junos firewall filters primarily operate up to Layer 4 and do not natively inspect Layer 7 parameters, which involve application-level data.

Traceoptions in Junos OS are used for detailed debugging and troubleshooting of protocols and processes within the system. They are not enabled by default due to the potential performance impact and volume of data generated. Instead, traceoptions are enabled through specific configuration settings under the relevant protocol or process hierarchy. This allows administrators to target their troubleshooting efforts and control the scope of logging. By default, the output generated by traceoptions is stored in files located in the /var/log directory, with the file name typically specified in the traceoptions configuration. This structured approach to logging and debugging helps in diagnosing complex issues without overwhelming the system or the administrator with irrelevant data.

After increasing the MTU size of an interface and committing the configuration, the command to verify the applied MTU change is D, "show interfaces ge-0/0/0." This command displays detailed information about the interface, including the current MTU size, making it the best choice for verifying the applied changes.

The Routing Engine (RE) in Junos OS has several critical functions, including processing all management traffic (A) and running the Junos operating system (B). The RE handles system management tasks, user interfaces, system services, and routing protocol processes. It does not directly process transit traffic or evaluate firewall filters for transit traffic, as these tasks are handled by the Packet Forwarding Engine (PFE).

The Packet Forwarding Engine (PFE) is an integral component of Juniper Networks devices, responsible for the data plane operations. The data plane, also known as the forwarding plane, is where the actual processing and forwarding of packets occur based on the routing and forwarding tables. The PFE executes the forwarding decisions made by the Routing Engine (RE), handling all packet transmissions, including routing, filtering, and switching packets towards their destination. This contrasts with the control plane operations handled by the RE, which involve routing table maintenance, system management, and control protocol processing.

Issuing the rollback 0 command in Junos OS will discard any uncommitted changes and revert to the last committed configuration. This command effectively cancels any configuration changes that have been made but not yet committed, ensuring that the device returns to its previous stable state.

References:

"rollback 0 ...................................(rolls back the changes just made )" from Useful Juniper Commands.txt​​.

Juniper official documentation: Rolling Back a Configuration.

RADIUS, which stands for Remote Authentication Dial-In User Service, provides authentication services for users trying to access a network. It is a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management for users who connect and use a network service.

The exhibit shows a ping test being executed from router R2 to the IP address 10.23.0.3. Since the ping command is issued on R2 and we see successful replies from 10.23.0.3, it means the source of the ping must be an interface on R2. Given the network diagram and the IP address scheme, the source IP address of the ping is on the interface ge-0/0/2 of R2, which is in the subnet 10.23.0.0/24. The only logical IP address for R2's interface in this subnet, based on standard networking practices and the given options, would be 10.23.0.2. The other addresses provided in the options belong to different subnets or are the destination of the ping itself.

The request system configuration rescue save command in Junos OS saves the most recently committed configuration as the rescue configuration. This rescue configuration can be used to recover the device if future configurations cause issues. It ensures there is a stable, known-good configuration to fall back on, which is crucial in network management and troubleshooting.

References:

"rescue : save configurations as the rescue: request system configuration save .................( saves the current configs as a rescue configs )" from Useful Juniper Commands.txt​​.

Juniper official documentation: Configuring and Activating a Rescue Configuration.

The Routing Engine (RE) in Juniper Networks devices plays a critical role in the control plane operations. One of its functions includes responding to network utility commands like ping and traceroute, which are essential for diagnosing network connectivity and path issues. Furthermore, the RE is responsible for maintaining the routing tables, which contain information about network paths and destinations. These tables are vital for making forwarding decisions but are distinct from the actual forwarding of packets, which is handled by the Packet Forwarding Engine (PFE).

The Routing Protocol Daemon (rpd) in Junos OS is responsible for maintaining routing protocols and tables. It handles all routing information, including the calculation of routes and the population of the routing table, making it crucial for dynamic routing operations.

In Junos OS, as with many network operating systems, the control plane is responsible for processes that determine how to route traffic. This includes maintaining routing tables, which store information about network paths and protocols. Therefore, routing tables are indeed stored in the control plane.

Exception traffic refers to packets that cannot be processed by the normal fast-path processing of the Packet Forwarding Engine (PFE) in the forwarding plane, and thus are sent to the control plane for further processing. This might include packets destined for the router itself, packets that need to be fragmented, or packets that match certain firewall filter criteria, among other reasons.

Routing tables are not stored in the forwarding plane. However, the forwarding plane contains the forwarding table (sometimes referred to as the forwarding information base or FIB), which is a distilled version of the routing table optimized for fast packet forwarding. The forwarding plane uses this information to perform the actual transfer of packets across the network device interfaces.

Referring to the exhibit, the presence of the "+" symbol next to the OSPF route for 192.168.100.2/32 indicates that this is the active route being used to forward traffic. The BGP route, although present, does not have the "+" symbol, indicating it is not the active route. In Junos OS, the routing table displays the active route with a "+" symbol, and the fact that the OSPF route has this symbol means it is the preferred path based on the routing protocol's decision process, which takes into account factors such as route preference (administrative distance) and metrics.

Class of Service (CoS) in Junos OS provides tools for managing traffic congestion and ensuring that latency-sensitive traffic is given priority over less time-critical data. By implementing CoS, network administrators can classify traffic into different priority levels, apply scheduling policies to ensure that high-priority traffic is transmitted first, and use congestion management techniques such as queue buffers and drop profiles. This helps in maintaining the quality of service for critical applications, especially during periods of high network congestion. However, CoS does not eliminate congestion entirely nor does it inherently make the network faster; it provides a mechanism for better managing and controlling traffic flows according to their importance and time sensitivity.

When you enter ? at the command-line prompt in Junos OS, the system provides assistance in two significant ways. Firstly, it lists the available commands and options that can be used at the current point in the command hierarchy, aiding users in understanding what commands they can execute next. Secondly, it displays summary information about those commands and options, providing brief descriptions or additional context that can help users understand the function of each command or option. This feature is particularly useful for learning the command structure or for quick reference when specific command syntax is forgotten.