An Epipe service transitions to an operational state of down when only a single entity SAP or binding is active and the operation state of the mate is down or displays an equivalent state. The default behavior does not allow you to validate the connectivity and measure performance metrics. With this feature an option is provided to allow you to validate the connectivity and measure performance metrics of an Epipe service.
You can also maintain performance and continuity measurement across the customer 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/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:
Configuration under SAP is required to change the default behavior of the Epipe service in response to the SAP failure.
The user can create a SAP on a LAG where the LAG has no port members. In this case, the operator configures the ignore-oper-state on the SAP and the service remains operational. However, as there are no ports existing in the LAG member group, there is no extraction function that can be created. This feature protects against an established working configuration with full forwarding capabilities from failing to collect PM data. The user should shutdown their equipment and place the Epipe SAP in an operationally down state.
The SAP connecting the provider equipment to the customer is configured to hold the Epipe service status UP when the customer facing SAP enters any failed state. Only one SAP per Epipe is allowed to be configured.
Any failure of the network entity (network SAP or SDP-Binding) still cause the Epipe service to transition to OPER=DOWN.
As the service remains operationally up, all bindings should remain operationally up and should be able to receive and transmit data. The PW status represents the failed SAP in the LDP status message, but this does not prevent the data from using the PW as a transport, in or out. This is the same as LDP status messaging.
The SAP failure continues to trigger normal reactions, except the operational state of the service.
ETH-CFM PM measurement tools (DMM/SLM) can be used with the UP MEP on the failed SAP to collect performance metric. Additionally, CFM troubleshooting tools and connectivity (LBM, LTM, AIS, CCM) can be used and function as usual.
ETH-CFM CCM processing and fault propagation does not change. Even when a SAP fails with the hold service UP configuration, CCM sets the Interface Status TLV to ‟Down”.
VPLS services remain operationally UP until the final entity in the service enters a failed operational state. There are no changes to VPLS services and the change is specific to Epipe.