HP Cisco Nexus 5000 Cisco MDS 9000 Family MIB Quick Reference (OL-18087-01, Fe - Page 49

Cisco-st-tc, Cisco-svc-interface-mib, Cisco-syslog-ext-mib, Cisco-tpc-mib

Page 49 highlights

Cisco-Specific MIBs Supported in the Cisco MDS 9000 Family Send documentation comments to [email protected] CISCO-ST-TC This file defines textual conventions used in MIBs that are specific to SANs in the Cisco MDS 9000 Family. CISCO-SVC-INTERFACE-MIB This MIB configures and monitors SVC related features in SAN switches. SVC supports a virtualized pool of storage from the storage subsystems attached to a SAN. This MIB monitors virtualization features per interface and per VSAN. CISCO-SYSLOG-EXT-MIB This MIB configures and monitors system log (syslog) management parameters. Syslog is defined by RFC 3164. Use this MIB to set up syslog servers and set logging severity levels. CISCO-SYSLOG-MIB This MIB collects system messages generated by Cisco MDS NX-OS or SAN-OS. These messages are typically sent to a syslog server. Use this MIB to retrieve SYSLOG-MIB system messages. CISCO-SYSTEM-MIB This MIB provides Cisco-defined extensions to the MIB-II systemGroup. CISCO-SYSTEM-EXT-MIB This MIB monitors high availability (HA) and provides an extension to the SNMP error status when an SNMP set request fails. CISCO-TC This file defines the common TEXTUAL-CONVENTIONS used in all Cisco MIBs. These conventions make it easier to realize the type or purpose of a MIB object by adding a label to an underlying primitive. DisplayString is a frequently used TEXTUAL-CONVENTION defined in SNMP. CISCO-TPC-MIB This MIB configures the TPC targets. This MIB is used with the Network Assisted Serverless Backup (NASB) feature. You specify the module and the VSAN on which the TPC feature needs to be configured. Once the feature is configured, target ports are created on the specified module and VSAN that are SCSI Extended Copy (XCOPY) capable. Any application that can source an XCOPY command can use these targets to perform data movement. OL-18087-01, Cisco MDS NX-OS Release 4.x Cisco MDS 9000 Family MIB Quick Reference 49

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56

Send documentation comments to [email protected]
49
Cisco MDS 9000 Family MIB Quick Reference
OL-18087-01, Cisco MDS NX-OS Release 4.x
Cisco-Specific MIBs Supported in the Cisco MDS 9000 Family
CISCO-ST-TC
This file defines textual conventions used in MIBs that are specific to SANs in the Cisco MDS 9000
Family.
CISCO-SVC-INTERFACE-MIB
This MIB configures and monitors SVC related features in SAN switches. SVC supports a virtualized
pool of storage from the storage subsystems attached to a SAN. This MIB monitors virtualization
features per interface and per VSAN.
CISCO-SYSLOG-EXT-MIB
This MIB configures and monitors system log (syslog) management parameters. Syslog is defined by
RFC 3164. Use this MIB to set up syslog servers and set logging severity levels.
CISCO-SYSLOG-MIB
This MIB collects system messages generated by Cisco MDS NX-OS or SAN-OS. These messages are
typically sent to a syslog server. Use this MIB to retrieve SYSLOG-MIB system messages.
CISCO-SYSTEM-MIB
This MIB provides Cisco-defined extensions to the MIB-II systemGroup.
CISCO-SYSTEM-EXT-MIB
This MIB monitors high availability (HA) and provides an extension to the SNMP error status when an
SNMP
set
request fails.
CISCO-TC
This file defines the common TEXTUAL-CONVENTIONS used in all Cisco MIBs. These conventions
make it easier to realize the type or purpose of a MIB object by adding a label to an underlying primitive.
DisplayString
is a frequently used TEXTUAL-CONVENTION defined in SNMP.
CISCO-TPC-MIB
This MIB configures the TPC targets. This MIB is used with the Network Assisted Serverless Backup
(NASB) feature. You specify the module and the VSAN on which the TPC feature needs to be
configured. Once the feature is configured, target ports are created on the specified module and VSAN
that are SCSI Extended Copy (XCOPY) capable. Any application that can source an XCOPY command
can use these targets to perform data movement.