The password (community name) that you want this SNMP agent to use to secure SNMPv1 or v2 communication with SNMP managers. Requires you to enable community based access for this agent. SNMPv3 does not use community names. Instead, it encrypts user names and passwords in its PDUs. When you use SNMPv1 or v2, there are two community names that are needed when the WebLogic SNMP agent and SNMP managers interact: The name that you specify in this community prefix. All SNMP managers must send this name when connecting to this SNMP agent. The community name that the SNMP manager defines. The SNMP agent must send this name when connecting to the manager. (You supply this community name when you configure a trap destination.) In addition to using the community prefix as a password, an SNMP agent on an Administration Server uses the prefix to qualify requests from SNMP managers. Because the Administration Server can access data for all WebLogic Server instances in a domain, a request that specifies only an attribute name is potentially ambiguous. For example, the attribute serverUptime exists for each WebLogic Server instance in a domain. To clarify requests that you send to SNMP agents on Administration Servers, use the community prefix as follows: To request the value of an attribute on a specific Managed Server, when you send a request from an SNMP manager, append the name of the server instance to the community prefix: community_prefix@server_name. To request the value of an attribute for all server instances in a domain, send a community name with the following form: community_prefix To secure access to the values of the WebLogic attributes when using the SNMPv1 or v2 protocols, it is recommended that you set community prefix to a value other than public. You cannot specify a null (empty) value for the community prefix. If you delete the prefix value, WebLogic Server resets the value to public. If you do not want this agent to receive SNMPv1 or v2 requests, instead of trying to set the community prefix to a null value, disable community based access. With community based access disabled, WebLogic Server ignores the community prefix value.
Parsed from file BEA-WEBLOGIC-MIB.mib.txt
Company: None
Module: BEA-WEBLOGIC-MIB
The password (community name) that you want this SNMP agent to use to secure SNMPv1 or v2 communication with SNMP managers. Requires you to enable community based access for this agent. SNMPv3 does not use community names. Instead, it encrypts user names and passwords in its PDUs. When you use SNMPv1 or v2, there are two community names that are needed when the WebLogic SNMP agent and SNMP managers interact: The name that you specify in this community prefix. All SNMP managers must send this name when connecting to this SNMP agent. The community name that the SNMP manager defines. The SNMP agent must send this name when connecting to the manager. (You supply this community name when you configure a trap destination.) In addition to using the community prefix as a password, an SNMP agent on an Administration Server uses the prefix to qualify requests from SNMP managers. Because the Administration Server can access data for all WebLogic Server instances in a domain, a request that specifies only an attribute name is potentially ambiguous. For example, the attribute serverUptime exists for each WebLogic Server instance in a domain. To clarify requests that you send to SNMP agents on Administration Servers, use the community prefix as follows: To request the value of an attribute on a specific Managed Server, when you send a request from an SNMP manager, append the name of the server instance to the community prefix: community_prefix@server_name. To request the value of an attribute for all server instances in a domain, send a community name with the following form: community_prefix To secure access to the values of the WebLogic attributes when using the SNMPv1 or v2 protocols, it is recommended that you set community prefix to a value other than public. You cannot specify a null (empty) value for the community prefix. If you delete the prefix value, WebLogic Server resets the value to public. If you do not want this agent to receive SNMPv1 or v2 requests, instead of trying to set the community prefix to a null value, disable community based access. With community based access disabled, WebLogic Server ignores the community prefix value.
Parsed from file BEA-WEBLOGIC-MIB.mib
Module: BEA-WEBLOGIC-MIB
Vendor: Independence Technologies, Inc.(ITI)
Module: BEA-WEBLOGIC-MIB
[Automatically extracted from oidview.com]
wlssnmpAgentDeploymentCommunityPrefix OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The password (community name) that you want this SNMP agent to use to secure SNMPv1 or v2 communication with SNMP managers. Requires you to enable community based access for this agent. SNMPv3 does not use community names. Instead, it encrypts user names and passwords in its PDUs. When you use SNMPv1 or v2, there are two community names that are needed when the WebLogic SNMP agent and SNMP managers interact: The name that you specify in this community prefix. All SNMP managers must send this name when connecting to this SNMP agent. The community name that the SNMP manager defines. The SNMP agent must send this name when connecting to the manager. (You supply this community name when you configure a trap destination.) In addition to using the community prefix as a password, an SNMP agent on an Administration Server uses the prefix to qualify requests from SNMP managers. Because the Administration Server can access data for all WebLogic Server instances in a domain, a request that specifies only an attribute name is potentially ambiguous. For example, the attribute serverUptime exists for each WebLogic Server instance in a domain. To clarify requests that you send to SNMP agents on Administration Servers, use the community prefix as follows: To request the value of an attribute on a specific Managed Server, when you send a request from an SNMP manager, append the name of the server instance to the community prefix: community_prefix@server_name. To request the value of an attribute for all server instances in a domain, send a community name with the following form: community_prefix To secure access to the values of the WebLogic attributes when using the SNMPv1 or v2 protocols, it is recommended that you set community prefix to a value other than public. You cannot specify a null (empty) value for the community prefix. If you delete the prefix value, WebLogic Server resets the value to public. If you do not want this agent to receive SNMPv1 or v2 requests, instead of trying to set the community prefix to a null value, disable community based access. With community based access disabled, WebLogic Server ignores the community prefix value." ::= { wlssnmpAgentDeploymentEntry 4 }
wlssnmpAgentDeploymentCommunityPrefix OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The password (community name) that you want this SNMP agent to use to secure SNMPv1 or v2 communication with SNMP managers. Requires you to enable community based access for this agent. SNMPv3 does not use community names. Instead, it encrypts user names and passwords in its PDUs. When you use SNMPv1 or v2, there are two community names that are needed when the WebLogic SNMP agent and SNMP managers interact: The name that you specify in this community prefix. All SNMP managers must send this name when connecting to this SNMP agent. The community name that the SNMP manager defines. The SNMP agent must send this name when connecting to the manager. (You supply this community name when you configure a trap destination.) In addition to using the community prefix as a password, an SNMP agent on an Administration Server uses the prefix to qualify requests from SNMP managers. Because the Administration Server can access data for all WebLogic Server instances in a domain, a request that specifies only an attribute name is potentially ambiguous. For example, the attribute serverUptime exists for each WebLogic Server instance in a domain. To clarify requests that you send to SNMP agents on Administration Servers, use the community prefix as follows: To request the value of an attribute on a specific Managed Server, when you send a request from an SNMP manager, append the name of the server instance to the community prefix: community_prefix@server_name. To request the value of an attribute for all server instances in a domain, send a community name with the following form: community_prefix To secure access to the values of the WebLogic attributes when using the SNMPv1 or v2 protocols, it is recommended that you set community prefix to a value other than public. You cannot specify a null (empty) value for the community prefix. If you delete the prefix value, WebLogic Server resets the value to public. If you do not want this agent to receive SNMPv1 or v2 requests, instead of trying to set the community prefix to a null value, disable community based access. With community based access disabled, WebLogic Server ignores the community prefix value." ::= { wlssnmpAgentDeploymentEntry 4 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 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.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.9 | wlssnmpAgentDeploymentLocalizedKeyCacheInvalidationInterval | 0 | 0 | The number of milliseconds after which WebLogic Server invalidates its cache of SNMP security keys. Setting a high value create… |
| 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… |