SOLVED
Hi @adam900331 !
You have 3 options:
1. Replace switches one by one. This document will be helpful as an example of such replacement - https://internal.support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=sf000005597en_us
2. Replace both at once. For that you need to save the IRF's configuration to a file, renumber each new switch by 'irf member <current_id> renumber <new_id>', load the old backed up configuration _to each of new switches_, connect IRF cables and exectute 'irf-port-configuration active' command on both switches.
3. Reconfigure IRF stack from the scratch, if you want to follow that guide you've mentioned.
If you will use absolutely the same IRF ports numbers on both switches and both new switches will have same IRF member IDs as old ones, then yes, you should be able to restore the old configuration using "restore startup-configuration..." as the most straightforward option among several available.
If you will use those two DAC cables for IRF, it won't cause any loop, because IRF protocol has embedded loop prevention for the ports used for IRF. But I recommend you to avoid logical ring when you have only two IRF devices, instead use logical chain with two ports.
Instead of this:
irf-port 1/1
port group interface Ten-GigabitEthernet1/0/23
#
irf-port 1/2
port group interface Ten-GigabitEthernet1/0/24
#
irf-port 2/1
port group interface Ten-GigabitEthernet2/0/23
#
irf-port 2/2
port group interface Ten-GigabitEthernet2/0/24
Use this:
irf-port 1/1
port group interface Ten-GigabitEthernet1/0/23
port group interface Ten-GigabitEthernet1/0/24
#
irf-port 2/2
port group interface Ten-GigabitEthernet2/0/23
port group interface Ten-GigabitEthernet2/0/24
It provides same level of redundancy, but from IRF protocol's view there is no loop, because one logical port irf-port1/1 is connected to another logical port irf-port2/2. It's not like the first example will break something, as I already stated IRF protocol will take care of this "loop" over the IRF links, but on some models it's known to create issues, so better stay on the safe side and avoid logical IRF loop topology unless you have 3 and more IRF devices in the stack.
The configuration seems ok, but keep in mind that IP address 192.168.53.201 on the Standby (Slot 2) switch won't be active when the switch joins the stack, because Master's 192.168.53.200 will take precedense. Also, after you save the configuration when the stack is joined, that 192.168.53.201 will disappear from the saved-configuration as well. In other words if this IP will exist only while the switch is standalone in sake of access to the switch during initial IRF configuation, it's fine. Otherwise Vlan-interface on all IRF members should have same configuration. Just FYI.
Also, there is one suggestion, just to develop correct skills - do not execute "irf-port-configuration activate' BEFORE you saved the config with IRF physical ports in 'undo shutdown' state. It's ok to do this if you plan to connect IRF cables afterwards, but many times we have to configure already cabled devices from remote, so this order of operations will lead to problems after Standby reboots. It's a little bit tricky, but if you do this:
Int range t2/0/15 to t2/0/16
Undo shutdown
Irf-port-configuration activethe Standby will reboot right away and many times it will do it BEFORE you will have a chance to execute 'save force' and as a result it will boot with Ten2/015;Ten2/0/16 in 'shutdown' state.
Therefore the good practice is to swap the order of commands and make it like this:
Int range t2/0/15 to t2/0/16
Undo shutdown
quit
save safely force
Irf-port-configuration activeImportant fact: "IRF port active" state is not saved in the 'saved-configuration', therefore it won't hurt if you activate IRF ports after saving the config.
Keep in mind that I give you example with IRF ports on the Slot 2, but this is valid for ALL IRF members, not only for Standby. This is a simple rule that will potentially save you a LOT of troubles when configuring IRF stack will all cables already plugged in.
As I can see you prefer to configure your switch using CLI and since this switch is very GUI-centric, you need to use command reference and configuration guides for a device that is closest to 1950 by its features. You can use 5130 EI for this purpose. This is not 1:1 match, 5130 has much more features, but if youi have any doubts about the meaning of this or that command, its format etc, you can use docs for 5130 as a reference point. Check the Fundamentals Command Reference Guide for it here https://internal.support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c04771719 page 163 for the details of 'restore startup-configuration' command.
Another useful guide would be Fundamentals Configuration Guide - https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c04771704 page 109, "Restoring the main next-startup configuration file from a TFTP server" section.