03-22-2005 06:05 AM
I'm trying to upgrade my css-11151's since I'm hitting a bug in my current version (5.00 Build 105). 5.00 Build 503 and 5.00 Build 605 have
the Internal RX error issues so I'm looking
at 5.00 Build 403. Build 403 has a few open
bugs, one of which is:
"CSCed06619 - The CSS may reboot when it performs task fmPeerMsgTask"
What is fmPeerMsgTask? Is that something to do with bgp? Also anyone have issues with build 403?
Thanks
-Dan
03-23-2005 06:38 AM
Dan,
this is internal communication.
The crash occurs only if you have the following specific config
The CSS is configured with ACL and source groups. The CSS was crashing repeatedly when ftp traffic was run.
The CSS configuration was such that the an ACL preferred a source group. However the client ip address was also an 'add service' to a different source group.
I'm not sure why you don't want to go to the latest version.
Could you specific what you mean by "Internal RX error ".
Thanks,
Gilles.
03-28-2005 10:19 AM
There is this issue I bumped in to when I tried to upgrade to 6.10 last summer:
"With software version 6.10.0.04 and higher, a change has been made to
the ingress data buffer size of 10/100 Ethernet ports to reduce the
number of reset operations performed on these ports. A maximum of eight,
minimum-sized packets, can now be buffered at ingress on a port. The
performance impact of this change will be seen during traffic bursts. If
the traffic is UDP, there will be no dropped packets or performance
impact. If the traffic is TCP, then certain traffic types will
experience dropped packets and a slight increase in TCP retransmissions
for those packets."
Now I am also seeing the same thing in the latest versions of 5.00. I upgraded our css's to 5.00 Build 503 and 5.00 Build 605 and the "internal rx error" counter increments when I push even small amounts of traffic through with my load generators. I've installed 5.00 Build 403 and
do not see this problem. There is no acceptable workaround for the RX error issue so I am looking at 5.00 build 403 for production.
03-29-2005 07:19 AM
OK,
so you might be interested in this bug :
CSCee55703 The CSS drops about 10% of server TCP packets with the FIN flag set. This is due to the inclusion of an EPIF errata fix that reduces the likelihood of EPIF resets on the CSS. The debug command "epif-errata disable" has been added to the code to disable the EPIF errata code.
With the latest version you can disable the *feature* that you do not like.
Regards,
Gilles.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide