VRF
Location in GUI: Application Management » Schemas
Diagram
Section titled “Diagram”Classes
Section titled “Classes”templates (ndo.schemas)
Section titled “templates (ndo.schemas)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| vrfs | List | [vrfs] | No |
vrfs (ndo.schemas.templates)
Section titled “vrfs (ndo.schemas.templates)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | Yes | |
| data_plane_learning | Boolean | true, false | No | true |
| preferred_group | Boolean | true, false | No | false |
| l3_multicast | Boolean | true, false | No | false |
| vzany | Boolean | true, false | No | false |
| sites | List | [sites] | No | |
| contracts | Class | [contracts] | No | |
| site_aware_policy_enforcement | Boolean | true, false | No | false |
sites (ndo.schemas.templates.vrfs)
Section titled “sites (ndo.schemas.templates.vrfs)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Yes | ||
| regions | List | [regions] | No |
contracts (ndo.schemas.templates.vrfs)
Section titled “contracts (ndo.schemas.templates.vrfs)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| consumers | List | [consumers] | No | |
| providers | List | [providers] | No |
regions (ndo.schemas.templates.vrfs.sites)
Section titled “regions (ndo.schemas.templates.vrfs.sites)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Yes | ||
| hub_network | Boolean | true, false | No | false |
| hub_network_name | String | No | ||
| hub_network_tenant | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | No | |
| vpn_gateway | Boolean | true, false | No | false |
| cidrs | List | [cidrs] | No |
consumers (ndo.schemas.templates.vrfs.contracts)
Section titled “consumers (ndo.schemas.templates.vrfs.contracts)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | Yes | |
| schema | String | No | ||
| template | String | No |
providers (ndo.schemas.templates.vrfs.contracts)
Section titled “providers (ndo.schemas.templates.vrfs.contracts)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | Yes | |
| schema | String | No | ||
| template | String | No |
cidrs (ndo.schemas.templates.vrfs.sites.regions)
Section titled “cidrs (ndo.schemas.templates.vrfs.sites.regions)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| ip | IP | Yes | ||
| subnets | List | [subnets] | No |
subnets (ndo.schemas.templates.vrfs.sites.regions.cidrs)
Section titled “subnets (ndo.schemas.templates.vrfs.sites.regions.cidrs)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| ip | IP | Yes | ||
| zone | String | No | ||
| name | String | No |
Examples
Section titled “Examples”Example 1: The YAML snippet below demonstrates how to enable “Site-aware Policy Enforcement Mode” in NDO for a stretched VRF, which is essential to support PBR vzAny Multi-Site deployments. This is enabled by setting the site_aware_policy_enforcement_mode: true flag, ensuring that policies within the stretched VRF are enforced with awareness of the site, allowing for proper PBR and vzAny functionality across multiple locations.
ndo: schemas: - name: SCH_TN_10_NONP templates: - name: TMP_STRETCHED tenant: TN_STAGING vrfs: - name: VRF_STAGING vzany: true site_aware_policy_enforcement: trueOn-premise VRF:
ndo: schemas: - name: ABC templates: - name: TEMPLATE1 vrfs: - name: VRF1 data_plane_learning: true preferred_group: false l3_multicast: true vzany: true site_aware_policy_enforcement: true contracts: consumers: - name: CONTRACT2Azure VRF:
ndo: schemas: - name: AZURE1 templates: - name: TEMPLATE1 vrfs: - name: VRF1 sites: - name: AZURE-SITE1 regions: - name: eastus hub_network: true hub_network_name: default hub_network_tenant: infra cidrs: - ip: 172.31.0.0/24