To configure system and port level ETH-OAM Dying Gasp notification

Reference

Ethernet First Mile OAM 802.3ah is deployed heavily at E-NNI and UNI connections. These connection points are typically multi-vendor and have resilient connectivity. Signaling the pending removal of a link when a soft reset could interrupt service on such ports is critical in reducing unacceptably long outages for known maintenance conditions. This signaling is accomplished by setting the Dying Gasp flag in the Information OAMPDU when a soft reset message is received by EFM for those ports that will be affected by the soft reset. The Dying Gasp flag can be enabled at both the port and system levels.

Steps


1	Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.
2	Right-click the device on which you want to configure dying gasp notification and select Properties. The Network Element (Edit) form opens.
3	Click on the Globals tab and then on the OAM sub-tab.
4	Enable the System Dying Gasp Tx on Reset Enable parameter. The default state is disabled. Both the system level and port level dying gasp functionality must be enabled for the notification capability to be active on a port. Note: You can click on Show system EFM-OAM Information to display additional EFM-OAM details.
5	Navigate to the port on which you want to configure the dying gasp notification. The path is Network→NE→Shelf→Card Slot→Daughter Card Slot→Port n/n/n.
6	Right-click on the Port icon and choose Properties. The Physical Port (Edit) form opens.
7	Click on the Ethernet tab and then on the EFM-OAM sub-tab.
8	Configure the Administrative State to Enabled.
9	Enable the Dying Gasp on Reset Enable and the Dying Gasp Notify parameters. The Dying Gasp Notify parameter determines whether or not the local OAM entity attempts to report a dying gasp to its peer OAM entity when a dying gasp event occurs.
10	Configure the Trigger Fault parameter as required. Enabling the Trigger Fault function allows an operator to invoke an ETH-OAM fault (either Dying Gasp or Critical Event) before shutting down the port.
11	Configure the remaining parameters as required.
12	Configure the required parameters in the Link Event Configuration panel. See To configure link monitoring on an Ethernet port for detailed information on configuring link monitoring. Note: The Reaction to Peer Dying Gasp parameter specifies how the local port will be impacted when it receives an Information OAMPDU from a peer with the Dying Gasp flag set.
13	Expand the Link Monitoring Error Event Logs panel to view signal failure and signal degradation event logs issued from local or remote link monitoring peer ports. The event logs on a remote peer will record active error events when receiving the trigger fault command from the source node. Perform the following: Click Refresh to obtain current event logs from the NE. Select a dying gasp log from the list under the Signal Failure sub-tab and click Properties to view the contents. Click Clear to clear local, remote, or all the event logs. Note: Clearing event logs cannot be undone.
14	Save your changes and close the form. End of steps