F5 is showing server out of service for few CAS service in Exchange 2013.

Recently I came across a situation where F5 was showing few of Exchange CAS Server out of service where probe for few service was failing, to fix the issue, I checked the Sever Component State using (Get-ServerComponentState ServerName) cmd, which showed me the Inactive Server Component , so I Set the Component state back in active State which fixed the issue and F5 started showing server as up again.

Example of the CMD I Used is below for full details of the same check the link below
Set-ServerComponentState

Example:
Set-ServerComponentState -Component UMCallRouter -Identity MailboxServer01 -Requester HealthAPI -State Active

Below are the some of the useful Blog post regarding the same.

Testing Exchange Server 2013 Client Access Server Health with PowerShell
Load Balancing in Exchange 2013