**p 1003 1004 ; targeted ldp hello ; 1069 ; 1027 ; 1086

- GRE is typically used when there are routers in the transport network that do not
support MPLS label switching .
- the service label, is used to identify to which service a specific packet
belongs.
- vpws and vpls uses t-ldp ; vprn uses mp-bgp
- A pseudowire is an emulated, Layer 2 circuit built across an MPLS network that
can
transport Layer 2 PDUs
- targeted ldp sends hello messages in unicast.
- T-LDP is enbaled automatically but can be disabled
- normally it is specified in the far end conf of the sdp / supports md5 auth

-------------------------------------------------
*A:R1>config>router>ldp# show router ldp peer detail
*A:R1>config>router>ldp$ show router ldp status

*A:PE-1# configure service customer 111 create

*A:PE-1>config>service>cust$ description “Customer Acme”
*A:PE-1>config>service>cust$ phone “+1-212-555-1212”

*A:PE-1# configure service epipe 50

*A:PE-1>config>service>epipe# sap 1/1/1:11 create
*A:PE-1>config>service>epipe>sap$ exit

*A:PE-1# configure service epipe 50 customer 111 create

*A:PE-1>config>service>epipe$ no shutdown

*A:PE-1# show service customer

*A:PE-1>config>service>epipe$ show service id 50 base
*A:PE-1>config>service>epipe# show service service-using epipe
*A:PE-1# show service id 50 sap 1/1/1:11 detail
*A:PE-1# show service sdp detail

*A:PE-1# configure service sdp 2 mpls create

*A:PE-1>config>service>sdp$ far-end 10.10.10.2
*A:PE-1>config>service>sdp$ lsp “to_PE-2
*A:PE-1>config>service>sdp$ no shutdown

*A:PE-1# show service sdp

*A:PE-1# show service sdp 2 detail
*A:PE-1># show router ldp bindings fec-type services ( check sdp tunnel to see if
labels sharing are bidirectional )

*A:PE-1# configure service epipe 55 customer 111 create

*A:PE-1>config>service>epipe$ sap 1/1/2 create
*A:PE-1>config>service>epipe>sap$ exit
*A:PE-1>config>service>epipe# spoke-sdp 2:55 create
*A:PE-1>config>service>epipe>spoke-sdp$ exit
*A:PE-1>config>service>epipe# no shutdown

--------------------------------------------------

- A VC ID (virtual circuit identifier) identifies the pseudowire

- After the successful exchange of service labels, a pseudowire has been created
between the two PE routers.
- On the 7750 SR, a service is identified on a router by its service ID .
- Best practice is to use the service ID value for the pseudowire VC ID whenever
possible.
- The customer ID for the service cannot be changed once the service is created.
- 5620 SAM requires that the customer ID is treated with global significance
- Although it is recommended that a globally consistent value be used for the
customer ID, it is never signaled to other PEs and has no effect on the service.
- Once a value is used for one service, it cannot be used for another on that
router.
- To be used as a SAP, a port must be configured as an access port
- RSVP-TE is required for traffic engeneering and fast reroute .
- The service MTU of any service bound to the SDP cannot be larger than the path
MTU of the SDP
- The SDP ID is locally unique to the router. Other routers can use the same SDP
ID.
- There are spoke or mesh binding. Mesh bindings are only used for VPLS services.
- The SDP binding specifies both the SDP ID and the VC ID in the format spoke-sdp
sdp-id:vc-id
- three types of ethernet SAP encap : null ; dot1q ; qinq .
- q-in-q tag : sap 1/1/1:10.111 | port provider customer.
- if null encapsulation is specified for an access port and SAP, the SAP will
accept all frames received on the port whether they are untagged, dot1Q tagged, or
Q-in-Q tagged .
- If the outer tag does not match the SAP value, the frame is ignored by the
service.
- If the 7750 SR, in its default configuration receives a tagged frame with an
Ethertype value other than 0x8100, it is simply treated as an untagged frame
- there are several entities for which MTU must be considered:
• Access port, or SAP MTU
• Service and virtual circuit (VC) MTU
• SDP(Service Distribution Point) path MTU
• Network port MTU
- Layer 2 technologies do not support fragmentation
- service mtu need to match at both ends .
-------------------------------------------------
**dot1q encapsulation on single interface
*A:CE-1>config>router# interface to_CE11_2
*A:CE-1>config>router>if$ port 1/1/2:11
*A:CE-1>config>router>if$ address 192.168.11.1/24

*A:PE-1# clear service statistics sap 1/1/2:22 all

*A:PE-1# show service id 11 sap 1/1/2:11 stats
*A:PE-1>config>port# ethernet dot1q-etype 0x88a8
*A:PE-1# show router ldp bindings fec-type services

*A:PE-1# configure service epipe 11

*A:PE-1>config>service>epipe# service-mtu 1518

*A:PE-2# show service fdb-mac

-------------------------------------------------
- In a Layer 2 service, the SAP MTU must always be equal to or larger than the
service MTU.
- A tool that is useful in determining the effective path MTU of an SDP is the
command oam sdp-mtu
- the PE maintains a separate FDB for every VPLS service configured on the router
- A VC ID is not specified for the mesh SDP; it uses the service number as the VC
ID

---------------------------------------------------------
Create the VPLS and bind mesh SDPs to the service
 *A:PE-2# configure service vpls 101 customer 1 create
*A:PE-2>config>service>vpls$ mesh-sdp 3 create
*A:PE-2>config>service>vpls>mesh-sdp$ exit
*A:PE-2>config>service>vpls# mesh-sdp 6 create
*A:PE-2>config>service>vpls>mesh-sdp$ exit
*A:PE-2>config>service>vpls# show service id 101 base

*A:PE-2>config>service>vpls# show service id 101 sdp 3:101 detail

----------------------------------------------------------