User Manual
Table Of Contents
- Insight Managed 8-Port Gigabit (Hi-Power) PoE+ Smart Cloud Switch with NETGEAR FlexPoE Power
- Contents
- 1 Getting Started
- Available publications
- Switch management options and default management mode
- Manage the switch by using the local browser UI
- Access the switch
- Credentials for the local browser UI
- Register and access the switch with your NETGEAR account
- Change the management mode of the switch
- Change the language of the local browser UI
- How to configure interface settings
- Use the Device View of the local browser UI
- 2 Configure System Information
- View or define system information
- Configure the IP network settings for management access
- Configure the time settings
- Manage the denial of service settings
- Configure the DNS settings
- Configure green Ethernet settings
- Manage the Bonjour settings and view Bonjour information
- Control the LEDs
- Use the Device View
- Configure Power over Ethernet
- Configure SNMP
- Configure Link Layer Discovery Protocol
- Configure DHCP snooping
- Set up Power over Ethernet timer schedules
- 3 Configure Switching
- Configure the port settings and maximum frame size
- Configure link aggregation groups
- Configure VLANs
- Manage the basic VLAN settings
- Configure VLAN membership
- View the VLAN status
- Configure the PVID settings for an interface
- Configure a MAC-based VLAN
- Configure protocol-based VLAN groups
- Configure protocol-based VLAN Group membership
- Configure a voice VLAN
- Configure the GARP switch settings
- Configure GARP ports
- Configure Auto-VoIP
- Configure Spanning Tree Protocol
- Configure multicast
- Configure multicast VLAN registration
- View, search, and configure the MAC address table
- Configure Layer 2 loop protection
- 4 Configuring Routing
- 5 Configure Quality of Service
- 6 Manage Switch Security
- Change the local device password for the local browser UI
- Manage the RADIUS settings
- Configure TACACS+ settings
- Configure authentication lists
- Configure management access
- Control access with profiles and rules
- Configure port authentication
- Set up traffic control
- Configure access control lists
- Use the ACL Wizard to create a simple ACL
- Configure a MAC ACL
- Configure MAC ACL rules
- Configure MAC bindings
- View or delete MAC ACL bindings in the MAC binding table
- Configure a basic or extended IPv4 ACL
- Configure rules for a basic IPv4 ACL
- Configure rules for an extended IPv4 ACL
- Configure an IPv6 ACL
- Configure rules for an IPv6 ACL
- Configure IP ACL interface bindings
- View or delete IP ACL bindings in the IP ACL binding table
- Configure VLAN ACL bindings
- 7 Perform Maintenance Tasks
- 8 Manage Power over Ethernet
- 9 Monitor the Switch
- A Configuration Examples
- B Switch Default Settings and Hardware Specifications
Insight Managed 8-Port Gigabit (Hi-Power) PoE+ Smart Cloud Switch with NETGEAR FlexPoE Power
Configuration Examples User Manual457
Multiple Spanning Tree Protocol (MSTP)
Spanning Tree Protocol (STP) runs on bridged networks to help eliminate loops. If a bridge
loop occurs, the network can become flooded with traffic. IEEE 802.1s Multiple Spanning
Tree Protocol (MSTP) supports multiple instances of spanning tree to efficiently channel
VLAN traffic over different interfaces. Each instance of the spanning tree behaves in the
manner specified in IEEE 802.1w, Rapid Spanning Tree, 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 to 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 a RSTP bridge or an STP bridge.
So, an IEEE 802.1s bridge inherently also supports IEEE 802.1w and IEEE 802.1D.
The MSTP algorithm and protocol provide simple and full connectivity for frames assigned to
any given VLAN throughout a bridged LAN comprising arbitrarily interconnected networking
devices, each operating MSTP, STP, or RSTP. MSTP allows frames assigned to different
VLANs to follow separate paths, each based on an independent Multiple Spanning Tree
Instance (MSTI), within Multiple Spanning Tree (MST) regions composed of LANs and or
MSTP bridges. These regions and the other bridges and LANs are connected into a single
Common Spanning Tree (CST). (IEEE DRAFT P802.1s/D13)
MSTP connects all bridges and LANs with a single Common and Internal Spanning Tree
(CIST). The CIST supports the automatic determination of each MST region, choosing its
maximum possible extent. The connectivity calculated for the CIST provides the CST for
interconnecting these regions, and an Internal Spanning Tree (IST) within each region.
MSTP ensures that frames with a given VLAN ID are assigned to one and only one of the
MSTIs or the IST within the region, that the assignment is consistent among all the
networking devices in the region, and that the stable connectivity of each MSTI and IST at
the boundary of the region matches that of the CST. The stable active topology of the bridged
LAN with respect to frames consistently classified as belonging to any given VLAN thus
simply and fully connects all LANs and networking devices throughout the network, 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 through 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. An MSTP bridge
transmits the appropriate BPDU depending on the received type of BPDU from a particular
port.