epipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-switching] [svc-sap-type {any | qinq-inner-tag-preserve}]
no epipe service-id
config>service
Supported on all 7210 SAS platforms as described in this document
This command configures a point-to-point Epipe service instance. An Epipe connects two endpoints, defined as Service Access Points (SAPs). In a local service, the SAPs can be defined in one 7210 SAS node, and in a distributed service, the SAPs can be defined on two different 7210 SAS nodes.
7210 SAS platforms as described in this document support local SAP-to-SAP service.
7210 SAS platforms as described in this document support both local and distributed services.
MAC learning and filtering are not supported on an Epipe service.
When a service is created, the customer keyword and customer-id parameter must be specified to associate the service with a customer. The customer-idmust already exist, having been created using the customer command in the service context. When a service has been created with a customer association, it is not possible to edit the customer association. The service must be deleted and recreated with a new customer association.
When a service is created, the use of the customer customer-id command is optional for navigating into the service configuration context. Edit a service with the incorrect customer-id value specified results in an error.
By default, no Epipe services exist until they are explicitly created with this command.
The no form of this command deletes the Epipe service instance with the specified service-id. The service cannot be deleted until the service has been shut down and all instances of SAPs, mesh SDPs, or spoke SDPs have been deleted from the service.
Specifies the unique service identification number or string identifying the service in the service domain. This ID must be unique to this service and may not be used for any other service of any type. The service-id must be the same number used for every 7210 SAS on which this service is defined.
Specifies the customer ID number to be associated with the service. This parameter is required on service creation and is optional for service editing or deletion.
Specifies the VPN ID number, which allows you to identify virtual private networks (VPNs). If this parameter is not specified, the VPN ID uses the same number as the service ID.
Specifies whether pseudowire switching signaling is used for the spoke-SDPs configured in the service.
Specifies the type of service and allowed SAPs in the service.
Keyword used to create the service instance. The create keyword requirement can be enabled or disabled in the environment>create context.
[no] endpoint endpoint-name [create]
config>service>epipe
Supported on all 7210 SAS platforms as described in this document
This command configures a service endpoint.
Specifies an endpoint name.
Mandatory keyword to create a service endpoint name.
active-hold-delay active-hold-delay
no active-hold-delay
config>service>epipe>endpoint
Supported on all 7210 SAS platforms as described in this document
This command specifies that the node delays sending the change in the T-LDP status bits for the VLL endpoint when the MC-LAG transitions the LAG subgroup that hosts the SAP for this VLL endpoint from active to standby or when any object in the endpoint. For example, SAP, ICB, or regular spoke-SDP, transitions from up to down operational state.
By default, when the MC-LAG transitioned the LAG subgroup that hosts the SAP for this VLL endpoint from active to standby, the node immediately sends new T-LDP status bits indicating the new value of "standby" over the spoke SDPs that are on the mate-endpoint of the VLL. The same applies when an object in the endpoint changes an operational state from up to down.
A value of zero means that when the MC-LAG transitioned the LAG subgroup which hosts the SAP for this VLL endpoint from active to standby, the node sends immediately new T-LDP status bits indicating the new value of standby over the spoke SDPs which are on the mate-endpoint of the VLL. The same applies when any object in the endpoint changes an operational state from up to down.
There is no delay applied to the VLL endpoint status bit advertisement when the MC-LAG transitions the LAG subgroup that hosts the SAP from "standby" to "active" or when an object in the endpoint transitions to an operationally up state.
0
Specifies the active hold delay in 100s of milliseconds.
revert-time [revert-time | infinite]
no revert-time
config>service>epipe>endpoint
Supported on all 7210 SAS platforms as described in this document
This command configures the time to wait before reverting back to the primary spoke-SDP defined on this service endpoint, after having failed over to a backup spoke-SDP.
Specifies the time, in seconds, to wait before reverting to the primary SDP.
Keyword that causes the endpoint to be non-revertive.
[no] standby-signaling-master
config>service>vll>endpoint
Supported on all 7210 SAS platforms as described in this document
When this command is enabled, the pseudowire standby bit (value 0x00000020) is sent to T-LDP peer for each spoke SDP of the endpoint that is selected as a standby.
This command cannot be used with a VLL mate SAP created on an MC-LAG or ICB. This command and the vc-switching parameter are mutually exclusive.
no standby-signaling-master
service-mtu octets
no service-mtu
config>service>epipe
Supported on all 7210 SAS platforms as described in this document
This command configures the service payload (Maximum Transmission Unit – MTU), in bytes, for the service. This MTU value overrides the service-type default MTU. The service MTU defines the payload capabilities of the service. It is used by the system to validate the SAP and the SDP binding operational state within the service.
The service MTU and a SAP service delineation encapsulation overhead (that is, 4 bytes for a dot1q tag) is used to derive the required MTU of the physical port or channel on which the SAP was created. If the required payload is larger than the port or channel MTU, the SAP is placed in an inoperative state. If the required MTU is equal to or less than the port or channel MTU, the SAP can transition to the operative state.
If a service MTU, port or channel MTU, or path MTU is dynamically or administratively modified, all associated SAP and SDP binding operational states are automatically reevaluated.
To disable service MTU check, execute the command no service-mtu-check. Disabling service MTU check allows the packets to pass to the egress if the packet length is less than or equal to the MTU configured on the port.
The no form of this command reverts to the default value.
VPLS: 1514
Specifies the size of the MTU in octets, expressed as a decimal integer. The following table lists MTU values for specific VC types.
| VC-type | Example service MTU | Advertised MTU |
|---|---|---|
Ethernet |
1514 |
1500 |
Ethernet (with preserved dot1q) |
1518 |
1504 |
VPLS |
1514 |
1500 |
VPLS (with preserved dot1q) |
1518 |
1504 |
VLAN (dot1p transparent to MTU value) |
1514 |
1500 |
VLAN (QinQ with preserved bottom Qtag) |
1518 |
1504 |
[no] service-mtu-check
config>service>epipe
Supported on all 7210 SAS platforms as described in this document
Disabling service MTU check allows the packets to pass to the egress if the packet length is less than or equal to the MTU configured on the port. The length of the packet sent from a SAP is limited only by the access port MTU. In case of a pseudowire, the length of a packet is limited by the network port MTU (including the MPLS encapsulation).
The no form of this command disables the service MTU check.
If TLDP is used for signaling, the configured value for service-mtu is used during pseudowire set up.
enabled