SAFfire Service Unit Remains Unassigned After Startup
(Doc ID 1631086.1)
Last updated on NOVEMBER 05, 2019
Applies to:Oracle Communications SAFfire - Version 3.1.0 and later
Information in this document applies to any platform.
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
Attempt to start the SAFfire srp process.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document