Juniper-HTTP-Profile-MIB :: juniHttpProfileSetMap

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › Juniper-HTTP-Profile-MIB › juniHttpProfileSetMap

juniHttpProfileSetMap

Module: Juniper-HTTP-Profile-MIB

OID (symbolic): Juniper-HTTP-Profile-MIB::juniHttpProfileSetMap

OID (numeric): 1.3.6.1.4.1.4874.2.2.79.1.1.1.1.2

Node type: OBJECT-TYPE

Type: JuniSetMap

Access: read-write

Description: A bitmap representing which objects in this entry have been explicitly configured. See the definition of the JuniSetMap TEXTUAL-CONVENTION for details of use.

The INDEX object(s) and this object are excluded from representation (i.e. their bits are never set).

When a SET request does not explicitly configure JuniSetMap, bits in JuniSetMap are set as a side-effect of configuring other profile attributes in the same entry.

If, however, a SET request explicitly configures JuniSetMap, the explicitly configured value overrides 1) any previous bit settings, and 2) any simultaneous 'side-effect' settings that would otherwise occur.

Once set, bits can only be cleared by explicitly configuring JuniSetMap.

What is juniHttpProfileSetMap?

This bitmap value tracks which specific configuration attributes within an HTTP profile entry have been explicitly set by an administrator, as opposed to values that were only set implicitly as a side effect of configuring some other attribute in the same profile, and once a bit is explicitly set it can only be cleared by explicitly reconfiguring this map itself. An administrator generally doesn't set this directly during normal configuration, since it's mainly maintained automatically as a side effect of setting the profile's other attributes, but a management system might read it to determine precisely which fields in a profile were deliberately configured versus left at implicit defaults. For example, after an administrator explicitly sets juniHttpProfileRedirectUrl on a profile, the corresponding bit in this map for that attribute would automatically become set to reflect that it was explicitly configured.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.79.1.1.1.1.2
snmpwalk -v2c -c public <target> Juniper-HTTP-Profile-MIB::juniHttpProfileSetMap

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.79.1.1.1.1.2.1
snmpget -v2c -c public <target> Juniper-HTTP-Profile-MIB::juniHttpProfileSetMap.1

Set instance 1 (SNMPv2c):

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

Start monitoring Juniper E-Series broadband edge router (subscriber HTTP redirect profiles) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Juniper-HTTP-Profile-MIB::juniHttpProfileSetMap OID value, configure state conditions and alerts, and monitor any Juniper E-Series broadband edge router (subscriber HTTP redirect 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.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.2juniperUniMibsJuniper-UNI-SMI
1.3.6.1.4.1.4874.2.2juniMibsJuniper-MIBs
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.79juniHttpProfileMIBJuniper-HTTP-Profile-MIB
1.3.6.1.4.1.4874.2.2.79.1juniHttpProfileObjectsJuniper-HTTP-Profile-MIB
1.3.6.1.4.1.4874.2.2.79.1.1juniHttpProfileJuniper-HTTP-Profile-MIB
1.3.6.1.4.1.4874.2.2.79.1.1.1juniHttpProfileTableJuniper-HTTP-Profile-MIB
1.3.6.1.4.1.4874.2.2.79.1.1.1.1juniHttpProfileEntryJuniper-HTTP-Profile-MIB
1.3.6.1.4.1.4874.2.2.79.1.1.1.1.2juniHttpProfileSetMapJuniper-HTTP-Profile-MIB