VCF fabric commands -- border enable

Use border enable to enable the border node service.

Use undo border enable to disable the border node service.

Syntax

border enable

undo border enable

Default

The device is not a border node.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

The external network and routers are created and deleted on the OpenStack Dashboard. Use this command to configure the device as a border node. The device automatically deploys the routing configurations made on the OpenStack Dashboard and implements connectivity between tenant networks and the external network.

On a VXLAN network with a centralized IP gateway or on a VLAN network, use this command on spine nodes. On a VXLAN network with distributed IP gateways, use this command on leaf nodes.

Examples

# Enable the border node service.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] border enable

VCF fabric commands -- display vcf-fabric role

Use display vcf-fabric role to display the role of the device in the VCF fabric.

Syntax

display vcf-fabric role

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

Use this command to display the default role and the current role of the device in the VCF fabric. To change the current role of the device, use the vcf-fabric role command.

Examples

# Display the role of the device in the VCF fabric.

<System> display vcf-fabric role

Default role: leaf

Current role: leaf

Table 1 Command output

Field | Description
Default role | Default role of the device: · spine. · leaf. · access.
Current role | Current role of the device: · spine. · leaf. · access.

Related commands

vcf-fabric role

VCF fabric commands -- display vcf-fabric topology

Use display vcf-fabric topology to display VCF fabric topology information.

Syntax

display vcf-fabric topology

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

This command displays VCF fabric topology information only when it is executed on the master spine node.

Before you display VCF fabric topology information, make sure VCF fabric topology discovery and automated underlay network deployment are enabled.

Examples

# Display VCF fabric topology information.

<Sysname> display vcf-fabric topology

Topology Information

----------------------------------------------------------------------------------

* indicates the master spine role among all spines

SpineIP Interface Link LeafIP Status

*10.11.113.51 GigabitEthernet1/0/1 Up 10.11.113.52 Deploying

GigabitEthernet1/0/2 Down -- --

GigabitEthernet1/0/3 Down -- --

GigabitEthernet1/0/4 Down -- --

GigabitEthernet1/0/5 Up 10.11.113.53 Deploying

GigabitEthernet1/0/6 Down -- --

GigabitEthernet1/0/7 Down -- --

GigabitEthernet1/0/8 Down -- --

Table 2 Command output

Field | Description
SpineIP | IPv4 address of the management Ethernet interface on the spine node. This field displays an asterisk (*) before the IP address if the device is the master spine node.
Interface | Interface through which the spine node connects to a leaf node. If the device is a master spine node, all interfaces on the device are displayed.
Link | Physical link state of the interface.
LeafIP | IPv4 address of the interface through which a leaf node connects to the spine node.
Status | Status of automated underlay network deployment on the leaf node. This field displays two hyphens (--) if automated underlay network deployment is not started. This field displays Deploying if automated underlay network deployment is in progress.

Related commands

vcf-fabric underlay autoconfigure

vcf-fabric topology enable

VCF fabric commands -- display vcf-fabric underlay autoconfigure

Use display vcf-fabric underlay autoconfigure to display information about automated underlay network deployment.

Syntax

display vcf-fabric underlay autoconfigure

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

Before you execute this command, make sure automated underlay network deployment is enabled.

Examples

# Display information about automated underlay network deployment.

<Sysname> display vcf-fabric underlay autoconfigure

success command:

#

system

clock timezone beijing add 08:00:00

#

system

lldp global enable

lldp compliance cdp

#

system

ospf 1

graceful-restart ietf

area 0.0.0.0

#

system

interface LoopBack0

#

system

l2vpn enable

#

system

vxlan tunnel mac-learning disable

vxlan tunnel arp-learning disable

#

system

stp global enable

#

system

ntp-service enable

ntp-service unicast-peer 172.16.1.136

#

system

netconf soap https enable

restful https enable

#

system

info-center loghost 172.16.1.136

#

system

local-user aaa

password ******

service-type https

authorization-attribute user-role network-admin

#

system

line vty 0 63

authentication-mode scheme

user-role network-admin

#

system

bgp 100

graceful-restart

address-family l2vpn evpn

#

system

vcf-fabric topology enable

#

system

neutron

rabbit user openstack

rabbit password ******

rabbit host ip 172.16.1.136

restful user aaa password ******

vpn-target 1:1 export-extcommunity

vsi-mac 789c-2f5f-0200

network-type distributed-vxlan

proxy-arp enable

l2agent enable

l3agent enable

#

system

snmp-agent

