Troubleshoot Spanning-Tree
[ Map + App ]

The primary function of spanning-tree is to cut loops that redundant links create in a layer-2 network. But this can fail in some cases, causing a bridging loop (a port that should block traffic forwards it instead). Some design issues leading to bridging loops include hello-timer mismatch, improperly enabled PortFast , or even a duplex mismatch.

NetBrain can help you troubleshoot spanning-tree effectively by enabling you to identify bridging loops, find spanning-tree resource errors, detect duplex mismatches, and diagnose port utilization. You can use a dynamic network map to target the relevant LAN segment and then drill down with apps to automatically diagnose spanning-tree performance, levering NetBrain's 'Map+App' troubleshooting methodology.

Back to the top

Build a Map

To visualize the bridge network

In order to know what to fix in the network, you need to know what the bridge network topology looks like, including the locations of redundant links. NetBrain can help you visualize the topology instantly. You can drill down into an existing map, or create a new targeted map from a simple keyword search. The resulting (live) network map is your ‘single pane of glass’ for troubleshooting and analysis.

Drill down from a Layer-3 map to see redundant links in a Layer-2 map

Learn More About Dynamic Network Diagrams »

Back to the top

Run Apps

To diagnose spanning-tree

A NetBrain app provides a way for you to collect the STP data you’re looking for without having to log into a bunch of switches serially and type in a string of show commands. NetBrain has several built-in apps that can automate STP diagnoses. Most importantly, you can easily write your own to automate many more. These apps leverage the map as the 'canvas' for your targeted data analysis.

Recommended App: Highlight STP

In order to troubleshoot spanning-tree, you first need to know what is the current state of the spanning-tree algorithm. NetBrain’s built-in Highlight STP app helps you immediately identify the following STP information:

  • What is the location of the root bridge
  • Where are the redundant links
  • What is the location of the blocked ports

Run App 'Highlight STP'

This App Highlights the Root Bridge and Forwarding/Blocking Ports in Real-Time

This app can be run on both the live and historic network. The benefit is that you can look back at a previous network state to see if the root bridge has changed, or to identify a previous STP converged state.

Back to the top

Recommended App: Monitor Network Health

An interface with traffic overload can fail to transmit vital BPDUs. A link overload also indicates a possible bridging loop. Therefore, a great way to identify a bridging loop is to check the port utilization on your devices and look for abnormal values. Additionally, a high CPU utilization can be dangerous for a system running spanning-tree.

The Monitor Network Health app will automatically look for both excessive port utilization and CPU utilization.

This App Displays Live Interface and CPU Utilization on the Map

This app will generate alarms if the threshold is exceeded for maximum port or CPU utilization levels. So if there’s a broadcast storm, you can be alerted that the network is behaving symptomatically. Further, you’ll have the ability to plot this data over time, so you can see if any spikes are occurring.

Collect and Log App Data over Time

Back to the top

Recommended App: Detect Speed/Duplex Mismatch

In some cases a bridge sending BPDUs may have the duplex mode set to half-duplex on one port, but the peer port on other end has the duplex mode set to full-duplex. This duplex mismatch on the link between the two bridges can easily lead to a bridging loop because bridge B would not perform carrier sense before link access.

This app will automatically detect if any duplex mismatches exist in the bridge network and annotate them on the map if they exist.

This App Detects Speed or Duplex Mismatches Automatically

Back to the top

Write Your Own Apps

There are over a dozen show commands for IOS alone that you may use to troubleshoot spanning-tree. Rather than issuing these commands one-by-one across each switch, you may choose to write an app that will perform that task for you automatically.

Writing an app is almost as easy as typing a show-command. There's no complex syntax or steep learning curve - after just 15 minutes of training you’ll be ready to write your first app. There are three main steps:

Step 1:
Define Variables of Interest

A sample of CLI command data is used to identify variables which indicate fields of interest. For example, an interface diagnosis app may use the 'show interface' IOS command to extract the speed and duplex from each interface.

Step 2:
Define Data Positions on the Map

An app uses the map to display the desired device and interface data. The positions of the data on the map are easily defined during app definition.

Step 3 (optional):
Define Alarm Thresholds

To raise an alarm, you can indicate a threshold condition and associated warning message which is raised if the variable exceeds the threshold.

After you write an app, you can run it directly on the map, as if it was built into the software:

Example Custom App Using ‘Show Interface’ IOS Command to Extract Interface Errors

Learn More About NetBrain Apps »

Back to the top

Solve virtually any network problem with NetBrain's ' Map + App'

Ready for more? See it in action. WATCH DEMO