GC-MIB

All MIBs › GC-MIB

Organization: Riverbed Technology, Inc.

Last Updated: 2014-12-09

Category: Technology: WAN Optimization, Vendor: Riverbed

Description: Riverbed Technology WAN optimization MIB for monitoring Gateway Controller appliance performance and session statistics.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is GC-MIB?

GC-MIB is a Riverbed Technology proprietary MIB for the SteelFusion Core (Granite Core) appliance, a WAN optimization and branch storage consolidation platform. It exposes identity and inventory data (model, serial number, software version) alongside operational health data such as overall system health status, temperature, and per-process status via a process table. It is explicitly designed for hardware and software status monitoring: administrators use it to track system uptime/clock, temperature sensor readings, systemHealth state, and the status of individual system processes to catch failures early. The MIB is self-contained but is typically deployed alongside standard SNMP MIB-II for interface-level statistics on the same appliance. It is used in enterprise branch-office environments, where GC-MIB SNMP monitoring tracks SteelFusion Core appliances that project block storage from a data center to remote sites.

IPNetwork Monitor allows you to monitor SNMP objects defined in GC-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Riverbed SteelFusion Core (Granite Core) appliance

Monitoring Examples

An administrator would poll systemHealth and systemTemperature to detect overheating or a degraded hardware state before it causes an outage, and would walk procTable/procEntry (indexed by procIndex, with procName and status columns) to confirm critical SteelFusion processes are still running. Reading model, serialNumber, and systemVersion together provides an inventory fingerprint useful for asset tracking and firmware-compliance audits. A status value flipping to a fault code in procEntry or systemHealth would be an early sign of an appliance-level issue.

What Can Be Monitored

system health status
system temperature
process table status
software/system version
serial number and model
system uptime/clock

Imported Objects

From RBT-MIB

products

OBJECT-IDENTITY

From SNMPv2-SMI

Counter64
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks
Unsigned32

From SNMPv2-TC

DateAndTime

How to Use in IPNetwork Monitor

Example using systemHealth OID:

Select a Riverbed SteelFusion Core (Granite Core) appliance as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type systemHealth into the Find box to locate it in the OID tree, then select it and click OK. It reports the current health of the system. This variable is identical to health except that it is of integer datatype. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'healthy', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
gc	1.3.6.1.4.1.17163.1.100			Riverbed Technology SteelFusion Core MIB
system	1.3.6.1.4.1.17163.1.100.1
OCT model	1.3.6.1.4.1.17163.1.100.1.1	OCTET STRING	read-only	Appliance model
OCT serialNumber	1.3.6.1.4.1.17163.1.100.1.2	OCTET STRING	read-only	Appliance serial number
OCT systemVersion	1.3.6.1.4.1.17163.1.100.1.3	OCTET STRING	read-only	System software version string
status	1.3.6.1.4.1.17163.1.100.2
DAT systemClock	1.3.6.1.4.1.17163.1.100.2.1	DateAndTime	read-only	System clock time
OCT health	1.3.6.1.4.1.17163.1.100.2.2	OCTET STRING	read-only	Current health
INT systemHealthEx	1.3.6.1.4.1.17163.1.100.2.3	INTEGER	read-only	Current health of the system. This variable is identical to health except that it is of integer datatype
U32 systemTemperature	1.3.6.1.4.1.17163.1.100.2.4	Unsigned32	read-only	The temperature of the system (C)
procTable	1.3.6.1.4.1.17163.1.100.2.11		not-accessible	List of managed processes
procEntry	1.3.6.1.4.1.17163.1.100.2.11.1		not-accessible	Entry for one process
U32 procIndex	1.3.6.1.4.1.17163.1.100.2.11.1.1	Unsigned32	not-accessible	Synthetic numeric unique ID of process
OCT procName	1.3.6.1.4.1.17163.1.100.2.11.1.2	OCTET STRING	read-only	Unique name of process
OCT procStatus	1.3.6.1.4.1.17163.1.100.2.11.1.3	OCTET STRING	read-only	Current state of process
U32 procNumFailures	1.3.6.1.4.1.17163.1.100.2.11.1.4	Unsigned32	read-only	Number of times process has crashed or exited unexpectedly
config	1.3.6.1.4.1.17163.1.100.3
OCT activeConfig	1.3.6.1.4.1.17163.1.100.3.1	OCTET STRING	read-only	Current active configuration
alarms	1.3.6.1.4.1.17163.1.100.4
alarmsPrefix	1.3.6.1.4.1.17163.1.100.4.0
NTF procCrash	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.
NTF procExit	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.
NTF configChange	1.3.6.1.4.1.17163.1.100.4.0.3			A change has been made to the system's configuration
NTF cpuUtil	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
NTF pagingActivity	1.3.6.1.4.1.17163.1.100.4.0.5			The system has been paging excessively (thrashing)
NTF linkError	1.3.6.1.4.1.17163.1.100.4.0.6			An interface on the appliance has lost its link
NTF powerSupplyError	1.3.6.1.4.1.17163.1.100.4.0.7			A power supply on the appliance has failed
NTF fanError	1.3.6.1.4.1.17163.1.100.4.0.8			A fan has failed on this appliance
NTF memoryError	1.3.6.1.4.1.17163.1.100.4.0.9			A memory error has been detected on the appliance
NTF ipmi	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
NTF localFSFull	1.3.6.1.4.1.17163.1.100.4.0.11			The appliance local filesystem is full.
NTF temperatureCritical	1.3.6.1.4.1.17163.1.100.4.0.12			The system temperature has reached a critical stage
NTF temperatureWarning	1.3.6.1.4.1.17163.1.100.4.0.13			The system temperature has exceeded the threshold
NTF scheduledJobError	1.3.6.1.4.1.17163.1.100.4.0.14			A scheduled job has failed during execution
NTF confModeEnter	1.3.6.1.4.1.17163.1.100.4.0.15			A user has entered configuration mode
NTF confModeExit	1.3.6.1.4.1.17163.1.100.4.0.16			A user has exited configuration mode
NTF secureVaultLocked	1.3.6.1.4.1.17163.1.100.4.0.17			Secure vault is locked. The secure datastore cannot be used.
NTF procRestart	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.
NTF testTrap	1.3.6.1.4.1.17163.1.100.4.0.19			This is a test trap.
NTF cpuUtilClear	1.3.6.1.4.1.17163.1.100.4.0.1004			The average CPU utilization has fallen back within the acceptable threshold
NTF pagingActivityClear	1.3.6.1.4.1.17163.1.100.4.0.1005			The system has stopped paging excessively (thrashing)
NTF linkErrorClear	1.3.6.1.4.1.17163.1.100.4.0.1006			An interface on the appliance has regained its link
NTF powerSupplyErrorClear	1.3.6.1.4.1.17163.1.100.4.0.1007			All power supplies are now functioning normally
NTF fanErrorClear	1.3.6.1.4.1.17163.1.100.4.0.1008			All system fans are now functioning normally
NTF memoryErrorClear	1.3.6.1.4.1.17163.1.100.4.0.1009			A memory error has been rectified on the appliance
NTF ipmiClear	1.3.6.1.4.1.17163.1.100.4.0.1010			An IPMI event has been rectified on the appliance
NTF localFSFullClear	1.3.6.1.4.1.17163.1.100.4.0.1011			The appliance local filesystem usage is below threshold.
NTF temperatureNonCritical	1.3.6.1.4.1.17163.1.100.4.0.1012			The system temperature is no longer in a critical stage
NTF temperatureNormal	1.3.6.1.4.1.17163.1.100.4.0.1013			The system temperature is back within the threshold
NTF secureVaultUnlocked	1.3.6.1.4.1.17163.1.100.4.0.1017			Secure vault is unlocked. The secure data store can be used now.
NTF edgeError	1.3.6.1.4.1.17163.1.100.4.0.10500			Edge module encountered error.
NTF highAvailabilityError	1.3.6.1.4.1.17163.1.100.4.0.10501			High Availability module encountered error.
NTF lunError	1.3.6.1.4.1.17163.1.100.4.0.10502			Lun module encountered error.
NTF iscsiError	1.3.6.1.4.1.17163.1.100.4.0.10503			iSCSI module encountered error.
NTF snapshotError	1.3.6.1.4.1.17163.1.100.4.0.10505			Snapshot module encountered error.
NTF applianceUnlicensedError	1.3.6.1.4.1.17163.1.100.4.0.10506			Appliance license expired/invalid.
NTF modelUnlicensedError	1.3.6.1.4.1.17163.1.100.4.0.10507			Model license expired/invalid.
NTF blkdiskError	1.3.6.1.4.1.17163.1.100.4.0.10508			Block-disk module encountered error.
NTF backupIntegrationError	1.3.6.1.4.1.17163.1.100.4.0.10509			Backup-Integration module encountered error.
NTF otherHardwareError	1.3.6.1.4.1.17163.1.100.4.0.10510			Hardware Error detected.
NTF edgeClear	1.3.6.1.4.1.17163.1.100.4.0.11500			Edge module error cleared.
NTF highAvailabilityClear	1.3.6.1.4.1.17163.1.100.4.0.11501			High Availability module error cleared.
NTF lunClear	1.3.6.1.4.1.17163.1.100.4.0.11502			Lun module error cleared.
NTF iscsiClear	1.3.6.1.4.1.17163.1.100.4.0.11503			iSCSI module error cleared.
NTF snapshotClear	1.3.6.1.4.1.17163.1.100.4.0.11505			Snapshot module error cleared.
NTF applianceUnlicensedClear	1.3.6.1.4.1.17163.1.100.4.0.11506			Appliance license active.
NTF modelUnlicensedClear	1.3.6.1.4.1.17163.1.100.4.0.11507			Model license active.
NTF blkdiskClear	1.3.6.1.4.1.17163.1.100.4.0.11508			Block-disk module error cleared.
NTF backupIntegrationClear	1.3.6.1.4.1.17163.1.100.4.0.11509			Backup-Integration module error cleared.
NTF otherHardwareClear	1.3.6.1.4.1.17163.1.100.4.0.11510			Hardware error cleared.
statistics	1.3.6.1.4.1.17163.1.100.5
cpuLoad	1.3.6.1.4.1.17163.1.100.5.1
U32 cpuLoad1	1.3.6.1.4.1.17163.1.100.5.1.1	Unsigned32	read-only	One-minute CPU load in hundreths
U32 cpuLoad5	1.3.6.1.4.1.17163.1.100.5.1.2	Unsigned32	read-only	One-minute CPU load in hundreths
U32 cpuLoad15	1.3.6.1.4.1.17163.1.100.5.1.3	Unsigned32	read-only	Fifteen-minute CPU load in hundreths
U32 cpuUtil1	1.3.6.1.4.1.17163.1.100.5.1.4	Unsigned32	read-only	Percentage CPU utilization, aggregated across all CPUs, rolling average over the past minute
cpuIndivUtilTable	1.3.6.1.4.1.17163.1.100.5.1.5		not-accessible	Details about the individual CPU utilization
cpuIndivUtilEntry	1.3.6.1.4.1.17163.1.100.5.1.5.1		not-accessible	Entry for one cpu
U32 cpuIndivIndex	1.3.6.1.4.1.17163.1.100.5.1.5.1.1	Unsigned32	not-accessible	A synthetic number numbering the cpus
U32 cpuIndivId	1.3.6.1.4.1.17163.1.100.5.1.5.1.2	Unsigned32	read-only	Name of the cpu, also serves as the Index for the table
U32 cpuIndivIdleTime	1.3.6.1.4.1.17163.1.100.5.1.5.1.3	Unsigned32	read-only	Idle time for this CPU
U32 cpuIndivSystemTime	1.3.6.1.4.1.17163.1.100.5.1.5.1.4	Unsigned32	read-only	System time for this CPU
U32 cpuIndivUserTime	1.3.6.1.4.1.17163.1.100.5.1.5.1.5	Unsigned32	read-only	User time for this CPU

RFC description

Riverbed Technology SteelFusion Core appliance MIB for system, status, configuration, alarms, and statistics monitoring.

Start monitoring Riverbed SteelFusion Core (Granite Core) appliance with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download GC-MIB