Configuring the Spanning Tree Protocol
727
IndirectLink Rapid Convergence Feature
To handle indirect link failure, the STP standard requires that a switch
passively wait for “max_age” seconds once a topology change has been
detected. IndirectLink Rapid Convergence (IRC) handles these failures in
two phases:
• Rapid detection of an indirect link failure. Tracking the inferior BPDUs
that a designated bridge detects when it transmits a direct link failure
indicates that a failure has occurred elsewhere in the network.
• Performing an immediate check if the BPDU information stored on a port
is still valid. This is implemented with a new protocol data unit (PDU) and
the Root Link Query message (RLQ).
Receiving an inferior BPDU on a port from the designated bridge indicates
that one of the following has occurred on the designated bridge:
• The path to the root has been lost and the switch starts to advertise a root
with a numerically higher bridge ID (worse root) than the local switch.
• The path cost to the root has increased above the path cost of the local
switch.
IEEE 802.1s behavior is to ignore inferior BPDUs. IRC retains the inferior
BPDUs sent by the designated bridge and processes them to determine if a
failure has occurred on the path to the root. In this case, it must age-out at
least one port. This process occurs only in the case that a bridge in the
network detects a direct link failure.
The switch tracks inferior BPDUs sent by the designated bridge only, since
this is the BPDU that is stored for the port. If, for instance, a newly inserted
bridge starts to send inferior BPDUs, it does not start the IRC feature.
Similar to DRC, the IEEE 802.1w standard incorporated the IRDC feature.
RSTP-PV enabled switches allow IRC to be enabled or disabled, but ignore
the setting as the RSTP-PV state machines already implement IRC.
Reacting to Indirect Link Failures
When an inferior BPDU is received on a non-designated port, phase 2 of IRC
processing starts. An RLQ PDU is transmitted on all non-designated ports
except the port where the inferior BPDU was received and self-looped ports.
This action is intended to verify that the switch can still receive from the root
Содержание N2000 Series
Страница 50: ...50 Contents ...
Страница 54: ...54 Introduction ...
Страница 134: ...134 Using Dell OpenManage Switch Administrator ...
Страница 168: ...168 Setting Basic Network Information ...
Страница 206: ...206 Managing a Switch Stack ...
Страница 242: ...242 Configuring Authentication Authorization and Accounting ...
Страница 318: ...318 Managing General System Settings Figure 12 24 Verify MOTD ...
Страница 322: ...322 Managing General System Settings ...
Страница 344: ...344 Configuring SNMP Figure 13 18 Trap Logs Click Clear to delete all entries from the trap log ...
Страница 358: ...358 Configuring SNMP ...
Страница 388: ...388 Managing Images and Files ...
Страница 415: ...Monitoring Switch Traffic 415 Figure 16 2 sFlow Agent Summary ...
Страница 451: ...Monitoring Switch Traffic 451 5 On the Capture Options dialog click Manage Interfaces ...
Страница 458: ...458 Monitoring Switch Traffic ...
Страница 488: ...488 Configuring Port Characteristics Figure 18 3 Copy Port Settings 8 Click Apply ...
Страница 502: ...502 Configuring Port Characteristics ...
Страница 541: ...Configuring Port and System Security 541 Figure 19 12 Configure Port Security Settings 5 Click Apply ...
Страница 567: ...Configuring Port and System Security 567 Figure 19 38 Captive Portal Client Status ...
Страница 666: ...666 Configuring VLANs Figure 21 6 Add Ports to VLAN 4 Click Apply 5 Verify that the ports have been added to the VLAN ...
Страница 674: ...674 Configuring VLANs Figure 21 17 GVRP Port Parameters Table ...
Страница 680: ...680 Configuring VLANs Figure 21 24 Double VLAN Port Parameter Table ...
Страница 714: ...714 Configuring VLANs ...
Страница 737: ...Configuring the Spanning Tree Protocol 737 Figure 22 9 Spanning Tree Global Settings ...
Страница 760: ...760 Configuring the Spanning Tree Protocol ...
Страница 786: ...786 Discovering Network Devices ...
Страница 793: ...Configuring Port Based Traffic Control 793 Figure 24 3 Storm Control 5 Click Apply ...
Страница 878: ...878 Configuring Connectivity Fault Management ...
Страница 899: ...Snooping and Inspecting Traffic 899 Figure 27 17 DAI Interface Configuration Summary ...
Страница 903: ...Snooping and Inspecting Traffic 903 Figure 27 24 Dynamic ARP Inspection Statistics ...
Страница 924: ...924 Configuring Link Aggregation Figure 28 7 LAG Hash Summary ...
Страница 982: ...982 Configuring Link Aggregation ...
Страница 1062: ...1062 Configuring DHCP Server and Relay Settings ...
Страница 1096: ...1096 Configuring L2 and L3 Relay Features Figure 34 3 DHCP Relay Interface Summary ...
Страница 1200: ...1200 Configuring OSPF and OSPFv3 ...
Страница 1216: ...1216 Configuring RIP ...
Страница 1240: ...1240 Configuring VRRP ...
Страница 1284: ...1284 Configuring DHCPv6 Server and Relay Settings Relay Interface Number Vl100 Relay Remote ID Option Flags ...
Страница 1291: ...Configuring Differentiated Services 1291 Figure 40 5 DiffServ Class Criteria ...
Страница 1336: ...1336 Configuring Auto VoIP ...
Страница 1367: ...Managing IPv4 and IPv6 Multicast 1367 Figure 43 20 IGMP Cache Information ...
Страница 1422: ...1422 Managing IPv4 and IPv6 Multicast ...
Страница 1440: ...1440 System Process Definitions ...
Страница 1460: ...Index 1460 ...