MIB Discovery
1930 modules enregistr├ęs
Chemin
MIX : 1 (iso). 0. 8802. 1. 1. 2 (lldpMIB). 1 (lldpObjects). 2 (lldpStatistics). 2 (lldpStatsRemTablesInserts)
OID : 1.0.8802.1.1.2.1.2.2
TXT : iso. 0. 8802. 1. 1. lldpMIB. lldpObjects. lldpStatistics. lldpStatsRemTablesInserts
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.0.8802.1.1.2.1.2.2
Module LLDP-MIB (CISCO)
NomlldpStatsRemTablesInserts
Accesreadonly
Statuscurrent
DescriptionThe number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects. The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed. This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
Unitetable entries
SyntaxeZeroBasedCounter32 (RMON2-MIB)
Module LLDP-MIB (DELL)
NomlldpStatsRemTablesInserts
Accesreadonly
Statuscurrent
DescriptionThe number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects. The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed. This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
Unitetable entries
SyntaxeZeroBasedCounter32 (LLDP-MIB)
Module LLDP-MIB (Alcatel)
NomlldpStatsRemTablesInserts
Accesreadonly
Statuscurrent
DescriptionThe number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects. The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed. This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
Unitetable entries
SyntaxeZeroBasedCounter32 (LLDP-MIB)
Module LLDP-MIB (Force10-9.14.2.1)
NomlldpStatsRemTablesInserts
Accesreadonly
Statuscurrent
DescriptionThe number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects. The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed. This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
Unitetable entries
SyntaxeZeroBasedCounter32 (RMON2-MIB)
Module LLDP-MIB (FS)
NomlldpStatsRemTablesInserts
Accesreadonly
Statuscurrent
DescriptionThe number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects. The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed. This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
Unitetable entries
SyntaxeZeroBasedCounter32 (RMON2-MIB)
Module LLDP-MIB (Nexans)
NomlldpStatsRemTablesInserts
Accesreadonly
Statuscurrent
DescriptionThe number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects. The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed. This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
Unitetable entries
SyntaxeZeroBasedCounter32 (RMON2-MIB)