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 in the CIDRs count that should not exceed 1000 per the recommendation in the Infoblox Discovery Best Practices Guide.
Note
title
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.
...
APIC Controller (managed device): Collects basic information on ACI fabric devices such as device model, vendor name, OS information, IP address, and the user system name.
ACI specific endpoint information such as EPG, Bridge Domain, and Tenant.
General Endpoint (devices) information such as name, IP address, VRFs, and physical connection (fabric port).
Fabric Name: Specify a short and unique name for the current Cisco ACI configuration.
Addresses: Click Add and enter the hostname or IP address of the Cisco APIC controller. If your fabric includes more than one controller, click Add again to add more addresses.
Network View: Select the network view to identify the corresponding network interface for connectivity with the Cisco ACI. Also, this network view will be . In parentheses next to the network view name is displayed the name of the associated collector. The network view and collector are assigned to discover devices from this the ACI fabric.
Protocol: SelectHTTPorHTTPS. If you select HTTPS, you must use a Root CA or Intermediate CA certificate to allow communication with the Cisco APIC as described below. If your ACI fabric includes multiple controllers, use a combined PEM certificate. To do so, copy the ASCII data from all of the certificates into a single file.
CA Certificate: Perform one of the following:
Select a previously imported CA certificate. To learn how to import a CA certificate in NetMRI, see Installing CA Certificate.
ClickImport CA Certificateand select a CA certificate directly from your machine. For how to prepare a CA certificate, see About CA Certificates for Cisco APIC. The APIC controller address must match either the certificate subject or one of subject alternative names.
Username: The login name for the Cisco ACI.
Password: The login password.
to or from
ClickTest Connection to check if the fabric is reachable and the provided credentials are correct. The connection test results are also written to the syslog.
Config Name: Specify a short and unique name for the current Cisco Meraki configuration.
Network Interface: Select the interface that will be used to access the device. In parentheses next to the interface name is displayed the name of the associated collector. As Cisco Meraki infrastructure may have overlapping IP addresses in different network views, you should explicitly specify a network interface exposed to the internet.
Protocol: HTTPS by default.
Address: Enter the hostname or IPaddress of the Cisco Meraki Dashboard API.By default it isapi.meraki.com.
ClickTest Connection to check if the device is reachable and the provided credentials are correct. The connection test results are also written to the syslog.
Default SDN Network View: The network view that will beassignedto discovered Cisco Meraki devices for which the automatic network view mapping is disabled. You enable or disable automatic mapping in the Advanced panel. For more information, see the step three below.
In Network View Mapping, select one of the following:
Disable automatic mapping and use predefined SDN Network View: Select to map collected SDN/SD-WAN devices to the default SDN network view defined in the previous steptwo above.
Automatically create network views for unmapped networks: Select to automatically map collected networks to their network views using NetMRI internal rules. Network views that do not exist are created automatically. The mapped networks are displayed in the table that is not editable.
Enable network view mapping defined below: This is custom mapping. Select this to manually map collected networks to the appropriate network views. To change a network view entry, double-click it in the table.
If necessary, override the global data collection interval that will be applied to the SDN/SD-WAN host polling:
Go to the Settings icon –> Setup –> Collection and Groups –> Switch Port Management.
Specify one of the following:
Periodic Collection: Specify the N minutes or hours when the collection should occur.
Scheduled Collection: Schedule recurrent collection based on hourly, daily, weekly, or monthly time periods. Click one of the tabs, Once, Hourly, Daily, Weekly, or Monthly to choose a recurrence pattern.
ClickSave.
...
Choose the Settings icon –> Setup –> Proxy Settings.
In the Proxy For drop down list, select the required collector.
Select Use Proxy Server.
Complete the following:
Name or IP Address: An FQDN or IP address of the Proxy.
Port: The port number of the Proxy.
Username: The username that NetMRI will use to log in to the Proxy.
Password: The password that NetMRI will use to log in to the Proxy.