HP-ICF-USER-PROFILE-MIB :: hpicfUsrProfileConfigConflictResolveMaxEgressBandwidth

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HP-ICF-USER-PROFILE-MIB › hpicfUsrProfileConfigConflictResolveMaxEgressBandwidth

hpicfUsrProfileConfigConflictResolveMaxEgressBandwidth

Module: HP-ICF-USER-PROFILE-MIB

OID (symbolic): HP-ICF-USER-PROFILE-MIB::hpicfUsrProfileConfigConflictResolveMaxEgressBandwidth

OID (numeric): 1.3.6.1.4.1.11.2.14.11.1.12.1.1.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This object controls how a device behaves when egress BW conflicts arise. A conflict can arise if a device only supports the egress BW access primitive on a per-port basis, but device is being configured with profiles that have per-user unique setting. Applying these profiles to the same port will cause the conflict to arise because the device cannot enforce a per-user egress BW setting. This object specifies two alternatives, as follows:

'non-strict' - Device does not signal errors when multiple access profiles are applied to a port. The device will apply the egress BW settings specified in the last profile applied to the port.

'strict' - Device does signal an error when an attempt to apply an access profile to a port that already has an active access profile with a different egress BW setting. Device will not activate the access profile in question after error is signaled.

What is hpicfUsrProfileConfigConflictResolveMaxEgressBandwidth?

A read-write switch (default non-strict(0)) controlling how the device handles an egress-bandwidth conflict when it only supports per-port enforcement but per-user profiles disagree on the same port: non-strict(0) silently applies whichever profile was applied last, while strict(1) rejects the conflicting profile and signals an error. Admins choose strict(1) when they'd rather see an explicit failure than have an egress bandwidth cap silently overridden on a shared port.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11.2.14.11.1.12.1.1.7
snmpwalk -v2c -c public <target> HP-ICF-USER-PROFILE-MIB::hpicfUsrProfileConfigConflictResolveMaxEgressBandwidth

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11.2.14.11.1.12.1.1.7.1
snmpget -v2c -c public <target> HP-ICF-USER-PROFILE-MIB::hpicfUsrProfileConfigConflictResolveMaxEgressBandwidth.1

Set instance 1 (SNMPv2c):

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

Start monitoring HP ProCurve switch (802.1X user access-profile assignment) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HP-ICF-USER-PROFILE-MIB::hpicfUsrProfileConfigConflictResolveMaxEgressBandwidth OID value, configure state conditions and alerts, and monitor any HP ProCurve switch (802.1X user access-profile assignment) from a single console.

OID Breakdown

Upper-level ancestors (12 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.11hpCLJ8500-MIB
1.3.6.1.4.1.11.2nmCLJ8500-MIB
1.3.6.1.4.1.11.2.14icfCONFIG-MIB
1.3.6.1.4.1.11.2.14.11hpicfObjectsCONFIG-MIB
1.3.6.1.4.1.11.2.14.11.1hpicfCommonHP-ICF
1.3.6.1.4.1.11.2.14.11.1.12hpicfCommonSecurityHP-ICF-OID
Numeric OIDNameModule
1.3.6.1.4.1.11.2.14.11.1.12.1hpicfUsrProfileMIBHP-ICF-USER-PROFILE-MIB
1.3.6.1.4.1.11.2.14.11.1.12.1.1hpicfUsrProfileConfigHP-ICF-USER-PROFILE-MIB
1.3.6.1.4.1.11.2.14.11.1.12.1.1.7hpicfUsrProfileConfigConflictResolveMaxEgressBandwidthHP-ICF-USER-PROFILE-MIB