OID reference

dot1dTpPortInFrames

1.3.6.1.4.1.49.2.4.14.4.4.1.3

Description

The number of frames that have been received by this port from its segment. Note that a frame received on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function.

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.49.2.4.14.4.4.1 (dot1dTpPortEntry)
Node code: 3
Node name: dot1dTpPortInFrames
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.49.2.4.14.4.4.1.3
URN notation: urn:oid:1.3.6.1.4.1.49.2.4.14.4.4.1.3
Type: OBJECT-TYPE

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 49 2 4 14 4 4 1 3}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) chipcom(49) chipmib02(2) chipExperiment(4) dot1dBridge(14) dot1dTp(4) dot1dTpPortTable(4) dot1dTpPortEntry(1) dot1dTpPortInFrames(3)}

OID-IRI notation

/1/3/6/1/4/1/49/2/4/14/4/4/1/3
/ISO/Identified-Organization/6/1/4/1/49/2/4/14/4/4/1/3
/ISO/3/6/1/4/1/49/2/4/14/4/4/1/3

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/identified-organization/dod/internet/private/enterprises/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/identified-organization/dod/internet/private/ldap-enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/identified-organization/dod/internet/private/vendor-objects/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/org/dod/internet/private/enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/org/dod/internet/private/enterprises/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/org/dod/internet/private/ldap-enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/org/dod/internet/private/vendor-objects/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/iso-identified-organization/dod/internet/private/enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/iso-identified-organization/dod/internet/private/enterprises/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/iso-identified-organization/dod/internet/private/vendor-objects/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/iso-organization/dod/internet/private/enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/iso-organization/dod/internet/private/enterprises/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/iso-organization/dod/internet/private/ldap-enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames
/iso/iso-organization/dod/internet/private/vendor-objects/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dTp/dot1dTpPortTable/dot1dTpPortEntry/dot1dTpPortInFrames

SNMP properties

Value type: Counter
Maximum access defined by MIB: read-only
Status in MIB: mandatory

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In ChpComm-Bridge, the row index dot1dTpPort is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.49.2.4.14.4.4.1.3.<dot1dTpPort>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

Published row index: dot1dTpPort.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.49.2.4.14.4.4.1.3

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The number of frames that have been received by
this port from its segment. Note that a frame
received on the interface corresponding to this
port is only counted by this object if and only if
it is for a protocol being processed by the local
bridging function.

Sources for this description

MIBdepot

Parsed from chipcom-bridge.mib.txt · a3com · ChpComm-Bridge

Source file: Download chipcom-mib.txt

Source file: Download chipcom-bridge.mib.txt

Browse all files from MIBdepot

Historical records

Additional source information

Information from OID Repository

Vendor: 3Com
Module: CHIPCOMMIB (chipcom-mib)
Type: TABULAR
Access: read-only
Syntax: Counter

Automatically extracted from www.mibdepot.com

Information from MIBdepot

dot1dTpPortInFrames OBJECT-TYPE
	SYNTAX  Counter
 	ACCESS  read-only
	STATUS  mandatory
	DESCRIPTION
		"The number of frames that have been received by
		this port from its segment. Note that a frame
		received on the interface corresponding to this
		port is only counted by this object if and only if
		it is for a protocol being processed by the local
		bridging function."
	REFERENCE
		"P802.1d/D9, July 14, 1989: Section 6.6.1.1.3"
	::= { dot1dTpPortEntry 3 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.49)

Cook John

Siblings (4)

OID	Name	Description
1.3.6.1.4.1.49.2.4.14.4.4.1.1	dot1dTpPort	The port number of the port for which this entry contains Transparent bridging management information.
1.3.6.1.4.1.49.2.4.14.4.4.1.2	dot1dTpPortMaxInfo	The maximum size of the INFO (non-MAC) field that this port will receive or transmit.
1.3.6.1.4.1.49.2.4.14.4.4.1.4	dot1dTpPortOutFrames	The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the interface corr…
1.3.6.1.4.1.49.2.4.14.4.4.1.5	dot1dTpPortInDiscards	Count of valid frames received which were discarded (i.e., filtered) by the Forwarding Process.