Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c862eadf5e0163170affe7001b, userName='null'}
JIRAIDAUTHSYMCHOR-3028911817
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc7d083d8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc7d083d8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}

This section details all 

Spacevars
0product
alarms and events. The 
Spacevars
0product
displays these alarms in the Viewing Alarms and Events and are configured in the Configuring Alarms and Events page.

Note

Hardware-related Alarms and Events are not applicable for

Spacevars
0product3
.

Table of Contents

...

The following list provides the alarms and events defined in various

Spacevars
0product
subsystems.

User Authentication and Directory Services

Children Display

Resource Manager

Licensing

Microsoft Survivable Branch Appliance Support

Call Routing

Common Call Control

uxAlmLicensedEnhancedMediaSessionswithTranscodingcountreached

uxAlmSRTPCallAttemptedNoLicenseAvailable

SIP

(tick)

  • Handshake response was started with valid certificate on local and remote gateway.
  • This event clears the 'SIP-TLS Handshake Negotiation Start Failure' alarm.

    Skype/Lync Presence Server Response Failure

    SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType

    ISDN

    Telco Interface Process

    Media Stream Controller

    Certificate Security Manager

    BMP

    Network Services

    System Health Monitor

    CAS 

    Configuration

    TCA Thresholds

    FQDN

    RAMP

    E911 Server

    SLB/SC Containers

    Media Containers

    MC Memory usage below [percentage] threshold.
    Div
    classpdf6pttext
    Div
    classpdf6pttext

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    1

    1

    Alarm

    uxAlmADcachingfailed1.3.6.1.4.1.177.15.2.65537

    AD caching failed

    Communication

    System;Service;IPAddress;PodName;ContainerType

    Minor

    (tick)

    • Failed to cache attributes from AD in memory.
    • Suggested action - try again later.
    • This alarm will be cleared by event AD caching successful.

    1

    2

    Event

    uxAlmOnlineADqueryfailed1.3.6.1.4.1.177.15.2.65538

    Online AD query failed

    Communication

    System;Service;PodName;ContainerType

    • Failed to run AD query.
    • Suggested action - confirm that AD is network reachable, check the AD configuration as well as AD access credentials.

    1

    4

    Event

    uxAlmUserloggedin1.3.6.1.4.1.177.15.2.65540

    User logged in

    Security

    Username;IPAddress;PodName;ContainerType

    • Specified user logged in.

    1

    5

    Alarm

    uxAlmUserloginfailed1.3.6.1.4.1.177.15.2.65541

    User login failed

    Security

    Username;IPAddress;PodName;ContainerType

    Major

    (tick)

    • Specified user login failed on [time] due to [reason].
    • This alarm will be cleared by event User logged in.

    1

    6

    Alarm

    uxAlmADUnreachable1.3.6.1.4.1.177.15.2.65542

    AD Unreachable

    Communication

    System;Service;IPAddress;DCType;PodName;ContainerType

    Major

    (tick)

    • Either AD is network unreachable, or the AD credentials are invalid.
    • This alarm will be cleared by 'AD Reachable' event.

    1

    7

    Event

    uxAlmADReachable1.3.6.1.4.1.177.15.2.65543

    AD Reachable

    Communication

    System;Service;IPAddress;DCType;PodName;ContainerType

    • Active directory is now reachable.

    1

    8

    Event

    uxAlmADcachingsuccessful1.3.6.1.4.1.177.15.2.65544

    AD caching successful

    Communication

    System;Service;IPAddress;PodName;ContainerType

    • AD caching was successful.

    1

    9

    Alarm

    uxAlmADbackupfailed1.3.6.1.4.1.177.15.2.65545

    AD backup failed

    Equipment

    System;Service;IPAddress;PodName;ContainerType

    Minor

    (tick)

    • Failed to backup cached values from AD to storage device.
    • Either the storage device is not present, or it is full.
    • Contact Ribbon Service for further assistance.

    1

    10

    Event

    uxAlmADsuccessfullybackedup1.3.6.1.4.1.177.15.2.65546

    AD successfully backed up

    Equipment

    System;Service;IPAddress;PodName;ContainerType

    • Successful backup of cached values from AD to storage device.

    1

    11

    Alarm

    uxAlmADcachetruncated1.3.6.1.4.1.177.15.2.65547

    AD cache truncated

    Equipment

    System;Service;PodName;ContainerType

    Minor

    • AD Cache is truncated, AD cache results have exceeded the maximum cache size.
    • Consider caching only the required attributes.
    • If the query is not found in cache, Online query will be performed, while affecting performance.

    1

    12

    Alarm

    uxAlmRADIUSServerUnreachable1.3.6.1.4.1.177.15.2.65548

    RADIUS Server Unreachable

    Communication

    System;Service;IPAddress;PodName;ContainerType

    Major

    (tick)

    • Either the RADIUS server is network unreachable, the configuration is incorrect, or due to service impacting change.
    • Suggested action - check shared secret, listening port, RADIUS server IP.
    • This alarm will be cleared by 'RADIUS Reachable' event.

    1

    13

    Event

    uxAlmRADIUSReachable1.3.6.1.4.1.177.15.2.65549

    RADIUS Reachable

    Communication

    System;Service;IPAddress;PodName;ContainerType

    • RADIUS server is online.

    1

    14

    Alarm

    uxAlmCDRloggingfailed1.3.6.1.4.1.177.15.2.65550

    CDR logging failed

    Communication

    System;Service;IPAddress;PodName;ContainerType

    Major

    • SBC Edge failed to send CDR to RADIUS based accounting server.
    • Either the server is network unreachable, or the configuration is incorrect.
    • Suggested action - check shared secret, listening port, RADIUS server IP.

    1

    15

    Alarm

    uxAlmCDRbackupfailed1.3.6.1.4.1.177.15.2.65551

    CDR backup failed

    Communication

    System;Service;IPAddress;PodName;ContainerType

    Major

    • SBC Edge failed to backup CDR in local file.
    • Either running with low disk space or CDR backup maximum limit is crossed.
    • Suggested action - Free up the disk space or save the CDR Queued file for future reference.

    1

    17

    Event

    uxAlmUserpasswordchangedsuccessfully1.3.6.1.4.1.177.15.2.65553

    User password changed successfully

    Security

    Username;PodName;ContainerType

    • Password changed successfully by [username] from [ipAddress].

    1

    18

    Alarm

    uxAlmUserpasswordchangefailed1.3.6.1.4.1.177.15.2.65554

    User password change failed

    Security

    Username;PodName;ContainerType

    Warning

    (tick)

    • Password change attempted by [username] from [ipAddress] failed.

    1

    19

    Event

    uxAlmUseraccountdisabled1.3.6.1.4.1.177.15.2.65555

    User account disabled

    Security

    Username;PodName;ContainerType

    • Account has been disabled by [username] from [ipAddress].

    1

    20

    Event

    uxAlmUseraccountactivated1.3.6.1.4.1.177.15.2.65556

    User account activated

    Security

    Username;PodName;ContainerType

    • Account has been activated by [username] from [ipAddress].

    1

    21

    Event

    uxAlmGlobalsecurityoptionschanged1.3.6.1.4.1.177.15.2.65557

    Global Security Options Changed

    Security

    Username;IPAddress;PodName;ContainerType

    • Global security options changed.

    1

    22

    Alarm

    uxAlmUserloginblocked1.3.6.1.4.1.177.15.2.65558

    User login blocked

    Security

    Username;PodName;ContainerType

    Major

    (tick)

    • User attempting to log in from [ipAddress] blocked due to excessive incorrect login attempts.

    1

    23

    Event

    uxAlmUserloginunblocked1.3.6.1.4.1.177.15.2.65559

    User login unblocked

    Security

    Username;PodName;ContainerType

    • User login is unblocked.
    124EventuxAlmUserpasswordexpired1.3.6.1.4.1.177.15.2.65560User password expiredSecurity

    Username;IPAddress;PodName;ContainerType

    • Password has expired.
    • User [username] logging in from [ipAddress] password is expired.
    125AlarmuxAlmADMaximumThreadsExceeded1.3.6.1.4.1.177.15.2.65561AD: Maximum Threads ExceededProcessing

    System;Service;PodName;ContainerType

    Major
    • AD has reached maximum threads. Please inform your service representative.
    126AlarmuxAlmADcachingtimedout1.3.6.1.4.1.177.15.2.65562AD caching timed outCommunication

    System;Service;IPAddress;PodName;ContainerType

    Minor
    • Timed out caching attributes due to lack of response from AD.
    • Suggested action - try again later.
    • The SBC will attempt to load the last successful cache from backup.
    127AlarmuxAlmADCacheEncryptionFailed1.3.6.1.4.1.177.15.2.65563AD Cache Encryption FailedCommunication

    System;Service;IPAddress;PodName;ContainerType

    Major(tick)
    • AD Cache encryption failed.
    • Cache will not be saved.
    128EventuxAlmADCacheEncryptionSuccessful1.3.6.1.4.1.177.15.2.65564AD Cache Encryption SuccessfulCommunication

    System;Service;IPAddress;PodName;ContainerType

    AD Cache encryption successful.

    ID

    Sub-ID

    Type

    MIB Trap  NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    2

    1

    Alarm

    uxAlmInvalidCardIDEEPROMData1.3.6.1.4.1.177.15.2.131073

    Invalid Card ID EEPROM Data

    Equipment

    System;Card;PodName;ContainerType

    Critical

    • A Card was detected with invalid Card ID EEPROM (failed CRC-CCITT check).
    • Suggested action - provide the entire alarm message including the numbers at the end to Ribbon Service for further assistance.

    2

    2

    Alarm

    uxAlmCardHealthCheckFailed1.3.6.1.4.1.177.15.2.131074

    Card Health Check Failed

    Equipment

    System;Card;PodName;ContainerType

    Critical

    • During Line Card activation, a Card Fault was detected after power was applied to the card.
    • The Card will remain out-of-service.
    • Suggested action - reboot system.
    • If issue persists, contact Ribbon Service with the alarm information.

    2

    3

    Alarm

    uxAlmCardnotSupported1.3.6.1.4.1.177.15.2.131075

    Card not Supported

    Equipment

    System;Card;PodName;ContainerType

    Major

    • A Card was detected which can be identified, but the SBC Edge software is unable to support.
    • The Card will remain out-of-service.
    • Suggested action - reboot system.
    • If issue persists, contact Ribbon Service with the alarm information.

    2

    4

    Alarm

    uxAlmPowerSupplyinputfailure1.3.6.1.4.1.177.15.2.131076

    Power Supply input failure

    Equipment

    System;PSU;PodName;ContainerType

    Major

    (tick)

    • A Power supply module has indicated a failure of input power.
    • The SBC Edge has lost Power Supply redundancy.
    • Suggested action - Verify that the power cable is connected and that the PS is functioning properly.

    2

    5

    Event

    uxAlmPowerSupplyinputrestored1.3.6.1.4.1.177.15.2.131077

    Power Supply input restored

    Equipment

    System;PSU;PodName;ContainerType

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

    2

    6

    Alarm

    uxAlmPowerSupplyoutputfailure1.3.6.1.4.1.177.15.2.131078

    Power Supply output failure

    Equipment

    System;PSU;PodName;ContainerType

    Major

    • A Power Supply module has indicated a failure of output power.
    • The SBC Edge has lost Power Supply redundancy.
    • Suggested action - Verify that the PS is functioning properly.

    2

    7

    Alarm

    uxAlmSingleFanfailure1.3.6.1.4.1.177.15.2.131079

    Single Fan failure

    Equipment

    System;Fan;PodName;ContainerType

    Major

    • Check the System tab to find the Fan ID of the failed fan.
    • Contact Ribbon Service with this information.

    2

    8

    Alarm

    uxAlmMultipleFanFailures1.3.6.1.4.1.177.15.2.131080

    Multiple Fan Failures

    Equipment

    System;Fans;PodName;ContainerType

    Critical

    • Check the System tab to find the Fan ID's of the failed fans.
    • Contact Ribbon Service with this information.

    2

    9

    Alarm

    uxAlmSystemTemperatureWarm1.3.6.1.4.1.177.15.2.131081

    System Temperature Warm

    Equipment

    System;PodName;ContainerType

    Minor

    (tick)

    • The temperature sensors have indicated that the system is running warm (55°C threshold).

    2

    10

    Event

    uxAlmSystemTemperatureWarmCleared1.3.6.1.4.1.177.15.2.131082

    System Temperature Warm Cleared

    Equipment

    System;PodName;ContainerType

    • The temperature sensors have indicated that the system is no longer running warm (55°C threshold).
    • This event clears the 'System Temperature Warm' Alarm.

    2

    11

    Alarm

    uxAlmSystemTemperatureHot1.3.6.1.4.1.177.15.2.131083

    System Temperature Hot

    Equipment

    System;PodName;ContainerType

    Critical

    (tick)

    • The temperature sensors have indicated that system is running hot (65°C threshold).

    2

    12

    Event

    uxAlmSystemTemperatureHotCleared1.3.6.1.4.1.177.15.2.131084

    System Temperature Hot Cleared

    Equipment

    System;PodName;ContainerType

    • The temperature sensors have indicated that the system is no longer running hot (65°C threshold).
    • This event clears the 'System Temperature Hot' Alarm.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    3

    1

    Alarm

    uxAlmLicensesexpired1.3.6.1.4.1.177.15.2.196609

    Licenses expired

    General

    System;Service;PodName;ContainerType

    Critical

    (tick)

    • License of the node has expired, all the licensed features would fail to work.
    • Contact Ribbon Enterprise Sales.

    3

    2

    Alarm

    uxAlmLicensewillexpirein14days1.3.6.1.4.1.177.15.2.196610

    License will expire in 14 days

    General

    System;Service;PodName;ContainerType

    Major

    (tick)

    • License of the node will expire in 2 weeks.

    3

    3

    Event

    uxAlmNewlicenseapplied1.3.6.1.4.1.177.15.2.196611

    New License applied.

    General

    System;Service;PodName;ContainerType

    • New License is applied on the node.

    3

    4

    Alarm

    uxAlmFailedtoApplyLicense1.3.6.1.4.1.177.15.2.196612

    Failed to Apply License.

    General

    System;Service;PodName;ContainerType

    Critical

    • Either an invalid key is used, or the license key applies to a different node, or the license key expiry is past the present date.
    • Contact Ribbon Sales to obtain a new license.

    3

    5

    Alarm

    uxAlmFailedtoacquirelicense1.3.6.1.4.1.177.15.2.196613

    Failed to acquire license.

    General

    System;Service;PodName;ContainerType

    Minor

    • Either [license type] are unlicensed, or all license(s) are exhausted.
    36AlarmuxAlmLicensedDS1portsexceedsinstalledports1.3.6.1.4.1.177.15.2.196614Licensed DS1 ports exceeds installed ports.General

    System;Service;PodName;ContainerType

    Critical
    • The alarm is generated when the license key applied has more DS1 ports licensed than are installed in the system.
    • The number of BRI ports installed will get activated.
    • As a fix, obtain a license with the correct number of DS1 ports.
    37AlarmuxAlmLicensedBRIportsexceedsinstalledports1.3.6.1.4.1.177.15.2.196615Licensed BRI ports exceeds installed ports.General

    System;Service;PodName;ContainerType

    Minor
    • The alarm is generated when the license key applied has more BRI ports licensed than are installed in the system.
    • The number of BRI ports installed will get activated.
    • As a fix, obtain a license with the correct number of BRI ports.
    38AlarmuxAlmLicensedFXSportsexceedsinstalledports1.3.6.1.4.1.177.15.2.196616Licensed FXS ports exceeds installed ports.General

    System;Service;PodName;ContainerType

    Minor
    • The alarm is generated when the license key applied has more FXS ports licensed than are installed in the system.
    • The number of FXS ports installed will get activated.
    • As a fix, obtain a license with the correct number of FXS ports.
    39AlarmuxAlmLicensedFXOportsexceedsinstalledports1.3.6.1.4.1.177.15.2.196617Licensed FXO ports exceeds installed ports.General

    System;Service;PodName;ContainerType

    Minor
    • The alarm is generated when the license key applied has more FXO ports licensed than are installed in the system.
    • The number of FXO ports installed will get activated.
    • As a fix, obtain a license with the correct number of FXO ports.
    310AlarmuxAlmFailedtogetkeyforLicensegeneration1.3.6.1.4.1.177.15.2.196618Failed to get key for License generationGeneralSystem;Service;PodName;ContainerTypeCritical
    • Failed to get key for license generation.
    311AlarmuxAlmLicensedSIPSignalingSessionsexceedssystemcapability1.3.6.1.4.1.177.15.2.196619Licensed SIP Signaling Sessions exceeds system capacityGeneralSystem;Service;PodName;ContainerTypeMinor
    • SIP Signaling Sessions of [number] licenses exceeds the capability of the system of [number] (Allocated Media Ports).
    312AlarmuxAlmLicensedSIPRegistrationsexceedssystemcapability1.3.6.1.4.1.177.15.2.196620Licensed SIP Registrations exceeds system capability.GeneralSystem;Service;PodName;ContainerTypeMinor
    • SIP Registration Sessions of [number] licenses exceeds the capability of the system of [number] (Allocated Media Ports).
    313AlarmuxAlmEnhancedMediaSessionswithTranscodingexceedssystemcapability1.3.6.1.4.1.177.15.2.196621

    Enhanced Media Sessions with Transcoding exceeds system capability.

    GeneralSystem;Service;PodName;ContainerTypeMinor
    • SIP Media Sessions Sessions of [number] licenses exceeds the capability of the system of [number] (Allocated Media Ports).
    314AlarmuxAlmEnhancedMediaSessionswoTranscodingexceedssystemcapability1.3.6.1.4.1.177.15.2.196622

    Enhanced Media Sessions w/o Transcoding exceeds system capability.

    GeneralSystem;Service;PodName;ContainerTypeMinor
    • Proxy Local SRTP Media Sessions of [number] licenses exceeds the capability of the system of [number] (Allocated Media Ports).
    315AlarmuxAlmLicensedRTPProxysessionsexceedsystemcapability1.3.6.1.4.1.177.15.2.196623Licensed RTP Proxy sessions exceed system capability.GeneralSystem;Service;PodName;ContainerTypeMinor
    • SIP RTP Proxy Sessions of [number] licenses exceeds the capability of the system of [number] licenses.
    316AlarmuxAlmLicensedVideosessionsexceedsystemcapability1.3.6.1.4.1.177.15.2.196624Licensed Video sessions exceed system capability.GeneralSystem;Service;PodName;ContainerTypeMinor
    • SIP Video Sessions of [number] licenses exceeds the capability of the system of [number] licenses. As a fix, obtain a license with correct number of SIP Video Sessions.
    317AlarmuxAlmLicensedHighCapacity250sessionsexceedsystemcapability1.3.6.1.4.1.177.15.2.196625Licensed High Capacity (250+) sessions exceed system capacityGeneralSystem;Service;PodName;ContainerTypeMinor
    • SIP High Capacity (250+) Sessions of [number] licenses exceeds the capability of the system of [number] licenses.
    • As a fix, obtain a license with correct number of SIP High Capacity Sessions.
    318AlarmuxAlmSIPHighCapacity250Licenserequired1.3.6.1.4.1.177.15.2.196626SIP High Capacity (250+) License required.GeneralSystem;Service;PodName;ContainerTypeMinor
    • The license includes 250 or more SIP Sessions but no High Capacity Enabled license.
    • Obtain a High Capacity Enabled license to use these additional sessions.
    319AlarmuxAlmNonAzureVMLicenseRejected1.3.6.1.4.1.177.15.2.196627Non-Azure VM License RejectedGeneralSystem;Service;PodName;ContainerTypeCritical(tick)
    • Submitted license key does not include Azure enablement flag.
    • Azure-related enablement flag must be included for an Azure-based
      Spacevars
      0series3
       instance to accept and enable newly acquired features.
    • Please consult product documentation for rectification.
    320EventuxAlmAzureLicenseInstalled1.3.6.1.4.1.177.15.2.196628Azure License InstalledGeneralSystem;Service;PodName;ContainerType
    • An Azure-enabled license has been successfully installed.
    321AlarmuxAlmTrialLicenseExpired1.3.6.1.4.1.177.15.2.196629Trial License ExpiredGeneralSystem;Service;PodName;ContainerTypeCritical(tick)
    • The trial period has expired.
    • Please obtain and install a production license to enable features on the 
      Spacevars
      0series3
      .
    322AlarmuxAlmObsoleteVersion2LicensePresent1.3.6.1.4.1.177.15.2.196630Obsolete Version 2 License PresentGeneralSystem;Service;PodName;ContainerTypeCritical(tick)
    • License Version 2 is unsupported.
    • Please contact Ribbon Support for a free feature equivalent License Version 3 immediately.
    • Roll back to the previous partition until this license is available.
    323AlarmuxAlmLicensedSILKTranscodedMediaSessionsexceedssystemcapability1.3.6.1.4.1.177.15.2.196631License SILK Transcoded media Sessions exceeds system capacityGeneralSystem;Service;PodName;ContainerTypeMinor
    • SILK Transcoding Sessions of [number] licenses exceeds the capability of the system of [number] (Allocated Media Ports).
    324AlarmuxAlmLicensedSIPRECSessionsexceedssystemcapability1.3.6.1.4.1.177.15.2.196632

    Licensed SIPREC Sessions exceeds system capability.

    GeneralSystem;Service;PodName;ContainerTypeMinor
    • SIPREC Sessions of [number] licenses exceeds the capability of the system of [number].
    325AlarmuxAlmOnlineLicenseModeConflict1.3.6.1.4.1.177.15.2.196633

    Online License Mode Conflict

    GeneralSystem;Service;PodName;ContainerTypeMajor(tick)
    • Management platform indicates NWDL mode, but no NWDL license received.
    • Review the management platform license server to resolve.
    326EventuxAlmNWDLLicenseApplied1.3.6.1.4.1.177.15.2.196634NWDL License AppliedGeneralSystem;Service;PodName;ContainerType
    • NWDL license applied.
    • This clears the online license mode conflict alarm.
    327AlarmuxAlmLicenseFeatureExpired1.3.6.1.4.1.177.15.2.196635License Feature ExpiredGeneralSystem;Service;PodName;ContainerTypeMinor
    • Feature: [feature string] : [line ID] expired.
    • Please check the Current License page.
    328AlarmuxAlmOnlineLicensesInvalidated1.3.6.1.4.1.177.15.2.196636Online Licenses InvalidatedGeneralSystem;Service;PodName;ContainerTypeCritical
    • Invalidating [license type] licenses.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    5

    1

    Alarm

    uxAlmASMUnreachable1.3.6.1.4.1.177.15.2.327681

    ASM Unreachable

    Communication

    SBA Instance;PodName;ContainerType

    Critical

    (tick)

    • ASM system can not be reached, system is down.
    • Check whether the ASM is rebooting.

    5

    2

    Event

    uxAlmClearASMUnreachable1.3.6.1.4.1.177.15.2.327682

    Clear ASM Unreachable

    Communication

    SBA Instance;PodName;ContainerType

    • Clears alarm 'ASM Unreachable'.

    5

    3

    Alarm

    uxAlmASMFailureRecovered1.3.6.1.4.1.177.15.2.327683

    ASM Failure Recovered

    Equipment

    SBA Instance;PodName;ContainerType

    Warning

    • ASM system was previously unreachable, but has come up.
    • This alarm doesn't autoclear so the user can investigate the cause, but the system should be working correctly now.

    5

    4

    Alarm

    uxAlmASMServicesNotRunning1.3.6.1.4.1.177.15.2.327684

    ASM Services Not Running

    Processing

    SBA Instance;PodName;ContainerType

    Critical

    (tick)

    • ASM services are not running, calls through the ASM cannot be placed.

    5

    5

    Event

    uxAlmClearASMServicesNotRunning1.3.6.1.4.1.177.15.2.327685

    Clear ASM Services Not Running

    Processing

    SBA Instance;PodName;ContainerType

    • Clears alarm 'ASM Services Not Running'.

    5

    6

    Alarm

    uxAlmASMServicesRestarted1.3.6.1.4.1.177.15.2.327686

    ASM Services Restarted

    Processing

    SBA Instance;PodName;ContainerType

    Warning

    • ASM Services was previously stopped, but has started.
    • This alarm doesn't autoclear so the user can investigate the cause, but ASM Services should be working correctly now.

    5

    7

    Alarm

    uxAlmASMServiceRestartFailed1.3.6.1.4.1.177.15.2.327687

    ASM Service Restart Failed

    Processing

    SBA Instance;PodName;ContainerType

    Critical

    • The system attempted to restart a failed service on the ASM, service did not start successfully.
    • User interaction is required.

    5

    8

    Event

    uxAlmASMSystemStarted1.3.6.1.4.1.177.15.2.327688

    ASM System Started

    Processing

    SBA Instance;PodName;ContainerType

    • This event is set when the SBA communication system is first established, and usually indicates that the Application Solution Module (ASM) has finished booting.
    • It should come up at system startup, it may come again if the ASM hardware is rebooted.

    5

    9

    Event

    uxAlmASMSystemShuttingdown1.3.6.1.4.1.177.15.2.327689

    ASM System Shutting down

    Processing

    SBA Instance;PodName;ContainerType

    • A planned or deliberate shut down is taking place on the Application Solution Module (ASM).

    5

    10

    Alarm

    uxAlmEthernetLinkDown1.3.6.1.4.1.177.15.2.327690

    Ethernet Link Down

    Equipment

    SBA Instance;Port;PodName;ContainerType

    Major

    (tick)

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

    5

    11

    Event

    uxAlmEthernetLinkUp1.3.6.1.4.1.177.15.2.327691

    Ethernet Link Up

    Equipment

    SBA Instance;Port;PodName;ContainerType

    • Ethernet port specific has recovered link.

    5

    12

    Alarm

    uxAlmASMSBCIPSubnetMismatch1.3.6.1.4.1.177.15.2.327692

    ASM-SBC IP Subnet Mismatch

    Equipment

    SBA Instance;PodName;ContainerType

    Critical

    (tick)

    • The ASM and SBC Edge IP interfaces are in different subnets and cannot communicate.

    5

    13

    Event

    uxAlmASMSBCIPSubnetMatch1.3.6.1.4.1.177.15.2.327693

    ASM-SBC IP Subnet Match

    Equipment

    SBA Instance;PodName;ContainerType

    • The ASM and SBC Edge IP interfaces are in the same subnet and can now communicate.
    514AlarmuxAlmASMQoESQLdatabaseisunreachable1.3.6.1.4.1.177.15.2.327694ASM-QoE SQL database is unreachableCommunicationSBA Instance;PodName;ContainerTypeMajor(tick)
    • The QoE database is unreachable from ASM, make sure Skype for Business Server or Skype/Lync is deployed and Monitoring database is running.
    515EventuxAlmClearASMQoESQLdatabaseisunreachable1.3.6.1.4.1.177.15.2.327695Clear ASM-QoE SQL database is unreachableEquipmentSBA Instance;PodName;ContainerType
    • The QoE database is now reachable from ASM.
    516AlarmuxAlmASMfailedtostoreQoEinformation1.3.6.1.4.1.177.15.2.327696ASM-failed to store QoE informationEquipmentSBA Instance;PodName;ContainerTypeMajor
    • Failed to store the QoE information from ASM.
    517AlarmuxAlmASMSBCCACUpdatefailed1.3.6.1.4.1.177.15.2.327697ASM-SBC CAC Update FailedEquipmentSBA Instance;PodName;ContainerTypeMajor(tick)
    • The ASM hasn't been able to apply the CAC update.
    518EventuxAlmASMSBCCACUpdateapplied1.3.6.1.4.1.177.15.2.327698ASM-SBC CAC Update AppliedEquipmentSBA Instance;PodName;ContainerType
    • ASM-SBC CAC Update applied.
    519AlarmuxAlmThiscopyofASMOperatingSystemisnotgenuine1.3.6.1.4.1.177.15.2.327699This copy of ASM Operating System is not genuineEquipmentSBA Instance;PodName;ContainerTypeCritical
    • ASM Windows Server is not able to activate as genuine Microsoft product.
    • Unlicensed ASM sends the alarm.
    • The alarm is removed after the license key is successfully installed and the ASM module is restarted.
    520AlarmuxAlmASMdriveNFSmountfailure1.3.6.1.4.1.177.15.2.327700ASM drive NFS mount failureEquipmentSBA Instance;PodName;ContainerTypeMajor(tick)
    • NFS mounting of ASM drive failed, make sure ASM module is up and NFS service is running on the ASM module.
    521EventuxAlmClearASMdriveNFSmountfailure1.3.6.1.4.1.177.15.2.327701Clear ASM drive NFS mount failureEquipmentSBA Instance;PodName;ContainerType
    • ASM hard drive is NFS mounted and available.
    522EventuxAlmASMOperatingSystemSuccessfullyActivated1.3.6.1.4.1.177.15.2.327702ASM Operating System Successfully ActivatedEquipmentSBA Instance;PodName;ContainerType
    • ASM Windows Server is activated as genuine Microsoft product.

    5

    23

    Alarm

    uxAlmASMIPaddressconflict1.3.6.1.4.1.177.15.2.327703

    ASM IP Address conflict

    Equipment

    SBA Instance;PodName;ContainerType

    Critical

    (tick)

    • The current ASM IP [ipAddress] is in use by a [address] ('MAC address'), Change the [address] IP 'Is PowerCycle required' and retry.

    5

    24

    Event

    uxAlmClearASMIPaddressconflict1.3.6.1.4.1.177.15.2.327704

    Clear ASM IP address conflict

    Equipment

    SBA Instance;PodName;ContainerType

    • ASM IP address conflict cleared.
    525AlarmuxAlmASMEthernetPortDown1.3.6.1.4.1.177.15.2.327705ASM Ethernet Port DownEquipmentSBA Instance;Port;PodName;ContainerTypeCritical(tick)
    • ASM Ethernet Port has been detected down.
    526EventuxAlmClearASMEthernetPortDown1.3.6.1.4.1.177.15.2.327706Clear ASM Ethernet Port DownEquipmentSBA Instance;Port;PodName;ContainerType
    • ASM Ethernet Port has been detected down is cleared.
    532AlarmuxAlmASMandSBCFirmwaremismatch1.3.6.1.4.1.177.15.2.327712ASM and SBC Firmware mismatchEquipmentSBA Instance;PodName;ContainerTypeMajor(tick)
    • ASM ([SbcCommsVersion]) and SBC ([SBCVersion]) firmware version does not match.
    533EventuxAlmClearASMandSBCFirmwaremismatch1.3.6.1.4.1.177.15.2.327713Clear ASM and SBC Firmware mismatchEquipmentSBA Instance;PodName;ContainerType
    • ASM and SBC firmware version does not match is cleared.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    7

    1

    Event

    uxAlmConfigurationchangeoccurredonActionSet1.3.6.1.4.1.177.15.2.458753

    Configuration change occurred on Action Set

    General

    ActSetTble;PodName;ContainerType

    • Action set modified [id].

    7

    2

    Event

    uxAlmConfigurationchangeoccurredonNormalizationTable1.3.6.1.4.1.177.15.2.458754

    Configuration change occurred on Normalization Table

    General

    NormTble;PodName;ContainerType

    • There is a normalization table number/name that should be printed with this event.

    7

    3

    Event

    uxAlmConfigurationchangeoccurredonRouteTable1.3.6.1.4.1.177.15.2.458755

    Configuration change occurred on Route Table

    General

    RtTble;PodName;ContainerType

    • Routing table modified [id].

    7

    4

    Event

    uxAlmConfigurationchangeoccurredonTransformationTables1.3.6.1.4.1.177.15.2.458756

    Configuration change occurred on Transformation Tables

    General

    TransTble;PodName;ContainerType

    • Transformation table modified [id].

    7

    5

    Alarm

    uxAlmRoutetemporarilydisabled1.3.6.1.4.1.177.15.2.458757

    Route temporarily disabled

    Communication

    RtTble;PodName;ContainerType

    Warning

    (tick)

    • Route temporarily disabled due to signaling group(s) down.

    7

    6

    Event

    uxAlmRouteenabled1.3.6.1.4.1.177.15.2.458758

    Route enabled

    Communication

    RtTble;PodName;ContainerType

    • Route enabled as the signaling group is up.

    7

    7

    Alarm

    uxAlmACallexceededthelimitfornumberofdestinations1.3.6.1.4.1.177.15.2.458759

    A Call exceeded the limit for number of destinations

    Communication

    CallDest;PodName;ContainerType

    Warning

    • Maximum (8) call forks exceeded, no more forks for this destination

    7

    8

    Alarm

    uxAlmCallforkingusedwithnoforkinglicense1.3.6.1.4.1.177.15.2.458760

    Call forking used with no forking license

    Communication

    CallDest;PodName;ContainerType

    Warning

    • Call forking used with no forking license.

    7

    9

    Alarm

    uxAlmInvocationofInvokeActionSetexceededthemaximumnestinglimit1.3.6.1.4.1.177.15.2.458761

    Invocation of InvokeActionSet exceeded the maximum nesting limit

    Communication

    CallDest;PodName;ContainerType

    Warning

    • Maximum (10) nested InvokeActionSet exceeded.

    7

    10

    Event

    uxAlmConfigurationchangeoccurredonCallbackTables1.3.6.1.4.1.177.15.2.458762

    Configuration change occurred on Callback Tables

    General

    CallbackTble;PodName;ContainerType

    • Callback table [id] modified.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    8

    1

    Event

    uxAlmChannelisinservice1.3.6.1.4.1.177.15.2.524289

    Channel is in service

    Communication

    Card;Port;Channel;PodName;ContainerType

    • Channel is up and is in service.
    • This clears the 'Channel out of service' alarm.

    8

    2

    Alarm

    uxAlmChannelisoutofservice1.3.6.1.4.1.177.15.2.524290

    Channel is out of service

    Communication

    Card;Port;Channel;PodName;ContainerType

    Minor

    (tick)

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

    8

    3

    Alarm

    uxAlmEmergencyCallAttempted1.3.6.1.4.1.177.15.2.524291

    Emergency Call Attempted

    Communication

    Number;Extension;IPAddress;PodName;ContainerType

    Minor

    (tick)

    • Specified emergency call is attempted, AttempTime: [time].

    8

    4

    Event

    uxAlmEmergencyCallCompleted1.3.6.1.4.1.177.15.2.524292

    Emergency Call Completed

    Communication

    Number;Extension;IPAddress;PodName;ContainerType

    • Emergency Call completed.
    • The alarm will be cleared after expiry time in emergency status table.
    85AlarmuxAlmQoEReportNotSentDuetoRTCPMediaList1.3.6.1.4.1.177.15.2.524293

    QoE report not sent due to RTCP Media List

    CommunicationSG;PodName;ContainerTypeMinor
    • QoE Report for the Signaling Group not sent.
    • To enable QoE report for this Signaling Group, check the Media List associated with the SG and set RTCP Mode to RTCP-XR.
    86EventuxAlmCallTransferfailedduetocallnotbeinginDSPmode1.3.6.1.4.1.177.15.2.524294Call Transfer failed due to call not being in DSP modeCommunicationCard;Port;Channel;PodName;ContainerType
    • The call is not in DSP mode - hence the call transfer could not be honored.
    • Set Agent Type as Access Mode to pass through the SIP REFER.
    87EventuxAlmCallAttemptfailedduetoMediaModemismatch1.3.6.1.4.1.177.15.2.524295Call Attempt failed due to Media Mode mismatchCommunicationCard;Port;Channel;PodName;ContainerType
    • The call failed due to Media Mode mismatch across SG and Call Route configuration.
    88AlarmuxAlmSGDrained1.3.6.1.4.1.177.15.2.524296SG DrainedCommunicationSG;PodName;ContainerTypeWarning
    • SG set to Drain Mode, all channels are idle.
    89AlarmuxAlmNonEmergencyCallPreemptedduetoanEmergencyCallAttempt1.3.6.1.4.1.177.15.2.524297Non-Emergency Call Preempted due to an Emergency Call AttemptCommunicationCard;Port;Channel;PodName;ContainerTypeMinor
    • Non-Emergency Call Preempted due to an Emergency Call Attempt.
    810Alarm1.3.6.1.4.1.177.15.2.524298Licensed Enhanced Media Sessions with Transcoding count reachedGeneralSystem;Service;PodName;ContainerTypeMinor
    • Number of licensed Enhanced Media Sessions with Transcoding has been reached.
    811Alarm1.3.6.1.4.1.177.15.2.524299SRTP Call Attempted, No License AvailableGeneralSystem;Service;PodName;ContainerTypeMinor
    • Either Enhanced Media Session without Transcoding is not licensed on this node, or the license count has reached zero.
    812AlarmuxAlmNoAMRWidebandlicense1.3.6.1.4.1.177.15.2.524300No AMR Wideband licenseCommunicationSystem;PodName;ContainerTypeMinor
    • AMR Wideband call attempted but not licensed.
    813AlarmuxAlmMaximumCallDurationExceeded1.3.6.1.4.1.177.15.2.524301Maximum Call Duration ExceededCommunicationCallID;PodName;ContainerTypeMinor
    • Maximum call duration exceeded for call and call has been disconnected.
    814AlarmuxAlmCountryCodeUnavailable1.3.6.1.4.1.177.15.2.524302Country Code UnavailableSecuritySystem;PodName;ContainerTypeMajor(tick)
    • Country Code is unavailable. Ribbon Protect Bad Actors detection will be impacted.
    815EventuxAlmCountryCodeAvailable1.3.6.1.4.1.177.15.2.524303Country Code AvailableSecuritySystem;PodName;ContainerType
    • Country Code is Available.
    816AlarmuxAlmLicensedSILKtranscodedmediasessioncountreached1.3.6.1.4.1.177.15.2.524304Licensed SILK transcoded media session count reachedGeneralSystem;Service;PodName;ContainerTypeMinor
    • Number of licensed SILK transcoded media session has been reached.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    9

    1

    Alarm

    uxAlmSIPServerNotResponding1.3.6.1.4.1.177.15.2.589825

    SIP Server not responding

    Communication

    SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType

    Major

    (tick)

    • SIP server has failed to respond and has been taken out of service.
    • This alarm will be cleared by the event 'SIP server became responsive'.

    9

    2

    Alarm

    uxAlmSignalingGroupTakenoutofService1.3.6.1.4.1.177.15.2.589826

    Signaling Group taken out of service

    Communication

    SG;PodName;ContainerType

    Critical

    (tick)

    • All servers in SG have failed.
    • This alarm will be cleared by 'SIP Signaling group enabled' event.

    9

    3

    Event

    uxAlmSignalingGroupDisabled1.3.6.1.4.1.177.15.2.589827

    Signaling Group disabled

    Communication

    SG;PodName;ContainerType

    • Configuration action has changed this Signaling Group from Enabled to Disabled.

    9

    4

    Alarm

    uxAlmSIPTLSServerHandshakeFailure1.3.6.1.4.1.177.15.2.589828

    SIP-TLS Server Handshake Failure

    Security

    TLSProfile;IPAddress;PodName;ContainerType

    Minor

    • TLS server handshake failed with alert code.
    • Action: Refer to Error Alerts in RFC 5246 for the problem.

    9

    5

    Alarm

    uxAlmSIPTLSHandshakeInactivityTimeoutFailure1.3.6.1.4.1.177.15.2.589829

    SIP-TLS Handshake Inactivity Timeout Failure

    Security

    TLSProfile;IPAddress;PodName;ContainerType

    Minor

    • Handshake failed due to no response from peer within specified timeout.
    • Action: Increase the Handshake Inactivity Timeout in TLS Profile.

    9

    6

    Alarm

    uxAlmConfiguredPortNumberMismatch1.3.6.1.4.1.177.15.2.589830

    Configured port number mismatch

    Processing

    SG;IPAddress;Port;PodName;ContainerType

    Minor

    • Discrepancy 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.
    • The DNS SRV port value will take priority over the configured port.

    9

    7

    Event

    uxAlmSIPServerBecameResponsive1.3.6.1.4.1.177.15.2.589831

    SIP Server became responsive

    Communication

    SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType

    • SIP server came up.

    9

    8

    Alarm

    uxAlmSIPclusterwentdown1.3.6.1.4.1.177.15.2.589832

    SIP cluster went down

    Communication

    SIPCluster;PodName;ContainerType

    Major

    (tick)

    • SIP cluster went down.
    • This is due to all the servers in the clusters being unresponsive.
    • This alarm will be cleared by the event 'SIP Cluster Enabled'. 

    9

    9

    Event

    uxAlmSIPClusterEnabled1.3.6.1.4.1.177.15.2.589833

    SIP Cluster enabled

    Communication

    SIPCluster;PodName;ContainerType

    • SIP cluster enabled.

    9

    10

    Event

    uxAlmSIPSignalingGroupEnabled1.3.6.1.4.1.177.15.2.589834

    SIP Signaling group enabled

    Communication

    SG;PodName;ContainerType

    • SIP Signaling group enabled.

    9

    11

    Alarm

    uxAlmSIPSignalingGroupDNSFailure1.3.6.1.4.1.177.15.2.589835

    SIP Signaling Group: DNS Failure

    Communication

    SG;PodName;ContainerType

    Major

    (tick)

    • Failed to resolve the FQDN entries in the SIP Signaling Group. [details].

    9

    12

    Event

    uxAlmSIPSignalingGroupFQDNResolved1.3.6.1.4.1.177.15.2.589836

    SIP Signaling Group: FQDN Resolved

    Communication

    SG;PodName;ContainerType

    • Successfully resolved the FQDN of the SIP Signaling group.

    9

    13

    Alarm

    uxAlmSIPServerDNSFailure1.3.6.1.4.1.177.15.2.589837

    SIP Server: DNS Failure

    Communication

    SIPCluster;ServID;PodName;ContainerType

    Major

    (tick)

    • Failed to resolve the SIP server FQDN entries in the SIP Server table. [details].

    9

    14

    Event

    uxAlmSIPServerFQDNResolved1.3.6.1.4.1.177.15.2.589838

    SIP Server: FQDN Resolved

    Communication

    SIPCluster;ServID;PodName;ContainerType

    • SIP Server config FQDN resolved.

    9

    15

    Alarm

    uxAlmSIPCallSessionDNSFailure1.3.6.1.4.1.177.15.2.589839

    SIP call session DNS failure

    Communication

    SG;PodName;ContainerType

    Major

    • Failed to resolve an FQDN with DNS server during a SIP call session.

    9

    16

    Alarm

    uxAlmAcquiringLicenseforRegisterFailed1.3.6.1.4.1.177.15.2.589840

    Acquiring license for Register failed

    Communication

    SG;PodName;ContainerType

    Major

    • Failed to acquire license from License Manager.
    917AlarmuxAlmSessionorOtherResourceLeak1.3.6.1.4.1.177.15.2.589841Session or other resource leakCommunicationSG;PodName;ContainerTypeMajor
    • SIP performs self-check for leaks.
    • Please enable logging for SIP and issue 'show resources' command.
    918AlarmuxAlmFailedtoBindtoNetworkInterface1.3.6.1.4.1.177.15.2.589842Failed to bind to network interfaceCommunicationSG;PodName;ContainerTypeMinor
    • Failed to bind to network interface due to dynamic IP address not available.
    919EventuxAlmSuccessfullyBoundtoNetworkInterface1.3.6.1.4.1.177.15.2.589843Successfully bound to network interfaceCommunicationSG;PodName;ContainerType
    • Successfully bound to network interface.
    • DHCP lease renewed.
    920AlarmuxAlmSIPRegisterServerNotResponding1.3.6.1.4.1.177.15.2.589844SIP Register Server not respondingCommunicationSIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerTypeMajor

    (tick)

    • SIP Register server has failed to respond.
    • This alarm will be cleared by the event 'SIP Regular server became responsive'.
    921EventuxAlmSIPRegisterServerBecameResponsive1.3.6.1.4.1.177.15.2.589845SIP Register Server became  responsiveCommunicationSIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType
    • SIP Register server came up.

    9

    22

    Alarm

    uxAlmRegistrationNotValidReceivedstalefalse1.3.6.1.4.1.177.15.2.589846

    Registration not valid; received stale=false

    Communication

    SG;AorName;PodName;ContainerType

    Major

    (tick)

    • Stale=false/Registration no longer valid due to incorrect credentials.

    9

    23

    Event

    uxAlmConfigChangeforSIPEndpointThatReceivedstalefalse1.3.6.1.4.1.177.15.2.589847

    Config change for SIP endpoint that received stale=false

    Communication

    SG;AorName;PodName;ContainerType

    • Config has changed, clear StaleIsFalse Alarm.

    9

    24

    Alarm

    uxAlmQoENotifyMessageResponseWasNotSuccessful1.3.6.1.4.1.177.15.2.589848

    QoE Notify Message response was not successful

    Communication

    SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType

    Minor

    (tick)

    • QoE Notify Message received a no response or a failed response.
    • This alarm will be cleared by the event 'QoE Notify Message received a successful response'.

    9

    25

    Event

    uxAlmQoENotifyMessageResponseWasSuccessful1.3.6.1.4.1.177.15.2.589849

    QoE Notify Message Response was successful

    Communication

    SG;PodName;ContainerType

    (tick)

    • QOE Notify Message received a successful response.

    9

    26

    Alarm

    uxAlmSystemOverloadDetected1.3.6.1.4.1.177.15.2.589850

    System overload detected

    Communication

    System;Service;PodName;ContainerType

    Minor

    (tick)

    • System processing is overloaded.

    9

    27

    Event

    uxAlmSystemOverloadCleared1.3.6.1.4.1.177.15.2.589851

    System overload cleared

    Communication

    System;Service;PodName;ContainerType

    • System processing resumes standard operation, overload cleared.

    9

    28

    Alarm

    uxAlmMaximumNumberofSIPSessionsReached1.3.6.1.4.1.177.15.2.589852

    Maximum Number of SIP Sessions Reached

    Communication

    SG;PodName;ContainerType

    Minor

    (tick)

    • The maximum number of SIP sessions (calls/register/subscribe) has been reached on the signaling group.
    • Increase the number of SIP Channels for the signaling group.

    9

    29

    Event

    uxAlmMaximumNumberofSIPSessionsAlarmCleared1.3.6.1.4.1.177.15.2.589853

    Maximum Number of SIP Sessions Alarm Cleared

    Communication

    SG;PodName;ContainerType

    • SIP sessions per signaling group is under the maximum limit.

    9

    30

    Alarm

    uxAlmErrorresolvingSRVrecord1.3.6.1.4.1.177.15.2.589854

    Error resolving SRV record

    Communication

    SIPCluster;ServID;PodName;ContainerType

    Major

    (tick)

    • Failed to run SRV record query.
    • Suggested action - confirm that DNS server network is reachable, check SRV and DNS server configuration.

    9

    31

    Event

    uxAlmSRVrecordresolved1.3.6.1.4.1.177.15.2.589855

    SRV record resolved

    Communication

    SIPCluster;ServID;PodName;ContainerType

    None

    • DNS server returned valid SRV record(s).
    932AlarmuxAlmSIPTLSHandshakeNegotiationStartFailure1.3.6.1.4.1.177.15.2.589856SIP-TLS Handshake Negotiation Start FailureSecurityTLSProfile;IPAddress;PodName;ContainerTypeCritical(tick)
    • [server] handshake failed to start with invalid certificate; [connectionID], [portID].
    • Action: confirm that both signed Ribbon SBC Edge Certificate and Trusted CA Certificate exist.
    933EventuxAlmSIPTLSHandshakeNegotiationStartSuccessful1.3.6.1.4.1.177.15.2.589857SIP-TLS Handshake Negotiation Start SuccessfulSecurityTLSProfile;IPAddress;PodName;ContainerTypeNone(tick)
    934EventuxAlmMaximumsupportedSIPSGsreached1.3.6.1.4.1.177.15.2.589858Maximum supported SIP SGs reachedGeneralSystem;Service;PodName;ContainerTypeWarning(tick)
    • SIP signaling group count reached maximum supported limit.
    935EventuxAlmMaximumsupportedSIPSGscleared1.3.6.1.4.1.177.15.2.589859Maximum supported SIP SGs cleared

    General

    System;Service;PodName;ContainerTypeNone
    • SIP signaling group count is under the maximum supported.
    936AlarmuxAlmMaximumnonSIPCallSessionsreached1.3.6.1.4.1.177.15.2.589860Maximum non-SIP call sessions reachedGeneralSystem;Service;PodName;ContainerTypeWarning(tick)
    • Number of SIP non-call sessions is over the system capacity.
    937EventuxAlmMaximumnonSIPCallSessionscleared1.3.6.1.4.1.177.15.2.589861Maximum non-SIP call sessions clearedGeneralSystem;Service;PodName;ContainerTypeNone
    • Number of SIP non-call sessions is under the system capacity.
    938AlarmuxAlmMaximumSIPCallSessionsreached1.3.6.1.4.1.177.15.2.589862Maximum SIP call sessions reachedGeneralSystem;Service;PodName;ContainerTypeWarning(tick)
    • Number of SIP call sessions is over the system capacity.
    939EventuxAlmMaximumSIPCallSessionscleared1.3.6.1.4.1.177.15.2.589863Maximum SIP call sessions clearedGeneralSystem;Service;PodName;ContainerTypeNone
    • Number of SIP call sessions is under the system capacity.
    940AlarmuxAlmBroadsoftSIPCallrerouted1.3.6.1.4.1.177.15.2.589864Broadsoft SIP call re-routedGeneralSG;PodName;ContainerTypeWarning(tick)
    • Broadsoft SIP call re-routed.
    941EventuxAlmBroadsoftSIPCallReroutedcleared1.3.6.1.4.1.177.15.2.589865Broadsoft SIP Call re-routed clearedGeneralSG;PodName;ContainerTypeNone
    • Broadsoft SIP call re-routed cleared.
    942AlarmuxAlmSIPSGListenProtocolandSIPServerHostProtocolmismatch1.3.6.1.4.1.177.15.2.589866SIP SG Listen Protocol and SIP Server Host Protocol mismatchProcessingSIPCluster;ServID;PodName;ContainerTypeMinor
    • Verify that the listen ports and protocols for the SG match those in the server table.
    943AlarmuxAlmConfigurationErrorSIPSGandServerProtocolMismatch1.3.6.1.4.1.177.15.2.589867Configuration Error: SIP SG and Server Protocol MismatchProcessingSIPCluster;ServerID or SIPCluster;ServID;PodName;ContainerTypeMajor
    • Verify that the listen ports and protocols for the SG match those in the server table.
    944AlarmuxAlmSIPTLSClientHandshakeFailure1.3.6.1.4.1.177.15.2.589868SIP-TLS Client Handshake FailureSecurityTLSProfile;IPAddress;PodName;ContainerTypeMinor(tick)
    • TLS client handshake failed with alert code.
    • Action: Refer to Error Alerts in RFC 5246 for the problem.
    945EventuxAlmSIPTLSHandshakeInactivityTimeoutCleared1.3.6.1.4.1.177.15.2.589869SIP-TLS Handshake Inactivity Timeout ClearedSecurityTLSProfile;IPAddress;PodName;ContainerType
    • Handshake response was received within specified timeout.
    • This event clears the 'SIP-TLS Handshake Inactivity Timeout Failure' alarm.
    946EventuxAlmSIPTLSServerHandshakeFailureCleared1.3.6.1.4.1.177.15.2.589870SIP-TLS Server Handshake Failure ClearedSecurityTLSProfile;IPAddress;PodName;ContainerType
    • Handshake failure error alert condition was cleared.
    • This event clears the 'SIP-TLS Server Handshake Failure' alarm. 
    947EventuxAlmSIPTLSClientHandshakeFailureCleared1.3.6.1.4.1.177.15.2.589871SIP-TLS Client Handshake Failure ClearedSecurityTLSProfile;IPAddress;PodName;ContainerType
    • Handshake failure error alert condition was cleared.
    • This event clears the 'SIP-TLS Client Handshake Failure' alarm. 
    948AlarmuxAlmSkypeLyncPresenceServerResponseFailure1.3.6.1.4.1.177.15.2.589872CommunicationSIPCluster;PodName;ContainerTypeMinor(tick)
    • A Presence Publish Request has been sent to the configured Lync Presence Front End and has received no response or a failed response.
    949AlarmuxAlmSkypeLyncPresenceServerResponseFailureCleared1.3.6.1.4.1.177.15.2.589873Skype/Lync Presence Server Response Failure ClearedCommunicationSIPCluster;PodName;ContainerTypeMinor(error)
    • A presence server that previously was unreachable has successfully sent a message that the SBC has received.
    950AlarmuxAlmSIPRequestfromUntrustedIP1.3.6.1.4.1.177.15.2.589874SIP Request from Untrusted IPSecurityIPAddress;PodName;ContainerType Minor
    • An INVITE message was received from a host without a matching Federated IP.
    951AlarmuxAlmSIPRequestfromUntrustedIPCleared1.3.6.1.4.1.177.15.2.589875SIP Request from Untrusted IP ClearedGeneralIPAddress;PodName;ContainerTypeMajor
    • Source IP is added to the list of federated IP addresses.
    952AlarmuxAlmReSyncmessagereceivedonSGnotselectedforAutoConfigtask1.3.6.1.4.1.177.15.2.589876Resync message received on SG, not selected for Auto Config task.ProcessingSG;PodName;ContainerTypeMajor
    • Check Auto configuration Task settings and verify that the Signaling Group selected is correct.
    953AlarmuxAlmMaximumNumberofSkypeLyncPresenceSessionsReached1.3.6.1.4.1.177.15.2.589877Maximum Number of Skype/Lync Presence Sessions ReachedCommunicationSG;PodName;ContainerTypeMinor(tick)
    • The maximum number of 500 concurrent SIP Publish sessions for Presence has been reached.
    • Skype/Lync Presence processing will be suspended until the number of concurrent sessions drops below 500 limit.
    954EventuxAlmMaximumNumberofS4BPresencePublishSessionsAlarmCleared1.3.6.1.4.1.177.15.2.589878Maximum Number of S4B Presence Publish Sessions Alarm ClearedCommunicationSG;PodName;ContainerType(tick)
    • SIP Publish sessions for S4B Presence is under the maximum limit.
    955AlarmuxAlmEnableMonitoringonSkypePresenceServerforbetterreliability1.3.6.1.4.1.177.15.2.589879Enable Monitoring on Skype Presence Server for better reliabilityCommunicationSIPCluster;PodName;ContainerTypeMinor(tick)
    • Enable Monitoring on Skype Presence Server for better reliability.
    956EventuxAlmMonitoringonSkypePresenceServerhasbeenenabled1.3.6.1.4.1.177.15.2.589880Monitoring on Skype Presence Server has been enabledCommunicationSIPCluster;PodName;ContainerType
    • Monitoring on Skype Presence Server has been enabled.
    957AlarmuxAlmTheSIPVoiceQualityServerConnectionisBroken1.3.6.1.4.1.177.15.2.589881The SIP Voice Quality Server Connection is BrokenCommunicationProtocol;IPAddress;Port;PodName;ContainerTypeMajor(tick)
    • Suggested Action: Verifying the IP, Port, Protocol, and Certificate (if TLS) are Correct.
    958EventuxAlmTheSIPVoiceQualityServerConnectionisResumed1.3.6.1.4.1.177.15.2.589882The SIP Voice Quality Server Connection is ResumedCommunicationProtocol;IPAddress;Port;PodName;ContainerType
    • The SIP Voice Quality Server Connection is Resumed.
    959AlarmuxAlmTheVoiceQualityNotifyRejectedbytheSIPVoiceQualityServer1.3.6.1.4.1.177.15.2.589883The Voice Quality Notify Rejected by the SIP Voice Quality ServerCommunicationIPAddress;Port;PodName;ContainerTypeWarning(tick)
    • Suggested Action: Examining the Notify Response Code and the Reason Header (if included) to understand why it was rejected.
    960AlarmuxAlmTheVoiceQualityNotifyAcceptbyTheSIPVoiceQualityServer1.3.6.1.4.1.177.15.2.589884The Voice Quality Notify Accept by the SIP Voice Quality ServerCommunicationIPAddress;Port;PodName;ContainerType
    • The Voice Quality Notify has been accepted by the SIP Voice Quality Server.
    961AlarmuxAlmFailedtoResolvetheFQDNoftheSIPVoiceQualityServer1.3.6.1.4.1.177.15.2.589885Failed to Resolve the FQDN of the SIP Voice Quality ServerCommunicationIPAddress;PodName;ContainerTypeWarning
    • Failed to Resolve FQDN of the SIP Voice Quality Server.
    • Suggested action - confirm the DNS access and FQDN.
    962EventuxAlmtheSIPVoiceQualityServerFQDNhasbeenResolved1.3.6.1.4.1.177.15.2.589886The SIP Voice Quality Server FQDN has been ResolvedCommunicationIPAddress;PodName;ContainerType
    • The SIP Voice Quality Server FQDN has been resolved.
    963AlarmuxAlmConfiguredRegistrationLimitreached1.3.6.1.4.1.177.15.2.589887Configured Registration Limit ReachedCommunicationSIPRegistrarTable;PodName;ContainerTypeWarning(tick)
    • Configured Registration Limit reached.
    • New SIP Registrations will be rejected until the number of registered users drops below maximum number of users configured for the Registrar.
    964EventuxAlmConfiguredRegistrationLimitCleared1.3.6.1.4.1.177.15.2.589888Configured Registration Limit ClearedCommunicationSIPRegistrarTable;PodName;ContainerType
    • Configured Registration Limit cleared.
    965AlarmuxAlmSignalingMediasourceIPissettoAuto1.3.6.1.4.1.177.15.2.589889Signaling/Media source IP is set to AutoCommunicationSG;PodName;ContainerTypeMinor(tick)
    • Signaling/Media source IP is set to Auto and default route uses Admin interface.
    966EventuxAlmSignalingMediasourceIPissettoAutocleared1.3.6.1.4.1.177.15.2.589890Signaling/Media source IP is set to Auto clearedCommunicationSG;PodName;ContainerType
    • Signaling/Media source IP is set to Auto cleared.
    967AlarmuxAlmSIPRecordingServerNotResponding1.3.6.1.4.1.177.15.2.589891SIP Recording Server Not RespondingCommunicationSIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerTypeMajor(tick)
    • SIP Recording server has failed to respond and has been taken out of service.
    • This alarm will be cleared by the event 'SIP Recording server became responsive'.
    968EventuxAlmSIPRecordingServerBecameResponsive1.3.6.1.4.1.177.15.2.589892SIP Recording Server Became ResponsiveCommunication
    • SIP Recording server came up.
    969AlarmuxAlmSCSLBconnectionisdown1.3.6.1.4.1.177.15.2.589893SC-SLB connection is downCommunicationSystem;PodName;ContainerTypeCritical(tick)
    • Signaling container connection with SLB container is down.
    970EventuxAlmSCSLBconnectionisup1.3.6.1.4.1.177.15.2.589894SC-SLB connection is upCommunicationSystem;PodName;ContainerType
    • Signaling container connection with SLB container is up.
    971AlarmuxAlmSCCACconnectionisdown1.3.6.1.4.1.177.15.2.589895SC-CAC connection is downCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • Signaling container connection with CAC Manager is Down.
    • Node: [nodename].
    • Login into CAC Manager Pod debug CLI to verify current operational status.
    972EventuxAlmSCCACconnectionisup1.3.6.1.4.1.177.15.2.589896SC-CAC connection is upCommunicationSystem;PodName;ContainerType
    • Signaling container connection with CAC Manager is Up.
    • Node: [nodename].
    973AlarmuxAlmCallAccessControlDenied1.3.6.1.4.1.177.15.2.589897Call Access Control DeniedCommunicationSG;PodName;ContainerTypeWarning(tick)
    • Call Access Control Denied Over [num] percent calls: Rejects: [num] Timeouts: [num] Sendfail: [num] Unknown: [num].
    974AlarmuxAlmSLBDiscoveryFailure1.3.6.1.4.1.177.15.2.589898SLB Discovery FailureCommunicationSystem;PodName;ContainerTypeCritical(tick)
    • SLB discovery failure because of kubeapi failure.
    975EventuxAlmSLBDiscoverySuccess1.3.6.1.4.1.177.15.2.589899SLB Discovery SuccessCommunicationSystem;PodName;ContainerTypeMajor
    • SLB Discovery Success.
    976AlarmuxAlmMediaIPAssociationfailed1.3.6.1.4.1.177.15.2.589900Media IP Associated failedCommunicationInterface;PodName;ContainerTypeMajor
    • Public IP Association to SC failed.
    977EventuxAlmMediaIpAssociationsuccessful1.3.6.1.4.1.177.15.2.589901Media IP Association SuccessfulCommunicationInterface;PodName;ContainerType
    • Public IP Association to SC successful: [ip address].
    978AlarmuxAlmSignalingContainerMemoryreachedThreshold1.3.6.1.4.1.177.15.2.589902Signaling Container Memory reached ThresholdCommunicationInterface;PodName;ContainerTypeMajor(tick)
    • Signaling container memory reached above [percent] percent threshold.
    979EventuxAlmSignalingContainerMemoryRechedBelowThreshold1.3.6.1.4.1.177.15.2.589903Signaling Container Memory Reched Below ThresholdCommunicationInterface;PodName;ContainerType
    • Signaling container memory reached below threshold.
    980EventuxAlmCallAccessControlDeniedCleared1.3.6.1.4.1.177.15.2.589904Call Access Control Denied ClearedCommunicationSG;PodName;ContainerType
    • Call Access Control Denied condition cleared.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    10

    1

    Alarm

    uxAlmDChanneldown1.3.6.1.4.1.177.15.2.655361

    D-Channel down

    Communication

    Card;Port;PodName;ContainerType

    Critical

    (tick)

    • The D-channel (layer 2) is out of service..

    10

    2

    Event

    uxAlmDChannelup1.3.6.1.4.1.177.15.2.655362

    D-Channel up

    Communication

    Card;Port;PodName;ContainerType

    • The D-channel (layer 2) is in service..

    10

    3

    Alarm

    uxAlmCallreleasedduetochannelrestartbyfarend1.3.6.1.4.1.177.15.2.655363

    Call released due to channel restart by far end

    Communication

    Card;Port;Channel;PodName;ContainerType

    Minor

    • Call released as the ISDN channel has been restarted by far end.

    ID

    Sub-ID

    Type

    MIB Trap  NameOID

    Default Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    11

    1

    Alarm

    uxAlmPortdisabledbyoperator1.3.6.1.4.1.177.15.2.720897

    Port disabled by operator

    Communication

    Card;Port;PodName;ContainerType

    Warning

    (tick)

    • Port is placed Out of Service by operator.

    11

    2

    Event

    uxAlmPortenabledbyoperator1.3.6.1.4.1.177.15.2.720898

    Port enabled by operator

    Communication

    Card;Port;PodName;ContainerType

    • Port is placed back in Service by operator.

    11

    3

    Alarm

    uxAlmDS1LoopbackEnter1.3.6.1.4.1.177.15.2.720899

    DS1 Loopback Enter

    Communication

    Card;Port;PodName;ContainerType

    Critical

    (tick)

    • The physical layer is in loopback state.

    11

    4

    Event

    uxAlmDS1LoopbackExit1.3.6.1.4.1.177.15.2.720900

    DS1 Loopback Exit

    Communication

    Card;Port;PodName;ContainerType

    • The physical layer is out of loopback state.

    11

    5

    Alarm

    uxAlmRedAlarmLossofSignal1.3.6.1.4.1.177.15.2.720901

    Red Alarm - Loss of Signal

    Communication

    Card;Port;PodName;ContainerType

    Critical

    (tick)

    • The physical layer has detected a Red (LOS) alarm.

    11

    6

    Event

    uxAlmRedAlarmLossofSignalcleared1.3.6.1.4.1.177.15.2.720902

    Red Alarm - Loss of Signal cleared

    Communication

    Card;Port;PodName;ContainerType

    • The physical layer RED alarm (LOS) is cleared..

    11

    7

    Alarm

    uxAlmRedAlarmLossofFrame1.3.6.1.4.1.177.15.2.720903

    Red Alarm - Loss of Frame

    Communication

    Card;Port;PodName;ContainerType

    Critical

    (tick)

    • The physical layer has detected a Red (LOF) alarm.

    11

    8

    Event

    uxAlmRedAlarmLossofFramecleared1.3.6.1.4.1.177.15.2.720904

    Red Alarm - Loss of Frame cleared

    Communication

    Card;Port;PodName;ContainerType

    • The physical layer RED alarm (LOF) is cleared.

    11

    9

    Alarm

    uxAlmBlueAlarm1.3.6.1.4.1.177.15.2.720905

    Blue Alarm

    Communication

    Card;Port;PodName;ContainerType

    Critical

    (tick)

    • The physical layer has detected a BLUE alarm.

    11

    10

    Event

    uxAlmBlueAlarmCleared1.3.6.1.4.1.177.15.2.720906

    Blue Alarm Cleared

    Communication

    Card;Port;PodName;ContainerType

    • The physical layer BLUE alarm is cleared.

    11

    11

    Alarm

    uxAlmYellowAlarm1.3.6.1.4.1.177.15.2.720907

    Yellow Alarm

    Communication

    Card;Port;PodName;ContainerType

    Critical

    (tick)

    • The physical layer has detected a YELLOW alarm.

    11

    12

    Event

    uxAlmYellowAlarmCleared1.3.6.1.4.1.177.15.2.720908

    Yellow Alarm Cleared

    Communication

    Card;Port;PodName;ContainerType

    • The physical layer YELLOW alarm is cleared.

    11

    13

    Alarm

    uxAlmPortdisabledasportnotfoundonDS11.3.6.1.4.1.177.15.2.720909

    Port disabled as port not found on DS1

    Communication

    Card;Port;PodName;ContainerType

    Critical

    • Port is now marked as disabled because the corresponding port was not present on the DS1 physical hardware.

    11

    14

    Alarm

    uxAlmClockrecoveryswitchedtoportconfiguredassecondary1.3.6.1.4.1.177.15.2.720910

    Clock recovery switched to port configured as secondary

    Communication

    System;PodName;ContainerType

    Critical

    (tick)

    • System has switched over to secondary clock recovery port as primary is lost.

    11

    15

    Event

    uxAlmClockrecoveryswitchovertosecondaryportcleared1.3.6.1.4.1.177.15.2.720911

    Clock recovery switchover to secondary port cleared

    Communication

    System;PodName;ContainerType

    • Secondary clock recovery alarm is being cleared as primary clock is recovered.

    11

    16

    Alarm

    uxAlmClockrecoveryswitchedtofreerunclock1.3.6.1.4.1.177.15.2.720912

    Clock recovery switched to freerun clock

    Communication

    System;PodName;ContainerType

    Critical

    (tick)

    • System has switched over to QF free-run clock as both primary/secondary recovery clocks are invalid.

    11

    17

    Event

    uxAlmClockrecoveryswitchovertofreerunclockcleared1.3.6.1.4.1.177.15.2.720913

    Clock recovery switchover to freerun clock cleared

    Communication

    System;PodName;ContainerType

    • Free-run clock recovery alarm is being cleared as primary clock is recovered.

    11

    18

    Alarm

    uxAlmLinecardnotdetected1.3.6.1.4.1.177.15.2.720914

    Line card not detected

    Communication

    Card;PodName;ContainerType

    Warning

    (tick)

    • Line card not detected.

    11

    19

    Event

    uxAlmLinecarddetected1.3.6.1.4.1.177.15.2.720915

    Line card detected

    Communication

    Card;PodName;ContainerType

    • Line card is detected.

    11

    20

    Alarm

    uxAlmPortdisabledforrelaypassthroughstateactivation1.3.6.1.4.1.177.15.2.720916

    Port disabled for relay passthrough state activation

    Communication

    Card;Port;PodName;ContainerType

    Warning

    (tick)

    • Port is now marked as disabled for activated relay passthrough state.

    11

    21

    Event

    uxAlmPortenabledforrelayonlinestateactivation1.3.6.1.4.1.177.15.2.720917

    Port enabled for relay online state activation

    Communication

    Card;Port;PodName;ContainerType

    • Port is now marked as enabled for activated relay online state.

    11

    22

    Alarm

    uxAlmLayer1down1.3.6.1.4.1.177.15.2.720918

    Layer 1 down

    Communication

    Card;Port;PodName;ContainerType

    Critical

    (tick)

    • The physical layer has detected layer 1 down due to state conditions that results in non-operational state of the BRI port.

    11

    23

    Event

    uxAlmLayer1up1.3.6.1.4.1.177.15.2.720919

    Layer 1 up

    Communication

    Card;Port;PodName;ContainerType

    • The physical layer 1 down alarm is cleared with operational state of the BRI port.

    11

    24

    Alarm

    uxAlmPortdisabledasportnotfoundonanalogcard1.3.6.1.4.1.177.15.2.720920

    Port disabled as port not found on analog card

    Communication

    Card;Port;PodName;ContainerType

    Critical

    • Port is now marked as disabled because the corresponding port was not present on the analog physical hardware.

    11

    25

    Alarm

    uxAlmPortsdisabledforrelaypassthrustatechgonanalogrelaycards1.3.6.1.4.1.177.15.2.720921

    Ports disabled for relay pass thru state chg on analog relay cards

    Communication

    System;Card;Card;PodName;ContainerType

    Warning

    (tick)

    • Ports are now marked as disabled for activated relay passthrough state on analog FXS/FXO card pair.

    11

    26

    Event

    uxAlmPortsenabledforrelayonlinestatechangeonanalogrelaycardpairs1.3.6.1.4.1.177.15.2.720922

    Ports enabled for relay online state change on analog relay card pairs

    Communication

    System;Card;Card;PodName;ContainerType

    • Ports are now marked as enabled for activated relay passthrough state on analog FXS/FXO card pair.

    11

    27

    Alarm

    uxAlmPortstatusdowndetected1.3.6.1.4.1.177.15.2.720923

    Port status down detected

    Communication

    Card;Port;PodName;ContainerType

    Warning

    (tick)

    • Line down condition detected due to no battery.

    11

    28

    Event

    uxAlmPortstatusup1.3.6.1.4.1.177.15.2.720924

    Port status up

    Communication

    Card;Port;PodName;ContainerType

    • Line down condition is cleared.

    11

    29

    Alarm

    uxAlmPortdisabledasportnotfoundonBRI1.3.6.1.4.1.177.15.2.720925

    Port disabled as port not found on BRI

    Communication

    Card;Port;PodName;ContainerType

    Critical

    • Port is now marked as disabled because the corresponding port was not present on the BRI physical hardware.

    11

    30

    Alarm

    uxAlmSystemnotoperational1.3.6.1.4.1.177.15.2.720926

    System not operational

    Communication

    System;PodName;ContainerType

    Critical

    • System not operational because DSP cannot be initialized.
    • Contact Ribbon Service with the information in this alarm.
    1131AlarmuxAlmDS1syncfailure1.3.6.1.4.1.177.15.2.720927DS1 sync failureCommunicationCard;Port;PodName;ContainerTypeCritical(tick)
    • DS1 sync failure could be due to mismatching line configuration.
    • Suggested Action: Disable "Admin State" of unused ports to avoid performance impact.
    1132EventuxAlmDS1syncfailurecleared1.3.6.1.4.1.177.15.2.720928DS1 sync failure clearedCommunicationCard;Port;PodName;ContainerType
    • DS1 sync failure cleared.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    12

    1

    Alarm

    uxAlmDSPnotcomingup1.3.6.1.4.1.177.15.2.786433

    DSP not coming up

    Equipment

    DSP;PodName;ContainerType

    Critical

    (tick)

    • DSP board [boardType] could not be brought up.
    • If the DSP does not come up, contact Ribbon Service with the information in this alarm.

    12

    2

    Alarm

    uxAlmDSPreset1.3.6.1.4.1.177.15.2.786434

    DSP reset

    Equipment

    DSP;PodName;ContainerType

    Major

    (tick)

    • This alarm will be generated if a DSP encounters a fatal error condition and has to be reinitialized.

    12

    3

    Event

    uxAlmDSPCardisUP1.3.6.1.4.1.177.15.2.786435

    DSP Card is UP

    Equipment

    DSP;PodName;ContainerType

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

    12

    4

    Event

    uxAlmDSPeventfailure1.3.6.1.4.1.177.15.2.786436

    DSP Event Failure

    Processing

    System;Service;PodName;ContainerType

    • Call related command on Connection ID [value] failed with error code [value].
    125AlarmuxAlmRTPRTCPPortRangeInvalid1.3.6.1.4.1.177.15.2.786437RTP/RTCP Port Range InvalidEquipmentSystem;Service;PodName;ContainerTypeCritical(tick)
    • This alarm is generated if a RTP/RTCP port range is found to be invalid.
    • This condition should be resolved by reconfiguring the RTP/RTCP Port Range under Media System Configuration.
    126EventuxAlmRTPRTCPPortRangeInvalidCleared1.3.6.1.4.1.177.15.2.786438RTP/RTCP Port Range Invalid ClearedEquipmentSystem;Service;PodName;ContainerType
    • This event will clear the "RTP/RTCP Port Range Invalid" alarm.
    127AlarmuxAlmMSCMediaStreamModeMismatch1.3.6.1.4.1.177.15.2.786439MSC Media Stream Mode MismatchGeneralSystem;Service;PodName;ContainerTypeMinor
    • This alarm is generated when there is a mismatch in media stream mode of the two call legs.
    • Suggested Action: Match "Audio/Fax Stream Mode" settings and clear alarm.
    128AlarmuxAlmMusicOnHoldfailedduetoimproperlyconfiguredsource1.3.6.1.4.1.177.15.2.786440Music-On-Hold failed due to improperly configured sourceCommunicationSystem;Service;PodName;ContainerTypeMinor
    • Music-On-Hold enabled; source is not properly configured. 
    • If source is set to File: upload a file, disable music-on-hold or switch source to an FXS port.
    129AlarmuxAlmFailedtoAllocateRTPports1.3.6.1.4.1.177.15.2.786441Failed to allocate RTP PortsCommunicationSystem;Service;PodName;ContainerTypeMajor
    • This alarm is generated if we exceed the configured number of RTP/RTCP port pairs.
    • This condition should be resolved by increasing the "Number of Port Pairs" in Media System Configuration.
    1210AlarmuxAlmVirtDSPeventfailure1.3.6.1.4.1.177.15.2.786442Virt DSP event failureCommunicationSystem;Service;PodName;ContainerTypeMinor
    • Virt DSP Command Failure: Conf=[conf] Type=[type] Error=[error].
    1211AlarmuxAlmMSCDTLSServerHandshakeFailure1.3.6.1.4.1.177.15.2.786443

    MSC-DTLS Server Handshake Failure

    Security

    DTLSProfile;IPAddress;PodName;ContainerType

    Minor(tick)
    • DTLS server handshake failed with alert code.
    • Action: Refer to Error Alerts in RFC 5246 for the problem.
     1212EventuxAlmMSCDTLSServerHandshakeFailureCleared1.3.6.1.4.1.177.15.2.786444

    MSC-DTLS Server Handshake Failure Cleared

    Security

    DTLSProfile;IPAddress;PodName;ContainerType

    • Handshake failure error alert condition was cleared.
    • This event clears the 'MSC-DTLS Server Handshake Failure' alarm.
     12 13AlarmuxAlmMSCDTLSHandshakeInactivityTimeoutFailure1.3.6.1.4.1.177.15.2.786445

    MSC-DTLS Handshake Inactivity Timeout Failure

    Security

    DTLSProfile;IPAddress;PodName;ContainerType

    Minor  (tick)
    • DTLS handshake failed due to no response from peer within specified timeout.
    • Action: Increase the Handshake Inactivity Timeout in DTLS Profile.
     12 14EventuxAlmMSCDTLSHandshakeInactivityTimeoutCleared1.3.6.1.4.1.177.15.2.786446

    MSC-DTLS Handshake Inactivity Timeout Cleared 

    Security

    DTLSProfile;IPAddress;PodName;ContainerType

    • Handshake response was received within specified timeout.
    • This event clears the 'MSC-DTLS Handshake Inactivity Timeout Failure' alarm. 
     12 15AlarmuxAlmMSCDTLSHandshakeNegotiationStartFailure1.3.6.1.4.1.177.15.2.786447

    MSC-DTLS Handshake Negotiation Start Failure

    Security

    DTLSProfile;IPAddress;PodName;ContainerType

    Critical (tick)
    • [server] handshake failed to start with invalid certificate; [connectionID], [portID].
    • Action: confirm that both signed Ribbon SBC Edge Certificate and Trusted CA Certificate exist.
     12 16EventuxAlmMSCDTLSHandshakeNegotiationStartSuccessful1.3.6.1.4.1.177.15.2.786448

    MSC-DTLS Handshake Negotiation Start Successful

    Security

    DTLSProfile;IPAddress;PodName;ContainerType

    • DTLS Handshake response was started with valid certificate on local and remote gateway.
    • This event clears the 'MSC-DTLS Handshake Negotiation Start Failure' alarm.
     12 17AlarmuxAlmMSCDTLSClientHandshakeFailure1.3.6.1.4.1.177.15.2.786449

    MSC-DTLS Client Handshake Failure

    Security

    DTLSProfile;IPAddress;PodName;ContainerType

    Minor (tick)
    • DTLS client handshake failed with alert code.
    • Action: Refer to Error Alerts in RFC 5246 for the problem.
     12 18EventuxAlmMSCDTLSClientHandshakeFailureCleared1.3.6.1.4.1.177.15.2.786450

    MSC-DTLS Client Handshake Failure Cleared

    Security

    DTLSProfile;IPAddress;PodName;ContainerType

    • Handshake failure error alert condition was cleared.
    • This event clears the 'MSC-DTLS Client Handshake Failure' alarm.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    13

    1

    Alarm

    uxAlmTLSOwnServerCertificatewillExpire1.3.6.1.4.1.177.15.2.851969

    TLS Own Server Certificate will Expire

    Security

    CertificateCommonName;PodName;ContainerType

    Major

    (tick)

    • CommonName: [name] StartDate: [startdate] EndDate: [enddate] will expire in a window time.
    • Action: Generate, Export CSR and Import a new signed certificate.

    13

    2

    Alarm

    uxAlmTLSOwnServerCertificatehasExpired1.3.6.1.4.1.177.15.2.851970

    TLS Own Server Certificate has Expired

    Security

    CertificateCommonName;PodName;ContainerType

    Critical

    (tick)

    • CommonName: [name] StartDate: [startdate] EndDate: [enddate] has expired.
    • Action: Generate, Export CSR and Import a new signed certificate.
    133AlarmuxAlmTLSOwnServerCertificateismissing1.3.6.1.4.1.177.15.2.851971TLS Own Server Certificate is missingSecurityCertificateCommonName;PodName;ContainerTypeCritical(tick)
    • This Server certificate is found to be missing or has failed validations.
    • Suggestion Action. Generate, Export CSR and Import a new signed certificate.

    13

    4

    Alarm

    uxAlmTLSSelfSignCertificateGenerationFailed1.3.6.1.4.1.177.15.2.851972

    TLS Self Sign Certificate Generation Failed

    Security

    CertificateCommonName;PodName;ContainerType

    Critical

    • Failed to create a default self signed certificate on the system.

    13

    5

    Event

    uxAlmNewandValidTLSOwnServerCertificateDetected1.3.6.1.4.1.177.15.2.851973

    New and Valid TLS Own Server Certificate Detected

    Security

    CertificateCommonName;PodName;ContainerType

    • Imported and validated common name: [name] StartDate: [startDate] EndDate: [endDate].
    • This event clears the Server Certificate Expiring, Expired and Missing alarms.

    13

    6

    Alarm

    uxAlmTLSTrustedCertificateAuthoritywillExpire1.3.6.1.4.1.177.15.2.851974

    TLS Trusted Certificate Authority will Expire

    Security

    CertificateCommonName;PodName;ContainerType

    Major

    (tick)

    • CommonName: [name] StartDate: [startDate] EndDate: [endDate] will expire in a window time.
    • Action: Obtain and Import a new valid certificate from the CA vendor.

    13

    7

    Alarm

    uxAlmTLSTrustedCertificateAuthorityhasExpired1.3.6.1.4.1.177.15.2.851975

    TLS Trusted Certificate Authority has Expired

    Security

    CertificateCommonName;PodName;ContainerType

    Critical

    (tick)

    • CommonName: [name] StartDate: [startDate] EndDate: [endDate] has expired.
    • Action: Obtain and Import a new valid certificate from the CA vendor.

    13

    8

    Event

    uxAlmTLSTrustedCertificateAuthoritywasDeleted1.3.6.1.4.1.177.15.2.851976

    TLS Trusted Certificate Authority was Deleted

    Security

    CertificateCommonName;PodName;ContainerType

    • The Trusted Certificate Authority is successfully deleted due to the expired or expiring soon validity status.
    139AlarmuxAlmTLSOwnServerCertificateExpiryNotice1.3.6.1.4.1.177.15.2.851977TLS Own Server Certificate Expiry NoticeSecurityCertificateCommonName;PodName;ContainerTypeMinor(tick)
    • CommonName: [name] StartDate: [startDate] EndDate: [endDate] will expire in a window time.
    • Action: Obtain and Import a new valid certificate from the CA vendor.
    1310AlarmuxAlmTLSTrustedCertificateAuthorityExpiryNotice1.3.6.1.4.1.177.15.2.851978TLS Trusted Certificate Authority Expiry NoticeSecurityCertificateCommonName;PodName;ContainerTypeMinor(tick)
    • CommonName: [name] StartDate: [startDate] EndDate: [endDate] has expired.
    • Action: Obtain and Import a new valid certificate from the CA vendor.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    14

    1

    Alarm

    uxAlmInvalidSessionforattemptedrealtimeconnection1.3.6.1.4.1.177.15.2.917505

    Invalid Session for attempted realtime connection

    Security

    IPAddress;PodName;ContainerType

    • If a web-client tries to open a realtime monitor connection with invalid session ID, BMP will generate this alarm.

    14

    2

    Alarm

    uxAlmBMPTLSHandshakeAlertFailure1.3.6.1.4.1.177.15.2.917506

    BMP-TLS Handshake Alert Failure

    Security

    IPAddress;PodName;ContainerType

    Minor

    • This alarm will be generated if TLS Connection failed with an Alert.
    • The connection associated with a TLS Connection ID is terminated.

    14

    3

    Alarm

    uxAlmBMPTLSHandshakeInactivityTimeoutFailure1.3.6.1.4.1.177.15.2.917507

    BMP-TLS Handshake Inactivity Timeout Failure

    Security

    IPAddress;PodName;ContainerType

    Minor

    • This alarm will be generated if there was long period of inactivity during exchange of handshake messages for an associated TLS Connection ID.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    15

    1

    Alarm

    uxAlmInterfaceoperdown1.3.6.1.4.1.177.15.2.983041

    Interface oper down

    Communication

    Port;PodName;ContainerType

    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 administrative state is enabled.
    • Is generated only on the SBC 2000.

    15

    2

    Event

    uxAlmInterfaceoperup1.3.6.1.4.1.177.15.2.983042

    Interface oper up

    Communication

    Port;PodName;ContainerType

    • 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

    uxAlmInterfaceadminup1.3.6.1.4.1.177.15.2.983043

    Interface admin up

    Communication

    LogicalInterface;PodName;ContainerType

    • Is generated when the administrative state of the Logical Interface is configured to be enabled.

    15

    4

    Event

    uxAlmInterfaceadmindown1.3.6.1.4.1.177.15.2.983044

    Interface admin down

    Communication

    LogicalInterface;PodName;ContainerType

    • Is generated when the administrative state of the Logical Interface is configured to be disabled.

    15

    5

    Event

    uxAlmAdminPortoperdown1.3.6.1.4.1.177.15.2.983045

    Admin Port oper down

    Communication

    Port;PodName;ContainerType

    • Is generated when the Admin Port is operationally down (e.g. cable unplugged, mismatched duplex/speed settings).
    • Is applicable to the SBC 2000 only.

    15

    6

    Event

    uxAlmAdminPortoperup1.3.6.1.4.1.177.15.2.983046

    Admin Port oper up

    Communication

    Port;PodName;ContainerType

    • Is generated with the port becomes operational after being in an 'Admin port oper down' state.
    • Is applicable to the SBC 2000 only.

    15

    7

    Event

    uxAlmPortoperdown1.3.6.1.4.1.177.15.2.983047

    Port oper down

    Communication

    Port;PodName;ContainerType

    • This event is generated when the port is operationally down.
    • It is generated for the SBC 1000 only.

    15

    8

    Event

    uxAlmRIPlicensenotenabled1.3.6.1.4.1.177.15.2.983048

    RIP license not enabled

    Communication

    System;PodName;ContainerType

    • RIP feature license is not enabled.

    15

    9

    Event

    uxAlmOSPFlicensenotenabled1.3.6.1.4.1.177.15.2.983049

    OSPF license not enabled

    Communication

    System;PodName;ContainerType

    • OSPF feature license is not enabled.

    15

    10

    Alarm

    uxAlmLinkMonitorPeerDown1.3.6.1.4.1.177.15.2.983050

    Link Monitor Peer down

    Communication

    IPAddress;PodName;ContainerType

    Major

    (tick)

    • Connection to the monitored host or gateway is down.

    15

    11

    Event

    uxAlmLinkMonitorPeerReady1.3.6.1.4.1.177.15.2.983051

    Link Monitor Peer ready

    Communication

    IPAddress;PodName;ContainerType

    (tick)

    • Connection to the monitored host or gateway is established.

    15

    12

    Event

    uxAlmTunnelconnectiondisabledbyoperator1.3.6.1.4.1.177.15.2.983052

    Tunnel connection disabled by operator

    Communication

    NetworkName;PodName;ContainerType

    • Tunnel connection is placed Out of Service by operator.

    15

    13

    Event

    uxAlmTunnelconnectionenabledbyoperator1.3.6.1.4.1.177.15.2.983053

    Tunnel connection enabled by operator

    Communication

    NetworkName;PodName;ContainerType

    • Tunnel connection is placed Back in Service by operator.

    15

    14

    Alarm

    uxAlmTunnellinklost1.3.6.1.4.1.177.15.2.983054

    Tunnel link lost

    Communication

    NetworkName;PodName;ContainerType

    Critical

    (tick)

    • Tunnel lost communication with the peer.
    • This alarm will be cleared by the "Tunnel link restored" event.

    15

    15

    Event

    uxAlmTunnellinkrestored1.3.6.1.4.1.177.15.2.983055

    Tunnel link restored

    Communication

    NetworkName;PodName;ContainerType

    • Tunnel is successfully established with the peer

    15

    16

    Event

    uxAlmIPseclicensenotenabled1.3.6.1.4.1.177.15.2.983056

    IPsec license not enabled

    Communication

    System;PodName;ContainerType

    • IPsec feature license is not enabled.

    15

    17

    Alarm

    uxAlmNegotiatedDuplexityHalf1.3.6.1.4.1.177.15.2.983057

    Negotiated  Duplexity Half

    Communication

    Port;PodName;ContainerType

    Warning

    (tick)

    • Port negotiated duplexity is half.
    • This degrades the performance.

    15

    18

    Event

    uxAlmNegotiatedDuplexityFull1.3.6.1.4.1.177.15.2.983058

    Negotiated Duplexity Full

    Communication

    Port;PodName;ContainerType

    • Port negotiation duplexity is back to full.

    15

    19

    Alarm

    uxAlmPreferredlinkdown1.3.6.1.4.1.177.15.2.983059

    Preferred link down

    Communication

    IPAddress;PodName;ContainerType

    Critical

    (tick)

    • This event is generated when the preferred link is down.

    15

    20

    Event

    uxAlmPreferredlinkready1.3.6.1.4.1.177.15.2.983060

    Preferred link ready

    Communication

    IPAddress;PodName;ContainerType

    • This event is generated when the the preferred link is ready for service.
    • This event automatically clears the 'preferred link down' alarm.

    15

    21

    Alarm

    uxAlmTunnelnotificationfailure1.3.6.1.4.1.177.15.2.983061

    Tunnel Notification failure

    Communication

    NetworkName;PodName;ContainerType

    Critical

    • Tunnel negotiation failed.
    • Suggested Action: Look up the 'Failure Reason' attribute details for the Source in the IPsec Tunnel Table.

    15

    22

    Event

    uxAlmTunnellocalsubnetsarenonnegotiable1.3.6.1.4.1.177.15.2.983062

    Tunnel local subnet(s) are non-negotiable

    Communication

    NetworkName;PodName;ContainerType

    • Local subnets [subnets] failed negotiation as a result of peer config mismatch.

    15

    23

    Event

    uxAlmTunnelremotesubnetsarenonnegotiable1.3.6.1.4.1.177.15.2.983063

    Tunnel remote subnet(s) are non-negotiable

    Communication

    NetworkName;PodName;ContainerType

    • Remote subnets [subnets] failed negotiation as a result of peer config mismatch.
    1524EventuxAlmPortStateLearning1.3.6.1.4.1.177.15.2.983064Port State LearningCommunicationMSTPInstance;Port;PodName;ContainerType
    • MSTP port is in learning state.
    1525EventuxAlmPortStateForwarding1.3.6.1.4.1.177.15.2.983065Port State ForwardingCommunicationMSTPInstance;Port;PodName;ContainerType
    • MSTP port is in forwarding state.
    1526EventuxAlmPortStateDiscarding1.3.6.1.4.1.177.15.2.983066Port State DiscardingCommunicationMSTPInstance;Port;PodName;ContainerType
    • MSTP port is in discarding state.
    1527AlarmuxAlmPacketCaptureStarted1.3.6.1.4.1.177.15.2.983067Packet Capture StartedGeneralSystem;PodName;ContainerTypeWarning
    • Packet capture has started.
    1528EventuxAlmPacketCaptureStopped1.3.6.1.4.1.177.15.2.983068Packet Capture StoppedGeneralSystem;PodName;ContainerType
    • Packet capture has stopped due to [reason].
    1529AlarmuxAlmDuplicateIPv6addressdetected1.3.6.1.4.1.177.15.2.983069Duplicate IPv6 address detectedCommunicationInterface;IPAddress;PodName;ContainerTypeCritical
    • The indicated IPv6 address has been detected as a duplicate address.
    1530EventuxAlmIPaddressconfigured1.3.6.1.4.1.177.15.2.983070IP address configuredCommunicationInterface;IPAddress;PodName;ContainerType
    • This event is generated when an IP address is configured on the node.
    1531EventuxAlmIPaddressremoved1.3.6.1.4.1.177.15.2.983071IP address removedCommunicationInterface;IPAddress;PodName;ContainerType
    • This event is generated when an IP address is removed from the node.
    1532AlarmuxAlmLinkfailoverdetected1.3.6.1.4.1.177.15.2.983072Link failover detectedCommunicationPort;PodName;ContainerTypeMinor
    • Link failover detected, the indicated Ethernet port became active.
    1533AlarmuxAlmMACaddresseshavechanged1.3.6.1.4.1.177.15.2.983073MAC addresses have changedGeneralSystem;PodName;ContainerTypeMajor
    • Some MAC addresses have changed since the last time the system was up.
    • It is recommended to log into console as 'netconfig' user and remap the interfaces as desired.
    1534AlarmuxAlmDomainNameEmpty1.3.6.1.4.1.177.15.2.983074Domain Name EmptyCommunicationSystem;PodName;ContainerTypeMajor
    • Domain Name for Split DNS should not be empty.
    1535AlarmuxAlmACLRuleAdditionFailed1.3.6.1.4.1.177.15.2.983075ACL Rule Addition FailedSecuritySystem;PodName;ContainerTypeMajor(tick)
    • ACL Rule Addition has failed on a SWe Edge Instance.
    1536EventuxAlmACLRuleDeletionSuccessful1.3.6.1.4.1.177.15.2.983076ACL Rule Deletion SuccessfulSecuritySystem;PodName;ContainerType
    • Clear Alarm for ACL Rule Addition Failure.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    16

    1

    Alarm

    uxAlmApplicationServicerestarted1.3.6.1.4.1.177.15.2.1048577

    Application Service restarted

    Processing

    Service;PodName;ContainerType

    Major

    • An SBC Edge Application service was restarted.
    • Contact Ribbon Service with the information in this alarm and any core files present.
    • These can be found in Diagnostics->Restart Report under the 'Core Files' tab.

    16

    2

    Alarm

    uxAlmActivepartitionswitched1.3.6.1.4.1.177.15.2.1048578

    Active partition switched

    Processing

    Partition;PodName;ContainerType

    Major

    • System detected a problem during previous boot cycle, active partition has switched automatically.
    • Suggested Action: Backup the configuration and re-apply the upgrade to the currently inactive partition.

    16

    3

    Alarm

    uxAlmFailedtomountpartition1.3.6.1.4.1.177.15.2.1048579

    Failed to mount partition

    Processing

    Partition;PodName;ContainerType

    Major

    • Mounting failed for partition [number].

    16

    4

    Alarm

    uxAlmFailedtosetactivepartition1.3.6.1.4.1.177.15.2.1048580

    Failed to set active partition

    Processing

    Partition;PodName;ContainerType

    Major

    • Failed to set active partition.
    • Contact Ribbon Service with the information in this alarm.

    16

    5

    Alarm

    uxAlmAttempttorepairbootparametermismatchfailed1.3.6.1.4.1.177.15.2.1048581

    Attempt to repair boot parameter mismatch failed.

    Processing

    Partition;PodName;ContainerType

    Major

    • Attempt to auto repair boot parameters failed.
    • Contact Ribbon Service with the information in this alarm.

    16

    6

    Alarm

    uxAlmBootparametermismatchdetected1.3.6.1.4.1.177.15.2.1048582

    Boot parameter mismatch detected

    Processing

    Partition;PodName;ContainerType

    Major

    • Boot parameter mismatch was detected.
    • Attempting to auto repair.

    16

    7

    Alarm

    uxAlmFailedPoweronmemoryselftest1.3.6.1.4.1.177.15.2.1048583

    Failed Power-on memory self test

    Equipment

    Partition;PodName;ContainerType

    Critical

    • Power-on self test failure.

    16

    8

    Alarm

    uxAlmFailedPoweronCoreSwitchtest1.3.6.1.4.1.177.15.2.1048584

    Failed Power-on Core Switch test

    Equipment

    Partition;PodName;ContainerType

    Critical

    • Power-on self test failure.

    16

    9

    Alarm

    uxAlmFailedPoweronSecondarySwitchtest1.3.6.1.4.1.177.15.2.1048585

    Failed Power-on Secondary Switch test

    Equipment

    Partition;PodName;ContainerType

    Critical

    • Power-on self test failure.

    16

    10

    Alarm

    uxAlmFailedPoweronexternalQuadPHYtest1.3.6.1.4.1.177.15.2.1048586

    Failed Power-on external Quad PHY test

    Equipment

    Partition;PodName;ContainerType

    Critical

    • Power-on self test failure.

    16

    11

    Alarm

    uxAlmFailedPoweronexternalSinglePHYtest1.3.6.1.4.1.177.15.2.1048587

    Failed Power-on external Single PHY test

    Equipment

    Partition;PodName;ContainerType

    Critical

    • Power-on self test failure.

    16

    12

    Alarm

    uxAlmFailedPoweronCPUPHYtest1.3.6.1.4.1.177.15.2.1048588

    Failed Power-on CPU PHY test

    Equipment

    Partition;PodName;ContainerType

    Critical

    • Power-on self test failure.

    16

    13

    Alarm

    uxAlmFailedPoweronTSItest1.3.6.1.4.1.177.15.2.1048589

    Failed Power-on TSI test

    Equipment

    Partition;PodName;ContainerType

    Critical

    • Power-on self test failure.

    16

    14

    Alarm

    uxAlmFailedPoweroninternal5PortPHYtest1.3.6.1.4.1.177.15.2.1048590

    Failed Power-on internal 5-Port PHY test

    Equipment

    Partition;PodName;ContainerType

    Critical

    • Power-on self test failure.

    16

    15

    Event

    uxAlmSystemUpAfterPlannedRestart1.3.6.1.4.1.177.15.2.1048591

    System Up After Planned Restart

    Equipment

    System;PodName;ContainerType

    • System up after planned restart.
    • Reboot reason [reason].

    16

    16

    Alarm

    uxAlmSystemUpAfterUnplannedRestart1.3.6.1.4.1.177.15.2.1048592

    System Up After Unplanned Restart

    Equipment

    System;PodName;ContainerType

    Major

    • System up after unplanned restart.
    • Reboot reason [reason].
    1617AlarmuxAlmEnteredpasswordrecoverymode1.3.6.1.4.1.177.15.2.1048593Entered password recovery modeSecuritySystem;PodName;ContainerTypeMajor
    • SBC has entered password recovery mode.
    1618EventuxAlmExitedpasswordrecoverymode1.3.6.1.4.1.177.15.2.1048594Exited password recovery modeSecuritySystem;PodName;ContainerType
    • SBC has exited password recovery mode.
    1619AlarmuxAlmFailedtomountUSBstoragedevice1.3.6.1.4.1.177.15.2.1048595Failed to mount USB storage deviceEquipmentSystem;Service;PodName;ContainerTypeMajor
    • SBC discovered USB storage.
    • SBC can mount flash drives formatted with FAT32 file system only.
    1620EventuxAlmUSBstoragedeviceconnected1.3.6.1.4.1.177.15.2.1048596USB storage device connectedEquipmentSystem;Service;PodName;ContainerType
    • USB storage device is connected.
    1621AlarmuxAlmUSBstoragedevicedisconnected1.3.6.1.4.1.177.15.2.1048597USB storage device disconnectedEquipmentSystem;Service;PodName;ContainerTypeWarning
    • USB storage device is disconnected.
    • This alarm will be cleared when USB drive is connected.
    1622AlarmuxAlmCriticalapplicationcrash1.3.6.1.4.1.177.15.2.1048598Critical application crashProcessingService;PodName;ContainerTypeCritical
    • A critical SBC Edge application has crashed, and the system will be restarted.
    • Contact Ribbon Service with the information in this alarm and any core files present.
    • These can be found in Diagnostics->Restart Report/Core Files tab.
    1623AlarmuxAlmOlderfirmwaredetected1.3.6.1.4.1.177.15.2.1048599Older firmware detectedProcessingSystem;Service;PodName;ContainerTypeCritical
    • A USB firmware update is available.
    • To perform upgrade, please first load SW release v4.1.1.
    1624EventuxAlmAutoConfigurationsuccessful1.3.6.1.4.1.177.15.2.1048600Auto Configuration successfulEquipmentSystem;Service;PodName;ContainerType
    • Auto Configuration successful after receiving SIP NOTIFY message.
    1625AlarmuxAlmAutoConfigurationfailed1.3.6.1.4.1.177.15.2.1048601Auto Configuration failedProcessingSystem;Service;PodName;ContainerTypeMajor
    • Failed to perform Auto Configuration after receiving SIP NOTIFY message.
    1626AlarmuxAlmSoftwareUpdateinprogress1.3.6.1.4.1.177.15.2.1048602Software Update in progressProcessingSystem;Service;PodName;ContainerTypeMajor
    • Current SIP NOTIFY message cannot be processed as software update is in progress.
    1627AlarmuxAlmNodeReboot1.3.6.1.4.1.177.15.2.1048603Node RebootEquipmentService;PodName;ContainerTypeMinor
    • Node Reboot requested by user [Username] from [ipAddress].
    1628AlarmuxAlmFactoryDefault1.3.6.1.4.1.177.15.2.1048604Factory DefaultEquipmentService;PodName;ContainerTypeMajor
    • Full factory default requested by user [Username] from [ipAddress].
    1629AlarmuxAlmInvalidSystemMemory1.3.6.1.4.1.177.15.2.1048605Invalid System MemoryEquipmentSystem;Service;PodName;ContainerTypeMajor
    • Unexpected memory size for virtual CPU detected.
    • Please consult documentation for memory requirement.
    1630AlarmuxAlmResetButtonFactoryDefault1.3.6.1.4.1.177.15.2.1048606Reset Button Factory DefaultEquipmentService;PodName;ContainerTypeMajor
    • Full factory default requested via hardware reset button.
    1631Alarm

    uxAlmSCMCconnectionisdown

    1.3.6.1.4.1.177.15.2.1048607

    SC-MC connection is downProcessingService;PodName;ContainerTypeCritical
    • Signaling container connection with media container is down.
    1632Alarm

    uxAlmSwitchoverToActive

    1.3.6.1.4.1.177.15.2.1048608Switchover To ActiveCommunicationIPAddressMinor
    • Logged when the Standby instance switches to the active role.
    • Event Text: System has switched to active HA role.
    1633Alarm

    uxAlmLostHAProtection

    1.3.6.1.4.1.177.15.2.1048609Lost HA ProtectionCommunicationIPAddressMajor(tick)
    • Logged when the Standby instance has gone offline.
    • Event Text: Peer HA node has gone offline.
    1634Event

    uxAlmHAProtectionRestored

    1.3.6.1.4.1.177.15.2.1048610HA Protection RestoredCommunicationIPAddressNone
    • Event Text: Peer HA node has come back online.
    • Clears alarm 16.33.
    1635Alarm

    uxAlmNoSpaceAvailableInRootPartition

    1.3.6.1.4.1.177.15.2.1048611No Space Available In Root PartitionEquipmentSystemCritical
    • No space is available in the root partition.
    • Suggested action: upload new firmware image and cut over partition. If the problem is still present afterwards, call TAC.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    17

    1

    Alarm

    uxAlmNoresponse1.3.6.1.4.1.177.15.2.1114113

    No response

    Communication

    Card;Port;Channel;PodName;ContainerType

    Major

    (tick)

    • No response to seizure.

    17

    2

    Alarm

    uxAlmRemoteenddidnotbackoffinglare1.3.6.1.4.1.177.15.2.1114114

    Remote end did not back off in glare

    Communication

    Card;Port;Channel;PodName;ContainerType

    Minor

    • Remote end did not back off in glare.

    17

    3

    Alarm

    uxAlmWinkexpecteddidnotarrive1.3.6.1.4.1.177.15.2.1114115

    Wink expected, did not arrive

    Communication

    Card;Port;Channel;PodName;ContainerType

    Major

    (tick)

    • Wink expected, did not arrive.

    17

    4

    Alarm

    uxAlmNodialtone1.3.6.1.4.1.177.15.2.1114116

    No dial tone

    Communication

    Card;Port;Channel;PodName;ContainerType

    Major

    (tick)

    • Event of off-hook did not produce dial tone as expected.

    17

    5

    Event

    uxAlmCASsignalinggroupdisabled1.3.6.1.4.1.177.15.2.1114117

    CAS signaling group disabled

    Communication

    SG;PodName;ContainerType

    (tick)

    • CAS signaling group disabled.

    17

    6

    Alarm

    uxAlmCASlicensenotenabled1.3.6.1.4.1.177.15.2.1114118

    CAS license not enabled

    General

    System;Service;PodName;ContainerType

    Major

    (tick)

    • Call attempted but CAS feature is not enabled.
    • This alarm is cleared by CAS license enabled event.

    17

    7

    Event

    uxAlmCASlicenseenabled1.3.6.1.4.1.177.15.2.1114119

    CAS license enabled

    General

    System;Service;PodName;ContainerType

    • License manager notify CAS that license is enabled.

    17

    8

    Event

    uxAlmWinkReceived1.3.6.1.4.1.177.15.2.1114120

    Wink Received

    Communication

    Card;Port;Channel;PodName;ContainerType

    • Wink failure had occurred, but wink is received now.

    17

    9

    Event

    uxAlmDialToneReceived1.3.6.1.4.1.177.15.2.1114121

    Dial Tone Received

    Communication

    Card;Port;Channel;PodName;ContainerType

    • No Dial Tone was received, but Dial Tone is received now.

    17

    10

    Event

    uxAlmResponseReceived1.3.6.1.4.1.177.15.2.1114122

    Response Received

    Communication

    Card;Port;Channel;PodName;ContainerType

    • No Response to seizure was received, but Response is received now.

    17

    11

    Alarm

    uxAlmInvalidcharactersincallingnumber1.3.6.1.4.1.177.15.2.1114123

    Invalid character(s) in calling number

    Communication

    Calling;PodName;ContainerType

    Warning

    • Invalid character(s) removed, correct issue and delete warning.

    17

    12

    Alarm

    uxAlmInvalidcharactersincallednumber1.3.6.1.4.1.177.15.2.1114124

    Invalid character(s) in called number

    Communication

    Called;PodName;ContainerType

    Warning

    • Invalid character(s) removed, correct issue and delete warning.

    17

    13

    Event

    uxAlmCASsignalinggroupenabled1.3.6.1.4.1.177.15.2.1114125

    CAS signaling group enabled

    Communication

    SG;PodName;ContainerType

    • CAS signaling group enabled.

    17

    14

    Alarm

    uxAlmCASR2CDBiterror1.3.6.1.4.1.177.15.2.1114126

    CAS-R2 CD Bit error

    Communication

    Card;Port;PodName;ContainerType

    Minor

    (tick)

    • CAS-R2 CD-Bits are mismatched on the span, this alarm is cleared when all channels match.

    17

    15

    Event

    uxAlmCASR2CDBiterrorclear1.3.6.1.4.1.177.15.2.1114127

    CAS-R2 CD Bit error clear

    Communication

    Card;Port;PodName;ContainerType

    • CAS-R2 CD-Bits now match on this span for all channels.

    17

    16

    Alarm

    uxAlmNetworkGlareoccured1.3.6.1.4.1.177.15.2.1114128

    Network Glare occured

    Communication

    Card;Port;Channel;PodName;ContainerType

    Minor

    • Network glare occurred on this interface.

    ID

    Sub-ID

    Type

    MIB Trap NameOID

    Condition

    Category

    Decode Key

    Default Severity

    Auto Clear

    Notes/Description

    18

    1

    Alarm

    uxAlmConfigvalidationfailure1.3.6.1.4.1.177.15.2.1179649

    Config validation failure

    General

    System;Service;PodName;ContainerType

    Warning

    • Config validation failure during startup.
    • Please check the configuration.
    182AlarmuxAlmNewerConfigLoaded1.3.6.1.4.1.177.15.2.1179650Newer Config loadedGeneralSystem;Service;PodName;ContainerTypeMajor
    • Configuration loaded from newer release than currently running release.
    183EventuxAlmPassworddecryptionfailed1.3.6.1.4.1.177.15.2.1179651Password decryption failedGeneralSystem;Service;PodName;ContainerType
    • Password decryption failed on configuration import operation.
    184EventuxAlmPartialFactoryDefault1.3.6.1.4.1.177.15.2.1179652Partial factory defaultEquipmentSystem;Service;PodName;ContainerType
    • Partial 'factory default or configuration import' requested by [Username] from [ipAddress].
    185EventuxAlmConfigurationRestore1.3.6.1.4.1.177.15.2.1179653Configuration RestoreEquipmentSystem;Service;PodName;ContainerType
    • Configuration restore requested by [Username] from [ipAddress].
    IDSub-IDTypeMIB Trap NameOIDConditionCategoryDecode KeyDefault SeverityAuto ClearNotes/Description
    191AlarmuxAlmSGChannelUsageexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245185SG Channel Usage exceeded TCA thresholdCommunicationSG;PodName;ContainerTypeMajor(tick)
    • Signaling Group channel usage exceeded configured TCA threshold.
    192EventuxAlmSGChannelUsagebelowTCAthreshold1.3.6.1.4.1.177.15.2.1245186SG Channel Usage below TCA thresholdCommunicationSG;PodName;ContainerType
    • Signaling Group channel usage fell below configured TCA threshold.
    193AlarmuxAlmSIPCallLicenseUsageexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245187SIP Call License Usage exceeded TCA thresholdCommunicationSystem;Service;PodName;ContainerTypeMajor(tick)
    • SIP Call license usage exceeded configured TCA threshold.
    194EventuxAlmSIPCallLicenseUsagebelowTCAthreshold1.3.6.1.4.1.177.15.2.1245188SIP Call License Usage below TCA thresholdCommunicationSystem;Service;PodName;ContainerType
    • SIP Call license usage fell below configured TCA threshold.
    195AlarmuxAlmSIPRegistrationUsageexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245189SIP Registration Usage exceeded TCA thresholdCommunicationSIPRegistrarTable;PodName;ContainerTypeMajor(tick)
    • SIP Registration usage exceeded configured TCA threshold.
    196EventuxAlmSIPRegistrationUsagebelowTCAthreshold1.3.6.1.4.1.177.15.2.1245190SIP Registration Usage below TCA thresholdCommunicationSIPRegistrarTable;PodName;ContainerType
    • SIP Registration usage fell below configured TCA threshold.
    197AlarmuxAlmDSPUsageexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245191DSP Usage exceeded TCA thresholdCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • DSP usage exceeded configured TCA threshold.
    198EventuxAlmDSPUsagebelowTCAthreshold1.3.6.1.4.1.177.15.2.1245192DSP Usage below TCA thresholdCommunicationSystem;PodName;ContainerType
    • DSP usage fell below configured TCA threshold.
    199AlarmuxAlmCPUUsageexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245193CPU Usage exceeded TCA thresholdCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • CPU usage exceeded configured TCA threshold.
    1910EventuxAlmCPUUsagebelowTCAthreshold1.3.6.1.4.1.177.15.2.1245194CPU Usage below TCA thresholdCommunicationSystem;PodName;ContainerType
    • CPU usage fell below configured TCA threshold.
    1911AlarmuxAlmMemoryUsageexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245195Memory Usage exceeded TCA thresholdCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • Memory usage exceeded configured TCA threshold.
    1912EventuxAlmMemoryUsagebelowTCAthreshold1.3.6.1.4.1.177.15.2.1245196Memory Usage below TCA thresholdCommunicationSystem;PodName;ContainerType
    • Memory usage fell below configured TCA threshold.
    1913AlarmuxAlmFileDescriptorUsageexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245197File Descriptor Usage exceeded TCA thresholdCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • File Descriptor Usage exceeded TCA threshold.
    1914EventuxAlmFileDescriptorUsagebelowTCAthreshold1.3.6.1.4.1.177.15.2.1245198File Descriptor Usage below TCA thresholdCommunicationSystem;PodName;ContainerType
    • File Descriptor Usage fell below TCA threshold.
    1915AlarmuxAlmCPUloadaverageinpast1minuteexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245199CPU load average in past 1 minute exceeded TCA thresholdCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • CPU load average in past 1 minute exceeded TCA threshold.
    1916EventuxAlmCPUloadaverageinpast1minutefellbelowTCAthreshold1.3.6.1.4.1.177.15.2.1245200CPU load average in past 1 minute fell below TCA thresholdCommunicationSystem;PodName;ContainerType
    • CPU load average in past 1 minute fell below TCA threshold.
    1917AlarmuxAlmCPUloadaverageinpast5minutesexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245201CPU load average in past 5 minutes exceeded TCA thresholdCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • CPU load average in past 5 minutes exceeded TCA threshold.
    1918EventuxAlmCPUloadaverageinpast5minutesfellbelowTCAthreshold1.3.6.1.4.1.177.15.2.1245202CPU load average in past 5 minutes fell below TCA thresholdCommunicationSystem;PodName;ContainerType
    • CPU load average in past 5 minutes fell below TCA threshold.
    1919AlarmuxAlmCPUloadaverageinpast15minutesexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245203CPU load average in past 15 minutes exceeded TCA thresholdCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • CPU load average in past 15 minutes exceeded TCA threshold.
    1920EventuxAlmCPUloadaverageinpast15minutesfellbelowTCAthreshold1.3.6.1.4.1.177.15.2.1245204CPU load average in past 15 minutes fell below TCA thresholdCommunicationSystem;PodName;ContainerType
    • CPU load average in past 15 minutes fell below TCA threshold.
    1921AlarmuxAlmTemporarypartitionusageexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245205Temporary partition usage exceeded TCA thresholdCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • Temporary partition usage exceeded TCA threshold.
    1922EventuxAlmTemporarypartitionusagefellbelowTCAthreshold1.3.6.1.4.1.177.15.2.1245206Temporary partition usage fell below TCA thresholdCommunicationSystem;PodName;ContainerType
    • Temporary partition usage fell below TCA threshold.
    1923AlarmuxAlmLoggingpartitionusageexceededTCAthreshold1.3.6.1.4.1.177.15.2.1245207Logging partition usage exceeded TCA thresholdCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • Logging partition usage exceeded TCA threshold.
    1924EventuxAlmLoggingpartitionusagefellbelowTCAthreshold1.3.6.1.4.1.177.15.2.1245208Logging partition usage fell below TCA thresholdCommunicationSystem;PodName;ContainerType
    • Logging partition usage fell below TCA threshold.
    IDSub-IDTypeMIB Trap NameOIDConditionCategoryDecode KeyDefault SeverityAuto ClearNotes/Description
    201AlarmuxAlmFailedtoresolveFQDN1.3.6.1.4.1.177.15.2.1310721Failed to resolve FQDNCommunicationSNMP;IPAddress;PodName;ContainerTypeMinor(tick)
    • Failed to resolve IP Address.
    • Ensure that FQDN and DNS server is configured properly.
    202EventuxAlmFQDNresolved1.3.6.1.4.1.177.15.2.1310722FQDN resolvedCommunicationSNMP;IPAddress;PodName;ContainerType
    • IP address successfully resolved.
    IDSub-IDTypeMIB Trap NameOIDConditionCategoryDecode KeyDefault SeverityAuto ClearNotes/Description
    211AlarmuxAlmLostconnectivitytoRAMPserver1.3.6.1.4.1.177.15.2.1376257Lost connectivity to RAMP serverCommunicationIPAddress;PodName;ContainerTypeMinor(tick)
    • Failed to connect to the configured RAMP.
    • Make sure connectivity is available.
    212EventuxAlmConnectedtoRAMPserver1.3.6.1.4.1.177.15.2.1376258Connected to RAMP serverCommunicationIPAddress;PodName;ContainerType
    • Successfully connected to RAMP server.
    213AlarmuxAlmRAMPtunnelrequestdenied1.3.6.1.4.1.177.15.2.1376259RAMP tunnel request deniedCommunicationIPAddress;PodName;ContainerTypeWarning(tick)
    • A device connect request from RAMP was denied due to a tunnel already being established.
    214EventuxAlmRAMPtunnelconnectionestablished1.3.6.1.4.1.177.15.2.1376260RAMP tunnel connection establishedCommunicationIPAddress;PodName;ContainerType
    • Device connect from RAMP server was established.
    215EventuxAlmRAMPtunnelconnectionclosed1.3.6.1.4.1.177.15.2.1376261RAMP tunnel connection closedCommunicationIPAddress;PodName;ContainerType
    • Device connect from RAMP server was closed normally.
    216AlarmuxAlmDidnotreceiveRAMPRequestforreportswhileC2Eisenabled1.3.6.1.4.1.177.15.2.1376262Did not receive RAMP Request for reports while C2E is enabledCommunicationIPAddress;PodName;ContainerTypeWarning
    • Please contact Ribbon technical support.
    217AlarmuxAlmReceivedRAMPRequestforreportswhileC2Eisdisabled1.3.6.1.4.1.177.15.2.1376263Received RAMP Request for reports while C2E is disabledCommunicationIPAddress;PodName;ContainerTypeMajor
    • Please contact Ribbon technical support.
    218AlarmuxAlmCDRloggingfailedforvoicequalityreporting1.3.6.1.4.1.177.15.2.1376264CDR logging failed for voice quality reportingGeneralSystem;Service;PodName;ContainerTypeMajor(tick)
    • Spacevars
      0product
       failed to log VQ CDRs in local file.
    • Either low disk space or maximum limit crossed for logging or EV not pulling reports.
    219EventuxAlmCDRloggingenabledforvoicequalityreporting1.3.6.1.4.1.177.15.2.1376265CDR logging enabled for voice quality reportingGeneralSystem;Service;PodName;ContainerType
    • Spacevars
      0product
       can log voice quality CDRs in local file.
    2110AlarmuxAlmLicenseExpireWarning1.3.6.1.4.1.177.15.2.1376266License Expire WarningCommunicationSystem;Service;PodName;ContainerTypeMajor(tick)
    • Last successful license check-in was on [checkinTime].
    • License will expire on [expireTime]. [numDays] days remaining."
    2111AlarmuxAlmLicensehasexpired1.3.6.1.4.1.177.15.2.1376267License has expiredCommunicationSystem;Service;PodName;ContainerTypeCritical(tick)
    • License expired after being unable to verify status.
    • Last successful check-in was on: [time].
    2112EventuxAlmLicenseVerified1.3.6.1.4.1.177.15.2.1376268License VerifiedCommunicationSystem;Service;PodName;ContainerType
    • Successfully verified License from RAMP server.
    IDSub-IDTypeMIB Trap NameOIDConditionCategoryDecode KeyDefault SeverityAuto ClearNotes/Description
    221AlarmuxAlmE911NotificationServerconnectionfailure1.3.6.1.4.1.177.15.2.1441793E911 Notification Server connection failureCommunicationService;PodName;ContainerTypeMinor(tick)
    • System was unable to connect to Notification server.
    222AlarmuxAlmEmergencyMessageSendFailure1.3.6.1.4.1.177.15.2.1441794Emergency Message Send FailureCommunicationService;PodName;ContainerTypeMinor(tick)
    • Emergency Message could not be sent [reason].
    • Check configuration.
    223EventuxAlmE911Notificationserverconnected1.3.6.1.4.1.177.15.2.1441795E911 Notification Server connectedCommunicationService;PodName;ContainerType
    • Connected with notification server.
    224EventuxAlmE911Messagesendsuccess1.3.6.1.4.1.177.15.2.1441796E911 Message send successCommunicationService;PodName;ContainerType
    • Message sent to all recipients successfully.
    IDSub-IDTypeMIB Trap NameOIDConditionCategoryDecode KeyDefault SeverityAutoClearNotes/Description
    231AlarmuxAlmSLBSCconnectionisdown1.3.6.1.4.1.177.15.2.1507329SLB-SC connection is downCommunicationIPAddress;PodName;ContainerTypeMajor(tick)
    • SLB container connection with Signaling container is down: [pod name].
    232EventuxAlmSLBSCconnectionisup1.3.6.1.4.1.177.15.2.1507330SLB-SC connection is upCommunicationIPAddress;PodName;ContainerType
    • SLB container connection with Signaling container is up: [pod name].
    233AlarmuxAlmIPAssociationfailed1.3.6.1.4.1.177.15.2.1507331IP Association failedCommunicationInterface;PodName;ContainerTypeMajor
    • Public IP Association to SLB failed: [ip address].
    234EventuxAlmIpAssociationsuccessful1.3.6.1.4.1.177.15.2.1507332IP Association successfulCommunicationInterface;PodName;ContainerType
    • Public IP Association to SLB successful: [ip address].
    235AlarmuxAlmSwitchoverinprogress1.3.6.1.4.1.177.15.2.1507333Switchover in progressCommunicationService;PodName;ContainerTypeMajor(tick)
    • SLB Switchover is in progress.
    236EventuxAlmSwitchovercompleted1.3.6.1.4.1.177.15.2.1507334Switchover completedCommunicationService;PodName;ContainerType
    • SLB Switchover completed.
    IDSub-IDTypeMIB Trap NameOIDConditionCategoryDecode KeyDefault SeverityAutoClearNotes/Description
    241AlarmuxAlmMCSCconnectionisdown1.3.6.1.4.1.177.15.2.1572865MC-SC connection is downCommunicationIPAddress;PodName;ContainerTypeMajor(tick)
    • Media container connection with Signaling container is down on the boot up.

    242EventuxAlmMCSCconnectionisup1.3.6.1.4.1.177.15.2.1572866MC-SC connection is upCommunicationIPAddress;PodName;ContainerType
    • Media container connection with Signaling container is up.
    243AlarmuxAlmMCSCestablishedconnectionisdown1.3.6.1.4.1.177.15.2.1572867MC-SC established connection is downCommunicationIPAddress;PodName;ContainerTypeCritical
    • Established connection between Media and Signaling container is down and hence dry-up timer started.
    244AlarmuxAlmDryUpTimerExpired1.3.6.1.4.1.177.15.2.1572868Dry-Up Timer ExpiredCommunicationIPAddress;PodName;ContainerTypeCritical
    • Dry-Up Timer Expired and MC is going for a restart.
    245AlarmuxAlmMCIPAssociationfailed1.3.6.1.4.1.177.15.2.1572869MC IP Association FailedCommunicationInterface;PodName;ContainerTypeMajor(tick)
    • Public IP Association to MC failed: [ip address].
    246EventuxAlmMCIpAssociationsuccessful1.3.6.1.4.1.177.15.2.1572870MC IP Association successfulCommunicationInterface;PodName;ContainerType
    • Public IP Association to MC successful: [ip address].
    247AlarmuxAlmBWUsageExceeedThreshold1.3.6.1.4.1.177.15.2.1572871BW Usage Exceed ThresholdCommunicationInterface;PodName;ContainerTypeMajor(tick)
    • MC BW usages exceed threshold: [interface].
    248EventuxAlmBWUsageBelowThreshold1.3.6.1.4.1.177.15.2.1572872BW Usage Below ThresholdCommunicationInterface;PodName;ContainerType
    • MC BW usages below threshold: [interface].
    249AlarmuxAlmMCMemoryUsageExceedThreshold1.3.6.1.4.1.177.15.2.1572873MC Memory Usage Exceed ThresholdCommunicationSystem;PodName;ContainerTypeMajor(tick)
    • MC Memory usage exceed [percentage] threshold.
    2410Event

    uxAlmMCMemoryUsageBelowThreshold

    1.3.6.1.4.1.177.15.2.1572874MC Memory Usage Below ThresholdCommunicationSystem;PodName;ContainerType

    Decode Key Table

    The following table defines the decode key types used throughout the system Alarms and Events in the SBC 1000/2000.

    Decode Key

    Description

    System

    By default it will be the SBC 1000/2000 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/even.

    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

    TLSProfileTLS Profile (ID of the TLS Profile)

    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


    ...