Nexus 5k to 9K upgrade

[TroyBolton]

Hi,

I'm currently tasked with an upgrade 5 switches, from 5Ks to 9Ks.

I haven't done an upgrade before FYI.

Now, i've been told that it's literally a same swap, configs are the same nothing's changed.

Realistically i can go through the configs and literally copy or should i say implement them onto the new 9Ks

Say for instance on the current switch, there's a Vlan say Vlan 12, configured, and that Vlan has an IP of 192.168.0.4/24, would i just literally copy that into the 9K switch or?

Is there a checklist as to a procedure for straight swap migrations?

Thanks

[marce1000]

 - Theoretically it should work, if the previous 5K switches are turned off , if there is a transition faze, I would advise to reserve an extra few  /new ip-addresses for the vlans on the 9k's.

 M.

[TroyBolton]

@marce1000 what would the be the benefit of reserving new IP addresses?

[marce1000]

 - To avoid accidental conflict with equipment still in place.

    M.

[TroyBolton]

Ok so the new switches are already powered on and patched and racked and I've nearly finished copying over the configs, so on the day of implementation what would be the process to make the new switch live? @marce1000 

[marce1000]

 - I guess just turning them on, and connect some none-vital equipment first , check whether networking is OK on these test-connections.

 M.

[TroyBolton]

For some reason i cant copy this onto the 9K

interface Ethernet102/1/30
  description [srv,rd=no-mon]
  shutdown
  switchport access vlan 404
  spanning-tree port type edge
  spanning-tree guard root
  link debounce time 10
  no snmp trap link-status
  logging event port link-status

i get this

is102-is.bllab(config)# interface Ethernet102/1/30
                                                 ^
Invalid range at '^' marker.
is102-is.bllab(config)#   description [srv,rd=no-mon]
                          ^
% Invalid command at '^' marker.
is102-is.bllab(config)#   shutdown
                          ^
% Invalid command at '^' marker.
is102-is.bllab(config)#   switchport access vlan 404
                              ^  spanning-tree port type edge

% Invalid command at '^' marker.
is102-is.bllab(config)#   spanning-tree port type edge
                                                    ^
% Incomplete command at '^' marker.
is102-is.bllab(config)#   spanning-tree guard root
                                      ^
% Invalid command at '^' marker.
is102-is.bllab(config)#   link debounce time 10
                           ^
% Invalid command at '^' marker.
is102-is.bllab(config)#   no snmp trap link-status
                                ^
% Invalid command at '^' marker.
is102-is.bllab(config)#   logging event port link-status
                                      ^
% Invalid command at '^' marker

@marce1000 @Reza Sharifi 

[marce1000]

 - Of course on the 9K your interface may have different names and you need to adapt the configuration accordingly , you can list the available interfaces with names using show interface status.

 M.

[Reza Sharifi · Accepted solution]

Hi,

Yes, the config should remain the same. You should be able to copy from the 5ks to notepad and than paste into the 9ks. If some commands are rejected due to a different (newer) OS on the 9ks, you can simply modify the config on the notepad and than paste in to the 9ks. If you are using the same exact IPs from the 5ks on the 9ks, make sure one switch at the time is on the network so you don't see duplicate IP. If you are using a different IP on the new switch, than they both can be on the network at the same time. It is usually better to use different IP on the new switch if possible. 

HTH

[TroyBolton]

Can you elaborate on "copying"? Are you saying sh run and copy? @Reza Sharifi 

[Reza Sharifi]

So, on the 5ks, after you login, just do a "sh run" and than copy from the 5ks and paste it into notepad or notepad++. From there you copy to the 9ks. When pasting into the new switch, try to paste a few lines at a time (20 to 30 lines) just in case there is an error. 

HTH

[Reza Sharifi]

BTW, on the nexus series, you can run below command to see the entire show run at once and than copy it.

sh run | no-more

HTH 

[TroyBolton]

From the the CLI how am i pasting it into it? Do i enter enabled mode and just paste the config bit by bit? @Reza Sharifi 

[Reza Sharifi]

Yes, you need to be in enable mode first.

HTH

[TroyBolton]

@Reza Sharifi about to get started today.

So i have a 9K to play with/test random config before i implement onto the actually production 9K's

I've literally copied 

feature pim
feature msdp
feature udld
feature interface-vlan
feature dot1x
feature hsrp



logging level cdp 6
logging level feature-mgr 0
logging level hsrp 5
logging level lldp 5

no pasting that into the conf t line of the switch im just getting:

R1#en
R1#logging level aaa 5
      ^
% Invalid input detected at '^' marker.

R1#logging level cdp 6
      ^
% Invalid input detected at '^' marker.

R1#logging level feature-mgr 0
      ^
% Invalid input detected at '^' marker.

R1#logging level hsrp 5
      ^
% Invalid input detected at '^' marker.

R1#logging level lldp 5
      ^
% Invalid input detected at '^' marker.

R1#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#logging level aaa 5
Translating "level"
                   ^
% Invalid input detected at '^' marker.

R1(config)#logging level cdp 6
                   ^
% Invalid input detected at '^' marker.

R1(config)#logging level feature-mgr 0
                   ^
% Invalid input detected at '^' marker.

R1(config)#logging level hsrp 5
                   ^
% Invalid input detected at '^' marker.

R1(config)#logging level lldp 5
                   ^
% Invalid input detected at '^' marker.