Sorry, I was wrong in saying the snmpgetnext command returns nothing.. I had
to use a different interface index as all the first ones are for DS1
interfaces.
For the lan interfaces with snmpgetnext I do see the wrong value
node> snmpgetnext -v2c -c public <ip address> ifPhysAddress.8
IF-MIB::ifPhysAddress.9 = STRING:
30:30:3a:31:30:3a:32:33:3a:63:30:3a:34:32:3a:35:64
--- On Fri, 7/16/10, Mike Ayers <mike_ay...@tva.tvworks.com> wrote:
From: Mike Ayers <mike_ay...@tva.tvworks.com>
Subject: RE: ifPhysAddress value shown wrong on NetSNMP client for ifTable
To: "Malathi Panyam" <malathipan...@yahoo.com>,
net-snmp-users@lists.sourceforge.net
Date: Friday, July 16, 2010, 10:14 AM
> From: Malathi Panyam [mailto:malathipan...@yahoo.com]
> Sent: Friday, July 16, 2010 9:17 AM
> Thanks for the reply. I see nothing with the snmpgetnext
>
> Node> snmpgetnext -v2c -c public <ip address> ifPhysAddress.1
> IF-MIB::ifPhysAddress.2 = STRING:
What's the matching ifDescr?
Did you really want the second row?
HTH,
Mike
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
