Configuring System Routing

Configuring the Maximum Layer-3 Host Routes

Configuring the Maximum Layer-3 Host Routes
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "DEFAULT"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>DEFAULT</routingMode>
  </pltfm-items>
</System>


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.

system routing max-mode host

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/media/dme/index.html

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 the Maximum Layer-3 Host Routes

Deleting the the Maximum Layer-3 Host Routes
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "DEFAULT"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>DEFAULT</routingMode>
  </pltfm-items>
</System>


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 system routing max-mode host

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/media/dme/index.html

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 Maximum Layer-2 Records and Fewer Layer-3 Host Routes

Configuring the Maximum Layer-2 Records and Fewer Layer-3 Host Routes
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "TOR_MAX_L2"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>TOR_MAX_L2</routingMode>
  </pltfm-items>
</System>


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.

system routing max-mode-tor l2

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/media/dme/index.html

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 Maximum Layer-2 Records and Fewer Layer-3 Host Routes

Deleting the Maximum Layer-2 Records and Fewer Layer-3 Host Routes
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "DEFAULT"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>DEFAULT</routingMode>
  </pltfm-items>
</System>


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 system routing max-mode-tor l2

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/media/dme/index.html

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 Max-Host Routing Mode

Configuring Max-Host Routing Mode
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "TOR_MAX_L3"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>TOR_MAX_L3</routingMode>
  </pltfm-items>
</System>

Puts the line cards in Broadcom T2 mode 2 and the fabric modules in Broadcom T2 mode 3 to increase the number of supported hosts.


CLI Command

The CLI command below is the equivalent to the payload example 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.

system routing max-mode l3

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 Layer-3 Longest-Prefix-Match (LPM) Routes

Configuring the Layer-3 Longest-Prefix-Match (LPM) Routes
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "TOR_MAX_L3"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>TOR_MAX_L3</routingMode>
  </pltfm-items>
</System>


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.

system routing max-mode-tor l3

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/media/dme/index.html

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 Layer-3 Longest-Prefix-Match (LPM) Routes

Deleting the Layer-3 Longest-Prefix-Match (LPM) Routes
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "DEFAULT"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>DEFAULT</routingMode>
  </pltfm-items>
</System>


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 system routing max-mode-tor l3

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/media/dme/index.html

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 Balance of Both Layer-2 records and Layer-3 Host Routes

Configuring the Balance of Both Layer-2 records and Layer-3 Host Routes
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "TOR_MAX_L2L3"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>TOR_MAX_L2L3</routingMode>
  </pltfm-items>
</System>


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.

system routing max-mode-tor l2-l3

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/media/dme/index.html

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 Configured Balance of Both Layer-2 records and Layer-3 Host Routes

Deleting the Configured Balance of Both Layer-2 records and Layer-3 Host Routes
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "DEFAULT"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>DEFAULT</routingMode>
  </pltfm-items>
</System>


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 system routing max-mode-tor l2-l3

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/media/dme/index.html

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 Layer-3 Longest-Prefix-Match (LPM) Routes for a Host Routing on LC and LPM Routing in Fabric Modules

Deleting Layer-3 Longest-Prefix-Match (LPM) Routes for a Host Routing on LC and LPM Routing in Fabric Modules
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "DEFAULT"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>DEFAULT</routingMode>
  </pltfm-items>
</System>


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 system routing hierarchical def-max-mode l3 64b-alpm

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/media/dme/index.html

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 Layer-3 Longest-Prefix-Match (LPM) Routes with Host Routing Disabled on LC and LPM Routing in Fabric Modules

Deleting Layer-3 Longest-Prefix-Match (LPM) Routes with Host Routing Disabled on LC and LPM Routing in Fabric Modules
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "routingMode": "DEFAULT"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <routingMode>DEFAULT</routingMode>
  </pltfm-items>
</System>


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 system routing non-hierarchical max-mode l3-nh 64b-alpm-nh

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/media/dme/index.html

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 ALPM for IPv6

Configuring ALPM for IPv6 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "IPV6alpmCarveValue": "4096"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <IPV6alpmCarveValue>4096</IPV6alpmCarveValue>
  </pltfm-items>
