NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX

Hi All,
Please tell me how to do "NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX" without downtime for FEX.
The Server are connected to FEX.
Attached the diagram.

Hi,
If the 5500s are layer-2 with vPC running between them than you can use ISSU to upgade.
here is doc to follow:
ISSU Support for vPC Topologies
An ISSU is completely supported when two switches are paired in a vPC configuration. In a vPC configuration, one switch functions as a primary switch and the other functions as a secondary switch .They both run the complete switching control plane, but coordinate forwarding decisions to have optimal forwarding to devices at the other end of the vPC. Additionally, the two devices appear as a single device that supports EtherChannel (static and 802.3ad) and provide simultaneously data forwarding services to that device.
While upgrading devices in a vPC topology,you should start with the switch that is the primary switch. The vPC secondary device should be upgraded after the ISSU process completes successfully on the primary device. The two vPC devices continue their control plane communication during the entire ISSU process (except when the ISSU process resets the CPU of the switch being upgraded).
This example shows how to determine the vPC operational role of the switch:
link:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/upgrade/513_N1_1/n5k_upgrade_downgrade_513.html
HTH

Similar Messages

Enhanced vpc with ucs 6248up

I got 2 6248up FI going to 2 N7k.
can i stup enhanced vpc using both FI as active uplinks or can only 1 be active at one time?
in ucsm, I am only seeing 1 pot channel on fabric A - with 4 uplinks 17-20
but on fabric B i see 1 port channel with no links

If your FI's are in endhost mode, they should act like access ports and not disable a connectino via STP. If that is happening maybe you are in Switch mode?
Craig

Upgrading Nexus 5548 UP, Release 5.1(3)N2(1b)

Hi,
I try upgrading my Nexus 5548 with the release 5.1(3)N2(1b)
But I see that the image is'y not compatibible with the module 1 !!!
I followed the Upgrade and Downgrade Guide.
Help me.
********************************************** CLI output *************
sw-tdb-nx5548-1# show install all status
This is the log of last installation.
Verifying image bootflash:/n5000-uk9-kickstart.5.1.3.N2.1.bin for boot variable "kickstart".
SUCCESS
Verifying image bootflash:/n5000-uk9.5.1.3.N2.1b.bin for boot variable "system".
SUCCESS
Verifying image type.
SUCCESS
Extracting "system" version from image bootflash:/n5000-uk9.5.1.3.N2.1b.bin.
SUCCESS
Extracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.5.1.3.N2.1.bin.
SUCCESS
Extracting "bios" version from image bootflash:/n5000-uk9.5.1.3.N2.1b.bin.
SUCCESS
Extracting "fexth" version from image bootflash:/n5000-uk9.5.1.3.N2.1b.bin.
SUCCESS
Recommended action::
"Module 1 might not be supported in the new image,
it should be powered off before proceeding with install".
Performing module support checks.
SUCCESS
Notifying services about system upgrade.
SUCCESS
Compatibility check is done:
Module bootable          Impact Install-type Reason
     1        no             n/a           n/a Incompatible image
   101       yes non-disruptive       rolling
Images will be upgraded according to following table:
Module       Image         Running-Version             New-Version Upg-Required
     1      system             5.1(3)N2(1)            5.1(3)N2(1b)            no
     1   kickstart             5.1(3)N2(1)             5.1(3)N2(1)            no
     1        bios      v3.5.0(02/03/2011)      v3.5.0(02/03/2011)            no
     1      SFP-uC                v1.0.0.0                v1.0.0.0            no
   101       fexth             5.1(3)N2(1)            5.1(3)N2(1b)           yes
     1   power-seq                    v1.0                    v1.0            no
     3   power-seq                    v2.0                    v2.0            no
     1          uC                v1.2.0.1                v1.2.0.1            no
sw-tdb-nx5548-1#
sw-tdb-nx5548-1#
sw-tdb-nx5548-1#

I was using an bad command, the right one is:
install all kickstart bootflash:n5000-uk9-kickstart.5.1.3.N2.1b.bin system bootflash:n5000-uk9.5.1.3.N2.1b.bin
Now the Nexus is upgraded.
Regards

Vision M - no connection with firmware upgrade with WMP

Now I know there's been a lot of fuss about WMP and firmware upgrades but I've got a problem with WMP0! If I connect my Vision M to the computer within seconds the Media Explorer page comes up and I'm away - success. If I run the firmware upgrade (ZENVision_PCFW_L6__42_0.exe) it comes up and says player is not connected. If I re-connect, Media Explorer pops up again and says player is connected but the firmware upgrade exe is still saying the player is not connected. It doesn't matter how many times I disconnect and reconnect, the upgrade program does not recognise the player! I checked WMP and that is version 0. So is this an earlier problem that someone's got an answer to I don't think I'll go to WMP! My Zen is version .40.02 and I'm trying to upgrade to .42.0. Please help?Glazza

Perhaps the player is faulty? Try to contact CS and see what they have to say:
http://us.creative.com/support/

Firmware upgrade, then lost

Hi,
Quickly following automatic firmware upgrade on 1 week old Time capsule, network is now lost. Airport set up utility can't find Time Machine .. others experience the same problem? TM feels hot .. perhaps overheated due to firmware upgrade. Solutions welcome.

Your computer came with OS 9.0.4 installed. OS9.1 is required for Classic so is handy to have, and apparently your firmware installer requires 9.2.1 You can use free updaters to update to any later OS9 version from any earlier one.
I don't see any option but to obtain a used copy of OS9. Make sure you get the gold full retail version rather than a machine specific version since the latter will only work in those computers for which they were designed. You can get away with a machine specific version as long as it exactly corresponds to the model and build of yours, but that is often hard to confirm until too late in the purchase.
Note that any drive you want to use with OS9 either for purposes of installing OS9 or for running software will have to have OS9 drivers present on it. These are installed when you format a drive and cannot be installed later without reformatting the drive (and losing everything on it). If your computer still has its original drive then those will likely still be on there unless you reformatted the drive with OSX and did not select the keep OS9 drivers option (there's no harm in doing so and it saves a lot of trouble for doing exactly what you are trying to do). You can can have a drive present that doesn't have the drivers but it simply won't be seen by OS9.
Disconnect all third party hardware (including PCI cards) when updating the firmware.
Message was edited by: Limnos

Has the cloud firmware upgrade being fixed yet?

I am looking to buy a new router (E3200 or greater)
All the reviews are complaining about that specific firmware upgrade that users` have been forced to with the cloud thing.
Is this still in place/happening?

This issue was clarified in this site: http://blogs.cisco.com/home/update-answering-our-customers-questions-about-cisco-connect-cloud-2/. These are the items tackled in that blog: Linksys customers are not required to sign-up for the Cisco Connect Cloud service and they are able to opt-out of signing up for an account, Customers can set-up and manage their Linksys router without signing up for a Cisco Connect Cloud account, Cisco will not arbitrarily disconnect customers from the Cisco Connect Cloud service based on how they are using the Internet, Cisco Linksys routers are not used to collect information about Internet usage, Cisco only retains information that is necessary to sign up for and support the Cisco Connect Cloud service , Cisco will not push software updates to customers’ Linksys routers when the auto-update setting is turned off.

FCoE using Brocade cards CNA1020 and Cisco Nexus 5548 switches

All,
I have the following configuration and problem that I am not sure how to fix:
I have three Dell R910 servers with 1TB of memory and each has two brocade 1020 CNA cards dual port. I am using distributed switches for the VM network and a second distributed switch for VMotion. I have two of the 10G ports configured in each distributed switch using IP Hash. The management network is configured using a standard switch with two 1G ports.
The Nexus configuration is we have two nexus 5548 switch connected together with a trunk. We have two VPC's configured to each ESX hosts consisting of two 10gig ports in each VPC with one port going to each switch. The VPC is configured for static LAG.
What I am seeing is that after a few hours the virtual machines will not be accessible via network anymore. So if you ping the VM it will not work and if you get on the console of the VM then ping the gateway then nothing as well but if you try to ping another virtual machine on the same host on the same VLAN then it will work so traffic is going through the ESX backplane. If I reboot the ESX host then things will work again for another few hours or so then the problem repeats.
The version of vSphere I am using is ESXi4.1
Please assist I am stuck.
Thanks...

Here is the link for Nexus and Brocade interoperability Matrix
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix7.html#wp313498
usually this table would show those models those have been tested and verified
However I do not see Brocade 5300 listed in the table . It could be, interoperability may have not been tested by both vendors perticularly to 5300 type Model.

Nexus 5548 and Define static route to forward traffic to Catalyst 4500

Dear Experts,
Need your technical assistance for the Static routing in between Nexus 5548 and Catalyst 4500.
Further I connected both Nexus 5548 with Catalyst 4500 as individual trunk ports because there is HSRP on Catalyst 4500. So I just took 1 port from each nexus 5548, make it trunk with the Core Switch (Also make trunk from each Switch each port). Change the speed on Nexus to 1000 because other side on Catalyst 4500 line card is 1G RJ45.
*Here is the Config on Nexus 5548 to make port a Trunk:*
N5548-A/ N5548-B
Interface Ethernet1/3
Switchport mode trunk
Speed 1000
Added the static route on both nexus for Core HSRP IP: *ip route 0.0.0.0/0 10.10.150.39 (Virtual HSRP IP )*
But I could not able to ping from N5548 Console to core Switch IP of HSRP? Is there any further configuration to enable routing or ping?
Pleas suggest

Hello,
Please see attached config for both Nexus 5548. I dont have Catalyst 4500 but below is simple config what I applied:
Both Catalyst 4500
interface gig 3/48
switchport mode trunk
switchport trunk encap dot1q
On Nexus 5548 Port 1/3 is trunk
Thanks,
Jehan

Toshiba STOR.E TV+ firmware upgrade

Hello,
Is there any unofficial firmware upgrade for the STOR.E TV+ product series? I can clearly see that there's no official firmware upgrade...
The one shipping with the product looks like "work in progress" (you can see this throughout the entire user interface, which is clumsy and very "90s", but especially if you access the device using your browser - though this one could be useful if your math is rusty and need a little help to perform basic additions :) ).
Moreover, despite the fact that the product is on the market for over 1 year now, there's no firmware upgrade available (despite the obvious need for one). Sometimes I wonder when would have been the release date if the product's time to market would have been extended in order to have a fully functional product upon the release!
@ Toshiba developers: if you don't bother to release a firmware at least give the code "as is" to the community. This way you will certainly find someone willing to do (out of pure passion) whatever you were supposed to do (for the money you make as developers, part of those we pay for this product as customers).
Thanks.

Hi there,
As expected, the software is... archaic!
You can telnet into your box (user: root, no password required) and you'll see the software specs: it is based on BusyBox 1.1.3! There's nothing wrong with BusyBox (a Debian-based Linux distribution, originally intended to run from a single floppy disk, but now able to run to almost anything: phones, routers, NASs...), except for the version: 1.1.3 has been released on May 17, 2006! (Yes, it was already 4 years old when Toshiba decided to put the STOR.E TV+ on the market!).
The newest version is 1.19.3, released on October 29, 2011 (and, if you follow the release notes, there have been some tremendous improvements form 2006 to 2011!).
So.. Toshiba guys, when can we expect an update? (I sure would like to have a proof that you're actually working!)
It is certainly not enough to just throw an update to the CLI-based code; it must be linked to the remote and OSD as well (besides, since Toshiba is not mentioned in the products list on the BusyBox site, I don't expect them to have been used an open code). So just changing the routines, without changing the way they're called for, is useless, and could brick your product.

Upgrading Nexus 5548

Hi,
We want to upgrade our pair of Nexus 5548 to the new NX-OS 5.1(3)N2(1a) from the 5.0(3)N1(1c) version. We would like to use the ISSU procedure. But when we execute the command "show spannig-tree issu-impact" we get the following output:
No Active Topology change Found!
Criteria 1 PASSED !!
No Ports with BA Enabled Found!
Criteria 2 PASSED!!
List of all the Non-Edge Ports
Port VLAN Role Sts Tree Type Instance
Ethernet2/8 1803 Desg FWD PVRST 1803
The 1803 vlan is only used for the peer-keepalive link and it only exists on these two Nexus. So one of the two Nexus needs to be the STP root. That makes the ports on that vlan to be in designated-forwarding state, which is not supported for the ISSU:
sh run int e2/8
!Command: show running-config interface Ethernet2/8
!Time: Fri Jun 8 17:04:33 2012
version 5.0(3)N1(1c)
interface Ethernet2/8
switchport access vlan 1803
speed 1000
That is the only port that belongs to that VLAN and it is directly connected to the other Nexus 5548. So the only way we see to avoid this port of being in designated-forwarding state is to apply the "no spanning-tree vlan 1803" command. Would it be a problem?
We can imagine that introducing the "spanning-tree port type edge" should not be a good idea, shouldn´t it?
Thank you very much for your help!
Josu

Hi,
Reviewing all the prerequisites for the ISSU, we have seen the following:
SSU and Layer 3
Cisco Nexus 5500 Platform switches support Layer 3 functionality. However, the system cannot be upgraded with the ISSU process (non disruptive upgrade) when Layer 3 is enabled. It is required to unconfigure all Layer 3 features to be able to upgrade in a non disruptive way with an ISSU.
We have the interface-vlan feature enabled. But it is only used for two interfaces:
- interface-vlan 510 --> It is only used in order connect to the switch
- interface-vlan 1803 --> The one used for the keepalive
We could administratevely shutdown the interface-vlan 510. But we could not do so with the interface-vlan 1803, since it is used for the keepalive. If we execute "no feature interface-vlan", would the keepalive stop working?
When we execute "sh install all impact ..." command the Nexus does not tell anything about this feature. Is really recommended to disable it? Is it needed for the ISSU procedure?
Thank you very much in advance!!
JOSU

Sky Router firmware upgraded - can no longer login with credentials

I usually have no problems accessing my sky router (white Sky Hub with ADSL) via the page 192.168.0.1 however I tried to login the other day and was greeted with an updated looking summary screen - all very nice I thought, let's go and explore! However when I put in the usual details - username: admin, password: sky I get prompted to input my details again which is very odd. Now I know that I am the only one who accesses the router in this way as my flatmate has never logged in and probably never will so I can only assume the firmware upgrade has caused the password/username to change. I logged in the other week and the password is saved in my browser so I am sure I am not making any mistake here. I have tried in chrome and IE just in case but I have the same issue in both. Has the new firmware brought a new default password? I cannot find any reference to this anywhere on this site so it seems unlikely. I would rather not reset my router to default settings as I have devices with static IP addresses and port forwarding setup that will take me some time to reconfigure. I don't think there is any feature to backup the config unless you are actually logged in to the router but would love to be worng about this. I am guessing I will have to bite the bullet and reset to factory defaults but would welcome any help or suggestions if possible?

After review the events of the morning.....
I normally keep my routers in the basement where my eth jacks all hub. High on a shelf, I got reasonable coverage on 2.4Ghz even on the second floor. I went to this router for the Dual mode, but found the 5Ghz didn't make it sufficiently well to the second floor. So it was moved to the first floor, on a counter. That morning the router started acting up a bit, not bringing an iphone online. It was looked at - and a couple of post cards that had been placed on top, removed. Air flow was not blocked around the sides in any way - just a few pieces of card stock on top to interfere with convection off the top.
1. There is no way to look at temperature - maybe the device doesn't even know its own temp.
2. There is no fan that I can discern. Clearly, creating a device that is designed to sit on a flat surface in a home environment ought to take into consideration "normal impediments to air flow". Temp controlled fans is simple, well proven tech.
3. This design is small, has TWO radios, sits horizonal (thus is going to have lousy convection) - seems to me an engineer ought to have given more thought to not only providing the user with easy to obtain data (temp), alternative methods (fan/vertical mounting) and/or self-protection (to hot, I'm shutting down rather than corrupt my database).
Having spent millions on Cisco gear in my career, I would have hoped that Cisco+Linksys would have a little more Cisco and a little less Linksys.
me

FCoE with Cisco Nexus 5548 switches and VMware ESXi 4.1

Can someone share with me what needs to be setup on the Cisco Nexus side to work with VMware in the following scenario?
Two servers with two cards dual port FCoE cards with two ports connected to two Nexus 5548 switches that are clusterd together. We want to team the ports together on the VMware side using IP Hash so what should be done on the cisco side for this to work?
Thanks...

Andres,
The Cisco Road Map for the 5010 and 5020 doesn't include extending the current total (12) FEX capabities. The 5548 and 5596 will support more (16) per 55xxk, and with the 7K will support upto 32 FEX's.
Documentation has been spotty on this subject, because the term 5k indicates that all 5000 series switches will support extended FEX's which is not the case only the 55xx will support more than 12 FEX. Maybe in the future the terminology for the 5k series should be term 5000 series and 5500 series Nexus, there are several differences and advancements between the two series.

Would you buy an n200 when firmware upgrade a problem or go with nan

My dealer has both the n200 and nano with n200 a bit lower in price.Would you go with n200 if no firmware upgrade seems to exist or go for the nano?Does the n200 have decent firmware in it so upgrade not needed?Is there firmware out there to stop the backlight buzz? thanks matt

First of all, compare the n200 to the Nano Plus. The Nano lacks FM radio and doesn't come with the case and armband(In the US both the n200 and Nano Plus have FM and the case and armband. In other places the case and armband might not be included). I would tend to want the Nano Plus if it is close in price to the n200 since going forward firmware upgrades for it will probably be available for longer than for the n200. Some of the earlier n200 firmware does have issues, especially that before .2 . If you do decide to buy an n200 you should plan to do a firmware upgrade as soon as you get it. It is not easy to tell what firmware an n200 will have just by looking at the package. If the price of the Nano Plus is $20 or more above that of the same capacity n200, then I would prefer an n200. If the Nano Plus is only $0 more then I would prefer the Nano Plus. Between those I guess it is a toss up.

**SPA2102 FIRMWARE UPGRADE PROBLEM WITH 5.2.12

I'm having problems loading firmware 5.2.12 onto my SP2102-R ATA. I have my laptop PC running Windows 7 directly with an ethernet cable from my laptop to the ethernet connection on the back of the SPA2102. I run the .bin file and In order to get the software to the upgrade stage I have to enter ****, 73738 1# to move to the next stage. I have now been waiting for 1/2 hour waiting for firmware download request from SPA. IT DOESN'T GET PASS THIS STAGE.......CAN SOMEONE PLEASE TELL WHAT I'M DOING WRONG OR WHAT I NEED TO DO DIFFERENT?
Thanks......

Based on my experience with the SPA2102-NA, it is not necessary to do a factory reset (*73738) in order to perform a firmware upgrade/downgrade.
However, now that you have done so, any and all previous user settings will have been reset to the original factory settings (including user set passwords - assuming your ATA is an un-locked SPA2102-NA).
If you think the firmware 5.2.12 is faulty, then repeat the upgrade/downgrade process by downgrading back to an earlier version:
http://www.cisco.com/cisco/software/release.html?mdfid=282414111&softwareid=282463187&release=5.2.12&relind=AVAILABLE&rellifecycle=&reltype=latest
If you are still having problems, see if this tutorial will reveal any procedural issues:
http://blog.cqvoip.net/2009/12/linksys-cisco-spa2102-updating-firmware.html
Regards,
Jeff - cqvoip.net

I have Lightroom 4.4 and a Nikon d800 with firmware upgrade 2.005. raw files are now since upgrade, unreadable. any plugins or advice? Thanks

I have Lightroom 4.4 and a Nikon d800 with firmware upgrade 2.005. raw files are now since upgrade, unreadable. any plugins or advice? Thanks

I select the images I want uploaded, NEF files, click the "IMPORT" button, process bar comes up and shows work in progress, but no progress. after about 2 minutes, dialogue box appears with message: "unable to import because the following files are unreadable: NEFxxxx, etc."

NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX

Similar Messages

Maybe you are looking for