sap sap-id [create]
no sap sap-id
config>service>epipe
Supported on all 7210 SAS platforms as described in this document
This command creates a Service Access Point (SAP) within a service. A SAP is a combination of port and encapsulation parameters that identify the service access point on the interface and within the 7210 device. 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. The SAP is owned by the service in which it was created.
On the 7210 SAS-D and 7210 SAS-Dxp, in a single physical port only one SAP can belong to one service. Multiple SAPs can be defined over a physical port but each of these SAPs should belong to different services. This restriction does not apply to the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, or 7210 SAS-K 3SFP+ 8C.
A SAP can be associated with only a single service. A SAP can only be defined on a port that has been configured as an access port. Additionally, in access-uplink mode, SAPs can also be defined on an access-uplink port. Access-uplink SAPs are network-facing SAPs representing dot1q or QinQ tunnels used to transport traffic toward the service nodes.
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, and QinQ.
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 be deleted. For IES, the IP interface must be shut down before the SAP on that interface may be removed.
A default SAP has the following format: port-id:*. This type of SAP is supported only on Ethernet MDAs, and its creation is only allowed 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 used to create a SAP instance. The create keyword requirement can be enabled or disabled in the environment>create context.
accounting-policy acct-policy-id
no accounting-policy [acct-policy-id]
config>service>epipe>sap
Supported on all 7210 SAS platforms as described in this document
This command enables the accounting policy context that can be applied to a SAP.
An accounting policy must be defined before it can be associated with a SAP. If the policy-id does not exist, an error message is generated.
A maximum of one accounting policy can be associated with a SAP 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, and the accounting policy reverts to the default.
Default accounting policy.
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 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 will 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] ais-enable
config>service>epipe>sap>eth-cfm
Supported on all 7210 SAS platforms as described in this document
This command enables the generation and the reception of AIS messages.
client-meg-level [[level [level ...]]
no client-meg-level
config>service>epipe>sap>eth-cfm>ais-enable
Supported on all 7210 SAS platforms as described in this document
This command configures the client maintenance entity group (MEG) levels to use for AIS message generation. Up to 7 levels can be provisioned, with the restriction that the client MEG level must be higher than the local MEG level.
Specifies the client MEG level.
interval {1 | 60}
no interval
config>service>epipe>sap>eth-cfm>ais-enable
Supported on all 7210 SAS platforms as described in this document
This command specifies the transmission interval of AIS messages.
Specifies the transmission interval of AIS messages, in seconds.
priority priority-value
no priority
config>service>epipe>sap>eth-cfm>ais-enable
Supported on all 7210 SAS platforms as described in this document
This command specifies the priority of AIS messages originated by the node.
Specifies the priority value of the AIS messages originated by the node.
[no] ccm-enable
config>service>epipe>sap>eth-cfm>mep
Supported on all 7210 SAS platforms as described in this document
This command enables the generation of CCM messages.
The no form of this command disables the generation of CCM messages.
ccm-ltm-priority priority
no ccm-ltm-priority
config>service>epipe>sap>eth-cfm>mep
Supported on all 7210 SAS platforms as described in this document
This command specifies the priority value for CCMs and LTMs transmitted by the MEP.
The no form of this command removes the priority value from the configuration.
The highest priority on the bridge-port.
Specifies the priority of CCM and LTM messages.
defect-oper-group name
no defect-oper-group
config>service>epipe>sap>eth-cfm>mep
Supported on all 7210 SAS platforms as described in this document, except 7210 SAS-D
This command configures an operational group for fault propagation.
Refer to the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C OAM and Diagnostics Guide for more information about fault propagation in an Epipe service.
The no form of this command removes the operational group.
Specifies the operational group name, up to 32 characters.
[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 or an ATM port. This command provides an end-to-end OAM fault notification for Ethernet VLL service. It brings down the Ethernet port (Ethernet LLF) toward the attached CE 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 T-LDP status bits. It ceases when the fault disappears.
The Ethernet port must be configured for null encapsulation.
[no] ignore-oper-down
config>service>epipe>sap
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command configures the optional command for 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
[no] send-ais-on-port-down
config>service>epipe>sap>eth-cfm>mep>ais-enable
config>service>vpls>sap>eth-cfm>mep>ais-enable
Supported on all 7210 SAS platforms as described in this document
This command specifies that ETH-AIS should be generated for client MEPs immediately when port down event is detected on the port where the server MEP (and the associated SAP) resides. By default, the system generates an ETH-AIS message, if enabled, when CCM messages are not received within the configured time period. On a subsequent port up event, the AIS messages continue to be sent until valid CCMs are received. If there are no remote MEPs configured for the MEP, on a subsequent port up event, the AIS messages are not sent.
The no form of this command reverts to the default value.
no send-ais-on-port-down
[no] eth-test-enable
config>service>epipe>sap>eth-cfm>mep
Supported on all 7210 SAS platforms as described in this document
This command enables the Ethernet test functionality on MEP. For ETH-test to work, users must configure ETH-test parameters on both sender and receiver nodes. The ETH-test can then be performed using the following OAM commands:
oam eth-cfm eth-test mac-address mep mep-id domain md-index association ma-index [priority priority] [data-length data-length]
A check is performed for both the provisioning and test to ensure that the MEP is an Y.1731 MEP (MEP provisioned with domain format none, association format icc-based.) If not, the operation fails. An error message in the CLI and SNMP indicates the problem.
test-pattern {all-zeros | all-ones} [crc-enable]
no test-pattern
config>service>epipe>sap>eth-cfm>mep>eth-test-enable
Supported on all 7210 SAS platforms as described in this document
This command configures the test pattern for eth-test frames.
The no form of this command removes the values from the configuration.
Keyword that specifies to use all zeros in the test pattern.
Keyword that specifies to use all ones in the test pattern.
Keyword that generates a CRC checksum.
bit-error-threshold errors
no bit-error-threshold
config>service>epipe>sap>eth-cfm>mep>eth-test-enable
Supported on all 7210 SAS platforms as described in this document
This command is used to specify the threshold value of bit errors.
one-way-delay-threshold seconds
config>service>epipe>sap>eth-cfm>mep
Supported on all 7210 SAS platforms as described in this document
This command enables eth-test functionality on MEP.
Specifies the one-way delay threshold in seconds.
[no] mac-swap-enable
config>service>epipe>sap config>service>vpls>sap
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command configures that the source and destination MAC address for all the packets to be sent out of the SAP is swapped, then the packets are looped back to ingress of the SAP. SAP loopback is typically used with Y.1564 testhead functionality to loop back packets received on the end that is acting as a reflector, looping back packets received from the testhead generator.
This command is available for testing VLL services and VPLS services only. When enabled, no packets egress the service SAP, and packets received on ingress are not processed.
Before enabling this command, turn off all Layer 2 and IP control protocols (such as LACP, EFM, 802.1x and so on) on the device and its peer to prevent errors such as protocol flaps because of timeout and so on.
When SAP loopback with MAC-swap is enabled for broadcast and multicast packets (that is, packets received with multicast or broadcast destination address), the source MAC address is used as the destination MAC address and the system MAC address is the source MAC address.
The user can enable MAC swap on multiple SAPs in the same service. The user can also configure static MAC on SAPs and traffic to prevent running into the MAC move, relearning issues and unpredictable device behavior.
no mac-swap-enable
mip [mac mac-address]
mip default-mac
no mip
config>service>epipe>sap>eth-cfm
config>service>epipe>spoke-sdp>eth-cfm (supported on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C only)
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command allows 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.
Specifies the MAC address of the MIP.
Using the no command deletes the MIP. If the operator needs to change the mac back to the default mac without having to delete the MIP and reconfiguring this command is useful.
fault-propagation-enable {use-if-tlv | suspend-ccm}
no fault-propagation-enable
config>service>epipe>sap>eth-cfm>mep
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command configures the fault propagation for the MEP.
Specifies to use the interface TLV.
Specifies to suspend the continuity check messages.