Ask questions, create discussions or post news! This subreddit is for all things Cisco related!New user accounts are moderated.This subreddit is not affiliated with Cisco Systems. Related subreddits:-Useful Links.Rules. Be respectful to others.
No questions about how to get Cisco software without a service contract. No posting or discussion of brain dumps. Stay on topic. No sales or recruitment posts. No homework help.
Any way of policing traffic on the Nexus 3k platform? I can't find a reference to say policing/shaping is supported. View 5 Replies View Related Cisco Switching/Routing:: Nexus 3048 VPC Doesn't Form Jun 11, 2012. I am building up vPC on 2 x Nexus 3048 and found that it did not work properly.The current config as follows, 1.
No low effort postNOTE: The 'Reddit Cisco Ring', its associates, subreddits, and creator 'mechman991' are not endorsed, sponsored, or officially associated with Cisco Systems Inc. All opinions stated are those of the poster only, and do not reflect the opinion of Cisco Systems Inc., or its affiliates.Last Update: Feburary 27th, 2019. I recently tried upgrading a Nexus 3048TP to n3000-uk9.6.0.2.U6.7.bin so that I could proceed with the upgrade to nxos.7.0.3.I4.7.bin. Install all system bootflash:n3000-uk9.6.0.2.U6.7.bin kickstart bootflash:n3000-uk9-kickstart.6.0.2.U6.7.binNormally, the switch would automatically reboot after the upgrade and everything will be good to go. However, this time, the switch hung up and stopped responding (via the console port).
I tried rebooting it multiple times, but I get no output from the console port.Power was not lost during the upgrade, but I bought these switches from eBay so I'm not exactly sure if the image (n3000-uk9-kickstart.6.0.2.U6.7.bin), which came pre-loaded, was exactly what the filename said it should be.On the outside, the switch's bright blue 'ID' light is constantly illuminated (even after about an hour of being online). The 'STAT' light is not lit at all. Both PSU's are online and are 'OK' according to the LED's.What would be my next steps in troubleshooting this? I read the online documentation about the 'STAT' light , and it claims that the light being off means that the module (I'm assuming the chassis or the supervisor) is not receiving power. However, this switch has worked perfectly before doing the OS upgrade, so I'm not sure what went wrong. Was just taking a look at the release notes for 6.0(2)U6(7):A Cisco Nexus 3048 switch may not boot up or become unusable after an upgrade to Cisco NX-OS Release 6.0(2)U6(7) or Cisco NX-OS Release6.0(2)U6(8).Note: To avoid this issue, any Cisco Nexus 3048 switch, that use software versions older than Cisco NX-OS Release 6.0(2)U6(2), must be first upgraded to Cisco NX-OS Release 6.0(2)U6(2) before upgrading to Cisco NX-OS Release 6.0(2)U6(3) or later releases.
For more information see: CSCvb78728. Well kudos to you to taking time to read release notes, whereas I just assumed it would be fine since the major software version was the same. Are you running this in production?If so, never buy critical infrastructure off eBay. There are legitimate sources of used gear. Hell, Cisco even sells used gear through resellers.Never load an image to any device without validating it. Either through the MD5 or SHA hash, or using the built in validation tools.My only advice, apart from calling TAC, is to pull all power and power supplies from the switch for 10 minutes, then reconnect, power on, leave console cabbie connected to look for output.It's possible it was still upgrading when you think it locked up, and sometimes those have to flash and rewrite EEPROMs on the switch and power supplies. If that got interrupted then there's no way to recover.
Never load an image to any device without validating itNexus software upgrade does this automatically: Verifying image bootflash:///n3000-uk9-kickstart.6.0.2.U6.10.bin for boot variable 'kickstart'.#################### 100% - SUCCESSVerifying image bootflash:///n3000-uk9.6.0.2.U6.10.bin for boot variable 'system'.#################### 100% - SUCCESSVerifying image type.#################### 100% - SUCCESSMy Nexus 3048 got bricked as well. Would suspect something goes wrong on the BIOS upgrade. Would the upgrade have taken over 30-45 minutes? Because that's around how long I waited before pulling the plug to reboot it (I don't remember the exact message, but there was some output from the console saying something along the lines of restarting with a code). I actually purchased two of these systems off the same seller.
I was able to upgrade the other one to 6.0(2)U6(5c) without a hitch in under 15-20 minutes. No freezing up or anything.Also, doesn't the system validate the images before using them in an upgrade? I see steps such as 'Verifying image' when doing the upgrade.