Rasmus,
The E.09.11 code has been officially released to support and is expected to be on the WEB approximately April 1st, 2005 (delay from code release to posting to the web). I would strongly urge you to open a call with hp support and reference this post. There are various perf issues noted in this news thread and it is impossible for me to tell if they are all related to the same exact underlying problem. My first impression is that they all are not related specifically to one single issue, but can not say with clarity unless able to reveiw the type of data needed to address a performance issue.
Unfortunately in a large enterprise such as hp, not everyone you speak with is going to be aware of every issue out there with any given product. But you can count on your issue be addressed to your satisfaction should you not feel you are getting the assistance you need. If you dont agree with the advise of the eng tech, just say so and they will get help from peers or their next level of support. If necessary, the case will get to us here in escalations.
In this one particular forum post case, if you open a call and do not feel you are getting the attention you need, please post the case id in this forum and I will follow up with the case owner (of course not all forum posts will be addressed as such. Only the ones where customers are certainly not getting the attention they feel they need). The first recommendation should be the code update to the E.09.11. If the call owner isnt aware of the latest revision, then just send them this post. You need not be concerned about the overhead of the added features since your existing config will be compatible with the newer code. You will not see an increase in overhead from the newer code features unless you enable them. I think LLDP is an exception but this can be disabled if you're concerned. As always, update your secondary flash with the newer code and boot the switch into the secondary flash. This way if something goes wrong, then a simple reboot (defaulting to primary flash) will put you back to the older code rev.
Other types of data relevant to address this performance type issues would be a network map showing your layout, show techs and network sniffer traces of the problem in action, a writeup of all the protocols you are using (which can be inferred from the show tech but not as clearly as your statemnets), as detailed a description as possible of which ports/clients/networks/subnets/etc that are known to be affected and which are not.
Here is the "skinny" of some issues addresses beyond E.09.03 upto E.09.11
├в ┬в Routing - Asymmetrical routing results in high CPU utilization and dropped packets.
├в ┬в XRRP - Different XRRP versions cause excessive event log messages...
├в ┬в QoS ├в DSCP tagging feature not working on routed packets.
├в ┬в Web ├в Java files now compiled using JDK 1.2. JDK 1.1 was used previously.
├в ┬в XRRP - XRRP Automatic Fail Over enhancement.
├в ┬в PIM ├в When PIM is enabled, all multicast streams managed by IGMP can be delayed whenever a Leave is received for any stream.
This forum post has caught the attention of the labs and they are very curious to determine what exactly we are dealing with since we apparently have some un-happy customers (we certainly do not wnat this!). The only way to do that is to have an active call open with hp support for us to to coordinate with the labs on.
At this point it does not "appear" that all issues noted in this post are stemmed from the same underlying issue, but to determine this, the level of technical assistance needed to address these perf issues is not really going to happen via
