[j-nsp] Graphing VCP Backplane (slax help needed)

[Curtis Call]

You'll want to use jcs:execute() instead of jcs:invoke(). Take a look at page 69-71 of the Mastering Junos Automation book for details on the performance difference when executing a lot of RPCs:

http://www.juniper.net/us/en/community/junos/training-certification/day-one/automation-series/mastering-junos-automation/


> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
> bounces at puck.nether.net] On Behalf Of Charlie Allom
> Sent: Wednesday, October 19, 2011 7:11 AM
> To: juniper-nsp
> Cc: Christoph Blecker
> Subject: Re: [j-nsp] Graphing VCP Backplane (slax help needed)
> 
> On Tue, Nov 09, 2010 at 04:30:28PM +0100, Phill Jolliffe
> <phill.jolliffe at gmail.com> wrote:
> > If you can find a counter for the vcp throughput then you can
> populate
> > the "utility mib" with the value and snmp poll and graph it.
> 
> I've done just this. It took me about 4 hours of learning SLAX.. enough
> to patch this together:
> 
>     http://capslock.playlouder.com/check-vc.slax
> 
> It actually only works as a proof of concept.
> 
> On a 2-member EX stack with little traffic, the load is high but it
> only takes a minute to run.
> 
> On a 3-member stack running decent traffic, the load grinds to 1.7 and
> the CPU is very busy. On anything more than 3*24T I would imagine the
> script is unusable!
> 
> The output is nothing like normal interfaces.. you'd need to craft your
> own poller with collectd or something to watch the traffic.
> 
> Can anyone help me with SLAX to maybe bring the load down? I am sure I
> am doing-it-wrong.
> 
> Regards,
>   C.
> --
>  +442077294797
>  http://mediasp.com/
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp