[j-nsp] convert config from m120 to mx480

Chad Myers Chad.Myers at theice.com
Fri Oct 2 16:12:37 EDT 2015

Unless you have a need for two or more interfaces on the MX to be in the same broadcast domain, skip it.  It will keep the configuration much simpler.  You can create bridge-domain(s) in the future if you find a need for multiple interfaces to be in the same broadcast domain.


Chad Myers - Senior Network Architect
Intercontinental Exchange | ICE
5660 New Northside Dr. NW | 3rd Floor | Atlanta, GA 30328
chad.myers at theice.com

On Oct 2, 2015, at 1:08 PM, David B Funk <dbfunk at engineering.uiowa.edu> wrote:

> We have a venerable m120 that's being used as an edge router in our
> department on campus. We've recently acquired an mx480 as a replacement.
> I'm trying to decide the best way to port the m120 config to the mx480;
> Either a pretty much straight up port (strictly a L3 device) or try
> to convert it to a L2/L3 config that can utilize some of the switching
> features of the mx480.
> Anybody have suggestions or advice for this scenario?
> Thanks,
> Dave
> --
> Dave Funk                                  University of Iowa
> <dbfunk (at) engineering.uiowa.edu>        College of Engineering
> 319/335-5751   FAX: 319/384-0549           1256 Seamans Center
> Sys_admin/Postmaster/cell_admin            Iowa City, IA 52242-1527
> #include <std_disclaimer.h>
> Better is not better, 'standard' is better. B{
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp


This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of Intercontinental Exchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.

More information about the juniper-nsp mailing list