snmp-agent packet max-size 4096

snmp-agent community read public

snmp-agent community write private

snmp-agent sys-info version all

#

Uplink interface:

GigabitEthernet1/0/1

GigabitEthernet1/0/2

Downlink interface:

GigabitEthernet1/0/3

GigabitEthernet1/0/4

Loopback0 IP Allocation:

DEV_MAC LOOPBACK_IP MANAGE_IP STATE

a43c-adae-0400 200.1.1.6 172.16.1.193 up

a43c-9aa7-0100 200.1.1.4 172.16.1.152 up

Aggregation configurations:

AggrID: 7

interface: GigabitEthernet1/0/6

interface: GigabitEthernet1/0/6

IRF Allocation:

Self Bridge Mac: a43c-adae-0400

IRF Status: Yes

Member List: [1, 2]

bgp configure peer:

200.1.1.4

Table 3 Command output

Field | Description
success command | Commands that have been successfully executed during automated underlay network deployment.
Uplink interface | Uplink interfaces of the device.
Downlink interface | Downlink interfaces of the device.
Aggregation configurations | Information about Layer 2 aggregation groups.
IRF Allocation | IRF configurations, including IRF bridge MAC address of the IRF fabric, IRF status, and the IRF member ID of the device.
Loopback0 IP Allocation | IP address assigned to the loopback interfaces.
bgp configure peer | Information about BGP peers of the device.

Related commands

vcf-fabric underlay autoconfigure

VCF fabric commands -- gateway ip

Use gateway ip to specify the IPv4 address of the border gateway.

Use undo gateway ip to restore the default.

Syntax

gateway ip ipv4-address

undo gateway ip

Default

No IPv4 address is specified for the border gateway.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

ipv4-address: Specifies the IPv4 address of the border gateway.

Usage guidelines

Use this command to specify the border gateway IP address for VMs to access the external network. On a VXLAN network with a centralized IP gateway or on a VLAN network, use this command on spine nodes. On a VXLAN network with distributed IP gateways, use this command on leaf nodes.

If you configure this command multiple times, the most recent configuration takes effect.

Examples

# Specify IPv4 address 100.1.1.1 for the border gateway.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] gateway ip 100.1.1.1

VCF fabric commands -- l2agent enable

Use l2agent enable to enable Layer 2 (L2) agent.

Use undo l2agent enable to disable L2 agent.

Syntax

l2agent enable

undo l2agent enable

Default

L2 agent is disabled.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

On a VLAN network, use this command on spine nodes and leaf nodes.

On a VXLAN network with a centralized IP gateway, use this command on spine nodes and leaf nodes.

On a VXLAN network with distributed IP gateways, use this command on leaf nodes.

Examples

# Enable L2 agent.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] l2agent enable

VCF fabric commands -- l3agent enable

Use l3agent enable to enable Layer 3 (L3) agent.

Use undo l3agent enable to disable L3 agent.

Syntax

l3agent enable

undo l3agent enable

Default

L3 agent is disabled.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

On a VLAN network or on a VXLAN network with a centralized IP gateway, use this command only on spine nodes.

On a VXLAN network with distributed IP gateways, use this command on leaf nodes.

Examples

# Enable L3 agent.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] l3agent enable

VCF fabric commands -- network-type

Use network-type to specify the network type.

Use undo network-type to restore the default.

Syntax

network-type { centralized-vxlan | distributed-vxlan | vlan }

undo network-type

Default

The network type is VLAN.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

centralized-vxlan: Specifies the VXLAN network with a centralized IP gateway.

distributed-vxlan: Specifies the VXLAN network with distributed IP gateways.

vlan: Specifies the VLAN network.

Examples

# Specify the network type as VXLAN network with a centralized IP gateway.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] network-type centralized-vxlan

VCF fabric commands -- neutron

Use neutron to enable Neutron and enter Neutron view.

Use undo neutron to disable Neutron and delete all configurations in Neutron view.

Syntax

neutron

undo neutron

Default

Neutron is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Examples

# Enable Neutron and enter Neutron view.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron]

VCF fabric commands -- proxy-arp enable

Use proxy-arp enable to enable local proxy ARP for VSI interfaces.

Use undo proxy-arp enable to restore the default.

Syntax

proxy-arp enable

undo proxy-arp enable

Default

Local proxy ARP is disabled for VSI interfaces. The device uses ARP flood suppression entries to answer ARP requests for MAC addresses of VMs on a different site from the requesting VMs.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Use this command only on leaf nodes on a VXLAN network with distributed IP gateways.

