To ensure a successful discovery, complete the following configurations for the Grid and Grid members that are acting as the Consolidator and Probes before you start a discovery:
Define polling methods and schedule.
Define advanced polling settings for TCP scanning and Ping sweeps. Also, specify routers and logging options.
To collect data from SDN and SD-WAN devices, add and configure them as described in Configuring Discovery for SDN and SD-WAN below.
If you use SNMP or CLI collection as the polling methods, define device credentials for data collection. .
Assign credentials to device groups.
Enable and schedule blackout periods for discovery and port configuration. For more information, see Defining Blackout Periods.
Configure automatic network view mapping for unassigned VRFs that have been discovered. For more information, see Configuring Automatic VRF Mapping.
Configure settings to monitor the lifecycle and vulnerabilities of discovered devices. For more information, see Configuring Advisor Properties below.
The following sections describe in detail how to configure discovery for the Grid, Grid members, and networks.
...
For the Grid: From the Grid tab, select Grid Manager > Discovery service, and then select Edit > Grid Discovery Properties from the Toolbar.
For Probe members: From the Grid tab, select Grid Manager > Discovery service, select a member, and then select Edit > Member Discovery Properties from the Toolbar.
For networks: From the IPAM tab, click a network name, and then click the Edit icon.In the Grid Discovery Properties or Member Discovery Properties editor, click Polling > Basic.
In the Network editor, click Discovery.If you want to override the inherited Grid settings for Probe members and networks, click Override and define the following settings.
SNMP Collection: Select this to execute SNMP protocols to discover and collect information such as traceroute/path collection, vendor and model, SNMP credential collection, routing and ARP tables, switch port data, and VLAN configuration data. If you disable SNMP collection, previously discovered data remains available for viewing. No new data is added and no existing data is removed.
Some devices may not support SNMP, and some devices may not enable SNMP by default.
Note When you disable SNMP collection on a network with enabled discovery, Network Insight still attempts to authenticate the SNMP credentials of devices that are newly discovered under this network. All newly discovered devices are automatically bound to a default group with enabled SNMP collection.CLI Collection: Select this if you expect to use Network Insight to discover devices that support CLI connectivity through Telnet or SSH, and that you possess admin account information. NIOS can use device admin account logins to query network devices for discovery data collection, including IP configuration, port configuration, routing and forwarding tables, and much more.
Note that for SNMP and CLI Collection methods, configure device polling credentials in the Credentials tab of the editor. For more information, see Configuring Device Credentials below.
Port Scanning: Select this to probe the TCP ports. Ensure that you go to the Advanced tab to configure more settings for this option as described in the next section. If you disable Port Scanning, NIOS attempts no port probes other than SNMP on any device.
Profile Device: If enabled, NIOS attempts to identify the network device based on the response characteristics of its TCP stack, and uses this information to determine the device type. In the absence of SNMP access, the Profile Device function is usually the only way to identify non-network devices. If disabled, devices accessible via SNMP are identified correctly. All other devices are assigned a device type of Unknown. Profile Device is disabled by default for network polling.
Smart IPv4 Subnet Ping Sweep: Select this to execute Ping sweeps only on subnetworks that are known to exist but no IPs can be found within the subnet, such as through ARP or other means.
Complete Ping Sweep: Select this to enable brute-force subnet Ping sweeps on IPv4 networks. This method executes Nmap that uses ICMP echo requests, ICMP timestamp requests, and TCP SYN to ports 161, 162, 22, and 23 (for the SNMP, SNMPTRAP, SSH, and TELNET services correspondingly). Subnet ping sweeps are used as a last resort in the discovery process. Perform a subnet ping sweep if NIOS cannot identify any network devices in a given subnet. Subnet ping sweeps should be performed no more than once per day, and will stop on a given subnet once NIOS Discovery locates a network device and is able to collect data from it. Ensure that you configure advanced settings for this option in the Advanced tab as described in the next section.
Note that NIOS does not perform Smart Subnet Ping sweeps on subnets larger than /22. NIOS also does not perform Ping sweeps on IPv6 networks, because of the dramatically greater scale of network addresses in the IPv6 realm. The Complete Ping Sweep differs from the Smart Subnet Ping Sweep in the following ways:The Complete Ping Sweep will run only against the specified range.
The sweep will run regardless of the range size.
The sweep will run regardless of the number of discovered devices within the specified range.
NetBIOS Scanning: Select this to enable NIOS to collect the NetBIOS name for endpoint devices in the network. This feature can be enabled only by users with SysAdmin privileges. This feature is globally disabled by default (and also for device groups) to prevent unexpected scanning of the network by a new collector.
Automatic ARP Refresh Before Switch Port Polling: Select this to enable refreshing of ARP caches on switches and switch-routers in the managed network before NIOS performs polling of switch ports. Enabling this feature applies only to switched Ethernet devices. This feature enables more accurate detection of all endpoint devices on L2 switches. Without ARP refresh, some endpoint devices may not be detected. This feature is globally disabled by default. Individual ARPs can also be set to enable or disable this feature.
Switch Port Data Collection: Select this to enable the Probe member to poll L2 enterprise switches. You can completely disable switch port polling by deselecting this checkbox. You can also separately schedule polling for switch port data collection as follows:
Periodic Polling: Define regular polling time periods. Choose a polling interval of 30 or more minutes or 1-24 hours.
Scheduled Polling: Schedule recurrent polling based on hourly, daily, weekly, or monthly time periods. Choosing this option, click the Calendar icon and a Polling Scheduler appears; click the Edit icon to make scheduling changes. Choose a recurrence pattern of Once, Hourly, Daily, Weekly, or Monthly. In all cases, you must choose an Execution Time.
In the Polling Frequency Modifier field, specify the coefficient that modifies the polling frequency modifier.
For example, by default it happens once a day. With the Polling Frequency Modifier option introduced in NIOS 9.0.4, you can set the polling frequency modifier to occur once every two days or twice a day.
You can set values between 0.5 and 2 for the global level polling frequency modifier. Interpret the values as follows:0.5: Makes polling twice as slow.
1: Takes the default setting, which is once a day.
2: Makes polling twice as fast.
To set the Polling Frequency Modifier value for global settings, ensure that you enable the Use Global Polling Frequency Modifier checkbox for network configuration.
Save the configuration.
...
For the Grid: From the Grid tab -> Grid Manager tab -> Discovery service, select Edit -> Grid Discovery Properties from the Toolbar.
For members: From the Grid tab -> Grid Manager tab -> Discovery service, select Edit -> Member Discovery Properties from the Toolbar.
For networks: From the IPAM tab, select the network checkbox and click the Edit icon.In the Grid Discovery Properties, Member Discovery Properties, or (IPv4 or IPv6) Network editor, click Polling -> Advanced and define the following settings.
If you want to override the inherited Grid settings for Probe members and networks, click Override and define the following settings.
TCP Scan Technique: Select the TCP technique you want to use for the discovery. The default is SYN. For more information, see TCP.
SYN: Select this to quickly perform scans on thousands of TCP ports per system, never completing connections across any well-known port. SYN packets are sent and the poller waits for a response while continuing to scan other ports. A SYN/ACK response indicates the protocol port is listening while an RST indicates it is not listening. The SYN option presents less impact on the network.
CONNECT: Select this to scan IPv6 networks. Unlike the SYN option, complete connections are attempted on the scanned system and each successive TCP protocol port being scanned.
Specify the TCP ports settings:
In the table, select the checkboxes of the TCP ports you want to discover. To select all ports, click the checkbox in the header.
To add a new port, click the Add icon.
Specify other advanced polling settings:
Purge expired assets data after: Removes records of discovered assets that are no longer reachable after a specified period of time. The default is set to one day.
Purge expired device data after: Removes records of discovered network infrastructure devices that are no longer reachable after a specified period of time. The default is set to seven days, a more forgiving value given that devices sometimes require maintenance, upgrades or repairs, or in cases where hosts leave the network on long trips.
ARP Aggregate Limit: Sets a limit for the number of entries (IP addresses) per MAC address in ARP tables. If there are too many entries associated with a MAC address, this can be treated, for example, as a "honeypot". Therefore, MAC addresses with more entries than the specified limit are ignored and filtered out during data extraction and parsing. The default limit is 30 ARP table entries (IP addresses) per MAC address.
Route Limit: Limits the size of the routing table that discovery is required to collect from any given device. Some routers can have tables in the hundreds of thousands of entries, and collecting such a large body of data can impose performance problems in the network and in discovery data collection. This setting defaults to 3000, and automatically excludes BGP routes from the collection. Consult Infoblox Technical Support before making changes to this value.
Ping Sweep Timeout (ms): Period of time allowed, in milliseconds, before a Ping times out to any given device.
Ping Sweep Attempts: The number of attempts on each address in a Ping sweep before the sweep continues.
Ping Sweep Frequency: Defaults to 1, because ping sweep should not be executed more than once a day when the feature is enabled at the grid level or for a given discovery range. This setting affects the SmartPingSweep and CompletePingSweep features under GridDiscoveryProperties.
ARP Cache Refresh: Defines the time period between ARP refreshes by Network Insight across all switch ports. Before any other switch port polling and discovery operations take place (including any global discovery polling operations initiated by the administrator), another ARP refresh is carried out by the Probe appliance regardless of the time interval. The default is five minutes, because switch forwarding tables are frequently purged from LAN switching devices. The default on Cisco switches is five minutes/300 seconds. Network Insight primarily uses ARP Cache refreshes to improve the accuracy of end-device discovery. Without this feature, some endpoints may not be discovered and cataloged.
Ignore Conflict Duration: Used when resolving conflicts and when choosing the option to Ignore the conflict when resolving it. The length of time during which conflicts is ignored is defined with this settings. Increments can be defined in Hours or Days.
Number of discovered unmanaged IP addresses per notification: The maximum number of unmanaged IP addresses that the appliance discovers before it sends SNMP and email notifications, if enabled. The appliance resets the counter after it hits this number and sends notifications. The default is 20.
Interval between notifications for discovered unmanaged IP addresses: This number determines how often the appliance sends SNMP and email notifications, if enabled, when it discovers the maximum number of unmanaged IP addresses (configured for Number of discovered unmanaged IP addresses per notification ). This is the time interval between two notifications for discovered unmanaged objects. Select the time unit from the drop-down menu. The default is five minutes.
DNS Lookup Option: Specify whether you want to perform a reverse DNS lookup from discovered IP addresses. Select one of the following from the drop-down list:
Network Devices: Select this to resolve network device (switches and routers) IP addresses. This option is selected by default.
Network Devices and End Hosts: Select this to resolve both network device (switches and routers) and end host IP addresses.
Off: Select this to turn off reverse DNS lookups for discovered IP addresses.
DNS Lookup Throttle: This is the value in a percentage that throttles the traffic on the DNS servers. Setting a lower value reduces the number of requests to DNS servers. You can specify a value between 1 and 100. The default value is 100.
Disable discovery for networks not in IPAM: Disables executing discovery on any infrastructure networks that are not presented in the Infoblox IPAM system; e.g. present and managed in a network view or network container.
Authenticate and poll using SNMPv2c or later only: For credential discovery and device polling exclusively using SNMPv2c and up, preventing use of SNMPv1, enable this checkbox.
Use DHCP Routers as Seed Routers: Select this so the Probe members can use the default gateways for associated DHCP ranges and networks as seed routers to more quickly discover and catalog all devices (such as endpoint hosts, printers and other devices). All such default gateways are automatically leveraged by discovery, and no further configuration is necessary unless you wish to exclude a device from usage.
Use this option carefully and avoid continuous updating of DHCP routers by a third-party component such as Microsoft servers, as it may trigger a discovery service restart when attempting to apply the new configuration.Ensure to check for a list of configured DHCP seed routers for any discovery Probe member in the Seed tab -> Advanced tab of the Member Discovery Properties editor.
Log IP Discovery events in Syslog: Sends a message to the configured Syslog service when an IP address of an active host is discovered.
Log network discovery events in Syslog: Sends a message to the configured Syslog service when a network discovery process takes place in the Grid.
Save the configuration.
...
For more information on configuring device credentials, see the following sections:
Configuring SNMPv3 Credentials
If any SNMP or CLI credentials become obsolete, you can reset them for all affected devices at once. After that, Network Insight re-guesses the credentials for each device. This does not apply to CLI credentials manually set for specific devices. For more information, see the reset snmp andreset cli Administrative Shell commands.
You can assign a credential to a credential group that is specific to a particular device group. For more information about credential groups, seeConfiguring Credential Groups below.
| Anchor | ||||
|---|---|---|---|---|
|
An SNMPv1/v2 community string is similar to a password in that the discovered device accepts queries only from management systems that send the correct community string. This community string must exactly match the value that is entered in the managed system.
...
From the Grid tab, select the GridManager tab, and then click Discovery.
For the Grid: Click Edit -> GridDiscoveryProperties in the Toolbar.
For the Probe member: Select the member checkbox, and then click Edit -> MemberDiscoveryProperties in the Toolbar.Click the Credentials tab.
To override the inherited Grid settings for a Probe member, click Override.
Click the Add icon and specify the credential details in the corresponding cells:
ReadCommunity: Enter a text string that the management system sends together with its queries to the network device during discovery.
Credential Group: For the Grid, select a group to which you want to assign the credential. For the Probe member, the table displays settings that were configured on the Grid, but only the default credential group is used for the member. You can edit the credentials list making up the default group by clicking Override.
Order: The order for attempting the use of the credential.
Comment: A text comment about the credential.
Optionally, you can test the credentials you added to the list. You can test SNMPv1/v2c and SNMPv3 credentials against any device or any IP address, at the Grid level or from any Probe member or network view. For more information, see Testing SNMP and CLI Credentials below.
Click Save&Close to save changes.
...
To export the entire list of community strings in a table file readable by a spreadsheet program, click the Export icon and choose Export Data in Infoblox CSV Import Format. To export all data in a different format, click the Export icon and choose Export Visible Data.
| Anchor | ||||
|---|---|---|---|---|
|
SNMPv3 allows the use of two secret keys for every credential — one for authentication and another for encryption. Network Insight allows flexible application of keys — authentication but no encryption, for example. You define users in one of the three following ways:
...
To export the entire list of community strings in a table file readable by a spreadsheet program, click the Export icon and choose Export Data in Infoblox CSV Import Format. To export just the subset of data that is visible in the dialog, click the Export icon and choose Export Visible Data. A ShowPasswords option allows the secret keys to be visible in the import.
| Anchor | ||||
|---|---|---|---|---|
|
SNMP protocols provide a powerful means of querying devices for broad arrays of information. The CLI discovery feature is required for port control tasks including port configuration and network provisioning and de-provisioning, but is not used for other discovery operations or to otherwise manage devices. By default, Probe appliances inherit their member discovery properties, including CLI credential sets, from the Grid level. Enable passwords are entered in separate records and kept as a separate list in Grid Manager.
...
From the Grid tab, select the GridManager tab, and then click Discovery.
For the Grid: Click Edit > GridDiscoveryProperties in the Toolbar.
For the Probe member: Select a member checkbox, and then click Edit > MemberDiscoveryProperties in the Toolbar.Click the Credentials tab > CLI tab.
To override the inherited Grid settings for a Probe member, click Override.
Click the Add icon to add a new CLI username/password entry to the list. Select the CredentialType, which can be one of two choices.
In LoginCredentials, click the Add icon and specify the credential details in the corresponding cells:
Protocol: Select SSH or Telnet. Infoblox recommends the use of SSH.
SSH: SSH credentials require both a username and a password. The default protocol is SSH.
Telnet: In Network Insight, Telnet credentials must use both a username and a password.
Note that should you choose to use a Telnet-based credential, Network Insight requires both the username and password for the login account. This also applies when you override the CLI credentials on objects such as a fixed address, host, or IPv4 reservation. For more information, see the section Defining CLI Credentials Settings for Objects section Defining CLI Credentials for Objects below.
Name: Username for the CLI login account.
Password: Login password for the CLI login account.
Credential Group: For the Grid, select a group to which you want to assign the credential. For the Probe member, the table displays settings that were configured on the Grid, but only the default credential group is used for the member. You can edit the credentials list making up the default group by clicking Override.
Comment: A text comment describing the CLI login account.
Order: By default, Network Insight inserts the new credential record at the bottom of the credentials list, which is reflected by its Order value, showing the order used for attempting the use of CLI credentials. Enter a new value in the Order field if you want the new credential to be in a position other than the last in order.
In EnableCredentials, click the Add icon and specify the credential details in the corresponding cells:
Protocol: SSH or Telnet. Infoblox recommends the use of SSH.
Password: Enable password for device configuration access.
Credential Group: For the Grid, select a group to which you want to assign the current credential. For the Probe member, this setting is inherited and cannot be changed.
Comment: A text comment about the credential.
Order: By default, Network Insight inserts the new record at the bottom of the list, reflected by its Order value, showing the order used for attempting use of the CLI credentials. Enter a new value in the Order field if you want the new credential to be in a position other than the last in order.
Optionally, you can test the credentials you added to the list. For more information, see Testing SNMP and CLI Credentials below.
Click Save&Close.
| Anchor | ||||
|---|---|---|---|---|
|
You can define CLI credentials and enable password credentials for individual devices through associated IPAM objects:
...
From the DataManagement tab, select the IPAM tab.
In the IPAM IP List page or the IPAM IP Map page, navigate to the required network and then to the IP associated with the object you want to edit.
Note for each network, the IP list page provides a Type data column showing the IPAM object type that is associated with any IP address. Also, check the MAC Address column in the IP List page for information about associated objects.
Click the IP address. On the IP address page, click the RelatedObjects tab.
Select the checkbox for the object in the Related Objects panel and click Edit.
In the object editor, click the Discovery tab.
Click OverrideCLICredentials.
By default, CLI credential definitions use SSH at the object level. Select AllowTelnet if you want to allow both SSH and Telnet credential usage. Infoblox recommends SSH because of better security.Enter the Name and Password values and the EnablePassword value.
Click TestCLICredentials to test the CLI discovery credential settings applied to the object.
When finished, click Save&Close.
| Anchor | ||||
|---|---|---|---|---|
|
After configuring SNMP and CLI credentials, you can click TestCredentials in the SNMP Credentials or CLI Credentials panel to test the credentials. Credential testing ensures that the configured credentials work for as many devices and networks as possible. The procedure in this section applies to both the Grid and the member levels. You can override the Grid settings at the member level.
...
For more information, see the following sections:
| Anchor | ||||
|---|---|---|---|---|
|
You can create, edit and delete custom credential groups. As for the default credential group, you can rename it, but not delete it.
...
To delete a credential group, select the group and click the Delete icon.
| Anchor | ||||
|---|---|---|---|---|
|
You populate a credential group with credentials in the Grid Discovery Properties. For Probe members, you can edit the credentials list inside a group for the default credential group only. choose to inherit the Grid credential groups settings or to override them with the default group. If the deafult group contains credentials from both Grid and member and it is assigned to a network, Network Insight uses only member-level credentials.
...
Configuring SNMPv1/v2 Credentials
Configuring SNMPv3 Credentials
Configuring CLI Credentials
| Anchor | ||||
|---|---|---|---|---|
|
Probe members, networks and ranges inherit the credential groups assignment from the Grid. You can override this assignment with another credential group for networks and ranges. For members, you cannot assign a credential group as they always use the default group for credential guessing.
Assigning a Credential Group to the Grid
...
Go to Data Management > DHCP.
Click the name of an existing IPv4/IPv6 network.
Click the Add or Edit icon > Range.
Click the Discovery tab.
Credential Group: The field displays the selection inherited from the Grid unless you override it. Click Override and select the required credential group.
Save the configuration.
| Anchor | ||||
|---|---|---|---|---|
|
To view which credential group was used to guess credentials for a particular device, complete the following:
Go to Data Management > IPAM or Devices tab > Discovery Status.
Hover the mouse over SNMP or CLI credential status of a device.
A tooltip mentioning the credential group name appears.
| Anchor | ||||
|---|---|---|---|---|
|
Seed routers can be defined only on Probe appliances. You can define seed routers that NIOS uses in quickly performing network discovery. The definition of seed routers is highly recommended for IPv4 networks and is required for IPv6 networks. For the discovery of any IPv6 networks, you must use seed router values that comprised of at least one well-connected IPv6 router, preferably with routes to all other networks to be managed. 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 seed router(s) also helps determine how many seed routers you need. Avoid having more seed entries than necessary.
...
For more information, see the following sections:
To view discovery results for SDN and SD-WAN, go to Data Management > Devices. For information, see Viewing Discovered Devices and their Properties.
| Note |
|---|
NoteTo ensure successful SDN and SD-WAN discovery, use an admin user account. |
| Anchor | ||||
|---|---|---|---|---|
|
Enabling discovery of Cisco ACI devices provides visibility into your Cisco ACI infrastructure. This allows you to view and manage discovered IP addresses of Cisco ACI fabric members such as APIC controllers and fabric switches with their attached end points.
...
From the Grid tab, select the Grid Manager tab, and then click Discovery.
Select a Probe member, and then click Edit > Member Discovery Properties in the Toolbar.
Click the SDN/SD-WAN tab.
Click the Add icon and select Cisco ACI.
Complete the following:
Fabric Name: Specify a short and unique name for the current Cisco ACI configuration.
Addresses: Enter the hostname or IP address of the Cisco APIC controller. If your fabric includes more than one controller, click the Add icon to add more addresses.
Protocol: Select HTTP or HTTPS.
Network View: Select the network view to identify the corresponding network interface for connectivity with the Cisco ACI. Also, this network view will be assigned to discovered devices from this ACI.
Username: The login name for the Cisco ACI.
Password: The login password.
Comment: Additional information about the Cisco ACI.
Connect using Grid Proxy settings if available: Select if you want to use the Grid Proxy for connectivity to or from the Cisco ACI. If the Proxy is specified in the Grid properties, then Network Insight uses it. For more information, see Configuring Proxy Servers.
Click Test Connection to check if the fabric is reachable and the provided credentials are correct. The connection test results are also written to the syslog.
Click Add.
Click Save & Close.
| Anchor | ||||
|---|---|---|---|---|
|
Enabling discovery of Cisco Meraki provides visibility into your Cisco Meraki SD-WAN elements, for example:
...
From the Grid tab, select the Grid Manager tab, and then click Discovery.
Select a Probe member, and then click Edit > Member Discovery Properties in the Toolbar.
Click the SDN/SD-WAN tab.
Click the Add icon and select Cisco Meraki.
Complete the following:
Config Name: Specify a short and unique name for the current Cisco Meraki configuration.
Address: Enter the hostname or IP address of the Cisco Meraki Dashboard API. By default, it is api.meraki.com.
Protocol: HTTPS by default.
Network Interface: Select the interface that will be used to access the device.
API Key: Access key required to use Cisco APIs.
Comment: Additional information about the Cisco Meraki device.
Connect using Grid Proxy settings if available: Select if you want to use the Grid Proxy for connectivity to or from the Cisco Meraki device. If the Proxy is specified in the Grid properties, then Network Insight uses it. For more information, see Configuring Proxy Servers.
Click Test Connection to check if the device is reachable and the provided credentials are correct. The connection test results are also written to the syslog.
Click Add.
Click Save & Close.
| Anchor | ||||
|---|---|---|---|---|
|
Enabling discovery of Cisco Viptela devices provides visibility into your Viptela SDN/SD-WAN infrastructure. You can use Viptela as an on-premise SDN controller or as a cloud solution.
...
From the Grid tab, select the Grid Manager tab, and then click Discovery.
Select a Probe member, and then click Edit > Member Discovery Properties in the Toolbar.
Click the SDN/SD-WAN tab.
Click the Add icon and select Viptela.
Complete the following:
Config Name: Specify a short and unique name for the current Viptela configuration.
Address: Enter the hostname or IP address of the Viptela vManage controller.
On-premise controller: Check this if your Viptela setup is on-premises.
Protocol: Select HTTP or HTTPS.
Network Interface: Select the interface that will be used to access the device.
Network View: Select the network view in which the discovered Viptela devices will be shown.
Username: The login name for the Viptela vManage controller.
Password: The login password.
Comment: Additional information about the Viptela vManage controller.
Connect using Grid Proxy settings if available: Select if you want to use the Grid Proxy for connectivity to or from the Viptela. If the Proxy is specified in the Grid properties, Network Insight uses it.
Click Test Connection to check if the device is reachable and the provided credentials are correct. The connection test results are also written to the syslog.
Click Add.
Click Save & Close.
| Anchor | ||||
|---|---|---|---|---|
|
On the Grid side, you can enable or disable the SDN and SD-WAN polling, specify end host collection timing, and define network view mapping rules. If SDN and SD-WAN polling is disabled, only traditional network devices are polled. Controlling the polling setting and end host data collection allows you to reduce the load on your system if required.
...
| Note |
|---|
NoteA network name in the mapping table is made up by combining the Meraki organization and network name. The Source column displays the fabric name or config name that you previously defined for the SDN or SD-WAN configuration. The network view name is made of the network and source values. |
| Anchor | ||||
|---|---|---|---|---|
|
For information about Advisor, see Monitoring Device Lifecycle and Vulnerabilities Using Advisor.
...