![]() N7K1(config-if)# ip flow monitor netflow-monitor-1 inputĮRROR: A sampler must be configured for an interface on an F2 card or F2e mixed vdc An error will prompt when trying to configure this in a mixed environment: N7K1(config)# interface vlan 10 The CPU will automatically rate limit netflow traffic to 1 out of a 1000 packets to protect the control plane. Due to the 元 proxy routing required for F2(e), netflow traffic is CPU processed. Netflow samplers become important when you’re running mixed M1/F2(e) VDCs. Apply the Netflow Monitor to the your 元 interfaces interface eth3/10 You can also apply multiple exporters to the same monitor: flow monitor netflow-monitor-3ĥ. Or you can use the built-in Netflow Flow Record: flow monitor netflow-monitor-2 flow exporter exporter-1įlow Monitors bind the Flow Record to the Flow Exporter flow monitor netflow-monitor-1 You can create a custom record, or use the built in record.īuilt-in: N7K1# show flow record netflow-originalĭescription: Traditional IPv4 input NetFlow with origin ASsĬreate your own: flow record custom-netflow-recordįlow exporters are your colletors, where you send the exported flow information to. (Optional) Configure a Netflow SamplerĪ Netflow record details what information you want to collect. Apply the Netflow Monitor to the your 元 interfacesĦ. Unlike IOS, there are few steps involved to get Netflow functioning, here is a quick run down:ĥ. For CCIE:DC purposes, an understanding of how NetFlow is configured in NXOS cannot hurt, especially since it is mentioned in the blueprint (1.5.b – Implement Netflow). This post is a part of my CCIE:DC studies, but will be useful for anyone needing to quickly configure NetFlow in NXOS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |