Configuring NetFlow on a Port-Channel Interface

Configuring a Flow Monitor for IPv4 Ingress Traffic

Configuring a Flow Monitor for IPv4 Ingress Traffic

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "pcAggrIf": {
                "attributes": {
                  "id": "po123",
                  "layer": "Layer3",
                  "medium": "p2p",
                  "userCfgdFlags": "admin_layer"
                }
              }
            }
          ]
        }
      },
      {
        "analyticsHwTelemetry": {
          "children": [
            {
              "netflowNetflow": {
                "children": [
                  {
                    "netflowInst": {
                      "attributes": {
                        "mode": "netflow"
                      },
                      "children": [
                        {
                          "netflowFwdInstTarget": {
                            "attributes": {
                              "id": "369098874"
                            },
                            "children": [
                              {
                                "netflowRsMonitorAtt": {
                                  "attributes": {
                                    "tDn": "sys/hwtelemetry/netflow/inst-netflow/monitor-mon_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <layer>Layer3</layer>
        <medium>p2p</medium>
        <userCfgdFlags>admin_layer</userCfgdFlags>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <fwdinst-items>
            <FwdInstTarget-list>
              <id>369098874</id>
              <rsmonitorAtt-items>
                <RsMonitorAtt-list>
                  <tDn>/System/hwtelemetry-items/netflow-items/inst-items/Inst-list[mode='netflow']/monitor-items/Monitor-list[name='mon_1']</tDn>
                </RsMonitorAtt-list>
              </rsmonitorAtt-items>
            </FwdInstTarget-list>
          </fwdinst-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.

interface port-channel 123
 no switchport
  medium p2p
  ip flow monitor mon_1 input

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 Monitor for IPv4 Ingress Traffic

Deleting a Flow Monitor for IPv4 Ingress Traffic

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "pcAggrIf": {
                "attributes": {
                  "id": "po123",
                  "layer": "Layer3",
                  "medium": "p2p",
                  "userCfgdFlags": "admin_layer"
                }
              }
            }
          ]
        }
      },
      {
        "analyticsHwTelemetry": {
          "children": [
            {
              "netflowNetflow": {
                "children": [
                  {
                    "netflowInst": {
                      "attributes": {
                        "mode": "netflow"
                      },
                      "children": [
                        {
                          "netflowFwdInstTarget": {
                            "attributes": {
                              "id": "369098874"
                            },
                            "children": [
                              {
                                "netflowRsMonitorAtt": {
                                  "attributes": {
                                    "status": "deleted",
                                    "tDn": "sys/hwtelemetry/netflow/inst-netflow/monitor-mon_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <layer>Layer3</layer>
        <medium>p2p</medium>
        <userCfgdFlags>admin_layer</userCfgdFlags>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <fwdinst-items>
            <FwdInstTarget-list>
              <id>369098874</id>
              <rsmonitorAtt-items>
                <RsMonitorAtt-list xc:operation="delete">
                  <tDn>/System/hwtelemetry-items/netflow-items/inst-items/Inst-list[mode='netflow']/monitor-items/Monitor-list[name='mon_1']</tDn>
                </RsMonitorAtt-list>
              </rsmonitorAtt-items>
            </FwdInstTarget-list>
          </fwdinst-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.

interface port-channel 123
 no switchport
  medium p2p
  no ip flow monitor mon_1 input

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

Configuring a Flow Monitor for IPv6 Ingress Traffic

Configuring a Flow Monitor for IPv6 Ingress Traffic

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "pcAggrIf": {
                "attributes": {
                  "id": "po123",
                  "layer": "Layer3",
                  "medium": "p2p",
                  "userCfgdFlags": "admin_layer"
                }
              }
            }
          ]
        }
      },
      {
        "analyticsHwTelemetry": {
          "children": [
            {
              "netflowNetflow": {
                "children": [
                  {
                    "netflowInst": {
                      "attributes": {
                        "mode": "netflow"
                      },
                      "children": [
                        {
                          "netflowFwdInstTarget": {
                            "attributes": {
                              "id": "369098874"
                            },
                            "children": [
                              {
                                "netflowRsMonitorAtt": {
                                  "attributes": {
                                    "tDn": "sys/hwtelemetry/netflow/inst-netflow/monitor-mon_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <layer>Layer3</layer>
        <medium>p2p</medium>
        <userCfgdFlags>admin_layer</userCfgdFlags>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <fwdinst-items>
            <FwdInstTarget-list>
              <id>369098874</id>
              <rsmonitorAtt-items>
                <RsMonitorAtt-list>
                  <tDn>/System/hwtelemetry-items/netflow-items/inst-items/Inst-list[mode='netflow']/monitor-items/Monitor-list[name='mon_1']</tDn>
                </RsMonitorAtt-list>
              </rsmonitorAtt-items>
            </FwdInstTarget-list>
          </fwdinst-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.

interface port-channel 123
 no switchport
  medium p2p
  ipv6 flow monitor mon_1 input

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 Monitor for IPv6 Ingress Traffic

Deleting a Flow Monitor for IPv6 Ingress Traffic

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "pcAggrIf": {
                "attributes": {
                  "id": "po123",
                  "layer": "Layer3",
                  "medium": "p2p",
                  "userCfgdFlags": "admin_layer"
                }
              }
            }
          ]
        }
      },
      {
        "analyticsHwTelemetry": {
          "children": [
            {
              "netflowNetflow": {
                "children": [
                  {
                    "netflowInst": {
                      "attributes": {
                        "mode": "netflow"
                      },
                      "children": [
                        {
                          "netflowFwdInstTarget": {
                            "attributes": {
                              "id": "369098874"
                            },
                            "children": [
                              {
                                "netflowRsMonitorAtt": {
                                  "attributes": {
                                    "status": "deleted",
                                    "tDn": "sys/hwtelemetry/netflow/inst-netflow/monitor-mon_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
        <layer>Layer3</layer>
        <medium>p2p</medium>
        <userCfgdFlags>admin_layer</userCfgdFlags>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <fwdinst-items>
            <FwdInstTarget-list>
              <id>369098874</id>
              <rsmonitorAtt-items>
                <RsMonitorAtt-list xc:operation="delete">
                  <tDn>/System/hwtelemetry-items/netflow-items/inst-items/Inst-list[mode='netflow']/monitor-items/Monitor-list[name='mon_1']</tDn>
                </RsMonitorAtt-list>
              </rsmonitorAtt-items>
            </FwdInstTarget-list>
          </fwdinst-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.

interface port-channel 123
 no switchport
  medium p2p
  no ipv6 flow monitor mon_1 input

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

Configuring a Flow Monitor for IPv4 Ingress Traffic

Configuring a Flow Monitor for IPv4 Ingress Traffic

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "pcAggrIf": {
                "attributes": {
                  "id": "po123"
                }
              }
            }
          ]
        }
      },
      {
        "analyticsHwTelemetry": {
          "children": [
            {
              "netflowNetflow": {
                "children": [
                  {
                    "netflowInst": {
                      "attributes": {
                        "mode": "netflow"
                      },
                      "children": [
                        {
                          "netflowFwdInstTarget": {
                            "attributes": {
                              "id": "369098874"
                            },
                            "children": [
                              {
                                "netflowRsMonitorAtt": {
                                  "attributes": {
                                    "tDn": "sys/hwtelemetry/netflow/inst-netflow/monitor-mon_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <fwdinst-items>
            <FwdInstTarget-list>
              <id>369098874</id>
              <rsmonitorAtt-items>
                <RsMonitorAtt-list>
                  <tDn>/System/hwtelemetry-items/netflow-items/inst-items/Inst-list[mode='netflow']/monitor-items/Monitor-list[name='mon_1']</tDn>
                </RsMonitorAtt-list>
              </rsmonitorAtt-items>
            </FwdInstTarget-list>
          </fwdinst-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.

interface port-channel 123
 ip flow monitor mon_1 input

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 Monitor for IPv4 Ingress Traffic

Deleting a Flow Monitor for IPv4 Ingress Traffic

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "pcAggrIf": {
                "attributes": {
                  "id": "po123"
                }
              }
            }
          ]
        }
      },
      {
        "analyticsHwTelemetry": {
          "children": [
            {
              "netflowNetflow": {
                "children": [
                  {
                    "netflowInst": {
                      "attributes": {
                        "mode": "netflow"
                      },
                      "children": [
                        {
                          "netflowFwdInstTarget": {
                            "attributes": {
                              "id": "369098874"
                            },
                            "children": [
                              {
                                "netflowRsMonitorAtt": {
                                  "attributes": {
                                    "status": "deleted",
                                    "tDn": "sys/hwtelemetry/netflow/inst-netflow/monitor-mon_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <fwdinst-items>
            <FwdInstTarget-list>
              <id>369098874</id>
              <rsmonitorAtt-items>
                <RsMonitorAtt-list xc:operation="delete">
                  <tDn>/System/hwtelemetry-items/netflow-items/inst-items/Inst-list[mode='netflow']/monitor-items/Monitor-list[name='mon_1']</tDn>
                </RsMonitorAtt-list>
              </rsmonitorAtt-items>
            </FwdInstTarget-list>
          </fwdinst-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.

interface port-channel 123
 no ip flow monitor mon_1 input

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

Configuring a Flow Monitor for IPv6 Ingress Traffic

Configuring a Flow Monitor for IPv6 Ingress Traffic

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "pcAggrIf": {
                "attributes": {
                  "id": "po123"
                }
              }
            }
          ]
        }
      },
      {
        "analyticsHwTelemetry": {
          "children": [
            {
              "netflowNetflow": {
                "children": [
                  {
                    "netflowInst": {
                      "attributes": {
                        "mode": "netflow"
                      },
                      "children": [
                        {
                          "netflowFwdInstTarget": {
                            "attributes": {
                              "id": "369098874"
                            },
                            "children": [
                              {
                                "netflowRsMonitorAtt": {
                                  "attributes": {
                                    "tDn": "sys/hwtelemetry/netflow/inst-netflow/monitor-mon_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <fwdinst-items>
            <FwdInstTarget-list>
              <id>369098874</id>
              <rsmonitorAtt-items>
                <RsMonitorAtt-list>
                  <tDn>/System/hwtelemetry-items/netflow-items/inst-items/Inst-list[mode='netflow']/monitor-items/Monitor-list[name='mon_1']</tDn>
                </RsMonitorAtt-list>
              </rsmonitorAtt-items>
            </FwdInstTarget-list>
          </fwdinst-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.

interface port-channel 123
 ipv6 flow monitor mon_1 input

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 Monitor for IPv6 Ingress Traffic

Deleting a Flow Monitor for IPv6 Ingress Traffic

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "pcAggrIf": {
                "attributes": {
                  "id": "po123"
                }
              }
            }
          ]
        }
      },
      {
        "analyticsHwTelemetry": {
          "children": [
            {
              "netflowNetflow": {
                "children": [
                  {
                    "netflowInst": {
                      "attributes": {
                        "mode": "netflow"
                      },
                      "children": [
                        {
                          "netflowFwdInstTarget": {
                            "attributes": {
                              "id": "369098874"
                            },
                            "children": [
                              {
                                "netflowRsMonitorAtt": {
                                  "attributes": {
                                    "status": "deleted",
                                    "tDn": "sys/hwtelemetry/netflow/inst-netflow/monitor-mon_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <aggr-items>
      <AggrIf-list>
        <id>po123</id>
      </AggrIf-list>
    </aggr-items>
  </intf-items>
  <hwtelemetry-items>
    <netflow-items>
      <inst-items>
        <Inst-list>
          <mode>netflow</mode>
          <fwdinst-items>
            <FwdInstTarget-list>
              <id>369098874</id>
              <rsmonitorAtt-items>
                <RsMonitorAtt-list xc:operation="delete">
                  <tDn>/System/hwtelemetry-items/netflow-items/inst-items/Inst-list[mode='netflow']/monitor-items/Monitor-list[name='mon_1']</tDn>
                </RsMonitorAtt-list>
              </rsmonitorAtt-items>
            </FwdInstTarget-list>
          </fwdinst-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.

interface port-channel 123
 no ipv6 flow monitor mon_1 input

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