Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Does NTA 4.0.1 supported nexus 3000?

joapple

how to enable netflow/sflow for this device?

thanks

Find more posts tagged with

Accepted answers

All comments

cnorborg

Looks like the Nexus 3000 is using SFlow, not Netflow. Interesting. Here is an article on how to configure it:

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/system_mgmt/503_U5_1/b_3k_System_Mgmt_Config_503_u5_1/b_3k_System_Mgmt_Config_503_u5_1_chapter_010010.html#d10764e267a1635

This might help too...

https://thwack.solarwinds.com/docs/DOC-173673

joapple

Hi, thanks for the info. I already configure the following sflow commands but still NTA cannot received data.

cnorborg

Ok, not familiar with sFlow or the Nexus 3000, but with Netflow, its usually very simple to get it to export records, but sometimes not in a way the server can recognize. The first thing to do is to see whether or not packets are going out. I believe "show sflow statistics" will do the trick. If the counters are not-zero and counting upwards, that means that the packets are going out, but that they're either going to the wrong place, or not being recognized for what they are.

The two big things to check are the port that your sending the traffic to, and the IP your sending traffic from.

Most Orion systems expect Netflow traffic on port 2055. You can check this by going to "Settings" / "NTA Settings" and seeing what it says under "Netflow Collector Services" under "Collection Ports". I'd recommend leaving the server on 2055 and changing the output from the Nexus. I believe that would be done with "sflow collector-port 2055".

The next thing that is usually forgotten is making sure the sflow packets are going out using the same interface that you managed your device with. For Layer-3 devices its usually best practice to make a loopback interface, lets say the IP of that was "172.24.0.1". You would configure this with "sflow agent-ip 172.24.0.1", documentation suggests that if you don't it will default to 0.0.0.0 and sflow will be disabled as a result. Remember that this IP should match what your polling the node with in NPM!!!

If none of this works, try posting your sflow configuration items so we can look at it.

ice

as long as your nexus is using this type of flows:

netflow v.5

netflow v.9

Flexible netflow

joapple

It is now working, thank you for your help.