Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Supervisor 8 e and NetFlow

I'm hoping this will be an easy question.

I have a 4506e enclosure in which we've upgraded to a Supervisor 8e card. Is a separate NetFlow hardware module required in order to use NetFlow?

 

I have configured the switch based on what I've found online.

 

flow record RECORD1
 match ipv4 source address
 match ipv4 destination address
 collect counter bytes
 collect counter packets
!
!
flow exporter EXPORT1
 destination 10.10.3.104
 source Vlan10
 transport udp 2055
!
!
flow monitor MONITOR1
 exporter EXPORT1
 cache timeout active 300
 record RECORD1

 

However, when I open the NetFlow analyzer the device does not show up.

  • WAN Routing and Switching
1 ACCEPTED SOLUTION

Accepted Solutions

Well what does the NTA say?

What I meant was, device might have to be in and monitoring via SNMP, and the Node IP should be interface VLAN 10. Perhaps just simple ICMP might work? - I haven't tried that though.

Well what does the NTA say? Normally it says it on the web page in orion if it doesn't like something. I have found that the NTA does not like it when it receives data from an unknown source (I have all my devices for SNMP monitoring), unless there is a way where you can configure Orion to just accept and not to ignore. Also its not instant, I had to wait a good 5 mins for things to start working.

Please rate useful posts & remember to mark any solved questions as answered. Thank you.
14 REPLIES

Have you applied ip flow

Have you applied ip flow monitor MONITOR1 input or output under an interface?

Also i noticed you are trying to export on udp 2055 is this to Solarwinds Orion Netflow? if so then you need to do this at a minimum:

flow record RECORD1

match ipv4 tos

match ipv4 protocol

match ipv4 source address
match ipv4 destination address

match ipv4 transport source-port

match ipv4 transport destination-port

collect interface input snmp

collect interface output snmp

collect counter bytes 

collect counter packets

 

Hope this helps.

Please rate useful posts & remember to mark any solved questions as answered. Thank you.
New Member

Thank you for responding. I

Thank you for responding. I have applied MONITOR1 to vlan 10. It IS the solar winds analyzer.
 

I tried to put in the additional commands for RECORD1 but got "invalid input detected" for the following commands:

match ipv4 transport source-port

match ipv4 transport destination-port

collect interface input snmp

collect interface output snmp

 

 

Okay - i am also using solar

Okay - i am also using solarwinds, apologies i made a mistake here is correction... One requirement in solarwinds is to monitor this device from VLAN 10. And add the interfaces for monitoring. Hopefully it should start working!

match transport source-port

match transport destination-port

collect interface input snmp

collect interface output snmp

collect counter bytes

collect counter packets

Please rate useful posts & remember to mark any solved questions as answered. Thank you.
New Member

Still not showing up in the

Still not showing up in the analyzer. Do I have to configure SNMP on the switch? I really do not want to.

 

What do you mean by this:
 

One requirement in solarwinds is to monitor this device from VLAN 10. And add the interfaces for monitoring.

Well what does the NTA say?

What I meant was, device might have to be in and monitoring via SNMP, and the Node IP should be interface VLAN 10. Perhaps just simple ICMP might work? - I haven't tried that though.

Well what does the NTA say? Normally it says it on the web page in orion if it doesn't like something. I have found that the NTA does not like it when it receives data from an unknown source (I have all my devices for SNMP monitoring), unless there is a way where you can configure Orion to just accept and not to ignore. Also its not instant, I had to wait a good 5 mins for things to start working.

Please rate useful posts & remember to mark any solved questions as answered. Thank you.
New Member

OK, I've made some progress.I

OK, I've made some progress.

I briefly turned on snmp with:
 snmp-server community public

When I did this, I was able to add the device to the SolarWinds analyzer. I then turned the snmp server off:

 no snmp-server

Closed the SolarWinds analyzer and opened it back up, and the device is still there.

However, I still not get vlan 10 to report NetFlow data. My config is pretty much the same as above:

 

flow record RECORD1
 match ipv4 source address
 match ipv4 destination address
 match transport source-port
 match transport destination-port
 collect counter bytes
 collect counter packets
!
!
flow exporter EXPORT1
 destination xxx.xxx.xxx.xxx
 source Vlan10
 transport udp 2055
!
!
flow monitor MONITOR1
 exporter EXPORT1
 cache timeout active 300
 record RECORD1
!
!
!
output omitted
!
!
!
vlan configuration 10
ip flow monitor MONITOR1 input
vlan internal allocation policy ascending

 

Not exactly sure what I could be missing. Any Ideas?

Hello, Please see my original

Hello, Please see my original post, I believe you are missing some commands there for the flow record.

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

see attached Doc. Follow

see attached Doc. Follow steps for Sup7 - same thing.

Hope it helps

Please rate useful posts & remember to mark any solved questions as answered. Thank you.
New Member

I went ahead and tried to all

I went ahead and tried to all all of the commands to the flow record and here is what I got:

 

switch(config)#flow record RECORD1
switch(config-flow-record)# match ipv4 tos
switch(config-flow-record)# match ipv4 protocol
switch(config-flow-record)# match ipv4 source address
switch(config-flow-record)# match ipv4 destination address
switch(config-flow-record)# match transport source-port
switch(config-flow-record)# match transport destination-port
switch(config-flow-record)# collect interface input snmp
                                                    ^
% Invalid input detected at '^' marker.

switch(config-flow-record)# collect interface output snmp
                                                     ^
% Invalid input detected at '^' marker.

switch(config-flow-record)# collect counter bytes
switch(config-flow-record)# collect counter packets

 

So I went ahead and tried to enter the "collect interface input" command manually followed by "?" to see the options available. The only thing that was there was "netflow". So I figured "awesome, that must be it". I was then able to add the updated flow record to MONITOR1, but when I applied the updated MONITOR1 to the vlan config I got the following error:


switch(config-vlan-config)#ip flow monitor MONITOR1 in
Warning: Exporter EXPORT1 could not be activated because of the following unsupported fields:
    interface input netflow
    interface output netflow

 

Are you using a hardware NetFlow module in your enclosure, or is it just done in IOS?

1096
Views
15
Helpful
14
Replies
This widget could not be displayed.