Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Using the DNS Manager, verify that the Lync 2010 Enterprise Pool Alias is pointing (therefore resolving) to the IP address of the hardware Load balancer machine as shown below.

    Panel
    borderStylenone

    Caption
    0Figure
    1DNS Manager

    Image Modified

  2. Verify that the VLAN interface used to communicate with the Lync server is tagged as indicted below.

    Panel
    borderStylenone

    Caption
    0Figure
    1Tag VLAN Interface

    Image Modified

  3. Verify that the F5 MGMT IP address is configured to use the VLAN interface set in the previous step.

    Panel
    borderStylenone

    Caption
    0Figure
    1Verify Configuration

    Of

    of F5 MGMT IP Address

    Image Modified 

  4. Verify that the VLAN interface Settings are configured as shown below.

    Panel
    borderStylenone

    Caption
    0Figure
    1Verify Configuration

    Of

    of VLAN Interface Settings

    Image Modified 

  5. Verify that Local Traffic > Nodes settings contain the Lync FE1, Lync FE2, and the virtual IP address of hardware load balancer machine as shown below.

    Panel
    borderStylenone

    Caption
    0Figure
    1Verify Node Settings

    Image Modified

  6. Verify that the settings found in Local Traffic > Pools contain the pools that the F5 load balancer listens to Lync on defined port numbers for various services as shown below.

    Panel
    borderStylenone

    Caption
    0Figure
    1Verify Pool Settings

    Image Modified

     

    NOTE: the details of pool creation is explained in Deploying the BIG-IP LTM with Microsoft Lync Server 2010as shown below.

    Panel
    borderStylenone

    Caption
    0Figure
    1Details of Pool Creation

    Image Modified

  7. Verify the virtual server making use of the pools created above has itself been created as shown below.

    Panel
    borderStylenone

    Caption
    0Figure
    1Verify Virtual Server

    Image Modified

Sonus SBC 2000 Configuration

...

  • Federated IP/FQDN: Pool FQDN in the IP/FQDN field
  • Netmask: 255.255.255.255 in the Netmask field

    These fields allow the Sonus SBC 1000/2000 to receive SIP messages from the hardware load balancer HWLB. However, in order to receive/send SIP messages to/from Front End Servers, the Netmask field must be configured with a value of 255.255.255.0.

Panel
borderStyle

...

none

Caption
0Figure
1Sonus SBC 2000 Configuration

Image Modified 

 

Call Flows

Using the Log Exchange utility, you can verify the F5 Hardware Load Balancer (HWLB) in action —

...

The deployment in this article allows the following call flow in PSTN ph > Sonus SBC 1000/2000 > Lync client call direction.

Panel
borderStylenone

Caption
0Figure
1PSTN ph > Lync Client Call Flow

Image Modified

 

LYNC client > Sonus SBC 1000/2000 > PSTN ph

The deployment in this article allows the following call flow in Lync client > Sonus SBC 1000/2000 > PSTN ph call direction.

Panel
borderStylenone

Caption
0Figure
1Lync Client > PSTN ph

Image Modified