netbrain instant trial

NetBrain Instant Trial Essential Features Walkthrough

NETBRAIN ITE WORKBOOK | 2

Contents

1. Getting Started ................................................................................................................................................................ 3

2. Product Tour ................................................................................................................................................................... 4

2.1 Search and Map ...................................................................................................................................................... 4

2.2 Data Views .............................................................................................................................................................. 5

2.3 A/B Path .................................................................................................................................................................. 8

2.4 Executable Runbooks ............................................................................................................................................ 10

3. Technology Labs ............................................................................................................................................................ 13

Read This First: Lab Overview and Instructions ................................................................................................................ 13

3.1 ASA ........................................................................................................................................................................ 16

3.2 BGP ........................................................................................................................................................................ 17

3.3 EIGRP ..................................................................................................................................................................... 18

3.4 FabricPath ............................................................................................................................................................. 19

3.5 IPsec ...................................................................................................................................................................... 20

3.6 IPv6 ........................................................................................................................................................................ 21

3.7 IS-IS ........................................................................................................................................................................ 22

3.8 MPLS VPN .............................................................................................................................................................. 23

3.9 Multicast ............................................................................................................................................................... 24

3.10 OSPF ...................................................................................................................................................................... 25

3.11 OTV ........................................................................................................................................................................ 26

3.12 PVST ...................................................................................................................................................................... 27

3.13 QoS ........................................................................................................................................................................ 28

3.14 vPC......................................................................................................................................................................... 29

3.15 VTP ........................................................................................................................................................................ 30

3.16 VXLAN .................................................................................................................................................................... 31

4. Common Tasks & Workflows ........................................................................................................................................ 32

4.1 View Device Detail and Extend Neighbors ............................................................................................................ 32

4.2 Perform Health Check on Site Map ....................................................................................................................... 34

4.3 Export to Visio ....................................................................................................................................................... 36

4.4 Share via Email ...................................................................................................................................................... 37

4.5 Monitor CLI Variables with Instant Qapp .............................................................................................................. 38

Additional Questions? ........................................................................................................................................................... 39


1. Getting Started

Welcome to NetBrain’s Instant Trial Environment (ITE), a sandbox environment in which you can explore and experience a real, live deployment of the NetBrain platform. During your 14-day trial period, you have two different options available to explore. The Product Tour is a great way to truly get a feel for the power and flexibility of NetBrain’s core functionality. To take the Product Tour, refer to the Product Tour section of this manual. You will be taken on a guided tour of the key features of the product with step-by-step instructions. The Technology Labs are a new and exciting feature of NetBrain’s Instant Trial Environment. We have created a sandbox environment for you to explore what it’s like to analyze, monitor, and troubleshoot key networking technologies such as QoS, Multicasting, and BGP, using NetBrain. Through the Technology Labs you will experience how easy and intuitive it is to perform complex analyses using NetBrain’s built-in automation features and embedded expert knowledge.

Instructions:

1. To get started, login to NetBrain ITE web page

