Knowledge Search


×
 

[MX] Example - Interface Bridge Configuration: Enterprise vs Service Provider style

  [KB27291] Show Article Properties


Summary:

The MX Series supports two methods of configuring bridge interfaces: enterprise and service provider style. This article explains each method.

Symptoms:

What is the difference between enterprise and service provider style configuration of a bridge interface on the MX Series?

Cause:

Service provider style requires explicit configuration of each feature on the interface, and the bridge domains need to reference the interface.

Enterprise style does not require explicit configuration for each feature, which reduces the amount of configuration but also reduces the number of features.

Solution:
Refer to the example equivalent configurations.
 

Service Provider Style

Configuring Service provider style requires:

  • vlan-tagging
  • encapsulation
  • unit

Example:

interfaces {
       ge-0/0/0 {
            vlan-tagging;
            encapsulation extended-vlan-bridge;
            unit 1 {
                   vlan-id 1;
            }
            unit 2 {
                  vlan-id 2;
            }
      }
      ge-0/0/1 {
           vlan-tagging;
           encapsulation extended-vlan-bridge;
           unit 1 {
                vlan-id 1;
           }
           unit 2 {
                vlan-id 2;
           }
      }
}
bridge-domains {
       VLAN-1 {
               vlan-id 1;
               interface ge-0/0/0.1;
               interface ge-0/0/1.1;
      }
      VLAN-2 {
              vlan-id 2;
              interface ge-0/0/0.2;
              interface ge-0/0/1.2;
      }
}
 

Another way to configure bridge interfaces on an interface with different encapsulations is to use encapsulation "flexible-ethernet-services" under the interface and encapsulation "vlan-bridge", under the logical unit. In the following configuration, the interface ge-0/0/0.2 will be part of the bridge-domain VLAN-2, while interface ge-0/0/0.1 will work as an L3 interface.

interfaces {
       ge-0/0/0 {
            vlan-tagging;
            encapsulation flexible-ethernet-services;
            unit 1 {
                   family inet {
                        address 192.168.0.27/31;
                   vlan-id 1;
            }
            unit 2 {
                  encapsulation vlan-bridge;
                  vlan-id 2;
            }
      }
bridge-domains {
      VLAN-2 {
              vlan-id 2;
              interface ge-0/0/0.2;
      }
}

 



Enterprise Style

Configuring enterprise style requires:

  • family
  • interface-mode
  • vlan-id

Example:

interfaces {
     ge-0/0/0 {
          unit 0 {
               family bridge {
                    interface-mode trunk;
                    vlan-id-list [ 1 2 ];
              }
         }
     }
     ge-0/0/1 {
          unit 0 {
               family bridge {
                    interface-mode trunk;
                    vlan-id-list [ 1 2 ];
               }
          }
     }
}
bridge-domains {
     VLAN-1 {
          vlan-id 1;
     }
     VLAN-2 {
         vlan-id 2;
     }
}
Modification History:
2019-08-23: Added another way to configure bridge interfaces under the Service Provider Style.
2018-03-14: Corrected values used in configuration example.
Related Links: