[mrtg] MIB query (re HP/Nortel Blade switches )...
Hazell Derek
dhazell at aap.com.au
Tue Feb 3 00:10:39 CET 2009
Hi Scott
I tried the ifdesc-alias option within cfgmaker, but it made little or
no difference - the Description field in the cfgmaker output still comes
up empty.
Seems to me though it is firstly a problem in the setup of the HP/Nortel
GbE2c blade switch. As I mentioned before an snmpwalk against the blade
switch returns info but no port description data. Actually the snmpwalk
command also returns an error (I don't know if that error is significant
- perhaps the missing description data is not being returned because of
this error(?)) (see below).
So I suspect I need to do something in the blade switch so that snmpwalk
will return the description data. Once snmpwalk can see that data then
perhaps mrtg cfgmaker will see the descriptions as well ...
regards
Derek
##########################################
BRIEF OUTPUT OF SNMPWALK COMMAND AGAINST BLADE SWITCH (NOTE ERROR AT THE
END)
$ snmpwalk -v2c -commstring bs11.xx.yyy
SNMPv2-MIB::sysDescr.0 = STRING: GbE2c Ethernet Blade Switch for HP
c-Class BladeSystem
SNMPv2-MIB::sysObjectID.0 = OID:
SNMPv2-SMI::enterprises.11.2.3.7.11.33.4.1.1
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2364917000) 273 days,
17:12:50.00
SNMPv2-MIB::sysContact.0 = STRING:
SNMPv2-MIB::sysName.0 = STRING: BS11.XX.YYY
SNMPv2-MIB::sysLocation.0 = STRING:
SNMPv2-MIB::sysServices.0 = INTEGER: 6
IF-MIB::ifNumber.0 = INTEGER: 280
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.257 = INTEGER: 257
IF-MIB::ifIndex.258 = INTEGER: 258
.
.
.
IF-MIB::ifInOctets.1 = Counter32: 2727786347
IF-MIB::ifInOctets.257 = Counter32: 142588718
IF-MIB::ifInOctets.258 = Counter32: 1280817
IF-MIB::ifInOctets.259 = Counter32: 0
.
.
.
IF-MIB::ifOutOctets.1 = Counter32: 1559593044
IF-MIB::ifOutOctets.257 = Counter32: 3928445505
IF-MIB::ifOutOctets.258 = Counter32: 272537458
IF-MIB::ifOutOctets.259 = Counter32: 262899569
.
.
.
Error: OID not increasing: RFC1213-MIB::ipRouteDest.224.0.0.0
>= RFC1213-MIB::ipRouteDest.224.0.0.0
-----Original Message-----
From: mrtg-bounces at lists.oetiker.ch
[mailto:mrtg-bounces at lists.oetiker.ch] On Behalf Of Scott Ocken
Sent: Tuesday, 3 February 2009 2:37 AM
To: mrtg at lists.oetiker.ch
Subject: Re: [mrtg] MIB query (re HP/Nortel Blade switches )...
For the Nortel 8600 switch you want to use --ifdesc=alias in cfgmaker.
Alias seems to work for most Nortel switches. In the past I hacked in
an alias2 for the 4500 series, but after upgrading MRTG I lost that,
and I don't think it was needed after that anyway.
Hope that helps with the Nortel Switches. Let me know if you have any
other Nortel switch issues as that is the only switch we use here.
Scott
Quoting "Mersberger, Robert" <robert.mersberger at goldenliving.com>:
> I will be watching this post because I am in the same situation. I
> did some research some time ago but final settled on what I could
> get. I would also like better descriptions for the interfaces but
> I can work with what HP/Nortel provide.
>
> ________________________________
> From: mrtg-bounces at lists.oetiker.ch
> [mailto:mrtg-bounces at lists.oetiker.ch] On Behalf Of Steve Shipway
> Sent: Sunday, February 01, 2009 6:21 PM
> To: 'Hazell Derek'; 'mrtg at lists.oetiker.ch'
> Subject: Re: [mrtg] MIB query (re HP/Nortel Blade switches )...
>
> Possibly, on the Nortel switch, the port descriptions are stored in
> a different vendor-specific area (cisco do this, but cfgmaker has
> specific support for the cisco description). In this case, you'd
> need to write your own interface template to extract and use them.
>
> Another possibility is that a weird auth rule on the switch is
> blanking out this specific community from viewing the specified
> OIDs, but this is less likely.
>
> Steve
>
>
> ________________________________
> From: mrtg-bounces at lists.oetiker.ch
> [mailto:mrtg-bounces at lists.oetiker.ch] On Behalf Of Hazell Derek
>
>
> By the way, regarding my query about the HP/Nortel blade switches I
> should have mentioned, when I run snmpwalk against the HP blade
> switch, that the snmpwalk response is missing the description data,
> while a similar snmpwalk query against a cisco switch does return
> the port description data.
>
> So it seems to me that I must do something to the blade switch to
> make the description data accessible. It also seems to me that I
> might need to also do something to the mrtg server to make it return
> this description data. Appreciate any guidance.
>
>
>
>
> Please consider the environment before printing this e-mail.
>
> CONFIDENTIAL NOTICE:
> This e-mail message and any attachment(s) (collectively, this
> 'Email') are intended
> only for the confidential use of the recipient(s) named above. If
> the reader of this
> message is not the intended recipient named above or an agent
responsible for
> delivering it to the intended recipient named above, you have
> received this Email in error.
> Please notify the sender immediately and permanently delete this
> Email and any copies thereof.
>
**********************************************************************
This email is intended for the use of the addressee only. If you receive this email in error, please delete it immediately. This email may contain information which is confidential and/or legally privileged. You must not use or disclose the contents of this email, or add the sender's email address to any database, list or mailing list unless you are expressly authorised to do so.
The statements or views expressed in this email are those of the individual sender and are not those of Australian Associated Press Pty Ltd (AAP). These statements are not binding on AAP, except where the sender expressly and with authority, states them to be.
AAP is unable to review the contents of all the email on its system. To the extent permitted by law, AAP disclaims all liability for any loss or damage caused by the contents of this email.
www.aap.com.au
**********************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/mrtg/attachments/20090203/2d2c5c94/attachment-0001.html
More information about the mrtg
mailing list