Guest

Preview Tool

Cisco Bug: CSCut16609 - PN-no ability to upgrade 4.1/4.0 with 6.4 to 4.2 (6.5 OS)

Last Modified

Jun 10, 2015

Products (1)

  • Cisco Prime Network

Known Affected Releases

4.2(0.1)PP1

Description (partial)

Symptom:
No ability to upgrade PN 4.1/4.0 with 6.4 to 4.2 (6.5 OS)
In PN 4.2 Installation guide, Upgrading to Prime Network 4.2 from 4.0 and 4.1 (Pg no121), does not mention the Upgrade flow, when Upgrading a PN with 4.1 or 4.0  to PN 4.2  with RHEL 6.5 .

Conditions:
1) After taking the backup from 4.1pp4 PN (which was running in RHEL 6.4 ).
2) Same server, will be reimaged with RHEL 6.5. 
3) After that whether PN 4.2   has to be installaed in RHEL 6.5  or what will  be the prerequisite to upgrade PN 4.2 from PN 4.0/4.1 in RHEL 6.5. 
4) The upgrade instructions exist in the install guide do not take into consideration the need to have a clean 6.5 server- which ends in non existence PN user. This cause us to be stuck in step #4 in the upgrade flow:
Step 4 Give the Prime_Network_upgrade directory and its contents pn user: pn group owner permissions:
chown - R pnuser: pn group directory name
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.