Epipe operational state decoupling

An Epipe service transitions to an operational state of down when only a single entity SAP or binding is active and the operational state of the mate is down or displays an equivalent state. The default behavior does not allow operators to validate the connectivity and measure performance metrics. With this feature, an option is provided to allow operators to validate the connectivity and measure performance metrics of an Epipe service before the customer handoff. The operator can also maintain performance and continuity measurement across their network regardless of the connectivity between the terminating node and the customer.

If the SAP between the operator and the customer enters a oper down state, the Epipe remains operationally up, so the results can continue to be collected uninterrupted. The operator receives applicable port or SAP alerts and alarms. This option is available only for the customer-facing SAP failures. If a network-facing SAP or spoke-SDP, fails the operational state of the Epipe service is set to down. That is, there is no option to hold the service in an up state, if a network component fails.

The following functionality is supported: