Enterprise

Community Forums Switches

bfd configuration on a su...

bfd configuration on a sub interface of eth trunk and remotely conected router interface. which is connceted via switch. without dping config on route

Created: Dec 2, 2019 18:31:52Latest reply: Dec 3, 2019 02:00:11 68 1 0 0

Rewarded Hi-coins： 0 (problem resolved)

display all floors ^#1

can we enable bfd on that sub eth -runk with out configuring the remote router interface . . meanz can we enable bfd from single side ?

x
convention：

I have this problem too (0) Favorite(0) Report

Featured Answers

chenhui Admin Created Dec 3, 2019 02:00:11

@manishah hello,
yes, bfd one-arm-echo could meet your requirement. please refer the configuration below

#
bfd t1 bind peer-ip 10.1.1.2 interface Eth-Trunk1.10 one-arm-echo
discriminator local 20
commit
#
and you can refer the documentation http://support.huawei.com/hedex/hdx.do?docid=EDOC1000163385&id=bfd_one-arm-echo_2&lang=en

x
convention：

All Answers

chenhui Admin Created Dec 3, 2019 02:00:11

@manishah hello,
yes, bfd one-arm-echo could meet your requirement. please refer the configuration below

#
bfd t1 bind peer-ip 10.1.1.2 interface Eth-Trunk1.10 one-arm-echo
discriminator local 20
commit
#
and you can refer the documentation http://support.huawei.com/hedex/hdx.do?docid=EDOC1000163385&id=bfd_one-arm-echo_2&lang=en

x
convention：

Comment

Notice

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:

Politically sensitive content
Content concerning pornography, gambling, and drug abuse
Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy

Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."