---
oid: "1.3.6.1.4.1.2011.10.2.75.5.2.2"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2011 h3c(10) h3cCommon(2) h3cDot11(75) h3cDot11WIDS(5) h3cDot11WIDSDetectGroup(2) h3cDot11WIDSRogueAPExtTable(2)}"
description: "h3cDot11WIDSRogueAPExtTable OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2018-01-08"
---

## OID : `1.3.6.1.4.1.2011.10.2.75.5.2.2`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2011 h3c(10) h3cCommon(2) h3cDot11(75) h3cDot11WIDS(5) h3cDot11WIDSDetectGroup(2) h3cDot11WIDSRogueAPExtTable(2)}
```

### Description

```asn1
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."
```

**Classification**: MIB object for network management

### Child OIDs

- [OID `1.3.6.1.4.1.2011.10.2.75.5.2.2.1`](https://oid-base.com/get-md/1.3.6.1.4.1.2011.10.2.75.5.2.2.1): `h3cDot11WIDSRogueAPExtEntry(1)`

### Terms of Use
[Terms of use](https://oid-base.com/disclaimer.htm.md)
