Antwort: RE: MRTG graphs problem - measurement units not taken into consideration

[Jim Avery]

On 29 June 2011 11:45,  <Radu.Popa at technomatic.de> wrote:
> Was a typo error of the community string, after putting "public" instead of
> "Public" everything looks cool.
>
> Still 1 question:
>
> If I try to query interface GigabitEthernet0/2 I get the response:
>
> GigabitEthernet0/21:DOWN, GigabitEthernet0/23:DOWN, GigabitEthernet0/24:UP
> No usable data on file (40 rows) , GigabitEthernet0/2:UP No usable data on
> file (1 rows) , GigabitEthernet0/22:DOWN, GigabitEthernet0/20:UP No usable
> data on file (1 rows) : 3 int NOK : CRITICAL
>
> So ti seems that it takes all interfaces starting with "0/2" string. Any way
> to limit this? Do I have to enter any escape character?
>
> Thank you!


I think you need the "-r" option, which means "Do not use regexp to
match NAME in description OID".

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null