FW: [802.1] [802.1AB]: Problem with the lldpXdot1RemProtoVlanEntry table inde x
"Romascanu, Dan \(Dan\)" <[email protected]> Thu, 20 Jan 2005 15:08:00 +0200
| Newsgroups | gmane.ietf.bridge |
|---|---|
| Message-ID | <AAB4B3D3CF0F454F98272CBE187FDE2F038AA021@is0004avexu1.global.avaya.com> |
The following question was asked on the IEEE 802.1 e-mail list. The referred index object lldpXdot1RemProtoVlanId has a syntax of Integer32(0|1..4094) - kind of similar to the TC once proposed by Bert. Regards, Dan -----Original Message----- From: IEEE 802.1 [mailto:[email protected]]On Behalf Of Eelco Chaudron Sent: 20 January, 2005 9:35 AM To: [email protected] Subject: [802.1] [802.1AB]: Problem with the lldpXdot1RemProtoVlanEntry table inde x Hi All, When implementing the dot1 extension MIB I was running into a problem with the lldpXdot1RemProtoVlanTable. The table has the following indexes: - lldpRemTimeMark - lldpRemLocalPortNum - lldpRemIndex - lldpXdot1RemProtoVlanId The problem lies within the last index, lldpXdot1RemProtoVlanId. This can have a value of zero, and would be causing an infinite loop when doing SNMP getnext operations. To my understanding a SNMP index can never have a value of zero, as it indicates to SNMP to get the first value. How would we hande this? For example not returning entries in the lldpXdot1RemProtoVlanTable wich have a vlanid of zero? Or report the zero values as 4096? Regards, Eelco IEEE 802.1 list info: http://www.ieee802.org/1/email-pages/etkg1204.html