Guest

Preview Tool

Cisco Bug: CSCum42101 - Last communication error after using wrong image type for Netscaler1000v

Last Modified

Jul 08, 2019

Products (1)

  • Cisco Virtual Network Management Center

Known Affected Releases

3.2 3.2(2.0)

Description (partial)

Symptom:
The error arises when a wrong Service image is used to deploy from PNSC. Since PNSC doesn't probe Service Images, user has to import/use the correct image for deployment.

Conditions:
If a user imports a wrong image and user it to deploy an end-point (for Ex: VPX), PNSC becomes unresponsive, and so the user has to be careful enough to import the correct image.

One specific example of this is the Netscaler1000v 10.1 image, which, is downloaded as a zip archive containing two different image files corresponding the different vCenter host types. For example:
-bash-3.2$ unzip NS1000V.10.1.zip
Archive:  NS1000V.10.1.zip
 extracting: NetScaler1000V-ESX-10.1-120.17_nc.zip
  inflating: NetScaler1000V-NEXUS-10.1-120.17_nc.ova

The two image types correspond to the ESX/ESXi hosts and the Cisco Nexus platforms such as  Nexus 1010, correspondingly.

PNSC 3.2 only supports the Netscaler1000v on the ESX/ESXi hosts, and use of the nexus-based OVA file could cause this issue.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.