Communication failure between the SM and the SCE

Unanswered Question
Mar 21st, 2008
User Badges:

i have upgard SM from 3.1.0 to 3.1.5 and after that the SCE can't sync to SM any one has work around on this issue.

SM Version: 3.1.5 Build 25 use pqi SCABB 3.1.5 build 25

SCE Version 3.1.5 Build 263

QS-2020#sh system operation-status

System Operation status is Warning


1. Lost connection with Subscriber Manager

[[email protected] bin]$ ./p3sm --resync-all

Error - Failed to synchronize all boxes

SCE QS-2020 had errors during subscribers synchronization: failed to synchronize 2 subscribers

[[email protected] bin]$ ./p3sm --sm-status

SM is running.

SM operational state is Active

Command terminated successfully

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
smalkeric Thu, 03/27/2008 - 07:35
User Badges:
  • Silver, 250 points or more

SM failed to become Active because when a failover is initiated, there is a so-called "make-active timeout"

that is watched during the failover process, to make the failover process doesn't take indefinitely. This timeout is 40 seconds.

If the Radius Server is on the SCE subscriber side, the second accounting request on a new flow (new tuple) will end up with the SCE sends corrupted RDRs.

And also removes the anonymous-group from the SCE configuration.


This Discussion