BEA-WEBLOGIC-MIB :: wlssnmpAgentDeploymentSNMPPort

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBEA-WEBLOGIC-MIBwlssnmpAgentDeploymentSNMPPort

wlssnmpAgentDeploymentSNMPPort

Module: BEA-WEBLOGIC-MIB

OID (symbolic): BEA-WEBLOGIC-MIB::wlssnmpAgentDeploymentSNMPPort

OID (numeric): 1.3.6.1.4.1.140.625.1040.1.6

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

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.

What is wlssnmpAgentDeploymentSNMPPort?

This OID defines the UDP port on which the WebLogic SNMP agent listens for incoming queries. Example: setting to 161 (the standard) makes the agent listen on UDP port 161 for SNMP requests.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.140.625.1040.1.6
snmpwalk -v2c -c public <target> BEA-WEBLOGIC-MIB::wlssnmpAgentDeploymentSNMPPort

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.140.625.1040.1.6.1
snmpget -v2c -c public <target> BEA-WEBLOGIC-MIB::wlssnmpAgentDeploymentSNMPPort.1

Start monitoring BEA/Oracle WebLogic Server (Java EE application server) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BEA-WEBLOGIC-MIB::wlssnmpAgentDeploymentSNMPPort OID value, configure state conditions and alerts, and monitor any BEA/Oracle WebLogic Server (Java EE application server) from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.140beaBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625wlsBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.1040wlssnmpAgentDeploymentTableBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.1040.1wlssnmpAgentDeploymentEntryBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.1040.1.6wlssnmpAgentDeploymentSNMPPortBEA-WEBLOGIC-MIB