Skip to end of metadata
Go to start of metadata

This section details all UX alarms and events. The UX system displays these alarms in the Viewing Alarms and Events and are configured in the Configuring Alarms and Events page.

Alarm and Event Subsystems

Following list provides the alarms and events defined in various UX subsystems.

User Authentication and Directory Services

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

1

1

alarm

AD caching failed

communication

System:Service:IPAddress

minor

(tick)

  • Failed to cache values from AD.
  • This alarm will be cleared by event AD caching successful.

1

2

event

Online AD query failed

communication

System:Service

 

 

  • Online AD query failed.

1

3

event

Cannot modify Active Directory (Not Supported)

security

System:service:IPAddress

 

 

  • Modifying active directory is not supported.

1

4

event

User logged in

security

Username:IPAddress

 

 

  • New user [UXDOC:username] logged in from [UXDOC:ip address] at [UXDOC:time].

1

5

alarm

User login failed

security

Username:IPAddress

major

(tick)

  • User [UXDOC:username] login failed from [UXDOC:ip address] at [UXDOC:time].
  • This alarm will be cleared by event User logged in.

1

6

alarm

AD DOWN

communication

System:service:IPAddress

major

(tick)

  • Active directory is not reachable.
  • This alarm will be cleared by AD UP event.

1

7

event

AD UP

communication

System:service:IPAddress

 

 

  • Active directory is now reachable.

1

8

event

AD caching successful

communication

System:Service:IPAddress

 

 

  • AD caching was successful.

1

9

alarm

AD backup failed

storage

System:Service:IPAddress

minor

(tick)

  • Failed to backup cached values from AD to storage device.
  • This alarm will be cleared by successful AD backup event.

1

10

event

AD successfully backed up

storage

System:Service:IPAddress

 

 

  • Successfully backup cached values from AD to storage device.

1

11

alarm

AD cache truncated

storage

System:Service

minor

(error)

  • AD Cache is truncated, estimated to exceed max allowed cache size.

Resource Manager

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

2

1

alarm

Invalid Card ID EEPROM Data

equipment

Shelf;Card

critical

 

  • A Card was detected with invalid Card ID EEPROM contents (failed CRC-CCITT check)
  • The Card will remain out-of-service
  • The alarm is on the Card

2

2

alarm

Card Healthy Signal Failure

equipment

Shelf;Card

critical

 

  • During Line Card activation procedures, the Card Health signal did not go active after power was applied to the Card, indicating a Card fault.
  • The Card will remain out-of-service
  • The alarm is on the Card

2

3

alarm

Card Not Supported

equipment

Shelf;Card

major

 

  • A Card was detected which can be identified, but the UX system software is unable to support.
  • The Card will remain out-of-service
  • The alarm is on the Card

2

4

alarm

Power Supply Input Failure

equipment

Shelf;Card

major

(tick)

  • A Power Supply module has indicated a failure of input power
  • The UX System has lost Power Supply redundancy
  • This event is on the System

2

5

event

Power Supply Input Restored

equipment

Shelf;Card

 

 

  • A Power Supply module has indicated that input power has been restored
  • This event clears the "Power Supply Input Failure" Alarm

2

6

alarm

Power Supply Output Failure

equipment

Shelf;Card

major

 

  • A Power Supply module has indicated a failure of output power
  • The UX System has lost Power Supply redundancy
  • This event is on the System

2

7

alarm

Single Fan Failure

equipment

System;Fan_No

minor

 

  • A UX Chassis fan has failed
  • This event is on the System

2

8

alarm

Multiple Fan Failures

equipment

System;Fan_No;Fan_No,...

major

 

  • Multiple UX Chassis fans have failed
  • This event is on the System

2

9

alarm

System Temperature Warm

equipment

System

minor

(tick)

  • The temperature sensors have indicated that the system is running warm (TBD threshold).
  • This event is on the System

2

10

event

System Temperature Warm Cleared

equipment

System

 

 

  • The temperature sensors have indicated that the system is NO LONGER running warm
    This event clears the "System Temperature Warm" Alarm

2

11

alarm

System Temperature Hot

equipment

System

critical

(tick)

  • The temperature sensors have indicated that the system is running hot (TBD threshold).
  • This event is on the System

2

12

event

System Temperature Hot Cleared

equipment

System

 

 

  • The temperature sensors have indicated that the system is NO LONGER running hot
  • This event clears the "System Temperature Hot" Alarm

Licensing

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

3

1

alarm

Licenses expired

general

System:service

critical

(tick)

  • License of the node has expired, all the licensed features would fail to work
  • Alarm is cleared when the new license is applied

3

2

alarm

License expires in 2 weeks

general

System:service

major

(tick)

  • License of the node will expire in 2 weeks
  • Alarm is cleared when the new license is applied

3

3

event

New License applied

general

System:service

  • New License is applied on the node

3

4

alarm

Failed to Apply License

general

System:service

critical

  • The license system may be trying to use an invalid key
  • The license key applies to a different node
  • The license key expiry is past the present date

3

5

alarm

Failed to acquire license

general

System:service

major

  • All the SIP calls are being used
  • All the SIP registrations are being used
  • All the TDM channels are being used
  • All the DSPs are being used
  • SBA is not licensed
  • Transcoding is not licensed
  • Active Directory query is not licensed

Microsoft Survivable Branch Appliance support

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

5

1

alarm

SBA Unreachable

communication

SBAInstance

Critical

(tick)

  • SBA system can not be reached, system is down * Source Instance: SBA Monitor

5

2

event

Clear SBA Unreachable

communication

SBAInstance

 

 

  • Clears alarm 'SBA Unreachable' * Source Instance: SBA Monitor

5

3

alarm

SBA Failure Recovered

Equipment

SBAInstance

Minor

(error)

  • SBA system was previously unreachable, but has come up. Auto Clear is no so the user can investigate what went wrong, but the system should be working correctly now. * Source Instance: SBA Monitor

5

4

alarm

SBA Services Not Running

processing

SBAInstance

Critical

(tick)

  • SBA services are not running, calls can not be placed * Source Instance: SBA Monitor

5

5

event

Clear SBA Services Not Running

processing

SBAInstance

 

 

  • Clears alarm 'SBA Services Not Running' * Source Instance: SBA Monitor

5

6

alarm

SBA Services Recovered

processing

SBAInstance

Minor

(error)

  • SBA services were previously not running, but have been restored. Auto Clear is 'no' so the user can investigate what went wrong, but the system should be working correctly now. * Source Instance: SBA Monitor

5

7

alarm

SBA Service Restart Failed

processing

SBAInstance

Critical

(error)

  • SBA attempted to restart a failed service, service did not start successfully. User interaction is required. * Source Instance: SBA Monitor

5

8

event

SBA System Started

processing

SBAInstance

 

 

  • This event is set when the SBA communication system is first established, and usually indicates that the Com Express Board has finished booting. It should come up at system startup, it may come again if the Com Express Board is rebooted. * Source Instance: SBA Monitor

5

9

event

SBA System Shutting down

processing

SBAInstance

 

 

  • A planned or deliberate shut down is taking place on the Com Express Board. * Source Instance: SBA Monitor

5

10

alarm

Ethernet Link Down

Equipment

SBAInstance;Port

Major

(tick)

  • Ethernet port specified has lost link. * Source Instance: Eth0/Eth1 via SBA Monitor.

5

11

event

Ethernet Link Up

Equipment

SBAInstance

 

 

  • Ethernet port specific has got link. * Source Instance: Eth0/Eth1 via SBA Monitor.

Call Routing

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

7

1

event

Configuration change occurred on Action Set

general

ActSetTble

 

 

  • There is an action set table number/name that should be printed with this event.

7

2

event

Configuration change occurred on Normalization Table

general

NormTble

 

 

  • There is an norm table number/name that should be printed with this event.

7

3

event

Configuration change occurred on Route Table

general

RtTble

 

 

  • There is an route table number/name that should be printed with this event.

7

4

event

Configuration change occurred on Translation Tables

general

TransTble

 

 

  • There is an translation table number/name that should be printed with this event.

7

5

alarm

Route temporarily disabled

communication

