Knowledge Base

    This plugin is an addition to benchmark device report. It compares the latest device logs to the previous task so that the NetBrain admin can easily figure out what just failed most recently. It needs to combine with an existing benchmark task and a report will be generated after benchmark task is completed. Below is a preview of the report....
    Read More »
    NetBrain users creates all site maps and benchmark is scheduled daily. However, the site maps are still up-to-date and always showing 'update map' link the top right corner of the maps. Site maps will not be updated automatically until "Update Site Maps" is enable in System Benchmark....
    Read More »
    Removing a device or site belonging to a site map, it will come back after update map while adding a device or site doesn't belong to a site map, it will be removed after update map. This type of customization will not be retained after either map update in a benchmark task or manual update map from a site map....
    Read More »
    NetBrain uses the default management interface selection order to select the management IPs that used for accessing to the devices. In some case the management IP NetBrain selection may be not expected as NetBrain could use the first IP it discovered on a device as the mgmt. IP when no matches found....
    Read More »
    Currently NetBrain could only add devices with the same telnet/SSH username to the device group. This guide instructs the steps to locate the devices that have SNMP RO string changed and update them accordingly. Out-dated SNMP RO could prevent NetBrain from accessing network devices via SNMP, which results inaccurate network topology, path failures, SNMP based Qapp failure, etc...
    Read More »
    Out-dated network credentials configured in Network Setting could prevent NetBrain from accessing network devices, which results inaccurate network topology, live path failures, benchmark failures, etc....
    Read More »
    NetBrain use ACI Fabric leaf ports to calculate license nodes. It would be a good idea to understand how many ports in the ACI instance before getting them discovered in NetBrain domain. This article instructs how to find out the total number of nodes that requires to discover an ACI fabric with a python program to retrieve the information from an APIC directly....
    Read More »
    Certain devices could have much bigger routing table size like Internet Edge Routers. Sometime the data table might be too big for NetBrain to retrieve it in 600 seconds (default), therefore NetBrain Front Server forces to break the connection....
    Read More »
    Maintaining network device access is the key to the success of NetBrain domain setup, which grants NetBrain the access to the Network where NetBrain benchmarks the device data. The higher rate NetBrain gets, the more accurate data, map, and topology NetBrain provides....
    Read More »
    Once ACI Fabric is discovered in NetBrain domain, the users are not only able to access ACI related data on the ACI maps from Network Pane, but also the Hybrid maps where shows the relationship between legacy network and ACI network. The best way to create a hybrid map is to utilize already-created site maps where all NetBrain users can easily access....
    Read More »
    To provide accurate and up-to-date network data for daily operations, it is essential for NetBrain admin to follow the instructions to maintain your domain data and your system on a regular basis....
    Read More »
    When discovering a new device with a management IP that already existed in NetBrain domain as an interface IP on another device, NetBrain could have different behaviors based on discovery methods....
    Read More »
    When discovering network devices, ICMP/SNMP/CLI are required by NetBrain to be able to perform a complete discovery. When a device doesn’t have SNMP access from NetBrain Front Server, discovery stops at this device and continue discovering others as SNMP returns the key information (ObjectID) from the device for NetBrain to determine the corresponding driver to perform CLI disc...
    Read More »
    NetBrain Discovery attempts to access all the IP addresses that it finds during Seed Discovery from configuration, route table, and CDP table. If attempts failed to access either SNMP or CLI to collect the configuration, the IP addresses will be saved in Unknown IP under Fine Tune manager from Domain Management interface. Identifying and resolving network devices among the Unkn...
    Read More »
    While discovering network devices, NetBrain checks all IP addresses from devices' configuration, CDP, and route table as source data via Seed Router Discovery or scan entire subnets via Scan IP Range. The discovered devices can be deleted from NetBrain domain. However, they will eventually come back if the IP addresses are part of discovery source data....
    Read More »
    Subscription
    Follow Knowledge Base posts
    Please enter your email address to subscribe:

    Email:
    Subscribe
    Tags