Juniper MX Series

Interface Bridge Configuration

The MX supports two methods of configuring interfaces for bridging, and each method has its own benefits and drawbacks. One method is geared for more control but requires additional configuration, and the other method is geared toward ease of use but offers less functionality. Both methods are covered in detail.

Service Provider Style

As mentioned previously in this chapter, Service Providers have very unique challenges in terms of providing both scale and Ethernet-based services to their customers. Such a solution requires extreme customization, flexibility, and scale. The drawback is that when crafting advanced bridging designs, the configuration becomes large. The obvious benefit is that all bridging features are available and can be arranged in any shape and size to provide the perfect Ethernet-based services for customers.

Enterprise Style

Typical Enterprise users only require traditional switching requirements. This means a single Layer 2 network with multiple bridge domains. Because the requirements are so simple and straightforward, the Juniper MX offers a simplified and condensed method to configure Layer 2 interfaces.

Basic Comparison of Service Provider versus Enterprise Style

Let’s start with a very basic example and create two bridge domains and associate two interfaces with each bridge domain, as shown in Figure 2-8, which would require the interfaces to use VLAN tagging.

Figure 2-8. Two interfaces and two bridge domains

Service Provider Style ...