Anchor | ||||
---|---|---|---|---|
|
...
Table Sample... |
| |
Copy – copies a selected record. | ||
Edit – Click here to edit a record in a table. | ||
Schedule – Where applicable, schedules the item in the table for execution. | ||
Run Now/Actions – Where applicable, Run Now immediately executes the directives in the current table record. The Actions icon contexts provide features to execute against individual records in data tables throughout the entire NetMRI system. | ||
Test Policy – Where applicable, tests the currently selected Policy. | ||
CSV Export – Where applicable, exports the contents of the current record to a tab-delimited file suitable for viewing in Excel. | ||
Delete – Deletes a selected record from a NetMRI table. | ||
Add – adds a new record to a table of NetMRI items. | ||
Tools – Opens a set of networking utilities for network admins to perform troubleshooting and device communication tasks, such as Ping, Traceroute, SNMP Walks and other operations. | ||
Background Task indicator bar – Indicates NetMRI is performing a background task. Appears on the NetMRI toolbar and disappears when the task completes. | ||
Settings – An important icon providing a hierarchical list of configuration settings such as User Admin, Issue Analysis configuration, general Setup, Notifications setup, Database setup and other fundamental areas that define how NetMRI operates. | ||
General online Help feature, providing the entire online Help information window without specificity to the currently displayed feature page in NetMRI. | ||
Context - sensitive online Help, from which the currently displayed UI page can show Help for that feature in a separate popup window. | ||
Refresh Grid – allows refreshing of a complete table list or 'grid' of information. NetMRI collects the same body of related information for the table, including any possible changes that may have occurred since the table was last compiled. | ||
Refine View – a tool to change and filter the data reflected in graphical Topology views | Arrows used to move the view horizontally and vertically in the Topology Viewer under Network Explorer. | |
Zoom In and Zoom Out – Tools to magnify or shrink the view in graphical the Topology views Viewer under Network Explorer. | ||
Fit Content – a A tool to resize a large map or a small view of a map to fit the entire graphic pane in graphical Topology views under Network Explorerin the Topology Viewer under Network Explorer. | ||
Allows adding or deleting nodes and edges in the Topology Viewer under Network Explorer. | ||
Allows adding a new node in the Topology Viewer under Network Explorer. | ||
Allows adding an edge in the Topology Viewer under Network Explorer. | ||
Deletes a selected node or edge in the Topology Viewer under Network Explorer. | ||
Reload–reloads the graph in the Topology Viewer under Network Explorer after some changes are made. |
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
The secondary system synchronizes data with the primary system. This process might take about one hour, depending on the appliance model.
Anchor | ||
---|---|---|
|
...
|
...
|
Anchor | ||||
---|---|---|---|---|
|
You can migrate two existing Operation Center (OC) or standalone appliances to form a failover pair. Ensure that both appliances are running versions NetMRI 7.1.1 or later. To form a collector failover, migrate the existing collector to NetMRI 7.1.2 or later releases.
Following are the pre-requisites for migrating existing systems as a failover pair:
...
You define Seed Routers for NetMRI to speed up network discovery. Definition of seed routers is highly recommended for IPv4 networks and is required for IPv6 networks. Seed routers are also given priority (like static IP definitions) for determining which devices are counted toward NetMRI's license limits.
For discovery of any IPv6 network, at least one well-connected IPv6 router (preferably with routes to all other networks to be managed by NetMRI) must be placed in the Seed Router list. In some cases, seed routers may not have the full routing tables or be unable to provide full information for some reason. The general rule of thumb is that more seed routers are better, but the connectivity of the seed router(s) also helps determine how many seed routers you need. Avoid having more seed entries than necessary. Also note that seed routers are included into the CIDRs count that should not exceed 1000 per recommendation in the Infoblox Discovery Best Practices Guide.
...
Note: For effective use of seed routers, you must also provide admin credentials to NetMRI to allow it to pull the key routing and connectivity information, including the IPv6 routing table and the local Neighbor Discovery Cache, from the device. NetMRI uses the standard IPv6 counterparts to standard communications protocols, including SSH and SNMP.
...
Note: For more information about Device Viewer functions, see Inspecting Devices in the Network and its subsections.
...
· Working familiarity with Python, Django and Mako