Free 500-230 sample questions

Correct answer: The `neighbor next-hop-self` command is missing on the ASBRs for the MP-eBGP session.

In an Inter-AS L3VPN Option B scenario, the ASBRs exchange VPNv4 routes via MP-eBGP. The next-hop for these routes is typically the PE router in the originating AS. Without the `next-hop-self` command, the receiving ASBR will not change the next-hop attribute, making the route unreachable for PEs in its own AS. While `send-community` is required for route-targets, the lack of `next-hop-self` is a common and critical error that directly prevents route propagation. An IGP does not run between ASBRs of different providers, and LDP is not required directly between ASBRs in Option B.

Correct answer: commit confirmed 5

The `commit confirmed ` command in IOS-XR is a safety mechanism that applies a configuration change but requires a second, confirming `commit` command within the specified time. If the confirmation is not received (e.g., because the change caused a loss of management access), the router automatically rolls back to the previous configuration. The value is specified in minutes, so `commit confirmed 5` sets a 5-minute timer.

Correct answers: show mpls ldp discovery; debug mpls ldp transport events

This command is crucial for viewing the LDP discovery process, including hello intervals and the state of adjacency with neighbors. It helps determine if the routers can even see each other at the LDP level, which is the first step in session establishment.

This debug command provides real-time information about the LDP TCP transport session events. It allows the engineer to see the session setup, keepalives, and any errors that might be occurring during the TCP handshake, which is a common point of failure or delay.

Correct answer: sysmgr

The System Manager (`sysmgr`) is a critical mandatory process in the IOS-XR operating system. Its primary function is to manage the lifecycle of all other processes. It reads the system configuration to determine which processes should be running, starts them, monitors their health, and restarts them if they fail.

Correct answer: ALPHA_VRF: export RT_ALPHA, import RT_ALPHA and RT_SHARED. BETA_VRF: export RT_BETA, import RT_BETA. SHARED_SERVICES_VRF: export RT_SHARED, import RT_ALPHA.

This configuration correctly implements the requirements. 1) `ALPHA_VRF` imports its own RT (`RT_ALPHA`) for full mesh connectivity and imports `RT_SHARED` to learn the route to the logging server. 2) `BETA_VRF` only imports its own RT (`RT_BETA`), ensuring complete isolation. 3) `SHARED_SERVICES_VRF` exports its routes with `RT_SHARED` and critically, only needs to `import RT_ALPHA` to learn the return path to AlphaCorp clients. It does not need to import its own routes or Beta's routes, ensuring one-way access initiation from AlphaCorp.

Correct answer: False

This statement is false. In IOS-XR's two-stage configuration model, changes made in configuration mode are held in a target or 'scratchpad' configuration. They are not applied to the active running configuration, nor are they synchronized to the standby RP, until the `commit` command is executed. The commit operation is what validates the changes, applies them to the active RP, and then synchronizes the new running configuration to the standby RP.

Correct answer: Labeled-unicast routes for the PE loopbacks must be exchanged between the ASes, typically via a dedicated BGP address-family.

Inter-AS Option C's main characteristic is that it extends the MPLS LSP from the ingress PE in one AS to the egress PE in another AS. To achieve this, the PE loopback addresses must be reachable across AS boundaries. This is accomplished by exchanging these loopbacks as labeled-unicast routes between the ASBRs (e.g., using `address-family ipv4 labeled-unicast`). This allows the PEs to build a recursive LSP to the remote PE's next-hop. Redistributing into the IGP would be a massive scalability and security issue.

Correct answer: install add source test

In IOS-XR, the `install add source test` command is specifically designed for pre-installation checks. It performs a dry run of the installation process, which includes verifying the package's integrity, checking for dependencies and prerequisites, and ensuring there are no conflicts, all without making any changes to the system. This is a critical best practice before applying any software update to a production device.

Correct answer: Use the `show processes bgp detail` command to inspect the threads and their individual CPU consumption.

When a process like BGP shows high CPU usage, it's often a single thread within that process causing the issue. The `show processes detail` command is the best first step as it breaks down the process into its individual threads and shows the CPU time consumed by each. This allows the engineer to pinpoint the specific function (e.g., scanner, router, I/O) that is misbehaving, which is essential for targeted debugging. Restarting the process is a last resort, and simply confirming the high usage doesn't provide new diagnostic data. flowchart TD A[Observe High CPU for 'bgp' process] --> B{What is the first diagnostic step?}; B --> C[show processes bgp detail]; C --> D{Identify high-CPU thread}; D --> E[Analyze thread function, e.g., 'BGP Scanner']; E --> F[Apply specific debugs for that function]; F --> G[Resolve underlying issue, e.g., route-policy loop];

Correct answer: `configure exclusive` prevents other users from entering configuration mode, while `lock` allows others to enter but prevents them from committing changes.

The `configure exclusive` command provides a system-wide lock, preventing any other user from entering configuration mode until the current user exits. The `lock` command is less restrictive; it is issued from within an existing configuration session and allows other users to enter configuration mode and make changes in their own sessions, but it prevents anyone from committing their changes until the lock is released.