(https://ite.netbraintech.com). Enter your username and password. If you do not have a username and password, go to the page https://www.netbraintech.com/try-netbrain-now/ to register yourself. The registration can be done in one minute.

2. Select Initial Tenant for the Tenant field. You will then be given a choice to either select the Product Tour domain or the Technology Labs domain. Select the domain you would like to explore, and click Apply.

Tip To switch domains at any time, click on the domain name on the top right of the screen.

3. Continue with the instructions in the appropriate section of this workbook based on the domain you have selected.

Continue reading for the Product Tour or click to jump to Technology Labs.

https://ite.netbraintech.com/

https://www.netbraintech.com/try-netbrain-now/


2. Product Tour

Powered by deep network discovery (via CLI and SNMP), NetBrain’s Adaptive Network Automation provides instant collection, visualization, and analysis of critical network data, without the need to write any scripts. Important stories live in data but network teams struggle to make sense of the vast amount of information available – from telnet/SSH, SNMP, or collected through 3rd party network management tools. Visualization is a powerful means to discover and understand these stories, and fundamental for collaboration. NetBrain Dynamic Maps provide the following key advantages over static Visio maps:

• They can be created instantly – thousands of nodes can be mapped in seconds.

• They provide full visibility of the network including L3 and L2 topology, network design and operational status.

• Recurring benchmarks can be scheduled to keep the maps always update-to-date.

• User activity is recorded for change tracking purposes.

• Any task can be embedded into the map in the form of an Executable Runbook.

• Results of analyses are embedded into the map for future reference. •

Take this Product Tour to learn about NetBrain’s powerful map-based automation and visualization capabilities.

2.1 Search and Map

With NetBrain, your entire network becomes a searchable database. You can enter any search string (e.g., any part of an IP address,

hostname, vendor/model, routing protocol, or configuration file) and generate a new network map directly from the search results.

Instructions:

1. Click “+” button in the menu bar on the left and select New Map to create a new map.

Tip: If no map is created please adjust your browser settings to allow pop-ups from ite.netbraintech.com.

2. Type the configuration string “ospf 140” into the Search box and press the Enter key.

Tip: Remember to include the quotation marks to return an exact match.


3. All devices with OSPF 140 configured are displayed in the search results. Check the checkbox besides Device (6) to select all 6 devices in the search results. Then click the Map button to draw all devices on the map.

4. Scroll the wheel of your mouse to zoom in on the map to view more detail. Hover over a map label such as OSPF 140 AREA 0 to view the associated configuration.

2.2 Data Views

NetBrain’s Dynamic Maps are a single pane of glass integrating data from multiple sources, such as, configuration files, CLI

commands and 3rd party systems (via API integration). With Data Views, a virtually infinite amount of data can be layered on to a

single map.

1. View different layers of data: Starting from the “ospf 140” map created in the last section, click on Data View to open the Data View pane. A Data View layers additional data onto the map, e.g., basic maintenance information, design data, or operational status. Click on a Data View, such as Maintenance Information.


2. The maintenance information such as software version and serial number are displayed under the device.

Tip: Zoom in to see the maintenance information if it is not visible under a device.

3. View OSPF info: At the bottom of Data View pane select the Data View Template OSPF Configuration Decoding [Cisco IOS]. Additional OSPF information will be displayed under the devices.

Tip: You can view Data View template definitions in the Data View Template Manager

which can be accessed by clicking the icon at the top left corner of the page, and selecting Data View Template.


4. A new Data View is created and displayed on the map. Additional OSPF configurations can be viewed by clicking on the tables. Click on Table data such as OSPF Neighbors to view the device neighbors.

5. Switch Data Views: In the Data View pane, click on a different Data View to display its data on the map.

Tip: You can layer multiple Data Views onto a map by clicking the “eye” icon next to a Data View.


2.3 A/B Path

The first step in troubleshooting a slow application is to map the network path. Given any source and destination address, NetBrain

can map both L2 and L3 application paths based on live or already baselined data. NetBrain emulates real packet forwarding to

analyze how traffic flows across the network and takes into account deep network protocol analysis (e.g. routing, ACLs, PBR, NAT,

VRF).

Instructions:

1. Click the Path icon on the top menu bar and then click on the Path Setting icon. In the Path Setting window make sure the Path Analysis Set is set to L2 Path and select TCP for the protocol setting.

2. Enter the source IP and port as 192.168.11.64 …1025 and destination IP and port 192.168.11.10 … 80.

Select the one-way path direction as . Select the gateway device NB_BOS_HQ_CE2 for this source IP from the pulldown. Click the Path button to calculate the path.

3. Zoom into the map to view the details along the path, such as speed/duplex parameters.

Tip: You can drag to reposition the icons on the map to create the shape shown below.


4. Map L3 path: Click on the to close the map. Select the L3 Path option from the Path Setting and map the L3 path.

5. The path detail pane shows the devices along the path, the technologies being evaluated (ACL, NAT,

PBR, VRF, MPLS, etc.) and the execution log. Click to open the detail pane for the path map. Select a device to view the technologies evaluated on this device.

Tip: Uncheck Only show steps matched with the device to view all steps evaluated.

6. Close the path detail pane by clicking on the . Zoom into the map to view the details along the path, such as interface ACL detail.

Tip: Click the path curve and then the View Details button to bring back the path detail pane.

7. Once a path is mapped, additional analysis can be run

across all devices in the path to identify problem areas deserving attention. Run the Overall Health Monitor Qapp: From the map menu bar select Actions > Overall Health Monitor. In the Run Qapp window, click the Run button. Zoom in to check the device status and interface data for any abnormalities.

Tip: The Overall Health Monitor collects SNMP device and interface data, such as CPU, memory, bandwidth utilization, delay and errors. This information is displayed as map labels on the map.


2.4 Executable Runbooks

An Executable Runbook is an active flow chart. Each node of the chart corresponds to a step of a network task and can take the form

of an executable application (Qapp), a built-in function (e.g. ping or traceroute) or simply text (e.g. a note or a description). The

runbook takes the map data as input and the results are displayed on the map. Runbook analysis can be triggered via API integration

with 3rd party trouble-ticketing, monitoring or IDS/SIEM systems, when events such as slow application performance or a cyber-

attack are detected.

To learn about NetBrain’s built-in functions and runbooks for running design/configuration checks and for troubleshooting specific

technologies, such as QoS, multicast, dynamic routing (OSPF, IS-IS, BGP, EIGRP), etc. jump ahead to the Technology Labs section of

this workbook.

This section will walk you through how to use an Executable Runbook for troubleshooting common network problems.

Instructions:

1. We’ll start by mapping the path between two server endpoints. In the Path Settings select the L2 Path and IPv4 protocol, and map the path from 158.4.0.192 to 158.4.0.202, selecting NB_KC_L2R1 as default gateway.

Tip: Refer to section 2.3 for details on how to map the path.

2. Open a runbook: Click on Runbook Template in the

left menu and type in Interface Checking to search

for the runbook. Click the Create Runbook button at

the lower right to run the runbook on the current

map.

Tip: Save the map if prompted to do so. You

can save the map by clicking on the icon at the top right of the map.


3. Select Start to read the Runbook Description.

4. Select the first node, Check Neighbor Interface Speed and Duplex and click the Run button to run the Qapp. Any speed or duplex mismatches are highlighted and interface notes are added for details.

Tip: A Qapp can be run once or repeatedly. If the purpose of the Qapp is to check configurations, running once is enough. If the Qapp is used for monitoring the operational status, it should be run for a period of time to allow deltas to be computed, and intermittent issues to be identified.


5. Run the other nodes of the Interface Checking runbook to check interface MTU, port modes and VLAN allowed on trunk modes.

Tip: You can execute any node of a runbook in any order.


3. Technology Labs

NetBrain integrates with existing IT workflows such as network troubleshooting, design engineering, and cyber-defense, to provide

valuable insights and minimize time spent in the command-line interface and across disparate tools. NetBrain employs a Dynamic

Map as the single pane of glass for data correlation and analysis and Executable Runbook technology to codify tribal knowledge,

making it shareable and executable.

Explore NetBrain’s Technology Labs for 16 different technologies, including BGP, OSPF, EIGRP, IS-IS, QoS, Multicast, etc., to learn

about the many ways in which NetBrain’s built-in intelligence can help you automate day-to-day and strategic tasks associated with

a diverse set of technologies.

Read This First: Lab Overview and Instructions

A typical Technology Lab consists of a site map, one or two runbooks, and often a dashboard. This section will walk you through the

canonical workflow that can be applied to all the Technology Labs. Refer to the technology-specific sections of this manual for

further details about a specific technology lab.

Instructions:

1. From the NetBrain desktop double-click to open the Overview Map. Clicking on the Overview Map opens a map of all the Technology Labs’ sites.

Tip: In a typical NetBrain deployment, sites are how you would organize your network by geographical area. In the Technology Labs, however, we’re using them to organize lab devices by technology and category.

2. Double-click on the technology you wish to explore e.g., OSPF. This will take you into the NetBrain OSPF Lab environment.

Tip: The map has been annotated with the relevant Executable Runbooks and Dynamic Dashboards (if any) for you to explore. Most labs have two runbooks: Check Status and Troubleshooting Example.


3. Launch the Check OSPF Status runbook. Click on Runbook Template on the taskbar along the left of the screen and browse to the relevant runbook within the Built-in Runbooks -> Shared Runbook Templates folder. Click on the runbook name to see a preview of the runbook. Click Create Runbook to launch the runbook.

Tip: You can also search for a runbook from the search bar.

4. Click on any node to see a detailed description of that node. Click on the Start node to display the Purpose of Runbook.

Tip: If the details pane does not open automatically, click on > to open it. The top section of this pane is for recording your own notes. Scroll down to see the pre-populated description.

5. Each runbook node is executable by clicking on the Run button in the lower right corner. To explore the lab environment, run each node of the runbook to collect data and overlay it on the map

Tip: The map background turns green and a Control Panel pops up when data is being collected. Note that some nodes run in a continuous monitoring mode. Once you see results start to populate on the map you can Stop the collection at any time via the Control Panel.


6. Click the Run button on a runbook node that is designed to Retrieve CLI Commands. A dialog box appears showing the list of CLI Commands and target devices. Click Run to begin the data collection. Click on any device and CLI command to view the corresponding output.

Tip: The CLI commands will be automatically run across all devices on the map. Based on device type or configuration all CLI commands may not be accepted by all devices.

7. Each set of results is layered on to the map in the form of a Data View. You can click on the Data View > Local Data Views to see all the available Data Views created for that map. Layer a Data View on or

off by clicking on the eye icon next to it.

Tip: Zoom in or out to control the level of detail on the map. Look for a helpful legend on the bottom left to interpret the map. Click to open any yellow “sticky notes” to view device configurations and other data.

8. Finally, click on Files in the taskbar on the left to view the dashboards in Public > Dashboards and double-click on any dashboard to view NetBrain’s Dynamic Dashboards, pre-populated with data for selected technologies.

Note: You will notice that these dashboards are in View Only mode: the dynamic ability to collect and update data by running the dashboard widgets has been disabled in the lab environment.


3.1 ASA

In this lab, you will be checking the ASA design and failover status. For step-by-step instructions, please refer to the Lab Overview.

Using pre-defined runbooks, you’ll be able to:

• Highlight ASA Active/Standby devices

• Monitor interface status

• Monitor ASA failover status and view last failover time

• View device details

• Retrieve the output of CLI commands: show failover, show monitor-interface

What’s in the Lab:

• Site Map name: ASA

• Data View name: Failover [Cisco ASA Firewall]

• Executable Runbooks:

o ASA – Check Failover Status

• Dashboard: ASA Dashboard

ASA Failover Data View: 1) ASA active and standby devices are highlighted 2) ASA failover status and last failover time are displayed 3) Interface status is highlighted.


3.2 BGP

In this lab, you will be checking the BGP design and running status and troubleshooting a BGP neighbor connection caused by a

misconfiguration. For step-by-step instructions, please refer to the Lab Overview. Using pre-defined runbooks, you’ll be able to:

• View Router IDs, AS numbers, RR Cluster IDs, and BGP device configurations

• View BGP neighbor relationships (eBGP and iBGP)

• Retrieve device tables (Route Table, BGP Table, BGP Neighbor)

• Monitor the number of eBGP and iBGP neighbors

• Monitor the number of BGP table entries

• Troubleshoot a BGP neighbor connection by checking for misconfigured AS number and eBGP-multihop, and by verifying

ping connectivity to the source IP

• Retrieve the output of CLI commands: show show ip bgp, show ip bgp summary, show ip bgp neighbors, show ip bgp peer-

group, show ip route, show ip route bgp


• Site Map name: BGP


o BGP – Check Status

o BGP – Troubleshooting Example

• Dashboard: none

BGP Data View: 1) BGP Devices are highlighted by AS number 2) Router IDs, AS numbers, and RR cluster IDs are displayed as device labels. 3) BGP device configurations are annotated as a device note.


3.3 EIGRP

In this lab, you will be checking the EIGRP design and running status and troubleshooting a EIGRP misconfiguration. For step-by-

step instructions, please refer to the Lab Overview. Using pre-defined runbooks and dashboards, you’ll be able to:

• View EIGRP interfaces color-coded according to area numbers

• View EIGRP configuration annotated as a device note

• View EIGRP protocols, redistribute information and neighbors embedded in device tables

• Check for configuration mismatches (AS numbers, authentication, K values)

• Retrieve the output of CLI commands: show ip eigrp neighbors, show ip eigrp interfaces, show eigrp protocols, show ip eigrp

traffic, show ip eigrp topology

• View EIGRP configurations and device details, route summary, neighbors information, topology table and EIGRP logs in a

dynamically populated dashboard


• Site Map name: EIGRP


o EIGRP – Check Status

o EIGRP – Troubleshooting Example

• Dashboard: EIGRP Dashboard

EIGRP Data View: 1) Interfaces are highlighted in different colors according to area numbers 2) EIGRP configuration is annotated as a device note 3) EIGRP Protocols, redistribute information and neighbors are embedded as device tables.


3.4 FabricPath

In this lab, you will be checking the FabricPath running status and related IS-IS and Multicast configurations. For step-by-step

instructions, please refer to the Lab Overview. Using pre-defined runbooks, you’ll be able to:

• View switch ports with FabricPath configured

• View FabricPath configurations displayed as device notes

• View Fabricpath route tables displayed as device labels

• Highlight VLAN and interfaces with FabricPath configured

• Retrieve and display ISIS adjacency tables as device labels

• Discover and display the multicast and broadcast trees including the tree root and switches along the path

• Retrieve the output of CLI commands: show fabricpath isis topology summary, show fabricpath isis hostname, show

fabricpath isis adjacency, show run fabricpath, show fabricpath route


• Site Map name: FabricPath

• Executable Runbooks: FabricPath – Check Status

• Dashboard name: none

FabricPath Data View: 1) Switch ports having “mode fabricpath” configured are highlighted in green 2) The FabricPath configuration

is annotated as a device note 3) The FabricPath route table is displayed as a device label.


3.5 IPsec

In this lab, you will be checking the IPsec running status and troubleshooting an IPsec misconfiguration. For step-by-step

instructions, please refer to the Lab Overview. Using pre-defined runbooks and dashboards, you’ll be able to:

• View IPsec dev and peers

• View IPsec profile

• View IPsec configuration for phase 1 and phase 2

• Check SAs and encrypted/de-encrypted packet counts, and identify a mismatch

