Use this procedure to configure Ethernet service OAM in bridging mode on VLNC40/42/42B networks using the Web GUI.

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

Refer to Service OAM in VLNC40/42/42B, and Figure 16-1, Service OAM reference model for an example.

Refer to the Alcatel-Lucent 1850 Transport Service Switch (TSS-5) Command Line Interface Guide, for help on using the Ethernet OAM CLI commands and parameters.

Service OAM provisioning consists of the following general order of steps:

1. Determine the VLAN tagging mode (VLAN ID) being used for this service.

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

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

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

5. 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.

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 tagging mode of the service and the VLAN ID to be used for the maintenance associations (MAs) being provisioned.

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

• Disable CFM traps for the switch during setup using the no snmp-server enable traps cfm command, if required. When a remote-mep is configured, a dot1agCfmFaultAlarm trap (DefRemoteCCM) will exist until the remote has been configured mep-cc enable if traps are not disabled.