Cisco nexus 5020 OS upgrade failed.

Hi All,
I have cisco 5020 nexus switch which is currently running with
kickstart: version 4.0(0)N1(2)
system:    version 4.0(0)N1(2)
I want to upgrade for
kickstart: version 4.2(1)N2(1)
system:    version 4.2(1)N2(1)
i believe it requires chain upgrade , hence i tried going for immediate next versions and also tried required version
4.0.1a.N2.1
4.0.1a.N1.1a
4.2.1.N2.1
But whenever i upload images and verify by giving
show install all impact kickstart bootflash:n5000-uk9-kickstaart.4.0.1a.N1.1a.bin system bootflash:n5000-uk9.4.0.1a.N1.1a.bin
i get the following error.
Verifying image bootflash:/n5000-uk9-kickstart.4.0.1a.N1.1a.bin for boot variabl
e "kickstart".
[#                   ]   0%[####################] 100% -- SUCCESS
Verifying image bootflash:/n5000-uk9.4.0.1a.N1.1a.bin for boot variable "system"
[#                   ]   0%[####################] 100% -- SUCCESS
Verifying image package type.
[#                   ]   0%[#####               ] 20%[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/n5000-uk9.4.0.1a.N1.1a.bin.
[#                   ]   0%[#                   ]   0% -- FAIL. Return code 0x404F0003 (SRG file not presen
t/cannot be opened).
Version Compatibility check failed. Return code 0x40930012 (SRG extraction failed).
Please help in getting this issue solve.
Thanks,
Atif

I get this:
show install all impact kickstart bootflash:n7000-s1-kickstart.5.2.7.bin system bootflash:n7000-s1-dk9.5.2.7.bin
Verifying image bootflash:/n7000-s1-kickstart.5.2.7.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/n7000-s1-dk9.5.2.7.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.5.2.7.bin.
[#                   ]   0% -- FAIL. Return code 0x404F0003 (SRG file not present/cannot be opened).
Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.5.2.7.bin.
[#                   ]   0% -- FAIL. Return code 0x404F0003 (SRG file not present/cannot be opened).
Extracting "bios" version from image bootflash:/n7000-s1-dk9.5.2.7.bin.
[####################] 100% -- SUCCESS
Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.5.2.7.bin.
[#                   ]   0% -- FAIL. Return code 0x404F0003 (SRG file not present/cannot be opened).
Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.5.2.7.bin.
[#                   ]   0% -- FAIL. Return code 0x404F0003 (SRG file not present/cannot be opened).
Extracting "system" version from image bootflash:/n7000-s1-dk9.5.2.7.bin.
[#                   ]   0% -- FAIL. Return code 0x404F0003 (SRG file not present/cannot be opened).
Extracting "kickstart" version from image bootflash:/n7000-s1-kickstart.5.2.7.bin.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/n7000-s1-dk9.5.2.7.bin.
[#                   ]   0% -- FAIL. Return code 0x404F0003 (SRG file not present/cannot be opened).
Pre-Upgrade check failed. Return code 0x40930012 (SRG extraction failed).
A show version:
Software
BIOS:      version 3.22.0
kickstart: version 5.1(1a)
system:    version 5.1(1a)
BIOS compile time:       02/20/10
kickstart image file is: bootflash:///n7000-s1-kickstart.5.1.1a.bin
kickstart compile time: 12/25/2020 12:00:00 [11/05/2010 00:14:37]
system image file is:    bootflash:///n7000-s1-dk9.5.1.1a.bin
system compile time:     11/4/2010 11:00:00 [11/05/2010 01:25:15]
Thanks in advance

Similar Messages

Highest supported Brocade DCX firmware version to be interoperable with Cisco Nexus 5020

A Cisco Nexus 5020 (FCoE) switch is connected to Brocade DCX-B switch.
5020 is at latest firmware level of 5.0.2.N2.1
Brocade is at firmware level of 6.2.1b
If we need to upgrade brocade firmware, what is the maximum revision we can go to? Is there some documentation available for interoperability between the code levels of the two hardwares?

Hi Anwarul,
Please refer to "Table 7-10 Nexus InterOp Matrix" near the end of this link:
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix7.html
Regards,
Ken

CISCO NEXUS 5020 Not Booting

I have a cisco nexus 5020 switch of 2 nos, but when i try to boot the device its result no image on the flash and it stuck in the boot mode. Is any possibility to boot the nexus from boot mode without having a image from flash.

Hi Michael,
If the unit is not showing anything at all when connecting screen/keyboards, there won't be much more investigation possible. Likely the HW has gone bad and you will have to replace it.
Regards,
Marco

ErrorDisabled status on a Cisco Nexus 5020 NX-OS 5.0(2)N2(1)

Any ideas how to NOT USE errdisable or allow the FCoE switch to put a port / interface / VFC into an error disabled state?
I do not see any command(s) to NOT use this feature.
thanks
matt

You can disable errordisable condition only for certain causes. Here are the options.
F340.24.10-5548-1(config)# no errdisable detect cause ?
all           Enable error detection on all cases
inline-power Enable error disable detection for POE
link-flap     Enable error disable detection on linkstate-flapping
loopback      Enable error disable detection on loopback
But you can enable recovery if needed
F340.24.10-5548-1(config)# errdisable recovery cause ?
all                Enable timer to recover from all causes
bpduguard          Enable timer to recover from BPDU Guard error disable state
failed-port-state Enable timer to recover from stp set port state failure
inline-power       Enable timer to recover from POE disabled state
link-flap          Enable timer to recover from linkstate flapping
pause-rate-limit   Enable timer to recover from pause rate limit error disabled state
udld               Enable timer to recover from udld error disabled state
F340.24.10-5548-1(config)#
Any particular condition you are after?

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.

Nexus 5020/2248: Best Practice for DSCP-trust, verses DSCP-don't trust

We have several Nexus 5020/2248's for our server access to the network (approximately 1000 ports). On about 20 of these ports we want to trust the DSCP markings, since they are from out Cisco Unified Comm appliances (these are access ports). However, on all other ports (mostly access, so DSCP, but ~ 100 trunks so some are COS also) we want to "not trust" or essentially zero out any non-zero DSCP value.
Does anyone have suggestions on easiest/best method for setting the trust boundaries for Nexus 5020/2248s?
Note: vers 5.0(3) NS(1)
Thanks!
Mike.

Hi
Before any other think I would like you to upgrade your WLC image to 7.6.130.0 & FUS to 1.9.0.0. FUS upgrade will require 30-40min downtime to your wireless.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn76mr03.html
It tells me to disable 802.11a and 802.11b. If I go into each radio on 'Network' tab and disable these - NOTHING can connect to any SSID. So unless I've misunderstood something - this is a contradiction in the best-practice link I posted above,
This simply says, you have to disable radio band before changing QoS profile values. Once you change those value you can re-enable the radio band. :)
If I enable FT-PSK and PSK - for devices that support FT-PSK (which i'm under the impression is 802.11r) will these devices use that and for devices that don't they'll use 'regular' PSK? How do I know if my client is connecting using PSK or FT-PSK as both are enabled on the same WLAN.
Read these 802.11r post & you will understand how 802.11r works. There are certain client devices does not like PSK & FT-PSK capability advertise on the same SSID & may have connectivity issues. But most of the clients like iPhone, iPads,etc will connect without any problems.
http://mrncciew.com/2014/09/06/cwsp-802-11r-ft-association/
http://mrncciew.com/2014/09/07/cwsp-802-11r-over-the-air-ft/
http://mrncciew.com/2014/09/08/cwsp-802-11r-over-the-ds-ft/
"show client detail <mac_address>" should indicate if client connected over FT-PSK or PSK.
HTH
Rasika
**** Pls rate all useful responses ****

Routing issue between Cisco Nexus and Cisco 4510 R+E Chassis

We have configured Cisco Nexus 7K9 as core and Cisco 4510 R+E as access switches for Server connectivity.
We are experiencing problem in terms of ARP learning and Ping issues between Cisco Nexus and end hosts.

Hi,
So you have N7k acting as L3 with servers connected to 4510?.
Do you see the MAC associated with failing ARP in 4510?. Is it happening with all or few servers?. Just to verify if it is connectivity issue between N7k and 4510, you can configure an SVI on 4510 and assign address from same raneg (server/core range) and perform a ping.
This will help narrow down if issue is between server to 4510 or 4510 to N7k.
Thanks,
Nagendra

Cisco ip phone 9971 registration failed with CME 8.6 on WAN

Dear Sir
Subject: Cisco ip
phone 9971 registration failed
with CME 8.6 on WAN
I have a WAN simulation with one Cisco2811 router one Cisco1841 router (connected with fast Ethernet interface) plus one layer 2 switch.
I upgraded the 2811 IOS to 15.4M and installed CME8.6, when we tried to add 9971 sip phone If the traffic goes throw LAN (Same subnet- directly from switch to 2811) everything is fine and the SIP phone (9971) added with no problem but when I change the subnet and traffic goes throw WAN
( from 1841 routed to 2811 with default route) my phone didn't register.
It will be great if anybody could help!!
If you can solve my problem, I will be happy to compensate.

Try binding SIP to an interface on which Phone can reach (Use "voice service voip" "sip" and then bind)
Udit

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.

ISE 1.3 Upgrade fails

Hi All
I did upgrades from 1.2.1.198 to 1.3. With one box (SNS-3495-K9) out of four I have a problem.
I've tried it many times, I even made it to a standalone and did an application reset-config ise to initialize the box prior updating, but it always fails at step 40.
- Data upgrade step 40/67, CertMgmtUpgradeService(1.3.0.616)... % Error: ISE Global data upgrade failed!
Rolling back the configuration database...
Starting application after rollback...
% Error: The node has been reverted back to its pre-upgrade state.
% Application install or upgrade cancelled.
Any Idea ?
Thanks Thomas

Upgrade Failures
During upgrade, the configuration database schema and data upgrade failures are rolled back automatically. Your appliance would return to the last known good state. If this is encountered, the following message appears on the console and in the logs:
% Warning: The node has been reverted back to its pre-upgrade state.
error: %post(CSCOcpm-os-1.2.0-899.i386) scriptlet failed, exit status 1
% Application upgrade failed. Please check logs for more details or contact Cisco Technical Assistance Center for support.
In case of upgrade failures, before you try to upgrade again:
Analyze the logs. Check the application bundle for errors.
Identify and resolve the problem by submitting the application bundle that you generated to the Cisco Technical Assistance Center (TAC).

ISE Upgrade Fails from 1.1.0 to 1.1.2.145

Hi,
I am trying to upgrade ISE from 1.1.0 to 1.1.2.145 but failed. Find the details below.
DR-ise-pdp-01/admin# application upgrade ise-appbundle-1.1.2.145.i386.tar.gz ISE1
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
Stopping ISE application before upgrade...
Running ISE Database upgrade...
% Application upgrade failed. Please check logs for more details.
Regards

Hi,
Try to go to v1.1.1 first, add patch 3 and then go to v1.1.2.
From ISE relaese notes:
Upgrade from Cisco ISE, Release 1.1.1 to release 1.1.2
Before you can upgrade to Cisco ISE, Release 1.1.2, you must first be sure you have upgraded your machine to Cisco ISE, Release 1.1.1 with patch 3 applied. For specific instructions on performing the upgrade procedure, see the Cisco Identity Services Engine Upgrade Guide, Release 1.1.x.
HTH

Ask the Expert: Cisco Nexus 2000, 5000, and 6000 Series Switches

with Cisco Expert Vinayak Sudame
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions how to configure and troubleshoot the Cisco Nexus 2000, 5000 and 6000 Series Switches with Cisco subject matter expert Vinayak Sudame. You can ask any question on configuration, troubleshooting, features, design and Fiber Channel over Ethernet (FCoE).
Vinayak Sudame is a Technical Lead in Data Center Switching Support Team within Cisco's Technical Services in RTP, North Carolina. His current responsibilities include but are not limited to Troubleshooting Technical support problems and Escalations in the areas of Nexus 5000, Nexus 2000, FCoE. Vinayak is also involved in developing technical content for Cisco Internal as well as external. eg, Nexus 5000 Troubleshooting Guide (CCO), Nexus 5000 portal (partners), etc. This involves cross team collaboration and working with multiple different teams within Cisco. Vinayak has also contributed to training account teams and partners in CAE (Customer Assurance Engineering) bootcamp dealing with Nexus 5000 technologies. In the past, Vinayak's responsibilities included supporting MDS platform (Fiber Channel Technologies) and work with EMC support on Escalated MDS cases. Vinayak was the Subject Matter Expert for Santap Technologies before moving to Nexus 5000 support. Vinayak holds a Masters in Electrical Engineering with Specialization in Networking from Wichita State University, Kansas. He also holds Cisco Certification CCIE (#20672) in Routing and Switching.
Remember to use the rating system to let Vinayak know if you have received an adequate response.
Vinayak might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community, Other Data Center Topics discussion forum shortly after the event.
This event last through Friday July 12, 2013. Visit the community often to view responses to youe questions of other community members.

Hi Vinayak,
Output of "show cfs internal ethernet-peer database"
Switch 1
ETH Fabric
Switch WWN logical-if_index
20:00:54:7f:ee:b7:c2:80 [Local]
20:00:54:7f:ee:b6:3f:80 16000005
Total number of entries = 2
Switch 2
ETH Fabric
Switch WWN logical-if_index
20:00:54:7f:ee:b6:3f:80 [Local]
20:00:54:7f:ee:b7:c2:80 16000005
Total number of entries = 2
Output of "show system internal csm info trace"
Switch 1 in which "show cfs peers" show proper output
Mon Jul 1 05:46:19.145339 (CSM_T) csm_sp_buf_cmd_tbl_expand_range(8604): No range command in buf_cmd_tbl.
Mon Jul 1 05:46:19.145280 (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
Mon Jul 1 05:46:19.145188 (CSM_T) csm_sp_handle_local_verify_commit(4291):
Mon Jul 1 05:46:19.145131 csm_continue_verify_ac[597]: peer is not reachable over CFS so continuing with local verify/commit
Mon Jul 1 05:46:19.145071 csm_tl_lock(766): Peer information not found for IP address: '172.16.1.54'
Mon Jul 1 05:46:19.145011 csm_tl_lock(737):
Mon Jul 1 05:46:19.144955 (CSM_EV) csm_sp_build_tl_lock_req_n_send(941): sending lock-request for CONF_SYNC_TL_SESSION_TYPE_VERIFY subtype 0 to Peer ip = (172.16.1.54)
Mon Jul 1 05:46:19.143819 (CSM_T) csm_copy_image_and_internal_versions(788): sw_img_ver: 5.2(1)N1(2a), int_rev: 1
Mon Jul 1 05:46:19.143761 (CSM_T) csm_sp_get_peer_sync_rev(329): found the peer with address=172.16.1.54 and sync_rev=78
Mon Jul 1 05:46:19.143699 (CSM_T) csm_sp_get_peer_sync_rev(315):
Mon Jul 1 05:46:19.143641 (CSM_EV) csm_sp_build_tl_lock_req_n_send(838): Entered fn
Mon Jul 1 05:46:19.143582 (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
Switch 2 in which "show cfs peers" does not show proper output
Mon Jul 1 06:13:11.885354 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 77 seq 482
Mon Jul 1 06:13:11.884992 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 357 seq 369
Mon Jul 1 06:13:11.884932 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 357 seq 368
Mon Jul 1 06:13:11.884872 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 357 seq 367
Mon Jul 1 06:13:11.884811 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 357 seq 366
Mon Jul 1 06:13:11.884750 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 352 seq 365
Mon Jul 1 06:13:11.884690 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 352 seq 364
Mon Jul 1 06:13:11.884630 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 352 seq 363
Mon Jul 1 06:13:11.884568 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 352 seq 362
Mon Jul 1 06:13:11.884207 (CSM_EV) csm_sp_acfg_gen_handler(3011): Preparing config into /tmp/csm_sp_acfg_1733916569.txt
Mon Jul 1 06:13:11.878695 csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
Mon Jul 1 06:13:11.878638 (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
Mon Jul 1 06:12:29.527840 (CSM_T) csm_pss_del_seq_tbl(1989): Freeing seq tbl data
Mon Jul 1 06:12:29.513255 (CSM_T) csm_sp_acfg_gen_handler(3106): Done acfg file write
Mon Jul 1 06:12:29.513179 (CSM_EV) csm_sp_acfg_gen_handler(3011): Preparing config into /tmp/csm_sp_acfg_1733911262.txt
Mon Jul 1 06:12:29.508859 csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
Mon Jul 1 06:12:29.508803 (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
Mon Jul 1 05:53:17.651236 Collecting peer info
Mon Jul 1 05:53:17.651181 Failed to get the argumentvalue for 'ip-address'
Mon Jul 1 05:40:59.262736 DB Unlocked Successfully
Mon Jul 1 05:40:59.262654 Unlocking DB, Lock Owner Details:Client:1 ID:1
Mon Jul 1 05:40:59.262570 (CSM_T) csm_sp_del_buf_cmd(1713): Deleting comand with Id = 1
Mon Jul 1 05:40:59.262513 DB Lock Successful by Client:1 ID:1
Mon Jul 1 05:40:59.262435 Recieved lock request by Client:1 ID:1
Mon Jul 1 05:40:41.741224 ssnmgr_ssn_handle_create_get: Session FSM already present, ID:1
Mon Jul 1 05:40:41.741167 ssnmgr_handle_mgmt_request: Create/Get request received for session[process_n5kprof]
show cfs lock gives no output.
Just to further clarify, we have 4 5548UP switches in the same management vlan. 2 switches are in one location lets say location A and they are CFS peers and are working fine.
These two switches which are having problem are in location B. All the switches are in the same vlan. Essentially the all CFS multicast messages will be seen by all 5548 switches as they are in the same vlan. I am assuming that this might not create any problems as we specify the peers in the respective configurations. Or do we have to change the CFSoIPv4 multicast addresses in location B or may be configure a different region.
Regards.

LMS4.0.1 Nexus 5020 - internal error in inventory collection

Hello,
2 Nexus 5020 (SysObjId ...3.719) brings internal error in inventory collection as following:
"RICS0001: Internal Error, unable to process the collected data from the device"
whereby 2 other devices from same type, same sysobjid are working well. SDT from v401 shows this device as supported.
What can we do?
Steffen

Hi Steffen,
Try updating the MDF and device packages for RME first and check the issue..
If you have not applied the below patch before ,kindly apply this :
Download the Patch for this BUg from cisco.com and apply it ..I hope that should take care of the issue.
CSCto46927 Psu support changes from CCO to SPRIT
lms40x-win-CSCto46927-0.zip (For windows)
lms40x-sol-CSCto46927-0.tar (For solaris)
Thanks
Afroj

Spa508 firmware upgrade failed

I bought a spa500ds and need to upgrade the firmware on my 508G to use it.
When I try to upgrade to 7.5.4, or 7.5.3 I get a failure. I was able to upgrade to 7.5.1a fine. All firmware was downloaded from cisco this morning and unziped
I see my tftp server giving the file.
I get upgrade failed: 12. corrupt file in my syslog
Any idea where to look next?

It states on the release notes of 7.5.4, that upgrading from 7.5.1a you should first upgrade the phone to 7.5.2b.
Have you done this upgrade step?
Joao

DCNM 6.1.1a and Nexus 5020

Hi all,
I've got a problem that I am not able to figure out.
I've got 2 nexus 5020 running
Software
system:    version 5.0(2)N2(1)
system image file is:    bootflash:/n5000-uk9.5.0.2.N2.1.bin
Hardware
cisco Nexus5020 Chassis ("40x10GE/Supervisor")
I use Nagios for management and so far, everything is working fine. Since a couple of days, I was thinking to install dcnm 6.1.1a on a red hat linux to test the app and see what can I do with the nexus. The problem is that every time that I try to work with the DCNM app, the CPU goes up a lot.
The show process cpu history is the following:
            1
   1 1 2 2 2014 3 1
   175785558555676737556055796009577855685588655825576458656955
100 #
90 #
80 #
70 #
60 #
50 # #
40 # #
30 # # #
20 # # # #### # #
10 ################################################### ########
   0....5....1....1....2....2....3....3....4....4....5....5....
             0    5    0    5    0    5    0    5    0    5
CPU% per second (last 60 seconds)
# = average CPU%
   111111111111111111111111111111111111111111111111111111111111
   000000000000000000000000000000000000000000000000000000000000
   000000000000000000000000000000000000000000000000000000000000
100 ************************************************************
90 ************************************************************
80 ***************************************** *******************
70 ************************************************************
60 ************************************************************
50 ************************************************************
40 ************************************************************
30 ************************************************************
20 ******#*****************************************************
10 ############################################################
   0....5....1....1....2....2....3....3....4....4....5....5....
             0    5    0    5    0    5    0    5    0    5
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
    111111111111111111111111111111111111111111111111111111111111111111111111
    335654444333535333333474344735935547557454443544355623332443363242463447
100
90
80
70
60
50
40
30
20 *** * * * * ** ** **** * * *** * * *
10 ############################################### #########################
   0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
             0    5    0    5    0    5    0    5    0    5    0    5    0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
        1      1 1          1 1 1                  1        1
   799870778787080999797778070770777887797877878760777776770777
   418260550868090312495185010220451125592520612190533039160102
100 * * * * * * * * * * *
90 ** * * ****** * ** * * * * * * *
80 ***************** ** *** * * * ***** * * * ** **
70 ************************************************************
60 ************************************************************
50 ************************************************************
40 ************************************************************
30 ************************************************************
20 ************************************************************
10 ############################################################
   0....5....1....1....2....2....3....3....4....4....5....5....
             0    5    0    5    0    5    0    5    0    5
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
Could SNMP be the cause of this high CPU? How could I confirm it? Maybe it is a bug but I could not find anything.
Any ideas or comments are welcomed!
THanks in advance,
Fernando

Just to close this thread, we saw that the average cpu utilization is 10%. The CPU spikes might be due to the polling time or some cosmetic output. There is no output error, no discards, no traffic loss.
thanks in advance,
Fernando

Cisco nexus 5020 OS upgrade failed.

Similar Messages

Maybe you are looking for