The SIP server has the ability to function as a Simple Network Management Protocol (SNMP) agent. The SNMP agent runs as a service which responds to requests from SNMP managers and sends SNMP trap notifications to SNMP managers.
To get the WebLogic SIP Server SNMP MIB, set the followings in the Administration Console screen.
(i) Enabling the SNMP service
Enable the SNMP service in the Domain --> Configuration --> SNMP tab.
(ii) Adding the SNMP service to the startup classes
Configure a new Startup Class in the Domain --> Deployments --> Startup & Shutdown tab.
Name - SNMPService
Class Name - com.oki.sip.mbeans.snmp.SNMPService
Argument - Server Name=Port Number,Server Name=Port Number,Server Name=Port Number
(Example)adminServer=161,managedServer_1=161,managedServer_2=162,managedServer_3=161
Target and Deploy - Managed servers
Note: The SNMP agent provided by WebLogic Server 8.1 SP4 can not use the WebLogic Server 8.1 SP4 MIB and the WebLogic SIP Server MIB at the same time. The above configuration makes it unable to get the WebLogic Server 8.1 SP4 MIB.
Note: When a port number is not specified by an argument,161 is used as a default port number. When two or more servers are started on the same machine, Even when the listen addresses which a server uses differ, please be sure to specify a port number.
To get the WebLogic SIP Server SNMP MIB, make a get/getnext request from the SNMP manager to the SNMP agent on the managed servers.
Note: All the MIB values are read-only because WebLogic Server 8.1 SP4 does not support SNMPv3. To set the MIB value, change the MBean attribute value that corresponds to the MIB through the Administration Console screen or a tool with a JMX interface.
You can use any of the following methods to browse the contents of the WebLogic SIP Server MIB:
WebLogic SIP Server MIB consists of all OIDs below .1.3.6.1.4.666.100.10.16.
WebLogic SIP Server generates its own trap notifications separately from the trap notifications provided by WebLogic Server.
While the WebLogic Server trap notifications are generated by the administration server, the WebLogic SIP Server trap notifications are generated by each managed server on which WebLogic SIP Server is running.
The WebLogic SIP Server trap notification setting depends on the SNMP service on the administration server.
Set the following attributes in the Domain --> Configuration --> SNMP tab in the WebLogic Administration Console screen.
| Traps (OID) | Generated When | Variable Bindings |
|---|---|---|
| okiSipAsStartup .1.3.6.1.4.1.666.100.10.16.0.1 |
WebLogic SIP Server started. | sipNotifApplIndex sipServerName |
| okiSipAsStop .1.3.6.1.4.1.666.100.10.16.0.2 |
WebLogic SIP Server stopped. | sipNotifApplIndex sipServerName |
| okiSipAsFailure .1.3.6.1.4.1.666.100.10.16.0.3 |
WebLogic SIP Server terminated for fatal status. | sipNotifApplIndex sipServerName |
| okiSipAsStatusChanged .1.3.6.1.4.1.666.100.10.16.0.6 |
Signifies that above configuration property value is changed. | sipNotifApplIndex sipServerName sipNotifTextualDescription |
| okiSipAsLicenseViolation .1.3.6.1.4.1.666.100.10.16.0.7 |
WebLogic SIP Server detected a license violation. | sipNotifApplIndex sipServerName sipNotifTextualDescription |
| okiSipAsRegurateThreshExceeded .1.3.6.1.4.1.666.100.10.16.0.8 |
Signifies that too many requests have been received by the system enough to exceed the configured threshold. This notification shows that admission control has started to regulate a new SIP request. | sipNotifApplIndex sipServerName callRegulateManagerRegulateType sipNotifIntValue callRegulateManagerThreshold |
| okiSipAsRegurateThreshRecovery .1.3.6.1.4.1.666.100.10.16.0.9 |
Signifies that the number of requests that received by the system have been less than configured threshold. This notification shows that admission control has released to allow a new SIP request. | sipNotifApplIndex sipServerName callRegulateManagerRegulateType sipNotifIntValue callRegulateManagerReleaseValue |
| okiSipAppStartup .1.3.6.1.4.1.666.100.10.16.0.10 |
SIP application installed. | sipNotifApplIndex sipServerName sipAplicationName |
| okiSipAppShutdown .1.3.6.1.4.1.666.100.10.16.0.11 |
SIP application stopped. | sipNotifApplIndex sipServerName sipAplicationName |
| okiSipAppFailure .1.3.6.1.4.1.666.100.10.16.0.12 |
SIP application failed to install . | sipNotifApplIndex sipServerName sipAplicationName |
| okiSipAppSessionThreshExceeded .1.3.6.1.4.1.666.100.10.16.0.13 |
Signifies that too many requests have been received by the SIP application system to exceed the configured application session threshold. | sipNotifApplIndex sipServerName sipAplicationName sipNotifIntValue |
When you use the HP OpenView Network Node Manager to receive the trap notifications, add the contents of the trapd.conf.txt to the trap definition.