</System>

Enables /128 IPv6 routes and carves the LPM table for all IPv6 entries.


CLI Command

The CLI command below is the equivalent to the payload example 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.

hardware profile ipv6 alpm carve-value 4096

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 Latency Monitor

Configuring the Latency Monitor
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "children": [
            {
              "platformLatencyMonitor": {
                "attributes": {
                  "latencyMonitorState": "Enable",
                  "latencyMonitorThreshholdAvg": "1000000",
                  "latencyMonitorThreshholdMax": "2000000",
                  "sampling": "3"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <latencymonitor-items>
      <latencyMonitorState>Enable</latencyMonitorState>
      <latencyMonitorThreshholdAvg>1000000</latencyMonitorThreshholdAvg>
      <latencyMonitorThreshholdMax>2000000</latencyMonitorThreshholdMax>
      <sampling>3</sampling>
    </latencymonitor-items>
  </pltfm-items>
</System>


CLI Commands

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

hardware profile latency monitor

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 Latency Monitor

Deleting the Latency Monitor
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "children": [
            {
              "platformLatencyMonitor": {
                "attributes": {
                  "latencyMonitorState": "Disable",
                  "latencyMonitorThreshholdAvg": "1000000",
                  "latencyMonitorThreshholdMax": "2000000",
                  "sampling": "3"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <latencymonitor-items>
      <latencyMonitorState>Disable</latencyMonitorState>
      <latencyMonitorThreshholdAvg>1000000</latencyMonitorThreshholdAvg>
      <latencyMonitorThreshholdMax>2000000</latencyMonitorThreshholdMax>
      <sampling>3</sampling>
    </latencymonitor-items>
  </pltfm-items>
</System>


CLI Commands

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

no hardware profile latency monitor

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 Buffer Monitor (Multicast Sampling Interval in Nano-Seconds and Histogram Threshold)

Configuring the Buffer Monitor (Multicast Sampling Interval in Nano-Seconds and Histogram Threshold)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "children": [
            {
              "platformBufferMonitor": {
                "attributes": {
                  "bufferMonitorMode": "Multicast",
                  "bufferMonitorState": "Enable",
                  "bufferMonitorThreshhold": "567",
                  "sampling": "456"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
    <buffermonitor-items>
      <bufferMonitorMode>Multicast</bufferMonitorMode>
      <bufferMonitorState>Enable</bufferMonitorState>
      <bufferMonitorThreshhold>567</bufferMonitorThreshhold>
      <sampling>456</sampling>
    </buffermonitor-items>
  </pltfm-items>
</System>


CLI Commands

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

hardware profile buffer monitor multicast sampling 456 threshold 567

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 Buffer Monitor (Unicast Sampling Interval in Nano-Seconds and Histogram Threshold)

Configuring the Buffer Monitor (Unicast Sampling Interval in Nano-Seconds and Histogram Threshold)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "children": [
            {
              "platformBufferMonitor": {
                "attributes": {
                  "bufferMonitorMode": "Unicast",
                  "bufferMonitorState": "Enable",
                  "bufferMonitorThreshhold": "456",
                  "sampling": "123"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <buffermonitor-items>
      <bufferMonitorMode>Unicast</bufferMonitorMode>
      <bufferMonitorState>Enable</bufferMonitorState>
      <bufferMonitorThreshhold>456</bufferMonitorThreshhold>
      <sampling>123</sampling>
    </buffermonitor-items>
  </pltfm-items>
</System>


CLI Commands

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

hardware profile buffer monitor unicast sampling 123 threshold 456

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 Service-Reflect Loopback Port

Configuring the Service-Reflect Loopback Port
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "multicastServiceReflectPort": "1"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <multicastServiceReflectPort>1</multicastServiceReflectPort>
  </pltfm-items>
</System>


CLI Commands

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

hardware profile multicast service-reflect port 1

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 Service-Reflect Loopback Port

 Deleting the Service-Reflect Loopback Port
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "multicastServiceReflectPort": "0"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <multicastServiceReflectPort>0</multicastServiceReflectPort>
  </pltfm-items>
</System>


CLI Commands

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

no hardware profile multicast service-reflect port 1

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