• Retrieve the output of CLI commands: show crypto engine connections ac, show crypto ipsec profile, show run | inc crypto,

show crypto en con ac

• View IPsec configurations and device details, crypto ISAKMP policy, ISAKMP SA, VPN session summary and crypto engine

connections in a dynamically populated dashboard


• Site Map name: IPsec


o IPsec – Check Status

o IPsec – Troubleshooting Example

• Dashboard: none

IPsec Data View: 1) IPsec devices are highlighted 2) IPsec configurations are annotated as a device note.


3.6 IPv6

In this lab, you will be checking the IPv6 routing protocol running status and troubleshooting a OSPFv3 authentication type

mismatch. For step-by-step instructions, please refer to the Lab Overview. Using pre-defined runbooks, you’ll be able to:

• View IPv6 configured devices and IPv6 interface addresses

• View configuration files and interface parameters for IPv6 configured protocols e.g., OSPFv3, RIPng, ISIS, BGP

• View devices configured with IPv6 static routes

• Highlight a mismatch in OSPFv3 Authentication Type e.g, No Authentication, Plain Text, MD5

• Retrieve the output of CLI commands: show ipv6 route, show ipv6 protocols, show ipv6 interface, show ipv6 ospf neighbor,

show ipv6 ospf neighbor detail, show ipv6 ospf interface, show ipv6 ospf database, show isis neighbors, show isis neighbors

detail, show isis database, show isis database detail, show isis topology, show ipv6 rip, show ipv6 rip database, show ipv6

static, show bgp ipv6 unicast, show bgp ipv6 unicast summary, show bgp ipv6 unicast neighbors


• Site Map name: IPv6


o IPv6 – Highlight Routing Protocols

o IPv6 – Troubleshooting Example


IPv6 Data View: 1) Devices configured with IPv6 routing protocols: OSPFv3, ISIS, RIPng, BGP are highlighted 2) The IPv6 address and

IPv6 interface protocol parameters (e.g., OSPFv3 10 area 0, RIP RIPTest, router isis) appear as interface labels


3.7 IS-IS

In this lab, you will be checking the IS-IS routing protocol design and running status and troubleshooting an IS-IS neighbor

connection. For step-by-step instructions, please refer to the Lab Overview. Using pre-defined runbooks and dashboards, you’ll be

able to:

• View IS-IS devices according to site ID

• View IS-IS neighbor tables for each device

• View IS-IS link types (level 1, level 2, level 1-2) and diagnose a level mismatch

• View encrypted links and interface passwords

• Retrieve the output of CLI commands: show isis neighbor, show isis database detail, show route isis


• Site Map name: IS-IS


o IS-IS – Check Status

o IS-IS – Troubleshooting Example

• Dashboard name: IS-IS Dashboard

ISIS Data View: 1) IS-IS interface tags and link types (level 1, level 2, level 1-2) are shown as link labels 2) IS-IS neighbors are embedded as device tables 3) IS-IS configurations are annotated as device notes.


3.8 MPLS VPN

In this lab, you will be checking the MPLS VPN running status and troubleshooting VRF reachability. For step-by-step instructions,

please refer to the Lab Overview. Using pre-defined runbooks, you’ll be able to:

• View the BGP, VRF and IGP (OSPF) design for the site

• Monitor overall health and performance of all devices

• Troubleshoot a reachability issue by verifying VRF routes are correctly populated and checking for misconfigured LDP

interfaces (is MPLS enabled?)

• Verify end-to-end ping connectivity for the Boston to San Francisco path

• Retrieve the output of CLI commands: show mpls forwarding, show ip bgp vpnv4 vrf all

• Map the L2 and L3 path between two nodes


• Site Map name: MPLS


o MPLS VPN – Check Status

o MPLS VPN – Troubleshooting Example


Tip: Click on Path at the top of the map and enter the source IP 10.0.1.69 (in Site 1) and destination IP: 10.0.2.68 (in Site 2).

Click on the Path Settings icon ( ) to switch from the L3 path to the L2 path and map both paths. Notice that access switches

are pure L2 devices and only show up in the L2 path.

MPLS Data View: 1) OSPF ASBR devices are highlighted 2) MPLS-configured interfaces, OSPF Area 0 interfaces and VRF interfaces are color coded 3) BGP design (IBGP and EBGP) is indicated with dotted arrows.


3.9 Multicast

In this lab, you will be checking the multicast network running status and troubleshooting a multicast RPF failure. For step-by-step


• Discover and display the Multicast Distribution Trees (Source Tree and Shared Tree)

• View the total number of PIM neighbors and receivers for each device

• View interface and device health metrics via SNMP

• View Rendezvous Point (RP), First Hop Router, Last Hop Router, Reporter and Multicast Source Device

