epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {any | qinq-inner-tag-preserve}] [customer-vid vlan-id] [pbb-epipe]
no epipe service-id
config>service
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
This command configures an Epipe service instance. This command is used to configure a point-to-point Epipe service. An Epipe connects two endpoints defined as Service Access Points (SAPs). In a local service, the SAPs may be defined in one 7210 SAS node and in distributed service the SAPs may be defined on two different 7210 SAS nodes.
On 7210 SAS, platforms operating in network mode, both local and distributed services are supported.
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-id value must 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. Editing a service with the incorrect customer-id value specified results in an error.
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, or spokes have been deleted from the service.
No Epipe services exist until they are explicitly created with this command.
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 optional for service editing or deleting.
Specifies the VPN ID number which allows you to identify virtual private networks (VPNs) by a VPN ID. If this parameter is not specified, the VPN ID uses the same service ID number.
Specifies the service type and the allowed SAPs in the service. When the pbb-epipe keyword is not configured, a plain Epipe service can be configured with SAPs and SDPs.
Keyword used to create the service instance. The create keyword requirement can be enabled or disabled in the environment>create context.
Specifies a PBB Epipe service, which allows the software to allocate the appropriate resources for PBB Epipe. Only SAPs can be configured with a PBB Epipe service.
PBB and the pbb-epipe keyword are supported only on 7210 SAS-T operating in the network mode.
epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {null-star | dot1q-preserve | any | dot1q-range}] [customer-vid vlan-id]
no epipe service-id
config>service
Only supported on 7210 SAS platforms configured in the access-uplink operating mode
This command configures an Epipe service instance. This command is used to configure a point-to-point Epipe service. An Epipe connects two endpoints defined as SAPs. In a local service, the SAPs may be defined in one 7210 SAS node and in distributed service the SAPs may be defined on two different 7210 SAS nodes.
Distributed services are only supported on 7210 SAS platforms operating in the network mode. 7210 SAS platforms operating in access-uplink mode only support local SAP-to-SAP service.
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-id parameter must 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. Editing a service with the incorrect customer-id value specified results in an error.
The no form of this command deletes the Epipe service instance with the specified service-id value. The service cannot be deleted until it has been shut down and all instances of SAPs have been deleted from the service.
No Epipe services exist until they are explicitly created with this command.
Specifies the unique service identification number or string identifying the service in the service domain. The ID must be unique to the service and may not be used for any other service of any type. The service-id must be the same value for every 7210 SAS device on which this service is defined.
Specifies the customer ID 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 , 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 the service type and the SAPs allowed in the service.
Specifies the dot1q VLAN ID to be used while creating the local dot1q SAP for the svc-sap-type command with the dot1q-preserve option specified.
Keyword used to create the service instance. The create keyword can be enabled or disabled in the environment>create context.
[no] endpoint endpoint-name
config>service>epipe
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures a service endpoint.
Specifies an 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, except those operating in access-uplink mode
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 which 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 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 which hosts the SAP from "standby" to "active" or when any object in the endpoint transitions to an operationally up state.
0 — 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.
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, except those operating in access-uplink mode
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.
The no form of this command resets the timer to the default value of 0.
Specify the time, in seconds, to wait before reverting to the primary SDP.
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, except those operating in access-uplink mode
This command enables the pseudowire standby bit (value 0x00000020) to be sent to T-LDP peer for each spoke SPD of the endpoint that is selected as a standby.
This command is mutually exclusive with a VLL mate SAP created on an MC-LAG or ICB. It is also mutually exclusive with vc-switching.
no standby-signaling-master
service-mtu octets
no service-mtu
config>service>epipe
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
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 SDP binding operational state within the service.
The service MTU and a SAP service delineation encapsulation overhead (i.e., 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 is able to transition to the operative state.
In the event that a service MTU, port or channel MTU, or path MTU is dynamically or administratively modified, then all associated SAP and SDP binding operational states are automatically re-evaluated.
The no form of this command returns the default service-mtu for the indicated service type to the default value.
Note: 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 lesser than or equal to the MTU configured on the port.
VPLS: 1514
The following table displays MTU values (in octets) 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 |
Specifies the size of the MTU in octets, expressed as a decimal integer.
service-name service-name
no service-name
config>service>epipe
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command configures an optional service name, up to 64 characters, which adds a name identifier to a specific service to then use that service name in configuration references as well as display and use service names in show commands throughout the system. This helps the service provider/administrator to identify and manage services within the 7210 SAS platforms.
All services are required to assign a service ID to initially create a service. However, either the service ID or the service name can be used o identify and reference a specific service when it is initially created.
Specifies a unique service name to identify the service. Service names may not begin with an integer (0-9).
[no] service-mtu-check
config>service>epipe
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
The no form of this command disables the service MTU check.
Disabling service MTU check allows the packets to pass to the egress if the packet length is lesser 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).
If TLDP is used for signaling, the configured value for service-mtu is used during a pseudowire setup.
enabled