RtTble

warning

(tick)

  • If a link is down or some other event occur to take a route entry out of service this alarm is set.

7

6

event

Route enabled

communication

RtTble

 

 

  • Route came up.

7

7

alarm

A Call exceeded the limit for number of destinations

communication

CallDest

warning

(error)

  • A call with destination of X tried to be forked more than the limit allows (currently 8)

Common Call Control

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

8

1

event

Channel is in service

Communication

Card;Port;Channel

 

 

Channel is up and is in service. This clears the "Channel Out Of Service Alarm".

8

2

alarm

Channel is out of service

Communication

Card;Port;Channel

Minor

(tick)

Channel Out Of Service Alarm. This alarm is automatically cleared when Channel is in service.

SIP

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto clear

Notes/Description

9

1

alarm

SIP Server not responding

Communication

SIPCluster;ServID;Protocol;IPAddress;Port

Major

(tick)

SIP server has failed to respond and has been taken out of service. This alarm will be cleared by the evnt "Sip server became responsive"

9

2

alarm

SIP Signaling Group taken out of service

Communication

SG

Critical

(tick)

All servers in SG have failed. This alarm will be cleared by "Sip Signaling group enabled" event.

9

3

event

SIP Signaling Group disabled

Communication

SG

 

 

Configuration has changed this SG to disabled

9

4

alarm

TLS Handshake Alert Failure

Security

IPAddress;Port

Minor

(error)

  • This alarm will be generated if TLS Connection failed with an Alert. The connection associated with a TLS Connection ID is aborted. Suggested action is to look up the TLS Alert code definitions and determine what corrective actions are to be taken.

9

5

alarm

TLS Handshake Inactivity Timeout Failure

Security

IPAddress;Port

Minor

(error)

  • This alarm will be generated if there was long period of inactivity during exchange of handshake messages for an associated TLS Connection ID. Suggested action for operator is to tune the configurable timeout value as to set it to maximum 30 seconds if network delays is experienced

9

6

alarm

Configured port number mismatch

Processing

IPAddress;Port

Minor

(error)

Discrepency of an FQDN/Port configured in the SipServer object that is different than the DNS SRV lookup. A DNS SRV record can return the port number for the selected protocol. This port value will take priority over the configured port.

9

7

event

SIP Server became responsive

Communication

SIPCluster;ServID;Protocol;IPAddress;Port

 

 

SIP server came up

9

8

alarm

SIP cluster went down

Communication

SIPCluster

Major

(tick)

SIP cluster went down.This is due to all the servers in the clusters are not responsive. This alarm will be cleared by the event "Sip cluster enabled".

9

9

event

SIP Cluster enabled

Communication

SIPCluster

 

 

SIP cluster enabled

9

10

event

SIP Signaling group enabled

Communication

SG

 

 

SIP Signaling group enabled

ISDN

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

10

1

alarm

D-Channel down

communication

Card;Port

critical

(tick)

  • The data link layer of the port has come down
  • The alarm is on the SG.

10

2

event

D-Channel up

communication

Card;Port

  • The data link layer of the port has come back up
  • The alarm is on the SG
  • This event will clear the D-channel down alarm.

10

3

alarm

call released due to channel restart by far end

communication

Card;Port;Channel

minor

(error)

  • call released as the ISDN channel has been restarted by far end
  • The alarm is on the SG

Telco Interface Process

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

11

1

alarm

port disabled by operator

communication

Card;Port

Warning

(tick)

  • The physical layer of the port has been brought down by the operator
  • The alarm is on the Port.

11

2

event

port enabled by operator

communication

Card;Port

  • The physical layer of the port has been brought back up by the operator
  • The alarm is on the Port
  • This event will clear the "Layer 1 disabled by operator" alarm.

11

3

alarm

DS1 Loopback Enter

communication

Card;Port

critical

(tick)

  • The DS1 has been put into a loopback state by the operator.
  • The alarm is on the Port.

11

4

event

DS1 Loopback Exit

communication

Card;Port

*The DS1 has been put out of the loopback state by the operator.

  • The alarm is on the Port
  • This event will clear the DS1 loopback Enter alarm.

