Home . Pricing Information . TRAINING . Pay for Services . Articles . Forum . Links . Available Mailing Lists . Visit my blogThursday, September 09, 2010
Navigation
Home
View my Calendar
Photo Gallery
FAQ
Forum
Contact Me
Links
Search
Users Online
Guests Online: 1
No Members Online

Registered Members: 251
Unactivated Members: 114
Newest Member: went1and
Forum Threads
Newest Threads
Packet Per Sec
Failover with NAT
Mikrotik Software
Service dropoff
antenna freq range
Hottest Threads
Packet Per Sec [2]
Failover with NAT [1]
Mikrotik Software [1]
exporting dynamic... [1]
Syslog Export [1]
Paypal Payments Accepted
Solution Graphics
Text Based Backups (/export)
Posted by butche on September 19 2006 21:08

Good question.  There is not a simple answer, either.  The basics are this:


1. Do the export
2. Transfer the file to your laptop/workstation
3. Edit the file in notepad and save it
4. Transfer the edited file to the new system
5. Run "/import file=FILENAME" in a terminal window


The only part of this that needs expansion is number 3.


When I edit these files, here are the things that I do:

1. In the /interface ethernet portion, you need to remove the excess "fluff" from this line.  If the interface name is not at it's default value (ether1, ether2, etc.) you have to account for that. Here are a couple of examples (they've already been edited down):

/ interface ethernet

set ether1 name="Public_ether1" auto-negotiation=no \
    full-duplex=yes speed=100Mbps disabled=no

set ether2 name="LAN_ether2"


These 2 entries show a couple of interfaces that have had their name changed and one of them has turned off auto-negotiation.  All the other settings that were in the file for these ports were default settings (mac-address, mtu, etc.) and were removed from the backup. 
(NOTE: If you leave all the other settings there, everything will work as expected, BUT YOU MUST REMOVE THE REFERENCES TO THE MAC ADDRESS!)

2. Go through the file and remove the settings that are default. For example, you can generally remove these (and some other) sections entirely:

/interface wireless align
/interface wireless snooper
/tool e-mail
/tool sniffer


There are many sections like that, that are in the export, but are not needed to move a config from one router to another


3. Check the /queue simple and /queue tree and remove some of their excess settings.  This takes a LOT of experimenting to get it right if you are not familiar with what parts are needed and which are "fluff".


My experience is that a simple config will be only 15-30 lines after it is edited.  Of course, if you have firewalls or queues it will be longer.

Comments
No Comments have been Posted.
Post Comment
Please Login to Post a Comment.
Ratings
Rating is available to Members only.

Please login or register to vote.

No Ratings have been Posted.
Login
Username

Password



Not a member yet?
Click here to register.

Forgotten your password?
Request a new one here.
WISPA
Member Poll
In what area do you most lack expertise? (What area would you like to learn more about?)

Security (firewalls)

Routing (static)

Scripting (automation)

Basic TCP/IP information

OSPF/Dynamic Routing

Other (you can leave a comment)

You must login to vote.
Newsletter
Members only