Nexus 5548UP upgrade, note on micro-controller

Hi, I recently upgraded our 5548UP nexus switches from 5.1(3)N1(1a) to 5.2.1.N1.3. during the end of the upgrade (before rebooting) it says the following -
ote: Micro-controller upgrade needs a power-cycle to take into effect.
On success of micro-controller upgrade, SWITCH OFF THE POWER to the system and then, power it up.
Do we really need to power cycle the SW, power off and on? is this step really needed after the upgrade aas it has already rebooted?
Thnx

Hi,
the note during the upgrade confuses me too.
As far as I understand, it depends on image uC version change.
Images will be upgraded according to following table:
Module       Image         Running-Version             New-Version Upg-Required
     1      system             5.1(3)N2(1)            5.2(1)N1(2a)           yes
     1   kickstart             5.1(3)N2(1)            5.2(1)N1(2a)           yes
     1        bios      v3.5.0(02/03/2011)      v3.6.0(05/09/2012)           yes
     1      SFP-uC                v1.0.0.0                v1.0.0.0            no
   101       fexth             5.1(3)N2(1)            5.2(1)N1(2a)           yes
   102       fexth             5.1(3)N2(1)            5.2(1)N1(2a)           yes
     1   power-seq                    v5.0                    v5.0            no
     1          uC                v1.0.0.2                v1.0.0.2            no
In this case no version change -> power off/on is not necessary.
Best regards

Similar Messages

Cisco Nexus 5548UP upgrade path

Hi,
I'm planning to upgrade Nexus 5548UP (no L3 services) from 5.2(1)N1(6) to 7.0(5)N1(1). Is this upgrade path vaild? or is there any intermediate version; also advise if ISSU is possible.
Regards,
Navin RK

Hi,
Yes you can upgrade directly from 5.2(1)N1(6) to 7.0(5)N1(1). ISSU is possible, provided you meet the requirements. You can copy the kickstart and system image to bootflash, then run the "show install all impact" command to see whether or not ISSU will be possible with your configuration.
Here is a document supporting the statements above: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/upgrade/705_N1_1/n5500_upgrade_downgrade_700.html#pgfId-640981

Galaxy Nexus - online upgrade not going well

I tried to order the Galaxy Nexus through the Verizon online site. Two problems: First, the system will not give me the NE2 discount. Second, I have an unlimited data plan on my existing phone and site wants me to change to another one. I'm going to order by phone but I prefer online as I can type in specific address information and verify the terms in writing.

I'm clearly eligible for the NE2 since it's only been three months since the regular upgrade time. And the VZW web page has an indicator that shows that this particular line is eligible for the loyalty discount.
But when browsing through the list of phones, the prices of some recent models, such as the RAZR and Galaxy Nexus, do not reflect the loyalty discount. Most others, such as the iPhones, clearly list the discount and show it subtracted from the normal price. Note that the Galaxy Nexus price does not have the NE2 already embedded in it. The Galaxy Nexus has the same price on my NE2-eligible account as on my other lines that are upgrade eligible but not NE-2 eligible. And the NE2 adjustment does not get taken off later in the order process.

Nexus 5548UP snmp gathering information from FC is not working

Hi all,
We have a couple of Nexus 5548UP.
Nx-OS = n5000-uk9.7.0.5.N1.1.bin
monitoring traffic of FC interfaces was working fine until we upgraded to 7.0.5.N1.1 from 6.0.2.N2.1.
We didn't change anything on our Nexus config and on our Centreon monitoring engine.
I also can't see Fc interface while browsing MIBs from the Nexus.
Is there any issue or something to do to recover the monitoring of The FC interface of the Nexus ?
Best Regards
Cyril

Hi,
It might be this bug.
FC interfaces are not listed in IF-MIB snmp walk
CSCup75270
-->Fixed in NX-OS 7.0(6) and above.

Cisco Nexus 5596 does not boots up after NX-OS upgrade 5.1.3.N1.1 to 6.0.2.N2.5 [CSCun66310]

Hello Friends,
Just want to save your precious time & effort, while doing Nexus 5596 upgrades so wanted to share some useful info which you can have a look prior to your upgrades of Cisco Nexus 5596 device.
I recently ran into trouble when upgarding one of datacenter switch Nexus 5596 does not boots up and after investigation from Cisco TAC it comes out to be Bug documented below.
https://tools.cisco.com/bugsearch/bug/CSCun66310/?reffering_site=dumpcr
My Upgrade path of device was : 5.1(3)N1(1)  to 6.0(2)N2(5).
Since this upgarde involves upgrade of Bios and Power sequensor, I was having some doubts to get this succesfully upgraded, But there was more twist involved in this upgrade which I came to know after contacting Cisco TAC for my died Nexus 5596 device and got info that if you have below impacted version in your Nexus 5596 device and you are planning to do Upgrade, then you migh RUN into this serious BUG aftre which device won't come up at all and only Option left is to replace with RMA device.
PID                          Impacted                   Hardware versions      Updated Versions
UCS-FI-6296UP                                            1.0                                       1.1
N5K-C5596UP                                              1.0                                        1.1
N5K-C5596T                                                 1.1                                         1.2
You can check hardware version using below command from your device.
5596# show sprom sup | inc H/W
H/W Version     : 1.1
So please be carefull when planning your Nexus 5596 upgrade and verify above things as this Bug is not present anywhere in Upgrade docuemntations unfortunately.
Hope this will help and save someone's precious Time.

Today "upgraded" our switch (N5k-C5596UP) to from 5.1(2)N1 to 7.0(5) and after reboot no life from the switch either. Even no console response. show sprom sup | inc H/W shows 1:0.
Only thing we could do is RMA the switch. So what must I do with these switches? Have still to do 3 of them.

Connecting many Brocade switches to Nexus 5548UP

Hello,
I have a SAN network composed of few separate PODs. Each POD is divided into SAN-A and SAN-B. Most of those PODs are Brocade switches (FOS 6.1). There are also few Nexus 5520s. Now, we have built new core infrastructure with Nexus 5548UPs and many MDS 9148s. We would like to move all servers and sotrage from old Brocades to the new SAN. As we cannot move all devices at the same time, all segments must be connected to the core for some time. Each POD has different zoning. Some zonings on Brocade switches are based on PWWN, some on Domain ID and Port ID. In my opinion, the only way of successfuly connecting all PODs together is to merge zones manualy (in excel, etc). and paste them on all switches. However, maybe there is some other way of merging all zones? What if I leave Nexus 5548UP in native mode (so zones from Brocade will not get merged), and only implement that manually merged zoneset on Nexus 5548UP? Will the ISL links get isolated due to zoning merge failure? Or they will maintain operational state even if zones are different on each POD? I do not have any lab boxes, so I cannot test it. Any advidse will be appreciated.
Best regards,
Krzyszof

well since you can not cluster the 45K as a virtual switch ( Cisco with new sup will start support VSS in the 4500 try to check which sup exactly and if you can upgrade as this will make a significant improvement to your design )
anyway the only method that you can use currently is the traditional way which is depending on STP ( use rapid-PVST)
from each N5K use one separate link to each 45K and STP will put on of the links in blocking mode
however you might do some STP and vlan design for load sharing where you can send vlan x over link1 and vlan y over link b to the 45K using STP cost
HTH

Cisco Nexus 5548UP Switch Current Version 5.2(1)N1(4)

Hi, we're currently have Cisco Nexus 5548UP Switch Current Version 5.2(1)N1(4)
It's not listed as affected version:
Known Affected Releases:
(5)
5.2(1)N1(8a)
6.0(2)N2(5)
7.0(3)N1(0.125)
7.0(4)N1(1)
7.1(0)N1(0.349)
The Known Fixed Releases as follow:
Known Fixed Releases:
(7)
6.0(2)N2(4.3)
6.0(2)N2(5a)
7.0(1)ZN(0.615)
7.0(5)N1(0.173)
7.0(5)N1(1)
7.1(0)N1(0.371)
7.1(0)N1(1)
Do we need to update to the latest releases?
If yes, which version of the known fixed release is best suit our current version
Cisco Nexus 5548UP Switch Current Version 5.2(1)N1(4)
Thanks.

I had the same question, so I opened a TAC case to find the right software version. I was told that the software listed as available on the bug report were custom NX-OS builds and that there are no patched versions available for the 5548p. The support engineer also said that the Nexus 5k upgrades were not expected until November or December. The best advice I could get was to subscribe to the bug report and wait to be notified of an available upgrade.

Micro controller

