SYNOPTICS-BASIC-ETHTOK-MIB :: s3EnetConcSecureStatus

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SYNOPTICS-BASIC-ETHTOK-MIB › s3EnetConcSecureStatus

s3EnetConcSecureStatus

Module: SYNOPTICS-BASIC-ETHTOK-MIB

OID (symbolic): SYNOPTICS-BASIC-ETHTOK-MIB::s3EnetConcSecureStatus

OID (numeric): 1.3.6.1.4.1.45.1.3.2.1.13

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This s3EnetConcSecureStatus object indicates whether the security features (both allowed nodes and LattisSecure) for the concentrator are active or inactive. If security is active, this object also indicates whether the allowed nodes feature is controlled at the concentrator, board, or port level. LattisSecure features are always controlled at the port level. (See the Authorized Nodes tables for more information about how the allowed nodes and LattisSecure receive security features are configured.)

If this object is set to concSecureOn(2), then the allowed nodes feature is controlled at the concentrator level and activated for every non-LattisSecure Ethernet port in the concentrator. If an authorized node violation occurs on any port, the action specified in s3EnetConcAuthAction is taken.

If this object is set to portCheckOn(3), then allowed nodes is controlled at the port level by the s3EnetPortSecureStatus object for that port. The port's s3EnetPortAuthAction determines the action taken when authorized nodes violations occur on that port.

If this object is set to slotCheckOn(4), then allowed nodes is controlled at the board level by the s3EnetBoardSecureStatus object for that board. The board's s3EnetBoardAuthAction determines the action taken when authorized nodes violations occur on that board's ports.

If this object is set to concentratorOff(5), then all security features, including LattisSecure, are deactivated for the entire concentrator.

No matter what the status of this object, the board and port level SecureStatus and AuthAction are not lost even if they are not currently being used. Thus, the user can change a port's status even if this object is slotCheckOn(4). If this object is then changed to portCheckOn(3), then the change will take effect.

The agent must support download of this object in the CFG file.

In release 4.0, this object was called s3EnetConcAuthStatus.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.45.1.3.2.1.13
snmpwalk -v2c -c public <target> SYNOPTICS-BASIC-ETHTOK-MIB::s3EnetConcSecureStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.45.1.3.2.1.13.1
snmpget -v2c -c public <target> SYNOPTICS-BASIC-ETHTOK-MIB::s3EnetConcSecureStatus.1

Set instance 1 (SNMPv2c):

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

Start monitoring SynOptics (Bay Networks/Nortel) Ethernet/Token Ring hubs with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SYNOPTICS-BASIC-ETHTOK-MIB::s3EnetConcSecureStatus OID value, configure state conditions and alerts, and monitor any SynOptics (Bay Networks/Nortel) Ethernet/Token Ring hubs from a single console.

OID Breakdown

Upper-level ancestors (7 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
Numeric OIDNameModule
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.1s3000EnetConcentratorSYNOPTICS-BASIC-ETHTOK-MIB
1.3.6.1.4.1.45.1.3.2.1.13s3EnetConcSecureStatusSYNOPTICS-BASIC-ETHTOK-MIB