Specifications

The mode statement indicates whether an MC-LAG is in active-standby mode
or active-active mode. Chassis that are in the same group must be in the same
mode.
7.
Configure a domain that includes the set of logical ports.
[edit bridge-domains bd0]
user@PE2# set domain-type bridge
user@PE2# set vlan-id all
user@PE2# set service-id 20
user@PE2# set interface ae0.0
user@PE2# set interface ae1.0
user@PE2# set interface ge-1/0/3.0
user@PE2# set interface ge-1/1/1.0
user@PE2# set interface ge-1/1/4.0
The ports within a bridge domain share the same flooding or broadcast
characteristics in order to perform Layer 2 bridging.
The bridge-level service-id statement is required to link related bridge domains
across peers (in this case Router PE1 and Router PE2), and should be configured
with the same value.
8.
Configure ICCP parameters.
[edit protocols iccp]
user@PE2# set local-ip-addr 100.100.100.2
user@PE2# set peer 100.100.100.1 redundancy-group-id-list 10
user@PE2# set peer 100.100.100.1 liveness-detection minimum-interval 1000
9.
Configure the service ID at the global level.
[edit switch-options]
user@PE2# set service-id 10
You must configure the same unique network-wide configuration for a service in
the set of PE routers providing the service. This service ID is required if the
multichassis aggregated Ethernet interfaces are part of a bridge domain.
Chassis-Level Feature Guide
•
The following additional information regarding the compatibility of modules for the
interoperation of RPM clients and RPM servers applies to the “Configuring RPM Probes”
section in the “Configuring Real-Time Performance Monitoring” topic:
Keep the following points in mind when you configure RPM clients and RPM servers:
•
You cannot configure an RPM client that is PIC-based and an RPM server that is
based on either the Packet Forwarding Engine or Routing Engine to receive the RPM
probes.
•
You cannot configure an RPM client that is Packet Forwarding Engine-based and an
RPM server that receives the RPM probes to be on the PIC or Routing Engine.
•
The RPM client and RPM server must be located on the same type of module. For
example, if the RPM client is PIC-based, the RPM server must also be PIC-based,
Copyright © 2015, Juniper Networks, Inc.138
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series