OID reference

dot1dBaseType

1.3.6.1.4.1.49.2.4.14.1.3

Description

Indicates what type of bridging this bridge can perform. If a bridge is actually performing a certain type of bridging this will be indicated by entries in the port table for the given type.

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.49.2.4.14.1 (dot1dBase)
Node code: 3
Node name: dot1dBaseType
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.49.2.4.14.1.3
URN notation: urn:oid:1.3.6.1.4.1.49.2.4.14.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 1 3}

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

OID-IRI notation

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

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/identified-organization/dod/internet/private/enterprises/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/identified-organization/dod/internet/private/ldap-enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/identified-organization/dod/internet/private/vendor-objects/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/org/dod/internet/private/enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/org/dod/internet/private/enterprises/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/org/dod/internet/private/ldap-enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/org/dod/internet/private/vendor-objects/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/iso-identified-organization/dod/internet/private/enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/iso-identified-organization/dod/internet/private/enterprises/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/iso-identified-organization/dod/internet/private/vendor-objects/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/iso-organization/dod/internet/private/enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/iso-organization/dod/internet/private/enterprises/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/iso-organization/dod/internet/private/ldap-enterprise/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType
/iso/iso-organization/dod/internet/private/vendor-objects/chipcom/chipmib02/chipExperiment/dot1dBridge/dot1dBase/dot1dBaseType

SNMP properties

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

Enumerated values

Value	Name
1	unknown
2	transparent-only
3	sourceroute-only
4	srt

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.49.2.4.14.1.3.0

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.

Indicates what type of bridging this bridge can
perform. If a bridge is actually performing a
certain type of bridging this will be indicated by
entries in the port table for the given type.

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

Child arc 0 is used to translate between SNMPv1 and SNMPv2 notification parameters as explained in IETF RFC 2576, section 3.

Information from MIBdepot

dot1dBaseType OBJECT-TYPE
	SYNTAX  INTEGER {
		unknown(1),
		transparent-only(2),
		sourceroute-only(3),
            	srt(4)
		}
 	ACCESS  read-only
	STATUS  mandatory
	DESCRIPTION
		"Indicates what type of bridging this bridge can
		perform.  If a bridge is actually performing a
		certain type of bridging this will be indicated by
		entries in the port table for the given type."
	::= { dot1dBase 3 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.49)

Cook John

Direct children (1)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.49.2.4.14.1.3.0	dot1dBaseType	0	0

Siblings (3)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.49.2.4.14.1.1	dot1dBaseBridgeAddress	1	1	The MAC address used by this bridge when it must be referred to in a unique fashion. It is recommended that this be the numeric…
1.3.6.1.4.1.49.2.4.14.1.2	dot1dBaseNumPorts	1	1	The number of ports controlled by this bridging entity.
1.3.6.1.4.1.49.2.4.14.1.4	dot1dBasePortTable	1	6	A table that contains generic information about every port that is associated with this bridge. Transparent, source-route, and sr…