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