cisco interactive experience manager installation guide v2€¦ · cisco interactive experience...

Cisco Interactive Experience ManagerInstallation GuideRelease 2.0April 6, 2013

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-26459-03

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.

Modifications to this product not authorized by Cisco could void the FCC approval and negate your authority to operate the product.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco Interactive Experience Manager Installation Guide© 2013 Cisco Systems, Inc. All rights reserved.

C O N T E N T S

C H A P T E R 1 Introduction

C H A P T E R 2 Installing the IEM Software

C H A P T E R 3 Configuring the IEM Software

C H A P T E R 4 Using the IEM Configuration Menu

C H A P T E R 5 Upgrading the IEM Software

A P P E N D I X A High Availability Installation and Configuration

iiiCisco Interactive Experience Manager Installation Guide

Cisco

C H A P T E R 1
Introduction
Revised: April 6, 2013, OL-26459-03

Chapter OverviewThe Cisco Interactive Experience Manager is software that allows for centralized management of Cisco Interactive Experience Client 4600 Series devices.

This chapter explains the audience and scope of this installation guide and provides an overview of the Cisco Interactive Experience Manager.

The sections in this chapter are:

• What’s New about the IEM in This Release, page 1-2

– Non-Administrator User Role, page 1-2

– Effective Profile, page 1-2

– High Availability, page 1-2

– IEM Configuration Menu, page 1-3

– User Lockout after Failed Login Attempts, page 1-3

– Licenses for IEM Management, page 1-3

– Other Changes in 2.0, page 1-3

• About This Installation Guide, page 1-4

– Terminology, page 1-4

– Audience, page 1-4

– Scope, page 1-5

• Cisco Interactive Services Solution, page 1-5

– Cisco Interactive Experience Client 4600 Series, page 1-6

– Cisco Interactive Experience Manager, page 1-6

– Principles of Operation, page 1-7

1-1 Interactive Experience Manager Installation Guide

Chapter 1 Introduction What’s New about the IEM in This Release

What’s New about the IEM in This ReleaseRelease 2.0 includes the following new features for the Cisco Interactive Manager (IEM):

• Non-Administrator User Role

• Effective Profile

• High Availability

• IEM Configuration Menu

• User Lockout after Failed Login Attempts

• Licenses for IEM Management

• Numerous performance upgrades and enhancements

Non-Administrator User RoleUsers by default are granted administrator-level access and permissions. This level of access can be removed for users that only need to view and monitor devices.

Non-administrator users can do the following:

access to the following tabs within the Device screen:

• View a device’s status, events. performance, and effective profile

• Use the predefined action buttons for devices including Reboot and Message

• Use any custom action buttons that have been created for devices

Effective ProfileThe Effective Profile tab for devices provides a time line of configuration changes to the IEC based on the scheduling of policies. With this feature, the administrator can see a cumulative view of the configuration changes applied to a device and understand where the configuration is originating. The cumulative changes on that device can come from the device profile, policies applied to the device, and the group to which the device belongs.

High AvailabilityThe IEM supports High Availability (HA) configured on VMware vSphere. HA must first be configured on vSphere before installing the IEM software on the virtual machine. Refer to the Cisco Interactive Experience Manager Installation Guide for more information.

The IEM also supports a Bare Metal HA setup.

Load BalancingLoad balancing is supported for the Bare Metal HA setup.

1-2Cisco Interactive Experience Manager Installation Guide

Chapter 1 Introduction What’s New about the IEM in This Release

IEM Configuration Menu The IEM Configuration Menu is accessed using a SSH client. The menu allows administrators to configure server settings, manage the server, troubleshoot, and enable the Cisco TAC to access the server.

User Lockout after Failed Login AttemptsThe administrator can now configure the number of times that a user can try logging into the IEM and fail. When the number of failed attempts has been reached, the user is locked out of the IEM for a time period that is also configured by the administrator.

Licenses for IEM ManagementEach Cisco Interactive Experience Client Series 4600 (IEC 4600) device requires a license in order for it to be managed on a Cisco Interactive Experience Manager (IEM). The IEM license bundles that you purchase support up to 10, 50, 100, 500, or 1,000 IEC 4600 devices. When ordering a license bundle, ensure that you have ordered enough licenses to cover all the IEC 4600 devices that will be managed by the IEM. You will add the licenses to the IEM before you register IECs. If the number of registered devices is exceeded, no additional devices can be registered in the IEM and managed by it.

Other Changes in 2.0The following are other changes in 2.0:

• Additional platforms and browsers are now supported by the IEM. Only use supported platforms and browser versions for full functionality. The supported platforms are Windows XP (32bit or 64bit), Windows 7 (32bit or 64bit), and Macintosh OS 10.6.8. The supported browser versions are Internet Explorer 8 and 9 (32bit and 64bit), Chrome, Safari, and Firefox 12 and higher.

• The IEM software no longer comes pre-installed on a Cisco UCS server. The 2.0 software is instead downloaded and installed on bare metal or a virtual machine. It is recommended that you install the IEM version 2.0 software on a VMware vSphere client.

• Revamped hotkey property within profiles and policies: All the previous hotkeys for the IEC were removed except for the hotkey used to access the System Settings menu on the IEC. The utilities previously accessed using hotkeys can be accessed using the System Settings menu. Those utilities are enabled or disabled in the settings property of the profile or policy.

• The email field in the Server Settings screen has been changed from the sender’s email to the administrator’s email. The email address entered will be used as the sender’s address when the system sends out notifications. It will also receive system alerts.

• Policy and profile hierarchy: If a policy is applied to a device, it takes precedence over the device’s profile. A policy applied to a device takes precedence over a policy applied to a group. The figure below illustrates the hierarchy for settings.


Chapter 1 Introduction About This Installation Guide

Figure 1-1 Settings Hierarchy

About This Installation GuideThis section describes the audience and scope of this installation guide.

TerminologyThe following terms are used in this user guide.

• Accounts - Allow multiple organizations to configure and manage devices and policies in a single Cisco Interactive Experience Manager instance. Use accounts to segregate users, devices, and policies. Each organization will have at least one account.

• Administrators - People who have access to all accounts on the system. This Cisco Interactive Experience Manager Installation Guide provides administrators with all the information necessary to install and administer a Cisco Interactive Experience Manager.

• Device - Cisco Interactive Experience Client 4600 Series

• Policies- An easy and flexible way of applying settings to multiple devices or users.

• Profiles - The settings of a single device or user.

• Users - People who configure and manage the Cisco Interactive Experience Manager. Users are associated with specific accounts on the Cisco Interactive Experience Manager. The Cisco Interactive Experience Manager User Guide was developed for users.

Audience

The intended audience for this guide is administrators. They will install, manage, and upgrade the Cisco Interactive Experience hardware and software.


Chapter 1 Introduction Cisco Interactive Services Solution

ScopeThis installation guide explains how to install the Cisco Interactive Experience Manager software. There is also a troubleshooting chapter so that the administrator can handle simple installation issues.

This user guide provides instructions so that an administrator can:

• Set up the Interactive Experience Manager

• Enable supported products

• Create and delete administrators

• Upgrade product version

• Add new products and models

After the Cisco Interactive Experience Manager has been installed, refer to the Cisco Interactive Experience Manager User Guide for instructions on how to use it to configure and manage Cisco Interactive Experience Client 4600 Series.

Cisco Interactive Services SolutionThe Cisco Interactive Services Solution leverages the network as the platform to transform customer experience with interactive digital media. Leveraging Cisco’s video, collaboration, and cloud architectures, the solution allows large and small enterprises and public agencies to seamlessly provide the most updated product or service information including educational content in real-time, improving customer experience and increasing customer retention. With built-in remote management capabilities, the solution enables organizations to get feedback instantaneously from end users to measure marketing effectiveness and impact as well as dynamically provision and disperse relevant content. Effective reuse of web content and applications along with remote delivery of content and advertisements helps increase advertising revenues, improve business and customer processes, through effective management of digital displays and open online spaces.

The Cisco Interactive Services Solution is the collective name for a product family that consists of thin clients hardware and software known as the Cisco Interactive Experience Client 4600 Series and remote management software which is called the Cisco Interactive Experience Manager.



Figure 1-2 Cisco Interactive Services Solution

Cisco Interactive Experience Client 4600 Series The Cisco Interactive Experience Client 4600 Series (IEC4600 Series) is a robust, configurable, and manageable web device designed for public venues and web-centric delivery. The devices can be controlled remotely using management software, the Cisco Interactive Experience Manager (IEM).

It is highly recommended that all the Cisco IEC4600 Series devices are managed and monitored using the Cisco Interactive Experience Manager as it ensures consistent remote management, with the option to configure the devices locally.

Cisco Interactive Experience ManagerThe Cisco Interactive Experience Manager (IEM) is the management software that allows the administrator to control and monitor Cisco IEC4600 Series devices. The Cisco IEC4600 Series devices are configured remotely through a combination of device, user, profile, and policy settings from the Cisco IEM,

Configuration settings are distributed between user and device settings; however profiles contain all the settings available to both device and users. Policies represent dynamic and transportable setup rules.



Cisco IEM is a solution allowing configuration, control, and support of Cisco Interactive Experience Client 4600 Series devices. With Cisco IEM, an administrator can perform the following functions:

• Configuration - Cisco IEM allows the administrator to configure the Cisco IEC4600 Series devices. IEC4600 Series devices can be configured to start with a predetermined Internet resource, such as a web page, flash, or movie, and then let the user navigate within a “walled garden” environment.

• Policy Management- Policies provide an easy and flexible way for administrators to apply settings to a group of users or devices.

• Session Management - An administrator can apply a session time limit to IEC4600 Series devices.

• Remote Control - Administrators can control the behavior of the IEC4600 Series devices in real-time including muting a station, locking out the user, or sending the user a message.

• Remote Assistance - To ask for help, users can simply press a help button on the screen to initiate a chat session with a virtual attendant or remote agent.

• Logs - Cisco IEM can be set up to log the traffic from the Cisco IEC4600 Series devices, making it easy for the administrators to analyze the data.

Principles of OperationThe following are principles of operation for this solution:

1. IEC4600 Series devices need to exist on the IEM in order to be managed by it. IEC4600 Series devices can either be provisioned ahead of time or from the device interactively. If registered from the device interactively, the installer has to use their account info to authorize the registration.

2. Policy applied to a device overrides its profile. Policies are templates for property settings.

3. Multiple policies can be attached to the same device (group). If policies contain conflicting settings, the policy that is higher in the stack order takes precedence. Device policies take precedence over group policies.

4. IEC4600 Series and IEM versions are best-effort compatible. A device that has a version that is not actively supported by the IEM will still be supported although some things may not have full functionality. A device version which is out of sync is indicated by the red FW flag. Communication between client and the IEM is defined by the communication protocol and specification that defines capabilities of each FW build. Older communication protocols are supported in the newer builds, but older specifications that reflect properties of the firmware are often not fully compatible with the later versions.

5. Policies can be persistent or transient (applied for short periods of time). Persistent policies are long-term or permanent. Persistent policies are applied when the IEC4600 Series device is booted or rebooted. Persistent policies are permanent until they are unapplied.

Transient, runtime, or IsAction policies are created by checking the IsAction check box when creating the policy or in the General tab of the policy. Transient policies are marked by a blue circle with a white arrow and are made available in form of a button under “Custom Actions”. These policies change the settings on the IEC4600 Series temporarily and will be reset by changing the settings within the policy, by applying counter action policy, or on the next reboot. IsAction policies can only work for runtime properties, which are marked by an orange arrow in the policy or profile.

6. Notifications and alerts work on a subscription basis. Once notification/alert has been created, it has to be assigned to a user. Notification/alert can submit to a third party application collecting the data – the URL has to be provisioned through User profile.


Chapter 1 Introduction

7. In order to optimize screen behavior, the application has to implement native components. Native components are available in form of a Browser API (refer to the documentation) and essentially move resource-intensive or asynchronously used components outside of the browser process-space.


Cisco

C H A P T E R 2
Installing the IEM Software

Chapter OverviewThis chapter explains how to install the IEM software on a virtual machine or bare metal.


• What You Will Need, page 2-1

– Physical Server Specifications, page 2-2

– Virtual CPUs, page 2-2

• Gather the IEM Software Files, page 2-3

• Install IEM Software on a Virtual Machine, page 2-4

– Configure High Availability in vSphere (Optional), page 2-4

– Launch VMware vSphere Client, page 2-4

– Create a Virtual Machine and Deploy the OVA File, page 2-7

– Upload and Deploy ISO File, page 2-19

– Install ISO and Boot Up, page 2-23

– Verify High Availability of the IEM’s VM, page 2-26

• Install IEM Software on Bare Metal - Method #1, page 2-28

– Configure CIMC on a UCS Server, page 2-28

– Launch CIMC KVM Console on the UCS Server, page 2-30

– Configure Hard Disks with LSI MegaRAID Configuration Utility, page 2-31

– Install IEM on CIMC KVM Console, page 2-37

• Install IEM Software on Bare Metal - Method #2, page 2-40

What You Will NeedTo install and configure the Cisco IEM, you will need the following:


Chapter 2 Installing the IEM Software What You Will Need

• IEM software files downloaded from www.cisco.com:

1. IEM-VM ISO file

2. IEM OVA file

• IEM license

• IP address of host server

• Network credentials

• Server running VMware vSphere version 4.1 (all editions) or later:

– If you are installing the software on a physical server, you will need a Cisco UCS server (see the physical server specifications in the next section).

– If you are installing the software on a virtual machine, you will need a server (Cisco or third-party).

• If High Availability is required:

– Minimum of two ESX/ESXi hosts

– Cluster setup

– vSphere HA configured and enabled on the server

Physical Server Specifications

Table 2-1 Physical Server Specifications

Note Always use 16GB RAM and 100GB HDD.

Virtual CPUs

Table 2-2 vCPU Recommendations

Model UCSC-C220-M35

CPU Cores 16 CPUs x 2.9 GHz

Processor Type Intel Xeon CPU E5-2690 @ 2.90 GHz

Processor Sockets 2

Cores per Socket 8

Logical Processors 32

Hyperthreading Active

Number of IECs Recommended Number of vCPUs

100 2

300 4


Chapter 2 Installing the IEM Software Gather the IEM Software Files

Note The default setting of vCPUs in the IEM OVA file is 12 vCPUs, which supports up to 1000 IECs.

Gather the IEM Software FilesThe IEM-VM ISO and IEM OVA files are available for download. Follow the steps below to download them.

Step 1 Enter the following URL in your web browser: http://www.cisco.com/en/US/partner/products/ps12434/tsd_products_support_general_information.html

Step 2 Log in using your partner or customer credentials.

Step 3 Within the Support area, click Download Software.

Figure 2-1 IEM Software Downloads, Release and General Information Page

Step 4 Under Release 2.0, select the IEM OVA file.

Step 5 Click the Download button.

Step 6 Select the IEM ISO file.

500 6

700 10

1000 12

Number of IECs Recommended Number of vCPUs


Chapter 2 Installing the IEM Software Install IEM Software on a Virtual Machine


Install IEM Software on a Virtual MachineFollow the instructions below to install the IEM software on a virtual machine (VM).

Configure High Availability in vSphere (Optional)The IEM supports High Availability (HA) configured on vSphere. Refer to the Cisco Interactive Experience Manager High Availability Installation and Configuration Guide for instructions on how to install additional components and update configurations.

If you wish to have HA on the IEM VM, make sure that you have configured HA on vSphere before installing the IEM software. vSphere HA provides the infrastructure to protect all workloads with the infrastructure. You do not need to install special software within the application or virtual machine. All workloads are protected by vSphere HA. After vSphere HA is configured, no actions are required to protect new virtual machines; they are automatically protected.

vSphere HA provides high availability for virtual machines by pooling the virtual machines and the hosts they reside on into a cluster. Hosts in the cluster are monitored and in the event of a failure, the virtual machines on a failed host are restarted on alternate hosts. vSphere HA leverages multiple ESXi hosts configured as a cluster to provide rapid recovery from outages and cost-effective high availability for applications running in virtual machines. vSphere HA protects application availability in two ways. First, it protects against a server failure by restarting the virtual machines on other hosts within the cluster. Second, it protects against application failure by continuously monitoring a virtual machine and resetting it in the event that a failure is detected.

Refer to the vSphere Availability documentation for how to set up, configure, and enable vSphere HA. The documentation for your vSphere version and edition can be found at: http://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html

Launch VMware vSphere Client

Step 1 Launch your VMware vSphere client.

Step 2 In the IP address / Name field, enter the IP address of the ESX host server that will be hosting the IEM virtual machine.



Figure 2-2 vSphere Client Login

Step 3 In the User name field, enter the username of the ESX host server.

Step 4 In the Password field, enter the password of the ESX host server.

Step 5 Click Login.

Step 6 When prompted with a security warning pop-up about Certificate Warnings, click Ignore.

Figure 2-3 Security Warning Dialog Box

Step 7 A Warning window appears. Click OK.



Figure 2-4 vCenter Server Warning Dialog Box

Step 8 Click on the IP address of the ESX host server in the left window pane and then click on the Summary tab in the right window pane.



Figure 2-5 Summary Tab

Create a Virtual Machine and Deploy the OVA FileThe IEM OVA file contains all the VM settings that you need so you do not need to configure or modify any VM settings when you are creating the VM for the IEM.

Note If you have configured vSphere HA, you will create a VM for IEM in the vSphere Client in the vCenter. If you have not configured vSphere HA, you will create a VM for IEM in the ESX/ESXi host.

Step 1 In vSphere, choose Deploy OVF Template option under File.



Figure 2-6 Deploy OVF Template Option

The Deploy OVF Template dialog box opens.

Figure 2-7 Deploy OVF Template Dialog Box

Step 2 Click Browse.

Step 3 In the Open dialog box, go to the location where the IEM OVA file is located and choose it.



Figure 2-8 Open Dialog Box

Step 4 Click Open.

Step 5 The path to the OVA file appears in the Source screen.



Figure 2-9 Source Screen

Step 6 Click Next.

Step 7 The Details screen displays the details of the OVA file including the product, release number, download size, and size on disk. Click Next.



Figure 2-10 Details Screen

Step 8 The Name and Location screen appears. By default, the template name appears as “Interactive Experience Manager”. It is recommended that you keep the default template name so it is easy to identify later. Click Next.



Figure 2-11 Name and Location Screen

Step 9 (Optional) Choose a resource pool if you have set up a hierarchy of resources and then click Next.



Figure 2-12 Resource Pool Screen

Step 10 In the Storage screen, choose a datastore and then click Next.

Note In a non-HA environment, you will have only one datastore available.



Figure 2-13 Storage Screen

Step 11 In the Disk Format screen, do not modify any of the settings. Click Next.



Figure 2-14 Disk Format Screen

Step 12 In the Network Mapping screen, choose the destination network that your VM will run on and then click Next.



Figure 2-15 Network Mapping Screen

Step 13 In the Ready to Complete screen, click Finish.

Note Be sure to leave the “Power on after deployment” checkbox unchecked.



Figure 2-16 Ready to Complete Screen

The Deploy OVF Template dialog box will close and the Deploying Interactive Experience Manager dialog box will appear.

Figure 2-17 Deploying Interactive Experience Manager Dialog Box

Step 14 When the deployment is complete and the new VM is created, you will see the message “Completed Successfully” in the Deployment Completed Successfully pop up dialog box. Click Close.

Figure 2-18 Deployment Completed Successfully Dialog Box



Step 15 Click the Virtual Machine tab to view the newly created VM.

Figure 2-19 Interactive Experience Manager VM

Step 16 In the left pane, choose Interactive Experience Manager.

Figure 2-20 Interactive Experience Manager VM

Step 17 Click the Summary tab to view details about the IEM’s VM.

Figure 2-21 Summary Tab

Note Your details may be different from those shown in the graphic above.



Upload and Deploy ISO FileNow you upload and deploy the ISO file.

Step 1 In the Summary tab of the IEM’s VM, right-click datastore in the Resources area.

Figure 2-22 Datastore in Resources Area of Summary Tab

Step 2 Choose Browse Datastore.

Figure 2-23 Browse Datastore Option

Step 3 In the Datastore Browser dialog box, click the Upload files to this datastore button, which is the fourth button from the left.



Figure 2-24 Datastore Browser Dialog Box

Step 4 Choose Upload File.

Figure 2-25 Upload File Option

Step 5 In the Upload Items dialog box, find the IEM-VM ISO file and select it.



Figure 2-26 Upload Items Dialog Box

Step 6 Click Open.

The IEM-VM ISO file is uploaded from your disk to the virtual disk.

Figure 2-27 ISO File Uploading Status Box

Step 7 When the upload is complete, the ISO file appears in the Datastore Browser dialog box.



Figure 2-28 Uploaded ISO File

Step 8 Close the Datastore Browser dialog box by clicking the X in the upper right corner of the box.

Step 9 In the Summary tab, go to the Commands section and click Edit Settings.

Figure 2-29 Commands Section of Summary Tab

Step 10 In the Virtual Machine Properties dialog box, choose CD/DVD drive 1.

Figure 2-30 CD/DVD Drive 1 Option in the Virtual Machine Properties Dialog Box

Step 11 Click the Datastore ISO File radio button within the Device Type area.

Step 12 Click the Browse button next to it.

Step 13 In the Browse Datastores dialog box, select the datastore and then the ISO file that you just uploaded.



Figure 2-31 Browse Datastores Dialog Box

Step 14 Click OK.

Step 15 Check the Connect at power on check box within the Device Status area.

Figure 2-32 Connect at power on Check Box

Step 16 Click OK.

Install ISO and Boot Up

Step 1 In the Summary tab, click Open Console to open the Console window. Alternatively, you can click the Console tab.

Figure 2-33 Open Console Command in the Summary Tab



Figure 2-34 Console Tab

Step 2 Click the green play button in the menu bar to power on the VM. Alternatively, click Power On in the Commands area of the Summary tab.

Figure 2-35 Play Button in the Menu Bar

Figure 2-36 Power On Button in the Summary Tab

When the VM power on process is complete, you will see the Cisco logo and the boot prompt.



Figure 2-37 Power On Complete Screen

Step 3 Move your pointer within the Cisco logo and click your mouse button to enter commands within the console.

Tip If you want to access features in vSphere, press Ctrl-Alt.

Step 4 Type install at the boot prompt and press the Enter key.

Figure 2-38 Type “install” at the Boot Prompt

The ISO installs and auto boots up. It also installs VMware Tools, which can be verified in the Summary tab.



Figure 2-39 VMware Tools are Installed and Running

The installation is complete when you see the message “IEM Installation is SUCCESS” and the iem login prompt.

Figure 2-40 IEM Installation Successful Screen

Verify High Availability of the IEM’s VMIf vSphere HA has already been configured, then it is automatically enabled for every VM including the IEM’s VM.

To verify that vSphere HA is turned on for your cluster, follow these steps:



Step 1 Choose the cluster and then choose Edit settings.

Figure 2-41 Cluster Menu

Step 2 Verify that the Turn On vSphere HA checkbox has a checkmark under the Features section.

Figure 2-42 vSphere HA shown as a Cluster Feature

You can also verify whether an individual VM such as the IEM’s VM is protected by HA by performing the following steps:

Step 1 Choose the VM.


Chapter 2 Installing the IEM Software Install IEM Software on Bare Metal - Method #1

Step 2 Go to the Summary tab.

Step 3 Look at the last entry in the General section listed as “vSphere HA Protection”.

Figure 2-43 vSphere HA Protection

Step 4 If there is a green checkmark and word “Protected” next to it, HA is protecting the VM.

If you are experiencing issues with vSphere HA or have questions, please refer to VMware’s documentation for your particular version and edition at: http://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html

Install IEM Software on Bare Metal - Method #1If you do not install the IEM software on a virtual machine (VM), you can install it on a Cisco UCS server.

This method requires the following tasks:

1. Configure CIMC on a UCS server

2. Launch the CIMC KVM Console on the UCS Server

3. Configure hard disks with the LSI MegaRAID Configuration Utility

4. Install the IEM software on the CIMC KVM Console

Configure CIMC on a UCS ServerThe instructions below indicate how to configure CIMC on a UCS C220 M3 server.

Step 1 Connect a keyboard, monitor, and mouse to the UCS server.

Step 2 Power on the server.

The selection menu appears.



Figure 2-44 Selection Menu

Step 3 Press the F8 key to enter the CIMC Configuration Utility.

Figure 2-45 CIMC Configuration Utility

Step 4 Within the NIC mode section of the CIMC Configuration Utility, select Dedicated.

Step 5 Within the NIC redundancy section, select None.

Step 6 Within the Default User (Basic) section, set the default password.

Step 7 Within the IPV4 (Basic) section, enter the CIMC IP address, Subnetmask, and Gateway values.

Step 8 Press the F10 key to save the configuration.

Step 9 Press the F5 key to refresh the screen.

Step 10 Press the ESC key to exit the CIMC Configuration Utility.



Launch CIMC KVM Console on the UCS ServerThe instructions below indicate how to launch the CIMC KVM Console on a UCS C220 M3 server.

Step 1 Open an browser, and enter the CIMC’s IP address.

Step 2 When the warning windows appears, select Continue.

Figure 2-46 CIMC Web UI

Step 3 Enter the username and password.

Figure 2-47 CIMC Web UI Login Screen

Step 4 Click Log In.

The Server Summary window of the Cisco Integrated Management Controller opens.

Step 5 Within the Actions area, click the Launch KVM Console button.

Note The KVM console is based on JAVA, please make sure the JAVA version is up to date.



Step 6 Within the Actions area, click the Power On Server button.

Configure Hard Disks with LSI MegaRAID Configuration Utility

Step 1 When the LSI MegaRaid Configuration Utility screen appears, press Ctrl + H on the KVM console.

Figure 2-48 KVM Console

Step 2 In the Adapter Selection window, click the Start button.

Figure 2-49 Adapter Selection Window

Step 3 In the MegaRAID BIOS Configuration Utility, click on the Configuration Wizard button.



Figure 2-50 MegaRAID BIOS Configuration Utility Home Page

Step 4 In the Configuration Wizard, click the New Configuration radio button.

Figure 2-51 Configuration Wizard

Step 5 Click the Next button.

Step 6 When asked whether you want to clear the configuration, click Yes.

Figure 2-52 Clear Confirmation Page

Step 7 Click the Manual Configuration radio button.



Figure 2-53 Configuration Method

Step 8 Click Next.

Step 9 Click the Add To Array button to add both disks to Drive Group 0.

Figure 2-54 Drive Group Definition

Step 10 Click the Accept DG button.

Step 11 Click Next.

Step 12 Click the Add to SPAN button to add Drive Group 0 to the Span.

Figure 2-55 Span Definition

Step 13 Click Next.

Step 14 In the Virtual Drive Definition screen, confirm that the RAID Level is RAID 1.



Figure 2-56 Virtual Drive Definition

Step 15 Update the Select Size.

Step 16 Click Accept.

Step 17 Click Next.

Step 18 When you are asked whether you want to select Write Back with BBU mode, click Yes.

Figure 2-57 BBU Confirmation Page

Step 19 Click Yes to save this configuration.

Figure 2-58 Configuration Confirmation Page

Step 20 In the SSD Caching page, click Cancel.



Figure 2-59 SSD Caching Page

Note This C220 M3 Server is using SAS disks.

Step 21 When asked whether you want to initialize, click Yes.

Figure 2-60 Virtual Drive Initialization Confirmation Page

Step 22 In the Virtual Drives page, click the Home button in the lower left corner.



Figure 2-61 Virtual Drives Page

Step 23 In the Home page, verify the Virtual Drive information.

Figure 2-62 Home Page

Step 24 Click the Exit button.

Step 25 When asked whether you want to exit the application, click Yes.

Figure 2-63 Exit Confirmation Page



Install IEM on CIMC KVM ConsoleIn this task, you install the IEM software on the CIMC KVM Console.

Step 1 On the KVM Console, click the Virtual Media tab.

Figure 2-64 Virtual Media Tab

Step 2 Click Add Image.

Step 3 Select the IEM image.

Figure 2-65 Image Location Window



Step 4 Click Open.

Step 5 In the Client View window, select the IEM image.

Figure 2-66 Client View Window

Step 6 Click the Mapped check box.

Step 7 Click the KVM tab.

Step 8 In the Actions area of the CIMC Web UI, click the Power Cycle Server button.

Figure 2-67 Actions Buttons

The selection menu will appear.



Figure 2-68 Selection Menu

Step 9 Press the F6 key to enter the Boot Menu.

Figure 2-69 Boot Menu

Step 10 Using the arrow keys, select Cisco Virtual CD/DVD 1.22.

Step 11 Press the Enter key.

Step 12 When the large green and red Cisco logo appears, type install at the boot prompt and press the Enter key.



Figure 2-70 Boot Prompt

The ISO installs and auto boots up.

Install IEM Software on Bare Metal - Method #2The Cisco IEM software (ISO file) can be burned on a CD and then that CD used to boot up the server. Follow the instructions below to install the IEM software on a UCS server using a CD.

Step 1 Download the ISO file to your desktop.

Step 2 Burn the ISO file to a CD.

Step 3 Use the UCS’ KVM cable to connect a keyboard and VGA monitor to the console connector on the front panel.

Note Alternatively, you can use the VGA and USB ports on the rear panel. However, you cannot use the front panel console connector VGA and the rear panel VGA at the same time. If you are connected to one VGA connector and you then connect a video device to the other connector, the first VGA connector is disabled. You can then reactivate the first VGA connector only by rebooting the server.

Step 4 Plug the monitor into an AC power outlet and turn it on.

Step 5 Attach a power cord to each power supply in your server, and then attach the power cord to a grounded AC power outlet.

Wait for approximately two minutes to let the server boot in standby power during the first bootup.

You can verify power status by looking at the Power Status LED on the front panel:



• Off—The server is not receiving power. Check the power cord connections and the power source of the facility.

• Blinking green—The server is in standby power mode. Power is supplied only to the service processor and some motherboard functions.

• Solid green—The server is in main power mode. Power is supplied to all server components.

Note During boot up, the server beeps once for each USB device that is attached to the server. Even if there are no external USB devices attached, there is a short beep for each virtual USB device such as a virtual floppy drive, CD/DVD drive, keyboard, or mouse. A beep is also emitted if a USB device is hot-plugged or hot-unplugged during BIOS power-on self-test (POST), or while you are accessing the BIOS Setup utility or the EFI shell.

Figure 2-71 IEM Screen During Boot Up



Figure 2-72 IEM Installation Complete using DHCP Login Prompt

When the server finishes booting up, a login prompt appears. A message appears confirming that the installation is complete and successful: “IEM Installation is SUCCESS”.


Cisco

C H A P T E R 3
Configuring the IEM Software

Chapter OverviewThis chapter explains how to configure the IEM software after it has been installed on either a virtual machine or bare metal.


• Log In as Installer and Change Installer Password, page 3-1

• Configure Server Settings, page 3-3

– Configure Network Settings, page 3-3

– Restart Networking, page 3-9

– Get MAC Address of Active Network Interface, page 3-10

– Configure Time Zone, page 3-13

– Configure NTP, page 3-14

– Set Up SMTP Provider, page 3-17

– Configure Remote Logging Server, page 3-18

– Upload SSL Certificates and Private Keys, page 3-19

– Restart Web Service to Apply New Keys and Certificates, page 3-21

• Change the Network Maintenance Password, page 3-23

• Log Into the IEM as the Administrator, page 3-24

Log In as Installer and Change Installer PasswordBefore you log in as the installer, choose a password now as the window of opportunity to enter the password is limited. The installer password or passphrase must meet the following criteria:

• Password: A combination of upper case letters, lower case letters, numbers, and other characters. If you choose a twelve character long password, then choose characters from at least three out of the four categories. If you choose a eight character password, you must use characters from all four


Chapter 2 3 Configuring the IEM Software Log In as Installer and Change Installer Password

categories. But if you start your password with an upper case letter or end it with a number, additional characters from those categories must also be included in the password in order for the password to be valid.

• Passphrase: Should be of at least three words and sixteen to forty characters that are a combination of upper and lower case letters, numbers, and other characters.

Step 1 Choose a password or passphrase.

Step 2 At the iem login prompt, type installer.

Figure 2-1 IEM Login Prompt


Step 4 At the Password prompt, type cisco!123, which is the default password.


Step 6 Re-enter the default password.

You will now be prompted to change the password.

Figure 2-2 New Password Prompt

Step 7 Enter a new password following the password criteria outlined on the screen.

Note If you do not choose a password that meets the criteria, you will be logged out and must repeat the steps in this section.

Step 8 Re-enter the new password.


Chapter 2 3 Configuring the IEM Software Configure Server Settings

Configure Server Settings

Configure Network SettingsIt is recommended that you use static addressing instead of DHCP. Using DHCP can result in error messages such as those indicating that the database is offline. If more than one IEM is on the network, DHCP will only work for one of the IEMs.

Note The IEM does not support two network interfaces.

Tip The default username for the IEM Configuration Menu is installer. Use the new password not the default password.

The instructions below will configure a static address for the IEM.

Step 1 In the Main menu of the IEM Configuration Menu, type a to access the System Settings menu.

Figure 2-3 Main Menu

Step 2 In the System Settings menu, type a to access the Network Settings.



Figure 2-4 System Settings Menu

Step 3 Press any key to begin network configuration.

Figure 2-5 Configure Network Screen

You should verify the network settings next.

Step 4 In the Select Action dialog box, choose Edit a device params by highlighting it and pressing the Enter key.



Figure 2-6 Configure a Device’s Parameters

Note Press the Tab or Arrow keys to navigate between choices. Press the Space key to confirm your selection.

Step 5 In the Select A Device dialog box, choose the Ethernet card.

Figure 2-7 Select a Device Dialog Box

Step 6 Press F12.

Step 7 In the Devernet Configuration dialog box, uncheck the Use DHCP field by pressing the Space key.



Figure 2-8 Static IP Address Configuration

Step 8 In the Static IP field, enter the IP address.

Step 9 In the Netmask field, enter the netmask.

Step 10 In the Default gateway IP field, enter the default gateway IP address.

Step 11 Choose Ok.

Step 12 Press Enter.

Step 13 In the Select Action dialog box, choose Edit DNS configuration.

Figure 2-9 Edit DNS Configuration


Step 15 In the DNS configuration dialog box, enter the hostname for the IEM server.



Figure 2-10 DNS Configuration

Step 16 In the Primary DNS field, enter the primary DNS address.

Step 17 (Optional) In the Secondary and Tertiary DNS fields, enter additional DNS addresses.

Step 18 (Optional) Enter a search value.

Step 19 Click Ok.


Step 21 In the Select Action dialog box, choose Save & Quit.

Figure 2-11 Save and Quit


Step 23 When it quits, you see an empty blue box on the screen. Press any key to continue to the IEM Configuration menu.



Figure 2-12 Screen with Empty Blue Box

You are returned to the Network Settings menu.

Figure 2-13 Network Settings Menu

Step 24 Press the R, <, or , key to return to the System Settings menu.

Step 25 Press the R, <, or , key to return to the Main menu.



Restart Networking

Step 1 In the Main Menu, type c to access the Services Control menu.


Step 2 In the Services Control menu, type a to access Networking.

Figure 2-15 Services Control Menu

Step 3 In the Networking menu, type a to Restart networking.



Figure 2-16 Networking Menu

This restarts the network and updates the configuration.

When it is complete, you will see the “Command completed successfully.” message.

Figure 2-17 Restarting Network Successful Screen

Step 4 Press any key.

Get MAC Address of Active Network InterfaceYou will need the MAC address of the active network interface for licensing.

Step 1 Use a Secure Shell (SSH) client to log into the VM.



Figure 2-18 Main Menu in a SSH Client

Step 2 In the Main menu, type a to access the System Settings menu.

Step 3 In the System Settings menu, type c to access System Information.


Step 4 Copy the MAC address, which follows the term “HWaddr” in the first line of the eth0 details of the IEM Configuration Menu screen.



Figure 2-20 IEM Configuration Menu

Step 5 Press any key to return to the System Settings menu.




Configure Time Zone


Step 2 In the System Settings menu, type b to access the Date and Time Settings.


Step 3 In the Date and Time Settings menu, type b to change the time zone.

Figure 2-22 Date and Time Settings Menu

Step 4 Select a continent or ocean by entering a number.

Figure 2-23 Continent or Ocean Selection

Step 5 Select a country.

Step 6 Select time zone region.

Step 7 Confirm that the current local time for your time zone and universal time (UTC) are correct. Type 1.



Figure 2-24 Current Local and Universal Times

Step 8 Press any key to continue.

Configure NTP

Using Console


Step 2 In the System Settings menu, type b to access the Date and Time Settings.


Step 3 In the Date and Time Settings menu, type a to access the NTP setup.

Figure 2-26 Date and Time Settings Menu

Step 4 In the Configure NTP screen, press any key to begin set up.

Figure 2-27 Configure NTP Screen



Step 5 Enter the NTP configuration information.

Figure 2-28 NTP Configuration Screen

Step 6 When you are finished, type :wq and press the Enter key to save and quit.

Using the Post-Install Configuration Screen

Tip The default username for the Post-Install Configuration site is admin and the default password is cisco!123.

Step 1 Go to the following link for Post-Install Configuration screen: http://[IEM_IP]/cisco/status.php where [IEM_IP] is the IP address of the IEM.

Step 2 In the Post-Install Configuration screen, click Configure NTP Server.



Figure 4-29 Post-Installation Configuration Screen

Step 3 In the NTP Configuration screen, click Edit.

Figure 4-30 NTP Configuration Screen

Step 4 Enter the NTP server(s) path(s).

Figure 4-31 Edit NTP Configuration Screen

Step 5 Once the changes are made, click Update Settings to save the changes.



Set Up SMTP ProviderThe SMTP Provider in the IEM sends notifications including the IECs’ status. The SMTP Provider is configured with an outbound URL in order to send the notifications.

The SMTP feature only works with non-authenticated mail servers. Free email service providers such as Gmail and Hotmail are not supported because they require authentication.

Note Cisco Advanced Services offers customized services such as the configuration of authenticated mail servers. Customers who are in need of this service should contact Cisco Advanced Services.

Once you have set up the SMTP provider, follow the instructions in the “Alerts & Notifications” chapter of the Cisco Interactive Experience Manager Administrator Guide to create a notification and associate it with users.

The following are instructions on how to configure the SMTP provider.

Step 1 Go to the Post-Installation Configuration screen.

Tip The default username for the Post-Install Configuration site is admin and the default password is cisco!123.


Step 2 Click Setup SMTP Provider.



Figure 4-33 SMTP Provider Configuration Screen

Step 3 In the SMTP Provider Configuration, click Edit.

Figure 4-34 Edit SMTP Provider Configuration Screen

Step 4 Enter the SMTP relay hostname or IP address of the SMTP provider.

Note The SMTP relay host must not require authentication.

Step 5 Click Update Settings to save the changes.

Configure Remote Logging Server

Step 1 In the Post-Installation Configuration screen, click Configure Remote Logging Server.




Step 2 In the Remote Logging Configuration Screen, click Edit.

Figure 4-36 Remote Logging Configuration Screen

Step 3 Enter the server path in the Remote Logging Server field.

Figure 4-37 Edit Remote Logging Configuration Screen

Step 4 Click Update Settings to save the changes.

Upload SSL Certificates and Private KeysThe IEM uses self-signing certificates. Thus you may see a similar pop-up to that in the figure below when accessing the IEM using your browser.



Figure 2-38 Security Exception Dialog Box

If your organization has a SSL certificate and private key, they can be uploaded into the IEM so that security warnings such as “this site is using an untrusted key” do not appear when accessing the IEM.

Step 1 In the Post-Installation Configuration screen, click Upload New Certificate/Private Key.


Step 2 Follow the steps in the Active SSL Certificate screen to upload a certificate and private key.



Figure 4-40 SSL Certificate Screen

Restart Web Service to Apply New Keys and CertificatesYou will need to restart the web service to apply the new keys and certificates.

Step 1 In the Main Menu, type c to access the Services Control menu.




Step 2 In the Services Control menu, type b to access Web Server.

Figure 2-42 Services Control Menu

Step 3 In the Web Server menu, type c to stop the service.

Figure 2-43 Networking Menu

Step 4 Press any key to return to the Web Server menu.

Step 5 Type a to view the status of the service. Before going to the next step, make sure that the service has stopped.


Chapter 2 3 Configuring the IEM Software Change the Network Maintenance Password

Figure 2-44 Web Service Stopped


Step 7 Type b to start the service.


Step 9 Type a to view the status of the service. Before going to the next step, make sure that the service has started.

Figure 2-45 Web Service Running


Change the Network Maintenance PasswordThe maintenance password, also known as DMC (Device Maintenance Code), is used to access the system settings of the IEC. This can be changed in the event a user forgets the password and needs to access system settings but is unable to fetch it from the IEM.

Step 1 Go to the following link for Post-Install Configuration screen: http://[IEM_IP]/cisco/status.php. [IEM_IP] is the IP address of the IEM.

Step 2 Click Change Maintenance Password.



Chapter 2 3 Configuring the IEM Software Log Into the IEM as the Administrator

Step 3 Enter a new password in the New Password and Confirm Password fields to change the maintenance password.

Figure 4-47 Update Password Screen

Step 4 Click Update Password.

Log Into the IEM as the AdministratorUse a supported platform and browser version to access the IEM.

The following platforms are supported by the IEM:

• Windows XP (32bit or 64bit)

• Windows 7 (32bit or 64bit)

• Macintosh OS 10.6.8

The following browser versions are supported by the IEM:

• Internet Explorer 8 and 9 (32bit and 64bit)

• Firefox 12

Step 1 Open a supported browser and enter the IEM’s IP address in the browser.

The IEM login window opens.

Figure 2-48 IEM Login Window



Step 2 In the Account field, enter Root.

Step 3 In the User Name field, enter Administrator.

Step 4 In the Password field, enter cisco!123.

You are now logged in the IEM.


Cisco

C H A P T E R 4
Using the IEM Configuration Menu

Chapter OverviewThis chapter explains how to use the IEM Configuration Menu that is accessed by using a SSH client.

The topics in this chapter are:

• View System Settings, page 4-2

• Ping a Host, page 4-4

• View Logs, page 4-5

• Reboot the Server, page 4-7

• Power Off the Server, page 4-8

• Enable Cisco TAC User, page 4-9

Tip When logging into the IEM using a SSH client, use the password that was chosen when the IEM was installed.

Note If you are configuring the server settings for the IEM in the console screen and have changed the password for the Administrator within the Root account, the message “IEM Installation has FAILED!”. This message is due to the fact that the IEM ISO in this build is using the default password to check whether the IEM is up and running. No action is required; you can ignore the failure message.

Figure 5-1 IEM Installation Failure Message


Chapter 4 Using the IEM Configuration Menu View System Settings

View System SettingsThe administrator can view system settings using the Console tab in the VM or a Secure Shell (SSH) client.

Step 1 Log into the VM.


Figure 2-2 Main Menu in the Console Tab


Chapter 4 Using the IEM Configuration Menu View System Settings


Step 3 In the System Settings menu, type c to access System Information.

Figure 4-4 System Settings


Chapter 4 Using the IEM Configuration Menu Ping a Host

Step 4 Review the system information.

Figure 4-5 System Information

Step 5 Press any key to return to the System Settings menu.


Ping a HostUse the Ping utility to verify that the IEM can reach an IEC or that the NTP and SMTP servers are up.



Chapter 4 Using the IEM Configuration Menu View Logs


Step 2 In the Main menu, type e to access the Troubleshooting menu.

Step 3 In the Troubleshooting menu, type a to ping a host.

Figure 5-7 Troubleshooting Menu

Step 4 When finished, press any key to return to the Troubleshooting menu.


View Logs



Chapter 4 Using the IEM Configuration Menu View Logs


Step 2 In the Main menu, type e to access the Troubleshooting menu.

Step 3 In the Troubleshooting menu, type b to access logs.

Figure 5-9 Logs Menu

Step 4 Choose the type of logs desired, such as the Web Server logs.

Figure 5-10 Web Server Logs

Step 5 Choose one of the menus, such as the Web Server SSL Engine Log menu.


Chapter 4 Using the IEM Configuration Menu Reboot the Server

Figure 5-11 Web Server SSL Engine Log Menu

Step 6 Type b to view the log.

Step 7 Press a key to begin watching the log.

Figure 5-12 Log Screen

Step 8 Press ESC :q! to stop watching the log.

Step 9 When finished, press the R, <, or , key to return to the previous menu.

Reboot the Server



Chapter 4 Using the IEM Configuration Menu Power Off the Server


Step 2 In the Main menu, type d to access the IEM Server Administration menu.

Step 3 In the IEM Server Administration menu, type b to reboot the server.

Figure 4-14 IEM Server Administration Menu

Power Off the Server



Chapter 4 Using the IEM Configuration Menu Enable Cisco TAC User


Step 2 In the Main menu, type d to access the IEM Server Administration menu.

Step 3 In the IEM Server Administration menu, type c to reboot the server.


Enable Cisco TAC UserCustomers who have purchased SMARTnet can give SSH access to Cisco TAC engineers to troubleshoot and fix IEM issues remotely. The key generated by the TAC is only valid for 24 hours.

Tip The TAC engineer can press Ctrl-C at anytime to log out of the session.

For a TAC engineer to SSH into the IEM, you must first enable the TAC user feature. Follow the steps below.





Step 2 In the Main menu, type b to access the System Accounts menu.

Step 3 In the System Accounts menu, type a to access the Enable/Disable TAC user menu.

Figure 5-18 System Accounts Menu

Step 4 In the Enable/Disable TAC user menu, type a to enable the TAC user. This gives a TAC engineer shell access.

Figure 5-19 Enable/Disable TAC User Menu

The TAC user is now enabled.



Figure 5-20 Enabled TAC User


Cisco

C H A P T E R 5
Upgrading the IEM Software

Chapter Overview

Tip When installing the Cisco IEM, check the Cisco Interactive Services Solution support pages on www.cisco.com for the latest software version. Check the site periodically after that for new software versions.

This chapter explains how to upgrade the IEM software.


• What You Will Need, page 5-1

• Gather the IEM Software Files, page 5-2

• Upgrade Options Overview, page 5-2

– 1.0.0, 1.0.1, or 1.0.2 to 2.0, page 5-2

– 1.0.3 to 2.0, page 5-3

– 2.0 to latest 2.0 build, page 5-3

• ISO Upgrade Option, page 5-4

• Fresh Install Upgrade Option, page 5-7

• Upgrading 2.0 Builds, page 5-11

What You Will NeedTo upgrade the Cisco IEM, you will need the following:

• IEM software files downloaded from www.cisco.com:

1. IEM-upgrade.ISO file

2. IEM OVA file


Chapter 5 Upgrading the IEM Software Gather the IEM Software Files

Gather the IEM Software FilesThe IEM-upgrade.ISO and IEM OVA files are available for download. Follow the steps below to download them.

Step 1 Enter the following URL in your web browser: http://www.cisco.com/en/US/partner/products/ps12434/tsd_products_support_general_information.html

Step 2 Log in using your partner or customer credentials.

Step 3 Within the Support area, click Download Software.

Figure 2-1 IEM Software Downloads, Release and General Information Page

Step 4 Under Release 2.0, select the IEM OVA file.


Step 6 Select the IEM-upgrade.ISO file.


Upgrade Options Overview

1.0.0, 1.0.1, or 1.0.2 to 2.0If you are using an IEM version that is older than 1.0.3, you must first upgrade the IEM to 1.0.3. Follow the instructions in Chapter 4 of the Cisco Interactive Experience Manager Installation Guide version 1.0.3 to upgrade from version 1.0.0, 1.0.1, or 1.0.2 to 1.0.3.


Chapter 5 Upgrading the IEM Software Upgrade Options Overview

Then upgrade from version 1.0.3 to 2.0. See the instructions below on how to upgrade from 1.0.3 to 2.0

Table 5-1 Upgrade from 1.0.3 Option Matrix

1.0.3 to 2.0A fresh installation is required for all upgrades from version 1.0.3 to 2.0 except if you are upgrading from 1.0.3 on a virtual machine (VM) to 2.0 on the same VM; then only the ISO needs to be upgraded. See the next section for instructions on how to upgrade the ISO only.

Table 5-2 Upgrade from 1.0.3 Option Matrix

Note Build number 1.8.05.5799 is only certified on bare metal.

Tip The default username for the Post-Install Configuration site is admin and the default password is cisco!123 if you have build 1.8.05.5799 (1.0.3 on bare metal). The default username for the Post-Install Configuration site is installer and the default password is cisco!123 if you have build 1.8.08.5799 (1.0.3 on a virtual machine).

2.0 to latest 2.0 buildIf you are upgrading from an older 2.0 build to the latest 2.0 build, an ISO upgrade is only required if you are using a VM. If you are using bare metal, you will need to perform a fresh install.

Table 5-3 Upgrade to Latest 2.0 Build Option Matrix

2.0 Virtual Machine 2.0 Bare Metal

1.0.0 Bare MetalUpgrade to 1.0.3 first then upgrade to 2.0

Upgrade to 1.0.3 first then upgrade to 2.0






1.0.3 Virtual Machine (build number 1.8.08.5799) ISO Upgrade only Fresh install

1.0.3 Bare Metal (build number 1.8.05.5799) Fresh install Fresh install


2.0 Virtual Machine ISO Upgrade only Fresh install

2.0 Bare Metal Fresh install Fresh install


Chapter 5 Upgrading the IEM Software ISO Upgrade Option

ISO Upgrade OptionAs explained above, this option is only possible if you are upgrading from 1.0.3 that is installed on a VM.

Requirements:

• Perform the backup before the upgrade to prevent data loss from upgrade failure.

• The upgrade must be performed by an authorized Cisco team member who is able to request a Cisco TAC user validation string at https://tacaccess.cisco.com/cgi-bin/tacaccess.cgi.

• The person performing the upgrade must be able to upload the IEM upgrade ISO via SCP/SFTP.

Tip The default username for the IEM Configuration Menu is installer. Use the password that was chosen when the IEM was installed.

Step 1 Perform a backup of the server. Refer to the Cisco Interactive Experience Manager Administrator Guide for instructions.

Step 2 Request a Cisco TAC user validation string at https://tacaccess.cisco.com/cgi-bin/tacaccess.cgi.

Step 3 Log in as installer.

Figure 5-2 IEM VM Console Login Screen

Step 4 In the IEM VM Configuration Menu screen, you will see that the IEM software version is given as 1.8.08-5799.



Figure 5-3 IEM VM Configuration Menu Screen

Step 5 Type b to access System Accounts.

Figure 5-4 System Accounts Menu

Step 6 Type a to access the Enable/Disable TAC user menu.

Figure 5-5 Enable/Disable TAC User Menu

Step 7 Type a to enable TAC user account.

Figure 5-6 TAC User Has Been Enabled

Step 8 Press any key to return to the menu.



Step 9 Now you will SSH into the VM as the Cisco TAC user. First, choose a password that you will temporarily use just for the session. Since the window to enter the password is limited and the password must be complex, choose the password now. The installer password or passphrase must meet the following criteria:

• Password: A combination of upper case letters, lower case letters, numbers, and other characters. If you choose a twelve character long password, then choose characters from at least three out of the four categories. If you choose a eight character password, you must use characters from all four categories. But if you start your password with an upper case letter or end it with a number, additional characters from those categories must also be included in the password in order for the password to be valid.

• Passphrase: Should be of at least three words and sixteen to forty characters that are a combination of upper and lower case letters, numbers, and other characters.

Step 10 SSH into the IEM VM as ciscotac with the default password (not the password that you chose in the step above).

Figure 5-7 SSH Terminal with Cisco User Credentials

Step 11 Copy the Cisco TAC user validation string and press the Enter key.

Figure 5-8 SSH Terminal with TAC Access Validation String

Step 12 Enter the new password that you chose earlier.

Figure 5-9 SSH Terminal with TAC User Password


Chapter 5 Upgrading the IEM Software Fresh Install Upgrade Option

Step 13 Re-log in with the new user credentials.

Step 14 Download the IEM Upgrade ISO and put it into the directory via SFTP.

Figure 5-10 SSH Terminal with Downloaded IEM Upgrade ISO File

Note Any directory on any SFTP server can be used.

Step 15 Type ls to confirm the IEM upgrade ISO is being downloaded.

To mount the ISO on a directory enter the command sudo mount -o loop IEM-UPGRADE-XXXX.iso /var/rpms/Cisco/.

Note Replace “XXXX” with the version number. The IEM Upgrade ISO version can vary so enter the version number carefully.

Figure 5-11 SSH Terminal with Mounting of the ISO

Step 16 To run the IEM Upgrade script, enter the command sudo /var/rpms/Cisco/scripts/iem_upgrade.sh.

Note The directory (e.g. /var/rpms/Cisco/) of the ISO being mounted is permanent.

After the upgrade is complete, log into the IEM GUI using a browser to confirm that the upgrade was successful and no information was lost.

Fresh Install Upgrade Option1. Follow either the VM or bare metal installation steps in Chapter 2 of this guide depending on

whether you will install 2.0 on a VM (recommended) or bare metal.

2. Follow the steps in Chapter 3 of this guide to configure the IEM.

3. Export data from the IEM 1.0.3 server (see below).

4. Import data into the new IEM 2.0 instance (see below).



In the following steps, you will export account data from the IEM 1.0.3 server and import it into the IEM 2.0 server.

Step 1 On the IEM 1.0.3 server, click Accounts.

Figure 5-12 Accounts Button

Step 2 Choose an account.

Step 3 In the Edit menu, click Export Account.

Figure 5-13 Export Account Button

The Export dialog box opens.

Step 4 From the drop-down list, choose the element to export.



Figure 5-14 Export Account Dialog Box

Step 5 Click Export.

Step 6 Repeat previous steps until you have exported all accounts.

Next you will import the account data to IEM 2.0.

Step 7 In the IEM 2.0 application, click Accounts.

Figure 5-15 Accounts Button

Step 8 Choose an account.

Step 9 In the Edit menu, click Import Account.



Figure 5-16 Import Account Button

Step 10 In the Import Account dialog box, click Add.

Figure 5-17 Import Account Dialog Box

Step 11 Find the file on your computer. Choose the file and then click Open.

Figure 5-18 Select Files Dialog Box on Computer

Step 12 The file name then appears in the Import dialog box.


Chapter 5 Upgrading the IEM Software Upgrading 2.0 Builds

Figure 5-19 File in Import Account Dialog Box

Step 13 Click Upload.

A green check mark appears next to the file after it has been uploaded.

Tip If a file uploaded is not desired or there is an error message associated with it, delete that file. Choose that file and then click remove.

Step 14 Click Close.

If you imported device names from 1.0.3 that included the dash/minus/hyphen sign (-), the sign will transfer to 2.0 and will still be present. But if you modify the name of the device after you import it into 2.0, you can no longer use the sign within the name of that device as per the naming rules set by 2.0. Refer to the Cisco Interactive Experience Manager Administrator Guide for more information about naming devices.

Upgrading 2.0 BuildsWhen a new build of the IEM software Version 2.0 is released, it is a best practice to upgrade your IEM to the latest build to take advantage of any enhancements and patches.

The process for upgrading to a newer 2.0 build is dependent on where the 2.0 IEM software has been installed:

• Bare metal: Follow the backup and restore steps in Chapter 9 of the Cisco Interactive Experience Manager Administrator Guide to upgrade the IEM software from an older 2.0 build to a newer 2.0 build.

• VM: Follow the steps below to upgrade a VM from an older 2.0 build to a newer 2.0 build.

Note It is best practice to backup the VM before starting the upgrading process to prevent data loss in case the upgrade fails.

Step 1 Open https://<IEM_IP>/cisco/status.php with a browser.



Figure 5-20 Status Page

Step 2 Look at the Build Version and verify the current IEM application version is older than the newest build posted on www.cisco.com.

Step 3 Click the Perform Upgrade button.

Figure 5-21 Upgrade Screen

Step 4 Click Browse.

Step 5 In the File Upload dialog box, choose the appropriate IEM Upgrade ISO file.



Figure 5-22 File Upload Dialog Box

Step 6 Click Open.

The ISO appears in the Choose an ISO to upload field.

Figure 5-23 Upgrade Screen With ISO Loaded

Step 7 Verify that the correct version of the IEM Upgrade ISO is uploaded.

Step 8 Click the Upload ISO button.

Step 9 SSH into the IEM as installer.

Figure 5-24 SSH Terminal



Step 10 Enter the installer password.

Step 11 In the Configuration Menu, type d to access the IEM Server Administration menu.

Figure 5-25 IEM Configuration Menu

Step 12 In the IEM Server Administration menu, type b to access the Upgrade Server menu.


Step 13 In the Upgrade Server menu, verify that the correct version of IEM Upgrade ISO exists.

Figure 5-27 Upgrade Server Menu

Step 14 Type the number that corresponds with the desired ISO. In the figure above, the only choice is “1”.


Step 16 Type C to continue with the upgrade.

Step 17 After the upgrade is complete, log out from the IEM.

Step 18 Log into the IEM GUI using a browser.

Step 19 Confirm that the upgrade is successful (the build number should be updated) and no information was lost.


Cisco Interac

A
P P E N D I X A High Availability Installation and Configuration

Appendix OverviewThis appendix explains how to install and configure high availability for the Cisco Interactive Experience Manager (IEM).

Topics in this appendix include:

• Conceptual Deployment Diagram, page A-2

• Install Additional Components, page A-2

– Install pgpool-II, page A-2

• System Level Prerequisites, page A-3

– Configure Password-less Remote Access on HOST 1, page A-3

– Configure Password-less Remote Access on HOST 2, page A-4

• Update Configurations, page A-4

– Update Postgres Configuration, page A-4

– Update pgpool-II Configuration, page A-5

– Synchronize Configuration Files, page A-5

– Restart postgresql, page A-6

– Restart pgpool-II, page A-6

– Configure the Virtual IP Address of the Load Balancer, page A-6

– pgpool-II Watchdog Script, page A-7

• Online Recovery Workflow Diagram, page A-7

A-1tive Experience Manager Installation Guide

Appendix A High Availability Installation and Configuration Conceptual Deployment Diagram

Conceptual Deployment DiagramFigure 2 Conceptual Deployment Diagram

Install Additional ComponentsBefore you can configure pgpool-II, you will need to install the IEM-HA ISO file.

Install pgpool-II

Step 1 Burn the IEM-HA-1.0.3-1.x86_64.iso file to a CD.

Step 2 Insert CD into the IEM server.

Step 3 SSH into the IEM server via the Cisco TAC generated account.

Step 4 Mount the CD using the following command:

`sudo mount /dev/cdrom /media`

A-2Cisco Interactive Experience Manager Installation Guide

Appendix A High Availability Installation and Configuration System Level Prerequisites

Step 5 Run the following commands:

$ sudo rpm –Uvh /media/RPMS/pgppol-II-2.3-1.el5.x86_64.rpm

$ sudo rpm –Uvh /media/RPMS/iem-ha-1.0.3-1.x86_64.rpm

System Level PrerequisitesPassword-less SSH access is required for the 'postgres' user across all IEM nodes for the online recovery feature.

The following step sets show you how to enable password-less SSH access to the 'postgres' user on HOST 1 and HOST 2.

Configure Password-less Remote Access on HOST 1

Step 1 On HOST 1, enter the following command:

$ sudo ssh-keygen -t rsa -b 2048

This command generates the public/private rsa key pair.

Step 2 Enter the file in which to save the key (/root/.ssh/id_rsa):

/var/lib/pgsql/.ssh/id_rsa

Step 3 Enter the passphrase (leave empty for no passphrase).

Step 4 Enter the same passphrase again.

Your identification has been saved in /var/lib/pgsql/.ssh/id_rsa.

Your public key has been saved in /var/lib/pgsql/.ssh/id_rsa.pub.

The key fingerprint is:

90:e9:46:26:6f:cd:0e:d9:92:7f:da:d9:eb:22:af:c2 root@HOST1

Step 5 On HOST 1, enter the following commands:

$ sudo chown -R postgres:postgres /var/lib/pgsql/.ssh

$ sudo scp /var/lib/pgsql/.ssh/id_rsa.pub <ciscotac account>@HOST2:


$ sudo cp id_rsa.pub /var/lib/pgsql/.ssh/authorized_keys

$ sudo chown postgres:postgres /var/lib/pgsql/.ssh/authorized_keys

$ sudo chmod 400 /var/lib/pgsql/.ssh/authorized_keys



Appendix A High Availability Installation and Configuration Update Configurations

Configure Password-less Remote Access on HOST 2

Step 1 On HOST 2, enter the following command:

$ sudo ssh-keygen -t rsa -b 2048

This command generates the public/private rsa key pair.

Step 2 Enter the file in which to save the key (/root/.ssh/id_rsa):

/var/lib/pgsql/.ssh/id_rsa

Step 3 Enter the passphrase (leave empty for no passphrase).

Step 4 Enter the same passphrase again.

Your identification has been saved in /var/lib/pgsql/.ssh/id_rsa.

Your public key has been saved in /var/lib/pgsql/.ssh/id_rsa.pub.

The key fingerprint is:

90:e9:46:26:6f:cd:0e:d9:92:7f:da:d9:eb:22:af:c2 root@HOST2



$ sudo scp /var/lib/pgsql/.ssh/id_rsa.pub <ciscotac account>@HOST1:


$ sudo cp id_rsa.pub /var/lib/pgsql/.ssh/authorized_keys

$ sudo chown postgres:postgres /var/lib/pgsql/.ssh/authorized_keys

$ sudo chmod 400 /var/lib/pgsql/.ssh/authorized_keys


Update ConfigurationsIn the following step sets, you will perform the following:

1. Update the Postgres configuration.

2. Update the pgpool-II configuration.

3. Synchronize the configuration files.

4. Restart postgresql.

5. Restart pgpool_II.

6. Configure the virtual IP address of the load balancer in the IEM configuration file.

Update Postgres Configuration

Step 1 Go to the Postgres configuration file (pg_hba.conf):

sudo vim /var/iem/etc/pgpool-II/pg_hba.conf



Step 2 Find the following lines of code:

## One entry for each postgres instance managed by pgpoolhost all all host0_ip/32 trusthost all all host1_ip/32 trust#

Step 3 Update the “host0_ip” and “host1_ip” entries.

Update pgpool-II Configuration

Step 1 Go to the pgpool-II configuration file (pgpool.conf):

sudo vim /var/iem/etc/pgpool-II/pgpool.conf


backend_hostname0 = 'host0_ip' # Host name or IP address to connect to for backend 0

backend_port0 = 6543# Port number for backend 0

backend_hostname1 = 'host1_ip'backend_port1 = 6543

Step 3 Update the “host0_ip” and “host1_ip” entries.

Step 4 Go to the pool hba configuration file (pool_hba.conf):

sudo vim /var/iem/etc/pgpool-II/pool_hba.conf


## One entry for each postgres instance managed by pgpoolhost all all host0_ip/32 trusthost all all host1_ip/32 trust#

Step 6 Update the “host0_ip” and “host1_ip” entries to ensure that Postgres instances of every IEM node can talk to each other.

Synchronize Configuration Files

Step 1 Run the following script:

$ sudo /var/iem/bin/sync_confs.sh



Restart postgresql

Step 1 Run the following script to restart postgreql:

$ sudo /bin/service postgresql restart

Restart pgpool-II

Step 1 Run the following script to restart the pgpool process:

$ sudo /bin/service pgpool restart

Note You may see the message “FAIL” when trying to stop the service. This is normal the first time.

Configure the Virtual IP Address of the Load BalancerIn this step set, you will set the virtual IP address of the load balancer in the IEM configuration file.


$ sudo vim /var/www/html/config.xml


<config><service>https://172.25.26.240/index.php/amf</service><debug>0</debug> <login>

<user></user><password></password><accname></accname>

</login><appName>ServiceGUI</appName><appHeader>true</appHeader><updateDelay>20000</updateDelay><useExperimentalProps>0</useExperimentalProps><allowRegistration>false</allowRegistration></config>

Step 3 Replace the IP address “172.25.26.240” in the <service>https://172.25.26.240/index.php/amf</service> line with the virtual IP address of the load balancer.


$ sudo vim /var/www/html/checker.php


<?php

$server = isset($argv[1]) ? $argv[1] : '172.25.26.240';$emails = isset($argv[2]) ? explode(',', $argv[2]) : array();


Appendix A High Availability Installation and Configuration Online Recovery Workflow Diagram

Step 6 Replace the IP address “172.25.26.240” in the $server = isset($argv[1]) ? $argv[1] : '172.25.26.240'; line with the virtual IP address of the load balancer.

pgpool-II Watchdog ScriptThe pgpool-II watchdog script is automatically installed and monitors the pgpool process. If the pgpool process fails, the watchdog script attempts to restart the process. If the process fails to start, the watchdog script will shut down the web server to failover to the other active node. The watchdog script will continue to check the progress of the pgpool process, and if the pgpool process starts, the watchdog script will bring the web server back up.

Online Recovery Workflow DiagramThe online recovery process can be logically defined in three steps:

1. (Script file -> copy_base_backup): During this step, pgpool takes a backup of the database yet still allows user connections. (File: copy_base_backup)

2. (Script file -> pgpool_recovery_pitr): This step waits for user connections to close [can force it] and stops new connections to pgpool.

3. (Script file -> pgpool_remote_start): This step starts postgres on the new or failed machine.


Appendix A High Availability Installation and Configuration Online Recovery Workflow Diagram


cisco interactive experience manager installation guide v2€¦ · cisco interactive experience...

Documents