Versions Compared

Old Version 3

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=8a00a0c86820e56901685f374974002d, userName='null'}
JIRAIDAUTHSBX-118835
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb1f0553, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7480005, userName='null'}

Type: MAJOR

Object ID1.3.6.1.4.1.2879.2.8.1.2.1.19.0.7

Description

This alarm indicates that an EMS/RAMP node ID has not been configured on the SBC.

Repetition

Repeats for each occurrence.

Event Codes

EVENT_LICENSE_MANAGER_EMS_NODEID_NOT_CONFIGURED

Instance Fields

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

Action

Check if the SBC has successfully registered with the EMS/RAMP and the performance data collection is enabled.

Impact

The SBC will not be able to register with the EMS/RAMP.

Info
titleNote
Include Page
_license_usage_unsanctioned
_license_usage_unsanctioned

If the SBC remains disconnected from the managing EMS/RAMP 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 EMS/RAMP instance.

Available_since
Release10.1.2

Clearing

Manual