11

5

alarm

Red Alarm - Loss of Signal

communication

Card;Port

critical

(tick)

  • The physical layer has detected an alarm
  • The alarm is on the Port.
  • This can be originated because of an alarm condition from far end

11

6

event

Red Alarm - Loss of Signal cleared

communication

Card;Port

  • The physical layer has detected an alarm clear.
  • The alarm is on the Port
  • This event will clear the " Red Alarm - Loss of Signal" alarm.

11

7

alarm

Red Alarm - Loss of Frame

communication

Card;Port

critical

(tick)

  • The physical layer has detected an alarm
  • The alarm is on the Port.
  • This can be originated because of an alarm condition from far end

11

8

event

Red Alarm - Loss of Frame cleared

communication

Card;Port

  • The physical layer has detected an alarm clear.
  • The alarm is on the Port
  • This event will clear the "Red Alarm - Loss of Frame" alarm.

11

9

alarm

Blue Alarm

communication

Card;Port

critical

(tick)

  • The physical layer has detected an alarm
  • The alarm is on the Port.
  • This can be originated because of an alarm condition from far end

11

10

event

Blue Alarm Cleared

communication

Card;Port

  • The physical layer has detected an alarm clear.
  • The alarm is on the Port
  • This event will clear the "Blue Alarm" alarm.

11

11

alarm

Yellow Alarm

communication

Card;Port

critical

(tick)

  • The physical layer has detected an alarm
  • The alarm is on the Port.
  • This can be originated because of an alarm assert issued by operator or a detection of alarm condition from far end

11

12

event

Yellow Alarm Cleared

communication

Card;Port

  • The physical layer has detected an alarm clear.
  • The alarm is on the Port
  • This event will clear the "Yellow Alarm" alarm.

11

13

alarm

Port Disabled as port not found on DS1

communication

Card;Port

critical

(minus)

  • The alarm is on the Port.
  • This alarm is generated to indicate that a port which was present in the UI is now marked as disabled because the corresponding port was not present on the DS1 physical hardware

11

14

alarm

Clock recovery port has fallen back from primary to secondary

communication

Card;Port

critical

(tick)

  • The alarm is on the Port.
  • This alarm is generated to indicate that the primary port from which clock was being recovered has gone down and so clock recovery is now being performed on the secondary port

11

15

alarm

Clock recovery port from primary to secondary cleared

communication

Card;Port

critical

  • The alarm is on the Port.
  • This alarm is generated to indicate that the primary port from which clock is back in operation and and so clock recovery is now being performed on the primary port

11

16

alarm

Clock recovery port has fallen back from secondary to holdover

communication

Card;Port

critical

(tick)

  • The alarm is on the Port.
  • This alarm is generated to indicate that the primary and secondary ports from which clock was being recovered have gone down and so clock recovery is now being performed internally from oscillator holdover clock

11

17

alarm

Clock recovery from holdover clock cleared

communication

Card;Port

critical

  • The alarm is on the Port.
  • This alarm is generated to indicate that either the primary and secondary ports from which clock was being recovered has come back in service and so clock recovery is now being performed from the primary or secondary port instead of the oscillator holdover clock

11

18

alarm

Line card not detected

communication

Card

critical

(tick)

  • UX has detected that a line card is not detected in a line card slot.
  • The alarm is on the line card slot.
  • This can be originated because a line card was not detected at the power up of UX node. If the line card was removed from the system for maintenance purposes then this alarm will disappear when the
    card is inserted back. If the line card is removed permanently then the configuration of the ports under this line card may be removed.

11

19

event

Line card detected

communication

Card

  • The physical layer has detected an alarm clear.
  • The alarm is on the line card slot
  • This event will clear the " Line card not detected" alarm, Specifically when Resource Manager informs TIP of a card detection.

Media Stream Controller

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

12

1

alarm

DSP Card not coming up

Equipment

Card

Critical

(tick)

  • This alarm will be generated if a C300, C900 or TI DSP card cannot be brought up.
  • This alarm will be cleared by the "DSP Card is UP" event.

12

2

alarm

DSP Card reset

Equipemnt

