Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The PE router providing MPLS Virtual Private Wire Service (VPWS) must be configured to have the appropriate virtual circuit identification (VC ID) for each attachment circuit.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-256055 | ARST-RT-000760 | SV-256055r882507_rule | High |
| Description |
|---|
| VPWS is an L2VPN technology that provides a virtual circuit between two PE routers to forward Layer 2 frames between two customer-edge routers or routers through an MPLS-enabled IP core. The ingress PE router (virtual circuit head-end) encapsulates Ethernet frames inside MPLS packets using label stacking and forwards them across the MPLS network to the egress PE router (virtual circuit tail-end). During a virtual circuit setup, the PE routers exchange VC label bindings for the specified VC ID. The VC ID specifies a pseudowire associated with an ingress and egress PE router and the customer-facing attachment circuits. To guarantee that all frames are forwarded onto the correct pseudowire and to the correct customer and attachment circuits, it is imperative that the correct VC ID is configured for each attachment circuit. |
| STIG | Date |
|---|---|
| Arista MLS EOS 4.2x Router Security Technical Implementation Guide | 2023-01-17 |
Details
| Check Text ( C-59731r882505_chk ) |
|---|
| Review the ingress and egress PE router configuration for each virtual circuit that has been provisioned. Verify the correct and unique VCID has been configured for the appropriate attachment circuit. Run the command sh run | section patch patch panel patch port connector 1 interface Ethernet2 connector 2 pseudowire bgp vpws evi-1 pseudowire pw1 patch subintf connector 1 interface Ethernet3.1 connector 2 pseudowire bgp vpws evi-1 pseudowire pw2 Run the command sh run | section router bgp router bgp 65000 neighbor 10.0.0.1 remote-as 1 neighbor 10.0.0.1 send-community extended neighbor 10.0.0.1 maximum-routes 12000 ! vpws evi-1 rd 10.2.2.2:2 route-target import export evpn 0.0.0.0:1 mpls control-word ! pseudowire pw1 evpn vpws id local 2001 remote 1001 ! pseudowire pw2 evpn vpws id local 2002 remote 1002 ! address-family evpn neighbor default encapsulation mpls next-hop-self source-interface Loopback0 neighbor 10.0.0.1 activate If the correct VC ID has not been configured on both routers, this is a finding. |
| Fix Text (F-59674r882506_fix) |
|---|
| Assign globally unique VC IDs for each virtual circuit and configure the attachment circuits with the appropriate VC ID. Configure the same VC ID on both ends of the VC. patch panel patch port connector 1 interface Ethernet2 connector 2 pseudowire bgp vpws evi-1 pseudowire pw1 patch subintf connector 1 interface Ethernet3.1 connector 2 pseudowire bgp vpws evi-1 pseudowire pw2 router bgp 65000 neighbor 10.0.0.1 remote-as 1 neighbor 10.0.0.1 send-community extended neighbor 10.0.0.1 maximum-routes 12000 ! vpws evi-1 rd 10.2.2.2:2 route-target import export evpn 0.0.0.0:1 mpls control-word ! pseudowire pw1 evpn vpws id local 2001 remote 1001 ! pseudowire pw2 evpn vpws id local 2002 remote 1002 ! address-family evpn neighbor default encapsulation mpls next-hop-self source-interface Loopback0 neighbor 10.0.0.1 activate VLAN mode example: interface Ethernet3 no routerport ! interface Ethernet3.1 encapsulation dot1q vlan 1 Flexible Encapsulation example: interface Ethernet3 no routerport ! interface Ethernet3.1 encapsulation vlan client dot1q 11 network client |