This post is more than 5 years old
12 Posts
0
1314
Issues with 9222i Upgrade
Hi All,
Today I upgraded a 9222i from 3.2.3a to 3.3.3 and facing the following issue.
When the switch went for the reboot finallly, it never came back. I mean all fc ports had come up....but the mgmt and console ports weren't coming up and so we had to do a reboot of the switch after which the mgmt port came online back....
When I do a 'sh version' / 'sh module' , it shows the version as 3.3.3 which is what I expected. However when I do a 'sh install all status' it gives me the following log. Could anyone explain and help me understand this ? Do I need to run a 'install all' again ?
xxxxxxxxx# sh install all status
This is the log of last installation.
Need to perform cleanup of failed upgrade.
Install has failed. Return code 0x40930039 (aborting due to failed upgrade).
Please identify the cause of the failure, and try 'install all' again.
Today I upgraded a 9222i from 3.2.3a to 3.3.3 and facing the following issue.
When the switch went for the reboot finallly, it never came back. I mean all fc ports had come up....but the mgmt and console ports weren't coming up and so we had to do a reboot of the switch after which the mgmt port came online back....
When I do a 'sh version' / 'sh module' , it shows the version as 3.3.3 which is what I expected. However when I do a 'sh install all status' it gives me the following log. Could anyone explain and help me understand this ? Do I need to run a 'install all' again ?
xxxxxxxxx# sh install all status
This is the log of last installation.
Need to perform cleanup of failed upgrade.
Install has failed. Return code 0x40930039 (aborting due to failed upgrade).
Please identify the cause of the failure, and try 'install all' again.
healyj
141 Posts
0
November 28th, 2017 07:00
Hi there,
In our efforts to clean up the forum, we came across your question / statement.
If the question / statement is still valid, not expired and you need an update please reach out again and we try to get it answered.
As for now we set it to “answered.”
Regards,
Jim
ironcheflouie
76 Posts
0
October 13th, 2009 18:00
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
March 22nd, 2014 02:00
I'm upgrading from 5.0(4) to 5.2(8c) on a 9222i and I'm seeing the exact same thing. But I did not loose mgmt connectivity.
So what was the outcome of your support call with EMC or Cisco? I'm facing the same thing and I'm wondering whether or not my switch is ok. It seems ok though.
RRR
1 Rookie
1 Rookie
•
5.7K Posts
1
April 1st, 2014 05:00
I had EMC/Cisco take a look and it turned out that we used to have a VSAN in interop mode once upon a time and even though the VSAN was gone, some counter was still there somewhere, which caused the crash / core dump (twice). The workaround would be to recreate the VSAN that we used to have, do the upgrade and delete this VSAN again.
I think it's a bad solution since I cannot tell what VSAN we used to have in a random switch and especially when you're new at a company and you don't know its history.