{1 3 6 1 4 1 52642 1 1 10 2 60 3 2 1}
when use CAPWAP, we must map pkt belong to certain WMM-AC to a Certian DSCP priv/802.1p pri and as we must encap the pkt ,we must support two kind of mappings - trunnel and inner, you can get the concept in RFC 5416
Status in source: current.
Names: fsPrivMappingAPstatusTable
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsPrivMappingAPstatusTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"FSAPdefaultStatusMappingEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\" when use CAPWAP, we must map pkt belong to certain WMM-AC to a Certian DSCP priv/802.1p pri and as we must encap the pkt ,we must support two kind of mappings - trunnel and inner, you can get the concept in RFC 5416 \"",
"::=",
"{",
"fsWlanDevicePrivMappingAPDefaultObjects",
"1",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"FSAPdefaultStatusMappingEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"when use CAPWAP, we must map pkt belong to certain WMM-AC to a Certian DSCP priv/802.1p pri and as we must encap the pkt ,we must support two kind of mappings - trunnel and inner, you can get the concept in RFC 5416"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. FS.COM support.
Module: FS-WLAN-QOS-EXTRA-MIB
fsPrivMappingAPstatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF FSAPdefaultStatusMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" when use CAPWAP, we must map pkt belong to certain WMM-AC to a Certian DSCP priv/802.1p pri
and as we must encap the pkt ,we must support two kind of mappings - trunnel and inner,
you can get the concept in RFC 5416
"
::= { fsWlanDevicePrivMappingAPDefaultObjects 1 }{'FS-SMI': ['fsMgmt'], 'SNMPv2-TC': ['TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'FS-AC-MGMT-MIB': ['fsApCfgRadioId', 'fsApgWlanId', 'fsStaMacAddr', 'fsApMacAddr']}Related source files and packages:
Downloaded: 2026-10-23T19:25:17.774942+00:00.
Module: FS-WLAN-QOS-EXTRA-MIB
fsPrivMappingAPstatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF FSAPdefaultStatusMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" when use CAPWAP, we must map pkt belong to certain WMM-AC to a Certian DSCP priv/802.1p pri
and as we must encap the pkt ,we must support two kind of mappings - trunnel and inner,
you can get the concept in RFC 5416
"
::= { fsWlanDevicePrivMappingAPDefaultObjects 1 }{'FS-SMI': ['fsMgmt'], 'SNMPv2-TC': ['TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'FS-AC-MGMT-MIB': ['fsApCfgRadioId', 'fsApgWlanId', 'fsStaMacAddr', 'fsApMacAddr']}Related source files and packages:
Same file in 20240129093459svlvsn.zip.
Downloaded: 2026-10-24T13:35:05.198055+00:00.
Module: FS-WLAN-QOS-EXTRA-MIB
fsPrivMappingAPstatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF FSAPdefaultStatusMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" when use CAPWAP, we must map pkt belong to certain WMM-AC to a Certian DSCP priv/802.1p pri
and as we must encap the pkt ,we must support two kind of mappings - trunnel and inner,
you can get the concept in RFC 5416
"
::= { fsWlanDevicePrivMappingAPDefaultObjects 1 }{'FS-SMI': ['fsMgmt'], 'SNMPv2-TC': ['TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'FS-AC-MGMT-MIB': ['fsApCfgRadioId', 'fsApgWlanId', 'fsStaMacAddr', 'fsApMacAddr']}Related source files and packages:
Same file in nc8200-and-nc8400-series-swithes-snmp-mib-files.zip.
Same file in n5860-and-n8560-series-swithes-snmp-mib-files.zip.
Downloaded: 2026-10-24T13:35:06.618037+00:00.
Module: FS-WLAN-QOS-EXTRA-MIB
fsPrivMappingAPstatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF FSAPdefaultStatusMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" when use CAPWAP, we must map pkt belong to certain WMM-AC to a Certian DSCP priv/802.1p pri
and as we must encap the pkt ,we must support two kind of mappings - trunnel and inner,
you can get the concept in RFC 5416
"
::= { fsWlanDevicePrivMappingAPDefaultObjects 1 }{'FS-SMI': ['fsMgmt'], 'SNMPv2-TC': ['TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'FS-AC-MGMT-MIB': ['fsApCfgRadioId', 'fsApgWlanId', 'fsStaMacAddr', 'fsApMacAddr']}Related source files and packages:
Same file in s3100-16tf-switch-snmp-mib-files.zip.
Same file in s5860-series-swithes-snmp-mib-files.zip.
Same file in s3910-series-swithes-snmp-mib-files.zip.
Downloaded: 2026-10-24T13:35:09.362002+00:00.
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.52642.1.1.10.2.60.3.2.1.1 | fsAPdefaultStatusMappingEntry | 2 | 2 |
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.52642.1.1.10.2.60.3.2.2 | fsPrivMappingAPDefaultTable | 1 | 3 |