• Retrieve results of the following CLI commands: show ip pim neighbor, show ip mroute, show ip mroute 228.1.1.1, show ip

route, show ip rpf 10.20.2.1

• View device details and configurations, multicast interface status, multicast packets, PIM neighbors table, and PIM hello

packets status in in dynamically populated dashboards


• Site Map name: Multicast


o Multicast – Troubleshooting Example

o Multicast Source Tree – Check Status

o Multicast Shared Tree – Check Status

Tip: Before running the Monitor Multicast Distribution Tree and Highlight Multicast Shared Tree nodes in these

runbooks, you’ll need to click into the Gtable hyperlink and supply NetBrain with the group address: 228.1.1.1 and

source address: 10.20.2.1.


Multicast Data View: 1) RP devices and interfaces running the multicast protocol are highlighted 2) Multicast protocol configuration

is annotated as a device note 3) PIM Neighbors and PIM Mroutes are embedded as device-level table data.


3.10 OSPF

In this lab, you will be checking OSPF neighbors and running status and troubleshooting duplicate router IDs. For step-by-step


• View ABR and ASBR devices, and interfaces color-coded by area number

• View OSPF configurations displayed as device notes

• View device data tables: OSPF Process ID, area information, neighbors, network info, redistribution info, total neighbors, up

neighbors, flapping neighbors, and OSPF routes

• Verify interface and device reachability

• Identify devices with duplicate IDs

• Retrieve the output of CLI commands: show ip ospf, show ip ospf database database-summary, show ip ospf database,

show ip ospf interface, show ip ospf neighbor, show ip ospf neighbor detail, show ospf overview, show ospf interface, show

ospf neighbor, show ospf neighbor detail, show ospf database, show ospf database summary

• View OSPF neighbors, interface parameters, route summary, SPF algorithm information, LSA count per area, and all OSPF-

related logs in a dynamically populated dashboard


• Site Map name: OSPF


o OSPF – Check Status

o OSPF – Troubleshooting Example

• Dashboard name: OSPF Dashboard

OSPF Data View: 1) ABR and ASBR devices are highlighted by color 2) Interfaces are color-coded by area number 3) OSPF

configurations are annotated as device notes 4) OSPF table data is embedded for each device.


3.11 OTV

In this lab, you will be checking the OTV design and running status and troubleshooting an OTV adjacency issue caused by a

misconfigured PIM connection. For step-by-step instructions, please refer to the Lab Overview. Using pre-defined runbooks, you’ll

be able to:

• Highlight OTV edge devices according to site ID

• Highlight internal and join interfaces according to site ID

• View OTV configurations annotated as device notes

• Highlight VLAN and trunk links related to OTV

• Monitor OTV adjacent neighbors (illustrated with the arrows on the map)

• Retrieve the device tables: OTV Adjacency, OTV Route, OTV ARP and OTV VLAN

• Monitor the number of OTV adjacency links and OTV VLANs

• Monitor the utilization of OTV WAN links

• Annotate OTV PIM misconfigurations as a device note

• Retrieve the output of CLI commands: show otv, show otv adjacency, show otv vlan, show otv arp, show arp


• Site Map name: OTV


o OTV – Check Running Status

o OTV – Troubleshooting Example


OTV Data View: 1) OTV Edge Devices are highlighted by site ID 2) Internal and join interfaces are highlighted 3) OTV device configurations are annotated as device notes.


3.12 PVST

In this lab, you will be checking the PVST design and running status and troubleshooting connectivity between two devices. For

step-by-step instructions, please refer to the Lab Overview. Using pre-defined runbooks and dashboards you’ll be able to:

• View devices highlighted according to STP mode and PVST configurations annotated as device notes

• View VLAN information displayed along each switch port and view switch port status

• View edge port configurations (Fast Port, BPDU Guard Port, BPDU Filter Port)

• View the root bridge and forwarding/blocking ports for a given VLAN

• Monitor the PVST role and status of switch ports

• Check interface forward status, interface error disabled and MAC address table

• Retrieve the output of CLI commands: show mac address-table count, show spanning-tree, show spanning-tree summary,

show vlan brief, show spanning-tree root, show vlan brief, show spanning-tree vlan $Vlan_id, show spanning-tree bridge

address, show interface status

• View PVST device and configuration details, switch port status and PVST switch summary information in a dynamically

populated dashboard


• Site Map name: PVST


o PVST – Check Status

Tip: Before running the Highlight PVST and Monitor Spanning Tree Status nodes, you’ll need to click into the

VlanTable hyperlink and add the value 100 for the VLAN ID.

o PVST Troubleshooting Example Runbook

• Dashboard name: PVST Dashboard

Spanning Tree Data View: 1) Devices are highlighted according to STP mode 2) PVST configurations are annotated as device notes 3) VLAN information is displayed along each switch port.


3.13 QoS

In this lab, you will be checking the QoS protocol status and troubleshooting output drops. For step-by-step instructions, please

refer to the Lab Overview. Using pre-defined runbooks and dashboards, you’ll be able to:

• Highlight devices configured with QoS

• Highlight interfaces by congestion management queue (LLQ/CBWLQ)

• View QoS configurations and policy tables for each device

• Monitor QoS Offered and Drop Rate table

• Verify interface and device reachability

• Retrieve the output of CLI commands: show policy-map interface, show class-map, show policy-map, show interfaces, show

logging

• Monitor device details and configuration information, class map offered and drop rate, and class map police detail in a

dynamically populated dashboard


• Site Map name: QoS


o QoS – Check Status

o QoS – Troubleshooting Example

• Dashboard name: QoS Dashboard

QoS Interface Queuing Strategy Data View: 1) QoS devices are highlighted 2) Interfaces are color-coded by congestion management

queue (LLQ/CBWLQ) 3) QoS configurations are annotated as device notes 4) QoS policy tables are displayed for each device.


3.14 vPC

In this lab, you will be checking and monitoring the vPC operational status. For step-by-step instructions, please refer to the Lab

Overview. Using a pre-defined runbook, you’ll be able to:

• View vPC links and peer links color-coded on the map

• View vPC configurations annotated as device notes on the map

• Highlight the device with the primary VPC role and view its device data: vPC domain ID, Peer status, vPC keep-alive status

and number of vPC configured, vPC system-mac, vPC system-priority, vPC local system-mac and vPC local role-priority

• View vPC status table and vPC peer link status table

• Retrieve the output of CLI commands: show running-config vpc, show vpc role, show vpc brief


• Site Map name: vPC

• Executable Runbooks: vPC – Check Status


vPC Data View: 1) vPC links and peer links are color-coded on the map 2) vPC configurations are annotated as device notes on the

map.


3.15 VTP

In this lab, you will be checking the VTP running status and troubleshooting a missed VLAN in the VTP client. For step-by-step

instructions, please refer to the Lab Overview. Using pre-defined runbooks, you’ll be able to:

• View VTP Roles, VTP Server, VTP Client, VTP Transparent highlighted on the map

• View VTP Domain name, VTP Mode, VTP running version, configuration version, and VTP pruning mode embedded as

device-level data tables

• Check for password mismatch and interface mismatch

• Retrieve the output of CLI commands: show show vlan brief, show vtp status, show vtp devices, show vtp counters, show vtp

interface, show vtp password, show interfaces trunk


• Site Map name: VTP


o VTP – Check Status

o VTP – Troubleshooting Example


VTP Data View: 1) VTP Roles, VTP Server, VTP Client, VTP Transparent are highlighted 2) VTP Domain name, VTP Mode and VTP running version is embedded as device-level data table.


3.16 VXLAN

In this lab, you will be checking and monitoring the VXLAN running status and troubleshooting an interface MTU mismatch. For

step-by-step instructions, please refer to the Lab Overview. Using pre-defined runbooks, you’ll be able to:

• View VNI-VLAN mapping table embedded as device data

• Highlight leaf and spine devices

• View NVE interface and bridge-domain configuration for leaf devices

• View the underlying routing protocol configurations (EIGRP and PIM neighbors)

• Check multicast status by highlighting PIM config and enabled interfaces

• Check VTEP peers status table

• Highlight interface MTUs and identify any inconsistencies

• Retrieve the output of CLI commands: show nve peers


• Site Map name: VXLAN


o VXLAN – Check Status

o VXLAN – Troubleshooting Example


VXLAN Data View: 1) VNI-VLAN mapping tables are embedded as device data


4. Common Tasks & Workflows

4.1 View Device Detail and Extend Neighbors

NetBrain turns your entire network into a searchable database. You can find any device, view its details, and extend its L2 and L3

neighbors to create a map of its connections.

Instructions:

1. Search for a device: You can find a device or create a group of devices by searching for any part of a hostname, IP address, configuration file, device type, vendor, etc. Type hostname NB_BOS_HQ_CE1 into the Search box and press the Enter key.

Tip: Just type in the first few letters of the hostname and select the device from the pulldown menu.

2. The search results are organized by All (devices), Configurations, Map and Dashboard. Click into the hostname NB_BOS_HQ_CE1 to view the device detail.


3. Device detail information such as vendor, model, software version as well as configurations, route table and CDP tables are displayed. A preview map with three of its neighbors are shown. Click Open Map link to create a new map.

Tip: You can also close the Device Detail page to return to the search results page. From the search results drag and drop a device icon to open a new map for just this device without its neighbors.