This feature enables the device to use the MAC address of VSI interfaces to answer ARP requests for MAC addresses of VMs on a different site from the requesting VMs. To configure the MAC address of VSI interfaces, use the vsi-mac command.

This command takes effect on VSI interfaces that are created after this command is executed. It does not take effect on existing VSI interfaces.

Examples

# Enable local ARP proxy for VSI interfaces.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] proxy-arp enable

VCF fabric commands -- rabbit durable-queue enable

Use rabbit durable-queue enable to enable creation of RabbitMQ durable queues.

Use undo rabbit durable-queue enable to disable creation of RabbitMQ durable queues.

Syntax

rabbit durable-queue enable

undo rabbit durable-queue enable

Default

Creation of RabbitMQ durable queues is disabled. RabbitMQ non-durable queues are created and stored in the memory of RabbitMQ servers.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

In a Neutron network, the device communicates with the Neutron server through RabbitMQ to obtain the configuration for deploying the overlay network. You must configure RabbitMQ server-related settings on the device and make sure the settings are the same as those on the Neutron server. If the durable attribute of RabbitMQ queues is set on the Neutron server, you must enable creation of RabbitMQ durable queues on the device so that RabbitMQ queues can be correctly created. The created RabbitMQ durable queues are stored in the disk of the RabbitMQ servers.

Examples

# Enable creation of RabbitMQ durable queues.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] rabbit durable-queue enable

VCF fabric commands -- rabbit host

Use rabbit host to specify the IPv4 address, port number, and MPLS L3VPN instance of a RabbitMQ server.

Use undo rabbit host to restore the default.

Syntax

rabbit host ip ipv4-address [ port port-number ] [ vpn-instance vpn-instance-name ]

undo rabbit host ip ipv4-address [ vpn-instance vpn-instance-name ]

Default

No IPv4 address or MPLS L3VPN instance of a RabbitMQ server is specified, and the port number of a RabbitMQ server is 5672.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

ip ipv4-address: Specifies the IPv4 address of a RabbitMQ server.

port port-number: Specifies the port number for the device to communicate with a RabbitMQ server. The value range for the port-number argument is 1 to 65535.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If a RabbitMQ server is on the public network, do not specify this option.

Usage guidelines

The device communicates with the Neutron server through RabbitMQ servers.

Before you configure this command, make sure the controller where the Neutron server resides has been installed with RabbitMQ components.

If the device connects to a RabbitMQ server cluster, you can repeat this command to specify the IPv4 addresses of multiple RabbitMQ servers in the cluster.

You can specify the IPv4 address for a maximum of 32 RabbitMQ servers.

Examples

# Specify 10.11.113.143 as the IPv4 address of a RabbitMQ server.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] rabbit host ip 10.11.113.143

VCF fabric commands -- rabbit password

Use rabbit password to configure the password for the device to establish connections with RabbitMQ servers.

Use undo rabbit password to restore the default.

Syntax

rabbit password { cipher | plain } string

undo rabbit password

Default

The device uses plaintext password guest to establish connections with RabbitMQ servers.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

cipher: Specifies a password in encrypted form.

simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.

string: Specifies the password. Its plaintext form is a case-sensitive string of 4 to 64 characters. Its encrypted form is a case-sensitive string of 36 to 256 characters.

Usage guidelines

If you configure this command multiple times, the most recent configuration takes effect.

Examples

# Configure the device to use plaintext password aaaa to establish connections with RabbitMQ servers.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] rabbit password plain aaaa

VCF fabric commands -- rabbit source-ip

Use rabbit source-ip to specify the source IPv4 address for the device to communicate with RabbitMQ servers.

Use undo rabbit source-ip to restore the default.

Syntax

rabbit source-ip ipv4-address [ vpn-instance vpn-instance-name ]

undo rabbit source-ip

Default

No source IPv4 address is specified for the device to communicate with RabbitMQ servers. The device automatically selects the source IPv4 address through the routing protocol to communicate with RabbitMQ servers.

Views

Neutron view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

ipv4-address: Specifies the source IPv4 address with which the device communicates with RabbitMQ servers.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If the specified source IPv4 address is on the public network, do not specify this option.

Usage guidelines

Use this command if multiple equal-cost routes exist between the device and RabbitMQ servers. For example, assume that two equal-cost routes exist, and the outgoing interface in one route is a logical interface and that in the other route is a physical interface. If the device automatically selects the physical interface, communications with RabbitMQ servers might be interrupted and Neutron services will be further affected when the physical interface goes down. To avoid this problem, specify the IPv4 address of the logical interface as the source IPv4 address.

