Configuring an administrative lock

An administrative lock is configured on a spoke-SDP using the admin-lock option of the tools perform command, as follows:

tools
    perform
      service-id <svc-id> 
         admin-lock
            pw
               sdp <sdp-id> admin-lock [test-svc-id <id>]

The following conditions and constraints apply for configuring an administrative lock:

• The lock can be configured either on a spoke-SDP that is bound to a SAP, another spoke-SDP or a VPLS interface.

• The lock is only allowed if a PW path ID is defined (for example, for static PWs with MPLS-TP identifiers).

• The lock cannot be configured on spoke-SDPs that are an Inter-Chassis Backup (ICB) or if the vc-switching keyword is present.

• The control-channel-status must be shutdown. The operator should also shutdown control-channel-status on spoke-SDPs belonging to an MS-PW at an S-PE whose far ends are administratively locked at its T-PEs. This should be enforced throughout the network management if using the 5620 SAM.

• When enabled, all traffic on the spoke-SDP is sent to and from a paired SAP that has the test keyword present, if such a SAP exists in the X endpoint (see Pseudowire redundancy service models). Otherwise, all traffic to and from the paired SAP is dropped.

• The lock can be configured at a spoke-SDP that is bound to a VLL SAP or a VPLS interface.

• The test-svc-id parameter refers to the test service that should be used to inject test traffic into the service. The test service must be of a compatible type to the existing spoke-SDP under test (see Table 1).

• If the test-svc-id parameter is not configured on an admin-locked spoke-SDP, user traffic is blocked on the spoke-SDP.

The service manager should treat an administrative lock as a fault from the perspective of a paired SAP that is not a test SAP. This causes the appropriate SAP OAM fault indication.

Table 1 maps supported real services to their corresponding test services.