Comware

Has anyone deployed loopback-detection acrossed their LAN? For my access ports I was going to go with this:

interface GigabitEthernet1/0/1
port link-mode bridge
loopback-detection enable
loopback-detection action shutdown

For my trunk links I was thinking of going this route:

interface GigabitEthernet1/0/48
port link-mode bridge
port link-type trunk
port trunk permit vlan 1
loopback-detection enable
loopback-detection control enable
loopback-detection action semi-block

With this deployment the access ports with shutdown when a loop is detected (this will send a trap). If the trunk sees a loop condition it will go into the "semi-block" mode which still sends traps and bpdu's, but I am  not sure what this would look like over a large deployment. Does anyone have any insight? 

Wow, nobody?

Hi

I'm working on the same.
you finished making your implementation?
you can help me?

regards

Atte.
Francisco

I wish I could say I had an answer for you. I have come up with nothing I feel comfortable with trying to deploy and I don't feel like forging this path on an environment of the size I am in.

This doc has some info on loopback detection but I guess you have already read it?

http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay?javax.portlet.prp_ba847bafb2a2d782fcbb0710b053ce01=wsrp-navigationalState%3DdocId%253Demr_na-c03166926-1%257CdocLocale%253D%257CcalledBy%253D

A previous example I have seen (I dont use loopback detection myself, yet) is:

Globally:

loopback-detection enable
loopback-detection multi-port-mode enable
loopback-detection interval-time 5

Per interface:

loopback-detection enable
loopback-detection control enable
loopback-detection per-vlan enable
loopback-detection action shutdown

A drawback of "action shutdown" is that you need to manually login to the device and enable the interface again, I guess this is what "semi-block" is supposed to take care of.

Link is broken.

Why on god's earth did HP have to change their site and break 1000s of links to important information?

Yeah I dont get that either, my bets are on bad management who makes stupid decisions...

In this case you can change hp.com into hpe.com to get networkingrelated links to work again.

That is:

http://h20566.www2.hpe.com/hpsc/doc/public/display?calledBy=&docId=emr_na-c03166926-1&lang=en-us&cc=us&docLocale=

Hi All,

Do  you know what exact means command : "loopback-detection per-vlan enable"

How it works on the trunk (e.g. all vlans allowed) without this "extra" entry?

Br,

Mike

>Why on god's earth did HP have to change their site and break 1000s of links

Due to the company split, HP Inc got the hp.com domain name and HPE moved to hpe.com.

If you have not disabled the HP vs HPE popup, clicking on "HP Support Center - Hewlett Packard Enterprise" will show you the right webpage.