netbox/docs/models/vpn/l2vpn.md

# L2VPN

A L2VPN object is NetBox is a representation of a layer 2 bridge technology such as VXLAN, VPLS, or EPL. Each L2VPN can be identified by name as well as by an optional unique identifier (VNI would be an example). Once created, L2VPNs can be terminated to [interfaces](../dcim/interface.md) and [VLANs](../ipam/vlan.md).

## Fields

### Name

A unique human-friendly name.

### Slug

A unique URL-friendly identifier. (This value can be used for filtering.)

### Type

The technology employed in forming and operating the L2VPN. Choices include:

* VPLS
* VPWS
* EPL
* EVPL
* EP-LAN
* EVP-LAN
* EP-TREE
* EVP-TREE
* VXLAN
* VXLAN-EVPN
* MPLS-EVPN
* PBB-EVPN
* EVPN-VPWS

!!! note
    Designating the type as VPWS, EPL, EP-LAN, EP-TREE will limit the L2VPN instance to two terminations.

### Status

The operational status of the L2VPN. By default, the following statuses are available:

* Active (default)
* Planned
* Faulty

!!! tip "Custom L2VPN statuses"
    Additional L2VPN statuses may be defined by setting `L2VPN.status` under the [`FIELD_CHOICES`](../../configuration/data-validation.md#field_choices) configuration parameter.

### Identifier

An optional numeric identifier. This can be used to track a pseudowire ID, for example.

### Import & Export Targets

The [route targets](../ipam/routetarget.md) associated with this L2VPN to control the import and export of forwarding information.
Add docs 2022-06-30 08:29:08 -05:00			`# L2VPN`

#14311: Update model documentation 2023-12-04 09:29:43 -05:00			`A L2VPN object is NetBox is a representation of a layer 2 bridge technology such as VXLAN, VPLS, or EPL. Each L2VPN can be identified by name as well as by an optional unique identifier (VNI would be an example). Once created, L2VPNs can be terminated to [interfaces](../dcim/interface.md) and [VLANs](../ipam/vlan.md).`
Add docs 2022-06-30 08:29:08 -05:00
Update IPAM models documentation 2022-08-16 15:32:00 -04:00			`## Fields`

			`### Name`

			`A unique human-friendly name.`

			`### Slug`

			`A unique URL-friendly identifier. (This value can be used for filtering.)`

			`### Type`

			`The technology employed in forming and operating the L2VPN. Choices include:`
Add docs 2022-06-30 08:29:08 -05:00
			`* VPLS`
			`* VPWS`
			`* EPL`
			`* EVPL`
			`* EP-LAN`
			`* EVP-LAN`
			`* EP-TREE`
			`* EVP-TREE`
			`* VXLAN`
Update IPAM models documentation 2022-08-16 15:32:00 -04:00			`* VXLAN-EVPN`
Add docs 2022-06-30 08:29:08 -05:00			`* MPLS-EVPN`
			`* PBB-EVPN`
Add EVPN-VPWS to L2VPNTypeChoices (#17694) * Add EVPN-VPWS to the availbable L2VPN Connection Types * Updated documentation to reference the new L2VPN type. 2024-10-10 00:28:53 +10:00			`* EVPN-VPWS`
Add docs 2022-06-30 08:29:08 -05:00
Misc cleanup 2022-07-12 12:30:07 -04:00			`!!! note`
Update IPAM models documentation 2022-08-16 15:32:00 -04:00			`Designating the type as VPWS, EPL, EP-LAN, EP-TREE will limit the L2VPN instance to two terminations.`

Closes #17608: Adds L2VPN.status field (#18791) 2025-03-06 16:06:06 -06:00			`### Status`

			`The operational status of the L2VPN. By default, the following statuses are available:`

			`* Active (default)`
			`* Planned`
			`* Faulty`

			`!!! tip "Custom L2VPN statuses"`
			Additional L2VPN statuses may be defined by setting `L2VPN.status` under the [`FIELD_CHOICES`](../../configuration/data-validation.md#field_choices) configuration parameter.

Update IPAM models documentation 2022-08-16 15:32:00 -04:00			`### Identifier`

Closes #10032: Remove unique constraint from L2VPN identifier 2022-08-17 10:47:42 -04:00			`An optional numeric identifier. This can be used to track a pseudowire ID, for example.`
Update IPAM models documentation 2022-08-16 15:32:00 -04:00
			`### Import & Export Targets`

#14311: Update model documentation 2023-12-04 09:29:43 -05:00			`The [route targets](../ipam/routetarget.md) associated with this L2VPN to control the import and export of forwarding information.`