Net Flow Not seeing Network Nodes with SFlow enabled.........

I have run into what would be a show stopper for me using Orion Net Flow. We are installing new Brocade MX switches in all of our facilities. All interfaces on the new Brocade switches are SFlow enabled and forwarding.

We use Orion NPM to monitor our entire Enterprise network and all of the Brocade switches are entered into the NPM database with a managemnet IP address on a loopback interface. We do not use actual physical interface IP's to manage our network devices in Orion.

I just installed our evaluation version of Network Traffic Analyizer but it will not see any of the Brocade switches unless I select to manually manage the device and go back through the 'Add Node' procedure on the web console. The differnce this time is that I need to use an IP address of a physical interface and then the node will start populating with Net Flow data. The problem with this is that now I have two (2) nodes with the exact same name in my Orion NPM database but each node is known with a different IP address. What this means is that by the time we finsh with our Network rebuild i will need to double the size of my NPM database becuse the Netflow module will not use the nodes that are already being monitored.

The other problem with this is that ther is no way to discern between the 2 nodes which one is for Sflow and which one is for Orion... Is ther a way to get the Netflow analyizer to use the nodes that are already in the NPM database?

Find more posts tagged with

sflow_procurve

Accepted answers

All comments

mavturner

This is happening because the source IP of the flows needs to match an existing node. On Cisco devices you can change the source interface used to send the flows from. I'm not sure if you can do the same with the Brocade switch, but I imagine there is a way.

Is there a command for slfow source ?

mavturner

We have made some changes as of NTA 3.9 and NPM 10.2 that actually make this scenario slightly better. Basically, NPM can keep track of multiple IPs of a node. NTA can do a lookup to see if the IP exists but isn't the primary management IP. It's could be a bit tricky to setup if NPM didn't automatically pick up the other addresses, but I can walk you through setting this up. I've emailed you directly to work on this. Once we have it up, I'll post the details here for others to see.

Mav

Nakuchar

Any progress made on this? Curious to hear what the outcome was.