4. Extend L3 neighbors: Click the attached to a device

icon to add neighbor devices to the map. In the Neighbors window, you can view all neighbor devices or filter neighbor by the interfaces and type of topology. For example, select the interface f0/1 of the device NB_BOS_HQ_CE1 to view three devices connected to this interface. Click a neighbor device to select a neighbor and click Add to Map button to draw it. You can select multiple devices.

Tip: Double click an interface to draw all neighbor devices connected to that interface in the map. You can also double-click All Neighbors to draw all neighbors on the map.

5. Extend L2 neighbors: In the Neighbors window, select L2 Topology from the pulldown menu of the topology and add L2 neighbors to the map. For example, for the device NB_BOS_HQ_CE2, select L2 Topology and double click All Neighbors to add all its neighbors in the map.


6. Repeat the step 5 and 6 till you have all devices you are interested in on the map.

4.2 Perform Health Check on Site Map

NetBrain discovers your entire network at a rate of 2000 devices per hour with its patented neighbor-walking algorithm. You can

explore the hierarchical virtual model, organized by site, and run a health check on any site.

Instructions:

1. Open a site map: Click Site in the left menu bar and browse through the site US/Canada > United States of America > MASSACHUSETTS > BOSTON. Right click the site and select Open Site Map from the menu.

Tip: The number in parentheses next to a site is the number of devices belonging to the site. A device can only belong to a leaf site which does not have any child sites.

2. The site map of a parent site shows how its child sites are connected. Zoom in to view more connection details.

Tip: A parent site has one or more child sites. Its site map shows the connections of its child sites. The site map of a leaf site shows the connections of its network devices in addition to the connections between its network devices and neighbor sites.


3. Right click the leaf site BOS_NB_SITE2 from the site tree or from the BOSTON site map to open its site map. The site map draws all devices belonging to this site and their IPv4 connections.

4. Auto layout: Right click the map and select one of layout algorithms such as Tree Layout Up for a better layout for the map. You can also drag any object on the map to adjust its position.

5. Run Overall Health Monitor: From the actions menu along the top of the map, select Actions > Overall Health Monitor. In the Run Qapp window, click Run.


6. The map background turns green in the monitoring mode. Zoom in to see more details, such as interface traffic and errors.

Tip: A Data View is created when a Qapp is executed on a map. For example, the Overall Health Monitor Data View can be viewed into the Data View > Local Data View pane. You can turn the monitored data display on and off by clicking on the “eye” icon in the Data View pane.

4.3 Export to Visio

NetBrain maps can be exported to Microsoft Visio diagrams, and auto-updated, with just a few clicks.

Instructions:

1. Export to Visio: Click on Map in the top left of the

map menu and select the Export to Visio option.

Tip: You may be prompted to save the map

but you may not have the rights to do so. In this

case you can click on the icon and save the

map to the Desktop.

2. Your map, including embedded detail, is exported to

a .vsd file.


4.4 Share via Email

Both for major team initiatives as well as day-to-day collaborative tasks, your team can operate off a common map, and seamlessly share

data and notes.

Instructions:

1. Share a map via email: Click the Share Map icon in the map menu bar. Select the users you want to share the map with and add any notes. Click the Share button to send an email with an embedded map link to the selected users.

Tip: You may not have the rights to save the map. In this case the system will ask you whether you want to share the original map instead. Select Share Original Map.

2. Your note, the map link and a map image are contained in the email you sent. The link will bring the recipient of the email directly to the NetBrain map you were working on, so they can continue working on the same map with all its existing data.


4.5 Monitor CLI Variables with Instant Qapp

NetBrain can automatically parse variables from any CLI command using its Parser Library. You can drag and drop these variables onto a map to instantly visualize the results, and continuously monitor these variables at a set frequency e.g. every minute.

Instructions:

1. Search and view variables from CLI commands: In the search box within the map, you can enter any CLI command you are interested in, such as show interface. Select Instant Qapp and then type show interface and then click on the table named intfs_table to expand the table. Select a variable such as crc by clicking the circle icon in the corner of the label. You can select multiple variables.

2. Drag and drop the selected variables onto the map. The system starts retrieving data from the live network and the results are displayed on the map.


3. Monitor variables on a set frequency: Change Data Source to Pull live data regularly. Set the frequency e.g., every 10 seconds. Click OK and then RUN. Save the map if prompted. The map switches to monitoring mode.

Tip: A new Data View Monitor Variables Periodically is created.

Additional Questions?

If you have additional questions, please contact us.

Support questions: Training questions:

+1 800.605.7964

[email protected]

+1 800.605.7964

[email protected]

mailto:[email protected]

mailto:[email protected]

netbrain instant trial

Documents