Hi Chad,
You must have running OpenSAF to be able to use immcfg.
It means, at least one controller.
When IMM is unavailable (example: sync data due to a new node joined the
cluster), you are not able to do any CCB operation.
Thanks,
Zoran
-Original Message-
From: Chad Lingrell
Hello,
I am in the process of getting familiar with the immcfg tool and the dynamic
configuration of OpenSAF. One thing I noticed, so far, is that I cannot add
seem to configuration unless the peer system controller is available. I would
expect to be able to change the configuration
Is it a command on AMF object or (log, clm?)
The reason for failure should be logged in the syslog, what's the command and
the error seen?
Mathi
-Original Message-
From: Chad Lingrell [chad.lingr...@genband.com]
Received: Thursday, 08 Oct 2015, 20:52
To: Zoran Milinkovic
The command and associated logs are below. The same command works when the peer
SC is up and enabled.
Command:
immcfg -c SaAmfSU safSu=saf-SU3,safSg=saf-Np1,safApp=safApp -a
saAmfSUType=safVersion=1,safSuType=safSuTypeNp1 -a saAmfSUFailover=1 -a
Looks like 2PBE is enabled.
and the other SC-2 is down. In this case the CCB will not be allowed.
An admin operation is required to enable 1safe2PBE.
For more information see the osaf/services/saf/immsv/README.2PBE
From the README:
The 1safe2PBE mechanism allows a 2PBE
