set interface gigabit-ethernet routed-interface enable

The set interface gigabit-ethernet routed-interface enable command enables the Ethernet port as a layer 3 routed interface. All Ethernet ports are layer 2 interfaces by default.

The delete interface gigabit-ethernet routed-interface enable command restores the Ethernet port to a layer 2 interface.

Command Syntax

set interface gigabit-ethernet <interface-name> routed-interface enable <true | false>

Parameter

Parameter

Description

gigabit-ethernet <interface-name>

Specifies a physical port name. The value is like ge-1/1/1, te-1/1/3, etc.

enable <true | false>

Enables or disables the Ethernet port as a layer 3 routed interface. The value could be true or false.

true: Enables the Ethernet port as a layer 3 routed interface.
false: Disables the Ethernet port as a layer 3 routed interface.

All Ethernet ports are layer 2 interfaces by default.

Usage Guidelines

Pay attention to the following precautions before configuring a routed interface:

When enabling an Ethernet port/LAG interface as a layer 3 routed interface, a name for the routed interface should be configured by using the command set interface gigabit-ethernet <interface-name> routed-interface name <string>. This name will be referred to as the “interface name” in other CLI commands.

NOTE:

To avoide conflict with the preserved interface names, the routed interface name and sub-interface name must start with the string "rif-". Otherwise, commit will fail with the error message "The name of interface must start with "rif-".

Reserved VLANs need to be configured on the device before configuring the routed interface.

Routed interface is mutually exclusive with the following layer 2 features, you have to delete all of the following configurations on the interface before enabling it as a routed interface, otherwise the routed interface commands will fail to commit.

set interface gigabit-ethernet <interface-name> backup-port XX
set interface aggregate-ethernet <lag-name> backup-port XX
set interface gigabit-ethernet <interface-name> crossflow XX
set interface aggregate-ethernet <lag-name> crossflow XX
set interface gigabit-ethernet <interface-name> family XX
set interface aggregate-ethernet <lag-name> family XX
set interface gigabit-ethernet <interface-name> loopback true
set interface gigabit-ethernet <interface-name> port-security XX
set interface aggregate-ethernet <lag-name> port-security XX
set interface gigabit-ethernet <interface-name> static-ethernet-switching mac-address XX
set interface aggregate-ethernet <lag-name> static-ethernet-switching mac-address XX
set interface gigabit-ethernet <interface-name> voice-vlan XX
set interface aggregate-ethernet <lag-name> voice-vlan XX
set protocols dhcp snooping trust-port <trust-port>
set protocols igmp-snooping vlan-id <vlan-id> mrouter interface <interface-name>
set protocols igmp-snooping vlan-id <vlan-id> static group <group-address> interface <interface-name>
set protocols dot1x interface <interface-name>
set interface gigabit-ethernet <interface-name> breakout true

Besides the layer 2 features listed above, routed interface does not support Spanning Tree Protocol (STP) and MAC learning. However, the Layer 2 feature of LLDP is supported on an Ethernet port enabled as routed interface.

After a routed interface is enabled, you have to configure the following node to bring the routed interface up. Only after this, the corresponding sub-interfaces can be used normally.

set l3-interface routed-interface <interface-name>

The member port of a LAG port cannot be enabled as a routed interface, correspondingly, the physical port enabled as a routed interface cannot be configured as a LAG member port.

Example

Enable the Ethernet port te-1/1/4 as a layer 3 routed interface.

admin@Xorplus# set interface gigabit-ethernet te-1/1/4 routed-interface enable true
admin@Xorplus# set interface gigabit-ethernet te-1/1/4 routed-interface name rif-te4
admin@Xorplus# commit