Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Sizing advice/guide for Lync SDN Manager server

This thread has been viewed 0 times

  • 1.  Sizing advice/guide for Lync SDN Manager server

    Posted Feb 25, 2016 04:57 PM

    Hi community,

     

    I'm not sure if this is the right place to ask this, but couldn't find a better alternative.

     

    Has anybody deployed the Lync SDN Manager (LSM) in their environment, and if so, did you refer to a Microsoft sizing guide when doing this? I was looking for some information regarding this as we are investigating introducing this into our environment, but are struggling to find any references regarding this e.g. if supporting X amount of controllers you need this amount of CPU/memory, etc.

     

    Any advice would be much appreciated. Thanks


    #SDN


  • 2.  RE: Sizing advice/guide for Lync SDN Manager server

    Posted Mar 12, 2016 11:06 PM

    Dazc,

     

    Aruba has a Validated Reference Design guide for Lync deployments.  You can find it here:  http://community.arubanetworks.com/aruba/attachments/aruba/Aruba-VRDs/71/1/Lync%20Over%20Aruba%20Wi-Fi%20Validated%20Reference%20Design.pdf

     

    On page 41, the SDN sizing recommendations are:

     

    On key SDN API parameter observe the controller message rate. For example, an Aruba 7240 controller can handle 270K messages per hour or 75 messages per second. This number exceeds the volume of messages that can be sent by the Lync server SDN API, so the 7240 controller is not a rate limiting factor with respect to call based constraint. For large deployments there should be one LSM per FE server pool, and each FE server pool should contain a minimum of three and a maximum of eight Lync FE servers.

     

    LSM/Controller ratio: 1:120