Академический Документы
Профессиональный Документы
Культура Документы
What happens if a switch sends out an RSTP proposal message and the recipient does
not understand it or can't respond?
The sender switch becomes overly-cautious and begins playing by the 802.1D rules
(moving into the listening, learning, and forwarding states at the Forward Delay timer
rate)
What is the difference between how 802.1D and 802.1w respond to topology changes?
- 802.1D switches detect a topology change when it detects that a port state has gone
either up or down and then sends a TCN BPDU to the root switch. The root switch then
sends that TCN message to all switches in its domain.
- 802.1w switches detect a topology change only when a nonage port transitions into
the Forwarding state. RSTP uses all its rapid convergence mechanisms to prevent
bridging loops from forming. Therefore, topology changes are detected only so that
bridging tables can be updated and corrected as hosts appear first on a failed port and
then on a different functioning port. The RSTP switch that noticed the change then
sends TC (topology change) BPDU out its nonedge designated ports throughout the
network in a wave.
What do RSTP TC (Topology Change) BPDUs do to switches when they are received
on their nonedge ports?
- They notify the switch that a new link has been established and the topology has
changed
- All MAC addresses associated with the nonedge designated ports are flushed from the
content-addressable memory (CAM) table. This forces the addresses to be relearned
after the change, in case hosts now appear on a different link.
For how long are RSTP TC BPDUs sent out after a topology change is detected?
Until the TC timer expires, after two intervals of the Hello time
What is the default STP configuration on a Catalyst switch?
It operates in Per-VLAN Spanning Tree Plus (PVST+) mode using traditional 802.1D
STP
Do you have to enable anything with regards to STP before changing the switch's mode
from the traditional 802.1D STP to RSTP?
Yes, you have to enable MST or RPVST+ first... think of RSTP and 802.1D STP as just
the underlying mechanisms of MST, RPVST+, and PVST+ STP modes
Will your switch know what its RSTP nonedge ports are automatically? And why or why
not?
Nope, you have to explicitly configure your nonedge ports as nonedge. Remember that
RSTP considers all ports with full-duplex as nonedge, so if a port should not expect
BPDUs (because it's attached to a host, for instance), you have to tell the switch
What command(s) do you use to configure a port as an RSTP nonedge port?
If for some reason, you have to force a port to act as a point-to-point port (if it had to be
put in half-duplex, for instance), what command would you use?
What command can you use to show what underlying STP is being used on your switch
and on your neighbor switches (e.g., for VLAN 171)?
Grey highlight #1: Your switch's STP mode
Grey highlight #2: First neighbors's STP mode (RSTP)
Grey highlight #3: Second neighbor's STP mode (802.1D)
What IEEE standard specifies that only a single instance of STP encompasses all
VLANs?
IEEE 802.1Q. While it specifies how VLANs are to be trunked between switches, it also
specifies that only a single instance of STP encompasses all VLANs.
What is the instance of STP that IEEE 802.1Q uses referred to as?
Common Spanning Tree (CST)
What VLAN does CST operate on?
The native VLAN on a trunk
What is the problem that you can have with only one instance of STP on your network
(as is the case with CST)?
At least one of the links will have a blocking port on it that is left completely unused... it's
just inefficient
Why might you want more than one instance of STP on your network if you have
multiple VLANs?
Instead of leaving a blocking port completely unused for all VLANs, you can switch off
which port is left blocking and which is left designated for each VLAN... that way you
can make more efficient use of ports (your resources)
If you want more than one instance of STP for all the VLANs on your network, what are
the alternatives to Common Spanning Tree (CST)?
- PVST+: One instance of STP for each VLAN
- MST: One instance of STP for each MST instance (each instance has multiple VLANs)
Why might you want to use MST over PVST+?
As the number of VLANs increases with PVST+, so does the number of STP
instances... Each instance uses some amount of the switch CPU and memory
resources. The more instances that are in use, the fewer CPU resources will be
available for switching.
Study the network topology on the other side of this card and determine the different
possible STP topologies for the two VLANs...
Based on the network topology from the previous card, what are the different possible
STP topologies for the two VLANs? Is the number of useful (unique) topologies
dependent on the number of VLANs?
The number of useful topologies is independent of the number of VLANs (even if you
had 14 VLANs here, you would still only have those 2 possible STP topologies)
Thinking about the network from the previous two cards, consider what would happen if
you had 4, 10, or 20 VLANs... is there a way you could continue using both topologies
(so ports are not left completely unused) and so that your system uses the least amount
of processing on STP (allowing for higher processing of switching)? What technology
could you use to do this?
Yes, you can use MST to create two STP instances and bundle half the VLANs into one
instance and the rest into the other.
Why is it important that switches using MST be mapped together? What is this group of
switches called?
Without having multiple switches participate in MST, only the switch with it enabled
benefits from the extra CPU and port usage... the others will still have to use PVST+ or
CST with the MST switch. The group of switches using MST together is called an MST
region
What information does a switch need to have about an MST region in order to run an
instance of MST (or MSTI)?
- MST configuration name (32 chars)
- MST configuration revision number (0 to 65535)
- MST instance-to-VLAN mapping table (4096 entries)
Can this MST region information be shared automatically between switches or must it
be statically configured?
MST region information has to be statically configured
How do switches know that they are part of the same MST region? They don't sent their
whole instance-to-VLAN mapping table, do they?
No they don't send the whole mapping table, and it's not solely based on the MST
configuration name either... a hash is made of the instance-to-VLAN mapping table
contents, and the hash is sent to the next switch. If the neighboring switches' hashes
match, they are part of the same MST region
If a switch connected to MST-enabled switches uses CST, how do the STP instances
coordinate? What does MST do to make this coordination easier?
CST doesn't really care about the number of VLANs in an MST instance. MST creates
an Internal Spanning Tree (IST) instance that it presents to CST switches outside its
region, so the IST makes the MST region look like a single bridge
How many MST instances (MSTIs) can be present in an MST region?
Up to 16 MSTIs can be present in an MST region
What does a switch running CST see when it coordinates with switches running MST
(see picture)?
Which MST instance (MSTI) is allowed to send and receive MST BPDUs?
Only the IST (MSTI 0) is allowed to send and receive MST BPDUs. Information about
each of the other MSTIs is appended to the MST BPDU as an M-record. Therefore,
even if a region has all 16 instances active, only 1 BPDU is needed to convey STP
information about them all.
If a switch connected to MST-enabled switches uses PVST+, how do the STP instances
coordinate? What does MST do to make this coordination easier?
MST can detect this situation by listening to the received BPDUs. If BPDUs are heard
from more than one VLAN (the CST), PVST+ must be in use. When the MST region
sends a BPDU toward the PVST+ switch, the IST BPDUs are replicated into all the
VLANs on the PVST+ switch trunk.
What commands do you use to enable and configure MST on a switch?
- Step 1: Enable MST:
Switch(config)# spanning-tree mode mst
- Step 2: Enter MST Config Mode: Switch(config)# spanning-tree mst configuration
- Step 3: Assign a Region Config Name: Switch(config-mst)# name MyRegion
- Step 4: Assign a Region Config Revision #: Switch(config-mst)# revision 42
- Step 5: Map VLANs to an MSTI:
Switch(config-mst)# instance 1 vlan 4,5,7,10
Switch(config-mst)# instance 2 vlan 3,6,8,9
- Step 6: Commit the changes: Switch(config-mst)# exit
What are all the MST configuration commands?