SYNOPTICS-ETHERNET-MIB :: s3EnetRedPortRedundMode

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SYNOPTICS-ETHERNET-MIB › s3EnetRedPortRedundMode

s3EnetRedPortRedundMode

Module: SYNOPTICS-ETHERNET-MIB

OID (symbolic): SYNOPTICS-ETHERNET-MIB::s3EnetRedPortRedundMode

OID (numeric): 1.3.6.1.4.1.45.1.3.2.3.3.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The redundancy mode of the port.

The possible values read, which report the redundancy mode of the port, are: standalone(1)...the port is not in any redundant pair. hwActive(2).....the port is the active companion in a hardware-redundant pair. hwStandby(3)....the port is the standby companion in a hardware-redundant pair. swActive(4).....the port is the active companion in a software-redundant pair. swStandby(5)....the port is the standby companion in a software-redundant pair.

The values that can be written, which change the redundancy mode, are: standalone(1)...causes the software-redundant pair to be broken up. hwActive(2).....if the previous value was hwStandby(3), this value will cause the port to become the active port in the hardware-redundant pair (i.e., a switchover). hwStandby(3)....if the previous value was hwActive(2), this value will cause the port to become the standby port in the hardware-redundant pair (i.e., a switchover). swActive(4).....if the previous value was swStandby(5), this value will cause the port to become the active port in the software-redundant pair (i.e., a switchover). swStandby(5)....if the previous value was swActive(4), this value will cause the port to become the standby port in the software-redundant pair (i.e., a switchover).

Notes: 1.) The value standalone(1) cannot be written to effect hardware-redundant pairs.

What is s3EnetRedPortRedundMode?

Redundancy role of the port: standAlone(1), hwActive(2), hwStandby(3), swActive(4) or swStandby(5) for hardware- and software-redundant pairs. Writing swapping values (for example hwActive on a hwStandby port) forces a switchover, and writing standAlone(1) breaks up a software-redundant pair; standAlone cannot be written to break hardware pairs.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.45.1.3.2.3.3.1.3
snmpwalk -v2c -c public <target> SYNOPTICS-ETHERNET-MIB::s3EnetRedPortRedundMode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.45.1.3.2.3.3.1.3.1
snmpget -v2c -c public <target> SYNOPTICS-ETHERNET-MIB::s3EnetRedPortRedundMode.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.45.1.3.2.3.3.1.3.1 i <value>

Start monitoring SynOptics Series 3000 Ethernet concentrators/hubs, NMM/NMM+ agents, legacy (hub/board/port status and security) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SYNOPTICS-ETHERNET-MIB::s3EnetRedPortRedundMode OID value, configure state conditions and alerts, and monitor any SynOptics Series 3000 Ethernet concentrators/hubs, NMM/NMM+ agents, legacy (hub/board/port status and security) from a single console.

OID Breakdown

Upper-level ancestors (13 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.45synopticsCMU-MIB
1.3.6.1.4.1.45.1productsSYNOPTICS-BASIC-ETHTOK-MIB
1.3.6.1.4.1.45.1.3series3000SYNOPTICS-BASIC-ETHTOK-MIB
1.3.6.1.4.1.45.1.3.2s3000EthernetSYNOPTICS-BASIC-ETHTOK-MIB
1.3.6.1.4.1.45.1.3.2.3s3000EnetPortSYNOPTICS-BASIC-ETHTOK-MIB
1.3.6.1.4.1.45.1.3.2.3.3s3EnetRedPortTableSYNOPTICS-BASIC-ETHTOK-MIB
1.3.6.1.4.1.45.1.3.2.3.3.1s3EnetRedPortEntrySYNOPTICS-BASIC-ETHTOK-MIB
Numeric OIDNameModule
1.3.6.1.4.1.45.1.3.2.3.3.1.3s3EnetRedPortRedundModeSYNOPTICS-ETHERNET-MIB