Cisco Unity Connection can be deployed in either of the following ways: • Standalone Deployment: Involves the installation of a Unity Connection as a single server. • Cluster Deployment: Involves the installation of same version of two Unity Connection servers in an active-active or high availability mode.

During the installation of Unity Connection as a cluster, the first server is referred to as publisher server and the second server as the subscriber server. For more information on cluster configuration, see the chapter. Methods of Installation You can use either of the following methods to install standalone or cluster server: • Standard Installation: Allows you to manually specify the installation information, such as hostname and IP address using installation wizard. • Unattended Installation: Allows you to install Unity Connection using an installation disk and a pre-configured answer file floppy diskette.

The answer file has all the information required for unattended installation. With Unity Connection 10.5(2) release, a seamless process of installation has been introduced, which allows you to start installation on both the publisher and subscriber servers simultaneously. The subscriber installation continues when the publisher is successfully installed. This type of unattended installation is Touchless Installation. For more information on Touchless Installation, see the. Important Considerations for Installation Before you proceed with the installation, consider the following points: • Verify the system requirements, such as licensing and phone integration requirements necessary for the Unity Connection server in the System Requirements for Cisco Unity Connection guide. • Be aware that when you install on an existing Unity Connection server, the hard drive gets formatted and all existing data on the drive gets overwritten.

• Ensure that you connect each Unity Connection server to an uninterruptible power supply (UPS) to provide power backup and protect your system. Failure to do so may result in damage to physical media and require a new installation. • For a Unity Connection cluster: –Install the Unity Connection software first on the publisher server and then on the subscriber server (applicable to only standard installation scenarios). For more information on installation scenarios, see. –Note down the Security password that you mention at the time of installing publisher server. You need to specify the same password when installing the subscriber server in a cluster.

–Do not run Network Address Translation (NAT) or Port Address Translation (PAT) between the publisher and subscriber servers. • Verify that DNS server is properly configured before installing Unity Connection. For more information, see the. • Do not perform any configuration changes during the installation. • Be aware that the directory names and filenames that you enter during the installation are case-sensitive.

Important Notes Step 1 Ensure that your servers are listed as supported hardware and sized appropriately to support the load of the cluster. For information about the capacity of server models, see the link.

Step 2 Create the virtual machine using the correct OVA template. For more information, see the section.

Step 3 Change the boot order of the virtual machine to update the BIOS settings. For more information, see the section. Step 4 Configure an external NTP server during a Unity Connection server installation.

For a Unity Connection cluster, the NTP server helps to synchronize time between publisher and subscriber server. Ensure the external NTP server is stratum 9 or higher (meaning stratums 1-9). The subscriber server will get its time from the publisher server. To verify the NTP status of the publisher server, log into the Command Line Interface on the publisher server and enter the following command: utils ntp status For more information, see the Command Line Interface Reference Guide for Cisco Unified Solutions for the latest release, available. Step 5 Record the network interface card (NIC) speed and duplex settings of the switch port that connects to the new server. Enable PortFast on all switch ports that are connected to Cisco servers. With PortFast enabled, the switch immediately brings a port from the blocking state into the forwarding state by eliminating the forwarding delay [the amount of time that a port waits before changing from its Spanning-Tree Protocol (STP) learning and listening states to the forwarding state].

If you have at least 30 Gb free disk space (roughly half of which can be reclaimed after installation), you may choose to perform a full installation of Cygwin with all of its optional packages. This choice is recommended for those who prefer to work in a Unix or GNU/Linux environment but who are constrained to work under. Jan 20, 2014. Every source I found online says a full installation of Cygwin takes over 1 GB, but mine is only 100 MB. I was pretty sure I downloaded everything from the mirror servers, but the install took less than 5 minutes to complete instead of hours, as I'd expect if it were installing gigabytes of software.

Step 6 Record the configurations settings for each server that you plan to install. To record your configuration settings, see the section. Step 7 Download the signed.iso file of required Unity Connection version from Cisco.com.Upload it on a data store or burn a disk image of the downloaded software. Download from the given link.

Changing the Boot Order of Virtual Machine To Change the Boot Order of the Unity Connection Virtual Machine Step 1In VMware client, power off the virtual machine that has the deployed OVA template. Step 2In the left pane of VMware client, right-click the name of the virtual machine, and select Edit Settings. Step 3In the Virtual Machine Properties dialog box, select the Options tab. Step 4In the Settings column, from the Advanced menu, select Boot Options.

Step 5In the Force BIOS Setup, check the The next time the virtual machine boots, force entry into the BIOS setup screen. Step 6Select OK to close the Virtual Machine Properties dialog box. Step 7Power on the virtual machine. The virtual machine will boot into the BIOS menu.

Step 8Navigate to the Boot menu and change the boot device order so the CD-ROM device is listed first and the Hard Drive device is listed second. Step 9Save the change and exit BIOS setup. Changing Reservation on Virtual Machines Running with E7 or E5 Processors Added February, 2015 The CPU reservations are now included in OVAs, which are based on the Xeon 7500 processor. For E7 processors and certain E5 processors, the CPU reservations are higher than available cycles on 1 virtual CPU.

In such cases, the administrator needs to change the reservation number of the virtual machine manually using the steps mentioned in. Additionally, based on the lab tests, we see that the 2.4 GHz reservation on E7 or E5 processor has the same performance as a 2.53 GHz Xeon 7500 processor. For more information see the docwiki available. Changing the Reservation Numbers Step 1In VMware vSphere Client, select the host on which virtual machine is created. Step 2Click the Summary tab, under CPU, note the available CPU cycles for 1 virtual CPU in GHz. Step 3Power off the virtual machine on which you deployed the OVA template Step 4In the left pane of vSphere Client, right-click the name of the virtual machine and select Edit Settings. Step 5In the Virtual Machine Properties dialog box, select the Resources tab.

Step 6In the Settings column, select CPU. Step 7Under Resource Allocation, enter the new reservation value in the Reservation textbox. The new reservation value is calculated as the number of CPUsX2.4GHz (for E5440 processor) and the number of CPUs multiplied by the 1 virtual CPU cycles in GHz (from step 2) (for E7 processor). Step 8Click OK to close the Virtual Machine Properties dialog box. Step 9Power ON the virtual machine.

Yes, using the CLI command CLI >set timezone MTU Size: ______________________ Sets the largest packet, in bytes, that this host will transmit on the network. By default, MTU is set to the size defined in the operating system. Selecting a different packet size would be more prevalent where a VPN or IPsec tunnel is used with a custom packet size.

Web access over VPN can cause web pages not to load because of an improper MTU configuration. The MTU size that you configure must not exceed the lowest MTU size that is configured on any link in your network.

NoteIn clustered server pairs, the MTU setting must be the same on both servers. Yes, using the CLI command CLI >set network mtu Hostname and IP addresses: DHCP (Yes/No): ______ If DHCP is No: Hostname: _________________ IP Address: _________________ IP Mask: ___________________ Gateway (GW) Address:________ Sets whether to use DHCP to automatically configure the network settings on your server. If you select No, you must enter a hostname, IP address, IP address mask, and the gateway IP address.

The hostname can contain up to 64 alphanumeric characters, hyphens, underscores, and period. The first character cannot be a hyphen.

We recommend you use static Dynamic Host Control Protocol (DHCP) host configuration to ensure the DHCP server always provides the same IP address settings to the server NoteIf you do not have a gateway, you must still set this field to 255.255.255.255. Not specifying a gateway may limit you to only being able to communicate with devices on your subnet.

Yes, using the CLI command CLI >set network dhcp CLI >set network gateway CLI >set network ip eth0 Domain Name Server: DNS: (Yes/No): ______ If DNS is Yes: Domain: ____________________ DNS Primary: _________________ DNS Secondary: _______________ Sets whether a DNS server resolves a hostname and IP address. NoteUnity Connection enables the use of a domain name server to locate other Cisco Unity servers and devices. This is necessary when configuring digital networking and clustered server pairs. We recommend you to configure a secondary DNS server to avoid any loss of connectivity or service. Yes, using the CLI commands CLI >set network dns CLI >set network domain Administrator Account Credentials: Login: ____________________ Password: _________________ Sets the administrator credentials for secure shell access to the CLI and for logging into Cisco Unified Communications Operating System and Disaster Recovery System. The administrator account should be shared only with installers and engineers who have a thorough understanding and are responsible for platform administration and upgrades, and backup and restore operations. NoteEnsure the password is at least six characters long; it can contain alphanumeric characters, hyphens, and underscore.

Password: yes, using the CLI command CLI >set password user admin NoteYou can create additional administrator accounts after installation. Certificate Information: Organization: ____________________ Unit: ______________________ Location: _________________ State: ____________________ Country: _________________ Sets information used by the server to generate certificate signing requests (CSRs) that are used to obtain third-party certificates. TipTo enter more than one business unit name, separate the entries with a comma. For entries that already contain a comma, enter a backslash before the comma that is included as part of the entry. For location, you can enter any setting that is meaningful within your organization. Examples include the state or the city where the server is located.

