OID reference

onuFePortBitmap

1.3.6.1.4.1.17409.2.3.4.3.1.5

Description

fePort Bitmap In slot+port pair list manner. Suppose each slot support up to 64 ports. One octet to indentify slot and 8 octets to identify portbitmap for the slot. The bitmap definition is internet sequence. The most left bit is for port 1 of the slot, the most right bit is for port 64 of the slot. If the slot cannot…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.17409.2.3.4.3.1 (onuCapabilityEntry)
Node code
5
Node name
onuFePortBitmap
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.17409.2.3.4.3.1.5
URN notation
urn:oid:1.3.6.1.4.1.17409.2.3.4.3.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 17409 2 3 4 3 1 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nscrtvRoot(17409) nscrtvEponEocTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nscrtvRoot(17409) nscrtvFTTxTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nscrtvRoot(17409) nscrtvEponEocTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nscrtvRoot(17409) nscrtvFTTxTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nscrtvRoot(17409) nscrtvEponEocTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nscrtvRoot(17409) nscrtvFTTxTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nscrtvRoot(17409) nscrtvEponEocTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nscrtvRoot(17409) nscrtvFTTxTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nscrtvRoot(17409) nscrtvEponEocTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nscrtvRoot(17409) nscrtvFTTxTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nscrtvRoot(17409) nscrtvEponEocTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nscrtvRoot(17409) nscrtvFTTxTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nscrtvRoot(17409) nscrtvEponEocTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nscrtvRoot(17409) nscrtvFTTxTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nscrtvRoot(17409) nscrtvEponEocTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nscrtvRoot(17409) nscrtvFTTxTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuFePortBitmap(5)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/17409/2/3/4/3/1/5
  • /ISO/Identified-Organization/6/1/4/1/17409/2/3/4/3/1/5
  • /ISO/3/6/1/4/1/17409/2/3/4/3/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/17409/nscrtvEponEocTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/enterprise/17409/nscrtvFTTxTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/enterprise/nscrtvRoot/nscrtvEponEocTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/enterprise/nscrtvRoot/nscrtvFTTxTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/enterprises/17409/nscrtvEponEocTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/enterprises/17409/nscrtvFTTxTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/enterprises/nscrtvRoot/nscrtvEponEocTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/enterprises/nscrtvRoot/nscrtvFTTxTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/17409/nscrtvEponEocTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/17409/nscrtvFTTxTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nscrtvRoot/nscrtvEponEocTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nscrtvRoot/nscrtvFTTxTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/vendor-objects/17409/nscrtvEponEocTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/vendor-objects/17409/nscrtvFTTxTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/vendor-objects/nscrtvRoot/nscrtvEponEocTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • /iso/identified-organization/dod/internet/private/vendor-objects/nscrtvRoot/nscrtvFTTxTree/eponTree/onuObjects/onuCapabilityTable/onuCapabilityEntry/onuFePortBitmap
  • Additional combinations skipped.

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-only
Status in MIB
current

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. The index encoding is not inferred here.

Published row index: onuCapabilityDeviceIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.17409.2.3.4.3.1.5

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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

onuFePortBitmap · current

onuFePortBitmap OBJECT-TYPE
			SYNTAX OCTET STRING
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
				"fePort Bitmap
				
				In slot+port pair list manner. Suppose each slot support up to 64 ports.
				One octet to indentify slot and 8 octets to identify portbitmap for
				the slot. The bitmap definition is internet sequence. The most left bit 
				is for port 1 of the slot, the most right bit is for port 64 of the slot.            
				If the slot cannot support 64 ports, set the bits of not supported ports
				to 0.            
				If the port is FE port, set the corresponding bit to 1.                 
				Since the slot num depends on each individual device, the object is variable
				length. If the device is fixed box (not modulized), set the slot number to 
				255. Then the network management system could ignore the slot info.            
				It is not necessary to list the slot doesn't support FE port.                        
				For example, if have 4 FE ports, of: 1/4, 1/6, 2/3, 4/17,
				the object will be presented in:
				01 14 00 00 00 00 00 00 00
				02 20 00 00 00 00 00 00 00
				04 00 00 80 00 00 00 00 00            
				Another example, for fixed box, if have 4 FE ports of 4,6,10,17, the object
				will be presented as:
				FF 14 40 10 00 00 00 00
				"
			::= { onuCapabilityEntry 5 }

onuFePortBitmap · current

onuFePortBitmap  OBJECT-TYPE
        SYNTAX      OCTET STRING
        MAX-ACCESS  read-only 
        STATUS      current
        DESCRIPTION
            "fePort Bitmap
            
            In slot+port pair list manner. Suppose each slot support up to 64 ports.
            One octet to indentify slot and 8 octets to identify portbitmap for
            the slot. The bitmap definition is internet sequence. The most left bit 
            is for port 1 of the slot, the most right bit is for port 64 of the slot.            
            If the slot cannot support 64 ports, set the bits of not supported ports
            to 0.            
            If the port is FE port, set the corresponding bit to 1.                 
            Since the slot num depends on each individual device, the object is variable
            length. If the device is fixed box (not modulized), set the slot number to 
            255. Then the network management system could ignore the slot info.            
            It is not necessary to list the slot doesn't support FE port.                        
            For example, if have 4 FE ports, of: 1/4, 1/6, 2/3, 4/17,
            the object will be presented in:
            01 14 00 00 00 00 00 00 00
            02 20 00 00 00 00 00 00 00
            04 00 00 80 00 00 00 00 00            
            Another example, for fixed box, if have 4 FE ports of 4,6,10,17, the object
            will be presented as:
            FF 14 40 10 00 00 00 00
            "
        ::= {onuCapabilityEntry 5 }

