Table Of Contents
Preparing for the Installation
Obtaining Cisco Unity License Files
Gathering Documentation and Tools
Determining the Drive Locations for Files on the Cisco Unity System
Drive Locations for Files on a Small-Scale System
Drive Locations for Files on a Medium-Scale System
Drive Locations for Files on a Large-Scale System
Preparing for the Installation
Note 
Failover: If you are installing the secondary Cisco Unity server now, skip this chapter.
In this chapter, you do the following tasks in the order listed:
1. Complete registration information on Cisco.com to obtain the applicable license files. See the "Obtaining Cisco Unity License Files" section.
2. Gather the documentation and tools needed for the installation. See the "Gathering Documentation and Tools" section.
3. Determine and record the drive locations for application, log, and database files on the Cisco Unity system. See the "Determining the Drive Locations for Files on the Cisco Unity System" section.
When you are finished with this chapter, return to the "Overview of Mandatory Tasks for Installing Cisco Unity" to continue installing the Cisco Unity system correctly:
Note The tasks in the list reference detailed instructions in the Cisco Unity Installation Guide and in other Cisco Unity documentation. Follow the documentation for a successful installation.
Obtaining Cisco Unity License Files
License files, which enable the features purchased by the customer, are required for installing Cisco Unity software, for some upgrades, and for adding or changing licensed features. You obtain the license files by completing registration information on Cisco.com.
Shortly after registration, Cisco e-mails the license files. The e-mail from Cisco contains instructions on how to save and store the files. The Cisco Unity Installation Guide later provides specific instructions on the use of the license files. (For more information on licensing, refer to White Paper: Licensing for Cisco Unity at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/licenses.htm.)
Note If the system is using failover, you install the license files only on the primary server.
The following information is required during registration:
•The MAC address (physical address) for the network interface card (NIC) in the Cisco Unity computer.
•The product authorization key (PAK), which appears on the sticker located on the front of the sleeve for Cisco Unity DVD 1 or CD 1.
Do the following two procedures in the order listed.
To Get the MAC Address of the Cisco Unity Computer
Step 1 On the computer on which Cisco Unity will be installed, on the Windows Start menu, click Programs > Accessories > Command Prompt.
Step 2 In the Command Prompt window, enter ipconfig /all, and press Enter.
Step 3 Write down the value of Physical Address, excluding the hyphens, or save it to a file that you can access during online registration. (For example, if the physical address is 00-A1-B2-C3-D4-E5, record 00A1B2C3D4E5.)
If the server contains more than one NIC, one value will appear for each NIC. Use the value for the primary NIC.
Step 4 Close the Command Prompt window.
To Register and Obtain the License Files
Step 1 Browse to the applicable registration site (URLs are case sensitive):
Step 2 In the Voice Products section, under Cisco Unity Software, click 4.0 New Install & Add-On Feature Licenses.
Step 3 Enter the requested information, and click Submit.
Step 4 Shortly after registration, you will receive an e-mail with the Cisco Unity license files.
If license files are lost, it can take up to one business day to get another copy.
If you do not receive the license files within 1 hour or to get another copy of a license file, call the Cisco Technical Assistance Center (TAC) and ask for the Licensing Team:
Or send e-mail to licensing@cisco.com.
You will need to provide information to verify Cisco Unity ownership—for example, the purchase order number or the PAK (which appears on the sticker located on the front of the sleeve for Cisco Unity DVD 1 or CD 1).
Note Cisco Unity software comes with a default license file that has a minimal number of settings. The license file allows installation of a Cisco Unity demonstration system. For information and instructions on installing a demonstration system, refer to the "Installing a Cisco Unity Demonstration System" section of the Cisco Unity release notes.
Gathering Documentation and Tools
You need the following items during the installation and configuration of the Cisco Unity system:
•Access to the following Cisco Unity documentation.
–Release Notes for Cisco Unity Release 4.0(3).
–Release Notes for Cisco Unity 4.0(3) Service Release 1.
–The Cisco Unity Installation Guide, Release 4.0(3).
–The Cisco Unity integration guide(s) for your phone system(s).
–If you are integrating Cisco Unity with Cisco CallManager, release notes for the applicable version of the Cisco Unity-CM TSP.
–The Cisco Unity System Administration Guide, Release 4.0(3).
–If you are setting up failover, the Cisco Unity Failover Configuration and Administration Guide, Release 4.0.
–If you are setting up Cisco Unity Digital Networking, AMIS, SMTP, or VPIM Networking, the Networking in Cisco Unity Guide, Release 4.0(3).
–If you are setting up Bridge Networking, release notes for the applicable version of the Cisco Unity Bridge, the Cisco Unity Bridge Installation Guide, Release 3.0, and the Cisco Unity Bridge Networking Guide, Release 3.0.
–If you are setting up AMIS, Bridge, SMTP, or VPIM Networking, release notes for the applicable version of the Cisco Unity Voice Connector for Microsoft Exchange.
Cisco Unity documentation is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_technical_documentation.html.
•A blank 3.5-inch 1.44-MB disk for creating an emergency repair disk.
•Two test phones.
Determining the Drive Locations for Files on the Cisco Unity System
You plan drive locations for application, log, and database files on the Cisco Unity system:
•To maximize performance, data integrity, and reliability for Cisco Unity, Microsoft Exchange, and SQL Server or MSDE transaction logs.
•To maximize performance, data storage, and access capacity for Cisco Unity data.
The way in which logical drives on the Cisco Unity server are set up and which application, log, and database files are located on the drives depend on the size of the Cisco Unity system, the RAID volume configuration used, whether the system will be installed as Voice Messaging (VM) or as Unified Messaging (UM), and whether Exchange is used on a separate server or on the Cisco Unity server.
Note If the system is using failover, the file locations must be the same on the primary and secondary servers.
Using one of the following sections, make note of the applicable drive locations for files on the Cisco Unity system that you are installing:
•Drive Locations for Files on a Small-Scale System
•Drive Locations for Files on a Medium-Scale System
•Drive Locations for Files on a Large-Scale System
The Cisco Unity Installation Guide alerts you when to refer to the file locations later in the installation process.
Drive Locations for Files on a Small-Scale System
A small-scale system has a maximum of 1,100 users and 32 ports.
Table 2-1 applies to the following small-scale RAID volume configurations:
•Single RAID 1 volume
•Single RAID 5 volume
•No RAID (Use the drive locations for the applicable Exchange configuration—on a separate server or on the Cisco Unity server.)
Note Except for the system drive, drive C, different drive letters may be used to label the drives.
Table 2-1 Drive Locations for Files on a Small-Scale System
Logical Drive
|
Files for Voice Messaging
with Exchange on the Cisco Unity Server
|
Files for Voice Messaging or Unified Messaging
with Exchange on a Separate Server
|
C
|
•Operating system
•Pagefile
•MSDE binaries (application with associated files)
|
•Operating system
•Pagefile
•MSDE binaries (application with associated files)
|
D
|
•Message store (Exchange)
•Exchange transaction logs
•SQL Server 2000 or MSDE 2000 databases
•SQL Server or MSDE transaction logs
•Unity Message Repository (UMR)
•Binaries (applications with associated files, including Cisco Unity and SQL Server)
•Cisco Unity trace logs
|
•SQL Server 2000 or MSDE 2000 databases
•SQL Server or MSDE transaction logs
•Unity Message Repository (UMR)
•Binaries (applications with associated files, including Cisco Unity and SQL Server)
•Cisco Unity trace logs
|
Drive Locations for Files on a Medium-Scale System
A medium-scale system has a maximum of 2,200 users on the Cisco Unity server or 2,500 users on a separate server, and more than 32 but no more than 48 ports.
Table 2-2 applies to the following medium-scale RAID volume configurations:
•Three RAID 1 volumes.
•Two RAID 1 volumes.
•Single RAID 1 volume and a single RAID 5 volume (with or without a hot spare drive).
Note Except for the system drive, drive C, different drive letters may be used to label the drives.
Table 2-2 Drive Locations for Files on a Medium-Scale System
Disk Array
|
Logical Drive
|
Files for Voice Messaging
with Exchange on the Cisco Unity Server
|
Files for Voice Messaging or Unified Messaging
with Exchange on a Separate Server
|
First
|
C
|
•Operating system
•Pagefile
|
•Operating system
•Pagefile
|
First
|
D
|
•Binaries (applications with associated files, including Cisco Unity, Exchange 2000, and SQL Server 2000)
•Cisco Unity trace logs
|
•SQL Server 2000 transaction logs
•Binaries (applications with associated files, including Cisco Unity, and SQL Server 2000)
•Cisco Unity trace logs
|
Second
|
E
|
•Exchange transaction logs
•SQL Server 2000 or MSDE 2000 transaction logs
|
•SQL Server 2000 databases
•Unity Message Repository (UMR)
|
Third
|
F
|
•Exchange 2000 databases
•SQL Server 2000
•Unity Message Repository (UMR)
|
N/A
|
Drive Locations for Files on a Large-Scale System
A large-scale system has a maximum of 3,000 users on theCisco Unity server or 7,500 users on a separate server, and more than 48 ports.
Table 2-3 applies to the following large-scale RAID volume configurations:
•Three RAID 1 volumes.
•Two RAID 1 volumes and a single RAID 5 volume (with or without a hot spare drive).
•Two RAID 1 volumes and a single RAID 10 volume (with or without a hot spare drive).
•Two RAID 1 volumes (with Exchange on a separate server).
Note Except for the system drive, drive C, different drive letters may be used to label the drives.
Table 2-3 Drive Locations for Files on a Large-Scale System
Disk Array
|
Logical Drive
|
Files for Voice Messaging
with Exchange on the Cisco Unity Server
|
Files for Voice Messaging or Unified Messaging
with Exchange on a Separate Server
|
First
|
C
|
•Operating system
•Pagefile
|
•Operating system
•Pagefile
|
First
|
D
|
•Binaries (applications with associated files, including Cisco Unity, and SQL Server 2000)
•Cisco Unity trace logs
|
•Binaries (applications with associated files, including Cisco Unity, and SQL Server 2000)
•SQL Server 2000 transaction logs
•Cisco Unity trace logs
|
Second
|
E
|
•Exchange transaction logs
•SQL Server 2000 transaction logs
|
•SQL Server 2000 databases
•Unity Message Repository (UMR)
|
Third
|
F
|
•Exchange 2000 databases
•SQL Server 2000 databases
•Unity Message Repository (UMR)
|
N/A
|
Feedback
