Re: [j-nsp] SNMP polling issue MX

2011-01-10 Thread Clarke Morledge
It looks like there were possibly multiple mib2d process bugs.   In our 
case, restarting mib2d did not always resolve the issue.


The good news is that it does look like 10.2R3 fixes the mib2d issues we 
were experiencing.  We've been running 10.2R3 (or a derivative) for 
several weeks and SNMP appears to be stable.


Clarke Morledge
College of William and Mary
Information Technology - Network Engineering
Jones Hall (Room 18)
Williamsburg VA 23187


On Sunday, Richard said:


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 PR, the
committed release is 10.2R3 which doesn't look likely.


Hrmm supposedly the mib2d memory leak is fixed was 10.2R3, but we never
actually tested it, we just skipped straight ahead to 10.3R2 on new
deployments (as there were many other SNMP bugs still not fixed in 10.2
at the time). A quick and dirty workaround for the memory leak issue is
to periodically restart the mib2d process, which you can do with an
event script like so:

event-options {
   generate-event {
   /* Adjust ttimer as necessary based on memory consumption */
   restart-mib2d time-interval 604800;
   }
   policy restart-mib2d {
   events restart-mib2d;
   /* Adjust this too, to something slightly less than above */
   within 60 {
   not events restart-mib2d;
   }
   then {
   event-script restart-mib2d;
   }
   }
}

/var/db/scripts/op/restart-mib2d.slax:

version 1.0;
ns junos = "http://xml.juniper.net/junos/*/junos";;
ns xnm = "http://xml.juniper.net/xnm/1.1/xnm";;
ns jcs = "http://xml.juniper.net/junos/commit-scripts/1.0";;
import "../import/junos.xsl";

match / {
{
   var $restart-mib2d = {
"restart mib-process gracefully";
   }
   var $result = jcs:invoke($restart-mib2d);
   }
}

--
Richard A Steenbergenhttp://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] SNMP polling issue MX

2011-01-09 Thread Richard A Steenbergen
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 PR, the 
> committed release is 10.2R3 which doesn't look likely.

Hrmm supposedly the mib2d memory leak is fixed was 10.2R3, but we never 
actually tested it, we just skipped straight ahead to 10.3R2 on new 
deployments (as there were many other SNMP bugs still not fixed in 10.2 
at the time). A quick and dirty workaround for the memory leak issue is 
to periodically restart the mib2d process, which you can do with an 
event script like so:

event-options {
generate-event {
/* Adjust ttimer as necessary based on memory consumption */
restart-mib2d time-interval 604800;
}
policy restart-mib2d {
events restart-mib2d;
/* Adjust this too, to something slightly less than above */
within 60 {
not events restart-mib2d;
}
then {
event-script restart-mib2d;
}
}
}

/var/db/scripts/op/restart-mib2d.slax:

version 1.0;
ns junos = "http://xml.juniper.net/junos/*/junos";;
ns xnm = "http://xml.juniper.net/xnm/1.1/xnm";;
ns jcs = "http://xml.juniper.net/junos/commit-scripts/1.0";;
import "../import/junos.xsl";
 
match / {
 {
var $restart-mib2d = {
 "restart mib-process gracefully";
}
var $result = jcs:invoke($restart-mib2d);
}
}

-- 
Richard A Steenbergenhttp://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] SNMP polling issue MX

2011-01-09 Thread Tarique A. Nalkhande - BMC
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
Tarique Abbas Nalkhande



-Original Message-
From: juniper-nsp-boun...@puck.nether.net 
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Richard A Steenbergen
Sent: 02 September, 2010 11:54 AM
To: Chintan Pandya
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] SNMP polling issue MX

On Thu, Sep 02, 2010 at 12:56:21PM +0530, Chintan Pandya wrote:
> Hi All,
> 
> We are facing issue in polling SNMP statistics on MX 960 sub-interfaces.
> JUNOS 10.2R1.8 is running on router.
> 
> The sub-interfaces statistics are not getting polled on the Reporter
> software, where as the parent statistics are getting polled.
> The SNMP statistics can be seen on the router.
> The issue is with all types of interfaces AE, XE, GE.
> 
> Nothing wrong seems with the configuration.

Semi-known issue, see the discussion about bugs in 10.2 (in the Trio 
card thread) from a few days ago. We somehow stopped being able to 
replicate it, and it didn't seem like they had a PR on it back when we 
were looking, so please open a case on it. :)

-- 
Richard A Steenbergenhttp://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

--Disclaimer-- This email and any files transmitted with are classified 
as confidential unless otherwise specified. This e-mail is intended solely for 
the use of the individual or entity to whom this e-mail is addressed. If you 
have received this email by mistake, please notify the sender and delete this 
e-mail immediately and permanently. Although measures were taken to free this 
e-mail and its attachments from any malicious code infection, it is the 
responsibility of the recipient to check this email and any attachments for the 
presence of such infection. The use of EEC(Mobily) e-mail service is limited 
for EEC(Mobily) business use only. 


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] SNMP polling issue MX

2010-09-02 Thread Chintan Pandya
Hey thanks Richard,

The case has been logged already.

On Thu, Sep 2, 2010 at 2:24 PM, Richard A Steenbergen wrote:

> On Thu, Sep 02, 2010 at 12:56:21PM +0530, Chintan Pandya wrote:
> > Hi All,
> >
> > We are facing issue in polling SNMP statistics on MX 960 sub-interfaces.
> > JUNOS 10.2R1.8 is running on router.
> >
> > The sub-interfaces statistics are not getting polled on the Reporter
> > software, where as the parent statistics are getting polled.
> > The SNMP statistics can be seen on the router.
> > The issue is with all types of interfaces AE, XE, GE.
> >
> > Nothing wrong seems with the configuration.
>
> Semi-known issue, see the discussion about bugs in 10.2 (in the Trio
> card thread) from a few days ago. We somehow stopped being able to
> replicate it, and it didn't seem like they had a PR on it back when we
> were looking, so please open a case on it. :)
>
> --
> Richard A Steenbergenhttp://www.e-gerbil.net/ras
> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] SNMP polling issue MX

2010-09-02 Thread Richard A Steenbergen
On Thu, Sep 02, 2010 at 12:56:21PM +0530, Chintan Pandya wrote:
> Hi All,
> 
> We are facing issue in polling SNMP statistics on MX 960 sub-interfaces.
> JUNOS 10.2R1.8 is running on router.
> 
> The sub-interfaces statistics are not getting polled on the Reporter
> software, where as the parent statistics are getting polled.
> The SNMP statistics can be seen on the router.
> The issue is with all types of interfaces AE, XE, GE.
> 
> Nothing wrong seems with the configuration.

Semi-known issue, see the discussion about bugs in 10.2 (in the Trio 
card thread) from a few days ago. We somehow stopped being able to 
replicate it, and it didn't seem like they had a PR on it back when we 
were looking, so please open a case on it. :)

-- 
Richard A Steenbergenhttp://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[j-nsp] SNMP polling issue MX

2010-09-02 Thread Chintan Pandya
Hi All,

We are facing issue in polling SNMP statistics on MX 960 sub-interfaces.
JUNOS 10.2R1.8 is running on router.

The sub-interfaces statistics are not getting polled on the Reporter
software, where as the parent statistics are getting polled.
The SNMP statistics can be seen on the router.
The issue is with all types of interfaces AE, XE, GE.

Nothing wrong seems with the configuration.

Thanks
Chintan
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp