Transcript The Design Process—Planning Understanding Capacity-Planning Considerations © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-1 Messaging Infrastructure Capacity Planning • Cisco Unity voice mail only.

The Design Process—Planning
Understanding Capacity-Planning
Considerations
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—2-1
Messaging Infrastructure Capacity Planning
• Cisco Unity voice mail only with independent mailstore
– Messages kept on Cisco Unity server or offbox on
Exchange servers specifically used for Cisco Unity
voice messages
• Cisco Unity unified messaging
– Cisco Unity obeys Exchange 2000 and 2003 storage limits
– Mailbox size increased
– Storage retention policy
– Storage codec
– Logon sessions increased
• Are messaging servers located by Cisco Unity or will new
messaging servers be needed?
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—2-2
Telephony Infrastructure Capacity Planning
• Circuit-switched PBX integration method may require
additional line cards for PBX.
• Traffic analysis
– Auto Attendant
– TRaP
• IP integration
– Create voice-mail ports
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—2-3
Network Infrastructure Capacity Planning
• Additional domain controllers or global catalog servers?
• Domain controller can be on box in voice mail. Not an option
for unified messaging. One domain controllers or global
catalog for every four Exchange message stores.
• Active Directory size increases by about 10% with schema
extensions.
• Cisco Unity can service one forest, up to three Windows sites
in one Windows domain.
• Bandwidth is a consideration.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—2-4
Cisco Unity Server Capacity Planning
• Number of subscribers
• Cisco Unity platform overlay
• Port usage
• Exchange or Domino topology
– Location
– Design rules
• One Cisco Unity can support 10 Exchange servers.
• One Cisco Unity per Exchange administrative group.
• One Cisco Unity per Domino domain.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—2-5
Example: Cisco Unity Platform Overlays
Description
Platform Overlay Number 1
Platform Overlay Number 2
Platform Overlay Number 3
Specifications
• Single processor
• Single processor
• Dual processors
• 1-GB RAM
• 2-GB RAM
• 4-GB RAM
• 1 x 80-GB SATA hard drive
• 2 x 72-GB SCSI hard drives,
RAID 1
• 4 x 72-GB SCSI hard drives, 2 x
RAID 1
or
or
• 2 x 80-GB SATA hard drives,
RAID 1
• 4 x 72-GB + 2 x 144-GB hard
drives, 3 x RAID 1
Ports
24
48
72/96*
TTS sessions
12
24
36
Voice-mail users
(on-box Exchange message store)
1000
2000
4000
Unified messaging users
or Voice-mail users
(off-box message store)
1000
2000
7500
Message store users
(non-IMAP, off box)
1000
2000
4000
Message store users
(with Groupwise connector, off-box)
500
1200
2500
Unity Inbox users
500
1000
1500
Usable as DC/GC Server
Yes
Yes
N/A
(3 x RAID 1 configuration only)
(3 x RAID 1 configuration only)
* Starting with Unity 4.2(1), 96 ports currently supported for all integrations except integrations using Dialogic voice cards. 72 ports supported for
Dialogic voice card integrations.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—2-6
Example: Exchange Topology
Site A
Site B
Exchange
2000
DC
DDNS
DC/GC Exchange
DDNS
2000
WAN
Cisco Unified
Call Manager1
Cisco Unified
Call Manager2
Workgroup
© 2006 Cisco Systems, Inc. All rights reserved.
DC/GC
DDNS
Cisco
Unity
Cisco
Unity
CUDN v1.1—2-7
Summary
• Taking time to adequately plan for capacity is critical for
successful Cisco Unity deployments.
• Factors for capacity planning include mailstore, telephony,
network, and Cisco Unity servers.
• Mailstore capacity planning should consider factors such as
unified messaging vs. voice mail only and on-box vs. off-box
message store.
• Telephony capacity planning will be influenced by the use of IP
vs. circuit-switched PBX and possibly the number of voice-mail
ports required.
• Networking capacity planning needs to consider access to
resources such as domain controllers and global catalogs.
Adequate bandwidth is an important consideration.
• Cisco Unity capacity planning is influenced by the messaging
system topology, subscriber population, voice port usage, and
design rules.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—2-8
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—2-9