We used to have one site with one Cisco switch to which a RANCID server was connected to take configuration backup.
A new site was opened, and we have another switch on this new site. The sites have the same IP network addressing, and we cannot change it, seriously.
We have a task to connect a second switch to the RANCID server, and this gives us a bit of a headache as the IP network addresses of the switches are the same.
The RANCID server connects to the switches via telnet (security is not important).
So, the question is - how to connect the RANCID server to both switches without making any changes on switches (minor changes can be done on switches only as last resort)?
It seemed to me that one of the solutions is to install a router between switches and RANCID Server and perform NAT port forwarding:
But we cannot do it as ports connected to the switches should be in the same subnet.
I thought about using PBR, but in any case both interfaces cannot be in the same subnet.
From one point of view it seems pointless to have on both interfaces the same subnet because "how will the router know to which interface to send packets", from another point I don't want the router to know where to send packets because I can manually specify what to do with packets that, for example, fall under PBR access-list
Could you please advise if there is solution of this problem of connecting RANCID to switches with the same IP?