User Manuals : FOXMAN-UN Help User Manual : Ethernet Networking Package : Service Provisioning and Deployment via ENP GUI
Hitachi Energy
Service Provisioning and Deployment via ENP GUI
This section includes the following topics:
The FOXMAN‑UN MPLS-TP service provisioning is possible via the ENP GUI.
* 
Please note: 
The term “ENP >” will be used as a shortcut for “NEM Desktop > Application > Ethernet Networking Package” to launch the ENP GUI.
The current release additionally requires the operator to assign the MPLS-TP port roles via FOXCST. The MPLS-TP node label range is fixed at 16-1048575.
The service configuration via the ENP GUI is in principle done in 2 steps:
1 Provisioning
Provisioning of MPLS-TP tunnel between two MPLS-TP nodes.
Manual or automatic selection of new paths to build Label Switched Paths (LSPs).
The provisioned tunnel can have one or two paths, a working and an optional protection LSP.
Creating the Service (see details further below).
2 Deployment
Apply the MPLS-TP configuration changes to the nodes.
FOXMAN‑UN verifies that the required resources are still available.
* 
Please note: 
Fiber connectivity is recommended to be in place between nodes prior to configuration. Routing of paths won’t be possible unless links are defined between the involved nodes.
The creation of a Service Profile and of services based on such Service Profiles requires a valid Traffic Engineering concept and includes the following steps:
1 Create a Class Type definition in FOXMAN‑UN, based on your Traffic Engineering concept. Use the “Class Type (HQoS Class Type Definition)” dialog for this purpose.
2 Create an appropriate set of Service Profiles. Use the “Create Service Profile” dialog. The number of required service profiles depends on the variety of services you have planned in your network.
3 Create VPWS or VPLS services, using the Service Profiles created in the previous step 2.
4 If required change the service parameters of service instances that have been set to “Variable” during the Service Profile creation. Service parameters that have been set to “Fixed” cannot be modified on a service instance.
5 Save the Service.
6 Deploy the (changed or new) Service.
7 The routing algorithm takes these (new) conditions into consideration.