Monday, June 30, 2014

Lync Stress Test – How Too, Setup and Configuration (free eBook)

I extended the last Lync Stress Test Guide. Version 2.0

Now all important information are provided, incl. all parameters which can be modified and customized around all stress tests.

You can download the free eBook here:
Microsoft TechNet: http://gallery.technet.microsoft.com/office/Lync-Stress-Test-How-Too-c4c276e1
SlideShare: http://de.slideshare.net/thomaspoett/lync-stress-test-guide-v20-ebook

 

Table of Content:

Introduction
The Calculation Process (I can recommend to you):
Build the Stress Test Lab
The Stress Test Process:
The Validation Process:
User Provisioning Tool
Setup User Provisioning Tool
User Creation
Contacts Creation
Distribution List Creation
Location Info Service Config
Run Configuration Scripts
Stress Test Simulations
User Profile Generator
Common Configuration
General Scenario
Voice Scenario
Reach Scenario
Mobility Scenario
Summary (Important User Load definition)
Table of Figures


Sunday, June 8, 2014

Lync Stress Test - Key Health Indicators KHI (how to design/ define the server hardware requirements)

Since Microsoft released Lync Server 2013, there was one change in the planning document. No detailed SPECs were released so you could exactly calculate your server performance requirements.
Truly, there is the performance calculation sheet which provides you with a rough overview.

For this entire process you need the following tools and documents:
I provide you with the Lync KHI Performance Counter: Download here
Note:
The XML I have provide contains a consolidated Lync Frontend installation entirely on drive C: with 6 CPU core. If you have another setup, please add more CPU counter and if the SQL Server is installed on drive D:, please also add the I/O counters for this drive too.

But generally the server hardware requirements are physically and virtually the same:


Front End, Back End, Standard Edition, pChat - Server
Component
Minimum requirements
CPU
2x64 bit CPU with 6 Core (also if virtualized)
Memory
32 GB
Disk
2x RAID 1 min. 72GB[1] free space
6x RAID 10 for SQL databases
Network
1x Dual-Port network card with min. 1GBit/Sec
If teaming is activated, unique MAC address must be used




[1] It is required having at least 20GB free disk space after installation, else it might have a serious impact during update and CU installations, this is related tot he local SQL database copies.


Edge, Standalone Mediation – Server and Director, Office Web Apps
Component
Minimum requirements
CPU
64 bit CPU and min. 4 Core (also if virtualized)
Memory
16 GB
Disk
Mind. RAID 6 Performance with min. 72GB free space
Network
1x Dual-Port network card with min. 1GBit/Sec
If teaming is activated, unique MAC address must be used

This general definition for your hardware is simply not enough if you design your environment. There are some questions you need to answer to your customers:
- how can I guarantee the hardware performance on virtual environments
- how does Lync impact our SAN
- if we don't utilize the max user, how and can I reduce CPU's and RAM, or even the SQL Disk I/O's

Here you stand as consultant and don't know what to say.
E.g. the supportability matrix give you a clear answer, design the server as provided in the requirement document.
So, say you have 3 Frontend servers as recommended for High Availability (HA), but you only run 1.000 users.
This would be a complicated answers, since you simply cannot know the answer, as it was possible with Lync 2010, since you had more information how to calculate.

The Calculation Process (I recommend to you):

Lync server load highly depends on the user profile!
Talk to your customer and figure out what is the main purpose and how in the past users utilized Voice (PSTN and PBX)
Analyze the Video utilization, also and especially the AppSharing (with is video data too)
Start using the Lync Server 2013 Capacity Calculator.
With the results popping up you need to reverse engineer the capacity needed on your servers.
 
Finally you have some SPEC's, but you need (better say: MUST) validate them if you are not using the exact SPEC provided in the tables above.


The Stress Test Process:

Please use the Stress Test Guide from Microsoft and setup the environment in a Test Lab first. It simple even on physical, as well as on virtual environment.

Some recommendations from my experiences:

1. the Stress Client SPEC's are not sufficient as Microsoft wrote, please use here more CPU's, at least the double amount.
2. Split the Test across 3 Stress Clients,
    Stress Test Client 1: All IM, APPClients and Conferences

    Stress Test Client 2: all Reach Client features
    Stress Test Client 3: all PSTN functions (PSTN Gateway Simulator), here you might need more clients, since the PSTN Simulator can only provide one (1) gateway on a PC
3. run a Pre-Test, where you closely monitor you client performances, especially the CPU after the so call RAMP UP TIME
4. Check if information are written to the Lync Monitoring Database (validate the reports)
5. Re-balance some of you Test Scenarios and run the Step 3 again if necessary
6. Start the Main Stress Test now

Now it's time for the core test itself.
Ensure you either monitor the KHI on a dedicated machine or on the Lync server themselves. Please do NOT use any of the Stress Test Clients!

I have provided you with the Performance Monitor DataCollection. Make sure you see some results during Step 3.


The Validation Process:

Now you have all results necessary to write your report and even see you underestimated the server load ;)

Get the Performance Data and see if any of the counters above did jump above some of the provided counters for a longer periods of time or if any of those counters jump more frequently above the thresholds.

The go to the Lync Monitoring Reporting and validate all Failure Reports (related to the test you have ran).

I also recommend checking the Lync Server Eventlogs.

With the collection and analysis of all data write your own validation paper to the customer.

NOTE:
If you need help, don't hesitate asking me for help, I can provide you professional service and do the write-up for you.
Use the contact app on the right site of my blog.



Friday, June 6, 2014

LS Data MCU Event ID 41029

Solving a conferencing component error.

ERROR:
LS Data MCU Event ID 41029
Conferencing modality.

Server Machine FQDN: lyncfe02.domain.com, Port:8061

Server Type: External-WebApp-Edge [HTTP side error:The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.]

If the problem persists this event will be logged again after 20 minutes

Cause: Service may be unavailable or Network connectivity may have been compromised.



SOLUTION:

This issue is related with your WAC, Office Web App Server.
Mostly, you need to validate this settings

Server FQDN spelling
check if WAC Server support only SSL
Check your Certificate Deployment on the WAC Server

This solves the issue.


Wednesday, June 4, 2014

Lync Voice Mail Survivability (SA) with Exchange Unified Messaging


The SBA is aware of the centrally configured Exchange Unified Messaging component. Additional it is important to understand the process of Voice Mail Survivability. While the VoicemailReroutingConfiguration in Lync provides the SBA with an alternative path, rerouted via PSTN to the central Exchange UM site.

The SBA is continuously check the SIP availability of the Exchange UM component, using the SIP OPTION based health checking. (Indeed, both SBA and non SBA Lync registrars act in the same way for all components, e.g. Exchange UM and other Gateway-SBC). Once the SIP OPTION command is sent, the sender expects an SIP 200 OK answer. Lync tries this health check several time even after it do NOT receive a 200 OK. As result of not receiving, the registrar will mark this target as DOWN and stop sending calls.

Note:You can drill down this process, if you us OCSLogger and Snooper catching the OPTION and 200 OK communication directly on the SBA.

Back to the Exchange UM, if Exchange is not responding, the SBA marks the UM SIP path as down and activated the configured PSTN reroute.

Note:

If a user SBA homed user is remotely connected to central site (his backup registrar), incoming PSTN call to this user will also be rerouted to Exchange UM VoiceMail.

A PSTN cannot be rerouted this this (backup) registered user!

Voice Mail Deposit

If a WAN outage occurs, the SBA has detected that UM connectivity is down, all unanswered or ignored call for effected user homed on this SBA will be routed over the PSTN to the assigned UM Auto Attendant (AA).

There is one change in user experience: Once the UM pickup this call, the AA will ask the calling party (either via speech or extension number) and then a voice mail can be recorded. This behavior is different to the native user mailbox response.

Voice Mail Retrieval


During a WAN outage, there are other service truly effected too, e.g. Exchange Server connection. But Exchange Subscriber Access is still available via PSTN calls. Therefor an effected user is NOT able to use his Lync Client for Voice Mail Preview, instead, the normal “Call Voice Mail” will place a PSTN call to the Exchange Server Subscriber Access Number (SA).

As long the user is assigned in AD and Lync with an E.164 phone number, Exchange is able to do a Reverse Number Lookup and can identify the users work number. Exchange then answer directly instead of asking for the user’s mailbox PIN.

Configuration


Voicemail rerouting configuration must be established for all Branch Site equipped with a SBA

New-CsVoicemailReroutingConfiguration -Identity Site:Ingolstadt

For each Voicemail Rerouting, the Exchange Auto Attendant (AA) and the Subscriber Access Number (SA) has to be published.

Set-CsVoicemailReroutingConfiguration -Identity Site:Ingolstadt -SubscriberAccessNumber “+49899090123″ -AutoAttendantNumber “+49899090456″ -Enabled $true

Thanks to Justin Morris for his detailed explanation