7 Replies Latest reply on Dec 3, 2013 8:09 AM by pedroluis

    Nexus 7K and NetFlow unmanaged interface 'does not support SNMP'

    scope2013

      NetFlow Receiver Service [SOLARWINDS ] is receiving flow data from unmanaged interface '#334' on NEXUS7K and it does not support SNMP. Click the "Add this interface" to manage interface and process its flow data.

       

      Receiving these alerts after implementing Netflow config on our Nexus devices. The Nexus are already monitored in SolarWinds orion, it knows about the interfaces already and polls them via the Mgmt0 interfaces.

       

      I can "Add this interface" but 1) it's hard to determine which "NTA Virtual Interface #333" is which actual interface and 2) If I change it to Ethernet 1/1, but thats already monitored now I have 2 instances of e1/1, one that has the NetFlow data but is in a constant "unknown" state and then one who's Tx/Rx, etc is properly reported.

       

      Is there either 1) a way to tie these interfaces together. or b) and more ideally, have NTA properly and automatically determine which interface is which.

       

      I'm not sure why it's saying it does not support SNMP.

       

      Using Ver5 Netflow on the exporters.

       

      Thanks. ,

        • Re: Nexus 7K and NetFlow unmanaged interface 'does not support SNMP'
          donthomas

          Is it a case of interface indexes changing and then the new interface index being discovered with NetFlow data? Make sure you have ifindex persistence enabled on the Nexus.Reguar IOS devices uses "snmp-server ifindex persist" for ifindex persistance.

           

          R,

          Don

          • Re: Nexus 7K and NetFlow unmanaged interface 'does not support SNMP'
            Martin.Krivanek

            NTA shows this message if interface indexes in flows doesn't match any interface indexes on the device (queried by SNMP). In your case NTA received flow with interface index 334, but no such interface existed in your NPM installation. Thus SNMP query was issued to check for that interface on the device - no such was found and that's why the message was generated. Anyway, I'd try advice from Don first and see if that helps.

             

            Regards,

            Martin

              • Re: Nexus 7K and NetFlow unmanaged interface 'does not support SNMP'
                wanine39

                hello

                 

                this is a common problem with most SNMP based appliances monitoring Cisco devices.

                 

                by default, the interface indexes are dynamically allocated

                for example, you may notice that the interface index for Gi 0/0 changes over time

                 

                luckily there is a fix

                 

                conf t

                snmp-server ifindex persist

                 

                this will ensure the the index states the says for any port

                once you do this, you should no longer see 100's of new index any more

                 

                to see the mapping, do this

                on ISR

                show snmp mib ifmib ifindex

                 

                on Nexus

                show interface snmp-ifidex

                to find a specific index value for a port

                on ISR

                show snmp mib ifmib ifindex Incl FastEthernet1/11


                on Nexus

                show interface snmp-ifindex | grep -i Eth12/1

                let us know if this fixes your messages

                 

                Walter

              • Re: Nexus 7K and NetFlow unmanaged interface 'does not support SNMP'
                wanine39

                as well

                 

                here are a few SNMP options to turn on

                snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart

                snmp-server enable traps vrrp

                snmp-server enable traps ds1

                snmp-server enable traps tty

                snmp-server enable traps eigrp

                snmp-server enable traps xgcp

                snmp-server enable traps ds3

                snmp-server enable traps envmon

                snmp-server enable traps icsudsu

                snmp-server enable traps isdn call-information

                snmp-server enable traps isdn layer2

                snmp-server enable traps isdn chan-not-avail

                snmp-server enable traps isdn ietf

                snmp-server enable traps ds0-busyout

                snmp-server enable traps ds1-loopback

                snmp-server enable traps ethernet cfm cc mep-up mep-down cross-connect loop config

                snmp-server enable traps ethernet cfm crosscheck mep-missing mep-unknown service-up

                snmp-server enable traps license

                snmp-server enable traps disassociate

                snmp-server enable traps deauthenticate

                snmp-server enable traps authenticate-fail

                snmp-server enable traps dot11-qos

                snmp-server enable traps switch-over

                snmp-server enable traps rogue-ap

                snmp-server enable traps wlan-wep

                snmp-server enable traps aaa_server

                snmp-server enable traps atm subif

                snmp-server enable traps bgp

                snmp-server enable traps bulkstat collection transfer

                snmp-server enable traps memory bufferpeak

                snmp-server enable traps cnpd

                snmp-server enable traps config-copy

                snmp-server enable traps config

                snmp-server enable traps config-ctid

                snmp-server enable traps dial

                snmp-server enable traps dsp card-status

                snmp-server enable traps dsp oper-state

                snmp-server enable traps entity

                snmp-server enable traps fru-ctrl

                snmp-server enable traps resource-policy

                snmp-server enable traps event-manager

                snmp-server enable traps frame-relay multilink bundle-mismatch

                snmp-server enable traps frame-relay

                snmp-server enable traps frame-relay subif

                snmp-server enable traps hsrp

                snmp-server enable traps ipmulticast

                snmp-server enable traps mpls ldp

                snmp-server enable traps mpls traffic-eng

                snmp-server enable traps mpls fast-reroute protected

                snmp-server enable traps msdp

                snmp-server enable traps mvpn

                snmp-server enable traps ospf state-change

                snmp-server enable traps ospf errors

                snmp-server enable traps ospf retransmit

                snmp-server enable traps ospf lsa

                snmp-server enable traps ospf cisco-specific state-change nssa-trans-change

                snmp-server enable traps ospf cisco-specific state-change shamlink interface-old

                snmp-server enable traps ospf cisco-specific state-change shamlink neighbor

                snmp-server enable traps ospf cisco-specific errors

                snmp-server enable traps ospf cisco-specific retransmit

                snmp-server enable traps ospf cisco-specific lsa

                snmp-server enable traps pim neighbor-change rp-mapping-change invalid-pim-message

                snmp-server enable traps pppoe

                snmp-server enable traps cpu threshold

                snmp-server enable traps rsvp

                snmp-server enable traps ipsla

                snmp-server enable traps syslog

                snmp-server enable traps l2tun session

                snmp-server enable traps l2tun pseudowire status

                snmp-server enable traps vtp

                snmp-server enable traps pw vc

                snmp-server enable traps firewall serverstatus

                snmp-server enable traps ipmobile

                snmp-server enable traps rf

                snmp-server enable traps isakmp policy add

                snmp-server enable traps isakmp policy delete

                snmp-server enable traps isakmp tunnel start

                snmp-server enable traps isakmp tunnel stop

                snmp-server enable traps ipsec cryptomap add

                snmp-server enable traps ipsec cryptomap delete

                snmp-server enable traps ipsec cryptomap attach

                snmp-server enable traps ipsec cryptomap detach

                snmp-server enable traps ipsec tunnel start

                snmp-server enable traps ipsec tunnel stop

                snmp-server enable traps ipsec too-many-sas

                snmp-server enable traps ccme

                snmp-server enable traps srst

                snmp-server enable traps mpls vpn

                snmp-server enable traps voice

                snmp-server enable traps dnis

                • Re: Nexus 7K and NetFlow unmanaged interface 'does not support SNMP'
                  donthomas

                  I read that NX-OS has ifindex persistence enabled by default. But I also happened to read about a possible Cisco bug on the Nexus which causes the ifindex can change.

                  https://supportforums.cisco.com/thread/2187129

                   

                  Could it be that you have an older OS on the device with this bug? And then, can you check the interface name for the newly discovered ifindex on the Nexus. I believe the command for NX-OS is "show interface snmp-ifindex". You can check the interface name for ifindex and then check if NPM is managing it or not.

                  • Re: Nexus 7K and NetFlow unmanaged interface 'does not support SNMP'
                    pizzagraveyard

                    Change your exporter on the Nexus 7k to use version 9.

                     

                    I had the same problem on my 7010's and changing my flow exporter from version 5 to version 9 resolved the issue. Most of my other Cisco gear is running version 5 so that is I had picked by default but the 7ks do not map the interfaces correctly when using version 5 changing nothing on my configuration expect the exporter version resolved the issue.

                     

                    For reference my relevant configuration sections are below:

                     

                    flow record Basic-Netflow-Record

                    description Generate Basic Netflow

                    match ipv4 source address

                    match ipv4 destination address

                    match transport destination-port

                    collect counter bytes

                    collect counter packets

                     

                    flow exporter Netflow-To-Orion

                    description Solarwinds Orion Server

                    destination 10.10.10.10 use-vrf management

                    source mgmt0

                    version 9

                    transport udp 2055

                     

                    flow timeout active 120
                    flow timeout inactive 32
                    flow timeout fast 32 threshold 100
                    flow timeout session
                    flow timeout aggressive threshold 75

                    flow monitor Netflow-Monitor-1
                    description Use Predefined Original-Netflow-Record
                    record netflow-original
                    exporter Netflow-To-Orion

                     

                    interface VLAN100

                    ip flow monitor Netflow-Monitor-1 input

                    ip flow monitor Netflow-Monitor-1 output

                      • Re: Nexus 7K and NetFlow unmanaged interface 'does not support SNMP'
                        pedroluis

                        This is a problem with IOS routers as well. It's driving me insane seeing this on the event log for the last year or so. It seems to temporarily go away with a reboot, but it always comes back after a couple of months. I cannot keep rebooting 250 plus routers and the four 6509 national hubs as you can imagine...

                         

                        I have the aforementioned
                        snmp-server ifindex persist

                         

                        command, as well as the always suggested

                        ip flow-export source FastEthernet0/0

                        ip flow-export version 9

                         

                        commands as well. As an example on a box such as this:

                        Cisco 2811 (revision 53.51), 2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(15)T13

                         

                        Messages like:

                        NetFlow Receiver Service [COLLECTOR] is receiving flow data from unmanaged interface '#710193670' on "ROUTERNAME" and it does not support SNMP. Click the "Add this interface" to manage interface and process its flow data.

                         

                        YET, there is no such interface in the snmp ifindex:

                        ROUTERNAME#show snmp mib ifmib ifindex detail
                        Description                     ifIndex  Active  Persistent
                        ----------------------------------------------------------------

                        FastEthernet0/0                  1      yes      enabled  
                        Null0                            4      yes      enabled  
                        Serial0/0/0:0                    7      yes      enabled  
                        VoIP-Null0                       3      yes      enabled  
                        T1 0/0/0                         5      yes      enabled  
                        FastEthernet0/1                  2      yes      enabled  
                        Serial0/0/1:0                    8      yes      enabled  
                        T1 0/0/1                         6      no       enabled

                         

                        See how annoying this is?

                        I suspect it is related to CPU usage on the collector. scope2013, how is your cpu usage during these messages looking like on your end?