A3COM-IPSO-R1-MIB :: a3IPsecureLabelSysAuth

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › A3COM-IPSO-R1-MIB › a3IPsecureLabelSysAuth

a3IPsecureLabelSysAuth

Module: A3COM-IPSO-R1-MIB

OID (symbolic): A3COM-IPSO-R1-MIB::a3IPsecureLabelSysAuth

OID (numeric): 1.3.6.1.4.1.43.2.12.3.1.6

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Like a3IPsecureLabelSysLevel, this parameter applies only to packets originated by this system and sent over this port. When such packets are sent, the value of this parameter determines the Protection Authority flag field that is attached to the packet before any processing is done. Note, this is assuming a3IPsecureLabelSysLevel has a value other than none (1).

The individual Protection Authority flags that are included are determined by the individual bits that are set in the value of this object, with the two least significant bytes being of interest. Starting from bit 7 of the INTEGER (with the least significant bit being numbered 0), the mapping of bits to Protection Authority flags is as follows (note: rfc1108 labels the most significant bit '0', the next most significant bit '1', etc),

bit# Prot. Auth. Flag 7 GENSER 6 SIOP 5 SCI 4 NSA 3 DOE

While only bits 7 through 3 have specific Protection Authority flags assigned to them, any 2 byte combination of bits may be set as long as that combination is allowed by rfc1108. The same 1 or 2 byte pattern of bits identified by the value of this object will be placed in the Protection Authority field of received packets with no IP security options present. (note: this is conditioned on a3IPsecureLabelDefaultLevel for this port having a value other than none (1).)

If this object has the value 0, then no Protection Authority field will be added to any received packets, regardless of the value of a3IPsecureLabelDefaultLevel.

What is a3IPsecureLabelSysAuth?

This integer defines Protection Authority flags attached to outbound packets generated by the system. Network administrators use it to mark locally generated traffic with specific authority origins. For instance, setting it marks outbound packets with an authority identifier recognized by downstream systems.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.43.2.12.3.1.6
snmpwalk -v2c -c public <target> A3COM-IPSO-R1-MIB::a3IPsecureLabelSysAuth

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.43.2.12.3.1.6.1
snmpget -v2c -c public <target> A3COM-IPSO-R1-MIB::a3IPsecureLabelSysAuth.1

Set instance 1 (SNMPv2c):

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

Start monitoring Legacy 3Com networking equipment with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the A3COM-IPSO-R1-MIB::a3IPsecureLabelSysAuth OID value, configure state conditions and alerts, and monitor any Legacy 3Com networking equipment from a single console.

OID Breakdown

Upper-level ancestors (8 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.43a3ComA3COM-AUDL-R1-MIB
1.3.6.1.4.1.43.2brouterMIBA3COM-AUDL-R1-MIB
Numeric OIDNameModule
1.3.6.1.4.1.43.2.12a3ComIPSOA3COM-IPSO-R1-MIB
1.3.6.1.4.1.43.2.12.3a3IPsecureParamTableA3COM-IPSO-R1-MIB
1.3.6.1.4.1.43.2.12.3.1a3IPsecureParamEntryA3COM-IPSO-R1-MIB
1.3.6.1.4.1.43.2.12.3.1.6a3IPsecureLabelSysAuthA3COM-IPSO-R1-MIB