Enabling Maintenance Intermediate-Points (MIP)

If MIP creation is enabled, MIPs are auto-created on all ports assigned to the CFM service. See Maintenance Intermediate Point (MIP) for a description of the role MIPs play in a CFM process.

MIP creation can be configured in CFM command modes: Default MD, Default MD VLAN, MD, MA-Comp configuration mode. The modes here are listed in precedence from lowest to highest. Configuring MIP creation in MA-Comp configuration mode takes precedence over any other CFM configuration mode for the current MA context.

You can specify:

• Default – MIPs are created for the MD or MA context
• Explicit – MIPs are created for the MD or MA context, only if a MEP exists at the next lower MD level
• None – MIPs are not created in the MD or MA context
• Defer – In a VLAN default or MA component context, the MIP creation defers to the next highest configuration level settings. The defer option is only valid in the Default Maintenance Domain VLAN service context, the (named) Maintenance Domain context, or the Maintenance Association Component context. When defer is used in the:
  • • – Default MD VLAN service context, MIP creation defaults to the value set for the default MD
  • • – MA component context, MIP creation defaults to the value set for the (named) Maintenance Domain within which the MA component resides

Use the mhf-creation command in the appropriate configuration mode to set whether the creation of maintenance intermediate-point half function (MHF) is allowed for the current context. MIPs are not enabled by default.

This example shows how to set the system default maintenance domain value to allow an MHF to be created only when a MEP in the next lowest MD exists:

System(rw-config)->cfm default-md default
System(su-config-cfm-default-md-def)->mhf-creation explicit
System(su-config-cfm-default-md-def)->