---
oid: "1.3.6.1.4.1.6486.801.1.2.1.14.1.1.4.1.8"
short-description: "directoryServerCacheChange OBJECT-TYPE"
last-modified: "2022-03-24"
parent-oid: "1.3.6.1.4.1.6486.801.1.2.1.14.1.1.4.1"
---

## OID: `1.3.6.1.4.1.6486.801.1.2.1.14.1.1.4.1.8`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 6486 alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Software(2) softwareIND1Entities(1) softentIND1Policy(14) alcatelENT1PolicyMIB(1) alcatelIND1PolicyMIBObjects(1) directoryServerTable(4) directoryServerEntry(1) directoryServerCacheChange(8)}
```

### Description

```asn1
directoryServerCacheChange OBJECT-TYPE
SYNTAX INTEGER {none(0), recachePolicy(1) -- ,
\-- recacheAll(2)}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows an NMS application to influence the policy
manager's cache of policy-related data when this server becomes
the primary LDAP server selected for the switch. Setting this object
to recachePolicy(1) conveys to the policy manager that the
policy class object should be obtained from the LDAP server
represented by this table entry when this server becomes the
primary LDAP server. By setting this object to 'none', the
policy manager will use the existing policy and policy rule
cache rather than reloading the policy data from this server.
In the case where there is no policy cache (for instance, when
the switch powers up) the policy manager will attempt to reload
the policy class cache even if this object is set to 'none'."
DEFVAL {none}
```

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