Status in source: current.
Names: h3cDot11WIDSRogueAPExtTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"h3cDot11WIDSRogueAPExtTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"H3cDot11WIDSRogueAPExtEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"As each rogue AP could be detected by multiple monitor APs, each monitor AP could have some kind of detailed information about a specific rogue AP. In the h3cDot11WIDSRogueAPTable table, the detailed information for a specific rogue AP will be summarized from information in the h3cDot11WIDSRogueAPExtTable table. For example, multiple monitor APs could receive RF signal of one rogue AP, and each monitor AP has its maximum signal strength by itself. The information will be kept as h3cDot11DetectMaxAPSigStrength in the h3cDot11WIDSRogueAPExtTable table. While only the maximum value among all the h3cDot11DetectMaxAPSigStrength for each monitor AP will be kept in the h3cDot11WIDSRogueAPTable as h3cDot11RogueAPMaxSigStrength.\"",
"::=",
"{",
"h3cDot11WIDSDetectGroup",
"2",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"H3cDot11WIDSRogueAPExtEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"As each rogue AP could be detected by multiple monitor APs, each monitor AP could have some kind of detailed information about a specific rogue AP. In the h3cDot11WIDSRogueAPTable table, the detailed information for a specific rogue AP will be summarized from information in the h3cDot11WIDSRogueAPExtTable table. For example, multiple monitor APs could receive RF signal of one rogue AP, and each monitor AP has its maximum signal strength by itself. The information will be kept as h3cDot11DetectMaxAPSigStrength in the h3cDot11WIDSRogueAPExtTable table. While only the maximum value among all the h3cDot11DetectMaxAPSigStrength for each monitor AP will be kept in the h3cDot11WIDSRogueAPTable as h3cDot11RogueAPMaxSigStrength."
],
null,
null,
null,
null
]
}
- H3C and HH3C MIB copies (Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
H3C and HH3C support.
Module: H3C-DOT11-WIDS-MIB
See published definition above
Module imports
{'SNMPv2-TC': ['TruthValue', 'MacAddress', 'RowStatus', 'DateAndTime', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32', 'TimeTicks'], 'H3C-DOT11-REF-MIB': ['h3cDot11', 'H3cDot11SSIDStringType', 'H3cDot11ChannelScopeType', 'H3cDot11RadioScopeType', 'H3cDot11ObjectIDType', 'H3cDot11RadioType']}
Related source files and packages:
- Netdisco MIB archive copies
· Publisher's source file: h3c-dot11-wids.mib
Vendor MIB copy from the Netdisco archive.
Module: H3C-DOT11-WIDS-MIB
Same published definition
Module imports
{'SNMPv2-TC': ['TruthValue', 'MacAddress', 'RowStatus', 'DateAndTime', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32', 'TimeTicks'], 'H3C-DOT11-REF-MIB': ['h3cDot11', 'H3cDot11SSIDStringType', 'H3cDot11ChannelScopeType', 'H3cDot11RadioScopeType', 'H3cDot11ObjectIDType', 'H3cDot11RadioType']}
Related source files and packages: