Last updated on JULY 30, 2012
Applies to:Oracle Communications SAFfire - Version 3.1.0 and later
Information in this document applies to any platform.
The info model XML file that loaded through the infoModel tool before starting SRP reflects a configuration of the fully populated chassis.
Sometimes deploy chassis that have a subset of hardware installed (i.e. with not all of the hardware elements present for some of the service groups).
To support these sparsely populated chassis configurations the process administratively locks missing nodes and then dynamically modify the info model at runtime by changing the saAmfSGNumPrefActiveSUs attribute using ImmOm CCB API.
This mechanism works well in SAFfire 3.0 but in SAFfire 3.1 the Service Groups with the modified saAmfSGNumPrefActiveSUs attribute do not receive the standby assignments.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms