User Manual

Table Of Contents
Insight Managed 8-Port Gigabit (Hi-Power) PoE+ Smart Cloud Switch with NETGEAR FlexPoE Power
Configure Switching User Manual147
The following table describes the nonconfigurable Auto-VoIP status information.
Table 25. Auto-VoIP status
Field Description
Auto-VoIP VLAN ID The Auto-VoIP VLAN ID.
Maximum Number of Voice Channels Supported The maximum number of voice channels supported.
Number of Voice Channels Detected The number of VoIP channels prioritized successfully.
Configure Spanning Tree Protocol
The Spanning Tree Protocol (STP) provides a tree topology for any arrangement of bridges.
STP also provides one path between end stations on a network, eliminating loops. Spanning
tree versions supported include Common STP, Multiple STP, and Rapid STP.
Spanning Tree Protocol overview
Classic STP provides a single path between end stations, avoiding and eliminating loops. For
information on configuring Common STP, see
Configure the CST port Settings on
page 151.
Multiple Spanning Tree Protocol (MSTP) supports multiple instances of spanning tree to
ef
ficiently channel VLAN traffic over different interfaces. Each instance of the spanning tree
behaves in the manner specified in IEEE 802.1w, Rapid Spanning Tree (RSTP), with slight
modifications in the working but not the end effect (chief among the effects is the rapid
transitioning of the port to the forwarding state). The difference between the RSTP and the
traditional STP (IEEE 802.1D) is the ability to configure and recognize full-duplex connectivity
and ports that are connected to end stations, resulting in rapid transitioning of the port to the
forwarding state and the suppression of Topology Change Notification. These features are
represented by the parameters pointtopoint and edgeport. MSTP is compatible with both
RSTP and STP. It behaves in a way that is appropriate for STP and RSTP bridges. An MSTP
bridge can be configured to behave entirely as an RSTP bridge or an STP bridge.
Note: For two bridges to be in the same region, the force version must be
802.1s and their configuration names, digest keys, and revision levels
must match. For additional information about regions and their effect
on network topology, refer to the IEEE 802.1Q standard.