What should be verified before running the initTM --f command on the Command Line Interface of Avaya Breeze platform (formerly known as Engagement Development Platform (EDP))?
See step 8 and step 9 below.
Repairing replication between Avaya Breeze and System Manager
Procedure
1. On the System Manager web console, navigate to Services > Replication.
2. In Replica Group column, click CollaborationEnvironment_3.1.
3. In Replica Node Host Name column, locate Avaya Breeze.
4. Verify that the status of the Synchronization Status field is green. If not, go to Step 5.
5. If Presence Services Snap-in has been deployed, in the Product column, verify that both Avaya Breeze and Presence Services are displayed.
6. Select Avaya Breeze, and click Repair.
7. After 2--15 minutes, verify that the status of the Synchronization Status field is green. If not, go to Step 8.
8. Verify that Enrollment Password is not expired.
a. Navigate to Services > Security.
b. In the navigation pane, click Certificates > Enrollment Password.
9. If the Enrollment Password is expired:
a. Enter a password, and click Commit.
It is highly recommended that the same password must be used. Otherwise, Avaya
Breeze and Presence Services must be re-administered, because System Manager
Enrollment Password was configured during deployment of Avaya Breeze.
b. Open an SSH session to the Avaya Breeze Management Module IP address as sroot.
c. On the command line interface, enter initTM -f.
d. When prompted for the enrollment password, enter the password that you provided in Step 9a.
e. Repeat Step 1 to Step 6.
References: Avaya Aura Presence Services Snap-in Reference, Release 7.0.1 (December 2016), page 223
https://downloads.avaya.com/css/P8/documents/101013646
Currently there are no comments in this discussion, be the first to comment!