Cisco Switching/Routing :: Upgrade Path For Nexus 5010s Running 4.1(3)N2(1)
Jun 26, 2012
I would like to perform nondisruptive upgrades on two Cisco Nexus 5010s that currently run NX-OS version 4.1(3)N2(1) to Release 5.1(3)N2(1a). Is this possible? Or, do I need to upgrade to Release 5.0(2)N1(1) first?
Is there a known bug for Nexus 7K version 6.0(4) related to route redistribution?I have few vlan interfaces and being redistributed to the BGP.vlan interfaces are all up ang pingable.After configuring redistribution, vlan route is not in the bgp table.sho ip bgp is saying "path invalid"
BGP routing table entry for 10.165.101.192/28, version 26302 Paths: (3 available, best #3) Flags: (0x180c0021) on new-list, is not in urib, need resync with RIB, exported, has label vpn: version 47719, (0x100002) on xmit-list local label: 492294
I am at a client that I upgrade from running a single 4507 to two Nexus 5548UP switches with two Nexus 2224 fex's connected. The other access layer switches are 2960S switches. I implemented hsrp on the nexus 5k's for redudancy. The issue they are having is that some networks cannot communicate with each other. All user vlans can communicate with the server vlan, but it is not running hsrp on the vlan interface (there is a reason for that, but it not relavent for this issue). The phone vlan, which is running hsrp, can communicate with all networks.
When I am connected to either 5k, they can communicate with all devices on all networks. However, I am on vlan 10, which is a user vlan. I can communicate fine with the server vlan (vlan 101 - not running hsrp) and the phone vlan (vlan 60 - running hsrp). I cannot communicate with vlan 30 or 40, which are both running hsrp. This makes absolutely no sense at all to me. I checked out trunk ports to be sure that vlans are allowed across the networks as well. There are no firewalls between the vlans or ACL's.
I need to upgrade my core switches at one of our locations (two 7009s with dual sups) from 6.0.1 to 6.1.2. After looking through the release notes it appears that this will be a disruptive upgrade?how long should I expect for the disruption? Are we talking a 7009 boot cycle (10 - 15 minutes) or something longer?How many disruptions can I expect? I suspect 1 per chassis during the failover to the standby but I'd like to validate.Is there any compelling reason to upgrade the EPDL? From what I can see, again from the release notes, this is only necessary with F2 cards if I were to upgrade to Sup2s . I'm in a healthcare environment and this upgrade will be affecting one of our major campuses so the more info I can get to the managers the more accepting they will be for the disruptions.
I'm planning to upgrade N5K from 5.1(3)N2(1b) to 5.2(1)N1(4)."sh install all impact kickstart bootflash:n5000-uk9-kickstart.5.2.1.N1.4.bin system bootflash:n5000-uk9.5.2.1.N1.4.bin"reports:
i need to do EPLD upgrade. on a couple of Nexus 7000 with only 1 10Gb card per Switch and 2 peer-link on this card. Can you tell me what's happening when the 10GB card on the vpc secondary role Switch will be EPLD upgraded.
Is there any challenge to upgrade core switch 6500 series from Nexus 7009 which runs NxOS, because i have 3750X series switches connected at distribution and access layer in my network topology??
Is there any challenge if we place NxOS in core and IOS in distribution and Access layer??? how we are able to match sh run config in existing 6500 switch to Nexus 7009 NXOS?
I finally can upgrade my 1841 routes from 12.4 to the latest 15.1 IOS. Any info about upgrade path , do I need to modify config file and provide me with upgrade instruction link or something like that ?
Where can I find information regarding the details and upgrade path for the 2821 Intergrated services router. We are looking to upgrade from 12.4 (c2800nmc-spservicesk9-mz.12.4xxx.bin) to 15.1. Is their a spefici location to look for in the download or IOS area for upgrade paths?
I've Cisco7609-S with IOS 12.2(33)SRC2 met an issue is that "show ip route x.x.x.x" and "show ip cef x.x.x.x" shown next-hop is not actual switched next-hop.
For example, "show ip route 192.168.1.1" and "show ip cef 192.168.1.1" shown correct next-hop is 10.1.1.1, but the traffic destine to 192.168.1.1 actually not through 10.1.1.1, but always through the default route next-hop. Everything works normal after rebooted the router. Suppose it should caused by a bug? BTW, my Cisco7609 is runing BGP with ISP which received about 10K routes.
We are planning to upgrade our controller 5508 from 7.0.116.0 to 7.1.91.0. Is this directly possible or i have to put some other image before directly upgrading it?
what the upgrade path is for 5505 ASA . I have one which is version 7.2 and need to upgrade it to 8.4(5). I have read that it needs to upgraded btwn major release versions.Not sure if I need to upgrade from 7.2 - 8.0 , then form 8.0 - 8.2, then from 8.2 - 8.3 and finally 8.3 to 8.4 or can I just upgrade from 7.2 - 8.2 and then from 8.2 - 8.4 .Also what is the minimum memory requirements for vers 8.4 .my ASA running on vers 7.2 currently has 256Mb Memory and I will be upgrading this to 512MB before I do the upgrade the image above?
Nexus infrastructure is pair of N7K switches, with dual homed 5K/2K devices connected, links use vPC. They want to extend vlan's from the 5K/2K side across a L2 path into another DC, this path is only connected into one of the N7K switches, call this 7K switch A.I'm concerned that packets from the 5K/2K side back to the remote DC could get dropped due to the vPC loop dectection process. If a packet from the 5K/2K side traverses the path into the same N7K (7K switch A) as the L2 extension, I dont see a problem. But, if the etherchannel load balance in the 5K sends traffic to the packet to N7K B, in order to get to the L2 path extension to the remote DC the packet gets forwarded across the vPC. My understanding is that this packet will get dropped by N7K A as its local L2 path to the remote DC is up, is this the case?I see a solution is to plug the L2 path into a 2K, but before I suggest this is my understanding of the loop detection process correct?
We are facing issue of continous packet discards On nexus4001L link (int po2) to Nexus5020 switch. Nexus4001L is installed in IBM blade center server and we have FCOE enabled in this setup. [code]
I have been tasked to replace the existing Cat 6500 and 3750 switches by Nexus 7000 and Nexus 2000.I was told initially my boss plans to get 2 x Nexus 7000 and then eventually blow up to 4 x Nexus 7000s.For Nexus, is there a list of tasks / points that i need to consider for building the initial design?
Can i just link the Nexus 7000 like the following?
N7k-A ========= N7k-B | | lots of N2ks lots of N2ks
May I know how to manually set the priority (root ID and bridge ID priority) and for spanning tree? Which one should I use based on the command below? and how does it affect the path cost of it?
Lets say i have 2 3750 switches stacked via backend stack cables. Now if a packet needs to go from 1 switch in the stack to second switch in the stack, will it travel via stack cable or do we need to connect both switches via uplink ports (ethernet or sfp). I tried reading datasheet but it no wheres mention the actual frame path between switches in stack.
we are planning a Nexus datacenter project with this layout:Our experiences with Nexus switches are not so large until now and the manuals are very extensive.Both N5K´s should be connected directly with all 4 N2K switches. I did not find a layout like this in the manuals. Only a design,where only 2 N2K are connected to one N5K, with this fex config:Now I´m not sure if it is right to make a config like this with the same slots and fex´s or with different slots and fex´s.
I have an issue that I am trying to track down. When I have 2 servers on the same VLAN on my AS pair, all is good because nothing leaves the switch. Where the issue is, is when I have 2 servers on different VLAN's and it requires a hop across the Core router pair. This hop drops the throughput rate by about 20-25% (from 44M to 35-36M)I think I know the issue, but want some input to from other to make sure I am not off-base. I have a pair of 6509E chassis' running Sup720 (VS-S720-10G) with CEF720 (X6748-GE-TX) modules. This is my Access Pair running VSS to look as 1 switch.
These tie into the Core pair of 6500E chassis' running Sup720 (Sup720-3B). This issue I see is that the core has a CEF720 card (6724-SFP), but the AS pair does not connect to the core on that card, they connect on a RJ45 Ethermodule (6148A-GE-TX) card. Would the fact that the AS pair does not connect to the core on the CEF7220 module on the core, cause the traffic to not make use of the CEF features of the Core and make each packet then have to be processed by the core instead of Express Forwarded?
I am in the process of upgrading our stack of 4 switches consist of WS-C3750G-48PS. Upon reading release notes found that there are two versions of release notes 1 day apart, the one 02 Sep 2012 saying that WS-C3750-48PS is not supported in this version. Then in release next day 03 Sep 2012 that note has been removed. Which one is correct. Is it supported with my model of switch or not.also unable to update boot path in the stack switches, "switch all" is not supported in the current IOS. Master switch has new boot path but unable to change in slaves.
have just set up a WLC 4402 as a Guest WLAN controller on the DMZ of our network. I have successfully managed to get our internal controllers to connect to it, with the exception of 1. it says the control path is up but the data path is down. the other 14 controllers worked fine, and in testing the last one was OK but it is now not working properly. the 2 controllers can ping each other but just won't create the data tunnel. there is a firewall in the middle but that has been set up to allow traffic between the 2 groups of controllers to be unrestricted.
the internal controllers are 4404's and all controllers are running the same version of code. 5.1.151.0.
I have a stack of 2 x 3750X switches these are running 12.2(55)SE5. I needed to add some static IP routes and found that the ‘ip routing’ command is not supported. I came across a document that stated “On switches running the LAN base feature, static routing on VLANs is supported only with Cisco IOS Release 12.2(58)SE and later.” So I have upgraded to 12.2(58)SE2, but ‘ip routing’ is still not a valid command.
The release notes state:“On the Cisco Catalyst 3560-X and 3750-X Series, it adds support for 16 static IPv4 routes in the LAN Base image.”
I have read other posts that talk about running the ‘sdm prefer routing’ command which I have done, but I am still unable to add any routes or run the ‘ip routing’ command.
I was trying to setup a Nexus (5596 running NX-OS 5.1(3)N2(1)) to use the "ip ospf name-lookup"command that I am using on IOS-based routers. Unfortunately this command does not appear to be supported on NX-OS and I cannot find a replacement.Is this another feature that's left out of NX-OS?
I've upgraded a 6509 switches wich are running in VSS, from IOS 12.2 (33)SHI1 to 12.2 (33)SHI5. After that I'm facing the folowing log messages periodically. [code] I know that this is a diagnostic result from TestUnusedPortLoopback feature. But this interface is disabled (shutdown).
I am trying to convince our Technical Lead that dual VSL links between our 6509-E chassis is a VERY good idea but he is fully convinced that the setup will work perfectly fine with only one VSL link. As I do agree that we can do this, I am looking for more concrete evidence that shows this would be a bad setup.
I know that we will lose the High Availably that comes with VSS, what I don't know is what will happen to all of the downstream switches that are connected and what will happen to the two 6509-E chassis..
Does the nexus 7010 support virtual switching yet? All of the posts I have found from about a year ago say that it is going to be supported, but there were no dates listed. I heard the same thing from Cisco a while back, but haven't followed up with it.If it is supported finally are there any configuration guides available for it?