---
oid: "1.3.6.1.4.1.9070.1.2.5.7.1.3.3.1.1"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 9070 symmNetworkManagement(1) symmSnmpManagement(2) symmCommonModelV1(5) symmDeviceDependent(7) tp5000e(1) tp5000eGlobalConfig(3) tp5000eRedundTable(3) tp5000eRedundEntry(1) tp5000eRedundModuleID(1)}"
description: "tp5000eRedundModuleID OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2023-05-02"
---

## OID : `1.3.6.1.4.1.9070.1.2.5.7.1.3.3.1.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 9070 symmNetworkManagement(1) symmSnmpManagement(2) symmCommonModelV1(5) symmDeviceDependent(7) tp5000e(1) tp5000eGlobalConfig(3) tp5000eRedundTable(3) tp5000eRedundEntry(1) tp5000eRedundModuleID(1)}
```

### Description

```asn1
tp5000eRedundModuleID OBJECT-TYPE
SYNTAX TP5000MODULEID
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The module ID can be either IOC1 or IOC2.
The system is currently hardcoded for card redundancy
(if two IOC cards are present, they are always configured as a
redundancy pair, with one active and one on standby). Whichever module ID
is used to access this table, the configuration will apply to both IOC cards.
In the future when the two IOC cards can be independent, configuration will
only apply to the current IOC module."
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

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