CISCO-APPNAV-MIB

        This MIB module defines SNMP management objects describing the
AppNav technology. A device, which implements the AppNav
technology, is known as the AppNav controller. The AppNav
controller intelligently navigates application traffic to a
group of devices, which offer services to the application
traffic. A device, which offers services to the application
traffic is known as service node.  
        
As an example, the WAN optimization service uses the AppNav
technology, where the AppNav controller intercepts applications
traffic and redirects it to service nodes, which offer the
WAN optimization service.
        
A deployment may use more than one AppNav controllers and
service nodes to provide high availability and scalability. In
such deployments, AppNav controllers and service nodes together
form a cluster, which is known as an AppNav cluster.
        
Definitions of various entities related to the AppNav technology
is as follows:
        
AppNav controller: It is a device that intercepts application
traffic and navigates (redirects) it to service nodes.
        
Service node: It is a device that offers services to the traffic
navigated (redirected) to it by the AppNav controller.
        
AppNav controller group: An AppNav controller group is a group
of one or more AppNav controllers. The AppNav controllers in the
AppNav controller group communicate with each other regarding
the connections being redirected by them, so that they redirect
traffic to the right service node, irrespective of which AppNav
controller receives packets for a given connection. For example,
if particular connection is served by the service node A then
that connection should always be served by the service node A
until client or server terminates it. This mechanism is needed
in the asymmetric network topologies, where packets may take
different paths for forward and return journey.
        
Service node group: A service node group is a group of one or
more service nodes. The AppNav controller intercepts and
redirects application traffic to service nodes in a service node
group. The service nodes update their load status to the AppNav 
controllers, so that they can do intelligent load distribution
among the available service nodes.
        
AppNav Cluster: An AppNav controller group and a service node
group together form a cluster, which is known as an AppNav
cluster. An AppNav cluster is also known as a service context.
    
Source file
CISCO-APPNAV-MIB
Last revised
Identity
ciscoAppNavMIB
Base OID
1.3.6.1.4.1.9.9.791
Imported Objects
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddress InetAddressType
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC TEXTUAL-CONVENTION (no object page)
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-APPNAV-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-APPNAV-MIB::ciscoAppNavMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-APPNAV-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-APPNAV-MIB::ciscoAppNavMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (44)
.1.3.6.1.4.1.9.9.791
.1.3.6.1.4.1.9.9.791.0
.1.3.6.1.4.1.9.9.791.0.1
.1.3.6.1.4.1.9.9.791.0.1.1
.1.3.6.1.4.1.9.9.791.0.1.1.1
Unsigned32
.1.3.6.1.4.1.9.9.791.0.1.1.1.1
OctetString
.1.3.6.1.4.1.9.9.791.0.1.1.1.2
.1.3.6.1.4.1.9.9.791.0.1.1.1.3
.1.3.6.1.4.1.9.9.791.0.1.1.1.4
.1.3.6.1.4.1.9.9.791.0.1.1.1.5
.1.3.6.1.4.1.9.9.791.0.1.1.1.6
.1.3.6.1.4.1.9.9.791.0.2
.1.3.6.1.4.1.9.9.791.0.2.1
.1.3.6.1.4.1.9.9.791.0.2.1.1
Unsigned32
.1.3.6.1.4.1.9.9.791.0.2.1.1.1
OctetString
.1.3.6.1.4.1.9.9.791.0.2.1.1.2
OctetString
.1.3.6.1.4.1.9.9.791.0.2.1.1.3
.1.3.6.1.4.1.9.9.791.0.3
.1.3.6.1.4.1.9.9.791.0.3.1
.1.3.6.1.4.1.9.9.791.0.3.1.1
Unsigned32
.1.3.6.1.4.1.9.9.791.0.3.1.1.1
OctetString
.1.3.6.1.4.1.9.9.791.0.3.1.1.2
OctetString
.1.3.6.1.4.1.9.9.791.0.3.1.1.3
.1.3.6.1.4.1.9.9.791.0.4
.1.3.6.1.4.1.9.9.791.0.4.1
.1.3.6.1.4.1.9.9.791.0.4.1.1
Unsigned32
.1.3.6.1.4.1.9.9.791.0.4.1.1.1
.1.3.6.1.4.1.9.9.791.0.4.1.1.2
.1.3.6.1.4.1.9.9.791.0.4.1.1.3
OctetString
.1.3.6.1.4.1.9.9.791.0.4.1.1.4
OctetString
.1.3.6.1.4.1.9.9.791.0.4.1.1.5
.1.3.6.1.4.1.9.9.791.0.4.1.1.6
.1.3.6.1.4.1.9.9.791.0.5
.1.3.6.1.4.1.9.9.791.0.5.1
.1.3.6.1.4.1.9.9.791.0.5.1.1
Unsigned32
.1.3.6.1.4.1.9.9.791.0.5.1.1.1
.1.3.6.1.4.1.9.9.791.0.5.1.1.2
.1.3.6.1.4.1.9.9.791.0.5.1.1.3
OctetString
.1.3.6.1.4.1.9.9.791.0.5.1.1.4
OctetString
.1.3.6.1.4.1.9.9.791.0.5.1.1.5
.1.3.6.1.4.1.9.9.791.0.5.1.1.6
.1.3.6.1.4.1.9.9.791.1
.1.3.6.1.4.1.9.9.791.1.1
.1.3.6.1.4.1.9.9.791.1.2
Dependencies (5) 5 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. INET-ADDRESS-MIBrfc
  5. SNMPv2-CONFrfc
  6. CISCO-APPNAV-MIBciscoselected
Type Definitions (4)
Enumeration
dead(1)
alive(2)
excluded(3)
partial(4)
na(5)
zombie(6)
inactive(7)
Enumeration
ready(1)
notReady(2)
na(3)
Enumeration
unknown(1)
notConfigured(2)
started(3)
aborted(4)
completed(5)
Enumeration
initializing(1)
converging(2)
internalError(3)
degraded(4)
operational(5)
adminDisabled(6)
initializingJoining(7)
convergingJoining(8)
operationalJoining(9)
degradedJoining(10)
Conformance Groups (6)
This group includes objects which gives information for service
context configured on the AppNav controller.
.1.3.6.1.4.1.9.9.791.1.2.1
This group includes objects, which give information related to
AppNav controller group configured on the AppNav controller.
.1.3.6.1.4.1.9.9.791.1.2.2
This group includes objects, which gives information related to
the service node group configured on the AppNav controller.
.1.3.6.1.4.1.9.9.791.1.2.3
This group includes objects, which gives information related to
AppNav controllers configured on the AppNav controller to
assign them to the AppNav cluster.
.1.3.6.1.4.1.9.9.791.1.2.4
This group contains objects, which gives information related to
service node configured on AppNav controller to assign them to
the AppNav cluster.
.1.3.6.1.4.1.9.9.791.1.2.5
This group includes objects which gives information for
service
context configured on the AppNav controller.
.1.3.6.1.4.1.9.9.791.1.2.6
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.791.1.1.1
This is a default module-compliance
containing default object groups.
Required groups

OID .1.3.6.1.4.1.9.9.791.1.1.2
This is a default module-compliance
containing default object groups. This compliance deprecated
ciscoAppNavMIBCompliance.
Required groups