create virtual-router

create virtual-router {type [vrf | vpn-vrf {vr parent_vr_name}]}

Description

Use the create virtual-router command to create a user VR or VRF.

Syntax Description

type	Specifies the type of virtual router you are creating.
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.
`parent_vr_name`	Specifies the parent VR that supports the VRF you are creating.

Default

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.

Usage Guidelines

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 (Multiprotocol Label Switching) 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.

When a new VR is created, by default, no ports are assigned, no VLAN (Virtual LAN) 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.