User Manual
Table Of Contents
- GS728TS, GS728TPS, GS752TS, and GS752TPS Gigabit Smart Switches
- Contents
- 1. Getting Started
- Getting Started with the Smart Switches
- Switch Management Interface
- Connecting the Switch to the Network
- Switch Discovery in a Network with a DHCP Server
- Switch Discovery in a Network without a DHCP Server
- Configuring the Network Settings on the Administrative System
- Web Access
- Smart Control Center Utilities
- Understanding the User Interfaces
- Interface Naming Convention
- 2. Configuring System Information
- 3. Configuring Switching Information
- 4. Configuring Routing
- 5. Configuring Quality of Service
- 6. Managing Device Security
- 7. Monitoring the System
- 8. Maintaining the System
- 9. Accessing Help
- A. Hardware Specifications and Default Values
- B. Configuration Examples
- C. Notification of Compliance
- Index
319
GS728TS, GS728TPS, GS752TS, and GS752TPS Gigabit Smart Switches
though frames belonging to different VLANs can take different paths within any Region, per
IEEE DRAFT P802.1s/D13.
All bridges, whether they use STP, RSTP or MSTP, send information in configuration
messages via Bridge Protocol Data Units (BPDUs) to assign port roles that determine each
port’s participation in a fully and simply connected active topology based on one or more
spanning trees. The information communicated is known as the spanning tree priority vector.
The BPDU structure for each of these different protocols is different. A MSTP bridge will
transmit the appropriate BPDU depending on the received type of BPDU from a particular
port.
An MST Region comprises of one or more MSTP Bridges with the same MST Configuration
Identifier, using the same MSTIs, and which have no Bridges attached that cannot receive
and transmit MSTP BPDUs. The MST Configuration Identifier has the following components:
1. Configuration Identifier Format Selector
2. Configuration Name
3. Configuration Revision Level
4. Configuration Digest: 16-byte signature of type HMAC-MD5 created from the MST
Configuration Table (a VLAN ID to MSTID mapping)
As there are Multiple Instances of Spanning Tree, there is a MSTP state maintained on a
per-port, per-instance basis (or on a per port per VLAN basis: as any VLAN can be in one
and only one MSTI or CIST). For example, port A can be forwarding for instance 1 while
discarding for instance 2. The port states have changed since IEEE 802.1D specification.
To support multiple spanning trees, a MSTP bridge has to be configured with an
unambiguous assignment of VLAN IDs (VIDs) to spanning trees. This is achieved by:
1. Ensuring that the allocation of VIDs to FIDs is unambiguous.
2. Ensuring that each FID supported by the Bridge is allocated to exactly one Spanning Tree
Instance.
The combination of VID to FID and then FID to MSTI allocation defines a mapping of VIDs to
spanning tree instances, represented by the MST Configuration Table.
With this allocation we ensure that every VLAN is assigned to one and only one MSTI. The
CIST is also an instance of spanning tree with a MSTID of 0.
An instance may occur that has no VIDs allocated to it, but every VLAN must be allocated to
one of the other instances of spanning tree.
The portion of the active topology of the network that connects any two bridges in the same
MST Region traverses only MST bridges and LANs in that region, and never Bridges of any
kind outside the Region, in other words connectivity within the region is independent of
external connectivity.










