Is Netflow supported for physical ports on Nexus 6000?
We have a Cisco Nexus 6000 switch and have been using Netflow commands on it.
Those commands can only be applied on Interface Vlans, it seems, not on physical ports.
We are also using Scrutinizer (Plixer) as the flow collector.
Our switch's interface Vlan 253 is configured as follows:
interface Vlan10 description SERVER no shutdown ip flow monitor NEXUS6000 input sampler WORD no ip redirects ip address 10.0.0.1/24
Now, we have a server connected to a switchport of the same Vlan, with IP address 10.0.0.50.
That server is sending much backup traffic every day, which exits from switch port Eth1/30, with a rate of 15Mbps.
The result is that Scrutinizer shows only traffic concerning interface Vlan10 (10.0.0.1/24) and thus we cannot see this whole amount of 15Mbps of traffic. Instead, we see just some minor traffic of 1Mbps, which apparently matches interface Vlan10.
1. Can we confirm that Nexus 6000 do not support netflow for physical ports?
2. I am apparently missing something very basic in the fact that a server's traffic is not displayed while we are monitoring the respective interface Vlan's traffic. I suspect that since we are monitoring the interface vlan via Netflow, in Scrutinizer we will just see the traffic originating and terminating to that Vlan's IP address (10.0.0.1/24) and not ANY other traffic from a server within the same Vlan. Is that correct?
Want roadmaps? Are you headed to Cisco Live? You're in luck!
As a member of the Data Center Customer Connection program (CCP) you have access to roadmap sessions exclusively at Cisco Live if you've registered for a full conference pass. Not a Data ...
Membership in the Cisco Customer Connection program is required to attend. Registration is free and easy to complete. During registration, choose the Data Center track. Once your membership is approved, you'll be able to register for thi...
By Andrew Boring
When you’re using curl to interact with the APIC API, or even if you’re using a toolkit/library to create applications, you may want to know which APIC API methods and objects are available for a given task.
Yeah, yeah. RTFM. You know wha...
The vast majority of ACI customers do not start out with an Application Centric deployment of ACI; mainly because they do not have a clear understanding of their applications and the vast amount of interdependencies.
However, with the advent of T...
Hey folks! Welcome to another blog where we tackle yet again, another ACI topic.
I was going to create a detailed configuration guide for Multi-Pod, however, after checking out the Cisco ACI MultiPod Configuration Whitepaper on CCO, I rea...