Examples

# Specify 1.1.1.1 as the source IPv4 address for the device to communicate with RabbitMQ servers.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] rabbit source-ip 1.1.1.1

VCF fabric commands -- rabbit user

Use rabbit user to configure the username for the device to establish connections with RabbitMQ servers.

Use undo rabbit user to restore the default.

Syntax

rabbit user username

undo rabbit user

Default

The device uses username guest to establish connections with RabbitMQ servers.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

username: Specifies the username for the device to establish connections with RabbitMQ servers, a case-sensitive string of 1 to 63 characters.

Usage guidelines

If you configure this command multiple times, the most recent configuration takes effect.

Examples

# Configure the device to use username aaa to establish connections with RabbitMQ servers.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] rabbit user aaa

VCF fabric commands -- rabbit virtual-host

Use rabbit virtual-host to specify a virtual host on a RabbitMQ server to provide services for the device.

Use undo rabbit virtual-host to restore the default.

Syntax

rabbit virtual-host hostname

undo rabbit virtual-host

Default

The virtual host with the name / provides RabbitMQ services for the device.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

hostname: Specifies the name of a virtual host on a RabbitMQ server. The hostname is a case-sensitive string of 1 to 63 characters.

Usage guidelines

Multiple virtual hosts might exist on a RabbitMQ server. Each virtual host can independently provide RabbitMQ services for the device. For the device to correctly communicate with the Neutron server, specify the same virtual host with the Neutron server.

Examples

# Specify the virtual host with the name aaa to provide RabbitMQ services for the device.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] rabbit virtual-host aaa

VCF fabric commands -- restful user

Use restful user to configure the username and password for the device to deploy configurations through a RESTful API.

Use undo restful user to restore the default.

Syntax

restful user username password { plain | cipher } string

undo restful user

Default

No username and password is specified for the device to deploy configurations through a RESTful API.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

username: Specifies the username for the device to deploy configurations through a RESTful AP. The username is a case-sensitive string of 1 to 63 characters.

cipher: Specifies a password in encrypted form.

simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.

string: Specifies the password. Its plaintext form is a case-sensitive string of 3 to 64 characters. Its encrypted form is a case-sensitive string of 36 to 256 characters.

Usage guidelines

You must specify an existing pair of username and password.

If you configure this command multiple times, the most recent configuration takes effect.

Examples

# Configure the device to use username aaa and plaintext password aaaa to deploy configurations through a RESTful API.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] restful user aaa password plain aaaa

VCF fabric commands -- vcf-fabric role

Use vcf-fabric role to specify the role of the device.

Use undo vcf-fabric role to restore the default.

Syntax

vcf-fabric role { access | leaf | spine }

undo vcf-fabric role

Default

The role of the device varies by device model.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

access: Specifies the access node.

leaf: Specifies the leaf node.

spine: Specifies the spine node.

Usage guidelines

If you change the role of the device, the new role takes effect after the device restarts.

Examples

# Specify the device as a spine node.

<Sysname> system-view

[Sysname] vcf-fabric role spine

VCF fabric commands -- vcf-fabric spine-role master

Use vcf-fabric spine-role master to specify the device as a master spine node.

Use undo vcf-fabric spine-role master to restore the default.

Syntax

vcf-fabric spine-role master

undo vcf-fabric spine-role

Default

The device is not a master spine node.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

You must execute this command on a spine node.

When multiple spines nodes exist in the VCF fabric, you must specify a device as the master spine node to collect the topology for the entire VCF fabric.

Examples

# Specify the device as a master spine.

<Sysname> system-view

[Sysname] vcf-fabric spine-role master

Related commands

vcf-fabric role

VCF fabric commands -- vcf-fabric topology enable

Use vcf-fabric topology enable to enable VCF fabric topology discovery.

Use undo vcf-fabric topology enable to disable VCF fabric topology discovery.

Syntax

vcf-fabric topology enable

undo vcf-fabric topology enable

Default

VCF fabric topology discovery is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Examples

# Enable VCF fabric topology discovery.

<Sysname> system-view

[Sysname] vcf-fabric topology enable

VCF fabric commands -- vcf-fabric underlay autoconfigure

Use vcf-fabric underlay autoconfigure to specify the template file for automated underlay network deployment.

