Skip to main content

Posts

Cisco Nexus 3000 can not upgrade because not enough space

Upgrade: nxos.7.0.3.I2.3.bin to  nxos.7.0.3.I7.6.bin Problem: NEXUS 3000  can not upgrade because not enough space Work around:   reload the nexus, enter ctrl-L enter loader> loader> boot usb1:nxos.7.0.3.I7.6.bin after it loaded delete old nxos on the bootflash copy new ios from usb1:nxos.7.0.3.I7.6.bin to bootflash: switch# install all nxos bootflash:<nxos-image-name> switch# install all nxos bootflash:  nxos.7.0.3.I7.6.bin    
Recent posts

Cisco UCS C Rack version CIMC issue with adobe flash player end of life

  Issue: can not open CIMC in the browser due to Adobe Flash no longer supported it affecting firmware ver 2.x Workaround: Uninstall current flash and Firefox, use flash_player 22.exe with Firefox ver 45 You can download it from here  https://drive.google.com/drive/folders/1oSoNuoCevCx00tQfT0eJLwaBEegmWJwE next step:  upgrade the firmware to ver3.x above NOTE: 2.0.4c and above you should be able to upgrade to 3.0.3f or 3.0.4 easily then you can goto 4.0 or 4.1 as required Don't upgrade to 3.0.3a, this version have a bug ver 3.x above using HTML5 After firmware upgraded: you need to download and install the latest Firefox that support HTML5 Firmware upgrade matrix https://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/c/sw/CIMC-Upgrade-Downgrade-Matrix/index.html =============================================================== Workaround 2: Run power shell script on FE laptop: Change IP, username and password on the script, before you run it Script: $cimcIP = &

New Catalyst 3850 can not join the stack, it show Lic_Mismatch

  New Catalyst 3850 can not join the stack, it show Lic_Mismatch Catalyst 3850 stackable with different License Levels? show license right-to-use default show license right-to-use summary How to Configure RTU Licenses Activating an Imaged Based License SUMMARY STEPS 1. license right-to-use activate{ipbase |ipservices | lanbase} {all | evaluation all } [slot slot-number] [ acceptEULA] 2. reload [ LINE | at | cancel | in | slot stack-member-number | standby-cpu ] 3. show license right-to-use usage [ slot slot-number ] DETAILED STEPS Command or Action Purpose Activates a type of image based license. Activation can happen on all license right-to-use activate{ipbase |ipservices | lanbase} {all | evaluation all } [slot slot-number] [ acceptEULA] Step 1 switches and also include the EULA acceptance. Example: Switch# license right-to-use activate ipservices all acceptEULA OR Example: Switch# license right-to-use activate ipbase all acceptEULA Switch# license right-to-use activate lanbase all a

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

Cisco FI Recovery

  Pre-troubleshooting checks: 1. Check Cluster State Central-BLRQA-Mini-10-B# show cluster state Cluster Id: 0xb1125e5643ad11e0-0x921574a02f402f50 B: UP, SUBORDINATE A: UNRESPONSIVE, PRIMARY HA NOT READY 2. Check f/w versions on active node(if any) Central-BLRQA-Mini-10-B# sh version System version: 3.1(0.297c) Central-BLRQA-Mini-10-B# show fabric-interconnect a detail Central-BLRQA-Mini-10-B# show fabric-in
  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 required

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: loader> boot tftp://10.104.10