Yes, using the CLI command CLI >set web-security Cluster: First server in cluster (Yes/No): ____ If First server is No: Publisher hostname: ____________ Publisher IP address: ____________ Publisher security password: ______ First server refers to the publisher server. During the installation of second or subscriber server, enter the details of the first server. NTP Servers: NTP Server 1: __________________ NTP Server 2: __________________ NTP Server 3: __________________ NTP Server 4: __________________ NTP Server 5: __________________ Sets the hostname or IP address of one or more network time protocol (NTP) servers that synchronizes with your Unity Connection server. The NTP service ensures that the time synchronized is accurate for date/timestamps of messages, reports, and various tools, such as logs and traces. All Unity Connection servers require an external NTP source that are accessible during installation. The source can be a corporate head-end router synchronized with a public NTP time server or it can be the public NTP time server itself.

NoteTo avoid potential compatibility, accuracy, and network jitter problems, the external NTP servers should be NTP v4 (version 4). If you are usingIPv6 addressing, external NTP servers must be NTP v6. NoteThe NTP server that you specify for the publisher server is automatically applied for the subscriber server. Yes, using Cisco Unified Operating System Administration: Settings >NTP Servers Using the CLI command CLI >using the CLI command Security Password Sets the password used by a subscriber server to communicate with a publisher server.

The security password is also used by the Disaster Recovery System to encrypt backups. The password must contain at least six alphanumeric characters. It can contain hyphens and underscores, but it must start with an alphanumeric character. Yes, using the CLI command CLI >set password user security. SMTP Server Sets the hostname or IP address for the SMTP server that is used for outbound e-mail, intrasite links, Voice Profile for Internet Mail (VPIM), and HTTPS networking. The hostname can contain alphanumeric characters, hyphens, or periods but it must start with an alphanumeric character. NoteYou must specify an SMTP server if you plan to use electronic notification.

Yes, using the CLI command: CLI >set smtp Application Account Credentials: Login: ____________________ Password: _________________ Sets the default credentials for the Unity Connection applications, including Cisco Unity Connection Administration and Cisco Unity Connection Serviceability. Yes, using Cisco Unity Connection Administration and the CLI command: CLI >utils cuc reset password. Installing the Publisher Server While installing a Unity Connection server, you are prompted to enter different configuration information. Refer the table mentioned in the section wherever applicable.

To Install a Unity Connection Publisher Server Step 1Prepare the virtual machine to install Unity Connection: a.Select Edit virtual machine settings to select the ISO image from CD/DVD drive using client device or from data store. B.Navigate to the Console tab. A screen prompting you to check the integrity of the DVD appears. C.Select Yes to perform the media check or Skip to move to the next step.

The Platform Installation Wizard window appears. Step 4In the Platform Installation Wizard window, select the applicable option: • If you want to perform a standard installation, select Proceed, and continue with this procedure. • If you want to perform an unattended installation, select Skip. Connect the answer file image on a virtual floppy diskette and select Continue. The installation wizard will read the configuration information during the installation process and then follow the steps mentioned in the section. Step 5If you select Proceed in the previous window, the Apply Patch window appears: • Select Yes to upgrade to a later Service Release of the software during installation and follow the process mentioned in the section.

• Select No to skip this step and the Basic Install window appears. Step 6In the Basic Install window, select Continue to install the software version or configure the pre- installed software. The Timezone Configuration window appears.

Step 7In the Timezone Configuration window, select the appropriate time zone for the server and then select OK. The Auto Negotiation Configuration window appears. The DHCP Configuration window appears. Step 10In the DHCP Configuration window, select the applicable option: • Select Yes to use DHCP server that is configured in your network.The network restarts and the Administrator Login Configuration window appears.

• Select No to configure a static IP address for the server and continue with this procedure. The Static Network Configuration window appears. Step 11In the Static Network Configuration window, enter the static network configuration information. The DNS Client Configuration window displays. Step 12To enable DNS, choose Yes, enter the DNS client information and select OK.

The network restarts using the new configuration information and the Administrator Login Configuration window appears. Step 13Enter the administrator login and password. The Certificate Information window appears. Step 14Enter your certificate signing request information and select OK. The First Node Configuration window appears. Step 15In the First Node Configuration window, select the applicable option: • Select Yes to configure this server as the publisher server or as a standalone server and continue this procedure. The Network Time Protocol Client Configuration window appears.

• Select No to configure this server as the subscriber server. Step 16In the Network Time Protocol Client Configuration window, enter the hostname or IP address of the NTP server(s) and select OK. The Security Configuration window appears. Configuring Subscriber Server on the Publisher Server To Configure Subscriber server on the publisher server Step 1Sign in to Cisco Unity Connection Administration. Step 2Expand System Settings and select Cluster. Step 3On the Find and List Servers page, select Add New.

Step 4On the New Server Configuration page, in the Hostname or IP Address field, enter the hostname or IP address of the second server in the cluster. Step 5 (Optional) In the MAC Address field, enter the MAC address of the second server.

Step 6In the Description field, enter a description for the second server and select Save. Installing the Subscriber Server To install the subscriber server, follow the steps of installing publisher server until the First Node Configuration window appears and then continue the following procedure. While installing a Unity Connection server, you are prompted to enter different configuration information. Refer the table mentioned in the section wherever applicable. To Install a Subscriber Server Step 1In the Console tab, on the First Node Configuration window, select No to continue the installation of the subscriber server and select OK. The Network Connectivity Test Configuration window displays. Step 2During installation of a subscriber server, the system checks to ensure that the subscriber server can connect to the publisher server.

• To pause the installation after the system successfully verifies network connectivity, select Yes. • To continue the installation, select No.

The First Node Access Configuration window displays. Step 3Enter the connectivity information for the publisher server and select OK. The system checks for network connectivity. If you select to pause the system after the system successfully verifies network connectivity, the Successful Cisco Unity Connection to First Node window displays.

Karaoke Revolution Party Rapidshare Downloader here. Select Continue. Generating Answer File for Unattended Installation You can generate answer files using Cisco Unified Communications Answer File Generator web application. To use the answer file during installation, you need to save the answer file to the root directory of a floppy diskette, browse to the file during installation, and leave the installation to complete. In case of Unity Connection cluster: • You need to generate separate answer files for publisher and subscriber servers. • You are not required to enter details of the publisher server manually on the subscriber server during subscriber server installation. Task List for Unattended Installation You need to perform the following tasks to generate answer file and create floppy image for unattended installation.

1.Generate and download answer files that includes the platformConfig.xml files for both the publisher and the subscriber server. For more information on how to generate answer files, see. 2.After generating the answer files, create a floppy image.

For more information, see. 3.Deploy and configure the servers in the cluster, publisher and subscriber. For more information, see the and section.

4.To install the publisher and subscriber server, see the and section. To Generate and Download Answer Files using AFG Step 1Log in to the Unity Connection Answer File Generator application. The answer file can be generated using the following link:. Step 2Enter details in the Clusterwide Configuration section. Step 3Enter details for the primary node in the Primary Node Configuration section.

Step 4(Optional) If you want to enable Dynamic Cluster Configuration, enter a value in the Dynamic-cluster-config-timer field. Step 5Enter details for the secondary node in the Secondary Node Configuration section.

Step 6In the List of Secondary Nodes list box, select Add Secondary Node. The node that you add as secondary node appears in this list box.

Step 7Click Generate Answer Files. A dialog box appears showing the details for the primary node, the secondary node, and the clusterConfig file. Step 8In the Communications Answer File Generator dialog box, follow the download instructions, and then click the Download File button to download the answer files to your computer. To Configure the Publisher Server on Virtual Machine Step 1Log in to the virtual machine to start the cluster installation. Step 2From the VM menu, choose Edit settings to mount the floppy image that you have created from the Answer File Generator tool. The Virtual Machine Properties dialog box appears. Step 3From the available hardware list, select Floppy drive 1.

Step 4In the Device Type section, select Use the existing floppy image in the database, and then click Browse to navigate to the floppy image. Step 5Click OK. The floppy image is attached. Step 6Select the CD/DVD Drive 1 >Connect to ISO image on local disk option from the toolbar and choose CD/DVD Drive1 >Connect to ISO image on a datastore, navigate to the data store to select the ISO image, and click OK. The ISO image is attached and the installation starts.

Step 7(Optional) If you want to test the media before the installation, click OK in the Disc Found message box, or select Skip to skip testing the media before the installation. The installation proceeds without any manual intervention. The publisher is installed and the subscribers is added to the publisher. Touchless Installation for Virtual Machine Touchless installation is an enhancement of the existing unattended installation, which promotes simplified cluster installation. In unattended installation, you first install Unity Connection on the publisher server using answer file, add the subscriber server to the Cluster page of the publisher server, and then start the installation of subscriber server. However, in Touchless installation, you are not required to manually enter the details of the subscriber server on the publisher server.

The subscriber details are automatically updated through clusterConfig.xml file or dynamic-cluster-configuration option in the AFG tool, which minimizes the need for intervention and scheduling during the deployment of a new cluster. Predefined Cluster Configurations (AFG Process) In this method of installation, the Answer File Generator (AFG) tool generates the clusterConfig.xml file along with the existing platformConfig.xml file for both the publisher and subscriber servers. If you specify the details of the subscriber server in the AFG tool, those details are included in the clusterConfig.xml file. After the publisher server is installed, it reads the clusterConfig.xml file and if the publisher server finds the subscriber server, it adds the subscriber server to its processnode table. Adding the subscriber server to the processnode table eliminates the need to wait for the publisher server to finish its installation, and then manually add the subscriber server on the server page.Thus, the entire installation process occurs automatically. Automatic Sequencing of Touchless Server (dynamic-cluster-configuration) In automatic sequencing feature, subscriber gets configured dynamically along with the publisher during the installation. To use this functionality, enable the dynamic-cluster-configuration option in the AFG tool or use the command line interface (CLI) command on the publisher server.

To use CLI to enable dynamic-configuration functionality, see. There is no clusterconfig.xml file in this process of Touchless install.You need to enable the Dynamic Cluster Config Timer (1-24 hours) and start the installation on both the servers at the same time. The number of hours is the duration for which subscriber waits for publisher to receive the subscriber entry in the processnode table.

You can access the upgrade file during the installation process either from a local disk (DVD) or from a remote FTP or SFTP server. To Apply a Patch Step 1If you select Yes in the Apply a Patch window, the Install Upgrade Retrieval Mechanism Configuration window appears. Step 2Select the upgrade retrieval mechanism to use to retrieve the upgrade file: • SFTP —Retrieves the upgrade file from a remote server using the Secure File Transfer Protocol (SFTP). Skip to the section. • FTP —Retrieves the upgrade file from a remote server using File Transfer Protocol (FTP). Skip to the section. • LOCAL —Retrieves the upgrade file from a local DVD.

Continue with the section. Upgrading from a Remote Server Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified version of Cisco Unified Communications Manager. For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to. Cisco uses the following servers for internal testing. You may use one of these servers, but you must contact the vendor for support: • Open SSH (for Unix systems. Refer to ) • Cygwin ( ) • Titan ( ).

• To enable automatic negotiation, select Yes. The MTU Configuration window displays. Continue with. • To disable automatic negotiation, select No.

The NIC Speed and Duplex Configuration window displays. Continue with. Step 3If you choose to disable automatic negotiation, manually select the appropriate NIC speed and duplex settings now and select OK to continue. The MTU Configuration window displays. Step 4In the MTU Configuration window, you can change the MTU size from the operating system default. The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value.

• To accept the default value (1500 bytes), select No. • To change the MTU size from the operating system default, select Yes, enter the new MTU size, and select OK. The DHCP Configuration window displays. Step 5For network configuration, you can choose to either set up static network IP addresses for the Unity Connection server and gateway or to use Dynamic Host Configuration Protocol (DHCP). Static IP addresses are recommended. • If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes.

The installation process attempts to verify network connectivity. • If you want to configure static IP addresses for the server, choose No. The Static Network Configuration window displays. Step 6If you choose not to use DHCP, enter your static network configuration values and select OK. The DNS Client Configuration window displays.

Step 7To enable DNS, select Yes, enter the DNS client information and select OK. After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays. Step 8Enter the location and login information for the remote file server. The system connects to the remote server and retrieves a list of available upgrade patches. If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path.

For example, if the upgrade file is in the patches directory, you must enter /patches If the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax, including: • Begin the path with a forward slash (/) and use forward slashes throughout the path. • The path must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows absolute path that starts with a drive letter (for example, C:). The Install Upgrade Patch Selection window displays.

Step 9Select the upgrade patch to install. The system downloads, unpacks, and installs the patch and then restarts the system with the upgraded software version running. After the system restarts, the Pre-existing Configuration Information window displays. Step 10To continue the installation, select Proceed. The Platform Installation Wizard window displays. Step 11To continue the installation, select Proceed or select Cancel to stop the installation. If you select Proceed, the Apply Patch window displays.

Continue with. If you select Cancel, the system halts, and you can safely power down the server.

Step 12When the Apply Patch window displays, select No, the “Basic Install” window appears. Step 13Select Continue in the window to install the software version on the DVD or configure the pre- installed software and move to of the section. Upgrading from a Local Disk Before you can upgrade from a local disk, you must download the appropriate patch file from Cisco.com and use it to create an upgrade DVD.

You must create an ISO image on the DVD from the upgrade file. Just copying the ISO file to a DVD will not work. To Upgrade from a Local Disk When Applying a Patch Step 1When the Local Patch Configuration window displays, enter the patch directory and patch name, if required, and select OK.

The Install Upgrade Patch Selection Validation window displays. Step 2The window displays the patch file that is available on the DVD. To update the system with this patch, select Continue. Step 3Select the upgrade patch to install.

The system installs the patch, then restarts the system with the upgraded software version running. After the system restarts, the Preexisting Configuration Information window displays. Step 4To continue the installation, select Proceed. The Platform Installation Wizard window displays. Step 5To continue the installation, select Proceed or select Cancel to stop the installation. If you select Proceed, the Apply Patch window displays.

Continue with. If you select Cancel, the system halts, and you can safely power down the server. Step 6When the Apply Patch window displays, select No, the “Basic Install” window appears. Step 7Select Continue in the window to install the software version on the DVD or configure the pre- installed software and move to of the section. Verifying the Installation After the installation application has finished, the new server displays its hostname and the administration account login prompt. To Verify the Installation Step 1Log in with the administration account user name and password. The server opens a command line interface.

Step 2Verify that server network services are running: a.At the CLI prompt, enter the command utils service list. It might take a few minutes for all services to start completely. During this time, you might notice that services might be listed as [Starting]. B.Repeat the utils service list command until all network services are listed as [Started].

In particular, the Cisco Tomcat service must be started before you can proceed to the next verification step. Step 3Verify the server details: a.Open a web browser on a personal computer that has network access to the server. Unity Connection supports different web browsers, such as Microsoft Internet Explorer and Mozilla Firefox. B.In the web browser, enter the URL “ /cmplatform”. C.Login to Cisco Unified OS Administration using the administrator user name and password specified during the installation.

D.Select Show >System from the toolbar to display the system status page, showing the current date, uptime, software level, along with the CPU and memory usage. E.Use the Show menu to check: – Cluster: displays the IP address, hostname, alias, server type, and database replication status of the single server or both the server in case of cluster. – Hardware: platform type, serial number, hardware, and other options – Network: current network interface configuration, status, and packets – Software: current active and inactive software partitions Step 4Verify the server status: a.In the web browser, enter the URL “ /cuadmin”. B.The Cisco Unity Connection Administration window opens. Select Cisco Unity Connection Serviceability from the navigation pane. Login using the application user name and password specified during the installation.

C.Select Tools >Cluster Management. It lists the server status of either single server or both the servers in case of cluster. For a standalone server deployment, the server shows Primary status whereas in case of cluster, one of the server shows Primary status and the other shows Secondary status.

Post-Installation Tasks After installing Unity Connection on your server, you should perform the following additional tasks before configuring the system for your application: • Obtain the licenses for the Unity Connection server. For more information, see the chapter. • (Optional) Change the application passwords. You can change the passwords using either the Cisco Unity Connection Administration web application, or you can log into the server and run the CLI command utils cuc reset password • If you require additional languages, install them.

For details, see the section. • Install the Cisco Unified Real-Time Monitoring Tool. You can use Cisco Unified Real-Time Monitoring Tool to monitor system health, and view and collect logs. For more information on RTMT, see the Cisco Unified Real-Time Monitoring Tool Administration Guide Release 10.x. (Optional): You can configure RTMT to send alert notifications through emails to the specified email address. For more information on enabling email alert, see the “ section of the Cisco Unified Real-Time Monitoring Tool Administration Guide.

• Activate Unity Connection feature services. For service activation requirements, see the Cisco Unified Serviceability Administration Guide Release 10.x.

• Configure the backup settings. For more information, see the chapter.

Frequently used acronyms • API: Application programming interface • IT: Information technology Alas, UNIX isn't the only tongue spoken in the machine room. IBM® mainframe folks speak cants of 'z,' such as IBM z/OS® and System z9 Virtual Machine (z/VM); harried embedded systems developers jabber in eCos; and still others chit-chat in various argots of UNIX, such as Linux®, FreeBSD, Sun Solaris, and Mac OS X. Modern information technology is a latter-day Babel. Of course, a great many also speak the Windows vernacular, although most are versed only in Windows' point-and-click patois. After some 20-odd years of revisions, the predominance of Windows users have forgotten the arcane DOS dialect. Indeed, compared to a UNIX shell, the Windows COMMAND utility is woefully underpowered; hence, UNIX users typically find Windows a frustrating platform. Moreover, Windows can be especially vexing for UNIX software developers accustomed to an expansive and rich set of command-line tools.

To UNIX developers, using Windows is akin to visiting a strange and foreign land. My Flash Recovery Serial Key. Luckily, Cygwin (see ) provides a familiar destination within Windows, like finding a McDonald's in France. (Royale with cheese, anyone?) Cygwin is a UNIX-like shell environment for Windows. It consists of two components: a UNIX API library to emulate many of the features that the UNIX operating system provides, and adaptations of the Bash shell and a plethora of UNIX utilities to provide the familiar UNIX command-line interface. The former component is provided as a Windows Dynamic Link Library (DLL).

The latter component is a collection of individual programs —many built from source code unchanged from UNIX—based on the Cygwin DLL. Combined, the two give you all the comforts of your UNIX home directory, sweet home. In this month's column, you install Cygwin, explore its command-line interface (CLI), and build open source software not included in the standard Cygwin distribution to experience how easy it is to port (at least some) UNIX applications to the emulation environment. Version details As of this writing, the current version of the Cygwin DLL is 1.5.25-15. You can install Cygwin on any recent, commercial version of Windows except for Windows CE. (However, support for Windows 95, Windows 98, and Windows ME will be obsolesced in an upcoming release of Cygwin.) The examples and figures shown in this article are based on Windows XP Professional with Service Pack 3 (SP3) running under Parallels version 3.0 on an Apple MacBook in Coherence mode. Installing Cygwin Unlike other software presented here, Cygwin uses the Windows Installer.

The Cygwin setup.exe file installs the software anew and is re-used any time you want to add, change, or upgrade components of your Cygwin configuration. Open a browser on your Windows system, and point to to download the Cygwin installer. The installer itself is very small (about 600KB), because the bulk of the Cygwin software is subsequently downloaded during the setup process. After your download succeeds, perform the following steps to install Cygwin: • Run the Setup program. Figure 1 shows the Cygwin welcome screen. The first of many dialog boxes presented during Cygwin setup.

In most cases, the recommended installation options are suitable, but you can customize with a few caveats: • Do not install Cygwin in the root directory of your Windows system, such as C: It's best to install Cygwin in its own subdirectory, such as the default—C: cygwin—or perhaps C: Program Files cygwin. (The target directory, whatever you choose, becomes the root directory—the /—of your emulated UNIX environment. For example, if you install to C: cygwin, the virtual /usr/bin can actually be found in C: cygwin usr bin.) • Do not choose Just Me for the Install For option. • Set the Default Text File type to Unix to maximize compatibility with existing files and files stored on other UNIX machines. • Click Next. In the window that appears, choose a directory in which to store the data Cygwin requires. Do not choose the Cygwin directory you selected in the previous step.

If possible, create or choose a directory on a drive with at least 1GB of free space. • Click Next again, and choose the type of Internet connection you use.

Direct Connection is typically apropos. • Click Next again. In a moment, Cygwin downloads its list of current mirror sites and prompts you to choose one, as shown in Figure 3. When in doubt, choose a site within close proximity. Choose the installation site you feel is reliable or is in close proximity. After a brief delay, the installer displays a complete list of available categories and packages.

Shows a partial catalog. Click on a plus sign ( +) to expand the corresponding category; click a 'loop' to cycle between Skip (which omits the package) and all available versions of the respective package. If Cygwin provides multiple versions of a utility, pick the instance that meets your requirements. By the way, the B column, if selected, downloads the binary package; if the S is selected, the source is downloaded, too. Choose the packages and instances that best suit your needs. More than 1,000 packages are available within Cygwin, so choose only the categories and packages you need. (Installing all of the Cygwin bundles takes up more than 800MB of disk space.) After all, you can always add an entire category or a single package in the future: Simply re-run the Cygwin installer.

(You can also remove or update a package at any time with the same installer.) To quickly determine whether your favorite UNIX utility is available within Cygwin, search the Cygwin package list (see ). • When you've chosen the tools you want, click Next, and the download process begins! The status bars reflect each package download, overall download headway, and disk usage, respectively.

Figure 5 is a snapshot taken during installation on my test machine. Cygwin downloads a great deal of software, so be patient. Finally, the Setup application installs the software and (optionally) adds shortcuts to your Start menu and desktop. Click Finish. • Launch Cygwin by using the Start menu or by double-clicking the Cygwin icon (if you installed those shortcuts), or you can execute the Cygwin script found in your Cygwin directory (such as C: cygwin Cygwin.bat).

Figure 6 shows Cygwin as it starts the first time: It creates your home directory, seeds shell startup files, and presents the prompt. You can now run UNIX commands! Now you can use UNIX commands in Windows! For example, try ls -a or type touch. The latter command indicates that touch is the executable /usr/bin/touch. The best of UNIX in Windows (and vice versa) Cygwin is a near-complete emulation of the UNIX shell within Windows. In fact, it marries the two operating systems quite nicely.

For example, run the command df -h to display an inventory of free disk space on your 'UNIX' machine. Figure 7 shows the result. Is that a UNIX file system on Windows or a Windows file system on UNIX? As, the Cygwin installation directory acts as the root directory of your virtual UNIX system. Cygwin simply maps subdirectories in its installation directory to familiar UNIX equivalents. It also provides the Windows drives as individual volumes, such as /cygwin/c.

You can use such a virtual path to launch Windows programs. Try it: Type /cygwin/c/Program Files/Internet Explorer/IEXPLORE.EXE to launch Windows Internet Explorer® from the command line. (You can also use the Tab key to automatically expand elements of the path.) By the way, if you want to convert a Windows path name to its UNIX equivalent or vice versa, try the built-in command cygpath. By default, cygpath produces the UNIX path name. Use the -w option to produce a Windows path.

$ cygpath -w /cygwin/c/Program Files/Internet Explorer/IEXPLORE.EXE c: Program Files Internet Explorer IEXPLORE.EXE Other niceties provide helpful bridges between the two environments: • Cygwin provides its own lpr (/usr/bin/lpr rather than Windows' own LPR.EXE) to print from the UNIX emulation directly. Simply set the PRINTER environment variable to a Cygwin UNC such as server printer_name or //server/printer_name—either slash direction works, as in all other parts of Cygwin. • Symbolic links created with ln -s in Cygwin are interpreted as shortcuts in Windows. Reflexively, Windows shortcuts are interpreted as symbolic links. Further, you can use a Windows shortcut to launch a UNIX command with parameters. • And because you have a full Bash shell at your disposal, you can use all the aforementioned compatibility features (among others) to write UNIX shell scripts to maintain Windows! For example, you can use UNIX find to hunt for data on your drives.

Here's a tip: it's common to use spaces in a Windows file name. To preserve an entire file name (remember, UNIX arguments are separated by white space), be sure to use find -print0 and its companion, xargs -0. How to update and extend your Cygwin As mentioned at the onset, you can add, remove, and update Cygwin categories and packages at any time by (re-)running the Cygwin installer.

Let's add a few software development packages to prepare for building additional code from source, as you typically do on a traditional UNIX system. Run the Cygwin setup.exe application again, and march through the initial dialogs until you return to the Select Packages window, shown in.

Expand the Devel category, and use the recycle control to select the highest-numbered versions of the following: • autoconf2.1 • automake1.10 • binutils • gcc-core • gcc4-core • gdb • pcre • pcre-devel After making all selections (which may automatically choose additional packages to satisfy dependencies), click Next to start the update. As before, the download and installation process may take some time—the development packages tend to be quite large. In the meantime, open a browser window and point to to download the latest source code of the GNU wget utility. (If you haven't used it before, wget is a command-line tool to download virtually anything. For more information about this tool, see ) Using Cygwin, copy the file to your home directory in Cygwin, and expand the tarball. Listing 1 shows the contents of the tarball. Contents of wget-1.11.4.tar $ cp /cygdrive/c/Documents and Settings/Martin/My Documents/wget-1.11.4.tar ~ $ tar xzvf wget-11.4.tar wget-1.11.4/ wget-1.11.4/AUTHORS wget-1.11.4/NEWS wget-1.11.4/COPYING wget-1.11.4/configure.bat wget-1.11.4/ChangeLog wget-1.11.4/ChangeLog.README wget-1.11.4/msdos/ wget-1.11.4/msdos/ChangeLog wget-1.11.4/msdos/Makefile.DJ.

Wget-1.11.4/src/cookies.c wget-1.11.4/src/http.h wget-1.11.4/src/log.h wget-1.11.4/src/sysdep.h wget-1.11.4/src/alloca.c wget-1.11.4/src/getopt.c wget-1.11.4/src/gnu-md5.h wget-1.11.4/src/ftp.c wget-1.11.4/config.sub wget-1.11.4/config.guess $ When the Cygwin download and installation process finishes, click Finish. You should now be ready to build the wget utility from source.

$ cd wget-1.11.4 $./configure configure: Configuring for GNU wget 1.11.4. Creating po/Makefile $ make gcc -I.

$ make install. /usr/bin/install -c -m 644./wget.1 /usr/local/share/man/man1/wget.1 $ type wget /usr/local/bin/wget To test the new utility, run it within Cygwin and the download the wget source code: $ /usr/local/bin/wget In a moment, you should have a new source tarball.

It's easiest to pull utilities from the Cygwin repository using the Cygwin installer, but you can build source you download—or your own source code—within Cygwin. The full suite of UNIX development tools, including the most popular scripting languages, are available within Cygwin. You can even build native Windows WIN32 applications with the UNIX compilers and tools found in Cygwin if you don't have something like Microsoft Visual Studio®. (These applications will not run on UNIX. To build a Windows application to run on UNIX, consider WINE.

See for more information.) Familiar, powerful, and useful Cygwin isn't a perfect emulation of UNIX, but it's a comforting surrogate. The documentation for the core components is good and especially forthcoming, describing limitations in the emulation DLL and security risks. If you want to port a complex UNIX package to Cygwin, consult the Developer's Guide (see ) to measure Cygwin's support for your API needs. Perhaps the best feature of Cygwin is its integration with Windows. To boost productivity, drop to Cygwin and use its UNIX-like command line to manipulate the system. One suggestion: Extend your shell PATH variable to include subdirectories in Windows' Program Files to launch any binary in your path by simply typing its name. Better yet, Cygwin can manage multiple jobs in the same window.

Press Control-Z to suspend a running job; type bg and fg to run a job in the background and foreground, respectively; and type jobs to manage the list of jobs. Of course, Cygwin also redirects input and output and pipes output from one command to another. Cygwin: It's better than a Royale with cheese.