CISCO-VPN-LIC-USAGE-MONITOR-MIB

        Acronyms and Definitions
The following acronyms and terms are used in this 
document:
        
  IPSec: Secure IP Protocol
        
  VPN:   Virtual Private Network
        
  LAN:   Local Area Network
        
  Group: A collection of VPN license usage users grouped
         and managed together as a single entity for
         administrative convenience.
        
  SVC:    SSL VPN Client
        
  LicServer: Multi-site shared License server.
        
  LicBkpServer: Multi-site shared License Backup server.
        
  LicClient: Multi-site shared License client.
        
Overview of the MIB
        
This is a MIB Module for monitoring licenses in Virtual 
Private Networks. The MIB seeks to create a common model of
VPN License 
Usage across different VPN implementations. The MIB defines
counters 
and objects of interest to usage/message monitoring in a 
way which is independent of which VPN technology is
requested.
        
MIB contains four major groups of objects which are used 
to get VPN License Usage information
 a) VPN Lic device type
    This section defines if the device is acting as a
server,
    backupserver, client(participant) in a shared license
system.
        
b) VPN License Server Usage group
    This section defines total network license usage
information
    and also server information as well along with backup
server address. 
    service.
        
c) VPN License Backup server Usage group
    This section defines backup license server information
in detail,
    along with statistics of hello, sync and update messages
from 
    server.
        
d) VPN License client Usage group
    This section defines license usage information by this
client.
    along with statistics about registration, get
request,release request
    and transfer request.
    
Source file
CISCO-VPN-LIC-USAGE-MONITOR-MIB
Last revised
Identity
ciscoVpnLicUsageMonitorMIB
Base OID
1.3.6.1.4.1.9.9.816
Imported Objects
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 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-VPN-LIC-USAGE-MONITOR-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-VPN-LIC-USAGE-MONITOR-MIB::ciscoVpnLicUsageMonitorMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-VPN-LIC-USAGE-MONITOR-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-VPN-LIC-USAGE-MONITOR-MIB::ciscoVpnLicUsageMonitorMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (58)
.1.3.6.1.4.1.9.9.816
.1.3.6.1.4.1.9.9.816.0
.1.3.6.1.4.1.9.9.816.0.1
.1.3.6.1.4.1.9.9.816.0.2
.1.3.6.1.4.1.9.9.816.0.2.1
.1.3.6.1.4.1.9.9.816.0.2.2
.1.3.6.1.4.1.9.9.816.0.2.3
.1.3.6.1.4.1.9.9.816.0.2.4
Integer32
.1.3.6.1.4.1.9.9.816.0.2.5
.1.3.6.1.4.1.9.9.816.0.2.6
.1.3.6.1.4.1.9.9.816.0.2.7
.1.3.6.1.4.1.9.9.816.0.2.7.1
.1.3.6.1.4.1.9.9.816.0.2.7.1.1
.1.3.6.1.4.1.9.9.816.0.2.7.1.2
.1.3.6.1.4.1.9.9.816.0.2.7.1.3
.1.3.6.1.4.1.9.9.816.0.2.7.1.4
.1.3.6.1.4.1.9.9.816.0.3
.1.3.6.1.4.1.9.9.816.0.3.1
.1.3.6.1.4.1.9.9.816.0.3.10
.1.3.6.1.4.1.9.9.816.0.3.11
.1.3.6.1.4.1.9.9.816.0.3.12
.1.3.6.1.4.1.9.9.816.0.3.13
.1.3.6.1.4.1.9.9.816.0.3.14
.1.3.6.1.4.1.9.9.816.0.3.15
.1.3.6.1.4.1.9.9.816.0.3.16
.1.3.6.1.4.1.9.9.816.0.3.17
.1.3.6.1.4.1.9.9.816.0.3.2
OctetString
.1.3.6.1.4.1.9.9.816.0.3.3
.1.3.6.1.4.1.9.9.816.0.3.4
.1.3.6.1.4.1.9.9.816.0.3.5
OctetString
.1.3.6.1.4.1.9.9.816.0.3.6
.1.3.6.1.4.1.9.9.816.0.3.7
.1.3.6.1.4.1.9.9.816.0.3.8
.1.3.6.1.4.1.9.9.816.0.3.9
.1.3.6.1.4.1.9.9.816.0.4
.1.3.6.1.4.1.9.9.816.0.4.1
.1.3.6.1.4.1.9.9.816.0.4.1.1
.1.3.6.1.4.1.9.9.816.0.4.1.1.1
.1.3.6.1.4.1.9.9.816.0.4.1.1.10
.1.3.6.1.4.1.9.9.816.0.4.1.1.11
.1.3.6.1.4.1.9.9.816.0.4.1.1.12
.1.3.6.1.4.1.9.9.816.0.4.1.1.13
.1.3.6.1.4.1.9.9.816.0.4.1.1.14
.1.3.6.1.4.1.9.9.816.0.4.1.1.15
.1.3.6.1.4.1.9.9.816.0.4.1.1.16
.1.3.6.1.4.1.9.9.816.0.4.1.1.17
.1.3.6.1.4.1.9.9.816.0.4.1.1.18
OctetString
.1.3.6.1.4.1.9.9.816.0.4.1.1.2
OctetString
.1.3.6.1.4.1.9.9.816.0.4.1.1.3
.1.3.6.1.4.1.9.9.816.0.4.1.1.4
.1.3.6.1.4.1.9.9.816.0.4.1.1.5
.1.3.6.1.4.1.9.9.816.0.4.1.1.6
.1.3.6.1.4.1.9.9.816.0.4.1.1.7
.1.3.6.1.4.1.9.9.816.0.4.1.1.8
.1.3.6.1.4.1.9.9.816.0.4.1.1.9
.1.3.6.1.4.1.9.9.816.1
.1.3.6.1.4.1.9.9.816.1.1
.1.3.6.1.4.1.9.9.816.1.2
Dependencies (6) 6 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
Type Definitions (4)
Enumeration
no(1)
yes(2)
invalid(3)
Enumeration
active(1)
inactive(2)
expired(3)
Enumeration
server(1)
bkpserver(2)
client(3)
Enumeration
other(1)
anyconnectpremium(2)
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.816.1.1.1
The compliance statement for SNMP entities
the Cisco VPN License Usage Monitoring MIB.
Required groups