Reference record for OID 1.3.6.1.4.1.9.9.847

Parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
Node code
847
Node name
ciscoLwappIpv6MIB
Numeric OID
1.3.6.1.4.1.9.9.847
URN notation
urn:oid:1.3.6.1.4.1.9.9.847
ASN.1 notation

{1 3 6 1 4 1 9 9 847}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappIpv6MIB(847)}
OID-IRI notation
  • /1/3/6/1/4/1/9/9/847
  • /ISO/Identified-Organization/6/1/4/1/9/9/847
  • /ISO/3/6/1/4/1/9/9/847
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/org/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/org/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/iso-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/iso-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoLwappIpv6MIB
  • /iso/iso-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoLwappIpv6MIB

Source records

This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about the ACLs on the controller. Particularly this mib covers the CPU ACLs for the wireless controllers. Traffic to the controller CPU comes from the NPU (Network Processing Unit). Using CPU ACLs, the user can place restrictions on type of traffic reaching the CPU of the controller from the NPU. CPU ACLs introduce an ACL for the traffic to the CPU of controller. With this ACL the type of packets reaching the CPU can be controlled. The mode of operation is as follows. The administrator designates one ACL for the traffic to the CPU. The ACL kicks in for packets from the NPU to the CPU. Each ACL is an ordered set of rules. If a rule matches then action for that rule is applied to the packet. The decision to send or drop the packet is taken based on the action parameter of the ACL. There will be no ACL for the packets from the CPU to the NPU. GLOSSARY Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU. Each ACL is an ordered set of rules and actions. If a rule matches then the action for that rule is applied to the packet. Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides acess to the distribution services via the wireless medium for associated clients. CPU ACL ( CPU ACL ) The ACL applied to the CPU. This controls the type of traffic reaching the CPU of the controller. Network Processing Unit ( NPU ) This entity is responsible for forwarding traffic to the CPU. The only exceptions are data coming thorugh the console port and the Service port i.e. these communicate directly with the CPU and not via the NPU. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communciation between the Access Points and the Central Controller. Cryptographically Generated Addresses (CGA) Cryptographically Generated Addresses (CGAs) are IPv6 addresses, which allow for a secure association of an IPv6 address, the CGA, with a public key. Internet Protocol Version 6(IPV6) An IPv6 address is a numerical label that is used to identify a network interface of a computer or other network node participating in an IPv6 computer network. An IP address serves the purpose of uniquely identifying an individual network interface of a host, locating it on the network, and thus permitting the routing of IP packets between hosts. For routing, IP addresses are present in fields of the packet header where they indicate source and destination of the packet. IPv6 is the successor to the first addressing infrastructure of the Internet, Internet Protocol version 4 (IPv4). In contrast to IPv4, which defined an IP address as a 32-bit value, IPv6 addresses have a size of 128 bits. Therefore, IPv6 has a vastly enlarged address space compared to IPv4. Neighbor Discovery Protocol (NDP) The NDP is a protocol in the Internet protocol suite used with IPv6. It operates in the Link Layer of the Internet model, and is responsible for address autoconfiguration of nodes, discovery of other nodes on the link, determining the addresses of other nodes, duplicate address detection, finding available routers and Domain Name System (DNS) servers, address prefix discovery, and maintaining reachability information of other active neighbor nodes. NDP defines five ICMPv6 packet types for the purpose of router solicitation, router advertisement, neighbor solicitation, neighbor advertisement, and network redirects. Router Solicitation(RS) Hosts inquire with Router Solicitation messages to locate routers on an attached link. Routers which forward packets not addressed to them generate Router Advertisements immediately upon receipt of this message rather than at their next scheduled time. Router Advertisement(RA) Routers advertise their presence together with various link and Internet parameters either periodically, or in response to a Router Solicitation message. Neighbor Solicitation (NS) Neighbor solicitations are used by nodes to determine the link layer address of a neighbor, or to verify that a neighbor is still reachable via a cached link layer address. Neighbor Advertisement(NA) Neighbor advertisements are used by nodes to respond to a Neighbor Solicitation message. Redirect Routers may inform hosts of a better first hop router for a destination. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications.

