GC-MIB
Riverbed Technology SteelFusion Core MIB
- Source file
GC-MIB- Last revised
- Identity
gc- Base OID
1.3.6.1.4.1.17163.1.100
Imported Objects
| RBT-MIB | products |
| SNMPv2-SMI | Counter64 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) TimeTicks Unsigned32 |
| SNMPv2-TC | DateAndTime |
Net-SNMP examples using the riverbed 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 'GC-MIB' -M '/opt/observium/mibs/riverbed:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'GC-MIB::gc'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'GC-MIB' -M '/opt/observium/mibs/riverbed:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'GC-MIB::gc'
Objects (33)
Showing 33 of 33 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.17163.1.100 |
||
.1.3.6.1.4.1.17163.1.100.1 |
||
|
OctetString
|
.1.3.6.1.4.1.17163.1.100.1.1 |
|
|
OctetString
|
.1.3.6.1.4.1.17163.1.100.1.2 |
|
|
OctetString
|
.1.3.6.1.4.1.17163.1.100.1.3 |
|
.1.3.6.1.4.1.17163.1.100.2 |
||
.1.3.6.1.4.1.17163.1.100.2.1 |
||
.1.3.6.1.4.1.17163.1.100.2.11 |
||
.1.3.6.1.4.1.17163.1.100.2.11.1 |
||
.1.3.6.1.4.1.17163.1.100.2.11.1.1 |
||
|
OctetString
|
.1.3.6.1.4.1.17163.1.100.2.11.1.2 |
|
|
OctetString
|
.1.3.6.1.4.1.17163.1.100.2.11.1.3 |
|
.1.3.6.1.4.1.17163.1.100.2.11.1.4 |
||
|
OctetString
|
.1.3.6.1.4.1.17163.1.100.2.2 |
|
|
Enumeration
|
.1.3.6.1.4.1.17163.1.100.2.3 |
|
.1.3.6.1.4.1.17163.1.100.2.4 |
||
.1.3.6.1.4.1.17163.1.100.3 |
||
|
OctetString
|
.1.3.6.1.4.1.17163.1.100.3.1 |
|
.1.3.6.1.4.1.17163.1.100.4 |
||
.1.3.6.1.4.1.17163.1.100.4.0 |
||
.1.3.6.1.4.1.17163.1.100.5 |
||
.1.3.6.1.4.1.17163.1.100.5.1 |
||
.1.3.6.1.4.1.17163.1.100.5.1.1 |
||
.1.3.6.1.4.1.17163.1.100.5.1.2 |
||
.1.3.6.1.4.1.17163.1.100.5.1.3 |
||
.1.3.6.1.4.1.17163.1.100.5.1.4 |
||
.1.3.6.1.4.1.17163.1.100.5.1.5 |
||
.1.3.6.1.4.1.17163.1.100.5.1.5.1 |
||
.1.3.6.1.4.1.17163.1.100.5.1.5.1.1 |
||
.1.3.6.1.4.1.17163.1.100.5.1.5.1.2 |
||
.1.3.6.1.4.1.17163.1.100.5.1.5.1.3 |
||
.1.3.6.1.4.1.17163.1.100.5.1.5.1.4 |
||
.1.3.6.1.4.1.17163.1.100.5.1.5.1.5 |
Dependencies (3) 3 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
- SNMPv2-SMIrfc
- RBT-MIBriverbed
- SNMPv2-TCrfc
- GC-MIBriverbedselected
Notifications / Traps (50)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.17163.1.100.4.0.1 |
A procCrash trap signifies that a process managed by PM
has crashed and left a core file. The variable sent with the notification indicates which process crashed. |
|
.1.3.6.1.4.1.17163.1.100.4.0.10 |
An IPMI event has been detected on the appliance. Please check
the details in the alarm report on the web UI |
|
.1.3.6.1.4.1.17163.1.100.4.0.1004 |
The average CPU utilization has fallen back
within the acceptable threshold |
|
.1.3.6.1.4.1.17163.1.100.4.0.1005 |
The system has stopped paging excessively (thrashing)
|
|
.1.3.6.1.4.1.17163.1.100.4.0.1006 |
An interface on the appliance has regained its link
|
|
.1.3.6.1.4.1.17163.1.100.4.0.1007 |
All power supplies are now functioning normally
|
|
.1.3.6.1.4.1.17163.1.100.4.0.1008 |
All system fans are now functioning normally
|
|
.1.3.6.1.4.1.17163.1.100.4.0.1009 |
A memory error has been rectified on the appliance
|
|
.1.3.6.1.4.1.17163.1.100.4.0.1010 |
An IPMI event has been rectified on the appliance
|
|
.1.3.6.1.4.1.17163.1.100.4.0.1011 |
The appliance local filesystem usage is below threshold.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.1012 |
The system temperature is no longer in a critical stage
|
|
.1.3.6.1.4.1.17163.1.100.4.0.1013 |
The system temperature is back within the threshold
|
|
.1.3.6.1.4.1.17163.1.100.4.0.1017 |
Secure vault is unlocked. The secure data store can be used now.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.10500 |
Edge module encountered error.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.10501 |
High Availability module encountered error.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.10502 |
Lun module encountered error.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.10503 |
iSCSI module encountered error.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.10505 |
Snapshot module encountered error.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.10506 |
Appliance license expired/invalid.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.10507 |
Model license expired/invalid.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.10508 |
Block-disk module encountered error.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.10509 |
Backup-Integration module encountered error.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.10510 |
Hardware Error detected.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11 |
The appliance local filesystem is full.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11500 |
Edge module error cleared.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11501 |
High Availability module error cleared.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11502 |
Lun module error cleared.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11503 |
iSCSI module error cleared.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11505 |
Snapshot module error cleared.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11506 |
Appliance license active.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11507 |
Model license active.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11508 |
Block-disk module error cleared.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11509 |
Backup-Integration module error cleared.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.11510 |
Hardware error cleared.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.12 |
The system temperature has reached a critical stage
|
|
.1.3.6.1.4.1.17163.1.100.4.0.13 |
The system temperature has exceeded the threshold
|
|
.1.3.6.1.4.1.17163.1.100.4.0.14 |
A scheduled job has failed during execution
|
|
.1.3.6.1.4.1.17163.1.100.4.0.15 |
A user has entered configuration mode
|
|
.1.3.6.1.4.1.17163.1.100.4.0.16 |
A user has exited configuration mode
|
|
.1.3.6.1.4.1.17163.1.100.4.0.17 |
Secure vault is locked. The secure datastore cannot be used.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.18 |
A procRestart trap signifies that a process managed by PM
has restarted. The variable sent with the notification indicates which process restarted. |
|
.1.3.6.1.4.1.17163.1.100.4.0.19 |
This is a test trap.
|
|
.1.3.6.1.4.1.17163.1.100.4.0.2 |
A procExit trap signifies that a process managed by PM
has exited unexpectedly, but not left a core file. The variable sent with the notification indicates which process exited. |
|
.1.3.6.1.4.1.17163.1.100.4.0.3 |
A change has been made to the system's configuration
|
|
.1.3.6.1.4.1.17163.1.100.4.0.4 |
The average CPU utilization in the past minute has gone
above the acceptable threshold |
|
.1.3.6.1.4.1.17163.1.100.4.0.5 |
The system has been paging excessively (thrashing)
|
|
.1.3.6.1.4.1.17163.1.100.4.0.6 |
An interface on the appliance has lost its link
|
|
.1.3.6.1.4.1.17163.1.100.4.0.7 |
A power supply on the appliance has failed
|
|
.1.3.6.1.4.1.17163.1.100.4.0.8 |
A fan has failed on this appliance
|
|
.1.3.6.1.4.1.17163.1.100.4.0.9 |
A memory error has been detected on the appliance
|