Dennis Knutson,
Some time back ( 1/26/05) you were helping someone with a problem communicating with a micro controller. You said if you tried to read too few bytes the vi times out. I'm using the Serial Read Write that ships with LV 7.1. One of our test is to verify that we do not have communications between one serial port to another. The operator keeps the cable off the UUT on the receive but has it on the send port and runs the vi. He verifies no data is received on the Read side of the port of interest. How can I handle this vi error to turn it into a pass/fail criteria for LV7.1? It looks like a Windows error message that pops up. I just want to display PASS or FAIL to the operator. I don't want to display the error message.
Thanks,
Clint

This is the "popup" I get and am trying to avoid see attached. I tried it at my desk w/o any serial card hooked up in case you'd like to try too. Just run the LABVIEW>>Serial vi that is under help>examples>search> type in serial. The vi is the 1st one in the list. If you open it and run it w/o changing anything you get the error I mentioned.
I want the SW to handle the error not the test person. They would have to hit "Continue" to .....continue ! This looks more like a Windows error rather than a LV error. Maybe something with an event vi ???
Attachments:
error.bmp ‏458 KB

AP Group VLAN "Feelgood" does not exists on controller.

Hi,
While appling tenplates from WCS, i getting status report error message AP Group VLAN "Feelgood" does not exists on controller.
I have double checked the perticular AP group WLAN is created & mapped to the correct interface in the controller. This is not first AP group created on the controller, other AP groups are working on the same controller.
Is there any Bug?
Thanks

Typically you still need to make sure that the country codes are indeed configured on the WLC. Thing can change when you upgrade code as standards might of changed and regulations also. If your AP's are functional, then you should be okay and I wouldn't worry too much about it, but if after the upgrade, the WLC complains about country code stuff, then you just need to verify that the AP's country code is defined on the WLC. May times the AP will not join and if it does join, the radios might be disabled or in a down status.
Sent from Cisco Technical Support iPad App

Partial collection Failure for nexus 5548UP in PI 2.1

Hi there,
I get "Partial Collection Failure" in the inventory collection status in Prime Infrastructure for all my Nexus 5548UP (8 devices).
i have seen in the PI 2.1 release notes that a bug CSCum16230 which look like my problem has been resolved in PI 2.1 but i continue getting the "partail collection failure"
Would like to know if the bug is still exist or get any other help to solve this problem.
Regards,
Alon.

hello
I have this problem as well...
we've got four N5K-C5548UP. Two with a layer 3 daughter card and two without.
interestingly we see the issue just on those boxes with the l3 daughter cards N55-D160L3-V2 installed...
Any help or ideas are highly appreciated
regards
roman
Sh inventory:
OK:
device-a# sh module
Mod Ports Module-Type Model Status
1 32 O2 32X10GE/Modular Universal Pla N5K-C5548UP-SUP active *
3 0 O2 Non L3 Daughter Card N55-DL2 ok
Mod Sw Hw World-Wide-Name(s) (WWN)
1 5.1(3)N2(1c) 1.0 --
3 5.1(3)N2(1c) 1.0 --
NOT OK:
device-b# sh modu
Mod Ports Module-Type Model Status
1 32 O2 32X10GE/Modular Universal Pla N5K-C5548UP-SUP active *
3 0 O2 Daughter Card with L3 ASIC N55-D160L3-V2 ok
Mod Sw Hw World-Wide-Name(s) (WWN)
1 5.1(3)N2(1c) 1.0 --
3 5.1(3)N2(1c) 1.0 --

LMS User Tracking for NEXUS 5548UP

Dear,
A while ago I received a ticket from one of our customers because User Tracking was not working for NEXUS 5548UP on LMS 3.2. I opened a TAC case for this but this was normal since it is a Datacenter switch. Now the customer came back on this because they really want to see which server is connected to which switch port. I understood from the TAC engineer this is not on the roadmap to integrate in LMS 4.x. They want to know if there exists another product (they thought about DCNM) and wanted to know how this integrates or works together with LMS...
Kind regards,
Sven Laureyssens

My latest understanding of User Tracking and Nexus 5K series is that it is not supported due to a limitation of the MIB support in the NX-OS.
The current DCNM (release 5.2) is distinct from the LMS and Cisco Prime umbrella but that wil be changing a bit moving forwad as DCNM is enhanced and rolled into the Cisco Prime family. Last I heard there should be some information coming out of Cisco Live this week and a new release will have some additional functionality and better integration. Still, I doubt we'll see UT for the 5K due to the NX-OS limitation.
One way to do what you're asking apart from use of any of the Cisco products is to enable LLDP on your Nexus and servers. That will at least give you the ability to pull the information from the NX-OS command line ("show lldp neighbor")

C-200 M2 with P81E to Nexus 5548UP

Hi all,
I'm working on a project which is about to set up a Cisco UCS Lab.
Actually the topology looks simple and easy but there must be some missconfiguration on my side because i can't see any of IDs (P81E's wwpn and mac address info) from the Nexus 5548UP.
I connected my 5548UP to MDS 9124 for providing the FCoE traffic to the C-200 Farm.
Then i configured the MDS with NPIV and converted couple of ethernet ports to the FC ports on 5548UP (which i'm using to connect to the MDS)
Finally i connected my C-200M2's VIC to the 5548UP but i couldn't see any information about server. The ports actually are up. But can't see nothing.
Some help and advises will be appreciated.

Padma,
Right now i connected the N5548 directly to the storage for that reason you can not see the fc uplink connections on running-configuration.
On Nexus 5548 ;
     Ethernet 1/1 and Ethernet 1/2 are the server ports (P81E)
     Ethernet 1/15 is the Uplink Ethernet port
     Fc 1/31 1/32 is the Storage Ports
     Storage has been configured for the wwpns and LUNs.
And here is the configuration :
N5548(config-if)# show running-config
!Command: show running-config
!Time: Tue Jan 24 13:32:53 2012
version 5.0(3)N2(1)
feature fcoe
feature telnet
feature lldp
username admin password 5 $1$XCMHODt3$yEItwOs0Vl.LLYyXBPjZu0 role network-admin
no password strength-check
ip domain-lookup
hostname N5548
class-map type qos class-fcoe
class-map type queuing class-fcoe
match qos-group 1
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
class-map type network-qos class-fcoe
match qos-group 1
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
slot 1
port 1-24 type ethernet
port 25-32 type fc
snmp-server user admin network-admin auth md5 0x29cde3d41c6724dcbec14cf28387824d
priv 0x29cde3d41c6724dcbec14cf28387824d localizedkey
snmp-server enable traps entity fru
vrf context management
vlan 1
fcoe vsan 1
fcdomain fcid database
vsan 1 wwn 50:06:0e:80:10:4d:03:60 fcid 0xa10000 dynamic
vsan 1 wwn 50:06:0e:80:10:4d:03:62 fcid 0xa10001 dynamic
interface vfc1
bind interface Ethernet1/1
no shutdown
interface vfc2
bind interface Ethernet1/2
no shutdown
interface fc1/25
interface fc1/26
interface fc1/27
interface fc1/28
interface fc1/29
interface fc1/30
interface fc1/31
no shutdown
interface fc1/32
no shutdown
interface Ethernet1/1
interface Ethernet1/2
interface Ethernet1/3
interface Ethernet1/4
interface Ethernet1/5
interface Ethernet1/6
interface Ethernet1/7
interface Ethernet1/8
interface Ethernet1/9
interface Ethernet1/10
interface Ethernet1/11
interface Ethernet1/12
interface Ethernet1/13
interface Ethernet1/14
interface Ethernet1/15
switchport mode trunk
speed 1000
interface Ethernet1/16
interface Ethernet1/17
interface Ethernet1/18
interface Ethernet1/19
interface Ethernet1/20
interface Ethernet1/21
interface Ethernet1/22
interface Ethernet1/23
interface Ethernet1/24
interface mgmt0
ip address 192.168.10.210/24
line console
line vty
boot kickstart bootflash:/n5000-uk9-kickstart.5.0.3.N2.1.bin
boot system bootflash:/n5000-uk9.5.0.3.N2.1.bin
interface fc1/25
interface fc1/26
interface fc1/27
interface fc1/28
interface fc1/29
interface fc1/30
interface fc1/31
interface fc1/32
N5548(config-if)#

AP is unable to associate. The Regulatory Domain '-E' configured on interface '802.11a' does not match the Controller Regulatory Domain '-C'

Hi,
There are three different types of APs associated with controller and working fine.
1.       AIR-LAP1252AG-E-K9
2.       AIR-LAP1522AG-E-K9
3.       AIR-CAP1552E-C-K9
WLC is AIR-CT5508-K9. Software version is 7.4.100.0. Field Recovery Image is 7.0.112.21. Firmware version is FPGA 1.7, Env 1.8, USB console 2.2. WCS is 7.0.240.0 for Windows.
WCS is sending alarms for AIR-LAP1522AG-E-K9:
Message: AP is unable to associate. The Regulatory Domain '-E' configured on interface '802.11a' does not match the Controller Regulatory Domain '-C'.
Before Controller was 7.2.4 (not sure).
Country configured on WLC is AE and shows -CE regulatory domain. Mesh APs are also associated.
I believe this Critical alarm should not come.
how much is this alarm important? What should be done to resolve this?

Typically you still need to make sure that the country codes are indeed configured on the WLC. Thing can change when you upgrade code as standards might of changed and regulations also. If your AP's are functional, then you should be okay and I wouldn't worry too much about it, but if after the upgrade, the WLC complains about country code stuff, then you just need to verify that the AP's country code is defined on the WLC. May times the AP will not join and if it does join, the radios might be disabled or in a down status.
Sent from Cisco Technical Support iPad App

Do we have a built-in option for web based tool in Nexus 5548UP switches for management purpose?

I have purchased Nexus 5548UP switch, i want to know if we have a built-in option for web based tool to manage and configur it just as ASA have ASDM. If there is no such options then what are the options available that can be freely available and can be used to get performance monitoring done.
Message was edited by: Praveen Varun

DCNM (Data Center Network Manager) runs on a server (Windows, RHEL or Solaris) and can be used to manage Nexus devices. It's free for Nexus 1K through 5K devices (paid license required for Nexus 7K management).
http://www.cisco.com/en/US/products/ps9369/index.html
There is not a "built-in" management product like ASDM for ASA.

Nexus 5548UP for SAN Switch

We have purchased a Nexus 5548UP switch for our SAN environment. I've only configured it for jumbo frames and currently doing testing on the performance, as some say use jumbo frames while others say do not. My question is, and I know this is a loaded question but how do you guys go about configuring your SAN switches? What exactly are you configuring on it? Such as for performance tuning or the like. The reason I ask, is we have the switch and it's pretty much working, but I'd like to learn more about it and how to tune it and fully take advantage of the switch.

That is correct, between two Dell Optiplex workstations. We also tested between the server that will go into prod and an Optiplex, but once again the Optiplex could be the limiting factor. You think that could be it? Here's my config, so you know how it's setup right now.
version 5.2(1)N1(7)
hostname N5K
feature telnet
feature lldp
feature vtp
username admin password 5 $1$oZ1234567898765432123456/ role network-admin
banner motd #Nexus 5000 Switch
ip domain-lookup
policy-map type network-qos jumbo
class type network-qos class-default
mtu 9216
multicast-optimize
system qos
service-policy type network-qos jumbo
snmp-server user admin network-admin auth md5 0x422842c9d320064123456789fc703d20
priv d3264f23456789000c703d20 localizedkey
vrf context management
port-profile default max-ports 512
interface Ethernet1/1
flowcontrol receive on
flowcontrol send on
interface Ethernet1/2
interface Ethernet1/3
interface Ethernet1/4
interface Ethernet1/5
flowcontrol receive on
flowcontrol send on
interface Ethernet1/6
interface Ethernet1/7
interface Ethernet1/8
interface Ethernet1/9
flowcontrol receive on
flowcontrol send on
interface Ethernet1/10
interface Ethernet1/11
interface Ethernet1/12
interface Ethernet1/13
flowcontrol receive on
flowcontrol send on
interface Ethernet1/14
interface Ethernet1/15
interface Ethernet1/16
interface Ethernet1/17
interface Ethernet1/18
interface Ethernet1/19
interface Ethernet1/20
interface Ethernet1/21
interface Ethernet1/22
interface Ethernet1/23
interface Ethernet1/24
interface Ethernet1/25
interface Ethernet1/26
interface Ethernet1/27
interface Ethernet1/28
interface Ethernet1/29
interface Ethernet1/30
interface Ethernet1/31
interface Ethernet1/32
interface mgmt0
ip address 11.11.11.11/24
line console
exec-timeout 720
line vty
boot kickstart bootflash:/n5000-uk9-kickstart.5.2.1.N1.7.bin
boot system bootflash:/n5000-uk9.5.2.1.N1.7.bin

Nexus 5548UP upgrade, note on micro-controller

Similar Messages

Maybe you are looking for