VXLAN Configuration Command Examples

This section contains payload examples and CLIs to demonstrate how to use NX-API REST to configure VXLAN on Cisco Nexus 3000 and 9000 Series switches and to show how the REST APIs correspond to the CLI commands. For more information, see the Cisco Nexus 9000 Series NX-OS VXLAN Configuration Guide, Release 7.x.

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-installation-and-configuration-guides-list.html/

Configuring VLAN and VXLAN VNI

Configuring VLAN and VXLAN VNI

POST http://<mgmt0_IP>/api/mo/sys/bd.json

{
 "bdEntity": {
   "children": [
     {
       "l2BD": {
         "attributes": {
           "accEncap": "vxlan-90001",
           "fabEncap": "vlan-123",
           "pcTag": "1"
}}}]}}

{
    imdata:[]
}

<System>
  <bd-items>
    <bd-items>
      <BD-list>
        <fabEncap>vlan-123</fabEncap>
        <accEncap>vxlan-90001</accEncap>
        <pcTag>1</pcTag>
      </BD-list>
    </bd-items>
  </bd-items>
</System>

This operation specifies a VLAN and maps the VLAN to a VXLAN VNI to configure Layer 2 VNI under VXLAN VLAN. This creates a VRF overlay VLAN for VXLAN routing.


CLI Commands

The CLI commands and options listed below are the equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.

vlan 123
 vn-segment 90001

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring SVI for Hosts for VXLAN Routing

Configuring SVI for Hosts for VXLAN Routing

POST http://<IP_Address>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ipv4Entity": {
          "children": [
            {
              "ipv4Inst": {
                "children": [
                  {
                    "ipv4Dom": {
                      "attributes": {
                        "name": "vxlan-90001"
                      },
                      "children": [
                        {
                          "ipv4If": {
                            "attributes": {
                              "id": "vlan123"
                            },
                            "children": [
                              {
                                "ipv4Addr": {
                                  "attributes": {
                                    "addr": "192.0.20.16/24"
}}}]}}]}}]}}]}},
      {
        "interfaceEntity": {
          "children": [
            {
              "sviIf": {
                "attributes": {
                  "id": "vlan123"
                },
                "children": [
                  {
                    "nwRtVrfMbr": {
                      "attributes": {
                        "tDn": "sys/inst-vxlan-90001"
}}}]}}]}},
      {
        "bdEntity": {
          "children": [
            {
              "l2BD": {
                "attributes": {
                  "fabEncap": "vlan-123",
                  "pcTag": "1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <ipv4-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>vxlan-90001</name>
          <if-items>
            <If-list>
              <id>vlan123</id>
              <addr-items>
                <Addr-list>
                  <addr>192.0.20.16/24</addr>
                </Addr-list>
              </addr-items>
            </If-list>
          </if-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </ipv4-items>
  <intf-items>
    <svi-items>
      <If-list>
        <id>vlan123</id>
        <rtvrfMbr-items>
          <tDn>/System/inst-items/Inst-list[name='vxlan-90001']</tDn>
        </rtvrfMbr-items>
      </If-list>
    </svi-items>
  </intf-items>
</System>

This operation configures SVI and an IP address on a VLAN for a host.


CLI Commands

The CLI commands and options listed below are the equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.

interface vlan123
 vrf member vxlan-90001
ip address 192.0.20.16/24

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring VNI Under VRF for VXLAN Routing

This operation configures a Layer 3 VNI under a VRF overlay VLAN. (A VRF overlay VLAN is a VLAN that is not associated with any server facing ports. All VXLAN VNIs that are mapped to a VRF, need to have their own internal VLANs allocated to it.)

Configuring VNI Under VRF for VXLAN Routing

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "encap": "vxlan-90005",
            "name": "vxlan-90001"
}}}]}}

{
    imdata:[]
}

<System>
  <inst-items>
    <Inst-list>
      <name>vxlan-90001</name>
      <encap>vxlan-90005</encap>
    </Inst-list>
  </inst-items>
</System>


CLI Commands

The CLI commands and options listed below are the equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.

vrf context vxlan-90001
 vni 90005

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring an Anycast Gateway for VXLAN Routing

This operation configures a distributed gateway virtual MAC address and associates the SVI with the anycast gateway.

Configuring an Anycast Gateway for VXLAN Routing

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "hmmEntity": {
          "children": [
            {
              "hmmFwdInst": {
                "attributes": {
                  "amac": "00:01:00:02:00:03"
                },
                "children": [
                  {
                    "hmmFwdIf": {
                      "attributes": {
                        "id": "vlan123",
                        "mode": "anycastGW"
}}}]}}]}},{
        "interfaceEntity": {
          "children": [
            {
              "sviIf": {
                "attributes": {
                  "id": "vlan123"
}}}]}},{
        "fmEntity": {
          "children": [
            {
              "fmInterfaceVlan": {
                "attributes": {
                  "adminSt": "enabled"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hmm-items>
    <fwdinst-items>
      <amac>00:01:00:02:00:03</amac>
      <if-items>
        <FwdIf-list>
          <id>vlan123</id>
          <mode>anycastGW</mode>
        </FwdIf-list>
      </if-items>
    </fwdinst-items>
  </hmm-items>
  <intf-items>
    <svi-items>
      <If-list>
        <id>vlan123</id>
      </If-list>
    </svi-items>
  </intf-items>
  <fm-items>
    <ifvlan-items>
      <adminSt>enabled</adminSt>
    </ifvlan-items>
  </fm-items>
</System>


CLI Commands

The CLI commands and options listed below are the equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.

feature interface-vlan
fabric forwarding anycast-gateway-mac 1.2.3
interface vlan123
  fabric forwarding mode anycast-gateway

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the NVE Interface and VNIs

Configuring the NVE Interface and VNIs

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "nvoEps": {
          "children": [
            {
              "nvoEp": {
                "attributes": {
                  "epId": "1",
                  "hostReach": "bgp",
                  "sourceInterface": "lo2"
},
"children": [
  {
    "nvoNws": {
      "children": [
        {
          "nvoNwRange": {
            "attributes": {
              "isLegacyMode": "no",
              "isMcastRange": "no",
              "mcastGroup": "225.4.0.1",
              "suppressARP": "no",
              "vniRangeMax": "5008",
              "vniRangeMin": "5000"
}}},{
  "nvoNw": {
    "attributes": {
      "isLegacyMode": "no",
      "vni": "4001"
    },
"children": [
  {
    "nvoIngRepl": {
      "attributes": {
        "proto": "bgp"
}}}]}},{
 "nvoNw": {
    "attributes": {
       "isLegacyMode": "no",
        "vni": "5000"
},
"children": [
{
"nvoIngRepl": {
   "attributes": {
      "proto": "static"
},
"children": [
  {
     "nvoConfigStIRPeer": {
       "attributes": {
         "ip": "1.1.1.1"
}}}]}}]}},{
  "nvoNw": {
    "attributes": {
      "associateVrfFlag": "yes",
      "isLegacyMode": "no",
      "vni": "90003"
}}}]}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <eps-items>
    <epId-items>
      <Ep-list>
        <epId>1</epId>
        <hostReach>bgp</hostReach>
        <sourceInterface>lo2</sourceInterface>
        <nws-items>
          <vni-items>
            <Nw-list>
              <vni>4001</vni>
              <isLegacyMode>false</isLegacyMode>
              <IngRepl-items>
                <proto>bgp</proto>
              </IngRepl-items>
            </Nw-list>
            <Nw-list>
              <vni>90003</vni>
              <associateVrfFlag>true</associateVrfFlag>
              <isLegacyMode>false</isLegacyMode>
            </Nw-list>
          </vni-items>
          <vnis-items>
            <NwRange-list>
              <vniRangeMin>5000</vniRangeMin>
              <vniRangeMax>5008</vniRangeMax>
              <isLegacyMode>false</isLegacyMode>
              <isMcastRange>false</isMcastRange>
              <mcastGroup>225.4.0.1</mcastGroup>
             <suppressARP>false</suppressARP> 
            </NwRange-list>
          </vnis-items>
        </nws-items>
      </Ep-list>
    </epId-items>
  </eps-items>
</System>

This operation performs the following configuration:

  • Configures a network virtualization edge (NVE) interface, which is the overlay interface that terminates VXLAN tunnels (only 1 NVE interface is allowed on the switch)
  • Defines BGP as the mechanism for host reachability advertisement
  • Adds an Layer 3 VNI to the overlay for a tenant VRF (required for VXLAN routing only)
  • Adds a Layer 2 VNI to the tunnel interface
  • Configures the multicast group on a per-VNI basis


CLI Commands

Static VNIs can only be configured without a host-reach BGP config.

The CLI commands and options listed below are the equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.

interface nve 1
 source-interface loopback 2
 host-reachability protocol bgp
 member vni 5000-5008   mcast-group 225.4.0.1
member vni 90003 associate-vrf
member vni 4001
 ingress-replication protocol bgp

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

Note: Starting with Cisco NX-OS Release 7.0.3I7(1), the nvoEps MO was added. To view the updated MOs and DNs, and for detailed information about classes and attributes described in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the Advertising of Virtual RMAC Capability for the VNI Member of an NVE Interface

Configuring the Advertising of Virtual RMAC Capability for the VNI Member of an NVE Interface

POST http://<mgmt0_IP>/api/mo/sys/eps.json

{
  "nvoEps": {
    "children": [
      {
        "nvoEp": {
          "attributes": {
            "advertiseVmac": "yes",
            "epId": "1"
          },
          "children": [
            {
              "nvoNws": {
                "children": [
                  {
                    "nvoNw": {
                      "attributes": {
                        "isLegacyMode": "no",
                        "vni": "123"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <eps-items>
    <epId-items>
      <Ep-list>
        <epId>1</epId>
        <advertiseVmac>true</advertiseVmac>
        <nws-items>
          <vni-items>
            <Nw-list>
              <vni>123</vni>
              <isLegacyMode>false</isLegacyMode>
            </Nw-list>
          </vni-items>
        </nws-items>
      </Ep-list>
    </epId-items>
  </eps-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface nve 1-1
 member vni 123
  advertise virtual-rmac

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting the Advertising of Virtual RMAC Capability for the VNI Member of an NVE Interface

Deleting the Advertising of Virtual RMAC Capability for the VNI Member of an NVE Interface

POST http://<mgmt0_IP>/api/mo/sys/eps.json

{
  "nvoEps": {
    "children": [
      {
        "nvoEp": {
          "attributes": {
            "advertiseVmac": "no",
            "epId": "1"
          },
          "children": [
            {
              "nvoNws": {
                "children": [
                  {
                    "nvoNw": {
                      "attributes": {
                        "isLegacyMode": "no",
                        "vni": "123"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <eps-items>
    <epId-items>
      <Ep-list>
        <epId>1</epId>
        <advertiseVmac>false</advertiseVmac>
        <nws-items>
          <vni-items>
            <Nw-list>
              <vni>123</vni>
              <isLegacyMode>false</isLegacyMode>
            </Nw-list>
          </vni-items>
        </nws-items>
      </Ep-list>
    </epId-items>
  </eps-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface nve 1-1
 member vni 123
  no advertise virtual-rmac

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Multisite Border-Gateway Interface for the VNI Member of an NVE Interface

Configuring a Multisite Border-Gateway Interface for the VNI Member of an NVE Interface

POST http://<mgmt0_IP>/api/mo/sys/eps.json

{
  "nvoEps": {
    "children": [
      {
        "nvoEp": {
          "attributes": {
            "epId": "1",
            "multisiteBordergwInterface": "lo123"
          },
          "children": [
            {
              "nvoNws": {
                "children": [
                  {
                    "nvoNw": {
                      "attributes": {
                        "isLegacyMode": "no",
                        "vni": "123"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <eps-items>
    <epId-items>
      <Ep-list>
        <epId>1</epId>
        <multisiteBordergwInterface>lo123</multisiteBordergwInterface>
        <nws-items>
          <vni-items>
            <Nw-list>
              <vni>123</vni>
              <isLegacyMode>false</isLegacyMode>
            </Nw-list>
          </vni-items>
        </nws-items>
      </Ep-list>
    </epId-items>
  </eps-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface nve 1-1
 member vni 123
  multisite border-gateway interface loopback 123

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Multisite Border-Gateway Interface for the VNI Member of an NVE Interface

Deleting a Multisite Border-Gateway Interface for the VNI Member of an NVE Interface

POST http://<mgmt0_IP>/api/mo/sys/eps.json

{
  "nvoEps": {
    "children": [
{
"nvoEp": {
  "attributes": {
    "epId": "1",
    "multisiteBordergwInterface": "unspecified"
},
"children": [
{
  "nvoNws": {
    "children": [
      {
        "nvoNw": {
          "attributes": {
            "isLegacyMode": "no",
            "vni": "123"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <eps-items>
    <epId-items>
      <Ep-list>
        <epId>1</epId>
        <multisiteBordergwInterface>unspecified</multisiteBordergwInterface>
        <nws-items>
          <vni-items>
            <Nw-list>
              <vni>123</vni>
              <isLegacyMode>false</isLegacyMode>
            </Nw-list>
          </vni-items>
        </nws-items>
      </Ep-list>
    </epId-items>
  </eps-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface nve 1-1
 member vni 123
  no multisite border-gateway interface loopback 123

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Multisite Ingress Replication for the VNI Member of an NVE Interface

Configuring Multisite Ingress Replication for the VNI Member of an NVE Interface

POST http://<mgmt0_IP>/api/mo/sys/eps.json

{
  "nvoEps": {
    "children": [
{
"nvoEp": {
  "attributes": {
    "epId": "1"
},
"children": [
{
  "nvoNws": {
    "children": [
      {
        "nvoNw": {
          "attributes": {
            "isLegacyMode": "no",
            "multisiteIngRepl": "enable",
            "vni": "123"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <eps-items>
    <epId-items>
      <Ep-list>
        <epId>1</epId>
        <nws-items>
          <vni-items>
            <Nw-list>
              <vni>123</vni>
              <isLegacyMode>false</isLegacyMode>
              <multisiteIngRepl>enable</multisiteIngRepl>
            </Nw-list>
          </vni-items>
        </nws-items>
      </Ep-list>
    </epId-items>
  </eps-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface nve 1-1
 member vni 123
  multisite ingress-replication

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Multisite Ingress Replication for the VNI Member of an NVE Interface

Deleting Multisite Ingress Replication for the VNI Member of an NVE Interface

POST http://<mgmt0_IP>/api/mo/sys/eps.json

{
  "nvoEps": {
    "children": [
{
"nvoEp": {
  "attributes": {
    "epId": "1"
},
"children": [
{
  "nvoNws": {
    "children": [
      {
        "nvoNw": {
          "attributes": {
            "isLegacyMode": "no",
            "multisiteIngRepl": "disable",
            "vni": "123"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <eps-items>
    <epId-items>
      <Ep-list>
        <epId>1</epId>
        <nws-items>
          <vni-items>
            <Nw-list>
              <vni>123</vni>
              <isLegacyMode>false</isLegacyMode>
              <multisiteIngRepl>disable</multisiteIngRepl>
            </Nw-list>
          </vni-items>
        </nws-items>
      </Ep-list>
    </epId-items>
  </eps-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface nve 1-1
 member vni 123
  no multisite ingress-replication

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Enabling an EVPN Multisite Border Gateway

Enabling an EVPN Multisite Border Gateway

POST http://<mgmt0_IP>/api/mo/sys/eps.json

{
"nvoEps": {
  "children": [
    {
      "nvoEvpnMultisiteBordergw": {
        "attributes": {
          "siteId": "123",
          "state": "enabled"
}}}]}}

{
    imdata:[]
}

<System>
  <eps-items>
    <multisite-items>
      <siteId>123</siteId>
      <state>enabled</state>
    </multisite-items>
  </eps-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

evpn multisite border-gateway 123

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Disabling an EVPN Multisite Border Gateway

Disabling an EVPN Multisite Border Gateway

POST http://<mgmt0_IP>/api/mo/sys/eps.json

      {
        "nvoEps": {
          "children": [
            {
              "nvoEvpnMultisiteBordergw": {
                "attributes": {
                  "status": "deleted"
}}}]}}

{
    imdata:[]
}

<System>
  <eps-items>
    <multisite-items xc:operation="delete">
    </multisite-items>
  </eps-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no evpn multisite border-gateway

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Enabling EVPN Multisite DCI Tracking on an Ethernet Interface

Enabling EVPN Multisite DCI Tracking on an Ethernet Interface

POST http://<mgmt0_IP>/api/mo/sys/intf.json

{
"interfaceEntity": {
  "children": [
    {
      "l1PhysIf": {
        "attributes": {
          "id": "eth1/3"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "tracking": "dci"

}}}]}}]}}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <multisiteiftracking-items>
          <tracking>dci</tracking>
        </multisiteiftracking-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface ethernet 1/3
 evpn multisite dci-tracking

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Disabling EVPN Multisite DCI Tracking on an Ethernet Interface

Disabling EVPN Multisite DCI Tracking on an Ethernet Interface

POST http://<mgmt0_IP>/api/mo/sys/intf.json

{
"interfaceEntity": {
  "children": [
    {
      "l1PhysIf": {
        "attributes": {
          "id": "eth1/3"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <multisiteiftracking-items xc:operation="delete">
        </multisiteiftracking-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface ethernet 1/3
 no evpn multisite dci-tracking

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Enabling EVPN Multisite Fabric Tracking on an Ethernet Interface

Enabling EVPN Multisite Fabric Tracking on an Ethernet Interface

POST http://<mgmt0_IP>/api/mo/sys/intf.json

{
"interfaceEntity": {
  "children": [
    {
      "l1PhysIf": {
        "attributes": {
          "id": "eth1/3"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "tracking": "fabric"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <multisiteiftracking-items>
          <tracking>fabric</tracking>
        </multisiteiftracking-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface ethernet 1/3
 evpn multisite fabric-tracking

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Disabling EVPN Multisite Fabric Tracking on an Ethernet Interface

Disabling EVPN Multisite Fabric Tracking on an Ethernet Interface

POST http://<mgmt0_IP>/api/mo/sys/intf.json

{
"interfaceEntity": {
  "children": [
    {
      "l1PhysIf": {
        "attributes": {
          "id": "eth1/3"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <multisiteiftracking-items xc:operation="delete">
        </multisiteiftracking-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface ethernet 1/3
 no evpn multisite fabric-tracking

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Enabling EVPN Multisite DCI Tracking on a Port-Channel Interface

Enabling EVPN Multisite DCI Tracking on a Port-Channel Interface

POST http://<mgmt0_IP>/api/mo/sys/intf.json

{
"interfaceEntity": {
  "children": [
    {
      "pcAggrIf": {
        "attributes": {
          "id": "po123"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "tracking": "dci"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <multisiteiftracking-items>
          <tracking>dci</tracking>
        </multisiteiftracking-items>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface port-channel 123
 evpn multisite dci-tracking

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Disabling EVPN Multisite DCI Tracking on a Port-Channel Interface

Disabling EVPN Multisite DCI Tracking on a Port-Channel Interface

POST http://<mgmt0_IP>/api/mo/sys/intf.json

{
"interfaceEntity": {
  "children": [
    {
      "pcAggrIf": {
        "attributes": {
          "id": "po123"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <multisiteiftracking-items xc:operation="delete">
        </multisiteiftracking-items>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX
  • N9K-N9K-93180YC-EX
  • N9K-N9K-C93108TC-EX

Note: This example was added in Release 7.0(3)I7(2).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

interface port-channel 123
 no evpn multisite dci-tracking

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Enabling EVPN Multisite Fabric Tracking on a Port-Channel Interface

Enabling EVPN Multisite Fabric Tracking on a Port-Channel Interface

POST http://<mgmt0_IP>/api/mo/sys/intf.json

{
"interfaceEntity": {
  "children": [
    {
      "pcAggrIf": {
        "attributes": {
          "id": "po123"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "tracking": "fabric"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <multisiteiftracking-items>
          <tracking>fabric</tracking>
        </multisiteiftracking-items>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
</System>

This is supported on the following switches:

  • N9K-C93180LC-EX

  • N9K-N9K-93180YC-EX

  • N9K-N9K-C93108TC-EX

    • Note: This example was added in Release 7.0(3)I7(2).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    interface port-channel 123
     evpn multisite fabric-tracking

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Disabling EVPN Multisite Fabric Tracking on a Port-Channel Interface

    Disabling EVPN Multisite Fabric Tracking on a Port-Channel Interface

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
"interfaceEntity": {
  "children": [
    {
      "pcAggrIf": {
        "attributes": {
          "id": "po123"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "status": "deleted"
}}}]}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <multisiteiftracking-items xc:operation="delete">
        </multisiteiftracking-items>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
</System>

    This is supported on the following switches:

    • N9K-C93180LC-EX
    • N9K-N9K-93180YC-EX
    • N9K-N9K-C93108TC-EX

    Note: This example was added in Release 7.0(3)I7(2).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    interface port-channel 123
     no evpn multisite fabric-tracking

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Enabling EVPN Multisite DCI Tracking on an Ethernet Interface Range

    Enabling EVPN Multisite DCI Tracking on an Ethernet Interface Range

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
"interfaceEntity": {
  "children": [
    {
      "l1PhysIf": {
        "attributes": {
          "id": "eth1/4"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "tracking": "dci"
}}}]}},{
  "l1PhysIf": {
    "attributes": {
      "id": "eth1/3"
    },
    "children": [
      {
        "nvoMultisiteIfTracking": {
          "attributes": {
            "tracking": "dci"
}}}]}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/4</id>
        <multisiteiftracking-items>
          <tracking>dci</tracking>
        </multisiteiftracking-items>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/3</id>
        <multisiteiftracking-items>
          <tracking>dci</tracking>
        </multisiteiftracking-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

    This is supported on the following switches:

    • N9K-C93180LC-EX
    • N9K-N9K-93180YC-EX
    • N9K-N9K-C93108TC-EX

    Note: This example was added in Release 7.0(3)I7(2).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    interface ethernet 1/3-4
     evpn multisite dci-tracking

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Disabling EVPN Multisite DCI Tracking on an Ethernet Interface Range

    Disabling EVPN Multisite DCI Tracking on an Ethernet Interface Range

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
"interfaceEntity": {
  "children": [
    {
      "l1PhysIf": {
        "attributes": {
          "id": "eth1/4"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "status": "deleted"
}}}]}},{
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                },
                "children": [
                  {
                    "nvoMultisiteIfTracking": {
                      "attributes": {
                        "status": "deleted"
}}}]}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/4</id>
        <multisiteiftracking-items xc:operation="delete">
        </multisiteiftracking-items>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/3</id>
        <multisiteiftracking-items xc:operation="delete">
        </multisiteiftracking-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

    This is supported on the following switches:

    • N9K-C93180LC-EX
    • N9K-N9K-93180YC-EX
    • N9K-N9K-C93108TC-EX

    Note: This example was added in Release 7.0(3)I7(2).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    interface ethernet 1/3-4
     no evpn multisite dci-tracking

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Enabling EVPN Multisite Fabric Tracking on an Ethernet Interface Range

    Enabling EVPN Multisite Fabric Tracking on an Ethernet Interface Range

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

          {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/4"
                },
                "children": [
                  {
                    "nvoMultisiteIfTracking": {
                      "attributes": {
                        "tracking": "fabric"
}}}]}},{
  "l1PhysIf": {
    "attributes": {
      "id": "eth1/3"
    },
    "children": [
      {
        "nvoMultisiteIfTracking": {
          "attributes": {
            "tracking": "fabric"
}}}]}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/4</id>
        <multisiteiftracking-items>
          <tracking>fabric</tracking>
        </multisiteiftracking-items>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/3</id>
        <multisiteiftracking-items>
          <tracking>fabric</tracking>
        </multisiteiftracking-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

    This is supported on the following switches:

    • N9K-C93180LC-EX
    • N9K-N9K-93180YC-EX
    • N9K-N9K-C93108TC-EX

    Note: This example was added in Release 7.0(3)I7(2).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    interface ethernet 1/3-4
     evpn multisite fabric-tracking

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Disabling EVPN Multisite Fabric Tracking on an Ethernet Interface Range

    Disabling EVPN Multisite Fabric Tracking on an Ethernet Interface Range

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
"interfaceEntity": {
  "children": [
    {
      "l1PhysIf": {
        "attributes": {
          "id": "eth1/4"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "status": "deleted"
}}}]}},{
"l1PhysIf": {
"attributes": {
  "id": "eth1/3"
},
"children": [
  {
    "nvoMultisiteIfTracking": {
      "attributes": {
        "status": "deleted"
}}}]}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/4</id>
        <multisiteiftracking-items xc:operation="delete">
        </multisiteiftracking-items>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/3</id>
        <multisiteiftracking-items xc:operation="delete">
        </multisiteiftracking-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

    This is supported on the following switches:

    • N9K-C93180LC-EX
    • N9K-N9K-93180YC-EX
    • N9K-N9K-C93108TC-EX

    Note: This example was added in Release 7.0(3)I7(2).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    interface ethernet 1/3-4
     no evpn multisite fabric-tracking

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Enabling EVPN Multisite DCI Tracking on a VLAN Interface

    Enabling EVPN Multisite DCI Tracking on a VLAN Interface

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
"interfaceEntity": {
  "children": [
    {
      "sviIf": {
        "attributes": {
          "id": "vlan123"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "tracking": "dci"
}}}]}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <svi-items>
      <If-list>
        <id>vlan123</id>
        <multisiteiftracking-items>
          <tracking>dci</tracking>
        </multisiteiftracking-items>
      </If-list>
    </svi-items>
  </intf-items>
</System>

    This is supported on the following switches:

    • N9K-C93180LC-EX
    • N9K-N9K-93180YC-EX
    • N9K-N9K-C93108TC-EX

    Note: This example was added in Release 7.0(3)I7(2).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    interface vlan 123
     evpn multisite dci-tracking

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Disabling EVPN Multisite DCI Tracking on a VLAN Interface

    Disabling EVPN Multisite DCI Tracking on a VLAN Interface

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
"interfaceEntity": {
  "children": [
    {
      "sviIf": {
        "attributes": {
          "id": "vlan123"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "status": "deleted"
}}}]}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <svi-items>
      <If-list>
        <id>vlan123</id>
        <multisiteiftracking-items xc:operation="delete">
        </multisiteiftracking-items>
      </If-list>
    </svi-items>
  </intf-items>
</System>

    This is supported on the following switches:

    • N9K-C93180LC-EX
    • N9K-N9K-93180YC-EX
    • N9K-N9K-C93108TC-EX

    Note: This example was added in Release 7.0(3)I7(2).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    interface vlan 123
     no evpn multisite dci-tracking

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Enabling EVPN Multisite Fabric Tracking on a VLAN Interface

    Enabling EVPN Multisite Fabric Tracking on a VLAN Interface

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
"interfaceEntity": {
  "children": [
    {
      "sviIf": {
        "attributes": {
          "id": "vlan123"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "tracking": "fabric"
}}}]}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <svi-items>
      <If-list>
        <id>vlan123</id>
        <multisiteiftracking-items>
          <tracking>fabric</tracking>
        </multisiteiftracking-items>
      </If-list>
    </svi-items>
  </intf-items>
</System>

    This is supported on the following switches:

    • N9K-C93180LC-EX
    • N9K-N9K-93180YC-EX
    • N9K-N9K-C93108TC-EX

    Note: This example was added in Release 7.0(3)I7(2).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    interface vlan 123
     evpn multisite fabric-tracking

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Disabling EVPN Multisite Fabric Tracking on a VLAN Interface

    Disabling EVPN Multisite Fabric Tracking on a VLAN Interface

    POST http://<mgmt0_IP>/api/mo/sys/intf.json

    {
"interfaceEntity": {
  "children": [
    {
      "sviIf": {
        "attributes": {
          "id": "vlan123"
        },
        "children": [
          {
            "nvoMultisiteIfTracking": {
              "attributes": {
                "status": "deleted"
}}}]}}]}}

    {
    imdata:[]
}

    <System>
  <intf-items>
    <svi-items>
      <If-list>
        <id>vlan123</id>
        <multisiteiftracking-items xc:operation="delete">
        </multisiteiftracking-items>
      </If-list>
    </svi-items>
  </intf-items>
</System>

    This is supported on the following switches:

    • N9K-C93180LC-EX
    • N9K-N9K-93180YC-EX
    • N9K-N9K-C93108TC-EX

    Note: This example was added in Release 7.0(3)I7(2).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    interface vlan 123
     no evpn multisite fabric-tracking

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Disabling VXLAN, BGP, and EVPN

    Disabling VXLAN, BGP, and EVPN

    POST http://<mgmt0_IP>/api/mo/sys.json

    {
  "topSystem": {
    "children": [
      {
        "fmEntity": {
          "children": [
            {
              "fmEvpn": {
                "attributes": {
                  "adminSt": "disabled"
}}},{
  "fmNvo": {
    "attributes": {
      "adminSt": "disabled"
}}},{
  "fmVnSegment": {
    "attributes": {
      "adminSt": "disabled"
}}}]}}]}}

    {
    imdata:[]
}

    <System>
  <fm-items>
    <evpn-items>
      <adminSt>disabled</adminSt>
    </evpn-items>
    <nvo-items>
      <adminSt>disabled</adminSt>
    </nvo-items>
    <vnsegment-items>
      <adminSt>disabled</adminSt>
    </vnsegment-items>
  </fm-items>
</System>


    CLI Commands

    The CLI commands and options listed below are the equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.

    no feature vn-segment
    no feature nv overlay
    no nv overlay evpn

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Querying Configuration and Operational Data

    Querying Configuration and Operational Data

    GET http://<IP_Address>/api/node/mo/sys/eps/epId-1.json?rsp-subtree=full

    Querying the NVE Interface Configuration and Operational Data

    {
"totalCount": "1",
"imdata": [
    {
        "nvoEp": {
            "attributes": {
                "adminSt": "enabled",
                "advertiseVmac": "no",
                "autoRemapReplicationServers": "no",
                "cfgSrc": "0",
                "childAction": "",
                "controllerId": "0",
                "descr": "",
                "dn": "sys/eps/epId-1",
                "encapType": "0",
                "epId": "1",
                "holdDownTime": "180",
                "holdDownTimerExpiryTime": "NA",
                "holdUpTime": "30",
                "holdUpTimerExpiryTime": "NA",
                "hostReach": "bgp",
                "learningMode": "CP",
                "mac": "F4:0F:1B:6F:F5:5B",
                "modTs": "2017-08-15T21:12:59.668+00:00",
                "monPolDn": "",
                "multisiteBordergwInterface": "unspecified",
                "operEncapType": "vxlan",
                "operState": "up",
                "persistentOnReload": "true",
                "propFaultBitmap": "",
                "sourceInterface": "lo2",
                "status": "",
                "uid": "0",
                "vpcVIPNotified": "no"
},
"children": [
{
"nvoPeers": {
    "attributes": {
        "childAction": "",
        "modTs": "2017-08-15T19:20:50.871+00:00",
        "monPolDn": "",
        "persistentOnReload": "true",
        "rn": "peers",
        "status": "",
        "uid": "0"
},
"children": [
{
"nvoDyIRPeer": {
    "attributes": {
        "createTs": "2017-08-15T21:45:15.593+00:00",
        "firstVNI": "0",
        "ip": "1.1.1.1",
        "mac": "00:00:00:00:00:00",
        "rn": "dyn_ir_peer-1.1.1.1",
        "state": "Up",
        "upStateTransitionTs": "2017-08-15T21:45:15.604+00:00"
}}},{
"nvoDyPeer": {
    "attributes": {
        "createTs": "2017-08-15T21:45:15.593+00:00",
        "firstVNI": "4001",
        "ip": "1.1.1.1",
        "mac": "50:87:89:D4:6B:B7",
        "rn": "dy_peer-1.1.1.1",
        "state": "Up",
        "upStateTransitionTs": "2017-08-15T21:45:15.604+00:00"
}}}]}},{
"nvoNws": {
    "attributes": {
        "childAction": "",
        "modTs": "2017-08-15T19:20:50.871+00:00",
        "monPolDn": "",
        "persistentOnReload": "true",
        "rn": "nws",
        "status": "",
        "uid": "0"
},
"children": [
{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "0.0.0.0",
        "rn": "opervni-90003",
        "state": "Up",
        "type": "L3",
        "vlanBD": "vlan-903",
        "vni": "90003"
}}},{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "225.4.0.1",
        "rn": "opervni-5007",
        "state": "Up",
        "type": "L2",
        "vlanBD": "vlan-507",
        "vni": "5007"
}}},{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "225.4.0.1",
        "rn": "opervni-5001",
        "state": "Up",
        "type": "L2",
        "vlanBD": "vlan-501",
        "vni": "5001"
}}},{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "225.4.0.1",
        "rn": "opervni-5003",
        "state": "Up",
        "type": "L2",
        "vlanBD": "vlan-503",
        "vni": "5003"
}}},{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "225.4.0.1",
        "rn": "opervni-5008",
        "state": "Up",
        "type": "L2",
        "vlanBD": "vlan-508",
        "vni": "5008"
}}},{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "225.4.0.1",
        "rn": "opervni-5005",
        "state": "Up",
        "type": "L2",
        "vlanBD": "vlan-505",
        "vni": "5005"
}}},{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "0.0.0.0",
        "rn": "opervni-4001",
        "state": "Up",
        "type": "L2",
        "vlanBD": "vlan-401",
        "vni": "4001"
}}},{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "225.4.0.1",
        "rn": "opervni-5002",
        "state": "Up",
        "type": "L2",
        "vlanBD": "vlan-502",
        "vni": "5002"
}}},{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "225.4.0.1",
        "rn": "opervni-5006",
        "state": "Up",
        "type": "L2",
        "vlanBD": "vlan-506",
        "vni": "5006"
}}},{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "225.4.0.1",
        "rn": "opervni-5004",
        "state": "Up",
        "type": "L2",
        "vlanBD": "vlan-504",
        "vni": "5004"
}}},{
"nvoOperNw": {
    "attributes": {
        "epId": "1",
        "mode": "CP",
        "operMcastGroup": "225.4.0.1",
        "rn": "opervni-5000",
        "state": "Up",
        "type": "L2",
        "vlanBD": "vlan-500",
        "vni": "5000"
}}},{
"nvoNwRange": {
    "attributes": {
        "associateVrfFlag": "no",
        "childAction": "",
        "isLegacyMode": "no",
        "isMcastRange": "no",
        "mcastGroup": "225.4.0.1",
        "modTs": "2017-08-15T19:21:03.043+00:00",
        "monPolDn": "",
        "multisiteIngRepl": "disable",
        "persistentOnReload": "true",
        "propFaultBitmap": "",
        "rn": "vnis-5000-5008",
        "status": "",
        "suppressARP": "no",
        "uid": "0",
        "vniRangeMax": "5008",
        "vniRangeMin": "5000"
}}},{
"nvoNw": {
    "attributes": {
        "associateVrfFlag": "no",
        "childAction": "",
        "isLegacyMode": "no",
        "mcastGroup": "0.0.0.0",
        "modTs": "2017-08-15T21:45:15.542+00:00",
        "monPolDn": "",
        "multisiteIngRepl": "disable",
        "persistentOnReload": "true",
        "propFaultBitmap": "",
        "rn": "vni-4001",
        "status": "",
        "suppressARP": "no",
        "uid": "0",
        "vni": "4001"
},
"children": [
{
"nvoIngRepl": {
    "attributes": {
        "childAction": "",
        "modTs": "2017-08-15T21:45:15.572+00:00",
        "monPolDn": "",
        "persistentOnReload": "true",
        "propFaultBitmap": "",
        "proto": "bgp",
        "rn": "IngRepl",
        "status": "",
        "uid": "0"
}}}]}},{
"nvoNw": {
    "attributes": {
        "associateVrfFlag": "yes",
        "childAction": "",
        "isLegacyMode": "no",
        "mcastGroup": "0.0.0.0",
        "modTs": "2017-08-15T19:20:51.075+00:00",
        "monPolDn": "",
        "multisiteIngRepl": "disable",
        "persistentOnReload": "true",
        "propFaultBitmap": "",
        "rn": "vni-90003",
        "status": "",
        "suppressARP": "no",
        "uid": "0",
        "vni": "90003"
}}}]}}]}}]}

    Note: Starting with Cisco NX-OS Release 7.0.3I7(1), the nvoEps MO was added. To view the updated MOs and DNs, and for detailed information about classes and attributes described in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html