I had to replace a CCR-1036 core router today in the data centre.
Everything is ok and traffic levels on the core switches is correct.
However the built in graphs on router OS are now wrong since the change over.
I uploaded the config of the bad router to the replacement router. The bad router had an intermittent PSU problem so no issue uploading config, so the original graphs have also copied to the new router.
Has anyone seen this before, if I was to believe the Router interface graphs traffic levels are down by 200Mbps but this is not the case as is evident in the core switches graphs.
Is there a way to wipe the historical graphs and start afresh?
One thing to note is the sofware on the replacement is 6.45.6, the failed router was 6.45.7. I don’t want to upgrade software right now as it will cause an outage and there has been enough customer grief already this week with the flaky PSU in the failed system.
Max traffic is usually 1.5Gbps. Yes i used backup file from failed router and loaded it on the new router. BTW failed router is totally dead now PSU buzzes so got there in time.
As far as I know using backup file is only supported on the same device. So if you are to move config export / import is what you must use.
Don’t really know what can go wrong with using a backup file but I think it will replace stuff like Mac address and use the old one etc.
Guessing this is what causing your issues.
Indeed, restoring a backup is not a completely safe thing to do.
I would probably /export the current config (as your old router is dead), hand-edit it to remove all MAC address parameters from things like ethernet ports, but also from bridges.
When removing a MAC address from a bridge, make a note.
Then connect from a local winbox in MAC address mode, reset all configuration and import the /exported file, and finally go back to the bridges where an admin-mac was present
and again set it (to the value that the bridge took automatically).
Then everything will probably work OK again. As far as OK goes in this case, because it is wellknown that traffic graphing does not work completely OK on high traffic ports because of 32-bit value wraparound issues.