---
oid: "1.3.6.1.2.1.160.1.1.14.1"
short-description: "t11ZsNotifyControlEntry OBJECT-TYPE"
last-modified: "2019-03-22"
parent-oid: "1.3.6.1.2.1.160.1.1.14"
---

## OID: `1.3.6.1.2.1.160.1.1.14.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) t11ZoneServerMIB(160) t11ZsMIBObjects(1) t11ZsConfiguration(1) t11ZsNotifyControlTable(14) t11ZsNotifyControlEntry(1)}
```

### Description

```asn1
t11ZsNotifyControlEntry OBJECT-TYPE
SYNTAX T11ZsNotifyControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry contains notification control information
specific to a Zone Server for a particular Fabric
(identified by the value of t11ZsServerFabricIndex)
on a particular switch (identified by values of
fcmInstanceIndex and fcmSwitchIndex).
The persistence across reboots of writable values in
a row of this table is specified by the instance of
t11ZsServerDatabaseStorageType that is INDEXed by
the same values of fcmInstanceIndex, fcmSwitchIndex,
and t11ZsServerFabricIndex."
INDEX { fcmInstanceIndex, fcmSwitchIndex,
t11ZsServerFabricIndex }
```

**Classification:** MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 4936](http://tools.ietf.org/html/rfc4936).

### Child OIDs

- `1.3.6.1.2.1.160.1.1.14.1.1`: `t11ZsNotifyRequestRejectEnable(1)`
- `1.3.6.1.2.1.160.1.1.14.1.2`: `t11ZsNotifyMergeFailureEnable(2)`
- `1.3.6.1.2.1.160.1.1.14.1.3`: `t11ZsNotifyMergeSuccessEnable(3)`
- `1.3.6.1.2.1.160.1.1.14.1.4`: `t11ZsNotifyDefZoneChangeEnable(4)`
- `1.3.6.1.2.1.160.1.1.14.1.5`: `t11ZsNotifyActivateEnable(5)`
- `1.3.6.1.2.1.160.1.1.14.1.6`: `t11ZsRejectCtCommandString(6)`
- `1.3.6.1.2.1.160.1.1.14.1.7`: `t11ZsRejectRequestSource(7)`
- `1.3.6.1.2.1.160.1.1.14.1.8`: `t11ZsRejectReasonCode(8)`
- `1.3.6.1.2.1.160.1.1.14.1.9`: `t11ZsRejectReasonCodeExp(9)`
- `1.3.6.1.2.1.160.1.1.14.1.10`: `t11ZsRejectReasonVendorCode(10)`

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