---
oid: "1.3.6.1.2.1.135.1.1.2.1.15"
short-description: "t11NsRegFc4Features OBJECT-TYPE"
last-modified: "2020-01-23"
parent-oid: "1.3.6.1.2.1.135.1.1.2.1"
---

## OID: `1.3.6.1.2.1.135.1.1.2.1.15`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) t11FcNameServerMIB(135) t11NsMIBObjects(1) t11NsStatus(1) t11NsRegTable(2) t11NsRegEntry(1) t11NsRegFc4Features(15)}
```

### Description

```asn1
t11NsRegFc4Features OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0 | 128))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The FC-4 Features associated with FC-4 Types on this
port encoded as a 128-byte value in network-byte order,
or the zero-length string if no 'FC-4 Features' have been
registered.
Section 5.2.3.15 of FC-GS-4 is the authoritative
definition of the format of the 128-byte value,
i.e., if different, FC-GS-4 takes precedence over the
following description:
The 128-byte value is an array of 4-bit values, one for
each FC-4 Type value, positioned as follows: the 5 most
significant bits of a Type value identify where it appears
within the 128-byte value, specifically, within which word:
- Word 0 (of the 128-byte value) contains information
related to Types '00' through '07';
- Word 1 contains information related to Types
'08' through 0F';
- and so forth, up to Word 31, which contains
information related to Types 'F8' through 'FF'.
The least significant of the eight 4-bit values in each
Word represents an FC-4 Type with 000 as its 3 least
significant bits, and most significant 4-bit value in
each Word represents an FC-4 Type with 111 as its 3 least
significant bits."
REFERENCE
"ANSI INCITS 387-2004, Fibre Channel - Generic
Services-4 (FC-GS-4), section 5.2.3.15."
DEFVAL {''H}
```

**Classification:** MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 4438](https://www.rfc-editor.org/rfc/rfc4438.html).

### 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.