Oracle SBC Security Guide
apSigRealmStatsPeriodASR (1.3.6.1.4.1.9148.3.2.1.2.4.1.18)
o The answer-to-seizure ratio expressed as a percentage during the 100 second sliding
window. For example, a value of 90 would represent 90% or 0.90
apSigRealmStatsRealmStatus (1.3.6.1.4.1.9148.3.2.1.2.4.1.30)
o State of the specified realm (INS, constraintviolation, or callLoadReduction)
The same list of statistics is also available per Session Agent.
Environmental Statistics
Below is a recommended list of SNMP OIDs to GET every 5 minutes from the Oracle System
Environment Monitor MIB (ap-env-monitor.mib). These will provide useful system environmental data.
apEnvMonObjects (1.3.6.1.4.1.9148.3.3.1)
apEnvMonI2CState (1.3.6.1.4.1.9148.3.3.1.1)
o State of environmental sensor on system chassis. A value of 2 is normal, all others need
to be investigated further [4].
apEnvMonTemperatureStatusEntry (1.3.6.1.4.1.9148.3.3.1.3.1.1)
apEnvMonTemperatureStatusValue (1.3.6.1.4.1.9148.3.3.1.3.1.1.4)
o Current temperature of mainboard PROM (in Celsius).
apEnvMonTemperatureState (1.3.6.1.4.1.9148.3.3.1.3.1.1.5)
o State of system temperature. A value of 2 is normal, all others need to be investigated
further [4].
Enterprise SNMP OIDs in a High Availability (HA) environment
SNMP polling is recommended for both Active and Standby SDs. The data from both Active and Standby
will be useful when troubleshooting. Also some data such as CPU, memory, interface stats, health score,
etc is independent data between Active and Standby SDs.
Of particular interest is the mib-system-name field in the system-config object. This is used as part of the
MIB-II sysName identifier. When performing a MIB-II sysName poll, an SBC will return a concatenation
of its assigned target name (as specified in the boot params), a dot, and the common hostname from the
system-config. Thus, systems in an HA pair named “acme1” and “acme2”, when assigned a mib-system-
name of “sbc.bedford”, would return acme1.sbc.bedford and acme2.sbc.bedford when polled,
respectively.
Enterprise SNMP Traps
SNMP traps enable an SNMP agent to notify the Network Management System (NMS) of significant
events using an unsolicited SNMP message. The SBC can be configured to send unsolicited SNMP traps
to a configured SNMP trap receiver [4] in SNMPv1, SNMPv2c and SNMPv3 formats (SNMPv3 trap
support was introduced in S-CX6.3.0). The snmp-agent-mode determines the trap format, and is set under
system-config.
SNMP Configuration recommendations
Under the system-config element the following settings should be enabled to provide additional visibility
to system events:
enable-snmp-auth-traps – sends a trap for a failed authentication as part of an SNMP request;
used to detect abuse
Comentarios a estos manuales