Upgrading IAM Stuck On Third Package

|
  • 190
  • 8

Issue Description

Customer feedback that when upgrading IAM the third package has been stuck in the upgrade for more than an hour.

Handling Process

(Describe the analysis and diagnosis process in a well-organized and logical sequence. This field is mandatory.)
1. Check the upgrade client, no error, still in connection status, not device unconnected status
2. Ping device IP, telnet IAMIP 51111 and 22345 ports are not available.
3. Directly connect to device management port, found that the device’s return route to the internal network is gone, communicate with the customer and found that it is an OSPF dynamic routing environment.
4. Manually write the static route to specify the down link core switch and re-upgrade it, or re-upgrade using the management port.

Root Cause

When upgrading under OSPF dynamic routing environment, yhe OSPF neighbor relationship fails to be establish. As a result, the upgrade package fails to be loaded.

Solution

Unstable environments such as VPN environment, public network environment, and dynamic routing are not recommended for upgrade. The risk is relatively high. It is recommended to upgrade under stable intranet environment.
Surbakti Lv3Posted 12 Apr 2020 18:08
  
simple solution
Yanto Peong Lv3Posted 12 Apr 2020 18:09
  
good solution
amad Lv3Posted 12 Apr 2020 18:10
  
great solution
Faisal Posted 11 Aug 2020 13:34
  
Thank you very much for the information ...
Faisal Posted 01 Nov 2020 16:27
  
Nice article ...
Faisal Posted 07 Dec 2020 06:39
  
Great Info
Faisal Posted 07 Mar 2021 08:59
  
Very informative …
Faisal Posted 26 May 2021 08:46
  
Nice guidance ...

I want to write a case
Doc ID: 2674
Author: Siva
Updated: 2019-12-24 14:06
Version: