Export (0) Print
Expand All

Stress and Performance Tool: Advanced Configuration

Lync Server 2010
 

Topic Last Modified: 2011-02-19

You can use the Lync Server 2010 Load Configuration Tool (UserProfileGenerator.exe) to configure a simulation for a single pool with no federated traffic. Cross pool and federation are also supported, but only for instant messaging (IM) and presence. The setup for cross pool and federation is very similar; there are only minor differences in the way contacts are specified in the Lync Server User Creation tool (StressConfig.exe). In order to run federation and/or cross pool, you must create a different set of users specifically for federation and/or cross pool.

Several steps have to be followed in order to configure federation properly. First, you need to create a set of users in and for each pool in which you want to enable federation. For example, if you have two pools, pool1 and pool2, you would need to create a group of users called (for example), imusers1 and imusers2. You would then need to create configuration files separately for each pool by using UserProfileGenerator, and then run those configuration files from client computers in each pool.

noteNote:
All users must have unique phone numbers. That means that if you are using cross pool or federation, when you create different batches of users with Stressconfig.exe, you must change the Area Code in the VOIP tab, as shown in the following figure. For details, see Stress and Performance Tool: Create Users and Contacts.

The VOIP tab of Stressconfig.exe

Area code entry in Stressconfig.exe

To create users for cross-pool:

  1. Start Stressconfig.exe, and then click the General Settings tab.

  2. Under Contact Settings, specify a number for Percent of contacts in the same pool/HS that is less than 100. For example, a value of 50 for Percent of contacts in the same pool/HS would result in 50% local pool contacts and 50% non-local pool contacts, as shown in the following figure.

    Contact settings for cross-pool users

    Contact settings for cross-pool users
  3. Click the Contacts tab.

  4. Specify each of the other pools and federated domains. Ensure that the values in the EntID and SipDomain columns are the same for each entry, similar to the values shown in the following figure.

    The Contacts tab of Stressconfig.exe showing domains for cross-pool configuration

    Domains for cross-pool contacts
  5. Click Create Contacts.

To create users for federation:

  1. Start Stressconfig.exe, and then click the General Settings tab.

  2. Under Contact Settings, specify a non-zero number for Percent of contacts out of enterprise (federated). For example, a value of 50 in Percent of contacts out of enterprise (federated) would result in 50% local pool contacts and 50% federated contacts, as shown in the following figure.

    Contact settings for federated users

    Contact settings for federated users
  3. Click the Contacts tab.

  4. Specify each of the other pools and federated domains. Ensure that the values in the EntID column are different for each entry, as shown in the following figure.

    The Contacts tab of Stressconfig.exe showing domains for federated users

    Domains for federated contacts
  5. Click Create Contacts.

noteNote:
When creating federated contacts you may receive the following error: “Enterprise '{0}' users in pool '{1}' do not exist. Users {2} - {3} will be created as federated users.” This error means that due to security boundaries, the StressConfig tool cannot validate because the federated users exist. In this case it is up to you to create the users and contacts on the federated domain; the tool cannot create them for you.

To generate the LyncPerfTool configuration files for the users that were created for federation, you need to run two instances of UserProfileGenerator. Each instance needs to have the settings on the Common Configuration tab properly specified for which pool and which users it will be covering. (For example, pool1.contoso.com for the access proxy and imusers1 for the user prefix, in addition to the appropriate values for the other fields). Then, you need to enable only the Instant Messaging load on the General Scenarios tab for each.

Finally, for the deployment from which you want to test federation or cross-pool, you must click the Advanced button for Instant Messaging, and then change the field InviteUsersInContactList to true.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft