Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c862eadf5e0163170affe7001b, userName='null'}
JIRAIDAUTHSBX-131552
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c863c32a720163c47764100001, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c87d403e06017d75ffbc0d0047, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85b00e7, userName='null'}

Type: CRITICAL

Object ID1.3.6.1.4.1.2879.2.8.1.2.1.8.0.7

Description

This trap indicates that triggers when the Peer host serial number does not match the serial number recorded in the license.

Repetition

None

Objects

  • sonusAlarmNodeID,sonusCpSystemServerName
  • sonusAlarmLevelsonusCpLicenseId

Action

Check the Peer's serial number and compare it to what is recorded in the license, and then refer to Node-Locked Licensing for guidance and/or contact your 

Spacevars
0company
account representative.

Impact

The license file is deemed invalid due to serial number mismatch. In HA scenario, the license file must contain both SBC serial numbers.

  • sonusAlarmSequenceId,
  • sonusAlarmTime,
  • sonusAlarmDescription
  • sonusCpSystemServerName
  • sonusCpLicenseId

Action

None.

Impact

None.

Clearing

Automatic; sonusCpLicenseBundleRenewedNotification2

Clearing

Manual