After I and configured Prime Infrastructure (PI) vSphere Client reported the PI vm was running an outdated version of VMware Tools. To upgrade VMware Tools you need to enable root access on the PI appliances, then follow the VMware instructions for '.Step 1 - SSH into the appliance and login.Step 2 - Enable root shell and set the password, then log into rootlab-prime/admin# rootenablePassword:Password Again:Root enabledlab-prime/admin#lab-prime/admin# rootEnter root password:Starting root bash shell.!Step 3 - On the VMware host, enable Interactive Tools Upgrade. Right click the VM, Guest, Install/Upgrade VMware Tools, and select Interactive Tools Upgrade.Step 4 - Back in the ssh windows, mount vmware tools and copy to /tmpade # mkdir /mnt/cdromade # mount /dev/cdrom /mnt/cdrommount: block device /dev/cdrom is write-protected, mounting read-onlyade # cd /mnt/cdromade # ls grep VMwareVMwareTools-9.4.0-1280544.tar.gz.
How to Inline Upgrade Cisco Prime 3.2 to 3.4. Cisco Prime supports inline upgrades of 3.1.x, 3.2.x, and 3.3.x to 3.4. This means you don’t have to stand up a new appliance and migrate data, saving gobs of time. Download the upgrade file for Prime 3.4 (or whichever version you’re upgrading to).
Product OverviewPrime Infrastructure provides a single integrated solution for comprehensive lifecycle management of the wired or wireless access, campus, and branch networks, and rich visibility into end-user connectivity and application performance assurance issues. Prime Infrastructure accelerates the rollout of new services, secure access and management of mobile devices, making “Bring Your Own Device” (BYOD) a reality for corporate IT. Tightly coupling client awareness with application performance visibility and network control, Prime Infrastructure helps ensure uncompromised end-user quality of experience. Deep integration with the Cisco Identity Services Engine (ISE) further extends this visibility across security and policy-related problems, presenting a complete view of client access issues with a clear path to solving them.For:.An overview of Prime Infrastructure features and benefits, see the latest.Information about frequently used Prime Infrastructure features, see the.Information about features intended for administrators, see the. Understanding System RequirementsPrime Infrastructure comes in two main forms:.Virtual: The Prime Infrastructure virtual appliance is packaged as an Open Virtualization Archive (OVA) file, which must be installed on a user-supplied, qualified server running VMware ESXi. This form allows you to run on the server hardware of your choice.
You can also install the virtual appliance in any of four configurations, each optimized for a different size of enterprise network. For hardware requirements and capacities for each of the virtual appliance’s size options, see.Physical: The physical appliance is packaged as a rack-mountable server, with Prime Infrastructure pre-installed and configured for you. For physical appliance hardware specifications and capacities, see. 1.You can configure any combination of sockets and cores, the product of which must equal the number of virtual CPUs required. For example, if 16 virtual CPUs are required, you can configure 4 sockets with 4 cores, or 2 sockets with 8 cores, etc.You can install any of the Prime Infrastructure options as an Open Virtual Appliance (OVA), running under VMWare ESXi, on your own hardware.
If you choose this implementation, the server that you supply must meet or exceed the requirements shown in the table for the option that you select.Prime Infrastructure is also available pre-installed on Cisco-supplied hardware as a physical appliance. See thefor more information.For maximum management capacities for each installation option, see. Improving Performance of AppliancesFor better performance on the Prime Infrastructure Appliance (Gen 2, UCS based), make sure you configure the virtual drive Write Policy to Write Back Good BBU. To configure the virtual drive Write Policy, follow these steps:Step 1Launch the CIMC web interface (see “” in the).Step 2Click theStoragetab, click on the SAS Modular Controller name, click theVirtual Drivetab, then clickEdit Virtual Drive.Step 3ClickOKon the dialog box that appears.Step 4In the Write Policy field, selectWrite Back Good BBU, then clickSave Changes. Web Client RequirementsPrime Infrastructure users access the product using a web browser client.
Web client requirements are:.Hardware—A Mac or Windows laptop or desktop compatible with one of the following tested and supported browsers:–Google Chrome 48 or later–Microsoft Internet Explorer 11 (No plug-ins are required.)–Mozilla Firefox ESR 38–Mozilla Firefox 44 or later.Display resolution—Prime Infrastructure supports 1366 x 768 or higher, but we recommend that you set the screen resolution to 1600 x 900. Events Sustained Rate (events per second; includes syslogs, traps, and system events)001000Syslog Rate600Trap Rate00System Event Rate0NetFlow Rate (flows per second),0,000Supported Hourly Host Records144,0,100,0006,000,00012,000,000Interfaces12,50,050,000NAM Data Polling Enabled55203040Polling Interfaces (polling of trunk ports),000,000Number of Sites/Campus25002500Groups: User-Defined + Out of the Box + Device Groups + Port Groups0150Virtual Domains50750Concurrent GUI Clients510255050Concurrent API (or northbound interface) Clients22555. 2.Compliance is supported on the Professional virtual appliance (OVA) and the Gen 2, UCS-based physical appliance only. It is not supported on: Express, Express Plus, or Standard OVAs; OVAs that have been resized to Professional; Gen 1 physical appliances. If you are running Prime Infrastructure on an unsupported OVA or physical appliance and want to enable Compliance, you must perform a fresh install of the 3.1 Professional OVA or Gen2 UCS appliance, then use backup/restore to migrate data from your old server to the new server. Scaling for Operations CenterWhen using Operations Center, we recommend that you:.Use the Standard OVA installation option.Ensure that your network is providing the following performance levels between Operations Center and its managed devices:–Bandwidth—250 Kbps–Latency—up to 5 ms.
This is not a hard requirement, but Operations Center will only be as fast as its slowest managed instance. The higher the latency, the slower the overall performance.
Use the Network Latency column on the Operations Center Manage & Monitor Servers page to spot managed instances that may be acting as bottlenecks.Ensure all instances managed by Operations Center are running Prime Infrastructure 3.1. To allow management of 3.0 instances, an Operations-Center-enabled patch needs to be installed on the Prime Infrastructure instances and restarted. To obtain this patch, please reach out to the following mailing alias:[email protected] help you roll out new versions of Prime Infrastructure at your own pace, Operations Center always supports management of instances of both the current and the very last version of Prime Infrastructure (also known as “N-1 management”). For example: If you upgrade your Operations Center management server to 3.1, you can use that server to continue managing Prime Infrastructure 3.0 instances, as well as upgraded 3.1 Prime Infrastructure instances.Make sure that you do the following when you are upgrading the Operations Center:.Remove the managed instances before upgrading the Operation Center.Upgrade the Operation Center.Re-add the managed instances.lists the Operations Center scaling parameters.
Hardware Appliance (Gen 2)CoreConv50 MB50 MB50 MB50 MB45 GBARTCltSvr50 MB50 MB50 MB50 MB40GBCustom NetFLow (per CDB created by user)00 MB. no. Of custom cdbs created00 MB.
no. Of custom cdbs created00 MB. no. Of custom cdbs created00 MB. no.
Of custom cdbs created5 GB. no.
Of custom cdbs createdDisk Space used by Other CDBs3 GB approximately3 GB approximately3 GB approximately6 GB approximately10 GB approximately. Before You Begin Installation on a Virtual MachineBefore installing Prime Infrastructure on a virtual machine, you must:.Ensure that VMware ESXi is installed and configured on the machine that you plan to use as the Prime Infrastructure server. See thefor information on setting up and configuring a VMware host. If you are using VMware ESX 5.5, you must use vSphere Client or ESX5.5U2 (or later) Client to manage the virtual machine. Do not edit the virtual machine settings and do not extend or manually add additional disks to the configuration.Check that the installed VMware ESXi host is reachable. See the VMware documentation on how to install the VMware vSphere Client. After the virtual host is available on the network, you can browse to its IP address to display a web-based interface from which you can install the VMware vSphere Client.Ensure that the Prime Infrastructure OVA is saved to the same machine where your VMware vSphere Client is installed.
Depending on your arrangement with Cisco, you may download the OVA file from Cisco.com or use your Cisco-supplied installation media. NoteWe recommend you reserve 100% of CPU and memory resources for optimal performance.Step 9ClickNext.Step 10In the Host/Cluster window, select the host or cluster on which you want to deploy the OVF template, then clickNext. (If the vSphere Client is connected directly to an ESXi host, this option does not appear.)Step 11In the Storage window, select the datastore that has the required space requirements described in, then clickNext.Step 12In the Disk Format window, selectThick Provision Lazy Zeroedto provision the virtual machine virtual disks, then clickNext. Do not select Thin Provision because if there is no free disk space when the virtual machine needs it, Prime Infrastructure will fail.Step 13In the Network Mapping window, select a network for the virtual machine to use, then clickNext.Step 14In the Ready to Complete window, review your settings, selectPower on After Deployment, then click Finish.Depending on your network speed and the IOPS of the server, the deployment can take a few minutes to complete. Setting Up Prime Infrastructure on a Virtual Machine or Physical AppliancePrime Infrastructure comes preinstalled on physical appliances, or you can install an image on an existing appliance.
TipKeep your Prime Infrastructure password in a safe place. If you forget the password, see in the.Step 5When you are done entering these values, the installer application tests the network configuration parameters that you entered. If the tests are successful, it begins installing Prime Infrastructure.Step 6When the application installation is complete, you will be prompted for the following post-installation parameters:.High Availability Role Selection—Enteryesat the prompt if you want this installed server to serve as the secondary server in a high availability implementation. You will be prompted to provide an authentication key to be used for high availability registration.
If you enternoat the prompt, the server will act as the primary server (standalone) and the installation will proceed with the following prompts:.Web Interface Root Password—Enter and confirm the password used for the default root administrator. This is the account used to log in to the Prime Infrastructure web user interface for the first time and set up other user accounts.Step 7SelectYesto proceed with the installation, or selectNoto re-enter high availability options.Step 8When the installation is complete, the appliance reboots and you are presented with a login prompt.Step 9Log in to the virtual machine using the “admin” username and password that you specified in Step 4.Step 10Run thencs statuscommand (seein the) to verify that the processes have restarted. You should see the following process statuses:.All Processes are up and running. Performing an Inline UpgradeInline upgrade is simpler than system migration, and requires no new hardware.
Prime Infrastructure 3.1 does not support inline upgrade from Prime Infrastructure 3.0.x secondary server. Replace the existing secondary server with a fresh installation of secondary Prime Infrastructure 3.1 and integrate it with the primary server for high availability.
For details, see.The following steps explain how to upgrade from Prime Infrastructure 3.0.x to Prime Infrastructure 3.1.Step 1If you have not already done so: Set up a remote backup repository for the Prime Infrastructure version you are currently running. For details, seein the.Step 2Take an application backup of the Prime Infrastructure version you are currently running, and store the backup in the remote repository. For details, seein the.Step 3Verify the integrity of the backup as explained in.Step 4Remove any existing High Availability configuration from your primary Prime Infrastructure server. You can do this using either of the following options:.Launch Prime Infrastructure, chooseAdministration Settings High Availability HA Configuration, and clickRemove. Ensure the configuration mode changes to “HA Not Configured.”.Ensure the primary server is the active Prime Infrastructure server, go to the admin console on the primary server and run thencs ha removecommand.Step 5Move backup files (all files with the.tar.gpg extension) from the /localdisk directory to another server and ensure that /localdisk has 80% free space.
For details, seeandin theCommand Reference Guide for Cisco Prime Infrastructure 3.1.Step 6Download the PI-Upgrade-3.0.Xto3.1.0.0.xxx.tar.gz file from Cisco.com and verify the integrity using the checksum listed for it on Cisco.com.Step 7Copy the verified upgrade file to the default repository. Where:.sourceis the upgrade file’s URL, path and filename (for example: FTP:///PI-Upgrade-3.0.Xto3.1.0.0.xxx.tar.gz).diskis the disk and path to the local defaultRepo.Step 8Ensure the current version of Prime Infrastructure is 3.0.x.Step 9Ensure the local repository (defaultRepo) contains no backup files.Step 10Stop the Prime Infrastructure server by entering the commandncs stop.Step 11Run the application upgrade from the console. For a virtual appliance, you can run the application upgrade from the VM console. For a physical appliance, you can run the application upgrade from the KVM, VGA, or serial console. (If you are using the serial console, make sure baud rate is configured to 9600. Before You Migrate Your DataYou should check the validity of your Prime Infrastructure backup data by setting up an additional Prime Infrastructure server (either a spare Prime Infrastructure appliance or a new Prime Infrastructure virtual machine) and perform the restore operation as explained inin theCisco Prime Infrastructure 3.1 Administrator Guide.
If you do not have an additional Prime Infrastructure system to validate the backup, take at least two backups to reduce the risk of losing data.If the restore operation does not work, or there are problems with the backed up image, try taking another backup from a production system, or try restoring from an earlier Prime Infrastructure backup.If you cannot create a verified backup before installing this version of Prime Infrastructure, open a support case with Cisco TAC. Migrating Data From Previous Releases of Prime InfrastructureIf you are running multiple previous releases of Prime Infrastructure (for example, you are running version 3.0 and 3.0.1 or 3.0.3), you must selectoneversion from which to restore data. You cannot restore data from more than one Prime Infrastructure version. To combine data from multiple Prime Infrastructure versions:1.Perform the restore operation for one Prime Infrastructure system running a previous Prime Infrastructure version.2.Export your device inventory and maps from other Prime Infrastructure systems and import the information into the Prime Infrastructure 3.1 system.Seebefore you start the following steps to restore your data from Prime Infrastructure 3.0.x to your newly installed Prime Infrastructure 3.1 server:Step 1Configure the new Prime Infrastructure host to use the same remote backup repository as the old host.
For details, seein the.Step 2Restore the application backup on the remote repository to the new host, as explained inin the.Step 3When the process is complete:.Instruct users to clear the browser cache on all client machines that accessed an older version of Prime Infrastructure before they try to connect to the upgraded Prime Infrastructure server.If you are using Prime Infrastructure to manage Cisco Wireless LAN Controllers, see.Synchronize your devices as explained inin the.Step 4After the new Prime Infrastructure 3.1 server is operational, decommission your previous server. Assurance Data after MigrationAfter restoring Prime Infrastructure 3.0.x on a new Prime Infrastructure 3.1 virtual machine or hardware appliance, your Assurance license is automatically applied to the new server.When you move your data to Prime Infrastructure 3.1, the following Assurance data is not migrated:.Raw NetFlow information.Custom NetFlow reports.Packet capture files.Processed non-aggregated data, such as PFR data and URLs5-minute, 1-hour, and 1-day aggregated data is migrated from Prime Infrastructure 3.0.x to 3.1.
Resynchronizing WLC Configurations after MigrationAfter you restore the backup of the previous version on the 3.0.x version of Prime Infrastructure, your server’s records of Cisco Wireless LAN Controller configurations might be out of sync with the configurations stored on those devices. Resynchronize them using the following steps before continuing.Step 1Log in to Prime Infrastructure.Step 2ChooseInventory Network Devices Wireless Controller.
Prime Infrastructure displays a list of all the controllers it is managing, including all Cisco WLCs.Step 3Select a device, then clickSync.Step 4Repeat steps 2 and 3 for all your other WLCs. Logging in to the Prime Infrastructure User InterfaceWe strongly recommend you use signed certificates to ensure secure connections between clients and the Prime Infrastructure server. For information about creating a signed certificate, seein the.Follow these steps to log in to the Prime Infrastructure user interface through a web browser:Step 1Launch one of the Supported Browsers (see) on a different computer from the one on which you installed and started Prime Infrastructure.Step 2In the browser’s address line, enterthe IP address of the server on which you installed Prime Infrastructure.
The Prime Infrastructure user interface displays theLoginwindow.When you access Prime Infrastructure for the first time, some browsers will display a warning that the site is untrusted. When this happens, follow the prompts to add a security exception and download the self-signed certificate from the Prime Infrastructure server. After you complete this procedure, the browser will accept the Prime Infrastructure server as a trusted site in all future login attempts.Step 3Enter therootadministrator username and password, as specified when.Step 4Click Login to log in to Prime Infrastructure. The user interface is now active and available for use. The home page appears.If any licensing problems occur, a message appears in an alert box. If you have an evaluation license, the number of days until the license expires is shown. You are also alerted to any expired licenses.
You have the option to go directly to theAdministration Licensespage to address these problems.Step 5To ensure system security, chooseAdministration Users, Roles & AAA Change Passwordto change the password for the root administrator.To exit the user interface, close the browser page or clickLogoutin the top-right corner of the page. Exiting a Prime Infrastructure user interface session does not shut down Prime Infrastructure on the server.If a system administrator stops the Prime Infrastructure server during your Prime Infrastructure user interface session, your session ends, and the browser displays this message: “The page cannot be displayed.” Your session does not re-associate to Prime Infrastructure when the server restarts. You must start a new Prime Infrastructure session. Getting Started Using Prime InfrastructureAfter you install Prime Infrastructure, you must perform additional tasks to begin managing your network.
If you are an administrator, see the following sections in the Administrator Setup Tasks in the., including enabling NetFlow and Performance Agent.on Prime Infrastructure servers.For information about installing the Cisco Plug and Play Application, see the.Users should complete the tasks listed in the “Getting Started” chapter of the.After you complete these tasks, you are ready to start monitoring and configuring your network. Removing the Prime Infrastructure Virtual ApplianceRemoving Prime Infrastructure using the following method will permanently delete all data on the server, including server settings and local backups. You will be unable to restore your data unless you have a remote backup.
![Cisco Prime Infrastructure Ova Download Free Cisco Prime Infrastructure Ova Download Free](/uploads/1/2/5/6/125621605/833843589.jpg)
For other methods of removal, seein the.Step 1In the VMware vSphere client, right-click the Prime Infrastructure virtual appliance.Step 2Power off the virtual appliance.Step 3ClickDelete from Diskto remove the Prime Infrastructure virtual appliance. Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional information, see the monthlyWhat’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:Subscribe to theWhat’s New in Cisco Product Documentationas an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.