Re: [Devmon] cisco templates

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Also, just a suggestion,  move unused or old templates out of the
template directory and store them somewhere else.  The entire directory
is read for templates.

-----Original Message-----
From: dev...@li...
[mailto:dev...@li...] On Behalf Of Trent
Melcher
Sent: Friday, September 21, 2007 3:14 PM
To: dev...@li...
Subject: Re: [Devmon] cisco templates

Check your specs file.  You have 2 templates with the same model or
sysdesc defined.

Trent

On Fri, 2007-09-21 at 16:00 -0400, Joshua Krause wrote:
> does anyone get this with templates?
>=20
> [07-09-21@15:59:06] Attempting to redefine cisco/6509/power template =20
> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@15:59:06] Attempting to redefine cisco/6509/if_col template

> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@15:59:06] Attempting to redefine cisco/6509/fans template =20
> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@15:59:06] Attempting to redefine cisco/6509/if_err template

> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@15:59:06] Attempting to redefine cisco/6509/if_stat template

> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@15:59:06] Attempting to redefine cisco/6509/cpu template =20
> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@15:59:06] Attempting to redefine cisco/6509/if_load template

> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@15:59:06] Attempting to redefine cisco/6509/if_dsc template

> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@16:00:06] Attempting to redefine cisco/6509/power template =20
> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@16:00:06] Attempting to redefine cisco/6509/if_col template

> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@16:00:06] Attempting to redefine cisco/6509/fans template =20
> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@16:00:06] Attempting to redefine cisco/6509/if_err template

> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@16:00:06] Attempting to redefine cisco/6509/if_stat template

> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@16:00:06] Attempting to redefine cisco/6509/cpu template =20
> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@16:00:06] Attempting to redefine cisco/6509/if_load template

> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
> [07-09-21@16:00:06] Attempting to redefine cisco/6509/if_dsc template

