The port on which you want this SNMP agent to listen for incoming requests from SNMP managers that use the UDP protocol. SNMP managers can use this port to ping the SNMP agent and request the status of specific attributes. If you target this SNMP agent to multiple server instances, and if two or more servers are running on the same computer, WebLogic Server will automatically increment this UDP port value by 1 for each agent. WebLogic Server never assigns port 162 because it is the default port that an agent uses to send notifications. In addition, if any port is already in use, WebLogic Server skips the port and assigns the next available port. For example, if you use the default value of this attribute and then target this agent to ManagedServer1 and ManagedServer2, and if both servers are running on the same computer, then the agent on ManagedServer1 will listen on UDP port 161 and the agent on ManagedServer2 will listen on UDP port 163. The incremented port number is not persisted in the domain's configuration; when WebLogic Server increments port numbers, it does so in the order in which servers are started on the same computer. If WebLogic Server re-assigns the UDP port for an SNMP agent, look in the agent's SNMPAgentRuntimeMBean to see the agent's runtime UDP port. SNMP agents can also communicate through the host server's TCP listen port (7001 by default) or through a TCP port that is configured by a custom network channel.
Parsed from file BEA-WEBLOGIC-MIB.mib.txt
Company: None
Module: BEA-WEBLOGIC-MIB
The port on which you want this SNMP agent to listen for incoming requests from SNMP managers that use the UDP protocol. SNMP managers can use this port to ping the SNMP agent and request the status of specific attributes. If you target this SNMP agent to multiple server instances, and if two or more servers are running on the same computer, WebLogic Server will automatically increment this UDP port value by 1 for each agent. WebLogic Server never assigns port 162 because it is the default port that an agent uses to send notifications. In addition, if any port is already in use, WebLogic Server skips the port and assigns the next available port. For example, if you use the default value of this attribute and then target this agent to ManagedServer1 and ManagedServer2, and if both servers are running on the same computer, then the agent on ManagedServer1 will listen on UDP port 161 and the agent on ManagedServer2 will listen on UDP port 163. The incremented port number is not persisted in the domain's configuration; when WebLogic Server increments port numbers, it does so in the order in which servers are started on the same computer. If WebLogic Server re-assigns the UDP port for an SNMP agent, look in the agent's SNMPAgentRuntimeMBean to see the agent's runtime UDP port. SNMP agents can also communicate through the host server's TCP listen port (7001 by default) or through a TCP port that is configured by a custom network channel.
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]
wlssnmpAgentDeploymentSNMPPort OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The port on which you want this SNMP agent to listen for incoming requests from SNMP managers that use the UDP protocol. SNMP managers can use this port to ping the SNMP agent and request the status of specific attributes. If you target this SNMP agent to multiple server instances, and if two or more servers are running on the same computer, WebLogic Server will automatically increment this UDP port value by 1 for each agent. WebLogic Server never assigns port 162 because it is the default port that an agent uses to send notifications. In addition, if any port is already in use, WebLogic Server skips the port and assigns the next available port. For example, if you use the default value of this attribute and then target this agent to ManagedServer1 and ManagedServer2, and if both servers are running on the same computer, then the agent on ManagedServer1 will listen on UDP port 161 and the agent on ManagedServer2 will listen on UDP port 163. The incremented port number is not persisted in the domain's configuration; when WebLogic Server increments port numbers, it does so in the order in which servers are started on the same computer. If WebLogic Server re-assigns the UDP port for an SNMP agent, look in the agent's SNMPAgentRuntimeMBean to see the agent's runtime UDP port. SNMP agents can also communicate through the host server's TCP listen port (7001 by default) or through a TCP port that is configured by a custom network channel." ::= { wlssnmpAgentDeploymentEntry 6 }
wlssnmpAgentDeploymentSNMPPort OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The port on which you want this SNMP agent to listen for incoming requests from SNMP managers that use the UDP protocol. SNMP managers can use this port to ping the SNMP agent and request the status of specific attributes. If you target this SNMP agent to multiple server instances, and if two or more servers are running on the same computer, WebLogic Server will automatically increment this UDP port value by 1 for each agent. WebLogic Server never assigns port 162 because it is the default port that an agent uses to send notifications. In addition, if any port is already in use, WebLogic Server skips the port and assigns the next available port. For example, if you use the default value of this attribute and then target this agent to ManagedServer1 and ManagedServer2, and if both servers are running on the same computer, then the agent on ManagedServer1 will listen on UDP port 161 and the agent on ManagedServer2 will listen on UDP port 163. The incremented port number is not persisted in the domain's configuration; when WebLogic Server increments port numbers, it does so in the order in which servers are started on the same computer. If WebLogic Server re-assigns the UDP port for an SNMP agent, look in the agent's SNMPAgentRuntimeMBean to see the agent's runtime UDP port. SNMP agents can also communicate through the host server's TCP listen port (7001 by default) or through a TCP port that is configured by a custom network channel." ::= { wlssnmpAgentDeploymentEntry 6 }
| 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.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.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… |