HP VPN Firewall Appliances Network Management Configuration Guide

92
Configuring edge ports
If a port directly connects to a user terminal rather than another device or a shared LAN segment, this
port is regarded as an edge port. When network topology changes occur, an edge port will not cause
a temporary loop. Because a device does not determine whether a port is directly connected to a
terminal, you must manually configure the port as an edge port. After that, the port can transit rapidly
from the blocked state to the forwarding state.
Configuration restrictions and guidelines
• If BPDU guard is disabled, a port set as an edge port will become a non-edge port again if it
receives a BPDU from another port. To restore the edge port, re-enable it.
• If a port directly connects to a user terminal, configure it as an edge port and enable BPDU guard
for it. This enables the port to transit to the forwarding state quickly while ensuring network security.
• You cannot configure edge port settings and loop guard on a port at the same time.
Configuration procedure
To configure edge ports:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Enter Ethernet interface view or
Layer 2 aggregate interface view.
interface interface-type interface-number N/A
3. Configure the current ports as edge
ports.
stp edged-port enable
All ports are non-edge
ports by default.
Configuring path costs of ports
Path cost is a parameter related to the rate of a port. On a spanning tree device, a port can have different
path costs in different MSTIs. Setting appropriate path costs allows VLAN traffic flows to be forwarded
along different physical links, achieving VLAN-based load balancing.
You can have the device automatically calculate the default path cost, or you can configure the path cost
for ports.
Specifying a standard for the device to use when it calculates the default path cost
CAUTION:
If you change the standard that the device uses to calculate the default path costs, you restore the path
costs to the default.
You can specify a standard for the device to use in automatic calculation of the default path cost. The
device supports the following standards:
• dot1d-1998—The device calculates default path costs for ports based on IEEE 802.1d-1998.
• dot1t—The device calculates default path costs for ports based on IEEE 802.1t.
• legacy—The device calculates default path costs for ports based on a private standard.
Table 15 sho
ws a comparison between link sp
eeds and path costs for each of these standards.