Actually, the 'pub...@643' community he has there gives the table for
VLAN 643.

And I've seen that sort of thing before, and it seems to be random
(there's probably some rhyme or reason, but I've learned that if I get
the table via SNMP multiple times, at different times of day, it
eventually catches it all).

Ken Matlock
Network Analyst
Exempla Healthcare
(303) 467-4671
[email protected]


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Phil Mayers
Sent: Wednesday, June 23, 2010 8:33 AM
To: [email protected]
Subject: Re: [c-nsp] SNMP descrepancy

On 23/06/10 15:11, Drew Weaver wrote:
> router#sh ip arp vlan 643
> Protocol  Address          Age (min)  Hardware Addr   Type   Interface
> Internet  10.1.164.46          2   0080.a38c.33d4  ARPA   Vlan643
> Internet  10.1.164.41          -   000f.f8a6.6d40  ARPA   Vlan643
> Internet  10.1.164.42        146   0030.48bf.3230  ARPA   Vlan643
>
> [r...@dev html]# snmpwalk -v2c -c pub...@643 192.168.0.1
.1.3.6.1.2.1.17.4.3.1.1

This is the dot1dTpFdb i.e. the "sh mac-address"; and by default, its 
just for vlan 1.

> SNMPv2-SMI::mib-2.17.4.3.1.1.0.15.248.166.109.64 = Hex-STRING: 00 0F
F8 A6 6D 40
> SNMPv2-SMI::mib-2.17.4.3.1.1.0.128.163.140.51.212 = Hex-STRING: 00 80
A3 8C 33 D4
>
> Does anyone know why I appear to get different data from SNMP than I
do from the switch?

Because you're polling the wrong oid?

ipNetToMedia is the arp table.
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to