Question about migration between core switches

[camelot1969]

Hello, 

I am hoping that someone here can point me in the right direction.  We are currently using a Cisco Nexus 5596 as our core switch and the directive has been given to migrate to a Cisco C9407R.  Everything that I have found online in the way of facilitating this is in the opposite direction i.e. going from a regular Cisco TO a Nexus switch; not the other way around. Even the tool I did find going from a Cisco to a Nexus doesn't even cover our version/model so I can even do a reverse comparison of some kind.

I am really HOPING that this isnt a situation where we will have to do a trial and error trying to get this to work?

Has anyone else run into this type of situation before?

[Richard Burts]

I do not have experience with that platform so can not speak from experience. In general I would expect some syntax differences in commands so a simple copy of config loaded on new switch is likely not going to work. If you do that you could look for any errors or warnings generated and work to resolve them. I would be inclined to do a section at a time taking parts of existing config and apply to new switch, resolving issues as they are encountered. We do not know what features you are using on the existing switch so it is difficult to predict how easy/how challenging the transition will be. Good luck with it.

[camelot1969]

Thank you Richard.  I believe that I have managed to piece together what I need from the Nexus over to the 9407. What I am seeing in my testing though is that while it will pass L2 traffic just fine; it is NOT passing L3, so I am wondering if I need a specific license for that?

[Richard Burts]

It is possible that it might be an issue with licensing. But let's start with easy stuff. Have you enabled ip routing on the 9407?

[camelot1969]

How can I tell if that's the case?  show run all | begin ip routing gets me a lot of data but I am not experienced enough at this stage to know if that means it is actually enabled or not. (It goes on for quite a few pages so I just put an abridged portion below:

ip routing protocol purge interface
ip routing
no ip arp proxy disable
ip arp queue 512
ip arp incomplete retry 20
ip arp incomplete entries 5000
ip arp incomplete enable
ip sticky-arp
ip gratuitous-arps non-local
ip icmp rate-limit unreachable 500
ip icmp redirect subnet
ip spd queue max-threshold 74
ip spd queue min-threshold 73
ip verify drop-rate compute window 300
ip verify drop-rate compute interval 30
ip verify drop-rate notify hold-down 300
!
!
!
ip nbar classification dns classify-by-domain
!
!
ip admission ratelimit 100
no ip admission watch-list enable
ip admission watch-list expiry-time 10
ip admission max-login-attempts 5
ip admission init-state-time 2
no ip admission auth-proxy-audit
ip admission inactivity-timer 60
ip admission absolute-timer 0
ip sap cache-timeout 1440
ip multicast redundancy routeflush maxtime 30
ip multicast route-limit 2147483647
ip pgm host ttl 255
ip pgm host stream-type apdu
ip pgm host nak-gen-ivl 60000
ip pgm host nak-rb-ivl 500
ip pgm host nak-rpt-ivl 2000
ip pgm host nak-rdata-ivl 2000
ip pgm host rx-buffer-mgmt minimum
ip pgm host tpdu-size 1400
ip pgm host ihb-min 1000
ip pgm host ihb-max 10000
ip pgm host join 0
ip pgm host spm-ambient-ivl 6000
ip pgm host txw-adv-secs 6000
ip pgm host txw-adv-timeout-max 3600000
ip pgm host txw-rte 16384
ip pgm host txw-secs 30000
ip pgm host ncf-max 4294967295
ip pgm host spm-rpt-ivl 3000
ip pgm host tx-buffer-mgmt return
ip pgm host txw-adv-method time
ip pgm router elimination-interval 2
no ip bootp server
no ip hostname strict
ip name-server 8.8.8.8 1.1.1.1
ip domain timeout 5
ip domain periodic-resolve 240
no ip domain lookup recursive
ip domain lookup
ip domain lookup nsap
ip domain name sasholdings.local
ip domain multicast in-addr.arpa
ip domain recursive retry 10
no ip domain recursive allow-soa
ip dhcp-server query lease retries 2
ip dhcp-server query lease timeout 10

[Richard Burts]

Thanks for the additional information. You asked "How can I tell if that's the case?". The answer is in the second line of your output "ip routing". So routing is enabled. That eliminates one potential source of the problem. I would like to start from the high levels of the protocols and work down to lower level/more detailed levels as necessary. So would you post the output of these commands:

show ip protocol

show ip interface brief

