Cisco Cisco Prime Infrastructure 2.0 Release Notes
6
Release Notes for Cisco Prime Infrastructure, Release 2.0
OL-27653-02
Important Notes
•
The Cisco Easy VPN Remote eliminates much of this tedious work by implementing Cisco Unity
Client Protocol, which allows most VPN parameters to be defined at a Cisco IOS Easy VPN server.
Client Protocol, which allows most VPN parameters to be defined at a Cisco IOS Easy VPN server.
•
The Interfaces feature helps in setting up physical and logical interfaces. Physical interfaces on a
device depend on the device type and its interface processors or port adapters.
device depend on the device type and its interface processors or port adapters.
•
Cisco AppNav, is a hardware and software solution that simplifies network integration of WAN
optimization. It also overcomes the challenges related to provisioning, visibility, scalability,
asymmetry, and high availability.
optimization. It also overcomes the challenges related to provisioning, visibility, scalability,
asymmetry, and high availability.
•
The Cisco Wide Area Application Services (Cisco WAAS) container is a powerful WAN
optimization acceleration solution
optimization acceleration solution
Important Notes
This section contains important notes about Cisco Prime Infrastructure.
•
If you have a large, dynamic network with a high range of roaming, some of the Prime Infrastructure
monitoring and configuring screens might show different data for the same devices. For some
monitoring screens, Prime Infrastructure displays data it retrieves directly from the devices. For
configuration screens, Prime Infrastructure polls the devices, and because polling takes longer
because of the network load, the configuration data might not refresh quickly. This limitation occurs
primarily on client management screens because of client roaming in wireless networks and the
increasing size and client density in such networks. Currently there is no workaround, but in
subsequent releases of Wireless Controller software and Prime Infrastructure, enhancements are
planned to improve data collection.
monitoring and configuring screens might show different data for the same devices. For some
monitoring screens, Prime Infrastructure displays data it retrieves directly from the devices. For
configuration screens, Prime Infrastructure polls the devices, and because polling takes longer
because of the network load, the configuration data might not refresh quickly. This limitation occurs
primarily on client management screens because of client roaming in wireless networks and the
increasing size and client density in such networks. Currently there is no workaround, but in
subsequent releases of Wireless Controller software and Prime Infrastructure, enhancements are
planned to improve data collection.
•
To reset the Prime Infrastructure server back to default factory settings, you must reinstall Prime
Infrastructure with the original software image.
Infrastructure with the original software image.
•
To completely erase all data from the Prime Infrastructure physical appliance (for example, if you
are disposing of the appliance and want to remove all data), follow these steps:
are disposing of the appliance and want to remove all data), follow these steps:
1.
During the Prime Infrastructure server boot sequence, press Ctrl-H when prompted to enter the
raid configuration screen.
raid configuration screen.
2.
Click on the virtual drive in the logical view.
3.
Select the slow init operation to erase all data from the Prime Infrastructure physical appliance
hard drive.
hard drive.
•
The CCX Client Statistics report does not contain client information from the Cisco 5760 Wireless
Controller and Cisco Catalyst 3850 Series Switches.
Controller and Cisco Catalyst 3850 Series Switches.
•
Client Statistics—You will notice that the client statistics data displayed in the CLI output and Prime
Infrastructure UI (in the Clients and Users page) are different. This is because the CLI output
displays the upstream (data sent to client) and downstream (data received from client) packet/byte
count from the AP’s point of view, whereas, the Prime Infrastructure UI displays the upstream (data
sent to AP and network) and downstream (data received from AP and network) packet/byte count
from client's point of view.
Infrastructure UI (in the Clients and Users page) are different. This is because the CLI output
displays the upstream (data sent to client) and downstream (data received from client) packet/byte
count from the AP’s point of view, whereas, the Prime Infrastructure UI displays the upstream (data
sent to AP and network) and downstream (data received from AP and network) packet/byte count
from client's point of view.
•
Support for Cisco 3850 and 5760 devices are available in the LifeCycle view only, that is, you can
use the Lifecycle view to configure and monitor Cisco 3850 and 5760 devices while you can use the
Classic view to manage the legacy controllers.
use the Lifecycle view to configure and monitor Cisco 3850 and 5760 devices while you can use the
Classic view to manage the legacy controllers.
•
The administrator should perform a “Refresh Config from Controller” or “Sync” operation for each
of the network devices in Prime Infrastructure after the devices are upgraded (or the version is
changed). Similarly, the administrator should perform a “Refresh Config from Controller” or “Sync”
of the network devices in Prime Infrastructure after the devices are upgraded (or the version is
changed). Similarly, the administrator should perform a “Refresh Config from Controller” or “Sync”