|
BEA-320900
|
Error: Agent will be unable to proxy for the agents specified due to Proxy initialization error
|
Description
| The SNMP Agent encountered an exceptional conditional while attempting to initialize the configured SNMPProxy entries.
|
|
Cause
| Refer to exception message for cause of initialization failure.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320901
|
Error: The SNMP Agent has received null SNMP PDU for a provided SNMP request.
|
Description
| An attempt to process a given SNMP request has determined that the requestor has provided a null SNMP PDU. Processing of this request cannot continue.
|
|
Cause
| Invalid SNMP request has been issued.
|
|
Action
| Verify that utilities being used for SNMP requests are valid.
|
|
|
BEA-320902
|
Error: Received SNMP PDU with incorrect community name.
|
Description
| An attempt to process a given SNMP request has determined that the specified community name is invalid. Processing of this request cannot continue.
|
|
Cause
| Invalid community name has been specified on the SNMP request.
|
|
Action
| Correct community name, to be consistent with that specified on the SNMPAgentMBean configuration, and reissue the request.
|
|
|
BEA-320903
|
Error: Failed to handle MBean delete Notification for SNMP Configuration MBean.
|
Description
| SNMP Agent configuration processing was unable to correctly handle the configuration update which requested the deletion of existing SNMP configuration.
|
|
Cause
| Internal processing error while attempting to dynamically modify SNMP configuration.
|
|
Action
| Take appropriate action based upon the specified exception message. This may require a server restart.
|
|
|
BEA-320904
|
Error: Unable to determine SNMP Table vector information for this MIB request for class class.
|
Description
| Processing for the specified MIB request was unable to locate the necessary SNMP table vector class needed to correctly return the requested attribute values.
|
|
Cause
| This is an internal error that could be the result of an invalid MIB entry or missing WebLogic class information.
|
|
Action
| Contact BEA Support.
|
|
|
BEA-320905
|
Error: Unable to return requested table vector information for a particular MBean Type for class class.
|
Description
| Processing for the specified MIB request was unable to locate the correct table vector information for the specified MBean Type.
|
|
Cause
| This is an internal error that could be the result of an invalid MIB entry or missing WebLogic class information.
|
|
Action
| Contact BEA Support.
|
|
|
BEA-320907
|
Error: Unable to determine index value for building the correct return table vector for type MBean Type
|
Description
| Processing for the specified MIB request was unable to determine index value for building the correct return table vector for the specified MBean Type.
|
|
Cause
| This is an internal error that could be the result of an invalid MIB entry or missing WebLogic class information.
|
|
Action
| Contact BEA Support.
|
|
|
BEA-320908
|
Error: Unable to set entries field value due to conversion error
|
Description
| Processing for the specified MIB request was unable to determine convert or support the attributes value.
|
|
Cause
| This is an internal error that could be the result of an invalid MIB entry or mismatch with existing WebLogic MBean information.
|
|
Action
| Contact BEA Support.
|
|
|
BEA-320909
|
Error: Error during initialization while attempting to obtain the required DomainRuntimeServer.
|
Description
| An error has occurred during initialization while attempting to obtain the required DomainRuntimeServer, therefore no MBean information will be available. Initialization of the SNMP Agent is terminated.
|
|
Cause
| This is an internal error.
|
|
Action
| Contact BEA Support.
|
|
|
BEA-320910
|
Error: Error during initialization while attempting to obtain required Admin Server RuntimeServer.
|
Description
| An error has occurred during initialization while attempting to obtain the required Admin Server Server RuntimeServer, therefore no MBean information will be available. Initialization of the SNMP Agent is terminated.
|
|
Cause
| This is an internal error.
|
|
Action
| Contact BEA Support.
|
|
|
BEA-320911
|
Error: Configuration error while initializing the set of configured WebLogic Servers that the SNMP Agent will return information for.
|
Description
| Initialization processing encountered a configuration error while initializing the set of configured WebLogic Servers that the SNMP Agent will return information for. Initialization of the SNMP Agent is terminated.
|
|
Cause
| This could be due to an invalid server configuration entry. Please refer to exception message for more specific cause information.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320912
|
Error: Error during initialization while attempting to obtain MBeanServerConnection.
|
Description
| An error has occurred during initialization while attempting to obtain the required MBeanServer connection, therefore no MBean information will be available. Initialization of the SNMP Agent is terminated.
|
|
Cause
| Please refer to exception message for more specific cause information.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320913
|
Error: Failed to register Attribute Change lisetener mon for MBean type type on server server.
|
Description
| An exception was encountered while attempting to create a JMX AttributeChangeListener for the specified SNMPAttributeChange trap.
|
|
Cause
| This may be due to a misconfigured SNMPAttributeChange entry specification in config.xml. Please refer to exception message for more specific cause information.
|
|
Action
| Modify configuration of the SNMPAttributeChange entry or take appropriate action based upon the specified exception message.
|
|
|
BEA-320914
|
Error: Failed to add MBeanListener for new instances of type type on server server
|
Description
| A exception was encountered while attempting to create a JMXNotificationListener to detect new MBean instances which would match criteria for the defined SNMPAttributeChange trap.
|
|
Cause
| This may be due to a misconfigured SNMPAttributeChange entry specification in config.xml. Please refer to exception message for more specific cause information.
|
|
Action
| Modify configuration of the SNMPAttributeChange entry or take appropriate action based upon the specified exception message.
|
|
|
BEA-320915
|
Error: Failed to send Attribute Change trap for server server for type type for name name
|
Description
| An exception was encountered while trying to construct and send a SNMP trap for a detected Attribute Change action.
|
|
Cause
| Please refer to exception message for more specific cause information.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320916
|
Error: Unable to handle MBeanServer Notification in AttributeChange Monitor mon for new instance
|
Description
| An exception was encountered while attempting to create a new AttributeChange JMX Monitor for the new instance.
|
|
Cause
| Please refer to exception message for more specific cause information.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320917
|
Error: Unable to add LogNotification Traps at this moment due to unavailability of LogBroadcaster Runtime MBean on server server
|
Description
| The required LogBroadcaster Runtime MBean for the specified server was unavailable. Therefore the SNMP Agent is unable to add LogNotification Traps at this moment.
|
|
Cause
| This is an internal error.
|
|
Action
| Contact BEA Support.
|
|
|
BEA-320918
|
Error: Failed to add NotificationListener to logBroadcaster for SNMPLogFilter logFilter.
|
Description
| An exception occurred while registering the log filter trap. This failure will result in no LogNotification Traps being generated for the given SNMPLogFilterMBean.
|
|
Cause
| Please refer to exception message for more specific cause information.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320919
|
Error: Failed to send Log Notification trap for server server for message msgID for subsystem subSys
|
Description
| An exception was encountered while trying to construct and send a SNMP trap for a detected Log Notification action.
|
|
Cause
| Please refer to exception message for more specific cause information.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320920
|
Error: MBeanServerConnection.createMBean failed for GaugeMonitor mon
|
Description
| Failed to register the requested GaugeMonitor in the MBeanServer.
|
|
Cause
| There may be a naming conflict with the specified Monitor name.
|
|
Action
| Query the MBeanServer to determine if the Monitor was successfully registered or already exists.
|
|
|
BEA-320921
|
Error: MBeanServerConnection.createMBean failed for CounterMonitor mon
|
Description
| Failed to register the requested CounterMonitor in the MBeanServer.
|
|
Cause
| There may be a naming conflict with the specified Monitor name.
|
|
Action
| Query the MBeanServer to determine if the Monitor was successfully registered or already exists.
|
|
|
BEA-320922
|
Error: MBeanServerConnection.createMBean failed for StringMonitor mon
|
Description
| Failed to register the requested StringMonitor in the MBeanServer.
|
|
Cause
| There may be a naming conflict with the specified Monitor name.
|
|
Action
| Query the MBeanServer to determine if the Monitor was successfully registered or already exists.
|
|
|
BEA-320923
|
Error: Error creating JMX Monitor monitorName of type type for MBean mbeanName.
|
Description
| An exception was encountered while attempting to create a JMX Monitor for the specified type.
|
|
Cause
| This may be due to a misconfigured Monitor entry specification. Please refer to exception message for more specific cause information.
|
|
Action
| Modify configuration of the SNMPJMXMonitorMBean entry or take appropriate action based upon the specified exception message.
|
|
|
BEA-320924
|
Error: Failed to add MBeanListener for new instances of type type on server server
|
Description
| An exception was encountered while attempting to create a JMXNotificationListener to detect new MBean instances which would match criteria for the defined Monitor Change trap.
|
|
Cause
| This may be due to a misconfigured SNMPXXXMonitor entry specification in config.xml. Please refer to exception message for more specific cause information.
|
|
Action
| Modify configuration of the SNMPXXXMonitor entry or take appropriate action based upon the specified exception message.
|
|
|
BEA-320925
|
Error: Failed to send Monitor trap for server server for type type for object name
|
Description
| An exception was encountered while trying to construct and send a SNMP trap for a detected JMX Monitor action.
|
|
Cause
| Please refer to exception message for more specific cause information.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320926
|
Error: Unable to handle MBeanServer Notification in JMX Monitor Type mon for new instance.
|
Description
| An exception was encountered while attempting to create a new JMX Monitor for the new instance.
|
|
Cause
| Please refer to exception message for more specific cause information.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320927
|
Info: SNMP agent is initializing.
|
Description
| The SNMP agent has begin its initialization process and will process its configuration.
|
|
Cause
| This message is for informational purposes only.
|
|
Action
| No action is required.
|
|
|
BEA-320928
|
Error: SNMP Agent initialization failed while accessing server information for the configured Domain.
|
Description
| The SNMP Agent was not able to successfully complete its initialization due to a failure to process the configured server information.
|
|
Cause
| Refer to earlier SNMP error log information for specific information on the cause of the problem.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320929
|
Info: SNMP agent initialization complete.
|
Description
| SNMP agent initialization complete. All configuration has been processed and the specified traps and MIB processing is ready.
|
|
Cause
| This message is for informational purposes only.
|
|
Action
| No action is required.
|
|
|
BEA-320930
|
Info: SNMP Agent Generic coldStart trap sent.
|
Description
| As part of its initialization and based upon the specified configured the WebLogic SNMP Agent has created and sent a Generic coldStart trap to the SNMP Manager.
|
|
Cause
| This message is for informational purposes only.
|
|
Action
| No action is required.
|
|
|
BEA-320931
|
Notice: The SNMP trap version is version
|
Description
| The SNMP Agent has been configured to run with the specified SNMP version.
|
|
Cause
| This message is for informational purposes only.
|
|
Action
| No action is required.
|
|
|
BEA-320932
|
Error: SNMPProxy proxy has Value for supportedOIDRoot of oidRoot. It must be an absolute OID beginning with . .
|
Description
| The SNMPProxy has an invalid OID configuration and will be discarded from the configuration.
|
|
Cause
| Invalid SNMPProxyMBean configuration.
|
|
Action
| Correct the SNMPProxy config.xml entry.
|
|
|
BEA-320933
|
Error: SNMP Agent failed initialization due to a configuration exception
|
Description
| An exception was encountered while trying to process the specified SNMP configuration from config.xml.
|
|
Cause
| This is due to an invalid configuration specification. Please refer to exception message for more specific cause information.
|
|
Action
| Modify config.xml to correct the invalid configuration entry(s).
|
|
|
BEA-320934
|
Error: Exceptional condition when checking server status
|
Description
| An exception was encountered while determine the status of the configured WebLogic Server.
|
|
Cause
| Please refer to exception message for more specific cause information.
|
|
Action
| Take appropriate action based upon the specified exception message.
|
|
|
BEA-320935
|
Error: Failed to retrieve attprefix MBean attribute attname for MBean type beanType object name beanName
|
Description
| Processing for the specified MIB request was unable to locate the necessary MBean meta-data needed to correctly return the requested attribute values.
|
|
Cause
| This is an internal error that could be the result of an invalid MIB entry that does not correspond with the currently supported attributes on the specified MBean Type.
|
|
Action
| Contact BEA Support.
|
|
|
BEA-320936
|
Error: Unable to determine MBean Information for this MIB request for Type type.
|
Description
| Processing for the specified MIB request was unable to locate the necessary MBean meta-data needed to correctly return the requested attribute values.
|
|
Cause
| This is an internal error that could be the result of an invalid MIB entry or missing WebLogic class information.
|
|
Action
| Contact BEA Support.
|
|
|
BEA-320937
|
Error: Exception occurred sending SNMP message, error.
|
Description
| A runtime error occurred during the sending of an SNMP message over TCP/IP, possibly due to a networking or configuration error.
|
|
Cause
| This is an internal error that occurred during the sending of an SNMP message using the TCP transport provider.
|
|
Action
| Contact BEA Support.
|
|
|
BEA-320938
|
Error: SNMP Agent does not support setting values for MBean attributes through SNMP.
|
Description
| The SNMP Agent provides a read-only view of the MBeanServer, it is not possible to make configuration changes using SNMP.
|
|
Cause
| User attempted to set an MBean attribute using SNMP.
|
|
Action
| Use JMX APIs to update WLS configuration MBeans.
|
|
|
BEA-320939
|
Error: There was an error adding a row to the SNMP table for MBean objName of type type.
|
Description
| The SNMP table row corresponding to the given MBean instance could not be added.
|
|
Cause
| It could be due to a row already existing in the SNMP Agent for the MBean or an error condition in the SNMP Agent.
|
|
Action
| Take appropriate action based on additional information in the error stack trace.
|
|
|
BEA-320940
|
Error: There was an error deleting the row from the SNMP table for MBean objName.
|
Description
| The SNMP table row corresponding to the given MBean instance could not be deleted.
|
|
Cause
| The specified MBean instance was not registered in SNMP or it could be due to an error condition in the SNMP Agent.
|
|
Action
| Take appropriate action based on additional information in the error stack trace.
|
|
|
BEA-320941
|
Error: An SNMP message was received over the default channel instead of the dedicated SNMP channel.
|
Description
| When a dedicated Network Access Point has been configured for the SNMP protocol, SNMP packets will only be accepted and processed over the dedicated channel(s) (in addition to the SNMP Agent's configured UDP port).
|
|
Cause
| This occurs when a dedicated Network Access Point for SNMP traffic has been configured and activated and an SNMP request is received over the default server channel.
|
|
Action
| Direct the SNMP request to the configured channel.
|
|
|
BEA-320942
|
Error: The specified type name type is invalid.
|
Description
| This error is thrown during validation for a SNMPJMXMonitorMBean or a SNMPAttributeChangeMBean configuration.
|
|
Cause
| The name specified is not recognized as a valid WebLogic Server MBean type.
|
|
Action
| Please specify the correct name for a WebLogic Server Configuration or Runtime MBean type.
|
|
|
BEA-320943
|
Error: The specified attribute name attr is not valid for the given type type.
|
Description
| This error is thrown during validation for a SNMPJMXMonitorMBean or a SNMPAttributeChangeMBean configuration.
|
|
Cause
| The attribute name specified that is not valid is specified as part of the configuration.
|
|
Action
| Please specify the correct attribute name for the WebLogic Server Configuration or Runtime MBean type.
|
|
|
BEA-320944
|
Error: The SecurityName attribute is not specified for the SNMPTrapDestination name.
|
Description
| When the SNMP Agents trap version is set to V3 the security name must be specified.
|
|
Cause
| The SNMP Agents trap version is set to V3 and the SecurityName is not specified for the given SNMPTrapDestination.
|
|
Action
| Please specify the SecurityName attribute on whose behalf the SNMP Agent will issue v3 traps.
|
|
|
BEA-320945
|
Error: The SNMP Agent's TrapVersion needs to be V2 or higher to be able to send INFORM notifications.
|
Description
| The SNMP Agent sends INFORM notifications instead of traps only when the SNMPTrapVersion is V2 or higher.
|
|
Cause
| The SNMPAgentMBean's SNMPTrapVersion attribute is set to V1.
|
|
Action
| Please specify the SNMPTrapVersion to be V2 or higher in the configuration.
|
|
|
BEA-320946
|
Error: The SNMP Agent agentName is already deployed to server serverName.
|
Description
| Only one SNMPAgentDeployment instance can be targetted to a given server.
|
|
Cause
| An attempt was made to target multiple SNMPAgentDeploymentMBeans to the same WebLogic Server instance.
|
|
Action
| Ensure that only one SNMPAgentDeploymentMBean is targetted to any Server in the domain.
|
|
|
BEA-320947
|
Error: The AuthenticationProtocol for SNMP Agent agentName cannot be noAuth when PrivacyProtocol priv is specified.
|
Description
| It is invalid to have a privacy protocol without specifying an autentication protocol.
|
|
Cause
| An invalid combination of authentication and privacy protocols is being configured.
|
|
Action
| Specify either MD5 or DES as the AuthenticationProtocol in combination with Privacy.
|
|
|
BEA-320948
|
Error: The SNMPTrapDestinationMBean trapDest has a higher SecurityLevel trapSecLevel than the SNMPAgent's SecurityLevel agentSecLevel.
|
Description
| The Security Level for all the SNMP users is implicitly defined by configuring the AuthenticationProtocol and the PrivacyProtocol attributes on the SNMPAgentMBean. The global security level for all the users should be a level equal to or greater than the security level specified by the SNMPTrapDestination target. So if the target specifies noAuthNoPriv, then any valid combination of AuthenticationProtocol and the PrivacyProtocol attributes on the SNMPAgentMBean is allowed. If the target is authNoPriv then the AuthenticationProtocol needs to be set to a value other than noAuth on the SNMPAgentMBean. And for a target of authPriv, both AuthenticationProtocol and the PrivacyProtocol must be specified on the SNMPAgentMBean.
|
|
Cause
| An invalid combination of authentication and privacy protocols on the SNMPAgentMBean and security level on the SNMPTrapDestinationMBean is being configured.
|
|
Action
| Specify the valid security level for the users and the trap destinations.
|
|
|
BEA-320949
|
Error: SNMPAgent agent is configured with a security level of agentLevel; the security level of proxySecLevel for proxy proxy must not exceed that of the SNMP agent.
|
Description
| The security level on the proxy configuration must be less or equal to that of the parent SNMP agent itself. Thus, if the SNMP agent is configured with AUTH_NOPRIV, the security level of the proxy cannot be AUTH_PRIV.
|
|
Cause
| Configuring a security level on the SNMP proxy which exceeds security level of the SNMP agent corresponding to its configured authentication and privacy protocols.
|
|
Action
| Configure a lower security level on the proxy than the security level of the SNMP agent. For example, if the SNMP agent is configured with authentication but no privacy, configure security level of NOAUTH_NOPRIV or AUTH_NOPRIV on the proxy.
|
|
|
BEA-320950
|
Error: Failed to start the SNMP agent. If it failed to bind to the port, check if the port is available or the process has permission to bind to the port.
|
Description
| The SNMP agent could not be started.
|
|
Cause
| A common problem is with binding to specified UDP and agentX ports. The ports to which the agent binds may not be available. Also, on UNIX platforms, ports upto 1023 are protected and can be bound only by processes owned by root.
|
|
Action
| Check if specified ports are available. On UNIX, the default UDP port (161) and master AgentX port (705) are protected to be used by processes owned by root. In that case, either start the server as root, or configure the SNMP agent to use port numbers higher than 1023.
|
|
|
BEA-320951
|
Error: Failed to initalize the SNMP AgentX master subagent. One possible cause is the failure to bind the Master agentX port. If this is the case, check to see if specified AgentX port is available, or ensure the process has permissions to bind to the desired port.
|
Description
| The SNMP AgentX subagent could not be started.
|
|
Cause
| A common problem is with binding to the specified agentX port. The port to which the agent binds may not be available. Also, on UNIX platforms, ports upto 1023 are protected and can be bound only by processes owned by root.
|
|
Action
| Check if the specified port are available. On UNIX, the default master AgentX port (705) is protected to be used by processes owned by root. In that case, either start the server as root, or configure the SNMP agent to use port numbers higher than 1023.
|
|
