From: Klomp, H. <kl...@nl...> - 2007-09-25 11:23:42
|
Hi All,=20 In the Cisco templates for the interfaces (if_load) I'm only monitoring t= he interfaces that are not in a "admin down" status.=20 On the hobbit page, the interfaces in admin down state are omitted.=20 But these interfaces keep showing up in the rrd data.=20 How can I also disable the creation of the rrd data files for these inter= faces, without putting them in the except rule in the BB-HOST file ?=20 Regards,=20 Bert Klomp -----Original Message----- From: dev...@li... [mailto:devmon-support= -bo...@li...] On Behalf Of Trent Melcher Sent: vrijdag 21 september 2007 17:56 To: dev...@li... Subject: Re: [Devmon] cisco templates On Fri, 2007-09-21 at 11:44 -0400, Joshua Krause wrote: > I tried throwing an exception in this format: >=20 > ifAdminStatNum : ignore : down(2) Try just "2" the down is being added from the MIB your OID is only reporting 2 =20 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=3Dl= owe 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 >=20 > Which i was hoping that it would just not display anything with a =20 > down(2) state. But when i do an snmpwalk with the "ifAdminStatNum" it = =20 > doesn't kick back anything. >=20 > [hobbit@gsonc-spg-ops-1 if_stat]$ snmpwalk -v 2c -c public gsonc-=20 > arc-4948-1 ifAdminStatNum > ifAdminStatNum: Unknown Object Identifier (Sub-id not found: (top) -> =20 > ifAdminStatNum) >=20 >=20 > but if i do this: >=20 > [hobbit@gsonc-spg-ops-1 if_stat]$ snmpwalk -v 2c -c public gsonc-=20 > 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) >=20 >=20 > Now the current oids file for if_stat has these listed: >=20 > [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 >=20 >=20 > Do these names need to match an actual name on the device itself? Or =20 > do the OID's just need to be correct? Or do both need to match? >=20 > On Sep 21, 2007, at 11:29 AM, Trent Melcher wrote: >=20 > > 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 >=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 |