sap sap-id [no-endpoint] [create]
sap sap-id endpoint endpoint-name [create]
no sap sap-id
config>service>epipe
Supported on all 7210 SAS platforms as described in this document
This command creates a SAP within a service. A SAP is a combination of port and encapsulation parameters that identify the SAP on the interface and within the service. Each SAP must be unique.
All SAPs must be explicitly created. If no SAPs are created within a service or on an IP interface, a SAP does not exist on that object.
Enter an existing SAP without the create keyword to edit SAP parameters.
For ports in network mode, multiple SAPs on the same port can belong to the same service.
If a port is shut down, all SAPs on that port become operationally down. When a service is shut down, SAPs for the service are not displayed as operationally down, although all traffic traversing the service is discarded.
The operational state of a SAP is relative to the operational state of the port on which the SAP is defined.
The following encapsulations are supported:
Ethernet access SAPs support null, dot1q
Ethernet access-uplink SAPs support only QinQ encapsulation.
The no form of this command deletes the SAP with the specified port. When a SAP is deleted, all configuration parameters for the SAP are also deleted.
A default SAP has the following format: port-id:*. This type of SAP is supported only on Ethernet MDAs, and its creation is allowed only in the scope of Layer 2 services (Epipe and VPLS).
Specifies the physical port identifier portion of the SAP. See Common CLI command descriptions for command syntax.
Keyword that adds a SAP endpoint association.
Keyword that removes the association of a SAP with an explicit endpoint name.
Keyword used to create a SAP instance. The create keyword requirement can be enabled or disabled in the environment>create context.
tod-suite tod-suite-name
no tod-suite
config>service>epipe>sap
Supported on all 7210 SAS platforms as described in this document
This command applies a time-based policy (filter or QoS policy) to the service SAP. The suite name must already exist in the config>cron context.
no tod-suite
Specifies a collection of policies (ACLs, QoS) including time-ranges that define the full or partial behavior of a SAP. The suite can be applied to more than one SAP.
accounting-policy acct-policy-id
no accounting-policy
config>service>epipe>sap
config>service>epipe>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
This command creates the accounting policy context that can be applied to a SAP or spoke-SDP.
An accounting policy must be defined before it can be associated with a SAP or spoke-SDP. If the policy-id does not exist, an error message is generated.
A maximum of one accounting policy can be associated with a SAP or spoke-SDP at one time. Accounting policies are configured in the config>log context.
The no form of this command removes the accounting policy association from the SAP or spoke-SDP, and the accounting policy reverts to the default.
Specifies the accounting policy-id, as configured in the config>log>accounting-policy context.
[no] collect-stats
config>service>epipe>sap
Supported on all 7210 SAS platforms as described in this document
This command enables accounting and statistical data collection for either the SAP, network port, or IP interface. When applying accounting policies, by default the data is collected in the appropriate records and written to the designated billing file.
When the no collect-stats command is issued, the statistics are still accumulated by the cards. However, the CPU does not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued, the counters written to the billing file include all the traffic while the no collect-stats command was in effect.
no collect-stats
ethernet
config>service>epipe>sap
Supported on all 7210 SAS platforms as described in this document
This command configures Ethernet properties in this SAP.
[no] llf
config>service>epipe>sap>ethernet
Supported on all 7210 SAS platforms as described in this document
This command enables Link Loss Forwarding (LLF) on an Ethernet port. It provides an end-to-end OAM fault notification for Ethernet VLL service.
LLF on an Ethernet port brings down the port when there is a local fault on the pseudowire or service, or a remote fault on the SAP or pseudowire, signaled with label withdrawal or TLDP status bits. LLF stops signaling when the fault disappears.
The Ethernet port must be configured for null encapsulation.
The no form of this command disables LLF.
[no] ignore-oper-down
config>service>epipe>sap
Supported on all 7210 SAS platforms as described in this document
This optional command configures a specific SAP to ignore the transition of the operational state to down when a SAP fails. Only a single SAP in an Epipe may use this option.
no ignore-oper-down
mip [mac mac-address]
mip default-mac
no mip
config>service>epipe>sap>eth-cfm
config>service>epipe>spoke-sdp>eth-cfm
config>service>vpls>sap>eth-cfm
config>service>vpls>spoke-sdp>eth-cfm
Supported on all 7210 SAS platforms as described in this document
This command enables Maintenance Intermediate Points (MIPs) to be created if mhf-creation for the MA is configured using the default option.
The no form of this command deletes the MIP.
no mip
Specifies the MAC address of the MIP.
Keyword to change the MAC back to the default MAC without having to delete the MIP and reconfigure it.