RE: ifPhysAddress value shown wrong on NetSNMP client for ifTable

Malathi Panyam <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
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 <[email protected]> wrote:


From: Mike Ayers <[email protected]>
Subject: RE: ifPhysAddress value shown wrong on NetSNMP client for ifTable
To: "Malathi Panyam" <[email protected]>, [email protected]
Date: Friday, July 16, 2010, 10:14 AM


> From: Malathi Panyam [mailto:[email protected]]
> 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
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.