- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: PCM+ B_02_10_5 bogus traffic
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2006 02:22 AM
тАО07-17-2006 02:22 AM
Re: PCM+ B_02_10_5 bogus traffic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2006 07:10 AM
тАО07-17-2006 07:10 AM
Re: PCM+ B_02_10_5 bogus traffic
In a nutshell, our testing failed to anticipate a particular pattern of IP addressing which anyone who has seen this bug has in their environment. When the collector receives sFlow samples from devices that meet the pattern it gets confused when computing hash keys from the incoming sFlow datagrams, and essentially multiplexes the data from multiple ports (across the devices) into the same set of internal data counters. This multiplexing leads to the erroneous values you observed in Traffic Monitor. Note that *only* sFlow data collection is affected by this bug - AU5 will correctly report statistics and sampled XRMON data.
This problem has been remedied and another autoupdate that fixes the problem, AU6, is on the way this week. We are truly sorry for any issues that this bug has caused for you. Please rest assured that we have augmented our testing procedures to ensure that nothing of this sort will occur again, and that changes proposed for inclusion in autoupdate will undergo additional scrutiny before they are accepted from this point forward.
Regards,
SVB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2006 07:32 AM
тАО07-17-2006 07:32 AM
Re: PCM+ B_02_10_5 bogus traffic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2006 11:52 AM
тАО07-18-2006 11:52 AM
Re: PCM+ B_02_10_5 bogus traffic
It is not a known issue whereby setting for notify actually installs an autoupdate. We will definitely pursue it, and in fact have been trying to replicate the behavior internally since you first mentioned the issue with no success thus far. Let's just use the same incident number; I will make sure our support engineers are aware that the autoupdate facet of the incident is still open.
AU6 was posted today, and should fix the erroneous traffic numbers you were seeing with AU5.
Regards,
SVB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-18-2006 09:06 PM
тАО07-18-2006 09:06 PM
Re: PCM+ B_02_10_5 bogus traffic
Is there some configuration that I have missed?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2006 04:56 AM
тАО07-19-2006 04:56 AM
SolutionGo to the Windows Service control panel and restart the HP ProCurve Traffic Launch Service. The message you're seeing indicates that for some reason the socket connection between the traffic data collector and PCM server processes has not been established - the PCM server is awaiting that connection. After you restart you should see that message disappear, and if you look at the Processes tab in Windows Task Manager you should see Trafficd.exe - the traffic data collector - listed.
Regards,
SVB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2006 06:53 AM
тАО07-19-2006 06:53 AM
Re: PCM+ B_02_10_5 bogus traffic
Lets not persue this any further at this time. I will watch it closely and if does it again, re-open this case. The bogus high watemarks are gone.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2006 03:23 PM
тАО09-05-2006 03:23 PM
Re: PCM+ B_02_10_5 bogus traffic
Speaking of update 7, it may be too early to tell but so far traffic is reporting more points and for a longer time. Generally my graphs look like a bad dentist worked on them and they seem to diminish what they will report on within hours of being rebooted. Eventually the top talkers reported will even include insignificant traffic like DHCP and DNS requests.
The release notes make no mention of traffic reporting changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2006 05:27 PM
тАО09-05-2006 05:27 PM
Re: PCM+ B_02_10_5 bogus traffic
I wonder what kind of data collection methode you use, is it sampling or stats ?
Good Luck !!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2006 02:21 AM
тАО09-06-2006 02:21 AM
Re: PCM+ B_02_10_5 bogus traffic
So far on day two, my graphs still show more data than toothless gaps and all Top 5 connections are plausible without miniscule any ping or DHCP or DNS stuff included.
I'm guessing something was improved but not mentioned in the release notes. Maybe I should "Disable automatic updates" entirely and stay frozen on this build which appears to be the best it has been in a very long time.
NAW! I still need the port speed change autodetect fix. What was I thinking?