Reference record for OID 1.3.6.1.4.1.9.9.792

Parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
Node code
792
Node name
ciscoLwappDhcpMIB
Numeric OID
1.3.6.1.4.1.9.9.792
URN notation
urn:oid:1.3.6.1.4.1.9.9.792
ASN.1 notation

{1 3 6 1 4 1 9 9 792}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappDhcpMIB(792)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappDhcpMIB(792)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappDhcpMIB(792)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappDhcpMIB(792)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappDhcpMIB(792)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappDhcpMIB(792)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappDhcpMIB(792)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappDhcpMIB(792)}
  • ...skipped...
OID-IRI notation
  • /1/3/6/1/4/1/9/9/792
  • /ISO/Identified-Organization/6/1/4/1/9/9/792
  • /ISO/3/6/1/4/1/9/9/792
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappDhcpMIB
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappDhcpMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoLwappDhcpMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoLwappDhcpMIB
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappDhcpMIB
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappDhcpMIB
  • /iso/org/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoLwappDhcpMIB
  • /iso/org/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoLwappDhcpMIB
  • ...skipped...
All recorded component names

Each component can use any of its recorded names. The examples above show up to eight combinations. ASN.1 names do not necessarily have registered OID-IRI labels.

  • 1: iso
  • 1.3: identified-organization, org, iso-identified-organization, iso-organization
  • 1.3.6: dod
  • 1.3.6.1: internet
  • 1.3.6.1.4: private
  • 1.3.6.1.4.1: enterprise, enterprises, ldap-enterprise, vendor-objects
  • 1.3.6.1.4.1.9: cisco
  • 1.3.6.1.4.1.9.9: ciscoMgmt
  • 1.3.6.1.4.1.9.9.792: ciscoLwappDhcpMIB

Source records