Card

Major

(tick)

  • This alarm will be generated if a C300, C900 or TI DSP card encounters a fatal error condition.
  • The only way to bring the card back to usable state is to restart the node.

12

3

event

DSP Card is UP

Equipment

Card

 

 

  • This event will clear the "DSP Card not coming up" and "DSP Card reset" alarms.

12

4

event

DSP Channel Failure

Processing

Card;Port;Channel

 

 

  • This event will be generated if a DSP channel encounters a fatal error condition and has to be closed. The call will be taken down.

12

5

event

Network Route Failure

Processing

Card;Port;Channel

 

 

  • This event will be generated if a DSP channel cannot be connected to the IP network. The call will be taken down.

Common Transport Layer

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

13

1

alarm

TLS Own Server Certificate will Expire

Security

CertificateCommonName

Minor

(tick)

This alarm is notified with lesser severity when the own server certificate will be expiring within a window time. This alarm provides additional description containing the certificate file name, validity start and end dates. Suggested action would be to request a new Certificate Signing Request, export the CSR file and send it out for signing. A new trusted and signed own server certificate is to be imported. Source Instance: Certificate CommonName.

13

2

alarm

TLS Own Server Certificate has Expired

Security

CertificateCommonName

Critical

(tick)

This alarm will be generated with critical severity when the own server certificate had expired. All TLS connection attempts will be aborted by the Mediation Server and no traffic will be exchange. This alarm provides additional description containing the certificate file name, validity start and end dates. Suggested action would be to request a new Certificate Signing Request, export the CSR file and send it out for signing. A new trusted and signed own server certificate is to be imported. Source Instance: Certificate CommonName.

13

3

alarm

TLS Own Server Certificate is missing

Security

CertificateCommonName

Critical

(tick)

This alarm will be generated with critical severity when the own server certificate is found to be missing or has failed validations. All TLS connection attempts will be aborted by the Mediation Server and no traffic will be exchange. Source Instance: Certificate CommonName.

13

4

alarm

TLS Self Sign Certificate Generation Failed

Security

CertificateCommonName

Critical

This alarm will be generated with critical severity when the self signed certificate generation failed by the system. The Web UI will not be able to establish HTTPS connection with the Web Server Interface. Source Instance: Certificate CommonName.

13

5

event

New and Valid TLS Own Server Certificate Detected

Security

CertificateCommonName

-

A new own server certificate was uploaded, validated, not expired and good to use in successfully establishing a TLS connection. This event will clear the TLS Own Server Certificate Expiring, TLS Own Server Certificate Expired and TLS Own Server Certificate Missing alarms. Source Instance: Certificate CommonName.

BMP

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

14

1

event

Invalid session

Security

IPaddress;port

 

 

  • If a web-client tries to open TLS connection with invalid session-id, BMP will generate this event

14

2

alarm

TLS Handshake Alert Failure

Security

IPaddress;port

Minor

 

  • This alarm will be generated if TLS Connection failed with an Alert. The connection associated with a TLS Connection ID is aborted. Suggested action is to look up the TLS Alert code definitions and determine what corrective actions are to be taken.

14

3

alarm

TLS Handshake Inactivity Timeout Failure

Security

IPaddress;port

Minor

 

  • This alarm will be generated if there was long period of inactivity during exchange of handshake messages for an associated TLS Connection ID. Suggested action for operator is to tune the configurable timeout value as to set it to maximum 30 seconds if network delays is experienced

Network Services

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

15

1

alarm

Interface oper down

Communication

Port

Major

(tick)

  • Occurs when an Ethernet port (of ports 1, 2, 3 and 4) is operationally down (e.g. cable unplugged, mismatched speed/duplexity settings) and if admin-status is ADMIN_UP. The alarm is automatically cleared when the interface returns to working condition or when the admin-status is configured to be ADMIN-DOWN.
  • Is generated only on UX2000 platform. This alarm is not generated on the UX1000 platform (See ID: 15, Sub-ID: 7 in this table)
  • The operator should check the physical cabling of the port that has this condition and verify the speed and duplexity settings on UX and on the device connected to the other end of the Ethernet cable.
  • If the alarm is reported on an unused port, the admin-status of the unused port should be configured as "ADMIN-DOWN".

