Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Validation Framework

This Metro Ethernet Business Services JVD addresses the network modernization journey, which includes multiple evolving use cases. A crucial aspect of the overall solution is enabling flexibility to support heterogeneous customer architectures within the same validated design. Major attributes include:

  • Seamless SR-MPLS with TI-LFA
  • Flexible Algorithm Application Specific Link Attribute (ASLA)
  • Co-Existence of Seamless SR-MPLS BGP-LU and BGP-CT inter-AS solutions
  • End-to-end color-aware Traffic Steering (à la Network “Lite-Slicing”)
  • Intra-domain Transport Class tunneling with Service Mapping
  • Inter-domain color awareness with BGP Classful Transport
  • All services include color-aware and color-agnostic path selection
  • Intent-based routing with Color Mapping based on Delay and TE metrics
  • Color agnostic services take IGP metric paths (inet.3)
  • Strict Resolution Scheme (no fallback) + Cascade Fallback Gold failback Bronze and Bronze fallback to Best Effort
  • Alignment with MEF 3.0 standards for service characteristics and attributes

An important focus of the Metro Ethernet Business Services JVD involves alignment with the MEF standards. The Metro Ethernet Forum is an industry consortium dedicated to accelerating the adoption of Carrier Ethernet services and technologies. Its primary purposes and goals revolve around standardization, interoperability, and innovation within the Ethernet ecosystem. The MEF works to develop and promote standards for Carrier Ethernet services, ensure interoperability between Carrier Ethernet networks and equipment from different vendors, foster innovation by promoting the development of new technologies and services based on Carrier Ethernet, and educate the market about the benefits and capabilities of Carrier Ethernet services.

The referenced technical specifications include:

  • MEF 6.3 Subscriber Ethernet Services Definitions
  • MEF 10.4 Subscriber Ethernet Service Attributes
  • MEF 23.2 Carrier Ethernet Class of Service
  • MEF 26.2 Operator Ethernet Service Attributes
  • MEF 35.1 Service OAM Performance Monitoring
  • MEF 45.1 Ethernet Layer 2 Control Protocols
  • MEF 48 Carrier Ethernet Service Activation
  • MEF 51.1 Operator Ethernet Service Definitions
  • MEF 62 Managed Access E-Line

The Juniper Networks routers that are featured in this JVD include MEF 3.0-certified MX304, ACX7100, ACX7509, ACX7024, ACX5448, and ACX710 platforms.

The services framework includes the following models:

  1. E-Line for delivering point-to-point connections as Ethernet Private Lines (EPL) or Ethernet Virtual Private Lines (EVPL).

  2. E-LAN for delivering multipoint-to-multipoint connections as Ethernet Private LAN (EP-LAN) or Ethernet Virtual Private LAN (EVP-LAN).

  3. E-TREE for delivering rooted-multipoint hub-and-spoke connections as Ethernet Private Tree (EP-TREE) or Ethernet Virtual Private Tree (EVP-TREE).

  4. E-ACCESS for delivering wholesale point-to-point services connecting UNI to NNI as Access EPL or Access EVPL.

  5. INTERNET ACCESS is an IP Service created by connecting IP Virtual Connections (IPVC) with other IPVC endpoints.

Services Attributes are further defined by the major characteristics:

  • Service multiplexing determines whether the UNI terminates one (disabled) or more (enabled) Ethernet services.
  • Bundling is enabled when multiple CE-VLANs are supported on the UNI, or disabled when each Ethernet Service includes a single CE-VLAN.
  • All-to-One bundling means that all CE-VLANs are associated with a single Ethernet Service as a private UNI service. When bundling is disabled, one or more virtual private services are enabled per UNI.

The MEF provides guidance for valid service multiplexing and bundling combinations, which are followed by this validated design. For more information, refer to the MEF documentation.

Table 1: MEF Bundling and Service Multiplexing
Service Multiplexing Bundling All to One Bundling Description
Yes No No Multiple virtual private services are allowed at the UNI with only one CE-VLAN ID mapped to each service.
Yes Yes No Multiple virtual private services enabled at the UNI and multiple CE-VLAN IDs can be mapped to each service.
Yes Yes Yes Illegal configuration
Yes No Yes Illegal configuration
No No Yes Single private service at the UNI.
No Yes No Single virtual private service enabled at the UNI with multiple CE-VLAN IDs mapped to it.
No Yes Yes Illegal configuration
No No No Single virtual private service enabled at the UNI with only a single CE-VLAN ID mapped to it.

Reference: https://wiki.mef.net/display/CESG/Bundling+and+Service+Multiplexing

We explain how the featured services map to the MEF definitions throughout this validated design.

Test Bed

This diagram explains the connectivity for building the Metro EBS JVD infrastructure. The Metro Fabric topology leverages a spine-and-leaf model in the green-dotted region with MEG1 and MEG2 as border leaf nodes. Services within the Metro Fabric use spine aggregation nodes (AG1.1, AG1.2) for communication between access nodes (AN). The multi-ring infrastructure in the orange-dotted region includes common metro distribution routers supporting inter-ring communications.

Figure 1: Metro EBS JVD Infrastructure Metro EBS JVD Infrastructure

Platforms / Devices Under Test (DUT)

Selected access platforms include ACX7024, ACX7100-48L, ACX710, ACX5448 and MX204 platforms. Aggregation or spine platforms include the ACX7100-32C in the metro fabric and ACX7509 with MX10003 routers as metro distribution routers in the ring architecture. The Metro edge gateway performs border leaf functions with the ACX7509 and ACX7100-32C providing connectivity into edge compute complexes. The Metro core uses the PTX10001-36MR core and peering platform. The MX304 is ideally situated for the multiservices edge, supporting complex services termination and interconnect points.

The supported versions of Junos OS and Junos OS Evolved for all devices is 23.2R2, where applicable.

Table 2: JVD Devices Under Test
Devices Under Test
Abbreviation Platform Role OS
AN ACX7100-48L Access Node Leaf Junos OS Evolved 23.2R2
AG1 ACX7100-32C Lean Spine Aggregation Node Junos OS Evolved 23.2R2
MEG1 ACX7100-32C Metro Edge Gateway Router Junos OS Evolved 23.2R2
MEG2 ACX7509 Metro Edge Gateway Router Junos OS Evolved 23.2R2
MSE MX304 Multiservices Edge Router Junos OS 23.2R2
MDR ACX7509 Metro Distribution Router Junos OS Evolved 23.2R2
MA ACX7100-48L Metro Access node Junos OS Evolved 23.2R2
MA ACX7024 Metro Access node Junos OS Evolved 23.2R2

Test Bed Configuration

Contact your Juniper Networks representative to get the full archive of the test bed configuration used for this JVD.