Meaning

Descriptions

1 unique

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

fePort Bitmap In slot+port pair list manner. Suppose each slot support up to 64 ports. One octet to indentify slot and 8 octets to identify portbitmap for the slot. The bitmap definition is internet sequence. The most left bit is for port 1 of the slot, the most right bit is for port 64 of the slot. If the slot cannot support 64 ports, set the bits of not supported ports to 0. If the port is FE port, set the corresponding bit to 1. Since the slot num depends on each individual device, the object is variable length. If the device is fixed box (not modulized), set the slot number to 255. Then the network management system could ignore the slot info. It is not necessary to list the slot doesn't support FE port. For example, if have 4 FE ports, of: 1/4, 1/6, 2/3, 4/17, the object will be presented in: 01 14 00 00 00 00 00 00 00 02 20 00 00 00 00 00 00 00 04 00 00 80 00 00 00 00 00 Another example, for fixed box, if have 4 FE ports of 4,6,10,17, the object will be presented as: FF 14 40 10 00 00 00 00

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)FS.COM MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), FS.COM MIB copies (LibreNMS/Observium Community)1 record · 3 sources

Description 1

onuFePortBitmap · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), FS.COM MIB copies (LibreNMS/Observium Community)3 sources

Status in source: current.

Names: onuFePortBitmap

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "onuFePortBitmap",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"fePort Bitmap In slot+port pair list manner. Suppose each slot support up to 64 ports. One octet to indentify slot and 8 octets to identify portbitmap for the slot. The bitmap definition is internet sequence. The most left bit is for port 1 of the slot, the most right bit is for port 64 of the slot. If the slot cannot support 64 ports, set the bits of not supported ports to 0. If the port is FE port, set the corresponding bit to 1. Since the slot num depends on each individual device, the object is variable length. If the device is fixed box (not modulized), set the slot number to 255. Then the network management system could ignore the slot info. It is not necessary to list the slot doesn't support FE port. For example, if have 4 FE ports, of: 1/4, 1/6, 2/3, 4/17, the object will be presented in: 01 14 00 00 00 00 00 00 00 02 20 00 00 00 00 00 00 00 04 00 00 80 00 00 00 00 00 Another example, for fixed box, if have 4 FE ports of 4,6,10,17, the object will be presented as: FF 14 40 10 00 00 00 00 \"",
    "::=",
    "{",
    "onuCapabilityEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "fePort Bitmap In slot+port pair list manner. Suppose each slot support up to 64 ports. One octet to indentify slot and 8 octets to identify portbitmap for the slot. The bitmap definition is internet sequence. The most left bit is for port 1 of the slot, the most right bit is for port 64 of the slot. If the slot cannot support 64 ports, set the bits of not supported ports to 0. If the port is FE port, set the corresponding bit to 1. Since the slot num depends on each individual device, the object is variable length. If the device is fixed box (not modulized), set the slot number to 255. Then the network management system could ignore the slot info. It is not necessary to list the slot doesn't support FE port. For example, if have 4 FE ports, of: 1/4, 1/6, 2/3, 4/17, the object will be presented in: 01 14 00 00 00 00 00 00 00 02 20 00 00 00 00 00 00 00 04 00 00 80 00 00 00 00 00 Another example, for fixed box, if have 4 FE ports of 4,6,10,17, the object will be presented as: FF 14 40 10 00 00 00 00"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.17409)

Chen Zhiguo

Siblings (12)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.17409.2.3.4.3.1.1 onuCapabilityDeviceIndex00
1.3.6.1.4.1.17409.2.3.4.3.1.2 onuGePortNum00
1.3.6.1.4.1.17409.2.3.4.3.1.3 onuGePortBitmap00
1.3.6.1.4.1.17409.2.3.4.3.1.4 onuFePortNum00
1.3.6.1.4.1.17409.2.3.4.3.1.6 onuQueueNumUplink00
1.3.6.1.4.1.17409.2.3.4.3.1.7 onuMaxQueueNumUplink00
1.3.6.1.4.1.17409.2.3.4.3.1.8 onuQueueNumDownlink00
1.3.6.1.4.1.17409.2.3.4.3.1.9 onuMaxQueueNumDownlink00
1.3.6.1.4.1.17409.2.3.4.3.1.10 onuFecEnable00
1.3.6.1.4.1.17409.2.3.4.3.1.11 onuEncryptMode00
1.3.6.1.4.1.17409.2.3.4.3.1.12 onuEncryptKeyExchangeTime00
1.3.6.1.4.1.17409.2.3.4.3.1.13 onuIsolationEnable00