---
oid: "1.3.6.1.4.1.2158.2.5.1.3.1.6"
short-description: "salixAtmfM4PlugInUnitRedundancyConfig OBJECT-TYPE"
last-modified: "2018-06-18"
parent-oid: "1.3.6.1.4.1.2158.2.5.1.3.1"
---

## OID: `1.3.6.1.4.1.2158.2.5.1.3.1.6`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2158 salixGeneric(2) salixM4MIB(5) salixM4MIBObjects(1) salixAtmfM4PlugInUnitTable(3) salixAtmfM4PlugInUnitEntry(1) salixAtmfM4PlugInUnitRedundancyConfig(6)}
```

### Description

```asn1
salixAtmfM4PlugInUnitRedundancyConfig OBJECT-TYPE
SYNTAX INTEGER { working(1),
protect(2),
none(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When retrieved, this attribute represents the current
redundancy configuration of the specified Plug-In Unit. A value
of 'none' indicates that the specified Plug-In Unit has no
redundant module. A status of either 'working' or 'protect'
indicates that the specified Plug-In Unit is either the
working or protect Plug-In Unit in a redundancy relationship.

When used with the 'salixAtmfM4PlugInUnitRedundancyPartnerModule'
attribute of the 'salixAtfM4PlugInUnitTable', it can be
determined which Plug-In Units are in redudancy relationship
and also the plug-in units role in that relationship (if
they are in a relationship at all).

In addition to using these attributes to get information on
redundant modules, these attributes can also be used to
create redundancy relationships. By setting the
'salixAtmfM4PlugInUnitRedundancyPartnerModule' to a valid PhysicalIndex
and also setting the 'salixAtmfM4PlugInUnitRedundancyConfig' on either of
the plug-in units to 'working' or 'protect' (as the desired
configuration for that plug-in unit), a redundancy pair is
created. Redundancy relationships can be destroyed by
setting the 'salixAtmfM4PlugInUnitRedundancyConfig' of either of the
modules to 'none'.

If a new value of either 'working' or 'protect' is written
to the 'salixAtmfM4PlugInUnitRedundancyConfig' attribute, a switchover
occurs in the system (i.e. the 'working' becomes the
'protect' while the 'protect' becomes the 'working).

NOTE: It is only necessary to set the information on one of
the plug-in unit entries. The information will be
automatically set in the other entry by the system."
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.