Layer 2 Virtual Network
Location in GUI:
Provision » SD-Access » Virtual Networks » Layer 2 Virtual Networks
Diagram
Section titled “Diagram”Classes
Section titled “Classes”fabric_sites (catalyst_center.fabric)
Section titled “fabric_sites (catalyst_center.fabric)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| l2_virtual_networks | List | [l2_virtual_networks] | No |
l2_virtual_networks (catalyst_center.fabric.fabric_sites)
Section titled “l2_virtual_networks (catalyst_center.fabric.fabric_sites)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Yes | ||
| vlan_name | String | No | ||
| vlan_id | Integer | min: 2, max: 4093 | No | |
| traffic_type | Choice | DATA, VOICE | No | |
| fabric_enabled_wireless | Boolean | true, false | No | |
| associated_l3_virtual_network_name | String | No |
Layer 2 Virtual Networks enable VLAN extension across the SD-Access fabric while maintaining Layer 2 adjacency for applications that require it. They are associated with a Fabric Site and a traffic type, and can be handed off to external networks via Layer 2 Handoffs on Border Devices. They can also be inherited into a Fabric Zone by listing the L2 VN name under fabric_zones[].l2_virtual_networks; the zone reuses the parent site’s vlan_id, vlan_name, traffic_type, fabric_enabled_wireless and associated_l3_virtual_network_name, so the VN definition only needs to be declared once at the site. This resource is SDA fabric only.
Examples
Section titled “Examples”Example-1: Basic Layer 2 Virtual Network for Data Traffic
This example demonstrates how to configure a basic Layer 2 virtual network within an SD-Access fabric site. Layer 2 virtual networks enable VLAN extension across the fabric while maintaining traditional Layer 2 networking semantics for applications and services that require Layer 2 adjacency.
The Layer 2 virtual network configuration includes:
- Virtual network name (L2_SDA_VN_1) for identification and policy assignment
- VLAN name (L2_VLAN_USERS) for traditional VLAN-based network segmentation
- VLAN ID (501) for 802.1Q tagging and network isolation
- Traffic type specification (DATA) for appropriate QoS and policy treatment
- Fabric-enabled wireless disabled for wired-only network segments
catalyst_center: fabric: fabric_sites: - name: Global/Canada authentication_template: name: No Authentication l2_virtual_networks: - name: L2_SDA_VN_1 vlan_name: L2_VLAN_USERS vlan_id: 501 traffic_type: DATA fabric_enabled_wireless: falseExample-2: Layer 2 Virtual Network with Wireless Integration
This example shows how to configure a Layer 2 virtual network with fabric-enabled wireless support for unified wired and wireless connectivity. This configuration enables seamless Layer 2 extension across both wired and wireless infrastructure within the SD-Access fabric.
catalyst_center: fabric: fabric_sites: - name: Global/North America/Corporate Campus authentication_template: name: Closed Authentication l2_virtual_networks: - name: CORPORATE_L2_NETWORK vlan_name: CORPORATE_USERS vlan_id: 100 traffic_type: DATA fabric_enabled_wireless: trueExample-3: Layer 2 Virtual Networks with L3 Virtual Network Association
This example demonstrates how to configure Layer 2 virtual networks associated with Layer 3 virtual networks for inter-VLAN routing within the SD-Access fabric. Associating an L2 VN with an L3 VN enables routing between Layer 2 segments while maintaining Layer 2 adjacency within each segment.
catalyst_center: fabric: fabric_sites: - name: Global/Europe/ManufacturingPlant authentication_template: name: Closed Authentication l3_virtual_networks: - CORP_VN - IOT_VN l2_virtual_networks: - name: PRODUCTION_L2_VN vlan_name: PRODUCTION_CONTROL vlan_id: 200 traffic_type: DATA fabric_enabled_wireless: false associated_l3_virtual_network_name: CORP_VN - name: IOT_L2_VN vlan_name: IOT_SENSORS vlan_id: 300 traffic_type: DATA fabric_enabled_wireless: true associated_l3_virtual_network_name: IOT_VN - name: GUEST_L2_VN vlan_name: GUEST_ACCESS vlan_id: 400 traffic_type: DATA fabric_enabled_wireless: trueExample-4: Layer 2 Virtual Network for Voice Traffic
This example shows how to configure a Layer 2 virtual network specifically optimized for voice traffic with appropriate QoS treatment and priority handling within the SD-Access fabric.
catalyst_center: fabric: fabric_sites: - name: Global/Asia Pacific/CallCenter authentication_template: name: Closed Authentication l2_virtual_networks: - name: VOICE_L2_VN vlan_name: VOICE_TRAFFIC vlan_id: 150 traffic_type: VOICE fabric_enabled_wireless: trueExample-5: Layer 2 Virtual Network for Legacy System Integration
This example shows how to configure Layer 2 virtual networks for integrating legacy systems that require specific VLAN configurations and Layer 2 adjacency within the modern SD-Access fabric infrastructure.
catalyst_center: fabric: fabric_sites: - name: Global/Europe/Legacy_Data_Center authentication_template: name: Closed Authentication l2_virtual_networks: - name: LEGACY_MAINFRAME_L2_VN vlan_name: MAINFRAME_ACCESS vlan_id: 999 traffic_type: DATA fabric_enabled_wireless: false - name: LEGACY_STORAGE_L2_VN vlan_name: STORAGE_NETWORK vlan_id: 998 traffic_type: DATA fabric_enabled_wireless: falseExample-6: Inheriting a Layer 2 Virtual Network into a Fabric Zone
This example demonstrates how to deploy an existing Layer 2 virtual network into a Fabric Zone. The L2 VN is defined once at the parent fabric site with the full attribute set, and is then referenced by name under the zone’s l2_virtual_networks list. The zone inherits the parent site’s vlan_id, vlan_name, traffic_type, fabric_enabled_wireless flag and associated_l3_virtual_network_name (the Catalyst Center API requires the vlan_id of a zone-scoped L2 VN to match the corresponding site-scoped L2 VN).
If the site L2 VN does not specify a vlan_id, Catalyst Center auto-assigns one when the site VN is created. In that case the assigned id is read back and applied to the zone automatically, so the two stay in sync without having to pin a vlan_id in the data model.
catalyst_center: fabric: fabric_sites: - name: Global/Poland/Warsaw authentication_template: name: Closed Authentication l2_virtual_networks: - name: L2_SDA_VN_1 vlan_name: L2_VLAN_USERS vlan_id: 224 traffic_type: DATA fabric_enabled_wireless: true fabric_zones: - name: Global/Poland/Warsaw/Bld_B/FLOOR_1 authentication_template: name: No Authentication l2_virtual_networks: - L2_SDA_VN_1Location in GUI:
Provision » SD-Access » Virtual Networks » Layer 2 Virtual Networks
Diagram
Section titled “Diagram”Classes
Section titled “Classes”fabric_sites (catalyst_center.fabric)
Section titled “fabric_sites (catalyst_center.fabric)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| l2_virtual_networks | List | [l2_virtual_networks] | No |
l2_virtual_networks (catalyst_center.fabric.fabric_sites)
Section titled “l2_virtual_networks (catalyst_center.fabric.fabric_sites)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Yes | ||
| vlan_name | String | No | ||
| vlan_id | Integer | min: 2, max: 4093 | No | |
| traffic_type | Choice | DATA, VOICE | No | |
| fabric_enabled_wireless | Boolean | true, false | No | |
| associated_l3_virtual_network_name | String | No |
Layer 2 Virtual Networks enable VLAN extension across the SD-Access fabric while maintaining Layer 2 adjacency for applications that require it. They are associated with a Fabric Site and a traffic type, and can be handed off to external networks via Layer 2 Handoffs on Border Devices. This resource is SDA fabric only.
Examples
Section titled “Examples”Example-1: Basic Layer 2 Virtual Network for Data Traffic
This example demonstrates how to configure a basic Layer 2 virtual network within an SD-Access fabric site. Layer 2 virtual networks enable VLAN extension across the fabric while maintaining traditional Layer 2 networking semantics for applications and services that require Layer 2 adjacency.
The Layer 2 virtual network configuration includes:
- Virtual network name (L2_SDA_VN_1) for identification and policy assignment
- VLAN name (L2_VLAN_USERS) for traditional VLAN-based network segmentation
- VLAN ID (501) for 802.1Q tagging and network isolation
- Traffic type specification (DATA) for appropriate QoS and policy treatment
- Fabric-enabled wireless disabled for wired-only network segments
catalyst_center: fabric: fabric_sites: - name: Global/Canada authentication_template: name: No Authentication l2_virtual_networks: - name: L2_SDA_VN_1 vlan_name: L2_VLAN_USERS vlan_id: 501 traffic_type: DATA fabric_enabled_wireless: falseExample-2: Layer 2 Virtual Network with Wireless Integration
This example shows how to configure a Layer 2 virtual network with fabric-enabled wireless support for unified wired and wireless connectivity. This configuration enables seamless Layer 2 extension across both wired and wireless infrastructure within the SD-Access fabric.
catalyst_center: fabric: fabric_sites: - name: Global/North America/Corporate Campus authentication_template: name: Closed Authentication l2_virtual_networks: - name: CORPORATE_L2_NETWORK vlan_name: CORPORATE_USERS vlan_id: 100 traffic_type: DATA fabric_enabled_wireless: trueExample-3: Layer 2 Virtual Networks with L3 Virtual Network Association
This example demonstrates how to configure Layer 2 virtual networks associated with Layer 3 virtual networks for inter-VLAN routing within the SD-Access fabric. Associating an L2 VN with an L3 VN enables routing between Layer 2 segments while maintaining Layer 2 adjacency within each segment.
catalyst_center: fabric: fabric_sites: - name: Global/Europe/ManufacturingPlant authentication_template: name: Closed Authentication l3_virtual_networks: - CORP_VN - IOT_VN l2_virtual_networks: - name: PRODUCTION_L2_VN vlan_name: PRODUCTION_CONTROL vlan_id: 200 traffic_type: DATA fabric_enabled_wireless: false associated_l3_virtual_network_name: CORP_VN - name: IOT_L2_VN vlan_name: IOT_SENSORS vlan_id: 300 traffic_type: DATA fabric_enabled_wireless: true associated_l3_virtual_network_name: IOT_VN - name: GUEST_L2_VN vlan_name: GUEST_ACCESS vlan_id: 400 traffic_type: DATA fabric_enabled_wireless: trueExample-4: Layer 2 Virtual Network for Voice Traffic
This example shows how to configure a Layer 2 virtual network specifically optimized for voice traffic with appropriate QoS treatment and priority handling within the SD-Access fabric.
catalyst_center: fabric: fabric_sites: - name: Global/Asia Pacific/CallCenter authentication_template: name: Closed Authentication l2_virtual_networks: - name: VOICE_L2_VN vlan_name: VOICE_TRAFFIC vlan_id: 150 traffic_type: VOICE fabric_enabled_wireless: trueExample-5: Layer 2 Virtual Network for Legacy System Integration
This example shows how to configure Layer 2 virtual networks for integrating legacy systems that require specific VLAN configurations and Layer 2 adjacency within the modern SD-Access fabric infrastructure.
catalyst_center: fabric: fabric_sites: - name: Global/Europe/Legacy_Data_Center authentication_template: name: Closed Authentication l2_virtual_networks: - name: LEGACY_MAINFRAME_L2_VN vlan_name: MAINFRAME_ACCESS vlan_id: 999 traffic_type: DATA fabric_enabled_wireless: false - name: LEGACY_STORAGE_L2_VN vlan_name: STORAGE_NETWORK vlan_id: 998 traffic_type: DATA fabric_enabled_wireless: falseLocation in GUI:
Provision » SD-Access » Virtual Networks » Layer 2 Virtual Networks
Diagram
Section titled “Diagram”Classes
Section titled “Classes”fabric_sites (catalyst_center.fabric)
Section titled “fabric_sites (catalyst_center.fabric)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| l2_virtual_networks | List | [l2_virtual_networks] | No |
l2_virtual_networks (catalyst_center.fabric.fabric_sites)
Section titled “l2_virtual_networks (catalyst_center.fabric.fabric_sites)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Yes | ||
| vlan_name | String | No | ||
| vlan_id | Integer | min: 2, max: 4093 | No | |
| traffic_type | Choice | DATA, VOICE | No | |
| fabric_enabled_wireless | Boolean | true, false | No | |
| associated_l3_virtual_network_name | String | No |
Layer 2 Virtual Networks enable VLAN extension across the SD-Access fabric while maintaining Layer 2 adjacency for applications that require it. They are associated with a Fabric Site and a traffic type, and can be handed off to external networks via Layer 2 Handoffs on Border Devices. This resource is SDA fabric only.
Examples
Section titled “Examples”Example-1: Basic Layer 2 Virtual Network for Data Traffic
This example demonstrates how to configure a basic Layer 2 virtual network within an SD-Access fabric site. Layer 2 virtual networks enable VLAN extension across the fabric while maintaining traditional Layer 2 networking semantics for applications and services that require Layer 2 adjacency.
The Layer 2 virtual network configuration includes:
- Virtual network name (L2_SDA_VN_1) for identification and policy assignment
- VLAN name (L2_VLAN_USERS) for traditional VLAN-based network segmentation
- VLAN ID (501) for 802.1Q tagging and network isolation
- Traffic type specification (DATA) for appropriate QoS and policy treatment
- Fabric-enabled wireless disabled for wired-only network segments
catalyst_center: fabric: fabric_sites: - name: Global/Canada authentication_template: name: No Authentication l2_virtual_networks: - name: L2_SDA_VN_1 vlan_name: L2_VLAN_USERS vlan_id: 501 traffic_type: DATA fabric_enabled_wireless: falseExample-2: Layer 2 Virtual Network with Wireless Integration
This example shows how to configure a Layer 2 virtual network with fabric-enabled wireless support for unified wired and wireless connectivity. This configuration enables seamless Layer 2 extension across both wired and wireless infrastructure within the SD-Access fabric.
catalyst_center: fabric: fabric_sites: - name: Global/North America/Corporate Campus authentication_template: name: Closed Authentication l2_virtual_networks: - name: CORPORATE_L2_NETWORK vlan_name: CORPORATE_USERS vlan_id: 100 traffic_type: DATA fabric_enabled_wireless: trueExample-3: Layer 2 Virtual Networks with L3 Virtual Network Association
This example demonstrates how to configure Layer 2 virtual networks associated with Layer 3 virtual networks for inter-VLAN routing within the SD-Access fabric. Associating an L2 VN with an L3 VN enables routing between Layer 2 segments while maintaining Layer 2 adjacency within each segment.
catalyst_center: fabric: fabric_sites: - name: Global/Europe/ManufacturingPlant authentication_template: name: Closed Authentication l3_virtual_networks: - CORP_VN - IOT_VN l2_virtual_networks: - name: PRODUCTION_L2_VN vlan_name: PRODUCTION_CONTROL vlan_id: 200 traffic_type: DATA fabric_enabled_wireless: false associated_l3_virtual_network_name: CORP_VN - name: IOT_L2_VN vlan_name: IOT_SENSORS vlan_id: 300 traffic_type: DATA fabric_enabled_wireless: true associated_l3_virtual_network_name: IOT_VN - name: GUEST_L2_VN vlan_name: GUEST_ACCESS vlan_id: 400 traffic_type: DATA fabric_enabled_wireless: trueExample-4: Layer 2 Virtual Network for Voice Traffic
This example shows how to configure a Layer 2 virtual network specifically optimized for voice traffic with appropriate QoS treatment and priority handling within the SD-Access fabric.
catalyst_center: fabric: fabric_sites: - name: Global/Asia Pacific/CallCenter authentication_template: name: Closed Authentication l2_virtual_networks: - name: VOICE_L2_VN vlan_name: VOICE_TRAFFIC vlan_id: 150 traffic_type: VOICE fabric_enabled_wireless: trueExample-5: Layer 2 Virtual Network for Legacy System Integration
This example shows how to configure Layer 2 virtual networks for integrating legacy systems that require specific VLAN configurations and Layer 2 adjacency within the modern SD-Access fabric infrastructure.
catalyst_center: fabric: fabric_sites: - name: Global/Europe/Legacy_Data_Center authentication_template: name: Closed Authentication l2_virtual_networks: - name: LEGACY_MAINFRAME_L2_VN vlan_name: MAINFRAME_ACCESS vlan_id: 999 traffic_type: DATA fabric_enabled_wireless: false - name: LEGACY_STORAGE_L2_VN vlan_name: STORAGE_NETWORK vlan_id: 998 traffic_type: DATA fabric_enabled_wireless: falseLocation in GUI:
Provision » SD-Access » Virtual Networks » Layer 2 Virtual Networks
Diagram
Section titled “Diagram”Classes
Section titled “Classes”fabric_sites (catalyst_center.fabric)
Section titled “fabric_sites (catalyst_center.fabric)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| l2_virtual_networks | List | [l2_virtual_networks] | No |
l2_virtual_networks (catalyst_center.fabric.fabric_sites)
Section titled “l2_virtual_networks (catalyst_center.fabric.fabric_sites)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Yes | ||
| vlan_name | String | No | ||
| vlan_id | Integer | min: 2, max: 4093 | No | |
| traffic_type | Choice | DATA, VOICE | No | |
| fabric_enabled_wireless | Boolean | true, false | No | |
| associated_l3_virtual_network_name | String | No |
Examples
Section titled “Examples”Example-1: Basic Layer 2 Virtual Network for Data Traffic
This example demonstrates how to configure a basic Layer 2 virtual network within an SD-Access fabric site. Layer 2 virtual networks enable VLAN extension across the fabric while maintaining traditional Layer 2 networking semantics for applications and services that require Layer 2 adjacency.
The Layer 2 virtual network configuration includes:
- Virtual network name (L2_SDA_VN_1) for identification and policy assignment
- VLAN name (L2_VLAN_USERS) for traditional VLAN-based network segmentation
- VLAN ID (501) for 802.1Q tagging and network isolation
- Traffic type specification (DATA) for appropriate QoS and policy treatment
- Fabric-enabled wireless disabled for wired-only network segments
catalyst_center: fabric: fabric_sites: - name: Global/Canada authentication_template: name: No Authentication l2_virtual_networks: - name: L2_SDA_VN_1 vlan_name: L2_VLAN_USERS vlan_id: 501 traffic_type: DATA fabric_enabled_wireless: falseExample-2: Layer 2 Virtual Network with Wireless Integration
This example shows how to configure a Layer 2 virtual network with fabric-enabled wireless support for unified wired and wireless connectivity. This configuration enables seamless Layer 2 extension across both wired and wireless infrastructure within the SD-Access fabric.
catalyst_center: fabric: fabric_sites: - name: Global/North America/Corporate Campus authentication_template: name: Closed Authentication l2_virtual_networks: - name: CORPORATE_L2_NETWORK vlan_name: CORPORATE_USERS vlan_id: 100 traffic_type: DATA fabric_enabled_wireless: trueExample-3: Layer 2 Virtual Networks with L3 Virtual Network Association
This example demonstrates how to configure Layer 2 virtual networks associated with Layer 3 virtual networks for inter-VLAN routing within the SD-Access fabric. Associating an L2 VN with an L3 VN enables routing between Layer 2 segments while maintaining Layer 2 adjacency within each segment.
catalyst_center: fabric: fabric_sites: - name: Global/Europe/ManufacturingPlant authentication_template: name: Closed Authentication l3_virtual_networks: - CORP_VN - IOT_VN l2_virtual_networks: - name: PRODUCTION_L2_VN vlan_name: PRODUCTION_CONTROL vlan_id: 200 traffic_type: DATA fabric_enabled_wireless: false associated_l3_virtual_network_name: CORP_VN - name: IOT_L2_VN vlan_name: IOT_SENSORS vlan_id: 300 traffic_type: DATA fabric_enabled_wireless: true associated_l3_virtual_network_name: IOT_VN - name: GUEST_L2_VN vlan_name: GUEST_ACCESS vlan_id: 400 traffic_type: DATA fabric_enabled_wireless: trueExample-4: Layer 2 Virtual Network for Voice Traffic
This example shows how to configure a Layer 2 virtual network specifically optimized for voice traffic with appropriate QoS treatment and priority handling within the SD-Access fabric.
catalyst_center: fabric: fabric_sites: - name: Global/Asia Pacific/CallCenter authentication_template: name: Closed Authentication l2_virtual_networks: - name: VOICE_L2_VN vlan_name: VOICE_TRAFFIC vlan_id: 150 traffic_type: VOICE fabric_enabled_wireless: trueExample-5: Layer 2 Virtual Network for Legacy System Integration
This example shows how to configure Layer 2 virtual networks for integrating legacy systems that require specific VLAN configurations and Layer 2 adjacency within the modern SD-Access fabric infrastructure.
catalyst_center: fabric: fabric_sites: - name: Global/Europe/Legacy_Data_Center authentication_template: name: Closed Authentication l2_virtual_networks: - name: LEGACY_MAINFRAME_L2_VN vlan_name: MAINFRAME_ACCESS vlan_id: 999 traffic_type: DATA fabric_enabled_wireless: false - name: LEGACY_STORAGE_L2_VN vlan_name: STORAGE_NETWORK vlan_id: 998 traffic_type: DATA fabric_enabled_wireless: false