Another reason to avoid virtualization is the complexity of
the network requirements, which I will address in the next section.
Planning for Network Interface Cards
To confi gure your consolidated Edge Server with all three services, you will need at least four
network interface cards (NICs) in your server: one for each of the three services, and a fourth
???internal??? interface for communications with the OCS front-end. Although it is possible to
use fewer than four NICs, I have found that confi guration is much simpler when you allocate
a separate NIC to each function. I??™ll explain why it??™s a bad idea to try to assign multiple
Internet Protocol (IP) addresses to the same NIC later in this section.
Planning DNS and IP Addressing
Planning for domain name system (DNS) and IP addresses ahead of time will save you major
headaches. Because the Edge Server requires so many different addresses and fully qualifi ed
domain names (FQDNs), you will fi nd yourself forgetting which address does what.
Creating DNS Entries
Each of the three services in the Edge Server needs an FQDN, such as sip.contoso.com for the
Access Edge service, conference.contoso.com for the Web Conferencing Edge service, and av.contoso.com
for the A/V Edge service. These are the names that external clients and servers use to reach
each service. Once you decide on FQDNs for your three services, create the corresponding
???A records??? in your external DNS server.
TIP
When deciding on a name for the FQDN for each service, try to use something
that describes the service rather than the actual server name.
Pages:
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196