Pseudowire
Pseudowire tests L2 services over MPLS. It can emulate an Ethernet pseudowire to one or more remote PEs and verify label negotiation, MTU, the control word, and PW status.
Table 213 — Pseudowire Parameters
| Name | Description | Value |
|---|---|---|
| Instance ID | Pseudowire set identifier | Specify a unique number |
| PW type | Pseudowire type | Usually ethernet |
| Control word | Use of a control word | Enable if required by the service |
| MTU | Pseudowire MTU | 1500 by default |
| PW status TLV | Advertise PW status | Enable to test status scenarios |
| LDP instance ID | LDP instance used for signaling | Must reference an existing LDP instance |
| Local label base | Base local label | 5000 by default |
| PW templates | Templates for generated pseudowires | Add the remote PE, PW ID, and count |
Table 214 — Pseudowire Template
| Name | Description | Value |
|---|---|---|
| PW ID start | First PW ID | 1 by default |
| Count | Number of pseudowires | Specify the number of services |
| Remote PE | Remote PE address | Specify the peer with which the PW is negotiated |
| Remote PE iter | Remote-PE increment | Used for bulk generation |
| Group ID | Group identifier | 0 means no separate grouping |
| Transport | Signaling transport | Usually ldp |
| RSVP tunnel ID | RSVP tunnel ID | Set when RSVP transport is used |
If the pseudowire does not come up, check the LDP session and compare the PW ID, MTU, control word, and labels at both ends.