Reference record for OID 1.3.6.1.4.1.140.625.1040.1.9


parent
1.3.6.1.4.1.140.625.1040.1 (wlssnmpAgentDeploymentEntry)
node code
9
node name
wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval
dot oid
1.3.6.1.4.1.140.625.1040.1.9
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bea(140) wls(625) wlssnmpAgentDeploymentTable(1040) wlssnmpAgentDeploymentEntry(1) wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bea(140) wls(625) wlssnmpAgentDeploymentTable(1040) wlssnmpAgentDeploymentEntry(1) wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bea(140) wls(625) wlssnmpAgentDeploymentTable(1040) wlssnmpAgentDeploymentEntry(1) wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bea(140) wls(625) wlssnmpAgentDeploymentTable(1040) wlssnmpAgentDeploymentEntry(1) wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bea(140) wls(625) wlssnmpAgentDeploymentTable(1040) wlssnmpAgentDeploymentEntry(1) wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bea(140) wls(625) wlssnmpAgentDeploymentTable(1040) wlssnmpAgentDeploymentEntry(1) wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval(9)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/bea/wls/wlssnmpAgentDeploymentTable/wlssnmpAgentDeploymentEntry/wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval
  • /iso/identified-organization/dod/internet/private/enterprises/bea/wls/wlssnmpAgentDeploymentTable/wlssnmpAgentDeploymentEntry/wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval
  • /iso/org/dod/internet/private/enterprise/bea/wls/wlssnmpAgentDeploymentTable/wlssnmpAgentDeploymentEntry/wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval
  • /iso/org/dod/internet/private/enterprises/bea/wls/wlssnmpAgentDeploymentTable/wlssnmpAgentDeploymentEntry/wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval
  • /iso/iso-identified-organization/dod/internet/private/enterprise/bea/wls/wlssnmpAgentDeploymentTable/wlssnmpAgentDeploymentEntry/wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval
  • /iso/iso-identified-organization/dod/internet/private/enterprises/bea/wls/wlssnmpAgentDeploymentTable/wlssnmpAgentDeploymentEntry/wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/140/625/1040/1/9

    Description by mibdepot

    The number of milliseconds after which WebLogic Server invalidates its cache of SNMP security keys. Setting a high value creates a risk that users whose credentials have been removed can still access SNMP data. An SNMP security key is an encrypted version of an SNMP agent's engine ID and an authentication password or privacy password. WebLogic Server generates one security key for each entry that you create in the SNMP credential map. When a WebLogic Server SNMP agent receives an SNMPv3 request, it compares the key that is in the request with its WebLogic Server keys. If it finds a match, it processes the request. The SNMP agent also encodes these keys in its responses and notifications. (You configure which keys are encoded when you create a trap destination.) Instead of regenerating the keys for each SNMPv3 communication, WebLogic Server caches the keys. To make sure that the cache contains the latest set of SNMP credentials, WebLogic Server periodically invalidates the cache. After the cache is invalidated, the next time an SNMP agent requests credentials, WebLogic Server regenerates the cache. Note that making a change to the credential map does not automatically update the cache. Instead, the cache is updated only after it has been invalidated. For example, if you update a privacy password in an existing entry in the SNMP credential map, the SNMP agent is not aware of the new password until the key cache is invalidated and regenerated. An SNMP user with the old security password can still access WebLogic Server data until the cache is invalidated. You can invalidate a key immediately instead of waiting for this invalidation interval to expire.

    Parsed from file BEA-WEBLOGIC-MIB.mib.txt
    Company: None
    Module: BEA-WEBLOGIC-MIB

    Description by circitor

    The number of milliseconds after which WebLogic Server invalidates its cache of SNMP security keys. Setting a high value creates a risk that users whose credentials have been removed can still access SNMP data. An SNMP security key is an encrypted version of an SNMP agent's engine ID and an authentication password or privacy password. WebLogic Server generates one security key for each entry that you create in the SNMP credential map. When a WebLogic Server SNMP agent receives an SNMPv3 request, it compares the key that is in the request with its WebLogic Server keys. If it finds a match, it processes the request. The SNMP agent also encodes these keys in its responses and notifications. (You configure which keys are encoded when you create a trap destination.) Instead of regenerating the keys for each SNMPv3 communication, WebLogic Server caches the keys. To make sure that the cache contains the latest set of SNMP credentials, WebLogic Server periodically invalidates the cache. After the cache is invalidated, the next time an SNMP agent requests credentials, WebLogic Server regenerates the cache. Note that making a change to the credential map does not automatically update the cache. Instead, the cache is updated only after it has been invalidated. For example, if you update a privacy password in an existing entry in the SNMP credential map, the SNMP agent is not aware of the new password until the key cache is invalidated and regenerated. An SNMP user with the old security password can still access WebLogic Server data until the cache is invalidated. You can invalidate a key immediately instead of waiting for this invalidation interval to expire.

    Parsed from file BEA-WEBLOGIC-MIB.mib
    Module: BEA-WEBLOGIC-MIB

    Information by oid_info

    Vendor: Independence Technologies, Inc.(ITI)
    Module: BEA-WEBLOGIC-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of milliseconds after which WebLogic Server invalidates its cache of SNMP security keys. Setting a high value creates a risk that users whose credentials have been removed can still access SNMP data. An SNMP security key is an encrypted version of an SNMP agent's engine ID and an authentication password or privacy password. WebLogic Server generates one security key for each entry that you create in the SNMP credential map. When a WebLogic Server SNMP agent receives an SNMPv3 request, it compares the key that is in the request with its WebLogic Server keys. If it finds a match, it processes the request. The SNMP agent also encodes these keys in its responses and notifications. (You configure which keys are encoded when you create a trap destination.) Instead of regenerating the keys for each SNMPv3 communication, WebLogic Server caches the keys. To make sure that the cache contains the latest set of SNMP credentials, WebLogic Server periodically invalidates the cache. After the cache is invalidated, the next time an SNMP agent requests credentials, WebLogic Server regenerates the cache. Note that making a change to the credential map does not automatically update the cache. Instead, the cache is updated only after it has been invalidated. For example, if you update a privacy password in an existing entry in the SNMP credential map, the SNMP agent is not aware of the new password until the key cache is invalidated and regenerated. An SNMP user with the old security password can still access WebLogic Server data until the cache is invalidated. You can invalidate a key immediately instead of waiting for this invalidation interval to expire." ::= { wlssnmpAgentDeploymentEntry 9 }

    Information by circitor

    wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of milliseconds after which WebLogic Server invalidates its cache of SNMP security keys. Setting a high value creates a risk that users whose credentials have been removed can still access SNMP data. An SNMP security key is an encrypted version of an SNMP agent's engine ID and an authentication password or privacy password. WebLogic Server generates one security key for each entry that you create in the SNMP credential map. When a WebLogic Server SNMP agent receives an SNMPv3 request, it compares the key that is in the request with its WebLogic Server keys. If it finds a match, it processes the request. The SNMP agent also encodes these keys in its responses and notifications. (You configure which keys are encoded when you create a trap destination.) Instead of regenerating the keys for each SNMPv3 communication, WebLogic Server caches the keys. To make sure that the cache contains the latest set of SNMP credentials, WebLogic Server periodically invalidates the cache. After the cache is invalidated, the next time an SNMP agent requests credentials, WebLogic Server regenerates the cache. Note that making a change to the credential map does not automatically update the cache. Instead, the cache is updated only after it has been invalidated. For example, if you update a privacy password in an existing entry in the SNMP credential map, the SNMP agent is not aware of the new password until the key cache is invalidated and regenerated. An SNMP user with the old security password can still access WebLogic Server data until the cache is invalidated. You can invalidate a key immediately instead of waiting for this invalidation interval to expire." ::= { wlssnmpAgentDeploymentEntry 9 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.140)

    Berthet Gerard

    Brothers (19)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.140.625.1040.1.1 wlssnmpAgentDeploymentIndex 0 0 Index column
    1.3.6.1.4.1.140.625.1040.1.2 wlssnmpAgentDeploymentObjectName 0 0 ObjectName column
    1.3.6.1.4.1.140.625.1040.1.3 wlssnmpAgentDeploymentType 0 0 Returns the type of the MBean.
    1.3.6.1.4.1.140.625.1040.1.4 wlssnmpAgentDeploymentCommunityPrefix 0 0 The password (community name) that you want this SNMP agent to use to secure SNMPv1 or v2 communication with SNMP managers. Req…
    1.3.6.1.4.1.140.625.1040.1.5 wlssnmpAgentDeploymentAuthenticationProtocol 0 0 The protocol that this SNMP agent uses to ensure that only authorized users can request or receive information about your WebLo…
    1.3.6.1.4.1.140.625.1040.1.6 wlssnmpAgentDeploymentSNMPPort 0 0 The port on which you want this SNMP agent to listen for incoming requests from SNMP managers that use the UDP protocol. SNMP …
    1.3.6.1.4.1.140.625.1040.1.7 wlssnmpAgentDeploymentSNMPEngineId 0 0 An identifier for this SNMP agent that is unique amongst all other SNMP agents in the current WebLogic Server domain. If you us…
    1.3.6.1.4.1.140.625.1040.1.8 wlssnmpAgentDeploymentSNMPAccessForUserMBeansEnabled 0 0 Configures this SNMP agent to provide read-only access to MBean types that you have created and registered (custom MBeans). If …
    1.3.6.1.4.1.140.625.1040.1.10 wlssnmpAgentDeploymentEnabled 0 0 Specifies whether this SNMP agent is enabled.
    1.3.6.1.4.1.140.625.1040.1.11 wlssnmpAgentDeploymentName 0 0 The user-specified name of this MBean instance. This name is included as one of the key properties in the MBean's javax.manage…
    1.3.6.1.4.1.140.625.1040.1.12 wlssnmpAgentDeploymentInformEnabled 0 0 Configures this SNMP agent to send notifications as an INFORM instead of a TRAP. Requires you to specify the agent's SNMPTrapVe…
    1.3.6.1.4.1.140.625.1040.1.13 wlssnmpAgentDeploymentSendAutomaticTrapsEnabled 0 0 Specifies whether this SNMP agent sends automatically generated notifications to SNMP managers. The SNMP agent generates autom…
    1.3.6.1.4.1.140.625.1040.1.14 wlssnmpAgentDeploymentInformRetryInterval 0 0 The number of milliseconds that this SNMP agent will wait for a response to an INFORM notification. If the agent does not recei…
    1.3.6.1.4.1.140.625.1040.1.15 wlssnmpAgentDeploymentDeploymentOrder 0 0 A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the…
    1.3.6.1.4.1.140.625.1040.1.16 wlssnmpAgentDeploymentPrivacyProtocol 0 0 The protocol that this SNMP agent uses to encrypt and unencrypt messages. Applicable only with SNMPv3. Requires you to also use…
    1.3.6.1.4.1.140.625.1040.1.17 wlssnmpAgentDeploymentMasterAgentXPort 0 0 The port that this SNMP agent uses to communicate with its subagents. The agent uses subagents to provide access to custom MBea…
    1.3.6.1.4.1.140.625.1040.1.18 wlssnmpAgentDeploymentSNMPTrapVersion 0 0 The SNMP notification version that this SNMP agent generates.
    1.3.6.1.4.1.140.625.1040.1.19 wlssnmpAgentDeploymentMaxInformRetryCount 0 0 The maximum number of times that this SNMP agent will resend INFORM notifications for which it has not received a response.
    1.3.6.1.4.1.140.625.1040.1.20 wlssnmpAgentDeploymentCommunityBasedAccessEnabled 0 0 Specifies whether this SNMP agent supports SNMPv1 and v2. SNMPv1 and v2 use community strings for authentication. If you disabl…