Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Measurement error: HP 5406zl vs. HP 2610-24

Hi!

We are using solarwinds to verify the traffic measured by our isp . For this purpose we had used until 2 days ago an hp 5406zl (sflow). We replaced the switch with an hp 2610-24. Now we have got the problem, that the hp 2610 is not measuring the traffic correct. I downloaded a file from the solarwinds host solarwinds.s3.amazonaws.com bwith nearly 34 Mbytes and the hp2610 displayed me just a traffic von nearly 3 Mbytes. The hp 5406zl reported 34,5 Mbytes from solarwinds.s3.amazonaws.com. Are there any know issues or bugs? What can I do or check?

Daniel

Find more posts tagged with

Accepted answers

All comments

davidmaltby

There was a known issue in NTA 3.1, where we were dropping traffic. It should be fixed in Service Pack 2. Try that and let us know if that helps.

Thanks,

David

snowfox8888

Still the same. I also replaced the hp 2610-24 switch by another hp 2610-24 switch (different firmware releases). The same problem... :-(

Daniel

HP 2610-24:

ProCurve Switch 2610-24# show sflow destination
sflow                     : Enabled
Datagrams Sent            : 4354
Destination Address       : 192.168.90.3
Receiver Port             : 9990
Owner                     : Administrator
Timeout (seconds)         : 2147380929
Max Datagram Size         : 1400
Datagram Version Support : 5

ProCurve Switch 2610-24# show sflow sampling
sflow destination Enabled

Port | Sampling                 Dropped    | Polling
       | Enabled Rate     Header Samples    | Enabled Interval
----- + ------- -------- ------ ---------- + ------- --------
1       Yes      20       128    19320        Yes     30
2       Yes      20       128    18847        Yes     30
3       Yes      20       128    0            Yes     30
4       Yes      20       128    538          Yes     30
5       Yes      20       128    0            Yes     30
6       Yes      20       128    0            Yes     30
7       Yes      20       128    4015         Yes     30
8       Yes      20       128    0            Yes     30
9       Yes      20       128    3553         Yes     30
10      Yes      20       128    97           Yes     30
...

HP 5406zl

ProCurve Switch 5406zl> show sflow 1 destination
Destination Instance      : 1
sflow                     : Enabled
Datagrams Sent            : 246691
Destination Address       : 192.168.90.3
Receiver Port             : 9990
Owner                     : Administrator, CLI-Owned, Instance 1
Timeout (seconds)         : 2147343711
Max Datagram Size         : 1400
Datagram Version Support : 5

ProCurve Switch 5406zl> show sflow 1 sampling

Port | Sampling                 Dropped    | Polling
       | Enabled Rate     Header Samples    | Enabled Interval
----- + ------- -------- ------ ---------- + ------- --------
A1      Yes(1)         50    128          0   Yes(1)        30
A2      Yes(1)         50    128          0   Yes(1)        30
A3      Yes(1)         50    128          0   Yes(1)        30
A4      Yes(1)         50    128          0   Yes(1)        30
A5      Yes(1)         50    128          0   Yes(1)        30
A6      Yes(1)         50    128          0   Yes(1)        30
A7      Yes(1)         50    128          0   Yes(1)        30
A8      Yes(1)         50    128          0   Yes(1)        30
A9      Yes(1)         50    128          0   Yes(1)        30
A10     Yes(1)         50    128          0   Yes(1)        30
...

floyd.may

The sFlow protocol works by randomly sampling packets, so there's a possibility that, depending on the sampling algorithm, the traffic distribution across the interface(s) in question, and luck, NTA doesn't have enough information to give you a more accurate answer.

mcbridea

can you attach a screen shot of the NTA results when you DL a known size file?

davidmaltby

Also, a PCAP (sniffer trace - WireShark) during that same time period would definately help resolve this.