Cisco Cisco Prime Infrastructure 3.0 Notas de publicación

 lists the Open Caveats in Cisco Prime Infrastructure Release 3.0.

Click the identifier to view the impact and workaround for the caveat. This information is displayed in the Bug Search Tool. 
You can track the status of the open caveats using the

While viewing client details, there are discrepancies in the VLAN ID and association ID, and clients 
statistics data is not shown in Operations Center.

Configuring the 802.11ac Radio status from the Lightweight AP template on AP 3600 with RM3000AC 
module shows the result as “Not Applicable.”

Controller names are missing in the Mobility Configuration page for IPV6 group members. 

Need to enhance manual SPT algorithm to handle trunk port discovery cases

Discrepancy between EOS dates displayed in Prime Infrastructure 3.0 PSIRT and EOS reports when 
compared with the dates on cisco.com.

Wireless deployed devices are not displayed with group name.

Sysname under Neighbors in 360 view for all devices is N/A.

Even when a virtual domain is associated to a user, it can be deleted in the Virtual Domain page.

When using Plug and Play, if you define a configuration template with an SSH configuration, Plug and 
Play might fail with an error message.

You cannot filter port groups according to speed rules you specified. 

In Operations Center, quick search of IPv6 for Clients and Users does not work.

Health Monitor page displays an error indicated the data replication operation failed abnormally. 

Double quotes value check are not accepted for audit if custom policies are created with “condition and 
actions” value field.

Wireless Clients might not be found if the Wireless Client filter is narrowed down to a specific client 
username or MAC address.

Alarms generated from MSE during MSE High Availability failover and failback are not sent as email 
notifications.

Filtering doesn't work on compliance jobs.

Inventory collection displays partial collection failure for particular devices.

When verifying the credentials for NAM, verification fails even when specifying the correct credentials.

When a configuration template that has a TACACS configuration is used as a configuration template in 
a Plug and Play profile in APIC-EM mode, an error message appears.

Bulk select on severity configuration and alarm auto clear is not working.

Inventory collection sometimes fails for devices using IPv6.

ICMP Reachability Metric Dashlet Count mismatch.

Creating a policy with multiple lines in the Condition Details field results in a “Policy did not compile 
successfully” error. 

Primary server start-up takes 40 minutes and startup time-out occurs after 30 minutes.