configure auto-peering one-config nsi-id

configure auto-peering one-config nsi-id id type [nsi | vrf] [add | delete] [[ipaddress {netmask} | ipNetmask ] | ipNetmaskv6] {vr vrname }

Description

Specifies a list of OneConfig dynamic auto-peering services.

Syntax Description

auto-peering Specifies Auto-peering.
one-config Specifies changing the BGP Auto-peering OneConfig configuration.
nsi-id Specifies setting the Network Service (NSI) ID for dynamic L3 configuration
id Specifies the NSI ID.
type Specifies configuring the NSI ID type.
nsi Specifies NSI ID type as NSI.
vrf Specifies NSI ID type as VRF.
add Adds subnet.
delete Deletes subnet.
ipaddress Specifies the IP address.
netmask Specifies the IP netmask.
ipNetmask Specifies the IPv4 address/netmask.
ipNetmaskv6 Specifies IPv6 address/netmask
vr Specifies selecting the virtual router (VR) If you do not specify a VR or VRF, the current VR context is used.
vrname Specifies the VR name.

Default

If you do not specify a VR or VRF, the current VR context is used.

Usage Guidelines

The configuration is held on each node and is inactive until a VLAN/NSI binding is made to a dynamic VLAN. After the NSI is discovered, the configuration associated with the NSI on the VLAN is applied. This consists of creating the VRF as needed, applying IPv4 and IPv6 prefixes, enabling Anycast IP, and enabling IP Forwarding on the mapped VLAN. The mechanism to assign VLAN to NSI mapping is done by following methods: policy by RADIS, and Fabric Attach; the VXLAN virtual network and VNI/NSI is dynamically created by the VXLAN service.

Example

The following example configures an NSI ID "1000" for type "VRF" on VR "red":

# configure auto-peering one-config nsi 1000 type VRF add vr red

History

This command was first available in ExtremeXOS 31.1.

Platform Availability

This command is available on the ExtremeSwitching X670-G2, X465, X590, X690, X695, X870, 5320, 5420, 5520 series switches.

This feature requires the Advanced Edge or Base license. For more information about licenses, see the ExtremeXOS and Switch Engine 31.7 Feature License Requirements .