Nokia 7330 - Configure Epipe Service MTU Attribute; Configuring Epipe SAP Parameters

FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Leased Line Services
Issue: 13 3HH-11985-AAAA-TQZZA 113
[cbs cbs-size] [pbs pbs-size]
no rate-limit
egress-network
qos policy-id
no qos
ingress
qos policy-id
no qos
ingress-network
qos policy-id
no qos
sgt-qos policy-id
no sgt-qos
4.4.2.2 Configure Epipe Service MTU Attribute
Use the following CLI syntax to configure the MTU for the Epipe service.
configure>service# epipe service-id [customer customer-id]
service-mtu octets
no service-mtu
4.4.2.3 Configuring Epipe SAP Parameters
Filter policies are configured in the configure>filter context and explicitly applied to
a SAP. There are no default filter policies.
Use the following CLI syntax to create Distributed Epipe SAPs
configure>service# epipe service-id [customer customer-id]
sap sap-id
description description-string
no shutdown
egress
filter {ip ip-filter-name|mac mac-filter-name}
ingress
filter {ip ip-filter-name|mac mac-filter-name}
Distributed Epipe SAPs
To configure a distributed Epipe service, you must configure service entities on the
originating and far-end nodes. You must use the same service ID on both ends (for
example, Epipe 5500 on ALA-1 and Epipe 5500 on ALA-2). The spoke-sdp
sdp-id:vc-id must match on both sides. A distributed Epipe consists of two SAPs on
different nodes.
Ingress and egress SAP parameters can be applied to the distributed Epipe service
SAPs.
For SDP configuration information, see “Configuring SDPs”. For SDP binding
information, see “Configuring SDP Bindings”.