某局点 DRNI MAD DOWN问题

两台设备组成DRNI，进行主备重启倒换测试。

当主设备重启后，备设备打印日志提示被MAD down 

%Sep 26 16:12:42:476 2021 GM_NHZ06_M01_R01C10_INT_LBI_S6850_ASW_38.8 DRNI/4/DRNI_DEVICE_MADDOWN: All new service interfaces not excluded from the DRNI MAD DOWN will change to the DRNI MAD DOWN state because the IPL and all DR interfaces went down. Please first check the IPL settings on both ends of the IPL.

%Sep 26 16:12:42:493 2021 GM_NHZ06_M01_R01C10_INT_LBI_S6850_ASW_38.8 DRNI/6/DRNI_IFEVENT_IPP_DOWN: IPP Bridge-Aggregation20 went down because the aggregate interface went down. Please check the aggregate link status.

%Sep 26 16:12:42:521 2021 GM_NHZ06_M01_R01C10_INT_LBI_S6850_ASW_38.8 DRNI/6/DRNI_SYSEVENT_DEVICEROLE_CHANGE: Device role changed from Secondary to None for IPL down and all local DR interfaces down.

1、查看了备设备，所有的DR口都是down 的状态，当主设备重启时，备设备上所有DR口和IPL都down，因此设备角色从备变为NONE。DRNI场景，IPL故障且本端所有DR接口处于down状态时，设备角色为None。 备设备角色变为NONE后，新版本就会MAD down，正常实现。

 2、当主设备重启完成后，IPL UP，从设备重新竞选加入DRNI系统，角色从None变为Secondary，由于drni restore-delay命令，备设备被MAD down30秒后才开始转发业务。

%Sep 26 16:15:30:559 2021 GM_NHZ06_M01_R01C10_INT_LBI_S6850_ASW_38.8 DRNI/4/DRNI_DEVICE_MADDOWN: All service interfaces not excluded from the DRNI MAD DOWN action will change to the DRNI MAD DOWN state because the IPL came up. Please wait for the data restoration delay timer to expire.

%Sep 26 16:15:30:646 2021 GM_NHZ06_M01_R01C10_INT_LBI_S6850_ASW_38.8 STP/5/STP_CONSISTENCY_CHECK: DR role assignment finished. Please verify that the local device and the peer device have consistent global and DR-interface-specific STP settings.

%Sep 26 16:15:30:647 2021 GM_NHZ06_M01_R01C10_INT_LBI_S6850_ASW_38.8 DRNI/6/DRNI_SYSEVENT_DEVICEROLE_CHANGE: Device role changed from None to Secondary for IPL calculation.

DRNI组网下尽可能使用DR口互联，不要无DR接口，设备上存在一个UP的DR接口也不会有前面的现象。