HP Advanced Services zl Module with Microsoft® Windows Server® 2008 R2 Planning and Design Guide

4-5
Solution 3: Survivable Communications
Solution Implementation
 WAN routers that connect the branch and data center
 Switches and routing switches at the branch and data center
 Domain controller and other servers at the data center
Solution Implementation
The following sections provide some basic guidelines for implementing this
solution as well as references to places where you can find more information.
You may need to adapt these guidelines to fit your particular network infra-
structure.
Predeployment Steps
By default, the Windows Server 2008 R2 that runs on the Advanced Services
zl Module requests a DHCP address—as does the SBM. Both devices request
the IP address on their internal interface 2. Network administrators can set
the IP addresses manually instead, or the DHCP server administrator can
create a fixed DHCP reservations for them. It is recommended that you give
the module running the Windows Server 2008 R2 a static IP address.
If you select the latter option for either module, the server administrator
should create the reservations in advance. The administrator needs to know
the MAC address on the module’s internal interface 2. This MAC address is
one higher than the address listed on the label on module’s underside.
Before you deploy the SBM, server administrators must complete several
more steps:
 Adding the SBM computer object to Active Directory
 Specifying the SBM’s service principal name (SPN)
 Adding the SBM to the Lync topology and publishing the topology
 Creating routing and normalization rules for the SBM
 Creating a CS-HealthMonitoring pool with test user accounts for the SBM
 Preparing a private key/certificate for the SBM or planning how to submit
the SBM’s certificate request
To learn how to complete these steps, refer the HP Survivable Branch
Communications zl Module Powered by Microsoft Lync
TM
Planning and
Design Guide.