CISCO-SAN-BASE-SVC-MIB

        Common MIB module to manage services in Storage Area
Network (SAN).  Service is deployed on service
nodes on multiple switches forming a cluster.  
Nodes in the same cluster pick up the workload of 
a failed node to provide fault tolerance.  An example 
of service that can be deployed is 
IO Acceleration (IOA) service.
        
Glossary:
The following terms are used in this MIB: 
pWWN:
Port World Wide Name is a identifier assigned to a 
port in a Fibre Channel fabric. They perform a function
equivalent to the MAC address in Ethernet protocol,
as it is supposed to be unique identifier in the 
network.
        
Nx_port:
Nx_port is a storage port in Fibre Channel fabric 
that belongs to host or target.
    
Source file
CISCO-SAN-BASE-SVC-MIB
Last revised
Identity
ciscoSanBaseSvcMIB
Base OID
1.3.6.1.4.1.9.9.702
Imported Objects
CISCO-SMI ciscoMgmt
CISCO-ST-TC FcNameId
IF-MIB ifDescr InterfaceIndex
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC RowStatus StorageType TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue
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-SAN-BASE-SVC-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-SAN-BASE-SVC-MIB::ciscoSanBaseSvcMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-SAN-BASE-SVC-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-SAN-BASE-SVC-MIB::ciscoSanBaseSvcMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (47)
.1.3.6.1.4.1.9.9.702
.1.3.6.1.4.1.9.9.702.0
.1.3.6.1.4.1.9.9.702.1
.1.3.6.1.4.1.9.9.702.1.1
.1.3.6.1.4.1.9.9.702.1.1.1
.1.3.6.1.4.1.9.9.702.1.1.1.1
.1.3.6.1.4.1.9.9.702.1.1.1.1.1
OctetString
.1.3.6.1.4.1.9.9.702.1.1.1.1.2
.1.3.6.1.4.1.9.9.702.1.1.1.1.3
.1.3.6.1.4.1.9.9.702.1.1.1.1.4
.1.3.6.1.4.1.9.9.702.1.1.1.1.5
.1.3.6.1.4.1.9.9.702.1.1.1.1.6
.1.3.6.1.4.1.9.9.702.1.1.1.1.7
.1.3.6.1.4.1.9.9.702.1.1.1.1.8
.1.3.6.1.4.1.9.9.702.1.1.2
.1.3.6.1.4.1.9.9.702.1.1.2.1
.1.3.6.1.4.1.9.9.702.1.1.2.1.1
OctetString
.1.3.6.1.4.1.9.9.702.1.1.2.1.2
OctetString
.1.3.6.1.4.1.9.9.702.1.1.2.1.3
.1.3.6.1.4.1.9.9.702.1.1.2.1.4
.1.3.6.1.4.1.9.9.702.1.1.2.1.5
.1.3.6.1.4.1.9.9.702.1.1.2.1.6
.1.3.6.1.4.1.9.9.702.1.1.2.1.7
.1.3.6.1.4.1.9.9.702.1.1.3
.1.3.6.1.4.1.9.9.702.1.1.3.1
.1.3.6.1.4.1.9.9.702.1.1.3.1.1
.1.3.6.1.4.1.9.9.702.1.1.3.1.2
.1.3.6.1.4.1.9.9.702.1.1.3.1.3
.1.3.6.1.4.1.9.9.702.1.1.3.1.4
.1.3.6.1.4.1.9.9.702.1.1.3.1.5
.1.3.6.1.4.1.9.9.702.1.1.4
.1.3.6.1.4.1.9.9.702.1.1.4.1
.1.3.6.1.4.1.9.9.702.1.1.4.1.1
.1.3.6.1.4.1.9.9.702.1.1.4.1.2
.1.3.6.1.4.1.9.9.702.1.1.4.1.3
.1.3.6.1.4.1.9.9.702.1.1.4.1.4
.1.3.6.1.4.1.9.9.702.1.1.5
.1.3.6.1.4.1.9.9.702.1.1.6
.1.3.6.1.4.1.9.9.702.1.1.7
.1.3.6.1.4.1.9.9.702.1.2
.1.3.6.1.4.1.9.9.702.1.2.1
.1.3.6.1.4.1.9.9.702.1.2.1.1
.1.3.6.1.4.1.9.9.702.1.2.1.1.1
.1.3.6.1.4.1.9.9.702.1.2.1.1.2
.1.3.6.1.4.1.9.9.702.2
.1.3.6.1.4.1.9.9.702.2.1
.1.3.6.1.4.1.9.9.702.2.2
Dependencies (10) 8 direct · 2 transitive 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 (3)
OctetString range: 8
Enumeration
unknown(1)
inactive(2)
degraded(3)
recovery(4)
active(5)
Enumeration
unknown(1)
initializing(2)
offline(3)
online(4)
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.702.2.1.1
The compliance statement for entities that implement
this base service.
Required groups
Notifications / Traps (3)
NameOIDDescription
.1.3.6.1.4.1.9.9.702.0.1
This notification is generated when a service interface
associated with a local device is created. The generation
of this notification is controlled by
cSanBaseSvcNotifyEnable
.1.3.6.1.4.1.9.9.702.0.2
This notification is generated when a service interface
associated with a local device is deleted. The generation
of this notification is controlled by
cSanBaseSvcNotifyEnable
.1.3.6.1.4.1.9.9.702.0.3
This notification is generated when the sending device
who is participating in a service cluster has transitioned
to be the master of the cluster. The generation
of this notification is controlled by
cSanBaseSvcNotifyEnable