SAFfire Service Unit Remains Unassigned After Startup (Doc ID 1631086.1)

Last updated on MARCH 11, 2014

Applies to:

Oracle Communications SAFfire - Version 3.1.0 and later
Information in this document applies to any platform.

Symptoms

When starting the srp process in SAFfire 3.1, some Service Units (SUs) do not receive either an ACTIVE or STANDBY assignment.  This results in an unassigned SU which leaves the entire chassis in a nonoperational state.

The following log messages can be seen in the srp trace:

1. An instantiation of the COM1 component is invoked from the manager

Jan  9 21:09:25:167 ftime:21:09.25.108 0xED03BB70 5 AMFClc amfInitiateClcCliOperation: clcCliOper = 1, oh = 0x5500001a, nodeId = Slot03.CPBM, pClcCliCmd = /root/srp/instantiate.sh, pClcCliCmdArgs = 1

2. 30 seconds later, the clcCliTimeout and saAmfCompInstantiateTimeout timers fire and the cleanup.sh script is invoked for the same component

Jan  9 21:09:55:157 ftime:21:09.55.102 0xED03BB70 5 AMFClc amfInitiateClcCliOperation: clcCliOper = 3, oh = 0x5500001a, nodeId = Slot03.CPBM, pClcCliCmd = /root/srp/cleanup.sh, pClcCliCmdArgs = 1

3. Shortly thereafter, and before the cleanup operation completes, the srp gets an “Undefined transition” for the component. An INSTANTIATION_SUCCESS event was received when in the CLEANING_UP_INSTANTIATION state. This is an invalid transition for this state.

Jan  9 21:09:55:907 ftime:21:09.55.848 0xED03BB70 5 AMFComp compFsm(0x5500001a) Undefined transition compFsm state = 3, event = 33

Changes

Attempt to start the SAFfire srp process.

Cause

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