Cisco Cisco Prime Infrastructure 3.0 Notas de publicación
10
Cisco Prime Infrastructure 3.0 Release Notes
Important Notes
•
NetFlow data from Cisco Adaptive Security Appliance (ASA) is not supported in this release of Prime Infrastructure.
•
If your browser prompts you to save your password, make sure click no and do not allow the browser to save any passwords.
If necessary, disable the password save option in your browser.
If necessary, disable the password save option in your browser.
•
While accessing Prime Infrastructure server using Internet Explorer 11, if you are unable to view buttons like Cancel, OK
delete the Temporary Internet files and Website files using the Delete Browsing History option in Internet Options.
delete the Temporary Internet files and Website files using the Delete Browsing History option in Internet Options.
•
Mozilla Firefox (version 35 or later) will abort or timeout the HTTP request which takes more than 300 seconds (5 minutes)
to get a response. This is to avoid unnecessary/unwanted TCP connections.
to get a response. This is to avoid unnecessary/unwanted TCP connections.
The preference used to timeout the request is “network.http.response.timeout”. Follow the steps below to modify the
preference value.
preference value.
–
Open a new tab.
–
Type about:config
–
Click I'll be careful, I promise! when you see a warning message. It loads the Firefox preference page.
–
In the search bar, type network.http.response.timeout.
–
Double click the preference, it will pop-up a dialog to change the value. Enter 0 and click OK.
The changes will take effect immediately.
•
The advance search returns correct search results only when you enter complete IPv6 address. The advance search options
do not work correctly if you enter partial IP address (that is, wildcard search) for IPv6 address.
do not work correctly if you enter partial IP address (that is, wildcard search) for IPv6 address.
•
The average memory utilization for Cisco 4500 controller is calculated using the average of two CLI outputs “show
memory location active and show memory location active-dc”.
memory location active and show memory location active-dc”.
•
In SWIM, the flash location of WLC is updated as “Not Applicable” as the flash details could not be collected during
inventory.
inventory.
•
When a WLC is added to Prime Infrastructure, the Prime Infrastructure will be automatically registered as trap receiver on
the WLC. If Prime Infrastructure fails to register as a trap receiver, the controller status task will try to register the Prime
Infrastructure IP Address as a trap receiver on WLC during polling. This would enable Prime Infrastructure to receive all
the traps raised by WLC.
the WLC. If Prime Infrastructure fails to register as a trap receiver, the controller status task will try to register the Prime
Infrastructure IP Address as a trap receiver on WLC during polling. This would enable Prime Infrastructure to receive all
the traps raised by WLC.
•
Switch Port Tracing is supported on Cisco Ethernet switches and the following Catalyst switches: 2960, 3560, 3560-E,
3750-E, 3850, and 4500 series.
3750-E, 3850, and 4500 series.
•
To increase the number of VLANs for which the client summary report can be generated, follow these steps:
–
Login to Prime Infrastructure Console.
–
Switch to root user.
–
Use the following File editor command:
VIM/opt/CSCOlumos/conf/rfm/classes/com/cisco/server/resources/ReportResources.properties.
–
Change the value of “key ClientSummary.MaxKeys” to required value. The default value is 20.
–
Restart the server.
•
While migrating to a new Mobility Controller (MC), the Cisco Prime Infrastructure may delete the Mobility Agent (MA)
Switch Peer Group (SPG) configuration on the new MC. This happens when both the MCs have the following configuration
preset value and are connected to the same Cisco Prime Infrastructure:
Switch Peer Group (SPG) configuration on the new MC. This happens when both the MCs have the following configuration
preset value and are connected to the same Cisco Prime Infrastructure:
wireless mobility controller peer-group SPG1 member ip 10.10.10.1 public-ip
10.10.10.1
–
The workaround is to remove wireless mobility controller peer-group SPG1 member ip
10.10.10.1 public-ip 10.10.10.1
10.10.10.1 public-ip 10.10.10.1
configuration from MC1 before adding it to MC2.