Supported Platforms
Related Documentation
- ACX, M, MX, T Series
- bridge-domain
- connectivity-fault-management
- instance
- Creating the Maintenance Domain
- Creating a Maintenance Association
- Continuity Check Protocol
- Configuring a Maintenance Endpoint
- Configuring a Connectivity Fault Management Action Profile
- Configuring Linktrace Protocol in CFM
- Configuring Ethernet Local Management Interface
- Configuring Port Status TLV and Interface Status TLV
- Configuring Rate Limiting of Ethernet OAM Messages
- Configuring 802.1ag Ethernet OAM for VPLS
- ACX, M, MX, PTX, T Series
- IEEE 802.1ag OAM Connectivity Fault Management Overview
- M, MX, SRX, T Series
- mip-half-function
- M, MX, T Series
- virtual-switch
- Configuring M120 and MX Series Routers for CCC Encapsulated Packets
- MX, T Series
- Configuring MAC Flush Message Processing in CET Mode
- Additional Information
- Ethernet Interfaces
Configuring Maintenance Intermediate Points
MX Series routers support maintenance intermediate points (MIPs) for the Ethernet OAM 802.1ag CFM protocol at a bridge-domain level. This enables you to define a maintenance domain for each default level. The MIPs names are created as default-level-number at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain] hierarchy level. Use the bridge-domain, instance, virtual-switch, and mip-half-function MIP options to specify the MIP configuration.
![]() | Note: Whenever a MIP is configured and a bridge domain is mapped to multiple maintenance domains or maintenance associations, it is essential that the mip-half-function value for all maintenance domains and maintenance associations be the same. |
To display MIP configurations, use the show oam ethernet connectivity-fault-management mip (bridge-domain | instance-name | interface-name) command.
The following sections describe MIP configuration:
Configuring MIP for Bridge Domains of a Virtual Switch
The default maintenance domain configuration allows MIP configuration for bridge domains for a default virtual switch or a user-defined virtual switch. You can use the virtual-switch and bridge-domain statements to specify which MIPs to enable for a user-defined virtual switch.
A bridge domain must be specified by name only if it is configured by including the vlan-id id statement under the virtual-switch statement.
If a bridge domain is configured with a range of VLAN IDs, then the VLAN IDs must be explicitly listed after the bridge domain name.
To configure a bridge domain under a user-defined virtual switch, include the virtual-switch name statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name default-x] hierarchy level.
Configuring the Maintenance Domain Bridge Domain
The VLAN corresponds to the bridge domain.
To configure the bridge domain for the default virtual switch, include the bridge-domain statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain maintenance-domain-name] hierarchy level.
Configuring the Maintenance Domain Instance
To configure the maintenance domain instance for a VPLS routing instance, include the instance statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain] hierarchy level.
Configuring the Maintenance Domain MIP Half Function
MIP Half Function (MHF) divides MIP functionality into two unidirectional segments, improves visibility with minimal configuration, and improves network coverage by increasing the number of points that can be monitored. MHF extends monitoring capability by responding to loopback and linktrace messages to help isolate faults.
Whenever a MIP is configured and a bridge domain is mapped to multiple maintenance domains or maintenance associations, it is essential that the MIP half function value for all maintenance domains and maintenance associations be the same. To configure the MIP half function, include the mip-half-function statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain] hierarchy level.
Related Documentation
- ACX, M, MX, T Series
- bridge-domain
- connectivity-fault-management
- instance
- Creating the Maintenance Domain
- Creating a Maintenance Association
- Continuity Check Protocol
- Configuring a Maintenance Endpoint
- Configuring a Connectivity Fault Management Action Profile
- Configuring Linktrace Protocol in CFM
- Configuring Ethernet Local Management Interface
- Configuring Port Status TLV and Interface Status TLV
- Configuring Rate Limiting of Ethernet OAM Messages
- Configuring 802.1ag Ethernet OAM for VPLS
- ACX, M, MX, PTX, T Series
- IEEE 802.1ag OAM Connectivity Fault Management Overview
- M, MX, SRX, T Series
- mip-half-function
- M, MX, T Series
- virtual-switch
- Configuring M120 and MX Series Routers for CCC Encapsulated Packets
- MX, T Series
- Configuring MAC Flush Message Processing in CET Mode
- Additional Information
- Ethernet Interfaces
Published: 2013-08-01
Supported Platforms
Related Documentation
- ACX, M, MX, T Series
- bridge-domain
- connectivity-fault-management
- instance
- Creating the Maintenance Domain
- Creating a Maintenance Association
- Continuity Check Protocol
- Configuring a Maintenance Endpoint
- Configuring a Connectivity Fault Management Action Profile
- Configuring Linktrace Protocol in CFM
- Configuring Ethernet Local Management Interface
- Configuring Port Status TLV and Interface Status TLV
- Configuring Rate Limiting of Ethernet OAM Messages
- Configuring 802.1ag Ethernet OAM for VPLS
- ACX, M, MX, PTX, T Series
- IEEE 802.1ag OAM Connectivity Fault Management Overview
- M, MX, SRX, T Series
- mip-half-function
- M, MX, T Series
- virtual-switch
- Configuring M120 and MX Series Routers for CCC Encapsulated Packets
- MX, T Series
- Configuring MAC Flush Message Processing in CET Mode
- Additional Information
- Ethernet Interfaces