> when reading data from /opt/devmon-0.3.0-beta2/templates/cisco-6509.
>=20
>=20
>=20
> On Sep 21, 2007, at 2:28 PM, Joshua Krause wrote:
>=20
> > will do.  Do you have a template that works with a 6500 series
> > switch.  The one the comes with the Template is a little off?
> >
> >
> > On Sep 21, 2007, at 2:24 PM, Trent Melcher wrote:
> >
> >> You really need to read the devmon docs then, all 5 files work in
> >> connection with each other to produce the output you see.  The oid
> >> file
> >> is sort of at top and you can use those defs directly but they are
> >> more
> >> powerful after being manipulated as needed then reported.  Look and
> >> the
> >> TEMPLATE file in the docs  it explains this in better detail.
> >>
> >> Trent
> >>
> >> -----Original Message-----
> >> From: dev...@li...
> >> [mailto:dev...@li...] On Behalf Of
> >> Joshua Krause
> >> Sent: Friday, September 21, 2007 1:19 PM
> >> To: dev...@li...
> >> Subject: Re: [Devmon] cisco templates
> >>
> >> I guess the reason I ask is because I thought the the oids file for
> >> devmon basically did a map of name to oid.  So since I don't have
> >> ifStat defined in my oids file for the if_stat column that devmon
> >> won't understand it.
> >>
> >>
> >> On Sep 21, 2007, at 2:10 PM, Trent Melcher wrote:
> >>
> >>> Try using IfStat instead
> >>>
> >>> ifStat: ignore : admin.+
> >>>
> >>> -----Original Message-----
> >>> From: dev...@li...
> >>> [mailto:dev...@li...] On Behalf Of
> >>> Joshua Krause
> >>> Sent: Friday, September 21, 2007 1:03 PM
> >>> To: dev...@li...
> >>> Subject: Re: [Devmon] cisco templates
> >>>
> >>> the command to run with snmpwalk to just get the values back is:
> >>>
> >>> snmpwalk -Oe -v 2c -c public gsonc-arc-4948-1 .=20
> >>> 1.3.6.1.2.1.2.2.1.7.38
> >>> IF-MIB::ifAdminStatus.38 =3D INTEGER: 2
> >>>
> >>> rather than:
> >>> [hobbit@gsonc-spg-ops-1 cisco-4948]$ snmpwalk -v 2c -c public
gsonc-
> >>> arc-4948-1 .1.3.6.1.2.1.2.2.1.7.38
> >>> IF-MIB::ifAdminStatus.38 =3D INTEGER: down(2)
> >>>
> >>> But devmon is still reporting the items that are "admin down" =20
> >>> which I
> >>> thought I was telling it not to by:
> >>> ifAdminStatNum : ignore : 2
> >>>
> >>> and i've tried it:
> >>> ifAdminStatNum : ignore : 2.+
> >>>
> >>> Don't know what is going on.
> >>>
> >>>
> >>>
> >>> On Sep 21, 2007, at 11:55 AM, Trent Melcher wrote:
> >>>
> >>>> On Fri, 2007-09-21 at 11:44 -0400, Joshua Krause wrote:
> >>>>> I tried throwing an exception in this format:
> >>>>>
> >>>>> ifAdminStatNum : ignore : down(2)
> >>>>
> >>>> Try just "2"   the down is being added from the MIB your OID is =20
> >>>> only
> >>>> reporting 2
> >>>>
> >>>> There is an option in snmpwalk to turn that off so you can see
just
> >>>> the
> >>>> stat being pulled.
> >>>>
> >>>> Look at your transform file you should see something similar to
> >>>> this:
> >>>>
> >>>> ifAdminStatTxt  : SWITCH        : {ifAdminStatNum} =
1=3Dup,2=3Dadmin
> >>>> down,3=3Dtesting
> >>>> ifOperStatTxt   : SWITCH        : {ifOperStatNum}
> >>>> 1=3Dup,2=3Ddown,3=3Dtesting,4=3Dunknown,5=3Ddormant,6=3Dnot =
present,7=3Dlowe
> >>>> r layer down
> >>>> ifStat          : BEST          :
{ifAdminStatTxt},{ifOperStatTxt}
> >>>> ifSpeed         : SPEED         : {ifBps}
> >>>> ifAliasBox      : REGSUB        : {ifAlias} /(\S+.*)/ [$1]/
> >>>>
> >>>> This shows where the "admin down" gets defined from to be
displayed
> >>>>
> >>>>>
> >>>>> Which i was hoping that it would just not display anything with
a
> >>>>> down(2) state.  But when i do an snmpwalk with the =20
> >>>>> "ifAdminStatNum"
> >>>>> it
> >>>>> doesn't kick back anything.
> >>>>>
> >>>>> [hobbit@gsonc-spg-ops-1 if_stat]$ snmpwalk -v 2c -c public
gsonc-
> >>>>> arc-4948-1 ifAdminStatNum
> >>>>> ifAdminStatNum: Unknown Object Identifier (Sub-id not found:
(top)
> >>>>> ->
> >>>>> ifAdminStatNum)
> >>>>>
> >>>>>
> >>>>> but if i do this:
> >>>>>
> >>>>> [hobbit@gsonc-spg-ops-1 if_stat]$ snmpwalk -v 2c -c public
gsonc-
> >>>>> arc-4948-1 ifAdminStatus
> >>>>> IF-MIB::ifAdminStatus.2 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.3 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.4 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.5 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.6 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.7 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.8 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.9 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.10 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.11 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.12 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.13 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.14 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.15 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.16 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.17 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.18 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.19 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.20 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.21 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.22 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.23 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.24 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.25 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.26 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.27 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.28 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.29 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.30 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.31 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.32 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.33 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.34 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.35 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.36 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.37 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.38 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.39 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.40 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.41 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.42 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.43 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.44 =3D INTEGER: down(2)
> >>>>> IF-MIB::ifAdminStatus.45 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.46 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.47 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.48 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.49 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.50 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.51 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.52 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.53 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.54 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.55 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.56 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.57 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.58 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.59 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.60 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.61 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.62 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.63 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.64 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.65 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.66 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.67 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.68 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.69 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.70 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.71 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.72 =3D INTEGER: up(1)
> >>>>> IF-MIB::ifAdminStatus.73 =3D INTEGER: up(1)
> >>>>>
> >>>>>
> >>>>> Now the current oids file for if_stat has these listed:
> >>>>>
> >>>>> [hobbit@gsonc-spg-ops-1 if_stat]$ more oids
> >>>>> ifName		: .1.3.6.1.2.1.31.1.1.1.1	: branch
> >>>>> ifAlias		: .1.3.6.1.2.1.31.1.1.1.18	: branch
> >>>>> ifBps		: .1.3.6.1.2.1.2.2.1.5		: branch
> >>>>> ifAdminStatNum	: .1.3.6.1.2.1.2.2.1.7		: branch
> >>>>> ifOperStatNum	: .1.3.6.1.2.1.2.2.1.8		: branch
> >>>>>
> >>>>>
> >>>>> Do these names need to match an actual name on the device
itself?
> >>>>> Or
> >>>>> do the OID's just need to be correct?  Or do both need to match?
> >>>>>
> >>>>> On Sep 21, 2007, at 11:29 AM, Trent Melcher wrote:
> >>>>>
> >>>>>> Look at the exception file in your templates.  The answer is in
> >>>>>> there.
> >>>>>> Also look at the TEMPLATES document in the doc folder.
> >>>>>>
> >>>>>> Trent
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: dev...@li...
> >>>>>> [mailto:dev...@li...] On Behalf