This MIB is used to manage Dynamic Host Configuration Protocol (DHCP) related information on the devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + MN + + MN + + MN + + MN + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ The LWAPP tunnel exists between the controller and the APs. The MNs communicate with the APs through the protocol defined by the 802.11 standard. LWAPP APs, upon bootup, discover and join one of the controllers and the controller pushes the configuration, that includes the WLAN parameters, to the LWAPP APs. The APs then encapsulate all the 802.11 frames from wireless clients inside LWAPP frames and forward the LWAPP frames to the controller. GLOSSARY Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides access to the distribution services via the wireless medium for associated clients. LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and sends them to the controller to which it is logically connected. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communication between the Access Points and the Central Controller. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Mobile Node, Mobile Station(MS) and client are used interchangeably. REFERENCE [1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol

Status in source: unspecified.

Names: ciscoLwappDhcpMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "ciscoLwappDhcpMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313730343237303030305a22"
    ],
    "ORGANIZATION",
    "\"Cisco Systems Inc.\"",
    "CONTACT-INFO",
    "\"Cisco Systems, Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS Email: cs-wnbu-snmp@cisco.com\"",
    "DESCRIPTION",
    "\"This MIB is used to manage Dynamic Host Configuration Protocol (DHCP) related information on the devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + MN + + MN + + MN + + MN + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ The LWAPP tunnel exists between the controller and the APs. The MNs communicate with the APs through the protocol defined by the 802.11 standard. LWAPP APs, upon bootup, discover and join one of the controllers and the controller pushes the configuration, that includes the WLAN parameters, to the LWAPP APs. The APs then encapsulate all the 802.11 frames from wireless clients inside LWAPP frames and forward the LWAPP frames to the controller. GLOSSARY Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides access to the distribution services via the wireless medium for associated clients. LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and sends them to the controller to which it is logically connected. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communication between the Access Points and the Central Controller. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Mobile Node, Mobile Station(MS) and client are used interchangeably. REFERENCE [1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol\"",
    "REVISION",
    [
      "literal",
      "223230313730343237303030305a22"
    ],
    "DESCRIPTION",
    "\"Updated the description of various objects.\"",
    "REVISION",
    [
      "literal",
      "223230313230313331303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of this MIB module.\"",
    "::=",
    "{",
    "ciscoMgmt",
    "792",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201704270000Z"
    ],
    [
      "ORGANIZATION",
      "Cisco Systems Inc."
    ],
    [
      "CONTACT-INFO",
      "Cisco Systems, Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS Email: cs-wnbu-snmp@cisco.com"
    ],
    [
      "DESCRIPTION",
      "This MIB is used to manage Dynamic Host Configuration Protocol (DHCP) related information on the devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + MN + + MN + + MN + + MN + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ The LWAPP tunnel exists between the controller and the APs. The MNs communicate with the APs through the protocol defined by the 802.11 standard. LWAPP APs, upon bootup, discover and join one of the controllers and the controller pushes the configuration, that includes the WLAN parameters, to the LWAPP APs. The APs then encapsulate all the 802.11 frames from wireless clients inside LWAPP frames and forward the LWAPP frames to the controller. GLOSSARY Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides access to the distribution services via the wireless medium for associated clients. LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and sends them to the controller to which it is logically connected. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communication between the Access Points and the Central Controller. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Mobile Node, Mobile Station(MS) and client are used interchangeably. REFERENCE [1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol"
    ],
    [
      "Revisions",
      [
        [
          "201704270000Z",
          [
            "DESCRIPTION",
            "Updated the description of various objects."
          ]
        ],
        [
          "201201310000Z",
          [
            "DESCRIPTION",
            "Initial version of this MIB module."
          ]
        ]
      ]
    ]
  ]
}
  • Cisco · Publisher's source file · Archived source file
    Source location: CISCO-LWAPP-DHCP-MIB::ciscoLwappDhcpMIB.
    Source version and references

    Downloaded: 2026-10-19T00:18:11.670911+00:00. SHA-256: e7d4ea10b421f696dee7f91ab17163956d76e63b28b16ac17e22793a257ba7b3

    {'kind': 'MODULE-IDENTITY', 'details': {'module': 'CISCO-LWAPP-DHCP-MIB', 'imports': {'CISCO-TC': ['CiscoURLString'], 'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TruthValue', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'IpAddress', 'Unsigned32', 'Counter32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}, 'smi_kind': 'MODULE-IDENTITY', 'definition': 'ciscoLwappDhcpMIB MODULE-IDENTITY\n    LAST-UPDATED    "201704270000Z"\n    ORGANIZATION    "Cisco Systems Inc."\n    CONTACT-INFO\n            "Cisco Systems,\n             Customer Service\n             Postal: 170 West Tasman Drive\n             San Jose, CA  95134\n             USA\n             Tel: +1 800 553-NETS\n\n             Email: cs-wnbu-snmp@cisco.com"\n    DESCRIPTION\n        "This MIB is used to manage Dynamic Host Configuration\n         Protocol (DHCP) related information on the devices \n         operating as Central controllers, that terminate the \n         Light Weight Access Point Protocol tunnel from Cisco \n         Light-weight LWAPP Access Points.\n\n         The relationship between CC and the LWAPP APs\n         can be depicted as follows:\n \n         +......+     +......+     +......+           +......+\n         +      +     +      +     +      +           +      +\n         +  CC  +     +  CC  +     +  CC  +           +  CC  +\n         +      +     +      +     +      +           +      +\n         +......+     +......+     +......+           +......+\n         ..            .             .                 .\n         ..            .             .                 .\n         .  .            .             .                 .\n         .    .            .             .                 .\n         .      .            .             .                 .\n         .        .            .             .                 .\n         +......+ +......+     +......+      +......+          +......+\n         +      + +      +     +      +      +      +          +      +\n         +  AP  + +  AP  +     +  AP  +      +  AP  +          +  AP  +\n         +      + +      +     +      +      +      +          +      +\n         +......+ +......+     +......+      +......+          +......+\n         .              .             .                 .\n         .  .              .             .                 .\n         .    .              .             .                 .\n         .      .              .             .                 .\n         .        .              .             .                 .\n         +......+ +......+     +......+      +......+          +......+\n         +      + +      +     +      +      +      +          +      +\n         +  MN  + +  MN  +     +  MN  +      +  MN  +          +  MN  +\n         +      + +      +     +      +      +      +          +      +\n         +......+ +......+     +......+      +......+          +......+\n\n \n         The LWAPP tunnel exists between the controller and\n         the APs.  The MNs communicate with the APs through\n         the protocol defined by the 802.11 standard.\n\n         LWAPP APs, upon bootup, discover and join one of the\n         controllers and the controller pushes the configuration,\n         that includes the WLAN parameters, to the LWAPP APs.\n         The APs then encapsulate all the 802.11 frames from\n         wireless clients inside LWAPP frames and forward\n         the LWAPP frames to the controller.\n\n                            GLOSSARY\n\n         Access Point ( AP )\n\n         An entity that contains an 802.11 medium access\n         control ( MAC ) and physical layer ( PHY ) interface\n         and provides access to the distribution services via\n         the wireless medium for associated clients.  \n\n         LWAPP APs encapsulate all the 802.11 frames in\n         LWAPP frames and sends them to the controller to which\n         it is logically connected.\n\n         Central Controller ( CC )\n\n         The central entity that terminates the LWAPP protocol\n         tunnel from the LWAPP APs.  Throughout this MIB,\n         this entity also referred to as \'controller\'. \n\n         Light Weight Access Point Protocol ( LWAPP ) \n\n         This is a generic protocol that defines the \n         communication between the Access Points and the\n         Central Controller.\n\n         Mobile Node ( MN )\n\n         A roaming 802.11 wireless device in a wireless\n         network associated with an access point. Mobile Node,\n         Mobile Station(MS) and client are used interchangeably. \n\n         REFERENCE\n\n         [1] Wireless LAN Medium Access Control ( MAC ) and\n         Physical Layer ( PHY ) Specifications.\n\n         [2] Draft-obara-capwap-lwapp-00.txt, IETF Light \n         Weight Access Point Protocol"\n    REVISION        "201704270000Z"\n    DESCRIPTION\n            "Updated the description of various objects."\n    REVISION        "201201310000Z"\n    DESCRIPTION\n            "Initial version of this MIB module."\n    ::= { ciscoMgmt 792 }', 'syntax_tree': [['LAST-UPDATED', '201704270000Z'], ['ORGANIZATION', 'Cisco Systems Inc.'], ['CONTACT-INFO', 'Cisco Systems, Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS Email: cs-wnbu-snmp@cisco.com'], ['DESCRIPTION', "This MIB is used to manage Dynamic Host Configuration Protocol (DHCP) related information on the devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + MN + + MN + + MN + + MN + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ The LWAPP tunnel exists between the controller and the APs. The MNs communicate with the APs through the protocol defined by the 802.11 standard. LWAPP APs, upon bootup, discover and join one of the controllers and the controller pushes the configuration, that includes the WLAN parameters, to the LWAPP APs. The APs then encapsulate all the 802.11 frames from wireless clients inside LWAPP frames and forward the LWAPP frames to the controller. GLOSSARY Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides access to the distribution services via the wireless medium for associated clients. LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and sends them to the controller to which it is logically connected. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communication between the Access Points and the Central Controller. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Mobile Node, Mobile Station(MS) and client are used interchangeably. REFERENCE [1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol"], ['Revisions', [['201704270000Z', ['DESCRIPTION', 'Updated the description of various objects.']], ['201201310000Z', ['DESCRIPTION', 'Initial version of this MIB module.']]]]], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4'}

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Direct children (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.792.0 ciscoLwappDhcpMIBNotif11
1.3.6.1.4.1.9.9.792.1 ciscoLwappDhcpMIBObjects546
1.3.6.1.4.1.9.9.792.2 ciscoLwappDhcpMIBConform24

Siblings (692)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.314 ciscoCasIfExtMIB3225 The MIB module is an extension of CISCO-CAS-IF-MIB.
It defines the attributes of a voice interface.
1.3.6.1.4.1.9.9.315 ciscoPortSecurityMIB389 The MIB module for managing Cisco Port Security.
1.3.6.1.4.1.9.9.317 ciscoIscsiGwMIB3145 MIB module for monitoring and configuring iSCSI
gateway functions. An iSCSI gateway represents FC
(Fibre Channel) targets/initiat…
1.3.6.1.4.1.9.9.318 ciscoXgcpMIB3120 This MIB is an enhancement for existing XGCP-MIB.

xGCP is a set of protocols, for example SGCP (Simple
Gateway Control Protocol) …
1.3.6.1.4.1.9.9.319 ciscoPropAtmIfMIB357 This MIB is designed for Propietary ATM (propAtm)
interfaces.
The propAtm interfaces are identified in the ifTable
entries with if…
1.3.6.1.4.1.9.9.321 ciscoMgcMIB343 This MIB is used to support MGC(call agent) and
MGC Group configuration.
The MGC or MGC group configuration is performed
under a s…
1.3.6.1.4.1.9.9.322 ccacSysMIB260 This MIB module provides provisioning and
monitoring Call Admission Control (CAC).
1.3.6.1.4.1.9.9.323 ciscoVoiceAalxProfileMIB387 This MIB defines the objects specific to voice
over ATM or voice over IP. Those objects are
related to the following areas:
1. COD…
1.3.6.1.4.1.9.9.324 ciscoMediaGatewayMIB3107 The MIB module for managing Trunk Media Gateway.

A Media Gateway is a network element that provides conversion
between the audio …
1.3.6.1.4.1.9.9.325 ciscoXgcpExtMIB265 This MIB module is an extension to CISCO-XGCP-MIB.

It defines the parameters related to the following
aspects in xGCP protocols:
*…
1.3.6.1.4.1.9.9.326 ciscoIpLocalPoolMIB357 This MIB defines the configuration and monitoring capabilities
relating to local IP pools.

Local IP pools have the following char…
1.3.6.1.4.1.9.9.329 ciscoFcipMgmtExtMIB375 A MIB module for extending the CISCO-FCIP-MGMT-MIB
to add objects which provide additional information
about FCIP interfaces not …
1.3.6.1.4.1.9.9.330 ciscoSysInfoLogMIB344 This MIB provides the configuration of System Information
Logging feature, which allows a certain number of commands
to be execut…
1.3.6.1.4.1.9.9.331 ciscoCsgMIB386 This MIB supports the Cisco Content Services Gateway
(CSG) product. It includes five traps and four tables
that enable querying C…
1.3.6.1.4.1.9.9.332 ciscoGsp2MIB391 The MIB for providing information specified
in ITU Q752 Monitoring and Measurements for
signalling System No. 7(SS7) Network.
This…
1.3.6.1.4.1.9.9.333 ciscoGactMIB340 The MIB for providing information specified
in ITU Q752 Monitoring and Measurements for
Signalling System No. 7(SS7) Network.
This…
1.3.6.1.4.1.9.9.334 ciscoGrtMIB3150 This MIB is for managing information required to
route messages transported over Signalling System
No. 7 (SS7) Network via Cisco …
1.3.6.1.4.1.9.9.335 ciscoGsccpMIB3293 The MIB for signalling Connection Control Part(SCCP)
messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP…
1.3.6.1.4.1.9.9.336 ciscoGspMIB3273 The MIB for managing Signalling Points and its
associated messages transported over Signalling
System No. 7 (SS7) Network via Ci…
1.3.6.1.4.1.9.9.339 ciscoSecureShellMIB240 MIB module for displaying and configuring
accounting and Secure Shell (SSH) related
features in a device.

SSH is a program to log …
1.3.6.1.4.1.9.9.340 ciscoLreCpeMIB321 The MIB module for the Cisco Long Reach Ethernet
Customer Premise Equipment device information.

*** ABBREVIATIONS, ACRONYMS, AND …
1.3.6.1.4.1.9.9.341 ciscoCableQosMonitorMIB357 This is the MIB module for subscriber QoS monitoring
for DOCSIS-compliant Cable Modem Termination Systems
(CMTS).

Several subscrib…
1.3.6.1.4.1.9.9.343 ciscoAuthorizationStatsMibModule225 The Cisco User Authorization Statistics MIB models
counters and objects that are of management
interest.
1.3.6.1.4.1.9.9.344 ciscoEntityDisplayMIB221 This MIB module provides information about the
status of display devices such as Light Emitting
Diodes (LEDs) and alphanumeric di…
1.3.6.1.4.1.9.9.350 ciscoEntityDiagMIB3139 This MIB module defines the managed objects that describe the
online diagnostics capabilities supported by the
physical entities …
1.3.6.1.4.1.9.9.351 ciscoAtmTrunkMIB3102 The MIB for voice and Nx64 over ATM Trunking applications.

The following lists the abbreviations used in this MIB:
AAL ATM …
1.3.6.1.4.1.9.9.356 ciscoVoiceToneCadenceMIB330 The MIB defines the attributes of the programmable
tones specified in ITU-T E.180 Supplement 2.

Each country has its own regulati…
1.3.6.1.4.1.9.9.358 ciscoBbsmMIB320 This mib is designed to send BBSM specific
notifications. There are variables that contain detail data
that are bind to a notifi…
1.3.6.1.4.1.9.9.359 ciscoLicenseMIB352 This MIB module provides objects to view the features
and services that are licensed to run on a system (usually
a network entity…
1.3.6.1.4.1.9.9.360 ciscoImageUpgradeMIB3101 This mib provides, objects to upgrade images on modules in the
system, objects showing the status of the upgrade operation,
and o…
1.3.6.1.4.1.9.9.361 ciscoCommonRolesMIB340 MIB module for managing the common roles between
access methods like Command Line Interface (CLI), SNMP
and XML interfaces.
Every …
1.3.6.1.4.1.9.9.362 ciscoPortStormControlMIB343 The MIB module for managing Cisco Port Storm Control.
1.3.6.1.4.1.9.9.363 ciscoFcSpanMIB249 MIB module for displaying and configuring
Switched Port Analyzer(SPAN) related features
in a Fibre Channel device.

SPAN is a featu…
1.3.6.1.4.1.9.9.364 ciscoPsmMIB3213 The MIB module for the management of the
Port Security Manager (PSM). The PSM
consists of 2 aspects: Port binding and
Fabric bindi…
1.3.6.1.4.1.9.9.365 ciscoFCCMIB342 The MIB module for the management of Fibre Channel
Congestion Control(FCC). FCC is a Cisco proprietary
flow control mechanism tha…
1.3.6.1.4.1.9.9.367 ciscoAAAServerExtMIB277 This MIB is an extension to the CISCO-AAA-SERVER-MIB.
This MIB module enhances the 'casConfigTable' to
include other types of Ser…
1.3.6.1.4.1.9.9.368 36800 Cisco Content Services (CSS) switch product, also known as Arrowpoint, for version 7.40 and later
1.3.6.1.4.1.9.9.369 ciscoLicenseMgrMIB3102 The MIB module for a method of managing license files on
the system.
Licensing mechanism provides more flexibility in supporting
v…
1.3.6.1.4.1.9.9.370 ciscoSslProxyMIB3372 This MIB module is for managing a Secure Socket Layer
(SSL) Proxy device which terminates and accelarates
SSL and Transport Layer…
1.3.6.1.4.1.9.9.371 ciscoIvrMIB3192 The MIB module for the management of Inter-VSAN
routing within the framework of Cisco's
Inter-VSAN Routing (IVR) Architecture. IV…
1.3.6.1.4.1.9.9.372 ciscoIsnsClientMIB316 MIB module for monitoring and configuring Internet
Storage Name Service (iSNS) client.
1.3.6.1.4.1.9.9.373 ciscoFdmiMIB347 Fabric Device Management Interface (FDMI) MIB. This MIB
module defines objects for managing the devices such as
HBA (Host Bus Ada…
1.3.6.1.4.1.9.9.374 ciscoDynamicArpInspectionMIB382 The MIB module is for configuration of Dynamic ARP Inspection
feature. Dynamic ARP Inspection is a security mechanism which
valid…
1.3.6.1.4.1.9.9.375 ciscoFiconMIB3176 This is the FICON (FIber CONnection) MIB module.

FICON is an IBM standard of transport mechanism
for communication between the ma…
1.3.6.1.4.1.9.9.376 ciscoSVIAutostateMIB319 The MIB module is for configuration of the switch virtual
interface (SVI) autostate feature. Autostate feature
is a mechanism to …
1.3.6.1.4.1.9.9.377 ciscoFeatureCtrlMIB353 There are two types of features in the system:

- Regular features
- Optional features

The Regular features may or may not need t…
1.3.6.1.4.1.9.9.378 ciscoSvcInterfaceMIB3115 MIB module for displaying and configuring
SVC (SAN Volume Controller) related features
in the Storage Area Network (SAN) switches…
1.3.6.1.4.1.9.9.379 ciscoItpmMIB347 The MIB for providing information related to
monitoring SS7 links.

This information can be used to manage the state
of software u…
1.3.6.1.4.1.9.9.380 ciscoDhcpSnoopingMIB3127 The MIB module is for configuration of DHCP Snooping
feature. DHCP Snooping is a security mechanism which
uses information gleane…
1.3.6.1.4.1.9.9.381 ciscoDiffServExtMIB249 This MIB is a Cisco extension to the
DIFFSERV-MIB, RFC 3289. This MIB defines
a Fibre Channel (FC) Multi Field filter to
be used i…