getting ARP and FWT from SNMP

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

getting ARP and FWT from SNMP

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
getting ARP and FWT from SNMP
getting ARP and FWT from SNMP
2014-04-14 22:02:13
Region : Argentina

Model : TL-SG5428

Hardware Version : V1

Firmware Version :

ISP :


Hello,
I would like to get ARP tables and MAC Forwarding tables from TL-SG3424.

It is claimed that this switch is compatible with public MIBs...

But I'm not able to get any relevant information without using private enterprise MIBs - nor ARP (ipNetToMediaTable), nor FWT (dot1d/qTpFdbTable), nor even interface descriptions configured through web interface.

On the other hand, with using TL-SG3424_V1_MIB(2) private MIBs, some values are not correctly parsable:
- l2BridgeManageDynMac (1.3.6.1.4.1.11863.1.1.3.2.3.2.2.1.1) has type MacAddress (OCTET STRING (SIZE(6))), but value '00 0C 29 F2 64 2E ..).d.',
- l2BridgeManageDynPort (1.3.6.1.4.1.11863.1.1.3.2.3.2.2.1.3) has type INTEGER, but value 'PORT16'

Please allow to use above by copying values also to public MIBs structure or at least correct values to the corresponding types.

Thank you very much for your meet half-way :rolleyes:
I keep my fingers crossed, developers!
  0      
  0      
#1
Options
2 Reply
Re:getting ARP and FWT from SNMP
2014-05-21 16:26:24
Latest firmware with your 3424?
  0  
  0  
#2
Options
snmpwalk from sg3210
2014-10-24 07:50:41
after downloading the mibs for this system (3210, in my case) I was able to do an snmpwalk using net-snmp and some tweaking.

my command:

% snmpwalk -O0 -Ob -Cc -t5 -r1 -v2c -c public 192.168.1.1 .1

note, first switch is uppercase 'oh' and then a zero. second one is uppercase 'oh' and lowercase b (this helps with display-hints). the -Cc is needed since, well, tplink can't seem to code snmp mibs or agents properly (you get oid's that are not always increasing in value. but don't feel too bad, even cisco gets this wrong sometimes).

sample output:

TLSG3210-BRIDGEMANAGE-MIB::l2BridgeManageDynMac.108.98.109.82.20.158.1 = STRING: 6c:62:6d:52:14:9e
TLSG3210-BRIDGEMANAGE-MIB::l2BridgeManageDynMac.64.44.244.233.52.125.1 = STRING: 40:2c:f4:e9:34:7d
TLSG3210-BRIDGEMANAGE-MIB::l2BridgeManageDynMac.56.96.119.228.20.169.1 = STRING: 38:60:77:e4:14:a9
TLSG3210-BRIDGEMANAGE-MIB::l2BridgeManageDynMac.0.160.201.93.229.210.1 = STRING: 00:a0:c9:5d:e5:d2

...

TLSG3210-BRIDGEMANAGE-MIB::l2BridgeManageDynPort.108.98.109.82.20.158.1 = STRING: "PORT1"
TLSG3210-BRIDGEMANAGE-MIB::l2BridgeManageDynPort.64.44.244.233.52.125.1 = STRING: "PORT1"
TLSG3210-BRIDGEMANAGE-MIB::l2BridgeManageDynPort.56.96.119.228.20.169.1 = STRING: "PORT1"
TLSG3210-BRIDGEMANAGE-MIB::l2BridgeManageDynPort.0.160.201.93.229.210.1 = STRING: "PORT1"

at least for the 3210, the mac addr's do come back properly and so do the port names.

I don't have the box that you have, but this is what happens for the 3210.

fwiw

/bryan
  0  
  0  
#3
Options