> >>>>>> Of
> >>>>>> Joshua Krause
> >>>>>> Sent: Friday, September 21, 2007 10:23 AM
> >>>>>> To: dev...@li...
> >>>>>> Subject: [Devmon] cisco templates
> >>>>>>
> >>>>>> How can i go about not showing any interface that is in an
"admin
> >>>>>> down" state.  But i would like to exclude them from all test.
> >>>>>> Until
> >>>>>> they are made active.
> >>>>>>
> >>>>>> thanks
> >>>>>>
> >>>>>>
> >>>
> >>
------------------------------------------------------------------------
> >>>>>> -
> >>>>>> This SF.net email is sponsored by: Microsoft
> >>>>>> Defy all challenges. Microsoft(R) Visual Studio 2005.
> >>>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >>>>>> _______________________________________________
> >>>>>> Devmon-support mailing list
> >>>>>> Dev...@li...
> >>>>>> https://lists.sourceforge.net/lists/listinfo/devmon-support
> >>>>>>
> >>>>>>
> >>>
> >>
------------------------------------------------------------------------
> >>> -
> >>>>>> This SF.net email is sponsored by: Microsoft
> >>>>>> Defy all challenges. Microsoft(R) Visual Studio 2005.
> >>>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >>>>>> _______________________________________________
> >>>>>> Devmon-support mailing list
> >>>>>> Dev...@li...
> >>>>>> https://lists.sourceforge.net/lists/listinfo/devmon-support
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>
------------------------------------------------------------------------
> >>> -
> >>>>> This SF.net email is sponsored by: Microsoft
> >>>>> Defy all challenges. Microsoft(R) Visual Studio 2005.
> >>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >>>>> _______________________________________________
> >>>>> Devmon-support mailing list
> >>>>> Dev...@li...
> >>>>> https://lists.sourceforge.net/lists/listinfo/devmon-support
> >>>>
> >>>>
> >>>
> >>
------------------------------------------------------------------------
> >>> -
> >>>> This SF.net email is sponsored by: Microsoft
> >>>> Defy all challenges. Microsoft(R) Visual Studio 2005.
> >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >>>> _______________________________________________
> >>>> Devmon-support mailing list
> >>>> Dev...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/devmon-support
> >>>
> >>>
> >>>
> >>
------------------------------------------------------------------------
> >>> -
> >>> This SF.net email is sponsored by: Microsoft
> >>> Defy all challenges. Microsoft(R) Visual Studio 2005.
> >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >>> _______________________________________________
> >>> Devmon-support mailing list
> >>> Dev...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/devmon-support
> >>>
> >>>
> >>
------------------------------------------------------------------------
> >> -
> >>> This SF.net email is sponsored by: Microsoft
> >>> Defy all challenges. Microsoft(R) Visual Studio 2005.
> >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >>> _______________________________________________
> >>> Devmon-support mailing list
> >>> Dev...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/devmon-support
> >>
> >>
> >>
------------------------------------------------------------------------
> >> -
> >> This SF.net email is sponsored by: Microsoft
> >> Defy all challenges. Microsoft(R) Visual Studio 2005.
> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >> _______________________________________________
> >> Devmon-support mailing list
> >> Dev...@li...
> >> https://lists.sourceforge.net/lists/listinfo/devmon-support
> >>
> >>
------------------------------------------------------------------------
-
> >> This SF.net email is sponsored by: Microsoft
> >> Defy all challenges. Microsoft(R) Visual Studio 2005.
> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >> _______________________________________________
> >> Devmon-support mailing list
> >> Dev...@li...
> >> https://lists.sourceforge.net/lists/listinfo/devmon-support
> >
> >
> >
------------------------------------------------------------------------
-
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Devmon-support mailing list
> > Dev...@li...
> > https://lists.sourceforge.net/lists/listinfo/devmon-support
>=20
>=20
>
------------------------------------------------------------------------
-
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support

------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Devmon-support mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devmon-support

Re: [Devmon] cisco templates

SNMP poller for Xymon

Re: [Devmon] cisco templates