...
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.
...
- In the Detail Columns field of the Add Command Script Issue dialog (see above), enter IP Address, string.
- In the Issue-Details section of the CCS script, add "IP Address" $ipaddress (including the quotation marks). The resulting CCS issue contains the IP address with a hyperlink to the Device Viewer.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
files
| Anchor | ||||
|---|---|---|---|---|
|
...
Custom issue help files provide NetMRI users with organization-specific information for individual issues. All issue help files associated with an issue are accessed via hyperlinks in the See Also section of the Issues Viewer. Multiple help files can be associated with an issue.
Help files can be stored in any format (e.g., .pdf, .doc, .txt, .jpg, etc.) that can be rendered by the web browser. Also, help files can be written in any language supported by NetMRI, enabling the user to view them in the language defined for the console.
...
- The Inventory tab provides basic information about all active devices, interfaces, operating systems and models in the network, including virtual devices, which are instances of virtual routers, virtual switches and other types that are supported by selected devices from some networked system vendors;
- The Summaries tab lists routes, subnets, VLANs, HSRPs/VRRPs, route targets, network views, VRFs and ports in the network;
- The Topology tab provides an interactive viewer in which you can visually explore your network’s topology and interconnectivity;
- The Discovery tab provides detailed information about NetMRI’s discovery processes, including the ability to affect Discovery settings for individual devices, perform/repeat Discovery on a single device, set licensing for a managed device and remove a device from NetMRI management. (For more information on device-related Discovery functions, see the section Viewing Device Discovery Status and Re-Discovering a Device);
- Switch Port Management is a key feature set for compiling, monitoring and controlling the devices, ports and end hosts throughout an enterprise’s switched Ethernet network. Consult the topics under Switch Port Management for many more details.
...
Note: If you know exactly what you are seeking, try typing a few characters in the FindIT search box (upper right corner of the main NetMRI page).
...
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, sees under Inspecting Devices in the Network.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
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 following
| Anchor | ||||
|---|---|---|---|---|
|
...
- To list devices comprising the route: Click a route in the left panel. The center panel refreshes to show the device reporting the route, the route's interface from which it was reported, the Network View for the management IP of the device reporting the route, and the route's Next Hop. The list also shows each device's Route Distinguisher. This feature can be helpful in tracing a path, and can be helpful with Path Analysis.
- To view detailed data for a device: Click the IP address hyperlink in the center panel. The Device Viewer opens.
...
- 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;
...
Note: The Most Likely Path and Path Analysis options require option requires the selection of a source network view.
...
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.
...
L3 n Hop shows all active devices that can be reached from a selected starting device in the network through a chosen number of routed Level 3 connections. In the resulting graph, the name of the starting device is highlighted in green. Devices that cannot be reached, or that are farther away than the Hop Count are not shown in the resulting view. The information conveyed here can be considered a superset of the Path Analysis feature, which shows the preferred L3 routed path from the selected stating device to a defined destination device.
- In the left panel, click L3 n Hop.
- In the left panel, click the row containing the starting device.
- In the L3 n Hop dialog, select a Hop Count and a Protocol.
- Click OK.
...
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.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
| Anchor | ||||
|---|---|---|---|---|
|
...
VLAN Network Topology
...
Note: Only VLANs with a spanning tree root that is managed by NetMRI can be viewed in the appliance.
...
VLAN graphs cannot be filtered by device group names in the Select Device Groups panel.
...
Path analysis (Network Explorer –> Topology –> Path Analysis) allows tracing a L3 path across a network of any scale, subject only to the restriction that NetMRI must discover and manage both the source and destination devices. The devices forming the endpoints of the path can be any of the following:
- Routers;
- VRF instances inside routers;
- Switch-Routers, including VLANs.
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.
Note: Path Analysis does not support L3 path traces across protocols that are not directly supported by NetMRI, including MPLS, MPLS-TE and GLBP. In cases where only a partial path can be traced because it terminates in a hop that is an endpoint for one of these protocols, you can use the Start From Device feature to resume the trace from the hop where the MPLS or GLBP tunnel terminates.
NetMRI calculates paths based on collected routing table information, and are determined in the following order:
- Directly connected;
- Longest subnet prefix;
- Administrative distance.
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.
To perform a basic Path Analysis, do the following:
- Open Network Explorer –> Topology.
- Choose a Device Group from the Select Device Groups menu in the right pane.
- In the left panel accordion menu, click Path Analysis.
A blank Topology Viewer panel appears in the center panel, with Source, Source Network View and Destination fields on the top. - Enter the Source and Destination values for the two devices whose common path(s) you want to trace. (You can press the Tab key to move between the Source, Destination and the Start button.) As you enter the IP values, NetMRI evaluates the entry to ensure the value is part of the chosen device group. If the value is correct, the device value displays in grey. If either value is incorrect for any reason, you will see an Invalid Source or Invalid Destination tooltip and the field will be outlined in red.
- Choose the network view for the network you are tracing from the Source Network View dropdown list. If the path is known to be within the globally routed network, select the Network1 network view. If there is only one network view being managed by NetMRI, this field will not appear.
If you choose an incorrect network view, you will receive a Path start device could not be determined error. - Choose Start from the drop-down menu.
After a moment, the topology map appears for the chosen values. - The system saves the Path Analysis instance you just created under the Path Analysis menu.
- After the path analysis completes, if a path does not complete because of intermediate devices that are endpoints for an MPLS encapsulated tunnel (or from other similar protocols), select the device in the path from which the VPN terminates, and continue the path analysis form there using the Continue Path Analysis From Device option. This option is similar to the Start from Device drop-down menu option in the center pane.
...
In a large network, more than one possible path my exist between two devices. You can control the number of path calculations performed for the same Source/Destination pair. The default number of simultaneous path calculations is 2, with a maximum value of 10. Go to Settings icon –> General Settings –> Path Analysis and edit the Number of Calculated Paths setting. Avoid setting this value to too high a number, as multiple active path calculations can affect performance.
...
When performing path analysis, the path may be incomplete due to the following reasons:
- One or more devices on the path is incompletely discovered;
- A segment of the network path is comprised of an encrypted tunnel.
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:
...
.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
If a device continues to appear in collected data, NetMRI will re-list the device unless you choose to exclude the device from discovery when it is deleted.
To un-manage devices, do the following:
...
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.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| 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:
...