Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

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

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a, userName='null'}
JIRAIDAUTH SBX-113464
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c86af1a8d3016afe2f47e10008, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7480005, userName='null'}

Type: MAJOR

Object ID1.3.6.1.4.1.2879.2.8.1.2.1.19.0.3

Description

This alarm indicates that the connection to the License Manager failed.

Repetition

Repeats for each occurrence.

Event Codes

EVENT_LICENSE_MANAGER_SERVER_CONNECT_ERROR

Instance Fields

  • sonusAlarmNodeID
  • sonusAlarmLevel
  • sonusAlarmSequenceId
  • sonusAlarmTime
  • sonusAlarmDescription
  • sonusServerIpAddress
  • sonusLicenseManagerGraceDaysLeft

Action

Check the IP address in the message and check connectivity to that address.

Impact

The SBC will not be able to register with

Spacevars
0model3
.

Info
titleNote
Include Page
_License Manager alarms note
_License Manager alarms note

If the SBC remains disconnected from the managing
Spacevars
0model3
instance for an extended period of time, it will result in the SBC operating in an unsanctioned manner from a licensing perspective. Reconnect the SBC to the managing EMS/RAMP instance. Contact
Spacevars
0company
Global Product Support for more information regarding the need for the SBC to remain in constant contact with the managing
Spacevars
0model3
instance.

Clearing

automatic; sonusCpLicenseManagerRegistrationSucceeded