CISCO-AON-STATUS-MIB

This MIB module defines managed objects that facilitate the
        management of AON node.
        
        The information available through this MIB includes
        o AON node state i.e., whether the AON node is 'unregistered',
        'registered', 'active', 'inactive'.
        
        o Node metrics information when a node is in the 'active'
        state.
        
        o The node metrics information includes the number of messages
        received by the node, number of PEPs deployed and number of
        messages received by a PEP as well as information about the end
        points that the messages are delivered to.  The metrics are
        reset when the AON data plane is restarted.
        
        The following terms are used throughout this MIB:
        
        AON : Application Oriented Networking.
        
          _____________ 
          | AON        |
          | Management |
          | Console    |
          |____________|
                |
                |
                |
                | 
           ____ |____________________________
          |     |        AON Node           |
          |   __V_________      _________   |
          |   |           |     |        |  |
          |   | AON       |     | AON    |  |
          |   | Management|---->| Data   |  |
          |   | Agent     |     | Plane  |  |
          |   |___________      |________|  |
          |                                 |
          |_________________________________|
                 Figure 1 : AON
        
        AON data plane: This is the piece of software that runs on the
        AON node and is responsible for processing application message
        traffic.
        
        AMC : AON Management Console.  A Web-based application used to
        manage the AON installation, upgrade, and operation.  This is
        also referred to as the AON Management Plane.
        
        AMA : AON Management Agent.  An agent that runs on the AON node
        and acts as intermediary between the AON data plane and the
        AMC.
        
        AON Node : An AON node is either a single device (blade or
        appliance) or a virtual cluster of devices (blades or
        appliances) that are running the AON software.
        
        AON Cloud :  A group of AON nodes that are connected together
        via NextHop configuration is referred to as an AON cloud.
        
          _____________                      _____________
         | Source      |                    | Destination |
         | End point   |                    | End point   |
         | Application |                    | Application |
         | ____________|                    |_____________|
           _____|________________________________^_____     
          (     |        AON Cloud               |     )
          (   __V______       ________       ____|___  )
          (   |        |     |        |     |        | )
          (   | AON    |     | AON    |     | AON    | )
          (   | Entry  |     | Inter- |     | Exit   | )
          (   | Node   |     | mediate|     | Node   | )
          (   |        |---->| Node   |---->|        | )
          (   |        |     |        |     |        | )
          (   |        |     |        |     |        | )
          (   |_______ |     |_______ |     |________| )
          (                                            )
          (                                            )
          (___________________________________________ )
                          Figure 2: AON Cloud
        
        Entry Node : The first node in an AON cloud, generally the one
        closest to the client, is known as the Entry Node.  This node 
        is also sometimes referred to as the Client Proxy.
        
        Exit Node : The ultimate node in an AON cloud, generally the
        one closest to the server, is known as the Exit Node.  This 
        node is also sometimes referred to as the Server Proxy.
        
        Intermediate Node : Any AON node in an AON cloud that is
        neither directly communicating with the client or the server
        (i.e. neither an Entry Node nor an Exit Node) is known as an
        Intermediate Node.
        
        PEP : Policy Execution Plan.  A PEP is a sequence of bladelets
        that determine how a message is processed in AON.
        
        MEP : Message Exchange Pattern.  MEP describes the pattern of
        messages required by a communications protocol to establish or
        use a communication channel. There are two major message       
        exchange patterns: a request response pattern, and a one way
        pattern.
        
        Bladelet : A bladelet is a piece of software that performs a
        specific message handling function.  Bladelets are combined
        together into PEPs.
        
        Send Bladelet : Routing bladelet that sends a message to a
        selected destination.
        
        Notify Bladelet :  Bladelet for generating a custom
        notification (either as SNMP trap or email) based on user
        specified condition.
        
        NamedException : A NamedException is exposed by a bladelet as
        connection points to identify a recoverable exception.  The
        action to handle a NamedException thrown by a bladelet can be
        explicitly designed in the PEP by associating a execution path
        which comprises of a series of bladelet.
        
        Exception Block : It is the block in the PEP that is marked by
        the exception marker and which is executed in case of a 
        bladelet exception that is not a NamedException that has an
        output path associated with it.
        
        URI : Uniform Resource Identifier.  A URI (Uniform Resource
        Identifier) is the way you identify any content in the Internet
        space, whether it be a page of text, a video or sound clip, a
        still or animated image, or a program.
        The most common form of URI is the Web page address, which is a
        particular form or subset of URI called a Uniform Resource
        Locator (URL).  A URI typically describes:
        * mechanism used to access the resource
        * specific computer that the resource is housed in
        * specific name of the resource (a file name) on the computer.
        
        URL : Uniform Resource Locator.  A URL (Uniform Resource
        Locator) is the unique Internet address for a file.  The URL
        contains the name of the protocol to be used to access the file
        resource, a domain name that identifies a specific computer on
        the Internet, and a pathname, a hierarchical description that
        specifies the location of a file in that computer.
        
        End point: An end point is an application that is either a
        sender (client) or a receiver (server) of messages that
        communicates with AON.

