RC-IP-MIB :: rcIpResourceUsageGlobalIngressRecInUse

MIB Reference — IPNetwork Monitor · Updated September 12, 2026

All MIBsRC-IP-MIBrcIpResourceUsageGlobalIngressRecInUse

rcIpResourceUsageGlobalIngressRecInUse

Module: RC-IP-MIB

OID (symbolic): RC-IP-MIB::rcIpResourceUsageGlobalIngressRecInUse

OID (numeric): 1.3.6.1.4.1.2272.1.8.25.1.1

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: Used to get the Ingress Record Usage in the switch. (S-G usage).

What is rcIpResourceUsageGlobalIngressRecInUse?

This is a read-only counter tracking how many ingress multicast records (Source-Group pairs) are currently active in the switch. It shows real-time memory consumption for incoming multicast streams. A network operator monitors this during peak traffic to ensure the switch won't run out of capacity for new multicast subscriptions.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2272.1.8.25.1.1
snmpwalk -v2c -c public <target> RC-IP-MIB::rcIpResourceUsageGlobalIngressRecInUse

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2272.1.8.25.1.1.1
snmpget -v2c -c public <target> RC-IP-MIB::rcIpResourceUsageGlobalIngressRecInUse.1

Start monitoring Bay Networks/Nortel Accelar (Rapid-City/Passport) Layer 3 switch (per-interface IP/routing-protocol configuration) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RC-IP-MIB::rcIpResourceUsageGlobalIngressRecInUse OID value, configure state conditions and alerts, and monitor any Bay Networks/Nortel Accelar (Rapid-City/Passport) Layer 3 switch (per-interface IP/routing-protocol configuration) from a single console.

How to Use in IPNetwork Monitor

Select a Bay Networks/Nortel Accelar (Rapid-City/Passport) Layer 3 switch 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 rcIpResourceUsageGlobalIngressRecInUse into the Find box to locate it in the OID tree, then select it and click OK. It reports the current number of ingress records in use on the switch (the S-G usage count). 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 Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if usage approaches the maximum ingress-record capacity for this platform, since running out of ingress records can block new flow programming. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (11 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.2272rapidCityRAPID-CITY
1.3.6.1.4.1.2272.1rcMgmtRAPID-CITY
1.3.6.1.4.1.2272.1.8rcIpRAPID-CITY
1.3.6.1.4.1.2272.1.8.25rcIpResourceUsageRAPID-CITY
1.3.6.1.4.1.2272.1.8.25.1rcIpResourceUsageGlobalRAPID-CITY
Numeric OIDNameModule
1.3.6.1.4.1.2272.1.8.25.1.1rcIpResourceUsageGlobalIngressRecInUseRC-IP-MIB