Configuring Flow Records

Configuring a Flow Record

Configuring a Flow Record

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "name": "record_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>record_1</name>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(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.

flow record record_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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
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 a Flow Record

Deleting a Flow Record

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "name": "record_1",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list xc:operation="delete">
              <name>record_1</name>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no flow record record_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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Number of Bytes in a Flow as a Non-Key Field for a Flow Record

Configuring the Number of Bytes in a Flow as a Non-Key Field for a Flow Record

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "count-bytes",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect>count-bytes</collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
collect counter bytes

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Number of Bytes in a Flow as a Non-Key Field for a Flow Record

Deleting the Number of Bytes in a Flow as a Non-Key Field for a Flow Record

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect></collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no collect counter bytes

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Number of Packets Using a 64-bit Counter

Configuring the Number of Packets Using a 64-bit Counter

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "count-pkts-long",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect>count-pkts-long</collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
collect counter packets long

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Number of Packets Using a 64-bit Counter

Deleting the Number of Packets Using a 64-bit Counter

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect></collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no collect counter packets long

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Value in the IPv4 Version Field

Configuring the Value in the IPv4 Version Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "ip-version",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect>ip-version</collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
collect ip version

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Value in the IPv4 Version Field

Deleting the Value in the IPv4 Version Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect></collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no collect ip version

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the System Uptime of the First Seen Packet

Configuring the System Uptime of the First Seen Packet

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "ts-first",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect>ts-first</collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
collect timestamp sys-uptime first

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the System Uptime of the First Seen Packet

Deleting the System Uptime of the First Seen Packet

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect></collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no collect timestamp sys-uptime first

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the System Uptime of the Last Seen Packet

Configuring the System Uptime of the Last Seen Packet

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "ts-recent",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect>ts-recent</collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
collect timestamp sys-uptime last

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the System Uptime of the Last Seen Packet

Deleting the System Uptime of the Last Seen Packet

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect></collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no collect timestamp sys-uptime last

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring TCP Fields as a Non-Key Field

Configuring TCP Fields as a Non-Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "tcp-flags",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect>tcp-flags</collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
collect transport tcp flags

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting TCP Fields as a Non-Key Field

Deleting TCP Fields as a Non-Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "collect": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <collect></collect>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no collect transport tcp flags

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Source MAC Address as a Key Field

Configuring the Source MAC Address as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "src-mac",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>src-mac</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match datalink mac source-address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Source MAC Address as a Key Field

Deleting the Source MAC Address as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match datalink mac source-address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Destination MAC Address as a Key Field

Configuring the Destination MAC Address as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "dst-mac",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>dst-mac</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match datalink mac destination-address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Destination MAC Address as a Key Field

Deleting the Destination MAC Address as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match datalink mac destination-address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Ethertype as a key Field

Configuring the Ethertype as a key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "ethertype",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>ethertype</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match datalink ethertype

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Ethertype as a Key Field

Deleting the Ethertype as a key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match datalink ethertype

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the VLAN ID as a Key Field

Configuring the VLAN ID as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "vlan",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>vlan</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match datalink vlan

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the VLAN ID as a Key Field

Deleting the VLAN ID as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match datalink vlan

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the IPv4 Protocol as a Key Field

Configuring the IPv4 Protocol as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "proto",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>proto</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match ip protocol

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the IPv4 Protocol as a Key Field

Deleting the IPv4 Protocol as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match ip protocol

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the IPv4 ToS as a Key Field

Configuring the IPv4 ToS as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "tos",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>tos</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match ip tos

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the IPv4 ToS as a Key Field

Deleting the IPv4 ToS as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match ip tos

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the IPv4 Source Address as Key Field

Configuring the IPv4 Source Address as Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "src-ipv4",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>src-ipv4</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match ipv4 source address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the IPv4 Source Address as Key Field

Deleting the IPv4 Source Address as Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match ipv4 source address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the IPv4 Destination Address as a Key Field

Configuring the IPv4 Destination Address as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "dst-ipv4",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>dst-ipv4</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match ipv4 destination address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the IPv4 Destination Address as a Key Field

Deleting the IPv4 Destination Address as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match ipv4 destination address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the IPv6 Source Address as a Key Field

Configuring the IPv6 Source Address as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "src-ipv6",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>src-ipv6</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match ipv6 source address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the IPv6 Source Address as a Key Field

Deleting the IPv6 Source Address as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match ipv6 source address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the IPv6 Destination Address as a Key Field

Configuring the IPv6 Destination Address as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "dst-ipv6",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>dst-ipv6</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match ipv6 destination address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the IPv6 Destination Address as a Key Field

Deleting the IPv6 Destination Address as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match ipv6 destination address

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the IPv6 Flow Label as a Key Field

Configuring the IPv6 Flow Label as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match ipv6 flow-label

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the IPv6 flow label as a Key Field

Deleting the IPv6 flow label as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match ipv6 flow-label

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring IPv6 Options as a Key Field

Configuring IPv6 Options as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "opt-ipv6",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>opt-ipv6</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match ipv6 options

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting IPv6 Options as a Key Field

Deleting IPv6 Options as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match ipv6 options

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Transport Destination Port as a Key Field

Configuring the Transport Destination Port as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "dst-port",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>dst-port</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match transport destination-port

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Transport Destination Port as a Key Field

Deleting the Transport Destination Port as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match transport destination-port

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Transport Source Port as a Key Field

Configuring the Transport Source Port as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "src-port",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match>src-port</match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
match transport source-port

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Transport Source Port as a Key Field

Deleting the Transport Source Port as a Key Field

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "match": "",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <match></match>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no match transport source-port

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring a Description

Configuring a Description

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "descr": "Some description text 123",
                  "name": "Flow_Rec_1"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list>
              <name>Flow_Rec_1</name>
              <descr>Some description text 123</descr>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
description Some description text 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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting a Description

Deleting a Description

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

{
  "netflowNetflow": {
    "children": [
      {
        "netflowInst": {
          "attributes": {
            "mode": "netflow"
          },
          "children": [
            {
              "netflowRecordP": {
                "attributes": {
                  "name": "Flow_Rec_1",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <recordp-items>
            <RecordP-list xc:operation="delete">
              <name>Flow_Rec_1</name>
            </RecordP-list>
          </recordp-items>
        </Inst-list>
      </inst-items>
    </netflow-items>
  </hwtelemetry-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

flow record Flow_Rec_1
no description

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html