Status in source: current.
Names: agentFIPSnoopingVlanStatisticsTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"agentFIPSnoopingVlanStatisticsTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"AgentFIPSnoopingVlanStatsEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"A table containing per-port, per-VLAN statistics for traffic received. Separate objects are provided for both the most-significant and least-significant bits of statistics counters for ports that are associated with this transparent bridge. The most-significant bit objects are only required on high capacity interfaces, as defined in the conformance clauses for these objects. This mechanism is provided as a way to read 64-bit counters for agents which support only SNMPv1. Note that the reporting of most-significant and least- significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification.\"",
"::=",
"{",
"agentFIPSnoopingStatisticsGroup",
"1",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"AgentFIPSnoopingVlanStatsEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"A table containing per-port, per-VLAN statistics for traffic received. Separate objects are provided for both the most-significant and least-significant bits of statistics counters for ports that are associated with this transparent bridge. The most-significant bit objects are only required on high capacity interfaces, as defined in the conformance clauses for these objects. This mechanism is provided as a way to read 64-bit counters for agents which support only SNMPv1. Note that the reporting of most-significant and least- significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification."
],
null,
null,
null,
null
]
}
- NETGEAR official product and EOL MIB downloads
· Publisher's source file: Source package: M6100-Mibs-v11.0.0.10.zip
Module: NETGEAR-FIPSNOOPING-MIB
See published definition above
Module imports
{'IF-MIB': ['InterfaceIndex', 'ifIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['RowStatus', 'TimeStamp', 'TruthValue', 'MacAddress', 'MacAddress', 'DateAndTime', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Counter32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'Q-BRIDGE-MIB': ['VlanIndex', 'dot1qVlanIndex'], 'NETGEAR-REF-MIB': ['ng7000managedswitch'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
Related source files and packages:
Show more related files and packages
Same file in m6100v11.0.0.31-mibs.zip.
Same file in m6100v11.0.0.28-mibs.zip.
Same file in m6100v11.0.0.25-mibs.zip.
Same file in m6100v11.0.0.18-mibs.zip.
- NETGEAR official product and EOL MIB downloads
· Publisher's source file: Source package: m6100v11.0.0.40-mibs.zip
Module: NETGEAR-FIPSNOOPING-MIB
See published definition above
Module imports
{'IF-MIB': ['InterfaceIndex', 'ifIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['RowStatus', 'TimeStamp', 'TruthValue', 'MacAddress', 'MacAddress', 'DateAndTime', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Counter32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'Q-BRIDGE-MIB': ['VlanIndex', 'dot1qVlanIndex'], 'NETGEAR-REF-MIB': ['ng7000managedswitch'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
Related source files and packages: