2
Table of Contents
LIST OF FIGURES ... 4
LIST OF TABLES... 5
OVERVIEW ... 6
START HERE: PLAN YOUR JUNIPER/MICROSOFT OCS NETWORK IN THREE STEPS
...
INTRODUCTION... 7
SCOPE
... 8
T
ARGETA
UDIENCE... 8
INTRODUCING MICROSOFT OFFICE COMMUNICATIONS SERVER 2007 R2... 9
MICROSOFT OCS 2007 R2 VERSIONS
... 9
Microsoft OCS 2007 R2 Standard Edition ... 9
Microsoft OCS 2007 R2 Enterprise Edition... 10
MICROSOFT OCS 2007 R2 DEPLOYMENT SCENARIOS
... 12
MICROSOFT OCS 2007 R2 REQUIREMENTS
... 12
MEDIATION SERVER
... 13
MEDIA GATEWAY INTEGRATION
... 13
OCS 2007 R2 IN A JUNIPER NETWORKS DISTRIBUTED ENTERPRISE ... 14
WHAT DOES JUNIPER OFFER?... 14
JUNIPER DISTRIBUTED ENTERPRISE COMPONENTS
... 15
EX Series Ethernet Switches ... 16
M/MX Series with IMSG... 17
SRX Series Services Gateways for the Branch ... 17
Additional Components ... 18
STEP 1: DESIGN THE NETWORK ARCHITECTURE ... 20
DATA CENTER ARCHITECTURE CONSIDERATIONS
... 20
CAMPUS AND OFFICE CONSIDERATIONS... 21
Layer 3 Recommendations ... 21
LAN Considerations... 22
Wireless LAN Considerations ... 22
WAN Considerations... 23
LAN and WAN Connectivity Recommendations... 23
WAN C
ONNECTIVITYC
ONSIDERATIONS: O
PTIMIZEM
EDIAR
OUTING... 24
6
Overview
This planning guide presents the Quality of Service (QoS) and connectivity considerations that are important for a successful implementation of Microsoft Office Communications Server (OCS) 2007 R2 in a Juniper Distributed Enterprise network. The guide describes how to determine the bandwidth requirements for the five key architectures that make up Juniper’s distributed enterprise: small office/home office (SOHO), remote office, medium‐to‐large branch office, campus/headquarters, and the data center. When you are planning a Microsoft OCS 2007 R2 implementation in a Juniper distributed enterprise, start by learning about the components. • For a brief introduction to Microsoft OCS 2007, including a description of versions, deployment scenarios, and a summary of requirements, see Introduction to Microsoft Office Communications Server 2007 R2. • For a description of a Juniper Distributed Enterprise and its components, including the SRX Series Services Gateway and the EX Series Ethernet Switches, see OCS 2007 R2 in a Juniper Networks Distributed Enterprise and Juniper DistributedEnterprise Components. A table in this section shows the Juniper solution components that enable an OCS implementation. Note that security is also a consideration. However, this document focuses on QoS only; security considerations are covered in other documents.
Start Here: Plan Your Juniper/Microsoft OCS Network in Three Steps
To plan your Microsoft OCS 2007 R2 implementation in a Juniper Distributed Network, you need to take a few basic steps. These steps include (but are not limited to) the following: 1. Step 1: Design the Network Architecture: engineer your network topology to optimize the media path. To ensure efficient network operation, you must seek the shortest media path by minimizing the number of hops (or links) used in order to minimize delay. You should therefore design the most appropriate high‐level topology—mesh or hub‐and‐ spoke, as well as consider the point of connection to remote telecommuters and SIP trunks—so that you have as much direct traffic as possible. See Step 1: Design the Network Architecture. 2. Step 2: Design the QoS Configuration: plan forwarding queues. Once your architecture design is stable, plan the use of forwarding queues throughout the network, including priority and bandwidth allocation. See Step 2: Design the QoS Configuration. Also see Packet Flow in a QoS Router and Juniper QoS Recommendations.3. Step 3: Analyze Delay and Jitter: verify that the expected delays for your implementation are acceptable.
9
Introducing Microsoft Office Communications Server 2007 R2
14
OCS 2007 R2 in a Juniper Networks Distributed Enterprise
16 Figure 5. Juniper Distributed Enterprise components.
EX Series Ethernet Switches
17 EX Series switches support eight QoS queues per port, ensuring proper prioritization of control plane, voice, video, and multiple levels of data traffic—with room to converge other networks, such as when adding automation and video security systems. Additional features that are VoIP or UC specific include: • Support for LLDP and LLDP‐ME, which enables the switches to automatically discover Ethernet‐enabled devices, determine their power requirements, and assign virtual LAN (VLAN) parameters. • Class 3 PoE with 15.4 W on some or all ports to VoIP phones, closed‐circuit security cameras, wireless access points, and other IP‐enabled devices. • 802.1X with VoIP VLAN support, which provides 802.1X (port‐level) access control as well as Layer 2‐4 policy enforcement based on user identity (such as those contained in Microsoft Active Directory), locations, and/or device.
M/MX Series with IMSG
Juniper M Series Multiservice Edge Routers (M7i, M10i, M120, and M320) have a wide array of WAN interfaces typically deployed in head office locations that require high‐performance packet processing, such as Internet gateways, WAN aggregation devices, data center routers, or backbone routers. The Juniper MX Series 3D Universal Edge Routers (MX80, MX240, MX480, and MX960), are optimized for Ethernet and provide high‐ performance and high port‐density routing and switching in both campus core and aggregation, in data center core and aggregation, and WAN edge. The M and MX Series offer IMSGs with session border control (SBC) in the core, as well as IPS, GW, IPsec, and video QoS monitoring. For the data center or large campus with many endpoints, IMSG provides large‐scale peering between the enterprise and the carrier or service provider. The Juniper IMSG package is similar to STEP, but can do much more, including the following: • Routing SIP properly. • Managing trunks and multiple carriers. • Controlling bandwidth between the enterprise and the service provider. • Providing security to prevent outside attacks.SRX Series Services Gateways for the Branch
Juniper Networks SRX Series Services Gateways provide the essential capabilities necessary to connect, secure, and manage enterprise and service provider networks, from the smallest sites to the largest headquarters and data centers. When they consolidate switching, routing, and security services in a single device, organizations can economically deliver new applications and services, secure connectivity, and ensure quality end‐user experiences. The SRX series is offered in versions for the branch (SRX100, SRX 210, SRX240, and SRX650), and for the data center (SRX3400, SRX3600, SRX5600, and SRX5800). SRX Series Services Gateways for the BranchThe SRX Series Services Gateways for the Branch (SRX100, SRX 210, SRX240, and SRX650) combine JUNOS routing, switching and security with integrated convergence services (ICS) security within a single device.
Features of the SRX Series Gateways for the Branch include: • OCS 2007 R2‐compatible Direct SIP Media Gateway
19 o SA Series SSL VPN Appliances: Feature best‐in‐class performance, scalability, and redundancy for organizations requiring high‐volume secure access and authorization. o Unified Access Control (UAC) Appliances: The IC4500 and IC6500 Unified Access Control Appliances are next‐ generation hardened, centralized policy management servers that deliver superior scalability, performance, and cryptographic operations for large, multinational organizations and government agencies. • For services: o J‐Care Technical Services: J‐Care Technical Services ensure rapid response from Juniper engineers and offer hardware replacement options so you can choose the timing and resources that are right for your network. • For routing: o MX Series Ethernet Services Routers: Provide Ethernet switching capabilities coupled with the carrier‐class routing features customers expect from Juniper. Table 1 lists the specific Juniper solution components for the distributed enterprise. Table 1. Juniper Solution Components that Enable Microsoft UC.
Enterprise Location Routing Switching Security/VPN Access Control WAN Optimization Policy Management
Integrated Convergence Services Data center MX960 MX480 MX240 M320 M120 M10i EX820 EX4200 EX3200 ISG2000 ISG1000 NetScreen‐5400 NetScreen‐5200 IDP8200 SA6500 IC6000 IC4000 WXC Stack WXC3400 WXC2600 WXC590 WXC500 WXC250 IC6000 IC4000 SRX 3000 SRX Series Services Gateways for the Data Center (SRX3400, SRX3600, SRX5600, and SRX 5800) Campus/Headquarters M10i M71 EX8200 EX4200 EX3200 ISG2000 ISG1000 NetScreen‐5400 NetScreen‐5200 IDP8200 SA6500 SA4500 IC6000 IC4000 WXC3400 WXC2600 WXC590 WXC5000 IC6000 IC4000 SRX 650 SRX Series Services Gateways for the Data Center (SRX3400, SRX3600, SRX5600, and SRX 5800) Medium‐to‐Large branches SRX240
20
Step 1: Design the Network Architecture
23 best in both security and ease‐of‐use capabilities. Network architects tend to select the tighter security functionality with WiFi Protected Access (WPA) encryption and 802.1X authentication to provide a truly secure WLAN for the office. Additionally where needed, architects can grant open access to a wireless network with limited risk by employing the user‐identity‐based access control Layer 3 and/or Layer 2 security policies to allow different levels of user access for different functional groups (for example, Finance, Human Resources, or engineering departments).
For more information about WLAN, see the Juniper Research report, Broadband Wireless LAN. Also, see information about the AX411 WLAN access point at AX Series in the Juniper product documentation.
WAN Considerations
It is important to consider the competing demands of cost containment and increased network traffic. Since WAN costs typically account for the IT department’s highest expenditure after headcount, most enterprises do not have the luxury of simply adding more WAN capacity to their networks. A SOHO or branch office typically uses one or a combination of the following three WAN connection types: • Private Management of Point‐to‐Point circuits Typically these circuits will provide Layer 2 (L2) connectivity between two locations. A branch office is more likely to use this connection type, typically referred to as L2VPN or private circuits, where locations are permanent and the importance of data communications is high. • Provider Provisioned VPN (PPVPN) With PPVPN, the enterprise receives a full mesh of connectivity between multiple nodes. Normally referred to as MPLS L2/L3 VPN, this connectivity is typically managed by the service provider, and the provider manages routing, or metro Ethernet switching if it’s L2, to form a full meshed topology. • The Internet This is usually a connection between sites over the Internet, wired or wireless, with IPsec tunneling to secure the internal traffic. A WAN optimization and application acceleration platform must have specific attributes in order to overcome the bandwidth, latency, congestion, and manageability issues that impede application performance over the WAN. It must also support QoS and bandwidth optimization features that are critical to deployment of real‐time applications like voice and video.For information about Juniper WAN acceleration (WX/WXC platforms), see WXC Series in the Juniper product documentation.
29
Step 2: Design the QoS Configuration
32 Forwarding class is assigned with packet loss priority (PLP) and DiffServ code points, which are used for queuing and BA in the core router. For the following UC applications, Juniper recommends the following classifiers and PLP (also known as drop precedence). Packet loss priority sets the packet drop precedence value (low or high) to help prevent queue congestion. Packets with a low PLP have higher buffer thresholds than packets with a high PLP. By default, the high threshold is 100 percent of the buffer. Table 2 shows the recommendation for DiffServ and PLP for voice, video, and other network traffic. Table 2. DiffServ Recommendations.
Applications DiffServ PLP Network Control CS6 Low
Voice EF Low
Video CS4 AF41 AF42 AF43 Low High Bandwidth Application AF21 AF22 AF23 Low High
33
Step 3: Analyze Delay and Jitter
36 Table 5. RTAudio Information.
* This is on a wideband MOS scale
Table 6 provides capacity planning information. Table 6. Audio Capacity Planning.
Media Codec Average Bandwidth (Kbps) Estimated Activity (%) Bandwidth (Kbps) Maximum
Wide Band Audio RTAudio 34.8 61 57 Wide Band Audio Siren 22.2 43 51.6 Narrow Band Audio RTAudio 25.9 65 39.8 Note that for the values in the tables: • Bandwidth numbers quoted for media streams include all overhead for framing, encryption, and IP routing information in addition to actual encoded media. • Average codec bandwidth values are based on measurements and derived from the maximum theoretical bandwidth based on typical activity level values. Audio activity levels take voice activity in the stream into account. • Activity levels for RTAudio narrow band are slightly higher to allow for less optimal voice activity detection in PSTN Gateways for OCS VoIP‐to‐PSTN calls. This number should be increased by another 15 percent if no voice activity detection is enabled on the deployed PSTN Gateway. Codec and Bit Rate (Kbps) Codec Sample
Size (Bytes) Codec Sample Interval (ms) Mean Opinion Score (MOS)
40
Sample Deployment of Microsoft OCS 2007 R2 within the Juniper
51
Figure 20 shows a typical architecture for a data center.
52 Table 19 shows the number of branches and headquarters that can be aggregated to a Juniper Networks data center with the different WAN bandwidth interfaces. Table 19. Branches and Campus/Headquarters Supported per Data Center with Different WAN Bandwidths. Location Mbps Support for 10 Gbps WAN
Interfaces Data Center Support for 40 Gbps WAN Interfaces Data Center
55 The following tables summarize the end‐to‐end delays under different sets of assumptions. Note that “WAN” indicates delay introduced by WAN: a typical rule of thumb is 1 ms for every 100 miles. (NA indicates cases where there is no direct traffic possible due to the IPsec topology.) Table 20 shows the various combinations of delay from the four different distributed enterprise network branches, assuming RTP flows directly between the sites and congestion occurs at both ends. Table 20 Worst Delay from Different Distributed Enterprise Networks Location Delay/Worst Delay (ms) SOHO (32 ms) Remote Office (36 ms) Medium/Lar ge Branches (37 ms) Campus/HQ (48 ms)
SOHO (32 ms) 64 + WAN* 68 + WAN* 69 + WAN* 80 + WAN
Remote office (36 ms) 68 + WAN* 72 + WAN* 73 + WAN* 84 + WAN
Medium/large branches (37 ms) 69+ WAN* 73 + WAN* 74 + WAN 85 + WAN
Campus/HQ (48 ms) 80 + WAN 84 + WAN 85 + WAN 96 + WAN
* Assumes direct IPsec connection site to site, or through group VPN. Table 21 shows the end‐to‐end delays with direct RTP flow between branches when only one end is congested. Table 21 Worst/Best Delays from Different Branch Types Location Delay Worst/Best Delay (ms) SOHO (22 ms) Remote Office (22 ms) Medium/Lar ge Branches (22 ms) Campus/HQ (4.5 ms)
SOHO (32 ms) 54 + WAN* 54 + WAN* 54 + WAN* 36.5 + WAN
Remote office (36 ms) 58 + WAN* 58 + WAN* 58 + WAN* 40.5 + WAN
Medium/large branches (37 ms) 59 + WAN* 59 + WAN* 59 + WAN 41.5 + WAN
Campus/HQ (48 ms) 70 + WAN 70 + WAN 70 + WAN 52.5 + WAN
56 Table 22 lists the delays when RTP flows through the data center and IP sec/ MPLS are terminated and rerouted to other sites. In this table, it is assumed that only one end is congested. Table 22 Delays if All Connections are Terminated and WAN Queuing at Datacenter. Location Delay Worst/Best Delay
(ms) SOHO (22 ms) Remote Office
(22 ms) Medium/Lar ge Branches (22 ms) Campus/HQ (4.5 ms)
SOHO (32 ms) 80 + 2xWAN 80 + 2xWAN 80 + 2xWAN 62.5 + WAN
Remote office (36 ms) 84 + 2xWAN 84 + 2xWAN 84 + 2xWAN 66.5 + WAN
Medium/large branches (37 ms) 85 + 2xWAN 85 + 2xWAN 85 + WAN 67.5 + WAN
Campus/HQ (48 ms) 96 + WAN 96 + WAN 96 + WAN 78.5 + WAN
57
Links for Further Information
The following links provide information about Microsoft OCS.
• Office Communications Server 2007 R2 Technical Reference Guide provides detailed technical reference information for administrators who are deploying, have deployed, or are administering Microsoft OCS 2007 R2.
• Office Communications Server 2007 R2 Technical Overview provides a technical overview of many OCS features, with an emphasis on features introduced in Microsoft OCS 2007 R2.
• The Microsoft TechNet portal for Office Communications Server includes a wealth of resources for OCS, as well as technical forums where you can ask specific questions. • The capacity planning requirements for OCS 2007 R2 are described in the TechNet article Capacity Planning. • For more information about RTAudio, see the Overview of the Microsoft RTAudio Speech Codec. • For the internal hardware and software requirements for OCS 2007 R2, see Internal Office Communications Server Component Requirements. • For a PDF of a PowerPoint deck, see Architecture, Implementing, and Migrating to Office Communications Server 2007 R2. • For a map of available documentation for Microsoft OCS 2007 R2, see the Microsoft Office Communications Server 2007 R2 Documentation Roadmap. • For a discussion of QoE in Microsoft implementations, see Quality of Experience: A strategic competitive advantage of Microsoft Unified Communications. The following links provide information about Juniper Networks. • For information about the Juniper Distributed Enterprise, see The New Network Has Distributed Enterprise Solutions. • For the press release, see Juniper Networks Introduces Distributed Enterprise Solutions with New SRX Services Gateways and EX Series Ethernet Switches.
• For a solution brochure, see Distributed Enterprise Solutions. Also see Distributed Enterprise Solutions for the Branch and Distributed Enterprise Solutions for the Campus.
• For a discussion of Juniper Networks’ approach to the branch offices, see Branch Office Reference Architecture.
58
About Juniper Networks
59
Appendix: Public and Private WAN Latency
This section provides public data from a variety of Internet/WAN providers as to typical latency over long‐haul WAN networks.
AT&T
http://ipnetwork.bgtmo.ip.att.net/pws/network_delay.html
60
Verizon Business
Private IP Service (MPLS)
http://www.verizonbusiness.com/about/network/latency/#pipInternet Service
Verizon Business Service Level Agreements (SLAs) guarantee Monthly latency figures of:
• 45 ms or less for regional round trips within North America • 30 ms or less for regional round trips within Europe
62
