Circuit Emulation Service Provisioning
Prerequisites
To start creating a point-to-point Circuit Emulation service, both NEs which are meant to be the service endpoints (Initiator NE, Terminator NE) need to:
• be manageable;
• be present in NP and ENP domains;
• have at least one CE unit which is assigned and still has available resources in terms of:
− maximum number of interfaces,
− maximum number of Pseudowires,
− free timeslots in P12 containers (Structure Aware only),
• be operating in required Structure Mode: Aware or Agnostic (for details see CEPI1 user manual, sections 5.5 (CESoP configuration model), 5.6 (Packet parameters), 6.1 and 6.2 (Commissioning of a Pseudo Wire)),
• if MEF8 is going to be used: be operating in needed MEF8 Protocol: with or without Real-Time Protocol (RTP),
If the service is going to use MEF8 Broadcast MAC addressing:
• the CE units need to operate in the mode supporting it.
Transport Service requirements:
• VPWS Service Profile exists which is compatible in several required parameters. The compatibility checks include:
− Bandwidth (BW): if the SP BW is smaller than required service BW, and BW variability in SP is set to fixed, the SP is not eligible.
− Protection (Prot): if the SP Prot variability is set to variable, the SP is not eligible.
− Protection (Prot): only SP with protected or unprotected tunnel with fixed protection variability is eligible.
− A-end and Z-end UNI port configuration of the transport VPWS (UNI): only SP with scheduling profile equal to UNI scheduling profile is eligible.
− BW Enforcement: SP is eligible only if with BW Enforcement can be enabled.
− CoS Type (CT): If the CoS Type in the SP cannot be changed to “PCP”, the SP is not eligible.
− CoS Type (CT): If the CoS Type in the SP cannot be changed to “DSCP”, the SP is not eligible.
− CoS Type (CT): If the CoS Type in the SP cannot be changed to “INTERFACE”, the SP is not eligible.
− CoS Type (CT): If the Default Priority in the SP cannot be changed, the SP is not eligible.
• Link path between Initiator NE and Terminator NE exists and meets bandwidth requirements considering Service Profile Class Type allocation.
Please note:
To complete the service provisioning, a TDM Circuit Service needs to be created after the point-to-point Circuit Emulation Service has been created any deployed.
→ The procedure to create the TDM Circuit Service is described in section End-to-End TDM Services.