Support

The Dying Gasp issues of Huawei Switch

switch-dying-gasp-issues

Stack Dying Gasp:

This feature applies to Huawei switches configured in a stack. When the master switch in the stack loses power, it sends a “Dying Gasp” packet to other switches in the stack. This packet triggers the remaining switches to elect a new master and maintain continuous operation. Therefore, the specific meaning of “Dying Gasp” for a Huawei switch depends on the context and switch configuration.

What models support Dying Gasp?

Unless otherwise specified:

  • The models listed in the table can send Dying Gasp messages to the remote device and send Dying Gasp alarms (EFM_1.3.6.1.4.1.2011.5.25.136.1.6.5_hwDot3ahEfmNonThresholdEvent) to the NMS.
  • All interfaces of the device can send Dying Gasp fault notification.

S5720-16X-PWH-LI-AC

PN: 98010657

In stock

3-5 days lead time | | 4 QA
 
S2720-EI All models
S5720-LI All models support except S5720-16X-PWH-LI-AC, S5720-28X-PWH-LI-AC, S5720-52X-PWR-LI-ACF
S5720S-LI S5720S-12TP-LI-AC, S5720S-12TP-PWR-LI-AC, S5720S-28TP-PWR-LI-ACL, and S5720S-28X-LI-24S-AC

NOTE:

  • They can send Dying Gasp messages to the remote device only, but cannot send Dying Gasp alarms to the NMS.
  • A maximum of 30 interfaces can send Dying Gasp messages.
S5720I-SI All models
S5735-L All models
S5735S-L All models support except S5735S-L48P4S-A and S5735S-L48P4X-A
S5735-L1 S5735-L24P4X-A1, S5735-L24T4X-A1, S5735-L24T4X-D1, S5735-L24T4X-QA1, S5735-L32ST4X-A1, S5735-L32ST4X-D1, S5735-L48T4X-A1, S5735-L8P4X-A1, and S5735-L8T4X-A1 support
S5735S-L1 S5735S-L32ST4X-A1 support
S5735S-L-M All models
S5735-L-I All models
S500-32ST4X S500-32ST4X support

FutureMatrix S5735-L32ST4X-A1

PN: 98011396

In stock

Ready to ship | 62 sold | 4 QA
  • The efm critical-event trigger error-down command is used and the remote interface associated with MGR goes Down. The local device will set the protocol status of the corresponding interface to Down after receiving an EFM OAM packet indicating a critical-event fault.
  • The efm dying-gasp trigger error-down command is used and the board where the remote interface resides is reset or the system restarts. The local device will set the protocol status of the corresponding interface to Down after receiving an EFM OAM packet indicating a dying-gasp fault.
  • The efm link-fault trigger error-down command is used and the physical link of the remote device is faulty. The local device will set the protocol status of the corresponding interface to Down after receiving an EFM OAM packet indicating a link-fault fault.
  • The efm timeout trigger error-down command is used on the local device. The local device will set the protocol status of the corresponding interface to Down if it does not receive packets from the remote device in a specified period of time (5s by default).

Examples for configure Dying Gasp:

# Associate dying-gasp faults with Layer 2 interface GigabitEthernet0/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 0/0/1
[HUAWEI-GigabitEthernet0/0/1] efm enable
[HUAWEI-GigabitEthernet0/0/1] efm dying-gasp trigger error-down

# Associate dying-gasp faults with Layer 3 interface GigabitEthernet0/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 0/0/1
[HUAWEI-GigabitEthernet0/0/1] undo portswitch
[HUAWEI-GigabitEthernet0/0/1] efm enable
[HUAWEI-GigabitEthernet0/0/1] efm dying-gasp trigger error-down

Dying Gasp is typically activated by default in stack configurations. You can manage its settings using the switch CLI or management interface, if you have further questions or need details about specific models or configurations, feel free to contact us!