Imported Objects

ciscoMgmtCISCO-SMI
CiscoPort, CiscoURLStringCISCO-TC
InetAddress, InetAddressTypeINET-ADDRESS-MIB
SnmpAdminStringSNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUPSNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, Counter32, NOTIFICATION-TYPE, Gauge32, TimeTicks, Unsigned32SNMPv2-SMI
TimeStamp, DateAndTimeSNMPv2-TC
ciscoAonStatusMIB .1.3.6.1.4.1.9.9.646
ciscoAonStatusMIBNotifs .1.3.6.1.4.1.9.9.646.0
caonUp .1.3.6.1.4.1.9.9.646.0.1
caonDown .1.3.6.1.4.1.9.9.646.0.2
caonNewPepDeployed .1.3.6.1.4.1.9.9.646.0.3
caonMessageDeliveryFailed .1.3.6.1.4.1.9.9.646.0.4
caonSendResponseThresholdExceeded .1.3.6.1.4.1.9.9.646.0.5
caonCustomNotification .1.3.6.1.4.1.9.9.646.0.6
ciscoAonStatusMIBObjects .1.3.6.1.4.1.9.9.646.1
caonSystemInfo .1.3.6.1.4.1.9.9.646.1.1
caonNodeState .1.3.6.1.4.1.9.9.646.1.1.1
caonPepEndPointTable .1.3.6.1.4.1.9.9.646.1.1.10
caonPepEndPointEntry .1.3.6.1.4.1.9.9.646.1.1.10.1
caonPepEndPointIndex .1.3.6.1.4.1.9.9.646.1.1.10.1.1
caonEndPointAvgResponseTime .1.3.6.1.4.1.9.9.646.1.1.10.1.10
caonPepEndPointUrl .1.3.6.1.4.1.9.9.646.1.1.10.1.2
caonEndPointAttemptedMessages .1.3.6.1.4.1.9.9.646.1.1.10.1.3
caonOneWayDeliveredMessages .1.3.6.1.4.1.9.9.646.1.1.10.1.4
caonOneWayFailedMessages .1.3.6.1.4.1.9.9.646.1.1.10.1.5
caonReqResponseDeliveredMessages .1.3.6.1.4.1.9.9.646.1.1.10.1.6
caonReqResponseFailedMessages .1.3.6.1.4.1.9.9.646.1.1.10.1.7
caonEndPointMinResponseTime .1.3.6.1.4.1.9.9.646.1.1.10.1.8
caonEndPointMaxResponseTime .1.3.6.1.4.1.9.9.646.1.1.10.1.9
caonCounterDiscontinuityTime .1.3.6.1.4.1.9.9.646.1.1.11
caonBootTime .1.3.6.1.4.1.9.9.646.1.1.2
caonLastActivateTime .1.3.6.1.4.1.9.9.646.1.1.3
caonReceivedMessages .1.3.6.1.4.1.9.9.646.1.1.4
caonAmcIpAddressType .1.3.6.1.4.1.9.9.646.1.1.5
caonAmcIpAddress .1.3.6.1.4.1.9.9.646.1.1.6
caonPepCount .1.3.6.1.4.1.9.9.646.1.1.7
caonPepTable .1.3.6.1.4.1.9.9.646.1.1.8
caonPepEntry .1.3.6.1.4.1.9.9.646.1.1.8.1
caonPepIndex .1.3.6.1.4.1.9.9.646.1.1.8.1.1
caonPepName .1.3.6.1.4.1.9.9.646.1.1.8.1.2
caonPepStyle .1.3.6.1.4.1.9.9.646.1.1.8.1.3
caonPepReceivedMessages .1.3.6.1.4.1.9.9.646.1.1.8.1.4
caonPepFailures .1.3.6.1.4.1.9.9.646.1.1.8.1.5
caonPepSecurityFailures .1.3.6.1.4.1.9.9.646.1.1.8.1.6
caonNotificationInfo .1.3.6.1.4.1.9.9.646.1.2
caonMessageSrcUri .1.3.6.1.4.1.9.9.646.1.2.1
caonMessageSrcIpAddressType .1.3.6.1.4.1.9.9.646.1.2.2
caonMessageSrcIpAddress .1.3.6.1.4.1.9.9.646.1.2.3
caonMessageSrcPort .1.3.6.1.4.1.9.9.646.1.2.4
caonNotificationName .1.3.6.1.4.1.9.9.646.1.2.5
caonNotificationText .1.3.6.1.4.1.9.9.646.1.2.6
caonSendResponseThreshold .1.3.6.1.4.1.9.9.646.1.2.7
caonNotifEnableIndicators .1.3.6.1.4.1.9.9.646.1.2.8
ciscoAonStatusMIBConform .1.3.6.1.4.1.9.9.646.2
ciscoAonStatusMIBCompliances .1.3.6.1.4.1.9.9.646.2.1
ciscoAonStatusMIBGroups .1.3.6.1.4.1.9.9.646.2.2