[mrtg] Re: Monitoring Cisco VPN Concentrator 3000

[Brown, James (IP)]

Hi Stuart,

Thank you for the advice...this has saved me a lot of time. Actually, we
usually just monitor active users, throughput and CPU/Memory. We then use a
.cgi menu to add the graphs to a webpage.

All the best,

James.

-----Original Message-----
From: Stuart Kendrick [mailto:skendric at fhcrc.org]
Sent: 18 March 2003 01:28
To: mrtg at list.ee.ethz.ch
Cc: jbbrown at lehman.com
Subject: Re: Monitoring Cisco VPN Concentrator 3000


Hi James,

Here is how I monitor my Altiga 3000s.  Briefly, I don't want two
parameters on these graphs ... when I'm monitoring CPU Utilization, for
instance ... I don't want to see anything else on the graph.  So I pick
some other variable which I believe will stay rock-solid at zero ...
alHardwareCpuTempCount.0, for example.

Active Sessions, CPU Util, and Throughput are the variables I watch.  I
should probably add ifInOctets/ifOutOctets on both interfaces, too.  What
else do you watch?

--sk

# Active Sessions

#Target[cf-vpn_session]:alActiveSessionCount.0&alHardwareCpuTempCount.0:publ
ic at cf-vpn
Target[cf-vpn_session]:1.3.6.1.4.1.3076.2.1.2.17.1.1.0&1.3.6.1.4.1.3076.2.1.
2.22
.1.31.0:public at cf-vpn
MaxBytes[cf-vpn_session]: 1500
Title[cf-vpn_session]: Sessions
PageTop[cf-vpn_session]: <H1>cf-vpn Active Sessions</H1>
YLegend[cf-vpn_session]: Sessions
Options[cf-vpn_session]: gauge, growright, unknaszero
ShortLegend[cf-vpn_session]: Sess
Legend1[cf-vpn_session]:
Legend2[cf-vpn_session]:
Legend3[cf-vpn_session]:
Legend4[cf-vpn_session]:
LegendI[cf-vpn_session]: Sessions
LegendO[cf-vpn_session]:
Colours[cf-vpn_session]:
GREEN#00eb0c,BLUE#0000ff,GRAY#AAAAAA,VIOLET#ff00ff
WithPeak[cf-vpn_session]: dymw


# CPU Utilization

#Target[cf-vpn_cpu]:alGeneralGaugeCpuUtil.0&alHardwareCpuTempCount.0:look-no
-han
ds at cf-vpn
Target[cf-vpn_cpu]:.1.3.6.1.4.1.3076.2.1.2.25.1.2.0&1.3.6.1.4.1.3076.2.1.2.2
2.1.
31.0:public at cf-vpn
MaxBytes[cf-vpn_cpu]: 100
Title[cf-vpn_cpu]: CPU
PageTop[cf-vpn_cpu]: <H1>cf-vpn CPU Utilization</H1>
YLegend[cf-vpn_cpu]: CPU
Options[cf-vpn_cpu]:gauge, growright, unknaszero
ShortLegend[cf-vpn_cpu]: CPU
Legend1[cf-vpn_cpu]:
Legend2[cf-vpn_cpu]:
Legend3[cf-vpn_cpu]:
Legend4[cf-vpn_cpu]:
LegendI[cf-vpn_cpu]: CPU
LegendO[cf-vpn_cpu]:
Colours[cf-vpn_cpu]: GREEN#00eb0c,BLUE#0000ff,GRAY#AAAAAA,VIOLET#ff00ff
WithPeak[cf-vpn_cpu]: dymw


# Throughput

#Target[cf-vpn_thru]:alGeneralGaugeThroughput.0&alHardwareCpuTempCount.0:loo
k-no
-hands at cf-vpn
Target[cf-vpn_thru]:1.3.6.1.4.1.3076.2.1.2.17.1.1.0&1.3.6.1.4.1.3076.2.1.2.2
2.1.
31.0:public at cf-vpn
MaxBytes[cf-vpn_thru]: 100
Title[cf-vpn_thru]: Throughput
PageTop[cf-vpn_thru]: <H1>cf-vpn Throughput</H1>
YLegend[cf-vpn_thru]: Throughput
Options[cf-vpn_thru]: gauge, growright, unknaszero
ShortLegend[cf-vpn_thru]:
Legend1[cf-vpn_thru]:
Legend2[cf-vpn_thru]:
Legend3[cf-vpn_thru]:
Legend4[cf-vpn_thru]:
LegendI[cf-vpn_thru]: Throughput
LegendO[cf-vpn_thru]:
Colours[cf-vpn_thru]: GREEN#00eb0c,BLUE#0000ff,GRAY#AAAAAA,VIOLET#ff00ff
WithPeak[cf-vpn_thru]: dymw



Thanks for the suggestion Dave.

Well, AFAIK, MRTG has to plot two OID's for each device it polls and I
think it would be tidier to poll just the one device rather than it's
switch port as well. I know there is an OID for throughput on the VPN
concentrator, I just can't find what it is!

If anyone knows, please let me know!

Thanks,

James.





--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi