5 2 Services EPipe

Section 5 Module 2 Page 1
All Rights Reserved 2010, Alcatel-Lucent

Do not delete this graphic elements in here:
All Rights Reserved Alcatel-Lucent 2010
Service Router Operating System (SROS)
Module 2
ePipe
Section 5
Services
Services ePipe 5 2 2
Objectives
Upon successful completion of this module, the student will
understand:
Characteristics of an ePipe service
Steps in configuring an ePipe service
ePipe service management tasks
OAM tools SDP-Ping, SDP-MTU, VCCV Ping and Service Ping

ePipe Service
An ePipe service provides a point to
point connection between two nodes.
Also referred to as a Virtual Leased Line
(VLL) service
From the customers perspective it
operates as a leased line between the
two locations.
The Service provider can apply billing,
ingress/egress shaping and policing
No MAC learning required
PE A
PE C
PE B
IP / MPLS
Network
ePipe Service
Characteristics
Point-to-point Ethernet service
Provides same functionality as a private line/leased line service
Transparent to higher layer traffic
Customer data is encapsulated and transported over across an IP/MPLS network
Does not perform any MAC learning
Troubleshooting aids such as Service Ping and VCCV Ping, aid in reducing the complexity of
setting up and maintaining the service
Creating an ePipe Service
Service-id: ePipe
Customer (subscriber) Association
Service Access Point Select node and port
Select Accounting Policy (optional)
Select Ingress/Egress QOS Policies (optional)
Select scheduler policy (optional)
Select Filter policies (optional)
Service Distribution Path Binds a service to an SDP
CORE
Service-id
SAP
SAP
PE-A
PE-B
Customer
access
ports
Customer
access
ports SDP
SDP
Service-id
D
D
Before any services are provisioned, the following tasks should be completed:
Build the IP (GRE) or IP/MPLS core network.
Configure routing protocols.
Configure MPLS LSPs (if MPLS is used).
Construct the core SDP service tunnel.
Create customer accounts
Create template QoS, scheduler, and accounting policies
Create SDPs
Service-specific Tasks Include:
Creating the service
Configure interfaces and SAPs; apply optional QoS, filter, accounting, and scheduler policies
Bind SDP to the service
SAPs and Spoke-SDPs
SAP
SDP
Flooded traffic received on SAPs and spoke SDPs:
Replicated on all other ports within the service (spoke-SDPs and SAPs)
Not replicated on the port it was received on
SAP
ePipe 200
SDP
ePipe 200
SAP Floods to everybody
Spoke SDP Floods to everybody
Flooded traffic received on:
SAP Flooded traffic received on a SAP is replicated to other SAPs, Spoke SDPs, and Mesh SDPs
Spoke-SDP Flooded traffic received on a Spoke SDP is replicated to other SAPs, Spoke SDPs, and
Mesh SDPs
SAP Encapsulations for EPipe Services
FR SONET / SDH FR
ATM SONET / SDH TDM
BCP-Dot1Q SONET / SDH TDM
BCP-Null SONET / SDH
IPCP SONET / SDH
QinQ Ethernet
Dot1Q Ethernet
NULL Ethernet
Encapsulation Port Type
Null Supports a single service on the port. For example, a single customer edge device attached to
the port
Dot1q Supports multiple services on the port. For example, a customer edge device running Virtual
LANs
QinQ Supports tags within tags
IPCP Internet Protocol Control Protocol is typically used for interconnection using point-to-point
protocol (PPP)
Bridging Control Protocol (BCP-null) is typically used for bridging a single service between two devices
using PPP over SONET/SDH with an encap ID of 0
Bridging Control Protocol (BCP-dot1q) supports multiple services on the SONET/SDH port/channel
ePipe Configuration
Create a customer:
conf i gur e ser vi ce cust omer 100 cr eat e
config>service>cust$
[ no] cont act - Conf i gur e cont act I nf or mat i on
[ no] descr i pt i on - Descr i pt i on f or t hi s cust omer
[ no] mul t i - ser vi ce- * + Conf i gur e a mul t i - ser vi ce si t e f or
t hi s cust omer
[ no] phone - Phone number s f or t he cont act

ePipe Configuration
Creating an ePipe Service:
config>service# epi pe 5500 cust omer 100 cr eat e
config>service>epipe$ descr i pt i on epi pe ser vi ce
config>service>epipe# no shut down
Applying Ingress and Egress SAP Parameters:
Node>config>service# epi pe 5500
config>service>epipe# sap 2/ 1/ 3: 0
config>service>epipe>sap# i ngr ess
config>service>epipe>sap>ingress# qos 555
config>service>epipe>sap>ingress# f i l t er i p 1
config>service>epipe>sap>ingress# exi t
config>service>epipe>sap# egr ess
config>service>epipe>sap>egress# qos 627
config>service>epipe>sap>egress# schedul er - pol i cy al pha
config>service>epipe>sap>egress# exi t
config>service>epipe>sap#

ePipe SDP Bindings
config>service# epi pe 5500
config>service>epipe# spoke- sdp 2: 5500 cr eat e
config>service>epipe>spoke-sdp$ no shut down
config>service>epipe>spoke-sdp$ exi t
config>service>epipe# exi t al l
After you have created an SDP
Service ID
User-assigned
SDP Number
VC ID

Switch to notes view!
ePipe Service Management
Modifying
Display the information for the service and select the parameter that you want to modify.
Deleting
Perform the following steps prior to deleting an Epipe service:
1. Shut down the SAP.
2. Delete the SAP.
3. Shut down the SDP.
4. Delete the SDP.
5. Shut down the service.
Example:
config>service>epipe# sap 2/ 1/ 3: 21
config>service>epipe>sap# shut down
config>service>epipe>sap# exi t
config>service>epipe# no sap 2/ 1/ 3: 21
config>service>epipe# spoke- sdp 2: 6000
config>service>epipe>spoke-sdp# shut down
config>service>epipe>spoke-sdp# exi t
config>service>epipe# no spoke- sdp 2: 6000
config>service>epipe# shut down
config>service>epipe# exi t
config>service# no epi pe 2
Disabling the Service
You can shut down an ePipe service without deleting the service parameters.
Example:
config>service>epipe# shut down
Re-enabling the Service
Example:
ePipe Service Management
You can perform the following ePipe management tasks:
Modify the ePipe service
Delete the ePipe service
Disable and re-enable the service

SDP Diagnostics SDP-Ping
SDP-Ping
Tests for uni-directional or round trip connectivity
Performs SDP MTU path tests
Configurable parameters:
Message size (default is 40 bytes)
Timeout (default is 5 seconds)
Interval (default is 1 second)
Number of messages to send (default is 1)
Originating SDP ID
Responding SDP ID (optional)
Forwarding class and in/out-of-profile of the OAM message
SDP Ping performs in-band uni-directional or round-trip connectivity tests on SDPs. The SDP Ping OAM
packets follow the same path as traffic within the service. The SDP Ping response can be received out-
of-band in the control plane, or in-band using the data plane for a round-trip test.
A unidirectional SDP Ping tests:
Egress SDP ID encapsulation
Ability to reach the far-end IP address of the SDP ID within the SDP encapsulation
Path MTU to the far-end IP address over the SDP ID
Forwarding class mapping between the near-end SDP ID encapsulation and the far-end
tunnel termination
A round-trip SDP Ping specifies a local egress SDP ID and an expected remote SDP ID. SDP round trip
testing is an extension of SDP connectivity testing with the additional ability to test:
Remote SDP ID encapsulation
Potential service round trip time
Round trip path MTU
Round trip forwarding class mapping
SDP-Ping
sdp-ping
Originating SDP Responding SDP Interval Timeout Count Size
Size Increment Step
MTU
discovery test
PE-A
PE-B
SDP
SDP D
E
M
U
X
D
E
M
U
X
CPU
Originating
Bidirectional - Responding
SDP Provided
CPU
Unidirectional - Responding SDP
not provided
QOS Test
Forwarding Class Profile
or
Originating SDP ID
The SDP-ID to be used by SDP-Ping. The far-end address of the specified SDP-ID is the expected
responder-id within each reply received. The specified SDP-ID defines the encapsulation of the SDP
tunnel encapsulation used to reach the far end, IP/GRE or MPLS.
Responding SDP ID
Optional parameter is used to specify the return SDP-ID to be used by the far-end for the message reply
for round trip SDP connectivity testing.
Forwarding Class Name
The forwarding class of the SDP encapsulation. The state can be specified as in or out-of-profile.
Timeout
The amount of time that the device will wait for a message reply after sending a message request.
Interval
Defines the minimum amount of time that must expire before the next message request is sent.
Size
OAM message size in octets.
Count
The number of messages to send. Each message request must either timeout or receive a reply before
the next message request is sent. The message interval value must be expired before the next message
request is sent.
Note: terminate an SDP-Ping test from the CLI use the Ctrl-C keyboard combination.
SDP-MTU
Network devices are required to support a variety of packet sizes transmitted across their interfaces.
This capability is referred to as the Maximum Transmission Unit (MTU) of the interface. It is important to
consider the MTU of the entire path end-to-end when provisioning services to ensure that the service is
able to transmit the largest customer packet.
The SDP-MTU discovery tool provides a means of determining the exact MTU supported between service
ingress and service termination points (accurate to one byte).
Parameters
Originating SDP ID
Originating SDP ID.
Size Increment
Specifies the start and end size, in octets, of the OAM packets. The range is 40 9198.
Step Size
Specifies the number of octets to increment the message size request for each message sent. The
default is 32, range 1 512.
Timeout
The amount of time, in seconds, that the device waits for a message reply after sending a message
request. Default is 5, range 1 10.
Interval
The default request message send interval defines the minimum amount of time, in seconds, that must
expire before the next message request is sent. Default is 1, range is 1 10.
SDP Diagnostics SDP-MTU
SDP-MTU
Performs MTU path tests on an SDP to determine the largest path-
mtu supported by the SDP.
Configurable parameters:
Originating SDP ID
Size increment (start and end size)
Step
Timeout
Interval
Sample SDP-MTU test output:

