ENTERASYS-POLICY-PROFILE-MIB :: etsysPolicyRFC3580MapResolveReponseConflict

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ENTERASYS-POLICY-PROFILE-MIB › etsysPolicyRFC3580MapResolveReponseConflict

etsysPolicyRFC3580MapResolveReponseConflict

Module: ENTERASYS-POLICY-PROFILE-MIB

OID (symbolic): ENTERASYS-POLICY-PROFILE-MIB::etsysPolicyRFC3580MapResolveReponseConflict

OID (numeric): 1.3.6.1.4.1.5624.1.2.6.12.1

Node type: OBJECT-TYPE

Type: PolicyRFC3580MapRadiusResponseTC

Access: read-write

Description: Indicates which field to use in the application of the RADIUS response in the event that both the proprietary filter-id indicating a policy profile and the standard (RFC3580) vlan- tunnel-attribute are present. If policyProfile(1) is selected, then the filter-id will be used, if vlanTunnelAttribute(2) is selected, then the vlan-tunnel-attribute will be used (and the policy-map will be applied, if present). A value of vlanTunnelAttributeWithPolicyProfile(3) indicates that both attributes should be applied, in the following manner: the policyProfile should be enforced, with the exception of the etsysPolicyProfilePortVid (if present), the returned vlan-tunnel-attribute will be used in its place. In this case, the policy-map will be ignored (as the policyProfile was explicitly assigned). VLAN classification rules will still be applied, as defined by the assigned policyProfile.

Modifications of this value will not effect the current status of any users currently authenticated. The new state will be applied to new, successful authentications. The current status of current authentication may be modified through the individual agents or through the ENTERASYS-MULTI-AUTH-MIB, if supported.

What is etsysPolicyRFC3580MapResolveReponseConflict?

Chooses which RADIUS attribute wins when both a proprietary policy-profile filter-id and a standard RFC 3580 VLAN tunnel attribute are returned for the same authentication, including a combined mode that applies the profile but lets the tunnel VLAN override just its PVID.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.6.12.1
snmpwalk -v2c -c public <target> ENTERASYS-POLICY-PROFILE-MIB::etsysPolicyRFC3580MapResolveReponseConflict

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.6.12.1.1
snmpget -v2c -c public <target> ENTERASYS-POLICY-PROFILE-MIB::etsysPolicyRFC3580MapResolveReponseConflict.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.5624.1.2.6.12.1.1 s <value>

Start monitoring Enterasys Networks switch (legacy, later Extreme Networks)/access edge device (per-user policy profiles) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ENTERASYS-POLICY-PROFILE-MIB::etsysPolicyRFC3580MapResolveReponseConflict OID value, configure state conditions and alerts, and monitor any Enterasys Networks switch (legacy, later Extreme Networks)/access edge device (per-user policy profiles) from a single console.

OID Breakdown

Upper-level ancestors (9 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.5624enterasysENTERASYS-MIB-NAMES
1.3.6.1.4.1.5624.1etsysMibsENTERASYS-MIB-NAMES
1.3.6.1.4.1.5624.1.2etsysModulesENTERASYS-MIB-NAMES
Numeric OIDNameModule
1.3.6.1.4.1.5624.1.2.6etsysPolicyProfileMIBENTERASYS-POLICY-PROFILE-MIB
1.3.6.1.4.1.5624.1.2.6.12etsysPolicyRFC3580MapENTERASYS-POLICY-PROFILE-MIB
1.3.6.1.4.1.5624.1.2.6.12.1etsysPolicyRFC3580MapResolveReponseConflictENTERASYS-POLICY-PROFILE-MIB