---
oid: "1.3.6.1.4.1.17409.2.3.4.3.1.3"
short-description: "onuGePortBitmap OBJECT-TYPE"
last-modified: "2022-02-02"
parent-oid: "1.3.6.1.4.1.17409.2.3.4.3.1"
---

## OID: `1.3.6.1.4.1.17409.2.3.4.3.1.3`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 17409 nscrtvEponEocTree(2) eponTree(3) onuObjects(4) onuCapabilityTable(3) onuCapabilityEntry(1) onuGePortBitmap(3)}
```

### Description

```asn1
onuGePortBitmap OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"gePort 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 GE 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 GE port.
For example, if have 4 GE 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 ge ports of 4,6,10,17, the object
will be presented as:
FF 14 40 10 00 00 00 00"
```

**Classification:** MIB object for network management

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.