Edge Server scenarios in Skype for Business Server 2015

Skype for Business Server 2015
 

마지막으로 수정된 항목: 2015-08-18

Summary: Review these scenarios to help you plan your 에지 서버 topology in 비즈니스용 Skype 서버 2015 .

We have some scenarios diagrams to assist with visualizing and deciding on what 비즈니스용 Skype 서버 에지 서버 topology you want to implement. Once you've picked a good candidate, you can go read up on the environmental requirements you'll need to address. The following is applicable to any of the scenarios, so we're mentioning it first.

These figures, which are shown for example purposes only (and as such contains sample IPv4 and IPv6 data), don't represent the actual communication flow, but rather a high-level view of your possible traffic. Port details can also be seen in the Port diagrams for each scenario below.

The diagrams show .com for the external interface and .net for the internal, which is also sample material; of course your own entries may be quite different when you're putting together your own final Edge plan.

We don't include the 디렉터 (which is an optional component) in any of the diagrams, but you can read about that separately (it's mentioned in other Planning topics).

As noted above, there is sample IPv6 data in the diagrams. Most of the documentation in Plan for Edge Server deployments in Skype for Business Server 2015 will refer to IPv4, but you are certainly supported if you want to use IPv6. Note that you'll need IPv6 addresses in your assigned address space, and they'll need to work with internal and external addressing, as with IPv4 IPs. You can, thanks to Windows, employ the dual stack feature, which is a separate and distinct network stack for IPv4 and IPv6. This will, if you need, allow you to assign IPv4 and IPv6 addresses concurrently.

There are NAT devices that allow for NAT64 (IPv6 to IPv4) and NAT66 (IPv6 to IPv6)), and this is valid for use with 비즈니스용 Skype 서버.

important중요:
If you're using Call Admission Control (CAC) you do have to use IPv4 on the internal interface for it to work.

With this scenario, there is no option for high availability. This will mean you spend less on hardware and have a simpler deployment. If high availability is a must, check out the Scaled consolidated scenarios below.

NAT를 사용하는 개인 IP 포함 단일 통합 에지용 에지 시나리오

We also have a diagram for ports for single consolidated 에지 서버.

에지 시나리오 단일 통합 에지용 네트워크 경계

With this scenario, there is no option for high availability. This will mean you spend less on hardware and have a simpler deployment. If high availability is a must, check out the Scaled consolidated scenarios below.

공용 IP 포함 단일 통합 에지용 에지 시나리오

We also have a diagram for ports for single consolidated 에지 서버.

에지 시나리오 단일 통합 에지용 네트워크 경계

With this scenario, you are able to have high availability in your Edge deployment, which gives you the advantages of scalability and failover support.

확장 통합 에지용 에지 시나리오, NAT를 사용하는 개인 IP 포함 DNS LB

We also have a diagram for scaled consolidated 에지 풀 with DNS load balancing.

DNS LB를 사용하는 에지 시나리오 확장 통합 에지용 네트워크 경계

With this scenario, you are able to have high availability in your Edge deployment, which gives you the advantages of scalability and failover support.

확장 통합 에지용 에지 시나리오, 공용 IP 포함 DNS LB

We also have a diagram for scaled consolidated 에지 풀 with DNS load balancing.

DNS LB를 사용하는 에지 시나리오 확장 통합 에지용 네트워크 경계

With this scenario, you are able to have high availability in your Edge deployment, which gives you the advantages of scalability and failover support.

HLB 포함 확장 통합 에지용 에지 시나리오

We also have a diagram for scaled consolidated 에지 풀 with hardware load balancing

에지 서버 경계 네트워크 포트 및 프로토콜
 
표시: