...
Issues are so important in NetMRI that a specific administrator user account is defined to manage them. For information, see Understanding Users and Roles.
The Issues pages are probably the most frequently used of all NetMRI features, designed to quickly and conveniently monitor the overall health of the network. In the Network Analysis –> Issues tab, the Network Scorecard shows the results of the daily analysis process and all issues generated for the latest time period. Issues can also be filtered.
...
The Network Scorecard (Network Analysis tab –> Issues tab) provides a high-level performance metric for the managed network. NetMRI measures the network's daily stability and correctness and calculates the normalized Scorecard value based on a statistical analysis of all issues discovered for that day. Counts of the three primary Issue types (Info, Warning and Error) also are shown.
The Network Scorecard shows the scorecard value for the current day, and a two-color graph showing the stability and correctness values over the selected time period, which by default is the last day's measurement.
Stability and correctness values are two data sets that cumulatively add up to the Overall Score in the Scorecard. Each data set has a maximum value of 5.0.
Stability issues are caused by events such as excessive spanning tree topology changes, unstable links, congestion and excessive CPU/memory utilization. Correctness issues are derived from configuration or design errors such as duplicate VLAN ID/name pairs or inconsistent routing protocol timers. Stability and correctness are measured across a variety of functional areas of the network.
The Network Scorecard table shows correctness and stability values by component area (hover over an indicator rectangle to see the numerical values). Stability and correctness "penalties" associated with each issue depend on the type and severity of the issue. Stability and correctness penalties for all components of the network combine to create the overall Network Scorecard value, expressed as the Overall Score in the upper right corner of the Scorecard.
...
The Issues by Device with Historic Chart view provides an adjustable view of Issue trends for any selected device group. The time period resides on the horizontal X axis, and the measurement, in number of issues, is on the vertical Y axis. Click the Time Selector drop-down menu to change the X-axis time period for the Historic chart.
The Historic chart displays up to four data sets: Adds, indicating the quantity of new Issues for each time period, Same, indicating Issues the time period that remain from the preceding time period; Cleared, indicating Issues that have been cleared from the system due to administrative remediation or other causes; and Suppressed, which shows the relative quantity of Issues that have been suppressed due to admin configuration of Issues that may be deemed to produce excessive notifications in each time period. Issue counts for each time increment appear as stacked bars in the chart. Move the mouse over any colored bar section to view the count for that Issue type.
To see a longer description of any issue, hover over the hyperlink in the Title column. Columns that are displayed by default include the following:
...
- Clicking one of the nine Component links at the bottom of the ScorecScorecard;
ard;Anchor bookmark284 bookmark284 - Clicking the Filters button at the top right of the Issues list, and choosing the columns and values to match against;
- Click the Display button and choose one of the drop-down menu options: All, Current, New, Cleared or Suppressed;
- Use the Search box at the top left of the Issues table to search for a characteristic phrase or word that appears as part of an issue title.
...
View an issue's details by clicking the issue title hyperlink. The Issues Viewer opens in a separate browser window, which lists the network components affected by the issue along with any relevant details. (Many Issue details appear in this window that do not appear in the main Issue table or in summaries.) You use the Issue Viewer toolbar to suppress or unsuppress an Issue; schedule a job to address an Issue type; send an email summary; and other operations.
Click a component's IP address hyperlink to open the corresponding Device Viewer for that network component.
The Issue Viewer provides a History chart for the specific issue instance, indicating the number of components affected by the issue over the past 30 days. (The chart measurement timeline can be adjusted to the standard Daily, Weekly, Monthly, 7-Day and 30-Day increments. Click the Time Selector drop-down menu to change the X-axis time period for the Issue Viewer. (Similar Issue information is also found for individual devices, under Device Viewer –> Network Analysis –> Issues.) The History chart is useful for determining how often this issue occurs and how much of the network is affected.
Issue details include how the issue has changed since the last run:
...
Set thresholds using the Criteria property available in the Settings icon –> Issue Analysis –> Issue Group Settings –> Device Groups side tab and Interface Groups side tab.
Click the Comprehensive Issue List under Additional Documentation in online Help for more detailed Issue listings to assist in decisions on which issues to isolate to specific device groups or interface groups.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Notifications
| Anchor | ||||
|---|---|---|---|---|
|
...
Issues generated by NetMRI are strong indicators of potential serious problems with the network. As such, you may want to be informed whenever certain issues are generated. The Issue Notification feature is provided for such purposes, allowing you to request one or more notifications to be sent via various protocols to various destinations. All notification messages can be fully customized and multiple delivery protocols are supported.
Issue notifications are listed and created, in the Settings icon –> Notifications section –> Subscriptions page. Notifications can be sent in one of three ways:
...
Note: A valid SMTP Server name or IP address must be entered before anyone can create an e-mail notification.
Further, the SMTP Server must be configured to accept incoming e-mail messages from NetMRI for them to be relayed to the appropriate destinations.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Viewer
| Anchor | ||||
|---|---|---|---|---|
|
...
The Issue Viewer appears in a new window when you click any issue hyperlink. By default, the Issue Viewer displays all issues of the selected type in a table, that occur across all NetMRI-managed devices. You can also filter the issue instances that appear in this window. Below the table, two important tabs appear.
The History tab provides a chart showing recent activity for the issue. The Issue Viewer is not device-specific: it is Issue-specific, which means that all devices that exhibit the issue may be listed in the Viewer, in the Components Affected by Issue table. (The instance shown to the left lists a single device, but this will not be the case for many Issue instances.) Devices are listed by their IP address and device name. The Issue Viewer's Components Affected by Issue table also shows a set of data columns crafted to match data reporting for the specific Issue.
History displays the stacked bar chart showing the four data sets Adds, showing new instances of the specific Viewer issue, Same, reflecting issue instances still present since their first appearance; Drops, instances no longer present and Suppressed, instances that are suppressed. The time span for the History chart can be adjusted as for other chart instances.
The Description tab explains the issue. The Description is taken from the Comprehensive Issue List.
To filter issues displayed in the Issue Viewer:
From the In list (in the page header), select the Device Group. All instances of the specific Issue across all related devices in the Group will be listed in the Issue Viewer.
...
To suppress an issue type for a device: click the check box for that device, then click Suppress Issues below the table.
To unsuppress an issue type for a device: Uncheck the check box for that device, then click Unsuppress Issues below the table.
...
Note: You can automate the notification process in the Settings icon –> Notifications section –> Subscriptions page.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Issues
| Anchor | ||||
|---|---|---|---|---|
|
...
Note: NetMRI automatically clears all custom Issue instances from the Network Analysis –> Issues page precisely 24 hours after each of the Issues appear, as the result for the executed jobs or scripts run by the administrator. Following the erasure of the Issue instance, the Issue associated with the job will appear again only when the job executes.
...
Create and manage custom issues from the Config Management tab –> Job Management –> Custom Issues page.
Perl and CCS Scripts can reference custom issues to bring attention to conditions discovered during script processing. Check the Comprehensive Issue List under Additional Documentation in online Help for more detailed Issue listings; it is possible that an Issue already exists for script reporting purposes.
To create a new custom issue, do the following:
...
Issue help files are stored in the Backup/IssueHelp directory as a collection of subdirectories, with each subdirectory devoted to a single issue. This allows multiple help files to be associated with each issue, and allows help files to be written in multiple languages.
The subdirectory name associated with each issue consists of the issue title with all non-alphanumeric characters removed. For example, the help files associated with the "Cisco Running Config Not Saved" issue would be stored in the CiscoRunningConfigNotSaved subdirectory, while the help associated with the "Bad Telnet / SSH Password" issue would be stored in the BadTelnetSSHPassword subdirectory.
All the help files stored in the subdirectory associated with a given issue are displayed as hyperlinks in the list. Each hyperlink label is derived from the name of the issue help file it references, and includes any spaces and special symbols.
Issue help file names must conform to the Unix file name convention, which does not allow certain characters, notably "/".
...
This enables help file authors to install different sets of help files for different languages when a system is deployed, while allowing users to choose their preferred language when accessing the system.
By default, the issue help file name is used as the hyperlink label displayed in the Issue Viewer. To display a different hyperlink label, one or more link translation files can be stored in the IssueHelp\LINKS directory. A link translation file maps an issue help file name to a hyperlink label.
Example. Suppose there are two help files associated with the "Cisco Running Config Not Saved" issue:
...
In these examples, the file names are pre-pended by an index number, which specifies the order in which the hyperlinks are displayed in the See Also list.
The link translation files define how the issue help file names should be displayed in the hyperlink labels based on the user's current language selection. NetMRI will automatically use the appropriate link translation file, if one is defined. If NetMRI doesn't find a link translation file, the issue help file name is shown as the hyperlink label.
...
- Click the by Device Groups or by Interface Groups side tab as appropriate.
- In the left panel, click the group name. Associated issues are listed in the Issue Settings for Group table.
- To edit an issue's settings for that group: Click Edit for the issue.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Suppression
| Anchor | ||||
|---|---|---|---|---|
|
...
Issue suppression enables users with Issues: Modify Suppression Parameters privileges to indicate which issues should be ignored by NetMRI for purposes of reporting and scorecard generation. Suppressed issues are still analyzed internally (because the associated analysis may be looking for multiple issues), but they are not displayed (by default) or used to compute scorecard values.
Issue suppression status is listed at Settings icon –>Issue Analysis section –>Suppression. The table in this page lists all issues defined in the system, and the analysis and penalties associated with that issue. The check box at the left end of each row indicates suppression status: if checked, the issue is suppressed.
To suppress an issue: Click the check box for that issue. Settings are committed automatically.
To see a full description of an issue and review suppressed instances: Click the hyperlink in the Issue Name column. To view analysis task details: Click the hyperlink in the Analysis Task Name column.
...
Note: It is possible to suppress all issues, which ensures a perfect score. Infoblox does not recommend this practice. Click the Component column header to sort Issue Names by their respective categories.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Suppression
| Anchor | ||||
|---|---|---|---|---|
|
...
...
Note: Group-based Issue Suppression settings recognize Device Group priority settings. NetMRI suppresses an Issue for any device if the Issue Suppression is enabled for the highest-ranking device group to which the device belongs. For example, consider a device that belongs to two device groups: Firewalls and Routing. Under Settings–> Issue Analysis–> By Device Groups, you will see that Firewalls is the highest-ranking device group. Should a particular Issue be suppressed in that device group, all devices participating in that group will have that Issue suppressed, regardless of the suppression settings in any lower-ranked device group to which the device(s) belong.
...
Suppressed issues continue to be analyzed internally (because the associated analysis may be looking for multiple issues) but they are not automatically displayed or used to compute scorecard values.
NetMRI supports two styles of issue suppression: full and partial.
...
NetMRI supports discovery and management of Cisco and Juniper device types that offer virtualization. Similar to servers that run VMware to run multiple instances of operating systems and data services in the same physical host, some Cisco and Juniper device types support multiple instances within the same device, each running the complete suite of protocols, configurations and operating system. NetMRI calls these instances virtual device contexts (VDCs). NetMRI detects devices that support virtual device contexts and provides the same management and cataloguing features that apply to conventional switches, routers and firewalls.
The Inventory page –> VirtualDevices menu item provides a list of all VDC–supporting devices that are discovered and catalogued by NetMRI. It displays the following values:
- IP Address: the IP for the virtual device;
- Device Name: The name detected for the virtual device;
- Collector (for OC systems only): the Collector appliance in the Operations Center that detected and manages the virtual device;
- Network View: the network view for which the detected virtual device is a member.
Each individual virtual device context appears in the Device Viewer, in the NetworkExplorer–>Inventory page, and in other locations of the NetMRI UI. NetMRI treats virtual device contexts identically to conventional routers, switches and firewall appliances, including the ability to send commands, schedule and execute jobs, display running configurations, view change histories and issues reported from the virtual device, apply compliance policies, run traces and SNMP walks, and many other operations.
NetMRI supports detection and management of the followfollowing
| Anchor | ||||
|---|---|---|---|---|
|
...
By default, the Virtual Devices list shows the IP Address for each virtual host, their provisioned Device Name and the Count of virtual device contexts for each Virtual Host managed by NetMRI. Click the IP address for any item in the Virtual devices list and the list of virtual device instances appears in the right pane.
The Virtual Host Details pane describes the basic information for the router, switch or firewall that is hosting the virtual device contexts, including its Network View, MAC Address ID, Model, assigned device name, OS version, the device type (Firewall, Switch, Router) and Context Name if any.
The Virtual Host Details pane also shows the context list, which are the actual virtual routers or other instance types that are being run by the hosting system. Each context is shown by its assigned IP address.
The pane also lists its assigned Device Name for each context (separately defined from the name of the hosting device) and the associated Context Name.
Click any IP address in the table and the Device Viewer popup window appears for that virtual device context.
You can also right-click on any virtual device instance to display the shortcut menu. Open the Device Viewer for any context, open the Config Explorer, view the current running configuration for the context, open its associated Issues List, execute a command, select a Telnet or SSH command-line session, and other operations.
Check the Virtual Asset Inventory report (under Reports –> Standard Reports) for more information on the virtual hosts and their respective VDCs.
Virtual Hosts can act as a proxy for access. If NetMRI is unable to connect to a Virtual Device directly, or the credentials are not known, NetMRI attempts to access the Virtual Device via the Virtual Host. CLI-based operations against a Virtual Device can be successful when connectivity is blocked to the Virtual Device, but not blocked to the Virtual Host. CLI operations include Job execution, Config Collection and in-browser CLI connections.
...
The network topologies for virtual hosts (i.e. the Cisco Nexus 7000 switch, Cisco ASA firewall, Juniper router, etc.) will often bear no connectivity relationship or topology resemblance to the network topologies for the virtual device contexts maintained by the virtual host.
Cisco's ASA firewalls use the term "Admin Context" to describe a top-level container that can run one or more virtual devices (VDCs). The ASA firewall's Admin Context is termed a virtual host in the NetMRI system, and it provides the management interfaces (SSH or Telnet) into the more-detailed virtual devices. (An ASA firewall can run more than one Admin Context/Virtual Host.)
The Cisco ASA uses the term "Customer Context" as a label for all virtual firewalls with their own discrete configurations and allocated interfaces. These entities are labeled as Virtual Device Contexts in the NetMRI system. These virtual "devices" support their own distinct topologies that can differ significantly from the hosting ASA firewall.
You can use the Topology Viewer (Network Explorer –> Topology) to look at the links between the Virtual Hosts and other devices in the network. Drilling further down, you use the Topology Viewer to examine the network linkages for the virtual device contexts themselves. Their topologies will often bear no relationship to the topologies of the virtual hosts upon which they are running. See Using the Topology Viewer for more information.
...
Clicking any link in the Interface column displays the Interface Viewer for the chosen device port, with features for viewing interface settings and performance metrics, and a Settings icon –> Port Control Settings feature for setting an interface to administratively Up or Down, changing a VLAN assignment or rewriting the port description.
Clicking any link in the Network View column opens the Network Viewer window.
...
The Device Viewer opens, listing any current Issues associated with the selected device.
The Device Viewer is not limited to this information. Seven categories of detailed information are provided by the Device Viewer for the displayed network entity. For more, see Inspecting Devices in the Network.
...
You can list all HSRP/VRRP Groups managed by NetMRI, or the HSRP/VRRP groups that are associated with a particular device group.
The HSRPs/VRRPGroups section lists Hot Standby Router Protocol (HSRP) groups and Virtual Router Redundancy Protocol (VRRP) groups found in the network, starting with the VirtualIP address of the group. Types are labeled in the Type column as HSRP or VRRP. The protocols are used for fault-tolerant
| Anchor | ||||
|---|---|---|---|---|
|
...
The Route Targets summary in the left panel shows the list of Import and Export route targets that are defined in VRF-aware devices in the managed networks. The VRF RD (route distinguisher) values are listed in a separate column, and you can click on the link for each VRF's network view, which opens the Network Viewer window. This window also lists all devices forming the VRF network.
Selecting a route target causes the center panel to display all the instances where it is being used, along with details of the device and the VRF. This is helpful to understand how VRFs and particularly VRF-Lite are configured across the network.
...
To view the complete list of network views, click the View all Network Views link at the top of the list. You can list all network views containing networks managed by NetMRI, or the network views that are associated with a particular device group. Each network view listed in the left panel provides a link to the Network View window.
The Count value indicates the number of interfaces sharing the same network view. Each instance is differentiated by the interface name.
If you have a significant number of network views, you can apply a filter by clicking the Filters button at the top of the table, choosing the Network View option from the Select a New Field selector, and entering the name of the network view.
Network Views represent each network that is managed and monitored by NetMRI. For more information about network views and how to use and configure them, see Configuring Network Views and its subsections.
...
After virtual routing and forwarding (VRF) networks are discovered and mapped to network views, you can use the VRFs summary to view the complete list of VRF instances throughout the managed network. You can sort the VRF information by any data column to see the relationships between VRF instances in virtual networks.
To view the complete list of VRF instances, click the ViewallVRFs link at the top of the list. By default, the VRFs are listed by VRF name.
Data columns include the following:
- VRF Name: displays the name of the VRF instance;
- VRF Description: Displays a description if the VRF instance is configured with a description on the device;
- Route Distinguisher: VRFs use route distinguishers to distinguish one set of routes (one VRF) from another. The route distinguisher is a unique number pre-pended to each route within a VRF to identify it as belonging to that particular VRF. The discovered route distinguisher value is listed here if a virtual network instance uses this value. (For related information, see Summarizing Route Targets.)
- Device Name: the discovered name of the device hosting the VRF instance;
- IP Address: The IP address of the managed VRF-hosting device. This value is a hotlink to the Device Viewer.
- Network View: The network view of the managed VRF-hosting device. This value is a hotlink to the Network Viewer window.
- VRF Network View: The network view to which the VRF is assigned. This value is a hotlink to the Network Viewer window. Note that this value may differ from the Network View identifier.
If you have a significant number of virtual routing and forwarding networks, you can apply a filter by clicking the Filters button at the top of the table, choosing the VRFName option from the SelectaNewField selector, and entering the name of the VRF. You can also filter by network view in the same way, or combine the two filters to isolate all VRF instances in a specific network view.
...
Note: Infoblox also provides a separate softsoftware
| Anchor | ||||
|---|---|---|---|---|
|
...
- The global Network View, where you can view different parts of the network based on the network type: the aggregate, which shows all active links of every type; Link Discovery Protocols, Serial Links and Switch Forwarding, which shows only Ethernet-switched connections throughout the network;
- The L2 nHop Network Topology, showing the Layer 2 switching paths of the network;
- The L3 nHop Network Topology, showing the Layer 3 switching/routing paths of the network;
- The L2/L3 Most Likely Path Network Topology, indicating the spanning tree paths preferred by switched network traffic in the network;
- The L3 Most Likely Path Network Topology, indicating the routed paths preferred by most packet flows in the network;
- The VLAN Network Topology, mapping the paths of VLANs throughout the network;
- Path Analysis (see Performing Path Analysis), enabling L3 path visualization across the enterprise or wide-area network.
...
Note: Most Likely Path and Path Analysis options require the selection of a source network view.
...
Search, CSV Export and Refresh Grid tools appear for all lists in the left pane of the Topology page. The Search feature allows contextual search from within any list for an IP address or a string of characters within the specific list of polled information. CSV Export enables exporting the current tabular list to a tab-delimited data file suitable for opening in Microsoft ExcelTM. You can also refresh any list by clicking the Refresh Grid tool. If changes occur after a refresh, the topology will redraw.
In all topology types (L2 nHop Network Topology, L3 nHop Network Topology, and so on) clicking on a device in the left-pane list displays a Hop Count selector. This selector changes its fields based on the protocol. (The figure to the left shows an L3 n Hop selector, in which you can choose a Hop Count from 1 to 4, and the protocol to view. The protocol you choose may or may not be active for the current device.
The Hop Count selector does not apply to the Path Analysis feature.
After you generate a graph, follow the topics below to change and enhance the graph.
Devices of different types appear differently in the View. Firewalls and virtual hosts such as Cisco ASA security devices and Nexus switches will show different icons.
...
| Anchor |
|---|
...
|
| Anchor |
|---|
...
|
...
The Refine View tool is handy for narrowing down the possibilities for path tracing, and for avoiding errors when attempting a possibly lengthy path analysis operation.
First, consider that Path Analysis is a L3 tracing feature. Before you perform any path analysis, click on Network Explorer –> Topology –> Network accordion menu –> Aggregate and click the Refine View button.
The Edit View dialog appears, displaying the Device Group tab.
Hover the mouse over the Action icon for the device group that you want to use as the basis for your path analysis. Choose Select Blue or Select Yellow from the Actions pop-up menu. The color for the Group appears under the Selections column. Click OK, and the Topology map redraws to add color markers to all devices in the map corresponding to the chosen device group. Apply colors to different device groups to help in a broader search across a large network.
Other tabs that you can use to outline parts of the network topology include the following:
VLAN – Select a VLAN form this tab, associate a color with it, and you can outline the path of a L3 switched VLAN in the network;
Network View – Select a network view from this tab, associate a color with it, and all devices participating in the network view will be labeled;
Issues – Enable the Show All Issues check box to show all devices in the network that are currently sustaining issues. Hover the mouse over the device icon to see an Issues Seen summary;
Change – Enable a checkbox, Show All Changes, to change the topology map to show an icon next to all devices that have sustained recent configuration changes. Hover the mouse over the Change icon to see a Changes Seen summary;
Policy – Enable a checkbox, Show All Policy Violations, to change the topology map to show an icon next to all devices that are currently sustaining policy violations. Hover the mouse over the Policy icon (icons are a green Pass checkmark icon or a Fail "X" icon) to view a summary of the device and its policy information;
By checking for Issues and general network connectivity characteristics, you can more easily choose the source and destination devices for a Path Analysis that have a correct L3 configuration to provide a likelihood of a successful path analysis operation.
...
|
The L2 nHop, L3 nHop, L2/L3 Most Likely Path, and L3 Most Likely Path topology menus all support the Network View data point, listing the network views in which each listed device participates. Clicking the link in this column for any device opens the Network Viewer window.
...
Right-clicking on any device icon on the Topology pane provides a selection of device exploration features. Its contents change based on the selected device.
- Device Viewer – Opens the Device Viewer for the chosen device.
- Config Explorer – Opens the Device Viewer's Config Explorer page for the chosen device. You can browse the list of configs in the device and edit existing config files.
- View Running Config – Displays the currently running configuration for the chosen device in a Configuration Viewer window.
- Changes – Opens the Device Viewer's Network Analysis –> Changes page for the chosen device.
- Issue List – Opens the Device Viewer's Network Analysis –> Issues page for the chosen device. This page lists all Error, Warning and Info issues for the chosen device.
- Policy Compliance – Opens the Device Viewer's Network Analysis –> Policy Compliance page for the chosen device. The current device's status in DISA-standard security and stability levels is outlined here, with links to configuration policy analysis functions from this page;
- L2 nHop – Displays the L2 nHop Network Topology in a separate window, showing the Layer 2 switching paths directly associated with the current device.
- L3 nHop – Displays the L3 nHop Network Topology map in a separate window, showing the Layer 3 routed switching paths directly associated with the current device.
- L2/L3 Path Viewer – Displays the L2/L3 Most Likely Path Network Topology map in a separate window, indicating the VLAN spanning tree paths directly associated with the current device.
- L3 Path Viewer – Displays the L3 Most Likely Path Network Topology map in a separate window, indicating the L3 routed paths directly associated with the current device.
- Schedule Job – Schedule a job script (CCS or Perl) to run on the chosen device, from the Script Run Now wizard. See Creating and Scheduling Jobs for more information about job scripting.
- Execute Command – Opens the Script Run Now wizard, with the Commands to be Executed section active. Type in any configuration command.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
- To restrict devices shown in the graph: Select a device group in the Select Device Groups panel. (This feature is not available for VLAN graphs.)
- To show all devices in the graph: Select All Devices in the Select Device Groups panel.To modify the graph in other ways: Click the Refine View button. The Edit View dialog appears, where you can:Show end hosts (by enabling the Show End Hosts option).
- Color-code members of a device group or VLAN (in the appropriate tab, select a color).
- Highlight devices having issues, changes and/or policy violations (in the appropriate tab, enable the option).
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
- To print the graph: Menu –> Print.
- To export the graph as an image: Menu –> Export as Image. Printing or exporting the graph reproduces the entire graph, not just the portion currently shown.
- To launch a larger view of the current graph in a separate window: Menu –> Detach View.
- To show a legend at the bottom of the screen: Menu –> Legend.
Note: Only items you have chosen in the Refine View will appear on the legend. If you have no options chosen you will not be able to turn on the legend.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Topology
| Anchor | ||||
|---|---|---|---|---|
|
...
L2 n Hop (Network Explorer –> Topology –> L2 n Hop) shows devices that can be reached from a selected starting device through a chosen number of Level 2 (actually a hybrid of L1 and L2) connections.
...
Note: L3 connections are directional; a hop to a neighboring router and back is considered two hops. If you set Hop Count to 1, you won't see any return hops to the starting device.
...
.
Juniper M5 and
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Topology
| Anchor | ||||
|---|---|---|---|---|
|
...
L2/L3 Most Likely Path shows the most likely path traffic would take between two devices, including both Layer 2 and Layer 3 connectivity.
- In the left panel, click L2/L3 Most Likely Path.
- In the left panel, click the row containing the starting device.
- In the L2/L3 Most Likely Path dialog, select the source network view from the Network View dropdown menu.
- In the L2/L3 Most Likely Path dialog, select the ending device. Shorten the device list by selecting a Device Group or by entering a search term.
In the resulting graph, the name of the starting device is highlighted in green, and the name of the ending device is highlighted in red.
...
, the name of the starting device is highlighted in green, and the name of the ending device is highlighted in red.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Topology
| Anchor | ||||
|---|---|---|---|---|
|
...
L3 Most Likely Path shows the most likely path that routable Layer 3 traffic would take between a source device and a destination device, ignoring Layer 2 connectivity between Layer 3 devices. By default, the
...
In the resulting graph, the name of the starting device is highlighted in green, and the name of the ending device is highlighted in red.
- To change the chart view: Click Refine View above the graph. Then, click Edit Address near the top of the dialog. The Address Table appears, listing all interfaces for the chosen destination device. From here, you choose a different IP address on the destination device as the destination for determining a path. By default the destination value is the Management IP address for the chosen device.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
VLAN
| Anchor | ||||
|---|---|---|---|---|
|
...
Note: Only VLANs with a spanning tree root that is managed by NetMRI can be viewed in the appliance.
...
Note: VLANs can have identical names as long as the root bridge is different.
...
.
...
VLAN graphs cannot be filtered by device group names in the Select Device Groups panel.
...
In the Network Explorer pages, you can also use a drag-and-drop interface to define the source and destination values for a Path Analysis.
You can also perform path analysis for multiple paths from the same source location, and you can define the maximum number of calculated paths from a device.
Path Analysis also enables a powerful feature called Start From Device, in which the only value needed for a path trace is the destination IP address or device's FQDN. Then, choose any device in the network to start the path trace.
...
NetMRI does not collect administrative distance from managed devices; when necessary, path calculations rely on the Routing Distance values defined in the NetMRI appliance (see Defining Path Analysis Settings for more information).
You may choose to have NetMRI calculate a path by specifying only a destination device.
...
The Start from Device feature for Path Analysis enables the resumption of a trace from any selected point elsewhere in the network. For example, a device might appear in the network that isn't fully discovered by NetMRI; once it is, and assuming it is covered by licensing, you can resume the path analysis from that device and continue on to finish the trace. You may have to wait for a brief period before the device is fully discovered and licensed, and the device has its routing tables added to the NetMRI database.
If the network provides for two Zones separated by a VPN, you can trace up to the endpoint of the first part of the path, note the device name where the VPN tunnel terminates, and use that device to resume the trace to the same Destination device. Do the following:
...
NetMRI gives explicitly licensed devices priority in determining which devices to manage. Unlicensed devices continue to be managed by the appliance, but only basic discovery data is periodically collected from them.
To force immediate discovery of devices: Click the check box for the device(s), then click Discover Now (above the table). NetMRI will execute the processes required against a device to complete discovery. These include SNMP credential collection, SNMP data collection, device group assignment and CLI credential collection.
To delete devices from NetMRI's database, do the following:
...
The Interface Viewer (accessed by clicking any hyperlinked interface identifier in the Interface column of the Interface Configuration list (located in Network Explorer –> Inventory –> Interfaces –> Interface Config), displays low-level interface data and network phenomena affecting the selected interface during a specified time period. The top panel lists basic information about the chosen interface, including the Type, Speed, Status (Up or Down, along with the date the interface was discovered to be changed in state), the host device's Network View, the Device IP, its interface MAC Address; the Interface IP (if any); and Ethernet Port Fast and Encapsulation settings where applicable (this value appears only when the interface is using 802.1Q tagging).
If a physical interface also contains logical subinterfaces that are locally assigned to VRFs, the Encapsulation field will appear in the top panel of the Interface Viewer window, also listing the protocol.
When an interface is locally assigned to a Network View, the Local VRF field appears in the top panel of the Interface Viewer window.
By default, the Interface Viewer displays any neighboring interface information for the selected interface. The assumption is that the selected interface is actually administratively On and active on the network; otherwise the Interface Viewer shows a blank page.
...
The Neighbors page (Interface Viewer –> Interface –> Neighbors) lists the MAC addresses, associated VRF Name and Neighbor VRF Name (if any), the Network View, IP addresses, interfaces and other data for neighbors of the currently displayed interface. If you select an interface that is administratively On and is active in the network, the Interface Neighbor information automatically appears. Otherwise the neighbor information remains blank.
Associated information provided includes the VLAN and/or trunk interface, the neighbor's MAC address, the neighbor type, and the Neighbor Assurance value.
...
Under Performance in the Interface Viewer, the Summary page (Interface Viewer –> Performance –> Summary) lists high-level statistics for inbound and outbound traffic for the selected interface. A table appears in the Interface Viewer, showing Counts, Rates and Percentages for Inbound and Outbound Octets, Packets, Unicast packets, Non-Unicast packets, Multicast packets, Broadcast packets, Discards, Errors, Changes, Alignment Errors, FCS Errors, and Late Collisions. These statistics cover the entire selected interface, cumulative for all subinterfaces if any.
The Rates page (Interface Viewer –> Performance –> Rates) shows inbound and outbound throughput and related rates for the interface, including Packet Rate, Broadcast Rate, Discard Rate and Error Rate;
The Percents page (Interface Viewer –> Performance –> Percents) shows inbound and outbound traffic statistics expressed as a percentage of total throughput, including % Utilization, Broadcast Percent, Discard Percent and Error Percent;
The Counts page (Interface Viewer –> Performance –> Counts) displays inbound and outbound traffic statistics expressed as counts, including columns of statistics for Octet Count, Packet Count, Broadcast Count, Discard Count and Error Count;
The Charts page (Interface Viewer –> Performance –> Charts) provides charts that show throughput, broadcasts/second, errors/second and discards/second. Use the Measure list at the tope of the page to select Rate or Percent for the charts' vertical axes.
...
The General Settings page (Interface Viewer –> Settings –> General Settings) enables you to apply or override the parent group's performance data collection setting, under the Performance Statistics Collection setting (group settings are defined in the Settings icon –> Setup section –> Collection and Groups page –> Groups tab –> Interface Groups side tab).
To ensure collection of all performance data for the specific device, choose the Enabled option.
Choose the Use Default option if you want performance information collection to only use the parent Interface Group's settings.
Interface performance data covers a broad selection of network phenomena, including but not limited to the following: port throughput, bandwidth utilization, packet errors percentage, broadcast packet percentage, and packet discard percentage.
A second option, SwSwitch
itch Port Management Control, enables or disables the current interface from management by Switch Port Manager.Anchor bookmark370 bookmark370
...
In all cases, click Save to commit settings.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
List
| Anchor | ||||
|---|---|---|---|---|
|
...
Ports listed in the Port List page (Settings icon –> Setup –> Port List) are probed when Port Scanning is enabled at Settings icon –> Setup section –> Collection and Groups –> Global tab –> Network Polling panel.
To add a port to the list, do the following:
...
To delete a port from the list: Click the Delete button for the port.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Status
| Anchor | ||||
|---|---|---|---|---|
|
...
The Collector Status page (Settings icon –> Setup –> Collector Status) shows the internal processing being performed by NetMRI. This page is used primarily for technical support purposes.
A property group is a collection of SNMP variables that NetMRI polls from a given device type and vendor at a given frequency. The collection of SNMP variables in a property group are not visible to the user.
...
To access the Interface Live Viewer, do the following:
1. Right-click any interface hyperlink, then click Interface Live Viewer in the pop-up menu.
...
If too many lines make it difficult to interpret the graph, hide lines having less value by clicking the colored check- box for any data type at the bottom of the chart window.
To hide or show data callouts within the graph, do the following: In the graph, click the line for which you want to hide/show data.
...