[mrtg] MIB query (re HP/Nortel Blade switches )...

Scott Ocken scott at infobunker.com
Mon Feb 2 16:37:01 CET 2009

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.


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.
> 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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 1324 bytes
Desc: PGP Public Key
Url : http://lists.oetiker.ch/pipermail/mrtg/attachments/20090202/c4558837/attachment.bin 

More information about the mrtg mailing list