On Sun, Jan 09, 2011 at 04:14:04PM +0300, Tarique A. Nalkhande - BMC wrote:
> All,
>
> Even we faced a similar problem on our MX's running 10.2R3. Further
> findings revealed memory leak bug for mib2d process.. restarting mib2d
> fixed it.
> Juniper is probably tracking it through some internal
All,
Even we faced a similar problem on our MX's running 10.2R3. Further findings
revealed memory leak bug for mib2d process.. restarting mib2d fixed it.
Juniper is probably tracking it through some internal PR, the committed release
is 10.2R3 which doesn't look likely.
Thanks & Regards
Tariq
Awesome.. thanks again to everyone on the list (and several folks who
replied offlist) for the help. This is probably one of the most convoluted
upgrade processes I've seen in a long time! ;)
Cheers,
Paul
-Original Message-
From: Justin Ryburn [mailto:jryb...@ryburn.org] On Behalf Of
3 matches
Mail list logo