Question 1
At a regional service-provider operations center, an engineering review finds: A metro aggregation design places a latency-sensitive enterprise E-Line directly across an IP core with no documented Ethernet service handoff, leading to mismatched expectations for transparent VLAN carriage. Which change most directly corrects the service problem?
Explanation
Correct Answer
Define the Carrier Ethernet E-Line service demarcation and use an appropriate provider Ethernet or pseudowire transport between the designated endpoints. This directly addresses the fictional service-provider network case: A metro aggregation design places a latency-sensitive enterprise E-Line directly across an IP core with no documented Ethernet service handoff, leading to mismatched expectations for transparent VLAN carriage. The technical mechanism is: An E-Line is a point-to-point Ethernet service whose service boundary must be explicit even when the underlying provider backbone uses routed transport. Verify success by: A test frame sent between the two UNI endpoints retains the required service VLAN attributes and does not reach any unapproved site.
Incorrect Answers
Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture. This would respond to a DIFFERENT fictional service-provider network issue: A 5G fronthaul transport team treats a RAN radio-to-distributed-unit path as an ordinary best-effort internet uplink and sees timing instability during peak load. It does not directly address the current situation: A metro aggregation design places a latency-sensitive enterprise E-Line directly across an IP core with no documented Ethernet service handoff, leading to mismatched expectations for transparent VLAN carriage.
Place an explicit supported SRv6-to-MPLS interworking function at the technology boundary or constrain the SRv6 path to capable nodes. This would respond to a DIFFERENT fictional service-provider network issue: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. It does not directly address the current situation: A metro aggregation design places a latency-sensitive enterprise E-Line directly across an IP core with no documented Ethernet service handoff, leading to mismatched expectations for transparent VLAN carriage.
Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload. This would respond to a DIFFERENT fictional service-provider network issue: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. It does not directly address the current situation: A metro aggregation design places a latency-sensitive enterprise E-Line directly across an IP core with no documented Ethernet service handoff, leading to mismatched expectations for transparent VLAN carriage.