SR# sdp- mt u 6 si ze- i nc 512 3072 st ep 256
Si ze Sent Response
- - - - - - - - - - - - - - - - - - - - - - - - - - -
512 . Success
768 . Success
1024 . Success
1280 . Success
1536 . Success
1792 . Success
2048 . Success
2304 Request Ti meout
Maxi mumResponse Si ze: 2048
Note: terminate an SDP-MTU test from the CLI use the Ctrl-C keyboard combination.
Service Ping (SVC-Ping)
The service ping tools tests a service ID for correct and consistent provisioning between two service end
points. The following information can be determined from svc-ping:
Local and remote service existence
Local and remote service state
Local and remote service type correlation
Local and remote customer association
Local and remote service-to-SDP bindings and state
Local and remote ingress and egress VC label association
Unlike SDP-Ping, only a single message will be sent per command; no count or interval parameter is
supported and round trip time is not calculated. A timeout value of 10 seconds is used before failing the
request. The forwarding class is assumed to be Best-Effort Out-of-Profile
Service Ping (Svc-Ping)
svc-ping Target node Service
local sdp remote sdp
Uses the configured
outbound SDP encapsulation and
label.
Try to limit the number of concurrent service tests.
Different services could be using the same SDPs.
SDP-Ping may be more effective test.
Uses the configured
remote SDP
encapsulation and label.
If not specified, GRE encapsulation packet
with OAM label used.
Service-id
SAP
PE-A
PE-B
Customer
access
ports SDP
SDP D
E
M
U
X
D
E
M
U
X
SVC
VC Label A
VC Label B
SVC
Customer
access
ports
No remote
SDP supplied
No local
SDP supplied
SAP
Service-id
Parameters
Far-End IP Address
The far end IP address that the service ping packet will be sent to.
DNS-Name
The Domain Name Server (DNS) name of the far end device that the service ping packet will be sent to.
Service-ID
The service ID of the service being tested.
Local-SDP
Specifies that the SVC-Ping request message should be sent using the same service tunnel
encapsulation labeling as service traffic; IP/GRE or MPLS. If the local-SDP parameter is not used, the
SVC-Ping message is sent using GRE encapsulation with an OAM label.
Remote-SDP
Specifies that the SVC-Ping reply message from the far-end should be sent using the same service tunnel
encapsulation labeling as service traffic. If the remote-SDP parameter is not used, the SVC-Ping reply
message is sent using GRE encapsulation with an OAM label.
VCCV OAM
VCCV-Ping
Used to check VLL connectivity
Verify that the destination PE is the egress for the L2 FEC
Works in-band
message is sent using the same encapsulation and along the same
path as user packets in that VLL
Equivalent of LSP-Ping for a VLL service
Virtual Circuit Connectivity Verification (VCCV)

VCCV-Ping is used to check connectivity of a VLL. Its intent is to check that the destination (target) PE is
the egress for the L2 FEC. It is in-band, meaning that the VCCV-Ping message is sent using the same
encapsulation and along the same path as user packets in that VLL. This feature is the equivalent of
LSP-Ping for a VLL service. In fact, VCCV-Ping reuses an LSP-Ping message format and can be used to
test a VLL configured over both an MPLS and a GRE SDP.
VCCV OAM (ctd)
Lab 6
VCCV-Ping application
VCCV effectively creates an IP control channel within the PW between PE1 and PE2. Following the
diagram above, an MPLS echo request message is sent with a destination address of PE2. The MPLS echo
request is encapsulated inside a PW packet and is forwarded to PE2. PE2 replies with a MPLS echo reply
packet. Unlike LSP-Ping, the reply is sent over the PW by default. The request may be sent over the IGP
path as an option.
VCCV messages can be encapsulated using the Router Alert Label control channel.
The supported reply modes include
Reply via IPv4/IPv6 UDP packet
Reply via application level control channel, in-band over the PW
Questions
1. An ePipe service on the 7750 SR is also known as what a ________ service.
a.VPLS
b.VLL
c.VPRN
d.Leased Line
2. An ePipe service performs MAC learning.
a.True
b.False
3. SAPs can be configured on access ports only.
a.True
b.False
This page left blank intentionally
Answers
1. An ePipe service on the 7750 SR is also known as what a ________ service.
a.VPLS
b.VLL
c.VPRN
d.Leased Line
2. An ePipe service performs MAC learning.
a.True
b.False
3. SAPs can be configured on access ports only.
a.True
b.False
This page left blank intentionally
End of Module
Services ePipe

5 2 Services EPipe

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

5 2 Services EPipe

Caricato da

Copyright:

Formati disponibili

Section 5 Module 2 Page 1

All Rights Reserved 2010, Alcatel-Lucent

Section 5 Module 2 Page 3

Sample SDP-MTU test output:

Virtual Circuit Connectivity Verification (VCCV)

Potrebbero piacerti anche