Cisco Cisco Prime Network Services Controller 3.0

 lists open bugs in Prime Network Services Controller 3.0.

The following Prime Network Services Controller documentation is available for this release:

Cisco Prime Network Services Controller 3.0 XML API Guide 

Moving a Windows VMDK from the enterprise to the cloud includes only actual interfaces configured in the 
VM.

InterCloud Switch and InterCloud Extender enter lost-visibility state if their hostnames are changed in Prime 
Network Services Controller.

If you edit the InterCloud Extender so that it points to a new ESXi host on a new vCenter, deployment of the 
InterCloud Extender fails.

One port ID is lost whenever the creation of a VM fails.

Editing the management IP address of an InterCloud Extender after the Extender is deployed stops the 
deployment.

Migrating a Linux VM fails with a vmware-mount error.

If you create a VSM port profile that is configured with an organization and then create a cloud VM using 
that port profile, incomplete information for that port profile is displayed when you view the properties for 
the VSM or cloud VM in Resource Management > Resources.

If a DNS server is not configured, VM Manager process fails.

Windows registry entries for NICs are displayed in random order.

The MAC address pool is not replenished when a cloud VM is terminated.

The access tunnel is up in the InterCloud Switch, but it is displayed as down in the GUI.

The InterCloud Agent Image URL www.cisco.com/go/network-controller that is noted in the GUI, results in 
a 404 error on cisco.com. The URL should be

Prime Network Services Controller fails to open known_hosts file during InterCloud link creation. 

VSG is missing some or all protected virtual machines (VMs) and thus dropping all traffic for those VMs.