Status in source: unspecified.

Names: ciscoLwappIpv6MIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "ciscoLwappIpv6MIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313730353233303030305a22"
    ],
    "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 intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about the ACLs on the controller. Particularly this mib covers the CPU ACLs for the wireless controllers. Traffic to the controller CPU comes from the NPU (Network Processing Unit). Using CPU ACLs, the user can place restrictions on type of traffic reaching the CPU of the controller from the NPU. CPU ACLs introduce an ACL for the traffic to the CPU of controller. With this ACL the type of packets reaching the CPU can be controlled. The mode of operation is as follows. The administrator designates one ACL for the traffic to the CPU. The ACL kicks in for packets from the NPU to the CPU. Each ACL is an ordered set of rules. If a rule matches then action for that rule is applied to the packet. The decision to send or drop the packet is taken based on the action parameter of the ACL. There will be no ACL for the packets from the CPU to the NPU. GLOSSARY Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU. Each ACL is an ordered set of rules and actions. If a rule matches then the action for that rule is applied to the packet. Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides acess to the distribution services via the wireless medium for associated clients. CPU ACL ( CPU ACL ) The ACL applied to the CPU. This controls the type of traffic reaching the CPU of the controller. Network Processing Unit ( NPU ) This entity is responsible for forwarding traffic to the CPU. The only exceptions are data coming thorugh the console port and the Service port i.e. these communicate directly with the CPU and not via the NPU. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communciation between the Access Points and the Central Controller. Cryptographically Generated Addresses (CGA) Cryptographically Generated Addresses (CGAs) are IPv6 addresses, which allow for a secure association of an IPv6 address, the CGA, with a public key. Internet Protocol Version 6(IPV6) An IPv6 address is a numerical label that is used to identify a network interface of a computer or other network node participating in an IPv6 computer network. An IP address serves the purpose of uniquely identifying an individual network interface of a host, locating it on the network, and thus permitting the routing of IP packets between hosts. For routing, IP addresses are present in fields of the packet header where they indicate source and destination of the packet. IPv6 is the successor to the first addressing infrastructure of the Internet, Internet Protocol version 4 (IPv4). In contrast to IPv4, which defined an IP address as a 32-bit value, IPv6 addresses have a size of 128 bits. Therefore, IPv6 has a vastly enlarged address space compared to IPv4. Neighbor Discovery Protocol (NDP) The NDP is a protocol in the Internet protocol suite used with IPv6. It operates in the Link Layer of the Internet model, and is responsible for address autoconfiguration of nodes, discovery of other nodes on the link, determining the addresses of other nodes, duplicate address detection, finding available routers and Domain Name System (DNS) servers, address prefix discovery, and maintaining reachability information of other active neighbor nodes. NDP defines five ICMPv6 packet types for the purpose of router solicitation, router advertisement, neighbor solicitation, neighbor advertisement, and network redirects. Router Solicitation(RS) Hosts inquire with Router Solicitation messages to locate routers on an attached link. Routers which forward packets not addressed to them generate Router Advertisements immediately upon receipt of this message rather than at their next scheduled time. Router Advertisement(RA) Routers advertise their presence together with various link and Internet parameters either periodically, or in response to a Router Solicitation message. Neighbor Solicitation (NS) Neighbor solicitations are used by nodes to determine the link layer address of a neighbor, or to verify that a neighbor is still reachable via a cached link layer address. Neighbor Advertisement(NA) Neighbor advertisements are used by nodes to respond to a Neighbor Solicitation message. Redirect Routers may inform hosts of a better first hop router for a destination. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications.\"",
    "REVISION",
    [
      "literal",
      "223230313730353233303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of this MIB module.\"",
    "::=",
    "{",
    "ciscoMgmt",
    "847",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201705230000Z"
    ],
    [
      "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 intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about the ACLs on the controller. Particularly this mib covers the CPU ACLs for the wireless controllers. Traffic to the controller CPU comes from the NPU (Network Processing Unit). Using CPU ACLs, the user can place restrictions on type of traffic reaching the CPU of the controller from the NPU. CPU ACLs introduce an ACL for the traffic to the CPU of controller. With this ACL the type of packets reaching the CPU can be controlled. The mode of operation is as follows. The administrator designates one ACL for the traffic to the CPU. The ACL kicks in for packets from the NPU to the CPU. Each ACL is an ordered set of rules. If a rule matches then action for that rule is applied to the packet. The decision to send or drop the packet is taken based on the action parameter of the ACL. There will be no ACL for the packets from the CPU to the NPU. GLOSSARY Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU. Each ACL is an ordered set of rules and actions. If a rule matches then the action for that rule is applied to the packet. Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides acess to the distribution services via the wireless medium for associated clients. CPU ACL ( CPU ACL ) The ACL applied to the CPU. This controls the type of traffic reaching the CPU of the controller. Network Processing Unit ( NPU ) This entity is responsible for forwarding traffic to the CPU. The only exceptions are data coming thorugh the console port and the Service port i.e. these communicate directly with the CPU and not via the NPU. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communciation between the Access Points and the Central Controller. Cryptographically Generated Addresses (CGA) Cryptographically Generated Addresses (CGAs) are IPv6 addresses, which allow for a secure association of an IPv6 address, the CGA, with a public key. Internet Protocol Version 6(IPV6) An IPv6 address is a numerical label that is used to identify a network interface of a computer or other network node participating in an IPv6 computer network. An IP address serves the purpose of uniquely identifying an individual network interface of a host, locating it on the network, and thus permitting the routing of IP packets between hosts. For routing, IP addresses are present in fields of the packet header where they indicate source and destination of the packet. IPv6 is the successor to the first addressing infrastructure of the Internet, Internet Protocol version 4 (IPv4). In contrast to IPv4, which defined an IP address as a 32-bit value, IPv6 addresses have a size of 128 bits. Therefore, IPv6 has a vastly enlarged address space compared to IPv4. Neighbor Discovery Protocol (NDP) The NDP is a protocol in the Internet protocol suite used with IPv6. It operates in the Link Layer of the Internet model, and is responsible for address autoconfiguration of nodes, discovery of other nodes on the link, determining the addresses of other nodes, duplicate address detection, finding available routers and Domain Name System (DNS) servers, address prefix discovery, and maintaining reachability information of other active neighbor nodes. NDP defines five ICMPv6 packet types for the purpose of router solicitation, router advertisement, neighbor solicitation, neighbor advertisement, and network redirects. Router Solicitation(RS) Hosts inquire with Router Solicitation messages to locate routers on an attached link. Routers which forward packets not addressed to them generate Router Advertisements immediately upon receipt of this message rather than at their next scheduled time. Router Advertisement(RA) Routers advertise their presence together with various link and Internet parameters either periodically, or in response to a Router Solicitation message. Neighbor Solicitation (NS) Neighbor solicitations are used by nodes to determine the link layer address of a neighbor, or to verify that a neighbor is still reachable via a cached link layer address. Neighbor Advertisement(NA) Neighbor advertisements are used by nodes to respond to a Neighbor Solicitation message. Redirect Routers may inform hosts of a better first hop router for a destination. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications."
    ],
    [
      "Revisions",
      [
        [
          "201705230000Z",
          [
            "DESCRIPTION",
            "Initial version of this MIB module."
          ]
        ]
      ]
    ]
  ]
}
  • Cisco · Publisher's source file · Archived source file
    Source location: CISCO-LWAPP-IPV6-MIB::ciscoLwappIpv6MIB.
    Source version and references

    Downloaded: 2026-10-19T00:18:11.686827+00:00. SHA-256: bb80a0f1329e47a19ed9214746fce55923c5eded63ed27770087640db3cbe5fc

    {'kind': 'MODULE-IDENTITY', 'details': {'module': 'CISCO-LWAPP-IPV6-MIB', 'imports': {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetPortNumber'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'CISCO-LWAPP-DOT11-CLIENT-MIB': ['cldcClientMacAddress']}, 'smi_kind': 'MODULE-IDENTITY', 'definition': 'ciscoLwappIpv6MIB MODULE-IDENTITY\n    LAST-UPDATED    "201705230000Z"\n    ORGANIZATION    "Cisco Systems Inc."\n    CONTACT-INFO\n            "Cisco Systems,\n            Customer Service\n\n            Postal: 170 West Tasman Drive\n            San Jose, CA  95134\n            USA\n\n            Tel: +1 800 553-NETS\n\n            Email: cs-wnbu-snmp@cisco.com"\n    DESCRIPTION\n        "This MIB is intended to be implemented on all those\n        devices operating as Central Controllers (CC) that\n        terminate the Light Weight Access Point Protocol\n        tunnel from Light-weight LWAPP Access Points.\n\n        This MIB provides configuration and status information\n        about the ACLs on the controller.\n\n        Particularly this mib covers the CPU ACLs for the wireless\n        controllers.\n\n        Traffic to the controller CPU comes from the NPU (Network\n        Processing Unit).\n\n        Using CPU ACLs, the user can place restrictions on type of\n        traffic reaching the CPU of the controller from the NPU.      \n\n\n\n        CPU ACLs introduce an ACL for the traffic to the CPU of\n        controller. With this ACL the type of packets reaching the\n        CPU can be controlled. The mode of operation is as follows.\n\n        The administrator designates one ACL for the traffic to the\n        CPU. The ACL kicks in for packets from the NPU to the CPU.\n        Each ACL is an ordered set of rules. If a rule matches then\n        action for that rule is applied to the packet. The decision\n        to send or drop the packet is taken based on the action\n        parameter of the ACL.\n\n        There will be no ACL for the packets from the CPU to the\n        NPU.\n\n\n\n                                GLOSSARY                              \n\n\n        Access Control List ( ACL )\n\n        A list of rules used to restrict the traffic reaching an\n        interface or the CPU.  Each ACL is an ordered set of rules\n        and actions.  If a rule matches then the action for that \n        rule is applied to the packet.\n\n\n\n        Access Point ( AP )\n\n        An entity that contains an 802.11 medium access control \n        ( MAC ) and physical layer ( PHY ) interface and provides\n        acess to the distribution services via the wireless medium\n        for associated clients.\n\n\n        CPU ACL ( CPU ACL )\n\n        The ACL applied to the CPU.  This controls the type of \n        traffic reaching the CPU of the controller.\n\n\n\n        Network Processing Unit ( NPU )\n\n        This entity is responsible for forwarding traffic to the\n        CPU. The only exceptions are data coming thorugh the \n        console port and the Service port i.e. these communicate\n        directly with the CPU and not via the NPU.\n\n\n        Light Weight Access Point Protocol ( LWAPP )\n\n        This is a generic protocol that defines the communciation\n        between the Access Points and the Central Controller.\n\n        Cryptographically Generated Addresses (CGA)\n\n        Cryptographically Generated Addresses (CGAs) are IPv6 \n        addresses, which allow for a secure association of an \n        IPv6 address, the CGA, with a public key.\n        \n        Internet Protocol Version 6(IPV6)\n\n        An IPv6 address is a numerical label that is used to \n        identify a network interface of a computer or other \n        network node participating in an IPv6 computer network.\n\n        An IP address serves the purpose of uniquely identifying \n        an individual network interface of a host, locating it on \n        the network, and thus permitting the routing of IP packets \n        between hosts. For routing, IP addresses are present in \n        fields of the packet header where they indicate source and \n        destination of the packet.\n\n        IPv6 is the successor to the first addressing infrastructure \n        of the Internet, Internet Protocol version 4 (IPv4). In \n        contrast to IPv4, which defined an IP address as a 32-bit \n        value, IPv6 addresses have a size of 128 bits. Therefore, \n        IPv6 has a vastly enlarged address space compared to IPv4.\n\n        Neighbor Discovery Protocol (NDP)\n\n        The NDP is a protocol in the Internet protocol suite used \n        with IPv6. It operates in the Link Layer of the Internet \n        model, and is responsible for address autoconfiguration \n        of nodes, discovery of other nodes on the link, determining \n        the addresses of other nodes, duplicate address detection, \n        finding available routers and Domain Name System (DNS) servers, \n        address prefix discovery, and maintaining reachability \n        information of other active neighbor nodes.\n\n        NDP defines five ICMPv6 packet types for the purpose of \n        router solicitation, router advertisement, neighbor \n        solicitation, neighbor advertisement, and network redirects.\n\n        Router Solicitation(RS)\n        Hosts inquire with Router Solicitation messages to \n        locate routers on an attached link. Routers which \n        forward packets not addressed to them generate Router \n        Advertisements immediately upon receipt of this message \n        rather than at their next scheduled time.\n\n        Router Advertisement(RA)\n        Routers advertise their presence together with various\n        link and Internet parameters either periodically, or \n        in response to a Router Solicitation message.\n\n        Neighbor Solicitation (NS)\n        Neighbor solicitations are used by nodes to determine \n        the link layer address of a neighbor, or to verify \n        that a neighbor is still reachable via a cached link \n        layer address.\n\n        Neighbor Advertisement(NA)\n        Neighbor advertisements are used by nodes to respond \n        to a Neighbor Solicitation message.\n\n        Redirect\n        Routers may inform hosts of a better first hop router \n        for a destination.\n\n        REFERENCE\n\n        [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and\n        Physical Layer ( PHY ) Specifications."\n\n    REVISION        "201705230000Z"\n    DESCRIPTION\n        "Initial version of this MIB module."\n    ::= { ciscoMgmt 847 }', 'syntax_tree': [['LAST-UPDATED', '201705230000Z'], ['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 intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about the ACLs on the controller. Particularly this mib covers the CPU ACLs for the wireless controllers. Traffic to the controller CPU comes from the NPU (Network Processing Unit). Using CPU ACLs, the user can place restrictions on type of traffic reaching the CPU of the controller from the NPU. CPU ACLs introduce an ACL for the traffic to the CPU of controller. With this ACL the type of packets reaching the CPU can be controlled. The mode of operation is as follows. The administrator designates one ACL for the traffic to the CPU. The ACL kicks in for packets from the NPU to the CPU. Each ACL is an ordered set of rules. If a rule matches then action for that rule is applied to the packet. The decision to send or drop the packet is taken based on the action parameter of the ACL. There will be no ACL for the packets from the CPU to the NPU. GLOSSARY Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU. Each ACL is an ordered set of rules and actions. If a rule matches then the action for that rule is applied to the packet. Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides acess to the distribution services via the wireless medium for associated clients. CPU ACL ( CPU ACL ) The ACL applied to the CPU. This controls the type of traffic reaching the CPU of the controller. Network Processing Unit ( NPU ) This entity is responsible for forwarding traffic to the CPU. The only exceptions are data coming thorugh the console port and the Service port i.e. these communicate directly with the CPU and not via the NPU. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communciation between the Access Points and the Central Controller. Cryptographically Generated Addresses (CGA) Cryptographically Generated Addresses (CGAs) are IPv6 addresses, which allow for a secure association of an IPv6 address, the CGA, with a public key. Internet Protocol Version 6(IPV6) An IPv6 address is a numerical label that is used to identify a network interface of a computer or other network node participating in an IPv6 computer network. An IP address serves the purpose of uniquely identifying an individual network interface of a host, locating it on the network, and thus permitting the routing of IP packets between hosts. For routing, IP addresses are present in fields of the packet header where they indicate source and destination of the packet. IPv6 is the successor to the first addressing infrastructure of the Internet, Internet Protocol version 4 (IPv4). In contrast to IPv4, which defined an IP address as a 32-bit value, IPv6 addresses have a size of 128 bits. Therefore, IPv6 has a vastly enlarged address space compared to IPv4. Neighbor Discovery Protocol (NDP) The NDP is a protocol in the Internet protocol suite used with IPv6. It operates in the Link Layer of the Internet model, and is responsible for address autoconfiguration of nodes, discovery of other nodes on the link, determining the addresses of other nodes, duplicate address detection, finding available routers and Domain Name System (DNS) servers, address prefix discovery, and maintaining reachability information of other active neighbor nodes. NDP defines five ICMPv6 packet types for the purpose of router solicitation, router advertisement, neighbor solicitation, neighbor advertisement, and network redirects. Router Solicitation(RS) Hosts inquire with Router Solicitation messages to locate routers on an attached link. Routers which forward packets not addressed to them generate Router Advertisements immediately upon receipt of this message rather than at their next scheduled time. Router Advertisement(RA) Routers advertise their presence together with various link and Internet parameters either periodically, or in response to a Router Solicitation message. Neighbor Solicitation (NS) Neighbor solicitations are used by nodes to determine the link layer address of a neighbor, or to verify that a neighbor is still reachable via a cached link layer address. Neighbor Advertisement(NA) Neighbor advertisements are used by nodes to respond to a Neighbor Solicitation message. Redirect Routers may inform hosts of a better first hop router for a destination. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications.'], ['Revisions', [['201705230000Z', ['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.847.0 ciscoLwappIpv6MIBNotifs00
1.3.6.1.4.1.9.9.847.1 ciscoLwappIpv6MIBObjects2100
1.3.6.1.4.1.9.9.847.2 ciscoLwappIpv6MIBConform25

Siblings (692)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.513 ciscoLwappApMIB51009 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.514 ciscoLwappTextualConventions00 This module defines textual conventions used
throughout the Cisco enterprise MIBs
designed for implementation on Central
Controlle…
1.3.6.1.4.1.9.9.515 ciscoLwappWebAuthMIB4133 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.516 ciscoLwappLinkTestMIB357 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.517 ciscoLwappReapMIB3342 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.518 ciscoLwappMfpMIB468 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.519 ciscoLwappIdsMIB328 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.520 ciscoLwappCcxRmMIB345 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.521 ciscoLwappWlanSecurityMIB377 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.522 ciscoLwappDot11ClientCalibMIB355 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.523 ciscoLwappClRoamMIB363 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.524 ciscoLwappQosMIB3322 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.525 ciscoLwappTsmMIB357 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.529 ciscoItpMsuRatesMIB361 This MIB provides information used to manage the number
of MTP3 MSUs transmitted and received per processor. Many
of the higher …
1.3.6.1.4.1.9.9.530 ciscoNacTcMIB00 This module defines the textual conventions for
Cisco Network Admission Control(NAC) system.

The Cisco Network Admission Control …
1.3.6.1.4.1.9.9.532 ciscoNATExtMIB313 This MIB is an extension to the NAT-MIB.
This MIB module includes objects for
providing the NAT related statistics.

Acronyms:

NAT…
1.3.6.1.4.1.9.9.533 ciscoCbpTargetMIB325 This MIB module defines the managed objects for
representing targets which have class-based policy
mappings. A target can be any…
1.3.6.1.4.1.9.9.543 ciscoLicenseMgmtMIB3131 The MIB module for managing licenses on the system.
The licensing mechanism provides flexibility to
enforce licensing for various…
1.3.6.1.4.1.9.9.548 ciscoErrDisableMIB345 This MIB module provides the ability for a Network
Management Station (NMS) to configure and monitor the
error-disable feature vi…
1.3.6.1.4.1.9.9.572 ciscoRttMonIPExtMIB257 This MIB contains extensions to tables in CISCO-RTTMON-MIB
to support IP-layer extensions, specifically IPv6 addresses
and other …
1.3.6.1.4.1.9.9.573 ciscoQosTcMIB00 This module defines the textual conventions used within
Cisco Qos MIBs.
1.3.6.1.4.1.9.9.576 ciscoLwappMobilityMIB3106 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that

terminate the Light Weight…
1.3.6.1.4.1.9.9.577 ciscoLwappAclMIB347 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.578 ciscoRoutePoliciesMIB35 This module provides a subtree to define OIDs so that
various routing 'policies' used by Cisco routers can be
expressed. This mod…
1.3.6.1.4.1.9.9.580 ciscoSwitchQosMIB3295 This MIB module extends the CISCO-CLASS-BASED-QOS-MIB
by defining configuration and statistics information
specific to the qualit…
1.3.6.1.4.1.9.9.583 ciscoGslbTcMIB00 This MIB module defines Textual Conventions and
OBJECT-IDENTITIES for use in documents defining
management information base (MIBs…
1.3.6.1.4.1.9.9.584 ciscoEntityDiagTcMIB00 This module defines the textual conventions used within
Cisco Entity Diag MIB.
1.3.6.1.4.1.9.9.585 ciscoIpSlaEthernetMIB3245 This MIB module consists of two parts.

1) Auto-Ethernet-CFM Control:
|
|

2) ethernetJitter Stats:
|
|

The first part defines a mechani…
1.3.6.1.4.1.9.9.586 ciscoNotificationControlMIB228 This MIB provides network management support to regulate
the transmission of notifications generated by a
system providing networ…
1.3.6.1.4.1.9.9.589 ciscoGslbSystemMIB3103 This MIB module defines objects for network and system
information of Global Server Load Balancer(GSLB) as a
network device. A G…
1.3.6.1.4.1.9.9.590 ciscoCvpMIB3255 The Cisco Unified Customer Voice Portal (CVP) application
integrates with both traditional time-division multiplexing
(TDM) and I…
1.3.6.1.4.1.9.9.592 ciscoPrefPathMIB356 The MIB module for the management of
preferred path. This MIB enables managers
to configure and monitor Preferred Path
parameters.
…
1.3.6.1.4.1.9.9.593 ciscoFcSdvMIB328 This MIB instrumentation is for managing Fibre
Channel (FC) SAN Device Virtualization (SDV)
solution on Cisco Fibre Channel devic…
1.3.6.1.4.1.9.9.594 ciscoApplicationAccelerationMIB337 This is a MIB for managing Application Acceleration System(s).
This MIB includes instrumentation for providing the
performance st…
1.3.6.1.4.1.9.9.595 ciscoGslbDnsMIB3165 The MIB defines objects for status and statistics
information of DNS related operations of
Global Server Load Balancer(GSLB). Th…
1.3.6.1.4.1.9.9.597 ciscoContentServicesMIB3349 Content Service is a capability to examine IP/TCP/UDP headers,
payload and enable billing based on the content being provided.

Ab…
1.3.6.1.4.1.9.9.598 ciscoLwappAAAMIB3150 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC), that
terminate the Light Weigh…
1.3.6.1.4.1.9.9.599 ciscoLwappDot11ClientMIB4439 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.600 ciscoGslbHealthMonMIB390 The MIB defines objects related to global keepalive
properties in GSLB devices. It contains the tables
for keep alive configurat…
1.3.6.1.4.1.9.9.601 ciscoResilientEthernetProtocolMIB377 This MIB module defines objects required for managing
Resilient Ethernet Protocol (REP).

Resilient Ethernet Protocol (REP) is a C…
1.3.6.1.4.1.9.9.602 ciscoPacketCaptureMIB3103 The MIB module for the management of packet capture
feature.
1.3.6.1.4.1.9.9.603 ciscoThreatMitigationServiceMIB368 This MIB provides management information about the Threat
Mitigation Service(TMS) entity named 'Consumer'. TMS is part
of Cisco's…
1.3.6.1.4.1.9.9.604 cdot1CfmMIB3166 Connectivity Fault Management module for managing IEEE 802.1ag
1.3.6.1.4.1.9.9.606 ciscoLwappMeshLinkTestMIB346 ciscoLwappMeshLinkTestMIB MODULE-IDENTITY
LAST-UPDATED "200702050000Z"
ORGANIZATION "Cisco Systems Inc."
CONTACT-INFO
"Cisco Sy…
1.3.6.1.4.1.9.9.607 ciscoDot11HtPhyMIB371 This MIB is intended to be implemented on Cisco's
WLAN devices that provide the wired uplink to wireless
clients through the high…
1.3.6.1.4.1.9.9.610 ciscoLwappRogueMIB4134 This MIB is intended to be implemented on all those
devices operating as Central Controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.611 ciscoLwappDot11ClientCCXTextualConventions00 This module defines the textual conventions used
throughout the Cisco enterprise MIBs designed for
implementation on Central Cont…
1.3.6.1.4.1.9.9.612 ciscoLwappDot11MIB3156 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.613 ciscoEvcMIB3156 Metro Ethernet services can support a wide range of
applications and subscriber needs easily, efficiently
and cost-effectively. …
1.3.6.1.4.1.9.9.614 ciscoLwappDot11LdapMIB333 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…