Why on the Same Boards, E5-ENETB, the Associations Did Not Work Towards MSC6 But Worked Towards Other Nodes - SGSN, SMSC (Doc ID 2149077.1)

Last updated on JUNE 17, 2016

Applies to:

Oracle Communications EAGLE (Hardware) - Version EAGLE 3x.x and later
Information in this document applies to any platform.

Goal

1. Why on the same boards E5-ENETB 2116 & 3116 the Associations did not work towards MSC6 but worked towards other nodes - SGSN, SMSC - see config below:

> rept-stat-card:loc=2116

 eagle 16-04-13 09:08:22 EET EAGLE5 44.0.4-64.34.24
 CARD VERSION TYPE GPL PST SST AST
 2116 134-034-024 E5ENETB IPSG IS-NR Active -----
  ALARM STATUS = No Alarms.
   ...
  PEAK TEMPERATURE: = 44C (112F) [16-02-16 01:53]
  SIGNALING LINK STATUS
  SLK PST    LS       CLLI
  A   IS-NR  mscp06   mscp06
  B   IS-NR  ssmsc101 smsc101sig
  A1  IS-NR  mss06    mss6sig
  B1  IS-NR  mss01    mss1sig


> rept-stat-card:loc=3116

 eagle 16-04-13 09:08:30 EET EAGLE5 44.0.4-64.34.24
 CARD VERSION TYPE GPL PST SST AST
 3116 134-034-024 E5ENETB IPSG IS-NR Active -----
  ALARM STATUS = No Alarms.
   ...
  SIGNALING LINK STATUS
  SLK PST   LS      CLLI
  A   IS-NR ssgsn04 sgsn04sig
  B   IS-NR mscp06  mscp06
  B1  IS-NR ussdn   ussdnav



2. When the Bugs #19116140 and #19086298 occur, why are all associations not affected? which s/w release solve these Bugs?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms