To create virtual routers, use the following command:
create virtual-router vr-name {type [vrf | vpn-vrf {vr parent_vr_name}]}To create local-only virtual routers (ExtremeSwitching 5320-24T/P and 5320-16P only), use the following command:
create virtual-router vr-name local-only {type [vrf | vpn-vrf {vr parent_vr_name}]}Use the create virtual-router command to create a user VR or VRF.
| vr-name | Virtual router name. |
| type | Specifies the type of virtual router you are creating. |
| local-only | Specifies local-only VR. For ExtremeSwitching 5320-24T/P and 5320-16P series switches and stacks only. |
| vrf | Specifies that you are creating a new L3 or IP routing domain. |
| vpn-vrf | Specifies that you are creating a new L3 or IP routing domain that supports L3VPNs. Not supported on Universal platforms. |
| parent_vr_name | Specifies the parent VR that supports the VRF you are creating. |
If no type is specified, then the default is to create a user virtual router. A virtual router creates separate L3 Routing Domains.
If parent_vr_name parameter is not specified, the VRF will be created under the VR of the current CLI context. The default is VR-Default.
All VRFs are created under default VR or a user created VR. VPN-VRFs can be created in any VR but for L3VPNs to work, VPN-VRFs should be created under a parent VR where MPLS is configured. There is a single namespace maintained by the configuration manager and it contains VRs and VRFs. Hence the name for a VR or a VRF must be unique in ExtremeXOS.
A VR or VRF name must begin with an alphabetical character and may contain alphanumeric characters and underscores ( _ ), but it cannot contain spaces. The maximum allowed length for a name is 31 characters. The name must be unique among the object names on the switch, and the name is case insensitive. For information on VR and VRF name guidelines and a list of reserved names, see Object Names in the Switch Engine 32.2 User Guide .
When a new VR is created, by default, no ports are assigned, no VLAN interface is created, and no support for any routing protocols is added. A protocol process is started in the parent VR when a protocol instance is added to a VRF. If you do not specify a VR type, this command creates a user VR.
VRFs are supported as children of user VRs or VR-Default. If a parent_vr_name is specified when a VRF is created, the new VRF is created under that parent, provided that the parent supports VRFs. If no parent is specified, the VRF is assigned to the VR for the current VR context, or to VR-Default if the current VR context does not support VRFs.
Note
To support Layer 3 VPNs, a VPN VRF must be created under the VR that supports MPLS. The software supports MPLS on only one VR.Starting with ExtremeXOS 22.6, you can create "local-only" virtual routers that have separate logical IP lookup tables used only for IP packets to or from the switch's local IP addresses. This feature is only applicable for ExtremeSwitching X440-G2 and X620 series switches and stacks with these switches. All other platforms support separate logical IP lookup tables in hardware, so "local-only" is not specified.
The following example creates the VR "vr-acme":
create virtual-router vr-acme
The following example creates the non-VPN VRF vrf1:
create virtual-router vrf1 type vrf
create virtual-router vr1 local-only
This command was first available in ExtremeXOS 11.0.
Support for non-VPNVRFs was added in ExtremeXOS 12.5.
Support for VPN VRFs was added in ExtremeXOS 12.6.0-BGP.
Support for L3 VPN VRFs was added in ExtremeXOS 15.3.
Support for local-only VRs was added in ExtremeXOS 22.6.
This command is available on ExtremeSwitching 5320, 5420, 5520, and 5720 series switches.