No. Nothing sensitive is exported. No passwords. No SSH keys. No
system/host SSH keys. The only time you get those is in a binary backup.
And restoring a binary backup from one architecture to another is asking
for trouble. The only time I'd use it is when replacing with identical
hardware.
All of my routers generate a nightly .backup and .rsc. I have a bash
script on a couple CentOS machines that gets those via sftp. I have ssh
configured to ignore host keys so that if a router is replaced, it
doesn't fail because the entry in known_hosts is different. And part of
my setup/replacement procedure is making sure the pub key is uploaded
and imported.
On 5/31/2017 2:21 PM, Steve Jones wrote:
crumbs, I was hoping it would see the copper modules and name them
etherx, that's why I hadn't even booted it yet, waiting on those. no
big deal, just do a find and replace on the export.
Unimus backups are just compact exports aren't they, so the macs
should not come over and the keys/password should come with it if I
use those?
On Wed, May 31, 2017 at 1:27 PM, George Skorup
<[email protected] <mailto:[email protected]>> wrote:
Just remember that you'll be going from etherX to sfpX interface
names, so you'll have to edit the export and adjust interface
names for IP addresses, OSPF interfaces, VLANs, etc.
On 5/31/2017 10:47 AM, Colin Stanners wrote:
I can't say for sure without seeing the config, but usually just
remove MAC addresses and L2MTU settings in config.
On Wed, May 31, 2017 at 10:24 AM, Steve Jones
<[email protected] <mailto:[email protected]>> wrote:
is there any major difference? we will be using the copper
modules, not fiber is it a simple compact export
