MICOM-RFC1604-MIB :: mcmFrPVCEndptInExcessFrames

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsMICOM-RFC1604-MIBmcmFrPVCEndptInExcessFrames

mcmFrPVCEndptInExcessFrames

Module: MICOM-RFC1604-MIB

OID (symbolic): MICOM-RFC1604-MIB::mcmFrPVCEndptInExcessFrames

OID (numeric): 1.3.6.1.4.1.335.1.4.8.1.3.1.14

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: NAME = ; DESC = The number of frames received by the \ network (ingress) for this PVC end-point \ which were treated as excess traffic. \ (Operational); HELP = Frames which are sent to the network \ with DE set to zero are treated as \ excess when more than Bc bits are submitted \ to the network during the Committed \ Information Rate Measurement Interval \ (Tc). Excess traffic may or may not \ be discarded at the ingress if more \ than Bc + Be bits are submitted to \ the network during Tc. Traffic discarded \ at the ingress is not recorded in \ mcmFrPVCEndptInExcessFrames. \ Frames which are sent to the network \ with DE set to one are also treated \ as excess traffic. \ Note: no Configuration counterpart for this object.; CAPABILITIES = ;

What is mcmFrPVCEndptInExcessFrames?

This counts frames received by the network for this PVC end-point that were treated as excess traffic, meaning more than Bc bits were submitted during the CIR measurement interval Tc; frames discarded outright at ingress for exceeding Bc+Be are not included in this count.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.335.1.4.8.1.3.1.14
snmpwalk -v2c -c public <target> MICOM-RFC1604-MIB::mcmFrPVCEndptInExcessFrames

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.335.1.4.8.1.3.1.14.1
snmpget -v2c -c public <target> MICOM-RFC1604-MIB::mcmFrPVCEndptInExcessFrames.1

Start monitoring MICOM frame relay access equipment (RFC 1604 DTE extension) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MICOM-RFC1604-MIB::mcmFrPVCEndptInExcessFrames OID value, configure state conditions and alerts, and monitor any MICOM frame relay access equipment (RFC 1604 DTE extension) from a single console.

OID Breakdown

Upper-level ancestors (9 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.335micomMICOM-OSCAR-MIB
1.3.6.1.4.1.335.1productsMICOM-OSCAR-MIB
1.3.6.1.4.1.335.1.4micom_oscarMICOM-OSCAR-MIB
Numeric OIDNameModule
1.3.6.1.4.1.335.1.4.8micom_rfc1604MICOM-RFC1604-MIB
1.3.6.1.4.1.335.1.4.8.1rfc1604_configurationMICOM-RFC1604-MIB
1.3.6.1.4.1.335.1.4.8.1.3mcmFrPVCEndptTableMICOM-RFC1604-MIB
1.3.6.1.4.1.335.1.4.8.1.3.1mcmFrPVCEndptEntryMICOM-RFC1604-MIB
1.3.6.1.4.1.335.1.4.8.1.3.1.14mcmFrPVCEndptInExcessFramesMICOM-RFC1604-MIB