Description
I saw that LLDPv2 MIBs already present but it looks like that they are not in use.
Is it planned to add this protocol?
Attachments
Activity
yah, still no useful information about remote neighbours:
LLDP-V2-MIB::lldpV2MessageTxInterval.0 = Gauge32: 30 seconds
|
LLDP-V2-MIB::lldpV2MessageTxHoldMultiplier.0 = Gauge32: 4
|
LLDP-V2-MIB::lldpV2ReinitDelay.0 = Gauge32: 2 seconds
|
LLDP-V2-MIB::lldpV2NotificationInterval.0 = Gauge32: 30 seconds
|
LLDP-V2-MIB::lldpV2TxCreditMax.0 = Gauge32: 5 PDUs
|
LLDP-V2-MIB::lldpV2MessageFastTx.0 = Gauge32: 1 seconds
|
LLDP-V2-MIB::lldpV2TxFastInit.0 = Gauge32: 4
|
LLDP-V2-MIB::lldpV2PortConfigAdminStatus.1.1 = INTEGER: disabled(4)
|
LLDP-V2-MIB::lldpV2PortConfigAdminStatus.2.1 = INTEGER: disabled(4)
|
LLDP-V2-MIB::lldpV2PortConfigAdminStatus.3.1 = INTEGER: disabled(4)
|
LLDP-V2-MIB::lldpV2PortConfigAdminStatus.4.1 = INTEGER: disabled(4)
|
LLDP-V2-MIB::lldpV2PortConfigAdminStatus.5.1 = INTEGER: disabled(4)
|
LLDP-V2-MIB::lldpV2PortConfigAdminStatus.6.1 = INTEGER: disabled(4)
|
LLDP-V2-MIB::lldpV2PortConfigAdminStatus.7.1 = INTEGER: disabled(4)
|
LLDP-V2-MIB::lldpV2PortConfigAdminStatus.8.1 = INTEGER: disabled(4)
|
LLDP-V2-MIB::lldpV2PortConfigNotificationEnable.1.1 = INTEGER: false(2)
|
LLDP-V2-MIB::lldpV2PortConfigNotificationEnable.2.1 = INTEGER: false(2)
|
LLDP-V2-MIB::lldpV2PortConfigNotificationEnable.3.1 = INTEGER: false(2)
|
LLDP-V2-MIB::lldpV2PortConfigNotificationEnable.4.1 = INTEGER: false(2)
|
LLDP-V2-MIB::lldpV2PortConfigNotificationEnable.5.1 = INTEGER: false(2)
|
LLDP-V2-MIB::lldpV2PortConfigNotificationEnable.6.1 = INTEGER: false(2)
|
LLDP-V2-MIB::lldpV2PortConfigNotificationEnable.7.1 = INTEGER: false(2)
|
LLDP-V2-MIB::lldpV2PortConfigNotificationEnable.8.1 = INTEGER: false(2)
|
LLDP-V2-MIB::lldpV2PortConfigTLVsTxEnable.1.1 = BITS: 00 00 00 F0 FF FF FF FF 24 25 26 27 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
|
LLDP-V2-MIB::lldpV2PortConfigTLVsTxEnable.2.1 = BITS: 00 00 00 F0 FF FF FF FF 24 25 26 27 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
|
LLDP-V2-MIB::lldpV2PortConfigTLVsTxEnable.3.1 = BITS: 00 00 00 F0 FF FF FF FF 24 25 26 27 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
|
LLDP-V2-MIB::lldpV2PortConfigTLVsTxEnable.4.1 = BITS: 00 00 00 F0 FF FF FF FF 24 25 26 27 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
|
LLDP-V2-MIB::lldpV2PortConfigTLVsTxEnable.5.1 = BITS: 00 00 00 F0 FF FF FF FF 24 25 26 27 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
|
LLDP-V2-MIB::lldpV2PortConfigTLVsTxEnable.6.1 = BITS: 00 00 00 F0 FF FF FF FF 24 25 26 27 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
|
LLDP-V2-MIB::lldpV2PortConfigTLVsTxEnable.7.1 = BITS: 00 00 00 F0 FF FF FF FF 24 25 26 27 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
|
LLDP-V2-MIB::lldpV2PortConfigTLVsTxEnable.8.1 = BITS: 00 00 00 F0 FF FF FF FF 24 25 26 27 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
|
LLDP-V2-MIB::lldpV2DestMacAddress.1 = STRING: x:x:x:x:x:x
|
LLDP-V2-MIB::lldpV2LocChassisIdSubtype.0 = INTEGER: macAddress(4)
|
LLDP-V2-MIB::lldpV2LocChassisId.0 = STRING: 30:30:20:31:66:20:61:30:20:31:33:20:31:66:20:33:30
|
LLDP-V2-MIB::lldpV2LocSysName.0 = STRING: XXX
|
LLDP-V2-MIB::lldpV2LocSysDesc.0 = STRING: Thunder Series Unified Application Service Gateway TH5330, ACOS 4.1.4-GR1-P1
|
Serial Number: XXX
|
Host Name: XXX
|
|
|
LLDP-V2-MIB::lldpV2LocSysCapSupported.0 = BITS: 28 00 bridge(2) router(4)
|
LLDP-V2-MIB::lldpV2LocSysCapEnabled.0 = BITS: 08 00 router(4)
|
LLDP-V2-MIB::lldpV2LocPortIdSubtype.1 = INTEGER: interfaceName(5)
|
LLDP-V2-MIB::lldpV2LocPortIdSubtype.2 = INTEGER: interfaceName(5)
|
LLDP-V2-MIB::lldpV2LocPortIdSubtype.3 = INTEGER: interfaceName(5)
|
LLDP-V2-MIB::lldpV2LocPortIdSubtype.4 = INTEGER: interfaceName(5)
|
LLDP-V2-MIB::lldpV2LocPortIdSubtype.5 = INTEGER: interfaceName(5)
|
LLDP-V2-MIB::lldpV2LocPortIdSubtype.6 = INTEGER: interfaceName(5)
|
LLDP-V2-MIB::lldpV2LocPortIdSubtype.7 = INTEGER: interfaceName(5)
|
LLDP-V2-MIB::lldpV2LocPortIdSubtype.8 = INTEGER: interfaceName(5)
|
LLDP-V2-MIB::lldpV2LocPortId.1 = STRING: 45:74:68:65:72:6e:65:74:20:31
|
LLDP-V2-MIB::lldpV2LocPortId.2 = STRING: 45:74:68:65:72:6e:65:74:20:32
|
LLDP-V2-MIB::lldpV2LocPortId.3 = STRING: 45:74:68:65:72:6e:65:74:20:33
|
LLDP-V2-MIB::lldpV2LocPortId.4 = STRING: 45:74:68:65:72:6e:65:74:20:34
|
LLDP-V2-MIB::lldpV2LocPortId.5 = STRING: 45:74:68:65:72:6e:65:74:20:35
|
LLDP-V2-MIB::lldpV2LocPortId.6 = STRING: 45:74:68:65:72:6e:65:74:20:36
|
LLDP-V2-MIB::lldpV2LocPortId.7 = STRING: 45:74:68:65:72:6e:65:74:20:37
|
LLDP-V2-MIB::lldpV2LocPortId.8 = STRING: 45:74:68:65:72:6e:65:74:20:38
|
LLDP-V2-MIB::lldpV2LocPortDesc.1 = STRING: Interface Ethernet 1
|
LLDP-V2-MIB::lldpV2LocPortDesc.2 = STRING: Interface Ethernet 2
|
LLDP-V2-MIB::lldpV2LocPortDesc.3 = STRING: Interface Ethernet 3
|
LLDP-V2-MIB::lldpV2LocPortDesc.4 = STRING: Interface Ethernet 4
|
LLDP-V2-MIB::lldpV2LocPortDesc.5 = STRING: Interface Ethernet 5
|
LLDP-V2-MIB::lldpV2LocPortDesc.6 = STRING: Interface Ethernet 6
|
LLDP-V2-MIB::lldpV2LocPortDesc.7 = STRING: Interface Ethernet 7
|
LLDP-V2-MIB::lldpV2LocPortDesc.8 = STRING: Interface Ethernet 8
|
Hey Mike,
I created new snmpwalk. Can you check if that is okay for you? ![]()
Yah, every quarter I double-check old issues and now I'm found that I missed your mail about this.
Can you duplicate mail?
Or better now - make snmp dump for A10 device as for other devices:
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
|
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
|
dklimek But I need access to device with real data.
Can you provide temporary access to A10 device with LLDP v2 data?
If yes, please write me to mail: mike@observium.org (or in official irc channel, nick - landy).
A10 devices are using V2 only. There is no V1 supported. I can only talk for those two different devices from A10:
- AX Series Advanced Traffic Manager AX3400
- Thunder Series Unified Application Service Gateway TH5330
Same, I not found any devices with V2 (without V1). Not see reason for implement just "for implement".
I don't think there's any benefit to us using this at the moment. I can't imagine there are any devices which support -V2 and not the original MIB, and I have seen devices which have broken V2 implementations that break during polling.
Mhhh.... can't find any other A10 device that is giving me a working snmpwalk output. Everytime its failing with:
Error in packet.
Reason: (genError) A general failure occured
Failed object: .1.3.6.1.4.1.22610.2.4.3.2.2.2.1.15.31.34.86.82.70.95.73.110.102.114.97.95.73.110.116.34.58.49.57.50.46.49.54.56.46.49.49.53.46.49.55.55