Use undo vcf-fabric underlay autoconfigure to restore the default.

Syntax

vcf-fabric underlay autoconfigure template

undo vcf-fabric underlay autoconfigure

Default

No template file is specified for automated underlay network deployment.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

template: Specifies a template file by its name, a case-insensitive string of 1 to 127 characters. A template file is a file ending with the .template file extension.

Usage guidelines

After this command is executed, the device uses the specified template file to deploy the underlay network.

Examples

# Specify template file vxlan_spine.template for automated underlay network deployment.

<Sysname> system-view

[Sysname] vcf-fabric underlay autoconfigure vxlan_spine.template

VCF fabric commands -- vcf-fabric underlay pause

Use vcf-fabric underlay pause to pause automated underlay network deployment.

Use undo vcf-fabric underlay pause to continue automated underlay network deployment.

Syntax

vcf-fabric underlay pause

undo vcf-fabric underlay pause

Default

Automated underlay network deployment is not paused.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

You can use this command to pause automated underlay network deployment if the device is in the process of automated underlay network deployment.

Examples

# Pause automated underlay network deployment.

<Sysname> system-view

[Sysname] vcf-fabric underlay pause

VCF fabric commands -- vpn-target export-extcommunity

Use vpn-target export-extcommunity to configure export route targets for a tenant VPN instance.

Use undo vpn-target export-extcommunity to restore the default.

Syntax

vpn-target target export-extcommunity

undo vpn-target target export-extcommunity

Default

No export route targets are configured for a tenant VPN instance.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

target: Specifies a route target, a string of 3 to 21 characters in one of the following formats:

· 16-bit AS number:32-bit user-defined number. For example, 101:3.

· 32-bit IP address:16-bit user-defined number. For example, 192.168.122.15:1.

· 32-bit AS number:16-bit user-defined number, where the AS number must not be less than 65536. For example, 65536:1.

Usage guidelines

In a data center, the border node connects to the external network through an interface which belongs to the global VPN instance. For the traffic from the external network to reach a tenant network, the border node needs to add the routes of the tenant VPN instance into the routing table of the global VPN instance. Use this command to configure export route targets of the tenant VPN instance as import route targets of the global VPN instance. This setting enables the global VPN instance to import routes of the tenant VPN instance.

Examples

# Configure export route targets for a tenant VPN instance.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] vpn-target 1:1 export-extcommunity

VCF fabric commands -- vpn-target import-extcommunity

Use vpn-target import-extcommunity to configure import route targets for a tenant VPN instance.

Use undo vpn-target import-extcommunity to restore the default.

Syntax

vpn-target target import-extcommunity

undo vpn-target target import-extcommunity

Default

No import route targets are configured for a tenant VPN instance.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

target: Specifies a route target, a string of 3 to 21 characters in one of the following formats:

· 16-bit AS number:32-bit user-defined number. For example, 101:3.

· 32-bit IP address:16-bit user-defined number. For example, 192.168.122.15:1.

· 32-bit AS number:16-bit user-defined number, where the AS number must not be less than 65536. For example, 65536:1.

Usage guidelines

Use this command only on leaf nodes on a VXLAN network with distributed IP gateways.

You do not need to execute this command if you have used the gateway ip or border enable command to create the default route to the external network.

In a data center, the border node connects to the external network through an interface which belongs to the global VPN instance. For tenant network data to reach the external network, use this command to configure import targets of the tenant VPN instance as export targets of the global VPN instance. This setting enables the tenant VPN instance to import routes of the global VPN instance.

Examples

# Configure import route targets for a tenant VPN instance.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] vpn-target 1:1 import-extcommunity

VCF fabric commands -- vsi-mac

Use vsi-mac to configure a MAC address for VSI interfaces.

Use undo vsi-mac to delete the MAC address for VSI interfaces.

Syntax

vsi-mac mac-address

undo vsi-mac

Default

No MAC address is specified for VSI interfaces.

Views

Neutron view

Predefined user roles

network-admin

mdc-admin

Parameters

mac-address: Specifies a MAC address in the H-H-H format.

Usage guidelines

Use this command only on leaf nodes on a VXLAN network with distributed IP gateways.

This command assigns the MAC address to all VSI interfaces newly created by automated overlay network deployment on the device.

This command takes effect only on VSI interfaces newly created after this command is executed.

Examples

# Configure the MAC address of all VSI interfaces as 1-1-1.

<Sysname> system-view

[Sysname] neutron

[Sysname-neutron] vsi-mac 1-1-1