Shulou(Shulou.com)06/01 Report--

I believe that one of the things that is very painful for friends who use HP Procurve series switches is that they have less data and fewer cases of implementation.

Here is a comparison of the spanning Tree Protocol (Spaninng Tree) comparison table between the Cisco and HP switches.

It is recommended that you enable bpdu-protection, admin-edge-port, and loop-protection commands on the edge port (only client computers or unmanaged switches are connected). Usually, because the devices connected by clients should not have switches that support spanning Tree Protocol, for a stable network, we should prevent other switches from connecting to the network to interfere with the already stable spanning tree.

If the switch supports it, it is recommended to use the link-keepalive and loop-guard commands.

I hope you will correct what is wrong.

Name CiscoHPHP default recommended port usage description detect unidirectional traffic udldlink-keepalive disable optical fiber port to prevent one core of optical fiber from failure. Neighboring devices must be the same implementation, and this setting cannot be used between devices from different vendors.

HP 2510 and 2520 are not supported, but HP 2530, 2600, 2800, 3400, 3500, 4200, 5300, 5400, 6200,6400,6600,8212, and 9300 are supported. DBPU protects bpduguardbpdu-protection disables edge ports enter the error-disabled state as soon as they receive BPDU.

A loop caused by a BPDU packet (forming a loop on a switch that supports STP). These three commands are used together on edge ports. Port Fast portfastadmin-edge-port disables the edge port without using the STP algorithm and directly enters the forwarding state.

If admin-edge-port is disabled and auto-edge-port is not disabled, auto-edge-port controls port behavior. Auto-edge-port enabled

If admin-edge-port is set, the auto-edge-port setting is ignored. Keep alive Keepaliveloop-protection disables sending Edge Ports when loop-protection receiver-action send-disable is enabled, the switch sends a loop protocol packet, then receives this loop protocol packet on the same port and closes the port.

The no loop-protection command does not remove the receive configuration unless it is set to receiver-action send-disable.

A loop caused by a non-BPDU packet (forming a loop on a switch that does not support STP). Loop protection guard looploop-guard disables the root port and the Block port to prevent blocking ports from mistakenly transitioning to the forwarding state, resulting in bridging loops. When the switch stops receiving BPDU on a non-designated port with the loop guard feature enabled, the switch will cause the port to enter the STP "inconsistent loop" (inconsistentports) blocking state, and when the inconsistent port receives BPDU again, the port will automatically filter to the STP state based on the BPDU. HP 2510 and 2520 are not supported, but HP 2530 is supported.

The HP 5400 series needs to be updated to version K.15.05.0001 or later to support this command.

The interface of PortFast cannot enable Loop Guard.

BPDU filtering bpdufilterbpdu-filter disabled Global Port portfast Port receives bpdu and enters the STP interface state. Bpdufilter takes precedence over bpduguard and should not be used with bpduguard. When bpduguard and bpdufilter are enabled at the same time, bpdufilter has a higher priority and bpduguard will fail. The separate port portfast port receives the bpdu, does not send the BPDU, and ignores the received BPDU.

Root guard guard rootroot-guard (for MSTP only) disables the edge port this port cannot become the root port, preventing the switch from becoming the root bridge. Ignore the high priority BPDU received and accept other BPDU.

If both loop guard and root guard are used, loop guard takes precedence over root guard.

Do not enable both loop guard and root guard. Tcn-guard disables edge ports and does not propagate received topology change notifications.

Backbone fast backbonefast does not know the corresponding command

The core switch is used to detect indirect link failures. When an BackboneFast-enabled switch detects an indirect link failure, it immediately puts the blocked port into a listening state, reducing the aging time of 20s. If we want to enable the BackboneFast feature, we should enable it on all switches in the network.

MSTP does not support UplinkFast, BackboneFast, and cross-stack UplinkFast. Cascaded Fast uplinkfast does not know the corresponding command

The access switch can detect the failure of directly connected links and improve the convergence speed of stp. When a link or switch fails, or when STP is reconfigured, UplinkFast can speed up the selection of a new root port. The root port immediately enters the forwarding state, and Uplinkfast limits burst multicast traffic by reducing the maximum update rate.

Uplinkfast is useful for wiring closet switches at the edge of the network. It is not suitable for backbone equipment. UplinkFast provides fast convergence after a directly connected link failure and is redundant through uplink groups. UplinkFast activates a condition for rapid reconfiguration:

a. The UplinkFast function must be enabled on the switch

b. At least one port in Blocking (that is, redundant links)

c. Link failure must occur on the Root Port.

After the switch starts UplinkFast, it is not suitable to be the root bridge because it increases the path cost of all ports on the switch.

Once UplinkFast is configured, the switch cannot become the root switch.

For more information about guard loop and udld, please refer to: http://blog.sina.com.cn/s/blog_bfab4a570101nug9.html

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.