Avaya 7130X Exam Questions

Fetchers pull the value of presence information for a specific presentity from the presence service. If a fetcher is fetching information on a regular basis, it is called a poller. Subscribers, on the other hand, subscribe to presentity information on the presence service.

Communication Profile tab: Presence Profile

Fields include:

* The SIP Entity field used to route SIP based messages through the Presence Services.

* IM Gateway The IP address of the IM gateway

Note: Avaya SMGR stands for Avaya System Manager.

References: Administering Avaya Aura System Manager for Release 6.3.11 and later, Release 6.3 November 2016, page 554

https://downloads.avaya.com/css/P8/documents/101008185

Enable load balancing for a cluster if you want to scale the HTTP services without targeting a particular Avaya Breeze server. All the requests are sent to the cluster IP address. When you enable load balancing, two Avaya Breeze servers are chosen as the active and standby load balancing servers. The active load balancer distributes the HTTP requests to all the other servers in the cluster in a round robin fashion.

References: Administering Avaya Breeze, Release 3.1 (May 2016), page 16

https://downloads.avaya.com/css/P8/documents/101014143

Confirming that Avaya Breeze successfully replicates with 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 your newly-deployed Avaya Breeze.

4. After 2 -- 15 minutes, verify that the status of the Synchronization Status field is green/

Synchronized. If not, see Repairing replication between Avaya Breeze and System Manager

References: Avaya Aura Presence Services Snap-in Reference, Release 7.0.1, (December 2016), page 24

https://downloads.avaya.com/css/P8/documents/101013646

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