Netflow problem with Prime Infrastructure

[Mason Tu]

Hi,

I am using Prime Infrastructure 1.2 eval version.(100 devices and 150 interfaces limit)

I was hoping to send netflow data from Nexus 7010 and 3750X to PI.

So I add them manually and set up configuration for netflow.

After that, I can't see anything about netflow in [Operate]->[Performance]->[Service Assurance]

It shows no data available.

I look up in the user guide to figure out the problem.

Then I use [Configuration Templates] to deploy netflow config again.

The result is the same.

Can anyone with experience using netflow function in PI 1.2 could tell me where did I miss?

Thanks in advanced.

[Pandian G K]

Hi Mason Tu,

Can you check any access list blocking your switches from sending data to PI

HTH ,

Pandian.

[Mason Tu]

Hi Pandian,

Thanks for your reply, but we don't have any access-list configuration on the switch.

And this is a test lab , there is no firewall as well.

I try to ping from switch to PI, it's fine.

[Mustafa Al Housami]

Dear Mason,

Did you ever find a solution for this problem?
Please advise,

Moustafa

[Mason Tu]

Hi Moustafa,

I don't have any solution for this problem.

Do you meet the same problem?

[Carl Dragert]

Hi Moustafa
I have the same problem. Is your prime server connected to a Nexus switchport?
May be My problem startes when I moved the prime server from a 3560x to a Nexus. It is a wild gues, but I will try moving it back.

Sent from Cisco Technical Support Android App

[Timothy Chan]

Any resolutions?

Same problem no netflow data.  Netflow data is being exported fine to Solarwinds and sh ip flow export shows many flows being exported.

[Christopher Bell]

Check the port assignments. We had an issue with this during Eval and it was due to ports.

Sent from Cisco Technical Support iPhone App

[Mason Tu]

Agree with Christopher, check the destination port setting.

Another concern point is the version of 3750X module has to be compatible with 3750X itself.

If the version of these two are mismatch, no netflow can be exported.

[Timothy Chan]

The port is 9991 for Prime right?  Here is my 6509 netflow config which works for other reporting software.  I've just added my prime vm appliance IP with port 9991.  I see a few netflows in data sources but no TX or RX data for the interface ( see attached pics ).

mls aging long 64

mls aging normal 64

mls netflow interface

mls flow ip interface-full

mls nde sender version 5

ip flow-export source VlanX

ip flow-export version 5

ip flow-export destination PRIME_IP 9991

ip flow-export destination SOLARWINDS_IP 2055

interface Port-channelX

ip address IP

ip flow ingress

ip flow egress

ip pim sparse-mode

end

6509#sh ip flow export

Flow export v5 is enabled for main cache

  Export source and destination details :

  VRF ID : Default

    Source(1)       MyIP (VlanX)

    Source(2)       MyIP (VlanX)

    Destination(1)  PRIME_IP (9991)

    Destination(2)  SOLARWINDS_IP (2055)

  Version 5 flow records

  23615010 flows exported in 1332989 udp datagrams

  0 flows failed due to lack of export packet

  0 export packets were sent up to process level

  0 export packets were dropped due to no fib

  0 export packets were dropped due to adjacency issues

  0 export packets were dropped due to fragmentation failures

  0 export packets were dropped due to encapsulation fixup failures

  0 export packets were dropped enqueuing for the RP

  0 export packets were dropped due to IPC rate limiting

  0 export packets were dropped due to Card not being able to export

[edeloscobos]

Mason,

Here are a working Netflow configuration for Nexus 7K switch:

!Command: show running-config netflow

!Time: Tue Jul 23 11:26:40 2013

version 6.1(3)

feature netflow

flow timeout active 120

flow timeout inactive 32

flow timeout fast 32 threshold 100

flow timeout session

flow timeout aggressive threshold 75

flow exporter EXP1

  destination 192.168.250.249

  transport udp 9991

  source Vlan998

  version 9

flow record REC1

  match ipv4 source address

  match ipv4 destination address

  match transport source-port

  match transport destination-port

  collect routing forwarding-status

  collect transport tcp flags

  collect counter bytes

  collect counter packets

  collect timestamp sys-uptime first

  collect timestamp sys-uptime last

flow monitor MON1_input

  record netflow ipv4 original-input

  exporter EXP1

flow monitor MON1_output

  record netflow ipv4 original-output

  exporter EXP1

interface Vlan2

  ip flow monitor MON1_input input 

  ip flow monitor MON1_output output 

interface Ethernet4/8

  ip flow monitor MON1_input input 

  ip flow monitor MON1_output output

I hope this can help you.

Regards

[Christopher Bell]

Which cards and fabric are you using? What version of NX-OS are you using? You may be running into an issue with what the Nexus will actually support with regards to Netflow. 

If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

[Timothy Chan]

I don't have a Nexus, I have Catalyst 6509 and 3750 mostly. 

[Christopher Bell]

My reply was directed to the original poster... who does have a Nexus.  If you have a separate issue with a separate product, it might be best to start your own thread?

If this posts answers your question or is helpful, please consider rating it and/or marking as answered.