Skip to main content

UCS-FI-6296UP Issue: need to upgrade to ver 4.1(1d)A New unit have version 2.1(3a)

 




PID: UCS-FI-6296UP

Issue: need to upgrade to ver 4.1(1d)A

New unit have version 2.1(3a)

According to upgrade matrix, it needs to upgrade to 2.2(8m) first

Via GUI

While login in, having issue with authentication  

Java issue

Login Error: java.io.IOException: Invalid Http response

Login Error: java.io.IOException: Server returned HTTP response code: 400 for URL

( Java issue )

Workaround: Rollback Java 7 to Update 25 or lower

Uninstall others java version

Login is working now

Upgrading to 2.2(8m)

Upload, activated

Upgrading ver 4.1(1d)A

Upload, activated

Erase config

Rack4-A# show version

System version: 2.0(1w)

Rack4-A# connect local-mgmt

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained in this software are

owned by other third parties and used and distributed under

license. Certain components of this software are licensed under

the GNU General Public License (GPL) version 2.0 or the GNU

Lesser General Public License (LGPL) Version 2.1. A copy of each

such license is available at

http://www.opensource.org/licenses/gpl-2.0.php and

http://www.opensource.org/licenses/lgpl-2.1.php

 

Rack4-A(local-mgmt)# erase configuration

All UCS configurations will be erased and system will reboot. Are you sure? (yes/no):yes

Removing all the configuration. Please wait....

/bin/rm: cannot remove directory `/bootflash/sysdebug//tftpd_logs': Device or resource busy

Configurations are cleaned up. Rebooting....

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

FI is ready with 4.1(1d)A

Comments

Popular posts from this blog

Recovering Fabric Interconnects When You Do Not Have Working Images on The Fabric Interconnect or The Bootflash

  Recovering Fabric Interconnects When You Do Not Have Working Images on The Fabric Interconnect or The Bootflash You can perform these steps when both or any fabric interconnect goes down during firmware upgrade, gets rebooted, and is stuck at the loader prompt, and you do not have working images on the fabric interconnect. Procedure Step 1 Reboot the switch, and in the console, press  Ctrl+L  as it boots to get the loader prompt. Note   You may need to press the selected key combination multiple times before your screen displays the loader prompt. Example: loader> Step 2 Configure the interface to receive the kickstart image through TFTP. Enter the local IP address and subnet mask for the system at the loader> prompt, and press  Enter . Example: loader> set ip 10.104.105.136 255.255.255.0 Specify the IP address of the default gateway. Example: loader> set gw 10.104.105.1 Boot the kickstart image file from the required server. Example...

Upgrade Software On A Cisco Catalyst 3850 Series Switch Stack

  Upgrade Software On A Cisco Catalyst 3850 Series Switch Stack Set a new SW#1 as stand alone copy bin file using usb copy usbflash0:xxxxx.bin flash: New-SW01#request platform software package install switch all file flash:cat3k_caa-universalk9ldpe .16 .03 .08 .SPA.bin new auto-copy New-SW01#reload New-SW01# request platform software package clean connect the stack cable
  Upgrading an Old Nexus 3048 to Current NX-OS Posted on 2018/11/16 Yeah, I know. I’m supposed to be a Wi-Fi guy. However, I sometimes still have to touch routers and switches. I have some help for you if you need to upgrade some old Nexus switches. The Nexus 3048s are great DC caliber gig switches with proper front-to-back airflow. Used ones are really cheap and I think they make great management switches, which is what I’m using them for. If you have a Cisco Nexus 3048 with an older release of NX-OS on it, you need to go through several upgrades to get it to NX-OS v7. Here’s a walkthrough on the procedures. If you find you already on v6, for example, you can skip the 5.x step. Upon initial boot, you will need to abort Power-On Auto Provisioning. You will then be prompted for the admin password. Skip the basic configuration dialog. After a few moments, you will be able to login with the admin credentials you set during boot. I suggest downloading all the requ...