Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Example: Configuring Multiple Bridge Domains with a VLAN ID List

    To configure multiple bridge domains with one statement, include the vlan-id-list statement at the [edit bridge-domains] hierarchy level.

    The following example automatically configures 4093 bridge domains named sales-vlan-2 through sales-vlan-4094:

    bridge-domains {sales { # This is the prefixvlan-id-list [ 2–4096 ]; # These are the numbers}}

    You can configure these bridge domains in a virtual switch routing instance. However, if a VLAN identifier is already part of a VLAN identifier list in a bridge domain under a routing instance, then you cannot configure an explicit bridge domain with that VLAN identifier. In other words. there can be no overlap between a VLAN identifier list and another VLAN identifier configuration.

    The following example removes the VLAN identifier 5 from the original VLAN list (vlan-id-list [ 1–10 ]) and configures the bridge domain explicitly:

    [edit routing-instance rtg-inst-10]instance-type virtual-switch;interface ge-7/3/0.0;
    bridge-domains {bd-vlan–5 {vlan-id 5;}bd {vlan-id [ 1–4 6–10 ];}}

    If a VLAN identifier is already part of a VLAN identifier list in a bridge domain under a routing instance, then you must delete the VLAN identifier from the list before you can configure an explicit or “regular” bridge domain. Also, the explicit bridge domain will not perform properly unless it has the same name as the bridge domain in the VLAN identifier list.

    In other words, if sales-vlan-100 was part of a bridge domain VLAN list and you wish to configure it explicitly, you must use the same naming convention:

    bridge-domains {sales-vlan-100 { # You must use this name explicitlyvlan-id 100;}}

    The following limitations apply to automatic bridge domain configuration:

    • Only one vlan-id-list statement is allowed in a routing instance.
    • Bridge options are not supported with the vlan-id-list statement.
    • Only trunk interfaces are supported.
    • There is no support for integrated routing and bridging (IRB).

    You display the status and other parameters for automatic bridge domains configured with the vlan-id-list statement using the same show l2-learning instance command as used for individually configured bridge domains.

    Modified: 2013-07-16