A test SAP is configured under a unique test service type. This looks similar to a normal service context, but normally only contain a SAP configuration:
config
service
epipe <service-id> [test] [create]
[no] sap <sap-id>
[no] shutdown
[no] shutdown
config
service
cpipe <service-id> [vc-type {satop-e1 | satop-t1 | cesopsn | cesopsncas}
[test][create]
[no] sap <sap-id>
[no] shutdown
[no] shutdown
You can define test SAPs appropriate to any service or PW type supported by MPLS-TP, including a Cpipe or Epipe. The following test SAP types are supported:
Ethernet NULL, 1q, Q-in-Q
TDM E1, E3, DS0, DS3, and so on
The following constraints and conditions apply:
Up to a maximum of 16 test services can be configured per system.
It is possible to configure access ingress and access egress QoS policies on a test SAP, as well as any other applicable SAP-specific commands and overrides.
Vc-switching and spoke-SDP are blocked for services configured under the test context.
The test keyword is mutually exclusive vc-switching and customer.
Valid commands under a compatible test service context do not need to be blocked just because the service is a test service.