show ip route

show arp

It would also be helpful if you would tell us about your testing for L3, starting with what device/what IP is the source and what device/what IP is the destination for L3 traffic.

[camelot1969]

show ip protocol
*** IP Routing is NSF aware ***

show ip interface brief
Interface IP-Address OK? Method Status Protocol
Vlan1 unassigned YES NVRAM administratively down down
Vlan230 10.1.168.2 YES NVRAM up up
GigabitEthernet0/0 unassigned YES NVRAM administratively down down
GigabitEthernet1/0/1 unassigned YES unset down down
GigabitEthernet1/0/2 unassigned YES unset up up
GigabitEthernet1/0/3 unassigned YES unset up up
GigabitEthernet1/0/4 unassigned YES unset up up
GigabitEthernet1/0/5 unassigned YES unset up up
GigabitEthernet1/0/6 unassigned YES unset up up
GigabitEthernet1/0/7 unassigned YES unset up up
GigabitEthernet1/0/8 unassigned YES unset down down
GigabitEthernet1/0/9 unassigned YES unset up up
GigabitEthernet1/0/10 unassigned YES unset up up
GigabitEthernet1/0/11 unassigned YES unset up up
GigabitEthernet1/0/12 unassigned YES unset down down
GigabitEthernet1/0/13 unassigned YES unset down down
GigabitEthernet1/0/14 unassigned YES unset down down
GigabitEthernet1/0/15 unassigned YES unset down down
GigabitEthernet1/0/16 unassigned YES unset down down
GigabitEthernet1/0/17 unassigned YES unset down down
GigabitEthernet1/0/18 unassigned YES unset down down
GigabitEthernet1/0/19 unassigned YES unset down down
GigabitEthernet1/0/20 unassigned YES unset down down
GigabitEthernet1/0/21 unassigned YES unset down down
GigabitEthernet1/0/22 unassigned YES unset down down
GigabitEthernet1/0/23 unassigned YES unset down down
GigabitEthernet1/0/24 unassigned YES unset down down
GigabitEthernet1/0/25 unassigned YES unset down down
GigabitEthernet1/0/26 unassigned YES unset down down
GigabitEthernet1/0/27 unassigned YES unset down down
GigabitEthernet1/0/28 unassigned YES unset down down
GigabitEthernet1/0/29 unassigned YES unset down down
GigabitEthernet1/0/30 unassigned YES unset down down
GigabitEthernet1/0/31 unassigned YES unset down down
GigabitEthernet1/0/32 unassigned YES unset down down
GigabitEthernet1/0/33 unassigned YES unset down down
GigabitEthernet1/0/34 unassigned YES unset down down
GigabitEthernet1/0/35 unassigned YES unset down down
GigabitEthernet1/0/36 unassigned YES unset down down
GigabitEthernet1/0/37 unassigned YES unset down down
GigabitEthernet1/0/38 unassigned YES unset down down
GigabitEthernet1/0/39 unassigned YES unset down down
GigabitEthernet1/0/40 unassigned YES unset down down
GigabitEthernet1/0/41 unassigned YES unset down down
GigabitEthernet1/0/42 unassigned YES unset down down
GigabitEthernet1/0/43 unassigned YES unset down down
GigabitEthernet1/0/44 unassigned YES unset down down
GigabitEthernet1/0/45 unassigned YES unset down down
GigabitEthernet1/0/46 unassigned YES unset down down
GigabitEthernet1/0/47 unassigned YES unset down down
GigabitEthernet1/0/48 unassigned YES unset down down
GigabitEthernet2/0/1 unassigned YES unset up up
GigabitEthernet2/0/2 unassigned YES unset up up
GigabitEthernet2/0/3 unassigned YES unset down down
GigabitEthernet2/0/4 unassigned YES unset up up
GigabitEthernet2/0/5 unassigned YES unset up up
GigabitEthernet2/0/6 unassigned YES unset up up
GigabitEthernet2/0/7 unassigned YES unset up up
GigabitEthernet2/0/8 unassigned YES unset down down
GigabitEthernet2/0/9 unassigned YES unset up up
GigabitEthernet2/0/10 unassigned YES unset up up
GigabitEthernet2/0/11 unassigned YES unset down down
GigabitEthernet2/0/12 unassigned YES unset down down
GigabitEthernet2/0/13 unassigned YES unset down down
GigabitEthernet2/0/14 unassigned YES unset down down
GigabitEthernet2/0/15 unassigned YES unset down down
GigabitEthernet2/0/16 unassigned YES unset down down
GigabitEthernet2/0/17 unassigned YES unset down down
GigabitEthernet2/0/18 unassigned YES unset down down
GigabitEthernet2/0/19 unassigned YES unset down down
GigabitEthernet2/0/20 unassigned YES unset down down
GigabitEthernet2/0/21 unassigned YES unset down down
GigabitEthernet2/0/22 unassigned YES unset down down
GigabitEthernet2/0/23 unassigned YES unset down down
GigabitEthernet2/0/24 unassigned YES unset down down
GigabitEthernet2/0/25 unassigned YES unset down down
GigabitEthernet2/0/26 unassigned YES unset down down
GigabitEthernet2/0/27 unassigned YES unset down down
GigabitEthernet2/0/28 unassigned YES unset down down
GigabitEthernet2/0/29 unassigned YES unset down down
GigabitEthernet2/0/30 unassigned YES unset down down
GigabitEthernet2/0/31 unassigned YES unset down down
GigabitEthernet2/0/32 unassigned YES unset down down
GigabitEthernet2/0/33 unassigned YES unset down down
GigabitEthernet2/0/34 unassigned YES unset down down
GigabitEthernet2/0/35 unassigned YES unset down down
GigabitEthernet2/0/36 unassigned YES unset down down
GigabitEthernet2/0/37 unassigned YES unset down down
GigabitEthernet2/0/38 unassigned YES unset down down
GigabitEthernet2/0/39 unassigned YES unset down down
GigabitEthernet2/0/40 unassigned YES unset down down
GigabitEthernet2/0/41 unassigned YES unset down down
GigabitEthernet2/0/42 unassigned YES unset down down
GigabitEthernet2/0/43 unassigned YES unset down down
GigabitEthernet2/0/44 unassigned YES unset down down
GigabitEthernet2/0/45 unassigned YES unset down down
GigabitEthernet2/0/46 unassigned YES unset down down
GigabitEthernet2/0/47 unassigned YES unset down down
GigabitEthernet2/0/48 unassigned YES unset down down
Te3/0/1 unassigned YES unset down down
Te3/0/2 unassigned YES unset down down
Te3/0/3 unassigned YES unset down down
Te3/0/4 unassigned YES unset down down
Te3/0/5 unassigned YES unset down down
Te3/0/6 unassigned YES unset down down
Te3/0/7 unassigned YES unset down down
Te3/0/8 unassigned YES unset down down
Fo3/0/9 unassigned YES unset down down
Fo3/0/10 unassigned YES unset down down
Te4/0/1 unassigned YES unset down down
Te4/0/2 unassigned YES unset down down
Te4/0/3 unassigned YES unset down down
Te4/0/4 unassigned YES unset down down
Te4/0/5 unassigned YES unset down down
Te4/0/6 unassigned YES unset down down
Te4/0/7 unassigned YES unset down down
Te4/0/8 unassigned YES unset down down
Fo4/0/9 unassigned YES unset down down
Fo4/0/10 unassigned YES unset down down
Te5/0/1 unassigned YES unset up up
Te5/0/2 unassigned YES unset up up
Te5/0/3 unassigned YES unset up up
Te5/0/4 unassigned YES unset up up
Te5/0/5 unassigned YES unset down down
Te5/0/6 unassigned YES unset down down
Te5/0/7 unassigned YES unset down down
Te5/0/8 unassigned YES unset down down
Te5/0/9 unassigned YES unset down down
Te5/0/10 unassigned YES unset down down
Te5/0/11 unassigned YES unset down down
Te5/0/12 unassigned YES unset down down
Te5/0/13 unassigned YES unset up up
Te5/0/14 unassigned YES unset down down
Te5/0/15 unassigned YES unset down down
Te5/0/16 unassigned YES unset down down
Te5/0/17 unassigned YES unset down down
Te5/0/18 unassigned YES unset down down
Te5/0/19 unassigned YES unset down down
Te5/0/20 unassigned YES unset down down
Te5/0/21 unassigned YES unset down down
Te5/0/22 unassigned YES unset down down
Te5/0/23 unassigned YES unset down down
Te5/0/24 unassigned YES unset down down
Te6/0/1 unassigned YES unset up up
Te6/0/2 unassigned YES unset up up
Te6/0/3 unassigned YES unset up up
Te6/0/4 unassigned YES unset down down
Te6/0/5 unassigned YES unset down down
Te6/0/6 unassigned YES unset down down
Te6/0/7 unassigned YES unset down down
Te6/0/8 unassigned YES unset down down
Te6/0/9 unassigned YES unset down down
Te6/0/10 unassigned YES unset down down
Te6/0/11 unassigned YES unset down down
Te6/0/12 unassigned YES unset down down
Te6/0/13 unassigned YES unset up up
Te6/0/14 unassigned YES unset down down
Te6/0/15 unassigned YES unset down down
Te6/0/16 unassigned YES unset down down
Te6/0/17 unassigned YES unset down down
Te6/0/18 unassigned YES unset down down
Te6/0/19 unassigned YES unset down down
Te6/0/20 unassigned YES unset down down
Te6/0/21 unassigned YES unset down down
Te6/0/22 unassigned YES unset down down
Te6/0/23 unassigned YES unset down down
Te6/0/24 unassigned YES unset down down
Port-channel9 unassigned YES unset up up
Port-channel13 unassigned YES unset up up

