netscreen devmon templates

pkc_mls pkc_mls at yahoo.fr
Thu Oct 2 14:25:23 CEST 2008


Hi all,

Here are the netscreen devmon templates I created and tested on an ns5gt 
running screenos 5.4.

my 2 cents of netscreen templates :

--------------------------
cpu directory :
[message]
{sysUpTimeSecs.color}: Up for {UpTimeTxt}
{nsResCpuLast5Min.color}: CPU usage: {nsResCpuLast5Min}%

System description:
{sysDescr}
<!--
<br>CPU 5 min average: {nsResCpuLast5Min}
-->

[oids]
sysDescr        : .1.3.6.1.2.1.1.1.0                    : leaf
sysUpTime       : .1.3.6.1.2.1.1.3.0                    : leaf
nsResCpuLast5Min        : .1.3.6.1.4.1.3224.16.1.3.0            : leaf

[thresholds]

nsResCpuLast5Min        : red           : >70   : CPU utilization is 
very high: {nsResCpuLast5Min}%
nsResCpuLast5Min        : yellow        : >50   : CPU utilization is 
high: {nsResCpuLast5Min}%
nsResCpuLast5Min        : green         :       : CPU utilization is 
nominal: {nsResCpuLast5Min}%

sysUpTimeSecs   : red           : <600  : Device rebooted recently. 
System uptime: {UpTimeTxt}
sysUpTimeSecs   : yellow        : <5000 : Device rebooted recently. 
System uptime: {UpTimeTxt}
sysUpTimeSecs   : green         :       : System uptime: {UpTimeTxt}

[transforms]
sysUpTimeSecs   : MATH          : {sysUpTime} / 100
UpTimeTxt       : ELAPSED       : {sysUpTimeSecs}
------------------------------------------------

policy_stat directory :
[message]
TABLE:
Policy Id|Policy Name|Policy Bps|Policy status
{policyId}|{policyName}|{policyBps}|{policyStatus.color}{policyStatusTxt}{policyStatus.errors} 


[oids]
policyName              : .1.3.6.1.4.1.3224.10.1.1.24   : branch
policyId                : .1.3.6.1.4.1.3224.10.1.1.1    : branch
policyStatus            : .1.3.6.1.4.1.3224.10.1.1.23   : branch
policyBps               : .1.3.6.1.4.1.3224.10.2.1.6    : branch

[thresholds]
policyStatusTxt : green         : 
inuse                                                 : {policyId} is 
{policyStatus}
policyStatusTxt : yellow                : 
inactive                                              : {policyId} is 
{policyStatus}
policyStatusTxt : clear         : 
hidden                                                : {policyId} is 
{policyStatus}

[transforms]
policyStatusTxt : SWITCH        : {policyStatus} 
0=inactive,1=inuse,2=hidden
policySpeed     : SPEED         : {policyBps}

-----------------------------------------------
sessions directory :

[message]
{sysUpTimeSecs.color}: Up for {UpTimeTxt}
{nsResSessAllocate.color}: number of active sessions: {nsResSessAllocate}

System description:
{sysDescr}
<!--
<br>number of sessions : {nsResSessAllocate}
-->

[oids]
sysDescr        : .1.3.6.1.2.1.1.1.0                    : leaf
sysUpTime       : .1.3.6.1.2.1.1.3.0                    : leaf
nsResSessAllocate       : .1.3.6.1.4.1.3224.16.3.2.0            : leaf

[thresholds]

nsResSessAllocate       : red           : >2000 : very high number of 
sesssions: {nsResSessAllocate}%
nsResSessAllocate       : yellow        : >1800 : high number of 
sesssions: {nsResSessAllocate}%
nsResSessAllocate       : green         :       : number of sessions is 
nominal: {nsResSessAllocate}%

sysUpTimeSecs   : red           : <600  : Device rebooted recently. 
System uptime: {UpTimeTxt}
sysUpTimeSecs   : yellow        : <5000 : Device rebooted recently. 
System uptime: {UpTimeTxt}
sysUpTimeSecs   : green         :       : System uptime: {UpTimeTxt}

[transforms]
sysUpTimeSecs   : MATH          : {sysUpTime} / 100
UpTimeTxt       : ELAPSED       : {sysUpTimeSecs}

-----------------------------------
vpn_mon directory :
[message]
TABLE:
vpn name|tunnel type|local gw IP|remote gw IP|Phase1 status|Phase2 
status|bytes in|bytes out
{nsVpnMonVpnName}|{nsVpnMonTunnelTypeTxt}|{nsVpnMonMyGwIp}|{nsVpnMonRmtGwIp}|{nsVpnMonP1State.color} 
{nsVpnMonP1StateTxt}|{nsVpnMonP2State.color} 
{nsVpnMonP2StateTxt}|{nsVpnMonBytesIn}|{nsVpnMonBytesOut}

[oids]
nsVpnMonVpnName         : .1.3.6.1.4.1.3224.4.1.1.1.4   : branch
nsVpnMonTunnelType      : .1.3.6.1.4.1.3224.4.1.1.1.6   : branch
nsVpnMonRmtGwIp         : .1.3.6.1.4.1.3224.4.1.1.1.13  : branch
nsVpnMonMyGwIp          : .1.3.6.1.4.1.3224.4.1.1.1.15  : branch
nsVpnMonP1State         : .1.3.6.1.4.1.3224.4.1.1.1.21  : branch
nsVpnMonP1LifeTime      : .1.3.6.1.4.1.3224.4.1.1.1.22  : branch
nsVpnMonP2State         : .1.3.6.1.4.1.3224.4.1.1.1.23  : branch
nsVpnMonP2LifeTime      : .1.3.6.1.4.1.3224.4.1.1.1.24  : branch
nsVpnMonBytesIn         : .1.3.6.1.4.1.3224.4.1.1.1.34  : branch
nsVpnMonBytesOut        : .1.3.6.1.4.1.3224.4.1.1.1.35  : branch

[thresholds]
nsVpnMonP1StateTxt      : green         : active   : phase1 active
nsVpnMonP1StateTxt      : yellow        : inactive : phase1 inactive
nsVpnMonP2StateTxt      : green         : active   : phase2 active
nsVpnMonP2StateTxt      : yellow        : inactive : phase2 inactive

[transforms]
nsVpnMonTunnelTypeTxt:  SWITCH  : {nsVpnMonTunnelType} 
0=reserved,1=isakmp,2=ipsec-ah,3=ipsec-esp,4=ipcomp
nsVpnMonP1StateTxt: SWITCH      : {nsVpnMonP1State} 0=inactive,1=active
nsVpnMonP2StateTxt: SWITCH      : {nsVpnMonP2State} 0=inactive,1=active

-----------------------------------------------------------------
only the cpu shows graphs, if someone wishes to rewrite those to create
the graphs for policy use, sessions, etc. don't hesitate.

the session thresholds were set for an ns5gt device. you should adapt those
according to your device max sessions.





More information about the Xymon mailing list