virtual-router

virtual-router {vr-name}

Description

Changes the VR context.

Syntax Description

vr-name Specifies the name of the VR.

Default

N/A.

Usage Guidelines

Use this command to change the VR context for subsequent commands. When you issue the command, the prompt changes to reflect the VR domain. Configuration commands for Layer 3 routing protocols, creating VLANs, and deleting VLANs apply only to the current VR context.

Use this command with no name, or use the name "VR-Default" to return to the default configuration domain.

Under a VR configuration domain, any VR commands are applied only to that VR. The VR commands consist of all the BGP, OSPF, PIM, and RIP commands, and the commands listed in the following table.

Table 1. VR Commands
[enable | disable] ipforwarding
clear iparp
clear counters iparp1
configure iparp 1
configure iparp [add | delete] 1
[enable | disable] iparp 1
show iparp 1
configure iproute [add | delete] 1
show iproute 1
show ipstats 1
rtlookup
create [vlan | vman] vlan-name
[enable | disable] igmp
[enable | disable] igmp snooping 1
[enable | disable] ipmcforwarding
show igmp
show igmp snooping
show igmp group
show igmp snooping cache
[enable | disable] mld
[enable | disable] mld snooping
show mld
show mld snooping
show mld group

The VR context simplifies configuration because you do not have to specify the VR for each individual protocol configuration command. The current VR context is indicated in the CLI prompt.

For example, if you wish to configure OSPF for the user VR vr-manufacturing, you would change the VR context to that of vr-manufacturing. All the subsequent OSPF commands would apply to that VR, unless the context is changed again.

A VR is identified by a name (up to 32 characters long). The name must be unique among the VLAN and VR names on the switch. For backward compatibility, you cannot name a virtual router VR-0, VR-1, or VR-2. VR names are case insensitive.

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.

Example

The following example changes the VR context to "vr-acme":

virtual-router vr-acme

History

This command was first available in ExtremeXOS 11.0.

Platform Availability

This command is available on all Universal switches supported in this document.


1 Other commands are available with these listed.