show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, m - OMP
n - NAT, Ni - NAT inside, No - NAT outside, Nd - NAT DIA
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
H - NHRP, G - NHRP registered, g - NHRP registration summary
o - ODR, P - periodic downloaded static route, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is 10.1.168.1 to network 0.0.0.0

S* 0.0.0.0/0 [1/0] via 10.1.168.1
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.1.168.0/24 is directly connected, Vlan230
L 10.1.168.2/32 is directly connected, Vlan230

show arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.1.168.1 10 8c60.4f58.58c1 ARPA Vlan230
Internet 10.1.168.2 - 7061.7bea.f6aa ARPA Vlan230

As to the last part of your question; initially there is connectivity out to the internet from the core switch. I can ping out, traceroute, etc. Within 60 seconds or so; connectivity to the internet is gone and am unable to get it back.

[Richard Burts]

Thanks for the additional information. Am I correct in assuming that you are doing your testing from the 9407? It might be helpful to see the output of a traceroute to some remote destination.

What is the device at 10.1.168.1? At this point I am wondering if the issue is something between your 9407 and that device.

[camelot1969]

Yes sir. You are correct. That last part is a bit deceptive. My apologies. 10.1.168.1 is the IP of the Nexus core switch itself that we are trying to switch from ultimately.  As of right now since we tried previously tried and failed to cutover before;  the Nexus is still the hop when anything tries to leave as we had to put it back in play.   What THAT looks like (and what I assume the new core is supposed to look like when the Nexus is removed is :

traceroute to yahoo.com (98.137.11.164), 30 hops max, 40 byte packets
1 10.1.168.254 (10.1.168.254) 0.909 ms 0.779 ms 0.898 ms
2 174.136.151.65 (174.136.151.65) 3.298 ms 10.288 ms 14.654 ms
3 208.81.181.93 (208.81.181.93) 1.199 ms 1.116 ms 4.758 ms
4 38.32.16.49 (38.32.16.49) 1.736 ms 1.81 ms 1.593 ms
5 te0-0-2-0.rcr11.dtw02.atlas.cogentco.com (154.24.62.225) 1.839 ms 1.846 ms te0-0-2-0.rcr12.dtw02.atlas.cogentco.com (154.24.64.109) 1.836 ms
6 te0-5-1-2.rcr21.dtw04.atlas.cogentco.com (154.24.64.85) 2.538 ms te0-1-0-8.rcr21.dtw04.atlas.cogentco.com (154.24.64.89) 1.989 ms te0-5-1-2.rcr21.dtw04.atlas.cogentco.com (154.24.64.85) 2.393 ms
7 be2123.rcr51.tol01.atlas.cogentco.com (154.54.82.137) 3.64 ms 13.665 ms 3.372 ms
8 be3744.ccr21.cle04.atlas.cogentco.com (154.54.0.145) 14.917 ms 6.044 ms 5.764 ms
9 * level3.cle04.atlas.cogentco.com (154.54.10.66) 24.638 ms 24.577 ms
10 * * *
11 YAHOO-INC.ear2.Seattle1.Level3.net (4.16.146.58) 62.706 ms 60.039 ms YAHOO-INC.ear3.Seattle1.Level3.net (4.16.168.186) 61.35 ms
12 ae-10.pat2.gqb.yahoo.com (209.191.65.51) 59.725 ms ae-7.pat2.gqb.yahoo.com (209.191.65.45) 60.384 ms 76.244 ms
13 et-0-0-0.msr1.gq1.yahoo.com (66.196.67.97) 61.431 ms et-1-0-0.msr2.gq1.yahoo.com (66.196.67.113) 89.198 ms et-18-1-0.msr1.gq1.yahoo.com (66.196.67.103) 61.246 ms
14 et-19-0-0.clr1-a-gdc.gq2.yahoo.com (98.136.158.213) 69.579 ms et-1-1-0.clr2-a-gdc.gq2.yahoo.com (98.136.158.175) 67.156 ms et-19-0-0.clr1-a-gdc.gq2.yahoo.com (98.136.158.213) 60.017 ms
15 lo0.fab7-1-gdc.gq2.yahoo.com (98.136.159.241) 61.445 ms lo0.fab1-1-gdc.gq2.yahoo.com (98.136.159.247) 67.184 ms lo0.fab7-1-gdc.gq2.yahoo.com (98.136.159.241) 61.473 ms
16 usw1-1-lbc.gq2.yahoo.com (98.136.158.192) 60.562 ms usw2-1-lbc.gq2.yahoo.com (98.136.158.193) 61.518 ms usw1-1-lbc.gq2.yahoo.com (98.136.158.192) 60.345 ms
17 media-router-fp73.prod.media.vip.gq1.yahoo.com (98.137.11.164) 61.413 ms 61.26 ms 61.375 ms

What the Cisco core switch looks like now with the Nexus still in place is this:

Tracing the route to media-router-fp74.prod.media.vip.gq1.yahoo.com (98.137.11.163)
VRF info: (vrf in name/id, vrf out name/id)
1 10.1.168.1 1 msec 0 msec 1 msec
2 10.1.168.254 0 msec 0 msec 0 msec
3 174.136.151.65 9 msec 13 msec 3 msec
4 208.81.181.93 0 msec 2 msec 3 msec
5 38.32.16.49 1 msec 1 msec 1 msec
6 te0-0-2-0.rcr11.dtw02.atlas.cogentco.com (154.24.62.225) 2 msec
te0-0-2-0.rcr12.dtw02.atlas.cogentco.com (154.24.64.109) 1 msec
te0-0-2-0.rcr11.dtw02.atlas.cogentco.com (154.24.62.225) 2 msec
7 te0-7-0-8.rcr21.dtw04.atlas.cogentco.com (154.24.32.121) 2 msec
te0-0-1-2.rcr21.dtw04.atlas.cogentco.com (154.24.64.81) 2 msec
te0-5-1-2.rcr21.dtw04.atlas.cogentco.com (154.24.64.85) 2 msec
8 be2123.rcr51.tol01.atlas.cogentco.com (154.54.82.137) 3 msec 3 msec 3 msec
9 be3744.ccr21.cle04.atlas.cogentco.com (154.54.0.145) 6 msec 6 msec 5 msec
10 * *
level3.cle04.atlas.cogentco.com (154.54.10.66) 24 msec
11 * * *
12 YAHOO-INC.ear2.Seattle1.Level3.net (4.16.146.58) 60 msec
YAHOO-INC.ear3.Seattle1.Level3.net (4.16.168.186) 61 msec 61 msec
13 ae-7.pat2.gqb.yahoo.com (209.191.65.45) 60 msec
ae-5.pat1.gqb.yahoo.com (209.191.65.49) 61 msec
ae-10.pat2.gqb.yahoo.com (209.191.65.51) 61 msec
14 et-0-0-0.msr1.gq2.yahoo.com (66.196.67.29) 60 msec
et-1-0-0.msr2.gq2.yahoo.com (66.196.67.125) 62 msec
et-0-0-0.msr2.gq2.yahoo.com (66.196.67.117) 60 msec
15 et-19-0-0.clr1-a-gdc.gq2.yahoo.com (98.136.158.213) 62 msec
et-0-0-0.clr2-a-gdc.gq2.yahoo.com (98.136.158.183) 61 msec
et-19-1-0.clr1-a-gdc.gq2.yahoo.com (98.136.158.201) 59 msec
16 lo0.fab6-1-gdc.gq2.yahoo.com (98.136.159.242) 61 msec
lo0.fab4-1-gdc.gq2.yahoo.com (98.136.159.244) 61 msec
lo0.fab5-1-gdc.gq2.yahoo.com (98.136.159.243) 60 msec
17 usw2-1-lbc.gq2.yahoo.com (98.136.158.193) 60 msec 59 msec
usw1-1-lbc.gq2.yahoo.com (98.136.158.192) 62 msec
18 media-router-fp74.prod.media.vip.gq1.yahoo.com (98.137.11.163) 60 msec 59 msec 60 msec

[Richard Burts]

Thanks for the additional information. I am a bit puzzled. In the previous post you indicated that the new switch was not passing layer 3 traffic. But the output in the most recent post shows traceroute getting out to the Internet. So what is not working.

I agree with Paul that there are things that you need to add to the configuration for it to be able to replace the existing core switch. But in terms of testing basic functionality it looks to me like it is working.

[paul driver]

Hello
You need to have a Layer2 & Layer 3 connection between old and new core switches, so to be able to migrate any L2 trunk interconnects onto the new core  but also allow thatr new core to eventually perform the intervlan routing- This is something you don’t seem to have?

Once you have the correct interconnections between old/new cores, Begin with any L2 trunks, then enable ip routing on the new core and start to relocate the L3 interfaces (svis) one by one making sure you disable the old L3 interface on the old core first?

Lasty once all L3 svis have been relocated, you can move the wan connection (if applicable) and any static/default routes and shutdown OLD core.

[camelot1969]

Quite right.  Perhaps I am failing to properly explain the situation.  I have attached a VERY basic diagram of the situation and maybe that will help where my explanation is failing.  Right now both switches are both online and running. What will be the NEW core switch is currently sitting "behind" the Nexus switch; so to respond to Paul ; all traffic and routing are already running through the Cisco and thats all it is doing.  The issue is that when we remove the Nexus from the equation by shutting it down and giving the new core switch the IP of the Nexus, enabling the WAN on the Cisco, etc.; it still does everything it is supposed to internally; vlans can talk to each other, etc. but the new Cisco core simply stops talking to the internet; wont pass a thing out to the internet after about 60 seconds to a minute as if for some reason it is either still looking for the Nexus to route out to the internet or what I asked earlier; it needs some license it doesn't have. 

[paul driver · Accepted solution]

Hello

---

@camelot1969 wrote:

The issue is that when we remove the Nexus from the equation by shutting it down and giving the new core switch the IP of the Nexus, enabling the WAN on the Cisco, etc.; it still does everything it is supposed to internally; vlans can talk to each other, etc.

---

When you cut over to the Cisco, try spoofing the mac-address of the nexus onto the cisco for that routed interface.
(Meaning give the cisco the same mac-address the nexus has)

[Richard Burts]

You are describing things in generalities "when we remove the Nexus from the equation by shutting it down and giving the new core switch the IP of the Nexus, enabling the WAN on the Cisco, etc.". Perhaps some specifics about enabling the WAN and etc would help us understand the issue a bit better.

I am also wondering about your statement that you shut down the Nexus. I am looking at your diagram which seems to show the the 9407 connection to outside is through the Nexus. If the Nexus is shut down how does the 9407 get out?

I am still trying to understand the traceroute information that you provided. It seems to show that the 9407 does have connectivity to the Internet. 

[camelot1969]

Sorry guys, I was trying to create a quick diagram to give an idea of how things are currently set up and made it worse..lol..so starting from the traceroute info; what you are seeing from the 9407 is what it looks like with the Nexus in "front" as you stated. I unfortunately dont have a traceroute of what it looks like without the Nexus in front as I wasn't thinking at the time to capture the traceroute when we tried to cut over and failed; so the "how" it is getting out to the internet now is because the next hop for it is the Nexus which then takes it out. As to the second part, my THOUGHT was (and maybe that is what is flawed here) is that all I would need to do once the vlans and routes were replicated over to the 9407; that all I needed to do at that point was re-ip my 9407 to use the same static IP and GW that the Nexus was using and move the WAN connection from the Nexus TO the pre-configured WAN port on the 9407. That is what I meant by "enabling" the WAN on the Cisco.  Sorry of this is frustrating.  Like I said, this is my first time having to do a core swap with two different types of switches.