Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

}
}
Logical Systems logical-system {
ls1 {
switch-options {
service-id 10;
}
}
}
logical-system {
ls1 {
routing-instances {
r1 {
switch-options {
service-id 10;
}
}
}
}
}
Copyright © 2012, Juniper Networks, Inc.
NOTE: Using a service name per bridge domain is not supported.
The bridge level service ID is required to link related bridge domains across peers, and
should be configured with the same value. The service-id values share the name space
across all bridging and routing instances, and across peers. Thus, duplicate values for
service IDs are not permitted across these entities.
The service ID at the bridge domain level is mandatory for type non-single VLAN bridge
domains. The service ID is optional for bridge domains with a VID defined. If no service
ID is defined in the latter case, it is picked up from the service ID configuration for that
routing instance.
NOTE: When this default routing instance (or any other routing instance)
which contains a bridge domain containing an MC-AE interface is configured,
you must configure a global level switch-options service-id number, irrespective
of whether the contained bridge domains have specific service IDs configured.
In the example shown in Figure 10 on page 102, network routing instances N1 and N2, both
for the same service ID, are configured with same service-id in both N1 and N2. Use of a
name string instead of a number is not supported.
Chapter 4: Configuring Aggregated Ethernet Interfaces
101