On Tue, 13 Apr 2010, Darren Reed wrote:
> unfortuantely the version of code in Solaris 10 U8 is pretty old and
> doesn't give you any additional insight.
Bummer :(, I would have hoped once they pulled it in as an official
component they would have kept it up to date. This is the third or fourth
problem we've had in the last year or so. We were fortunate enough not to
have installed the recent ipf patch that completely broke state before it
was withdrawn so managed to miss that escapade. I guess we could upgrade to
your latest release; but we used to run ipf under Solaris 8, and it was a
huge PITA dealing with Sun support running a third party kernel module 8-/.
Is the ipf bundled in OpenSolaris more up to date? We were planning on
migrating, although now with the Oracle takeover we're probably going to
sit for a while and see how things pan out.
> What you might be able to do is use dtrace to provide some additional clues
> by using where the return is being made from:
>
> # dtrace -n 'fbt:ipf:fr_addstate:return/arg1==0/{...@returns[arg0] =
> count();}'
My dtrace skill level isn't that high; I ran this for a while, during which
interval the lost count increased by 1 or 2, and when I C-c'd dtrace it
spit out:
1720 2
Does that have any helpful meaning?
Thanks...
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst | [email protected]
California State Polytechnic University | Pomona CA 91768
