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 Topology
The next step in deploying an Edge Server is to edit the existing Lync Server topology. To edit the topology, perform the following steps:
1. Open the Lync Server Topology Builder.
2. When prompted to import an existing topology from Active Directory, click OK.
3. Expand the Site node where the Edge Server will deployed.
4. Right-click the Edge pools node, and select New Edge Pool.
5. Click Next to begin the wizard.
6. Enter the fully qualified name of the internal Edge Server pool in the Pool FQDN field.
7. Follow the appropriate following sections depending on whether a single Edge Server or pool of load-balanced Edge Servers will be deployed.
Deploying Standalone Edge Server
1. Select Single computer pool, and click OK.
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 is used, check the Enable federation box.
4. If the IP address used for the A/V Edge uses NAT, check the The external IP address of this Edge pool is translated by NAT box. Click Next when complete.
5. Under the SIP Access section, enter the external server FQDN and port. Typically, this is similar to sip.companyabc.com and port 443.
6. Under the Web Conferencing section, enter the external server FQDN and port. Typically, the name and port are similar to webconf.companyabc.com and port 443.
7. Under the Audio/Video section, enter the external server FQDN, IP address, and port. Typically, the name and port are similar to av.companyabc.com and port 443. Click Next when complete.
8. Enter an internal-facing IP address for the Edge Server pool and click Next.
9. Under the SIP Access section, enter the external IP address.
10. Under the Web Conferencing section, enter the external IP address.
11. Under the Audio/Video section, enter the external IP address and click Next.
12. If the A/V Edge IP address is translated by NAT enter the public IP address and click Next.
13. Select a next-hop pool to be used by the Edge Server pool and click Next. If a Director is deployed, that should be the next hop.
14. Place a checkmark next to any Front-End pools in the deployment that will use this Edge server pool for external web conferencing and A/V content. Click Finish to complete the wizard.
Deploying Load-Balanced Edge Server Pool
1. Select Multiple computer pool and click OK.
2. If a single public IP address will be used for the Access Edge, Web Conferencing Edge, and A/V Edge services on each server 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 is used, check the Enable federation box.
4. If the IP address used for the A/V Edge uses NAT, check the The external IP address
of this Edge pool is translated by NAT box. Click Next when complete.
5. Under the SIP Access section, enter the external server FQDN and port. Typically, this is similar to sip.companyabc.com and port 443.
6. Under the Web Conferencing section, enter the external server FQDN and port.
Typically, the name and port are similar to webconf.companyabc.com and port 443.
7. Under the Audio/Video section, enter the external server FQDN, IP address, and
port. Typically, the name and port are similar to av.companyabc.com and port 443.
Click Next when complete.
8. Click the Add button to define computers within the pool.
9. Enter the internal-facing IP address and internal FQDN of the server. Click Next.
10. Under the SIP Access section, enter the external IP address.
11. Under the Web Conferencing section, enter the external IP address.
12. Under the Audio/Video section, enter the external IP address and click Next.
13. If the A/V Edge IP address is translated by NAT enter the public IP address and click Next.
14. Repeat steps 8–13 for any additional Edge Server pool members and click Next when all nodes have been added.
15. Select a next-hop pool to be used by the Edge Server pool and click Next. If a Director is deployed, that should be the next hop.
16. Place a checkmark next to any Front-End pools in the deployment that will use this Edge server pool for external web conferencing and A/V content. Click Finish to complete the wizard.
Publish Topology
After the topology is modified to include the Edge Server pool, the configuration can be published. This step publishes the changes to the Central Management Store, and all existing Lync Server servers will update their local configuration stores to match.
1. Ensure that the Lync Server Topology Builder is open and contains the Edge Server pool recently added.
2. Click the top node of the management console, Lync Server.
3. Click the Action menu and select Publish Topology, or select Publish Topology from the Actions pane on the right side of the console.
4. Click Next to begin publishing the topology.
5. When the log indicates a successful update, click Finish to complete the wizard.
Source of Information : Wiley - Cloud Computing Principles and Paradigms 2011
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 Topology
The next step in deploying an Edge Server is to edit the existing Lync Server topology. To edit the topology, perform the following steps:
1. Open the Lync Server Topology Builder.
2. When prompted to import an existing topology from Active Directory, click OK.
3. Expand the Site node where the Edge Server will deployed.
4. Right-click the Edge pools node, and select New Edge Pool.
5. Click Next to begin the wizard.
6. Enter the fully qualified name of the internal Edge Server pool in the Pool FQDN field.
7. Follow the appropriate following sections depending on whether a single Edge Server or pool of load-balanced Edge Servers will be deployed.
Deploying Standalone Edge Server
1. Select Single computer pool, and click OK.
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 is used, check the Enable federation box.
4. If the IP address used for the A/V Edge uses NAT, check the The external IP address of this Edge pool is translated by NAT box. Click Next when complete.
5. Under the SIP Access section, enter the external server FQDN and port. Typically, this is similar to sip.companyabc.com and port 443.
6. Under the Web Conferencing section, enter the external server FQDN and port. Typically, the name and port are similar to webconf.companyabc.com and port 443.
7. Under the Audio/Video section, enter the external server FQDN, IP address, and port. Typically, the name and port are similar to av.companyabc.com and port 443. Click Next when complete.
8. Enter an internal-facing IP address for the Edge Server pool and click Next.
9. Under the SIP Access section, enter the external IP address.
10. Under the Web Conferencing section, enter the external IP address.
11. Under the Audio/Video section, enter the external IP address and click Next.
12. If the A/V Edge IP address is translated by NAT enter the public IP address and click Next.
13. Select a next-hop pool to be used by the Edge Server pool and click Next. If a Director is deployed, that should be the next hop.
14. Place a checkmark next to any Front-End pools in the deployment that will use this Edge server pool for external web conferencing and A/V content. Click Finish to complete the wizard.
Deploying Load-Balanced Edge Server Pool
1. Select Multiple computer pool and click OK.
2. If a single public IP address will be used for the Access Edge, Web Conferencing Edge, and A/V Edge services on each server 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 is used, check the Enable federation box.
4. If the IP address used for the A/V Edge uses NAT, check the The external IP address
of this Edge pool is translated by NAT box. Click Next when complete.
5. Under the SIP Access section, enter the external server FQDN and port. Typically, this is similar to sip.companyabc.com and port 443.
6. Under the Web Conferencing section, enter the external server FQDN and port.
Typically, the name and port are similar to webconf.companyabc.com and port 443.
7. Under the Audio/Video section, enter the external server FQDN, IP address, and
port. Typically, the name and port are similar to av.companyabc.com and port 443.
Click Next when complete.
8. Click the Add button to define computers within the pool.
9. Enter the internal-facing IP address and internal FQDN of the server. Click Next.
10. Under the SIP Access section, enter the external IP address.
11. Under the Web Conferencing section, enter the external IP address.
12. Under the Audio/Video section, enter the external IP address and click Next.
13. If the A/V Edge IP address is translated by NAT enter the public IP address and click Next.
14. Repeat steps 8–13 for any additional Edge Server pool members and click Next when all nodes have been added.
15. Select a next-hop pool to be used by the Edge Server pool and click Next. If a Director is deployed, that should be the next hop.
16. Place a checkmark next to any Front-End pools in the deployment that will use this Edge server pool for external web conferencing and A/V content. Click Finish to complete the wizard.
Publish Topology
After the topology is modified to include the Edge Server pool, the configuration can be published. This step publishes the changes to the Central Management Store, and all existing Lync Server servers will update their local configuration stores to match.
1. Ensure that the Lync Server Topology Builder is open and contains the Edge Server pool recently added.
2. Click the top node of the management console, Lync Server.
3. Click the Action menu and select Publish Topology, or select Publish Topology from the Actions pane on the right side of the console.
4. Click Next to begin publishing the topology.
5. When the log indicates a successful update, click Finish to complete the wizard.
Source of Information : Wiley - Cloud Computing Principles and Paradigms 2011
|
|
0 comments
Post a Comment