View Alarm Details

You can select a specific alarm to view detailed information on the alarm as described in the tables below.

➢

Do the following:

Select the alarm entry whose details you wish to view.

The table below describes the Alarm fields.

Field

Description

ITU X.733 Field

Alarm Info

Severity

See table below.

Received Date and Time

The time stamp DD-MM-YY HH:MM:SS indicating when the alarm was retrieved by Live Platform portal.

Source

Possible values of sources if applicable to a specific alarm. This value is displayed from the variable-binding tgTrapGlobalsSource

See the following examples:

■

IP Phones: IPPhone/security_advisor/admin/adb_enabled/<MACaddress>

■

SBC devices: System#0/Proxy-Set#<ProxySetNumber>

■

MSBR devices: WAN link

■

Meeting Insights and Interaction Insights: <Unique Services Id>/<StorageFriendlyName>-SystemConfiguration

Name

The name of the alarm.

Unique ID

The unique index for the alarm on the source device:

■

For SBC devices: ID corresponds to the "Sequential" field in the Alarms table (Monitor > Summary > Active Alarms).

■

For IP Phones, ARM, UCaaS Connect, VOCA CIC, Meeting Insights and Interaction Insights, this ID is generated internally by Live Platform.

Alarm ID

The unique database ID index for the alarm in the Live Platform portal database.

Alarm Category

■

other(0)

■

communicationsAlarm(1)

■

qualityOfServiceAlarm(2)

■

processingErrorAlarm(3)

■

equipmentAlarm(4)

■

environmentalAlarm(5)

■

integrityViolation(6)

■

operationalViolation(7)

■

physicalViolation(8)

■

securityServiceOrMechanismViolation(9)

■

timeDomainViolation(10)

Probably Cause

■

other(0)

■

adapterError(1)

■

applicationSubsystemFailure(2)

■

bandwidthReduced(3)

■

callEstablishmentError(4)

■

communicationsProtocolError(5)

■

communicationsSubsystemFailure(6)

■

configurationOrCustomizationError(7)

■

congestion(8)

■

corruptData(9)

■

cpuCyclesLimitExceeded(10)

■

dataSetOrModemError(11)

■

degradedSignal(12)

■

dteDceInterfaceError(13)

■

enclosureDoorOpen(14)

■

equipmentMalfunction(15)

■

excessiveVibration(16)

■

fileError(17)

■

fireDetected(18)

■

floodDetected(19)

■

framingError(20)

■

heatingVentCoolingSystemProblem(21)

■

humidityUnacceptable(22)

■

inputOutputDeviceError(23)

■

inputDeviceError(24)

■

lanError(25)

■

leakDetected(26)

■

localNodeTransmissionError(27)

■

lossOfFrame(28)

■

lossOfSignal(29)

■

materialSupplyExhausted(30)

■

multiplexerProblem(31)

■

outOfMemory(32)

■

ouputDeviceError(33)

■

performanceDegraded(34)

■

powerProblem(35)

■

pressureUnacceptable(36)

■

processorProblem(37)

■

pumpFailure(38)

■

queueSizeExceeded(39)

■

receiveFailure(40)

■

receiverFailure(41)

■

remoteNodeTransmissionError(42)

■

resourceAtOrNearingCapacity(43)

■

responseTimeExecessive(44)

■

retransmissionRateExcessive(45)

■

softwareError(46)

■

softwareProgramAbnormallyTerminated (47)

■

softwareProgramError(48)

■

storageCapacityProblem(49)

■

temperatureUnacceptable(50)

■

thresholdCrossed(51)

■

timingProblem(52)

■

toxicLeakDetected(53)

■

transmitFailure(54)

■

transmitterFailure(55)

■

underlyingResourceUnavailable(56)

■

versionMismatch(57)

■

authenticationFailure(58)

■

breachOfConfidentiality(59)

■

cableTamper(60)

■

delayedInformation(61)

■

denialOfService(62)

■

duplicateInformation(63)

■

informationMissing(64)

■

informationModificationDetected(65)

■

informationOutOfSequence(66)

■

intrusionDetection(67)

■

keyExpired(68)

■

nonRepudiationFailure(69)

■

outOfHoursActivity(70)

■

outOfService(71)

■

proceduralError(72)

■

unauthorizedAccessAttempt(73)

■

unexpectedInformation(74)

Description

Hard-coded description of the that is displayed in the Live Platform portal.

Status

One of the following:

■

New: A new alarm is raised. For example "Connection Lost"

■

Cleared: The new alarm is cleared. For example, "Connection Established"

■

Automatically Cleared: The alarm is cleared as a result of the configuration of the Automatic Clearing feature by AudioCodes Professional Services which enables you to purge records. (see Automatic Alarms Clearing)

Entity Info

Entity Name

The name of the entity upon which the action was performed.

IP Address

The IP address of the managed entity.

Source

As above

Tenant

The name of the Service Provider tenant to which the entity is attached.

Region

The name of the region to which the entity is attached.

Site

The name of the site to which the entity is attached.

Customer

The name of the customer to which the entity is attached.

Service

The name of the service from which the alarm is raised.

SNMP Info

Trap OID

NOTIFICATION-TYPE OID as it appears in the MIB.

System Up Time

Timestamp <HH, MM, SS> indicating the elapsed time that the device was active when the alarm was raised.

Trap Remote Port

SNMP Trap Manager port on the device that is used to send traps to the Live Platform portal. Used also by Fixed License Pool and Floating License Service.

Trap Community

SNMPV2 User configured on Live Platform and on the connected device where the trap is raised.

Trap SNMP Version

SNMP version of the device connection with Live Platform portal.

The table below describes the Alarm Severity fields.

Alarm Severity

Condition

Description

CorrectiveAction

Possible severity value. This value is displayed from the variable-binding tgTrapGlobalsSeverity.

One of the following:

■

cleared(0)

■

indeterminate(1)

■

warning(2)

■

minor(3)

■

major(4)

■

critical(5)

Condition upon which the alarm is raised for the specific severity. There may be several conditions for each severity.

Textual description of specific problem. This value is displayed from the variablebinding tgTrapGlobalsTextualDescription. The document includes a few examples of the possible values of this field.

Possible corrective action when applicable.

For details of the fields used in Alarm and Journal Forwarding, see Alarm and Journal Forwarding Data Formats. For details of the fields used in Alarm Forwarding, see Alarm and Journal Forwarding Data Formats.

You can enable the capture of additional alarms (excluding Service level alarms) for Service Providers in the Service Provider tenant entity settings by configuring parameter "Allowed Alarms (in addition to service level alarms)".