Shulou(Shulou.com)06/02 Report--

System Engineer Training

-09-Deploy Instant Messaging System

-02-Deploy Edge Servers-2-Design Topology

Author: Learning without Stop

QQ communication group: 454544014

1. Login-Front End Server

2. Click Skype for Business Server Topology Builder.

3. In the console tree, expand the site where you want to deploy the edge server.

4. Right-click Edge Pool and select New Edge Pool.

5. In Define New Edge Pool, click Next.

6. In Define Edge Pool FQDN, do the following:

○ In FQDN, type the fully qualified domain name (FQDN) selected for the inner end of the edge pool.

Important Note:

The name specified for the pool must be an inner edge pool name. This name must be defined as FQDN. Topology Generator uses FQDN instead of short names. Use only standard characters (including A-Z, a-z, 0-9, and hyphens) when assigning FQDN for Lync Server, Edge Server, and Pool. Do not use Unicode characters or underscores. External DNS and public CAs generally do not support the use of non-standard characters in an FQDN when an FQDN must be assigned to an SN in a certificate.

○ Click Multi-computer Pool, and then click Next.

SFBEdgePool01.i-x-Cloud.com

7. In Enable Federation, do the following:

○ If you plan to enable federation, select the Enable federation for this edge pool (port 5061) check box.

Note:

You can select this option, but only one edge pool or edge server in the organization can be published for federation. All access from federated users, including public instant messaging (IM) users, will go through the same edge pool or single edge server. For example, if one edge pool or single edge server in a deployment is deployed in New York and another in London, and federation support is enabled for the edge pool or single edge server in New York, signal traffic for federated users will pass through the edge pool or single edge server in New York. The same applies to traffic from London users, although calls from London internal users to London Alliance users will route A/V traffic using London pool or edge servers.

○ If you plan to support Extensible Messaging and State Protocol (XMPP) for deployment, select the Enable XMPP Federation (port 5269) check box.

8. In Select Features, do the following:

○ If you plan to use a single FQDN and IP address for SIP Access Services, r Web Conferencing Services, and A/V Edge Services, select the Use a single FQDN and IP address check box.

9. Click Next. In Select IP Options, do the following:

▪ Enable IPv4 on internal interfaces: Select this check box if you need to apply IPv4 addresses to edge server or edge pool internal interfaces

▪ Enable IPv6 on internal interfaces: Select this check box if you need to apply IPv6 addresses to edge server or edge pool internal interfaces

▪ Enable IPv4 on external interfaces: Select this check box if you need to apply IPv4 addresses to edge server or edge pool external interfaces

▪ Enable IPv6 on external interfaces: Select this check box if you need to apply IPv6 addresses to edge server or edge pool external interfaces

Important Note:

Do not select the "External IP addresses of edge pools are translated by NAT" check box. Network Address Translation (NAT) is not supported when hardware load balancing is used.

10. In External FQDN, do the following:

○ If you selected to use a single FQDN and IP address for SIP Access, Web Conferencing Services, and A/V Edge Services in Select Features, type the external FQDN in SIP Access.

Note:

If you select this option, you must specify a different port number for each edge service (recommended port settings are: 5061 for Access Edge, 444 for Web Conferencing Edge, and 443 for A/V Edge). Selecting this option helps prevent potential connectivity problems and simplifies configuration because the same port number (for example, 443) can be used for all three services.

○ If you did not select Use a single FQDN and IP address in Select Features, type the FQDN selected for the public side of the edge pool in SIP Access. In Web Conferencing, type the FQDN selected for the public side of the edge pool. In Audio/Video, type the FQDN selected for the public end of the edge pool. Use default port.

Note:

These FQDNs will be the pool's public virtual IP (VIP) FQDNs.

11. In Define computers in this pool, click Add.

12. In Define Internal IP Addresses, do the following:

13. In Define an External IP Address, do the following:

14. In Define Public IP Addresses, do the following:

15. Click Finish.

16. In Define computers in this pool, click Add, and repeat steps 17 through 21 for the second edge server you want to add to the edge pool.

17. In the Define Next Hop, Next Hop Pool list, select the name of the internal pool, which can be either a front-end pool or a Standard Edition pool. Or, if the deployment includes a controller, select the name of the controller. Then click Next.

18. In Associate Front-End Pools, specify one or more internal pools to associate with this edge server by selecting the name of the internal pool that this edge server uses to communicate with supported external users, which can include Front-End Pools and Standard Edition Servers.

Note:

Only one load-balanced edge pool or single edge server can be associated with each internal pool of A/V traffic. If you have associated an internal pool with an edge pool or edge server, a warning appears indicating that the internal pool is associated with an edge pool or edge server. If you select a pool that is already associated with another edge server, the association changes.

19. Click Finish.

20. In the Topology Builder console tree, right-click Skype for Business Server, and then click Publish Topology.

21. On the Welcome page of the wizard, click Next.

22. Click Finish.

23. Export topology and copy it to external media for edge installation

1)In the Skype for Business Server Management Shell, run the following cmdlets:

replication

Export-CsConfiguration -FileName

Export-CsConfiguration -FileName D:\CsConfiguration\CsConfiguration-081-SFBEdge01-2019-03-16-1510.zip

2)Export-Post

3)Copy exported files to external media (for example, USB drives or network shares accessible from edge servers during deployment).

Copy the exported file to Skype for Business Server 2015 Edge Server-SFBEdge01

CsConfiguration-SFBEdge01-2015-05-16-2030.zip

This article is finished!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.