Service OAM in the TMPLS mode is supported on the VLNC42B only.

Use this procedure to configure Ethernet service OAM on VLNC42B networks in TMPLS mode using the Web GUI. Its external interface is implemented using SNMP instead of CLI commands.

See Procedure 16-2: Configure Ethernet service OAM in Bridging mode using the Web GUI to configure Ethernet service OAM on VLNC42B networks in Ethernet Bridging mode.

Since service OAM in the TMPLS mode is managed by SNMP, there are some differences from the implementation based on CLI commands.

• T-MPLS is VPWS (p2p virtual private line), which means that maintenance points are defined by the PW. No VLAN is used.

• The service, and therefore Service OAM, terminates at tunnel endpoints.

• Local maintenance associations contain no MIP’s, only a pair of MEP’s. This limits the utility of LT and LB.

• MEP’s at multiple levels for the same PW are redundant and therefore for simplicity, not allowed.

• Customer MIP’s are not allowed

Service OAM provisioning in TMPLS mode consists of the following general order of steps, the same as Ethernet Bridge mode:

1. Enabling Connectivity Fault Management (CFM) on each node in the network using the Service OA&M → Connectivity Fault Mgmt → Configuration command.

2. Provision the Maintenance Domains (MDs) using the Service OA&M → Maintenance Domain → Configuration command.

   Only one MD is allowed per PWID. The maximum number of MD is 8.

3. Provision the Maintenance Associations (MAs) using the Service OA&M → Maintenance Association → Configuration command.

   The MA is defined by PWID rather than VLAN. There is no equivalent to an MA with no VID. Only one MA is allowed per PWID. Multiple MEP’s at different MD levels would be redundant (service terminates at tunnel endpoints), and a customer MIP is not supported. The maximum number of MA is 120. In R7.2, this is reduced to 63 to accommodate the CIR/PIR color marking feature. The MA and MD name lengths are brought into compliance with 802.1ag: when both are character strings, the combined length can be up to 44 characters. When the MD name is null, the MA name length can be up to 45 characters.

4. Provision the Maintenance association End Points (MEPs) to be used using the Service OA&M → Maintenance Association End Point → Configuration and Service OA&M → Maintenance Association End Point → Remote Configuration commands.

   There is only one Up-MEP supported per service per NE, at the PW/tunnel endpoint. Ethernet has no visibility in the T-MPLS domain, so no MIP’s are available. Down-MEP’s are not available. They are not needed on the UNI if customer equipment does not support SOAM. They are not needed on the NNI ports: AIS is not allowed on redundant NNI’s, T-MPLS has its own fault detection and protection switching triggers, and Link OAM is available. The maximum number of MEP’s per MA is two (one local, one remote) The CFM MIB has an object for disabling a MEP. VLNC4x packs do not have this capability, so this object is not available.

You must be familiar with the concepts of IEEE Std 802.1ag™ -2007 Connectivity Fault Management and/or have detailed work instructions.

In addition, you should:

• Make a sketch of the network with the Nodes and ports being used for this service.

• Know the number of players (owners), domains, and maintenance associations of the OAM functions being provisioned at each of the nodes in the network.

• Determine the location of all Maintenance association End Points (MEPs and remote-MEPs) and Maintenance Intermediate Points (MIPs).