Question 120
During production incident triage, engineers observe: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
- IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
- IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
- The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
Explanation
Correct Answer
C:IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. This principle directly explains the live production incident: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The aligned engineering response is: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended. The result should be established through: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
Incorrect Answers
A:Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. That explanation applies to the different IS-IS ISO family missing scenario rather than this live production incident. The current fault evidence is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The controlling mechanism is instead: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The correct response would be: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
B:IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. That explanation applies to the different IS-IS narrow metric ceiling scenario rather than this live production incident. The current fault evidence is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The controlling mechanism is instead: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The correct response would be: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
D:The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. That explanation applies to the different IS-IS DIS election surprise scenario rather than this live production incident. The current fault evidence is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The controlling mechanism is instead: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The correct response would be: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
Question 121
During production incident triage, engineers observe: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
- Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.
- VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.
- Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.
Explanation
Correct Answer
B:Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. This principle directly explains the live production incident: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The aligned engineering response is: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support. The result should be established through: The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
Incorrect Answers
A:MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. That explanation applies to the different MSTP region mismatch scenario rather than this live production incident. The current fault evidence is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The controlling mechanism is instead: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The correct response would be: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
C:VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. That explanation applies to the different Per-VLAN spanning-tree path scenario rather than this live production incident. The current fault evidence is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The controlling mechanism is instead: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The correct response would be: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
D:Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. That explanation applies to the different Root bridge election priority scenario rather than this live production incident. The current fault evidence is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The controlling mechanism is instead: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The correct response would be: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
Question 122
During production incident triage, engineers observe: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
- Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.
- Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
- A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
Explanation
Correct Answer
B:Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. This principle directly explains the live production incident: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The aligned engineering response is: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership. The result should be established through: The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
Incorrect Answers
A:Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. That explanation applies to the different Native VLAN mismatch scenario rather than this live production incident. The current fault evidence is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The controlling mechanism is instead: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. The correct response would be: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
C:Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. That explanation applies to the different Flexible VLAN tagging logical units scenario rather than this live production incident. The current fault evidence is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The controlling mechanism is instead: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. The correct response would be: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
D:A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. That explanation applies to the different Unknown unicast flooding behavior scenario rather than this live production incident. The current fault evidence is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The controlling mechanism is instead: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. The correct response would be: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
Question 123
During production incident triage, engineers observe: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
- RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
- Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
- Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
Explanation
Correct Answer
C:Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. This principle directly explains the live production incident: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The aligned engineering response is: Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted. The result should be established through: The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.
Incorrect Answers
A:MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. That explanation applies to the different MSTP region mismatch scenario rather than this live production incident. The current fault evidence is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The controlling mechanism is instead: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. The correct response would be: Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.
B:RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. That explanation applies to the different RSTP alternate port activation scenario rather than this live production incident. The current fault evidence is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The controlling mechanism is instead: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. The correct response would be: Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.
D:Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. That explanation applies to the different Unexpected BPDU on edge port scenario rather than this live production incident. The current fault evidence is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The controlling mechanism is instead: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. The correct response would be: Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.
Question 124
During production incident triage, engineers observe: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.
- For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.
- An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.
- Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
Explanation
Correct Answer
C:An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. This principle directly explains the live production incident: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The aligned engineering response is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination. The result should be established through: A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.
Incorrect Answers
A:A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. That explanation applies to the different Recursive next-hop resolution scenario rather than this live production incident. The current fault evidence is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The controlling mechanism is instead: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The correct response would be: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
B:For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. That explanation applies to the different Administrative preference overrides static scenario rather than this live production incident. The current fault evidence is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The controlling mechanism is instead: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The correct response would be: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
D:Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. That explanation applies to the different Generated default route prerequisite scenario rather than this live production incident. The current fault evidence is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The controlling mechanism is instead: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The correct response would be: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
Question 125
During production incident triage, engineers observe: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC.
- LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
- MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
- Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
Explanation
Correct Answer
B:LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. This principle directly explains the live production incident: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The aligned engineering response is: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors. The result should be established through: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
Incorrect Answers
A:LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC. That explanation applies to the different Missing LDP FEC label mapping scenario rather than this live production incident. The current fault evidence is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The controlling mechanism is instead: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The correct response would be: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
C:MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. That explanation applies to the different Incoming label missing in LFIB scenario rather than this live production incident. The current fault evidence is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The controlling mechanism is instead: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The correct response would be: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
D:Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. That explanation applies to the different Penultimate hop popping scenario rather than this live production incident. The current fault evidence is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The controlling mechanism is instead: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The correct response would be: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
Question 126
During production incident triage, engineers observe: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.
- Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
- IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
- The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.
Explanation
Correct Answer
A:When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. This principle directly explains the live production incident: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The aligned engineering response is: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs. The result should be established through: Neighbor exchanges succeed without authentication errors and their corresponding LSDB contents are current.
Incorrect Answers
B:Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. That explanation applies to the different IS-IS ISO family missing scenario rather than this live production incident. The current fault evidence is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The controlling mechanism is instead: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The correct response would be: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
C:IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. That explanation applies to the different IS-IS narrow metric ceiling scenario rather than this live production incident. The current fault evidence is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The controlling mechanism is instead: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The correct response would be: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
D:The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. That explanation applies to the different IS-IS DIS election surprise scenario rather than this live production incident. The current fault evidence is: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. The controlling mechanism is instead: When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. The correct response would be: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
Question 127
During production incident triage, engineers observe: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
- Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
- RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.
- LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.
Explanation
Correct Answer
D:LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. This principle directly explains the live production incident: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The aligned engineering response is: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution. The result should be established through: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
Incorrect Answers
A:LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. That explanation applies to the different LDP TCP 646 establishment scenario rather than this live production incident. The current fault evidence is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The controlling mechanism is instead: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The correct response would be: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.
B:Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. That explanation applies to the different Penultimate hop popping scenario rather than this live production incident. The current fault evidence is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The controlling mechanism is instead: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The correct response would be: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.
C:RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. That explanation applies to the different RSVP link protection plan scenario rather than this live production incident. The current fault evidence is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The controlling mechanism is instead: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The correct response would be: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.
Question 128
During production incident triage, engineers observe: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.
- LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
- LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
- Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
Explanation
Correct Answer
A:SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. This principle directly explains the live production incident: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The aligned engineering response is: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers. The result should be established through: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.
Incorrect Answers
B:LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. That explanation applies to the different LDP discovery and IGP mismatch scenario rather than this live production incident. The current fault evidence is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The controlling mechanism is instead: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The correct response would be: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
C:LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. That explanation applies to the different LDP TCP 646 establishment scenario rather than this live production incident. The current fault evidence is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The controlling mechanism is instead: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The correct response would be: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
D:Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. That explanation applies to the different Penultimate hop popping scenario rather than this live production incident. The current fault evidence is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The controlling mechanism is instead: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The correct response would be: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
Question 129
During production incident triage, engineers observe: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
- MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
- LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
- RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
Explanation
Correct Answer
B:MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. This principle directly explains the live production incident: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The aligned engineering response is: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC. The result should be established through: A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
Incorrect Answers
A:LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. That explanation applies to the different LDP discovery and IGP mismatch scenario rather than this live production incident. The current fault evidence is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The controlling mechanism is instead: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. The correct response would be: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
C:LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. That explanation applies to the different LDP TCP 646 establishment scenario rather than this live production incident. The current fault evidence is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The controlling mechanism is instead: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. The correct response would be: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
D:RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. That explanation applies to the different RSVP reservable bandwidth shortage scenario rather than this live production incident. The current fault evidence is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The controlling mechanism is instead: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. The correct response would be: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
Question 130
During production incident triage, engineers observe: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?
- MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
- RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
- LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
- Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.
Explanation
Correct Answer
B:RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. This principle directly explains the live production incident: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The aligned engineering response is: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling. The result should be established through: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.
Incorrect Answers
A:MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. That explanation applies to the different MPLS interface not enabled scenario rather than this live production incident. The current fault evidence is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The controlling mechanism is instead: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The correct response would be: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.
C:LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. That explanation applies to the different LDP discovery and IGP mismatch scenario rather than this live production incident. The current fault evidence is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The controlling mechanism is instead: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The correct response would be: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.
D:Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. That explanation applies to the different Penultimate hop popping scenario rather than this live production incident. The current fault evidence is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The controlling mechanism is instead: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The correct response would be: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests