5 Replies Latest reply on Nov 7, 2008 11:57 AM by chopperpl

    NTA on your demo site

       Hi,

      It looks like one of the demo devices on NTA site is HP ProCurve 4000M (according to description), however, HP does not report this device as sFlow supported. Does anyone know if that device support sFlow?

      Thanks

        • Re: NTA on your demo site
          Patrick Hubbard

           Hi,

          It looks like one of the demo devices on NTA site is HP ProCurve 4000M (according to description), however, HP does not report this device as sFlow supported. Does anyone know if that device support sFlow?

          Thanks

           



          That's a good question and the first time anyone asked about that.  Let me do a little research. :)

            • Re: NTA on your demo site
              Patrick Hubbard

              That's a good question and the first time anyone asked about that.  Let me do a little research.

               



              chopperpl good call.  I haven't done a re-discovery on that node in some time, and it is or has been swapped from a 2900 to a 2800, (and probibly before that the 4000).  I've updated it's name and caption in Orion and the description has been updated from the MIB: "ProCurve J4904A Switch 2848, revision I.08.105, ROM I.08.07 (/sw/code/build/mako(ts_08_5))".

              Thanks!

                • Re: NTA on your demo site

                   Thanks for correction, but we would like to know if 4000 unit was fully functional via sFlow. I know it is not officialy supported by HP, but it is OS driven device, and vendors usually include "non-supported" features with newer OS releases, for example cisco's IOS... I had evaluated your NTA with HP ProCurve 2610 last month, and I could not get it to work with NTA 3.0. 2610 does support sFlow v5 according to HP's website.

                  Thanks

                    • Re: NTA on your demo site
                      Patrick Hubbard

                       Thanks for correction, but we would like to know if 4000 unit was fully functional via sFlow. I know it is not officialy supported by HP, but it is OS driven device, and vendors usually include "non-supported" features with newer OS releases, for example cisco's IOS... I had evaluated your NTA with HP ProCurve 2610 last month, and I could not get it to work with NTA 3.0. 2610 does support sFlow v5 according to HP's website.

                      Thanks

                       



                      I'm ore of a software guy than hardware so I spoke with one of the lab guys and here's what he said

                       



                      The 2610 switch should be really similar to one of my 2848's and it works with sflow but it’s been added onto the OS. It can only be configured through snmp and is not in the cli. If you lose power the configuration is not saved. Heres an example config:

                      setmib sFlowRcvrAddress.1 -o 0A6E421B (ip in hex format)
                      setmib sFlowRcvrPort.1 -i 2055
                      setmib sFlowRcvrOwner.1 -D net sFlowRcvrTimeout.1 -i 100000000
                      setmib 1.3.6.1.4.1.14706.1.1.5.1.4.11.1.3.6.1.2.1.2.2.1.1.1.1 -i 37 (sample rate)
                      setmib 1.3.6.1.4.1.14706.1.1.5.1.3.11.1.3.6.1.2.1.2.2.1.1.1.1 -i 1 (enable sflow)
                      setmib 1.3.6.1.4.1.14706.1.1.6.1.4.11.1.3.6.1.2.1.2.2.1.1.53.1 -i 8 (polling interval)
                      setmib 1.3.6.1.4.1.14706.1.1.6.1.3.11.1.3.6.1.2.1.2.2.1.1.53.1 -i 1 (enable polling)

                       



                      I hope that helps.  Was there anything else on Thwack about configuring sFlow on the 2610?

                      -Patrick

                        • Re: NTA on your demo site

                          Thanks for quick reply...

                           That's exactly how I configured it (via snmp) with HP support verifying all commands... no luck. However, the switch was transmitting sflow data to scrutinizer just fine. I had noticed NTA was complaining about index# of the interface sending sflow data. The 10 digit number pulled by NTA seemed to be from snmp walk, and not really what NPM was showing in system manager. Perhaps your next NTA version would verify all indexes per interface before making decision to accept the data stream or not...     

                          Did you get any info on 4000m switch? Any unofficial workarounds?

                          Thanks