Manual VPWS
Load basic.vpws.init.cfg
Create a VPWS between CE1 and CE8. Do not use a tLDP session between R1 and R6.
Answer
Explanation
Usually tLDP is used with VPWS. tLDP gives us a dynamic way to signal the service label, MTU, control word, and interface status. However, we can manually specify these values instead of using tLDP. When we do this, we lose the dynamic ability to advertise that the AC is down to the other end, so this is usually not done. But it helps your understanding of how VPWS works by doing this exercise.
To create a manual PW, we first must define a static label range. This is needed to statically allocate a local service label for the VPWS.
Next we create the explicit pseudowire interface, specify that the signaling protocol is none instead of the default (LDP), specify the neighbor and the local/remote service labels. Remember, LDP is not going to signal this, so we must manually specify it on each end.
Lastly, we associate the pseudowire with the xconnect.
Verification
Verification in general is the same as with tLDP pseudowires. However we have lost the ability to signal the status, MTU, etc. of the VPWS service.
On R1 shutdown Gi3 and notice that the VC is still up on R6.
Also notice the static label that has been assigned to the PW on each PE.
Last updated