15

2

event

Interface oper up

Communication

Port 

 

 

  • Is generated when an Ethernet port (of ports 1, 2, 3 and 4) becomes operationally up. This event automatically clears the "Interface oper down" alarm.

15

3

event

Interface admin up

Communication

Port/Logical Interface

 

 

  • Is generated when the admin-status of the Port or Logical Interface is configured to be ADMIN-UP.
  • Is applicable to UX2000 platform only

15

4

event

Interface admin down

Communication

Port/Logical Interface

 

 

  • Is generated when the admin-status of the Port or Logical Interface is configured to be ADMIN-DOWN.
  • Is applicable to UX2000 platform only

15

5

event

Admin port
oper down

Communication

Port

 

 

  • Is generated when the Admin Port is operationally down (e.g. cable unplugged, mismatched duplex/speed settings).
  • Is applicable to UX2000 platform only
  • The operator should check the physical cabling of the port that has this condition and verify the speed and duplexity settings on UX and on the device connected to the other end of the Ethernet cable.
  • It is very common and typical for UX2000 to leave the ADMIN-PORT unconnected and hence this condition is reported as an event and not an alarm.

15

6

event

Admin port oper up

Communication

Port

 

 

  • Is generated with the port becomes operational after being in an *Admin port oper down* state.
  • Is applicable to UX2000 platform only

15

7

event

Interface oper down

Communication

Port



  • Occurs when an Ethernet port (of ports 1 and 2) is operationally down (e.g. cable unplugged, mismatched speed/duplexity settings)
  • Is generated only on UX1000 platform. The same conditions are reported as alarm (ID: 15, Sub-ID: 1) on UX2000 platform.
  • When this event occurs (noticed as a trap), operator should check the physical cabling of the port that has this condition and verify the speed and duplexity settings on UX and on the device connected to the other end of the Ethernet cable.



System Health Monitor

ID

Sub-ID

Type

Condition

Category

Decode Key

Severity

Auto Clear

Notes/Description

16

1

alarm

Application Service stopped

Processing

Service

critical

(tick)

  • An Application service failure was detected

16

2

event

Application Service restarted

Processing

Service



  • An Application service was restarted
  • This event clears "Application Service stopped"

Decode Key Table

Following tables defines the decode key types used through out the system Alarms and Events system in UX.

Decode Key

Description

System

By default it will be the UX system

Service

Service in which this alarm/event belongs to, for ex. ISDN, SIP etc..

Username

Username responsible for the generation of the alarm/event, mostly related to the User Authentication Service.

IP address

IP address of the system responsible for generation of this alarm/event

Frame

Frame responsible, at which the data transmission has failed/generated an error

Card /Slot

Card /Slot involved in generating the alarm For ex. TI DSP etc..

ActSetTble

Action set table number responsible for the alarm/event.

NormTble

Normalization table number responsible for this alarm

RtTble

Route table number responsible for this alarm/event.

TransTble

Translation table number responsible for this alarm/event.

Call Dest

Call destination (address) responsible for this alarm/event

Conference ID

Conference ID involved in the alarm generation. It will be an integer starting from 1 to FFFFFFFF.

Codec

Media codec like G711, used when this alarm is generated

SG/Signaling Group

Signaling Group on which this alarm occurred

Channel

Channel number that involved in generating this alarm.

CallID

Call ID of the call failed/is responsible for generating this alarm.

Port

Port number on which this alarm is generated.

Interface

Name/Number of the interface involved in generating this alarm. For ex. ETH1, T1 etc..

Server

Server responsible for this alarm. for Ex. SIP server which is not responding..

CertificateCommonName

Server certificate common name for ex:"VeriSign Trial Secure Server CA - G2 "

SBAInstance

Its the SBA monitor involved in generating the alarm.

Interface

By default it will be the Ethernet interface card.

SIPCluster

Name of the SIP cluster associated with a set of SIP servers

ServID

ID of the SIP server

Protocol

Protocol involved in generating this alarm/event

Fan_No

Fan number