Lync Server 2013 now supports IPv6 addressing
for all Edge Server services. If you have configured IPv6 addresses on
your Windows Server, you can now configure the Lync Server Topology to
use these IPv6 addresses. All services, including the XMPP gateway,
support IPv6.
Tip
To support IPv6, you must create DNS records
for the IPv6 addresses. These host records are defined as AAAA records.
The DNS records required is consistent between IPv4 and IPv6.
Create the Edge Pool
After the server has been fully
prepared for installation, the topology must be edited and published to
reflect the new Edge Server pool. This involves editing the existing
topology, if it exists, and then republishing the topology so that all
other servers in the environment are aware of the new Edge Server pool.
Edit the Topology
The next step in deploying a Lync Edge Server
is to edit the existing Lync Server topology. This task must be
performed from a Lync Server on the internal network such as a Front
End Server. To edit the topology, perform the following steps:
1. Open the Lync Server Topology Builder.
2. When prompted to download a topology from an existing deployment, click OK.
3. Save your topology file as appropriate.
4. Expand the Site node where the Edge Server will be deployed.
5. Expand the Lync Server 2013 node.
6. Right-click on the Edge Pools node, and select New Edge Pool.
7. Click Next to begin the wizard.
8. Enter the fully qualified name of the internal Edge Server Pool FQDN field.
9. Follow the
appropriate following sections depending on whether a single Edge
Server or a pool of load-balanced Edge Servers will be deployed.
Deploying a Single Edge Server Pool
If you are deploying a single Edge Server Pool, follow these steps:
1. Select Single Computer Pool, and click Next.
2. If a single public
IP address will be used for the Access Edge, Web Conferencing Edge, and
A/V Edge services, check the box Use a Single FQDN and IP Address. This
requires using ports other than 443 for two of the services.
3. If federation will be used, check the Enable Federation box.
4. If XMPP federation will be used, check the Enable XMPP Federation box, and then click Next.
5. Check valid IP
options as they relate to your deployment. If your deployment is using
IPv6, check the IPv6 boxes for the internal and external interface. If
not, ensure that only the IPv4 boxes are checked.
6. If the IP address
used for the A/V Edge uses NAT, check the box The External IP Address
of This Edge Pool Is Translated by NAT. Click Next when complete.
7. Under the Access Edge Service section, enter the external FQDN and port. Typically, this is similar to sip.companyabc.com and port 443.
Note
If you elected to use a single FQDN and IP
address for your public edge services, you will be permitted to enter
only a single FQDN, and the default ports will be set to 5061, 444, and
443.
8. Under the Web
Conferencing Edge Service section, enter the external server FQDN and
port. Typically, the name and port are similar to webconf.companyabc.com and port 443.
9. Under the A/V Edge Service section, enter the external server FQDN and port. Typically, the name and port are similar to av.companyabc.com and port 443. Click Next when complete.
Note
If you are using IPv6 in your environment,
and have selected to enable IPv6 on the Edge Server, you will be
required to enter the IPv6 and/or IPv4 address for each Edge Server.
10. Enter the internal-facing IP address for the Edge Server Pool and click Next.
11. Under the Access Edge Service section, enter the external IP address.
12. Under the Web Conferencing Edge Service section, enter the external IP address.
13. Under the A/V Edge Service section, enter the external IP address. When finished, click Next.
14.
Select a next-hop pool to be used by the Edge Server pool and click
Next. If a director is deployed, you should select the director as the
next-hop.
15. Select
any Front End Server pools or Mediation Server pools that will use this
Edge Server pool for external media traffic. Click Finish to complete
the wizard.
