New and Changed Information
The following table provides an overview of the significant changes up to this current release. The table does not provide an exhaustive list of all changes or of the new features up to this release.
Release Version | Feature | Description |
---|---|---|
There were no major changes from the previous release. |
IPAM Integrator
The IPAM Integrator allows read-only access to the IPAM and NDFC servers. Currently, IPv4 overlay DHCP is supported. In read-only access mode, IPAM records are retrieved and mapped to NDFC networks in Easy Fabric and eBGP VXLAN fabric. You can also choose to sync up records on-demand between NDFC and IPAM server. An Infoblox user who has the API permission and at least IPv4 network read permission of IPAM will be able to view the retrieved Infoblox records.
In addition to the matched subnets that exist on both IPAM server and NDFC, the IPAM Integrator lists the subnets with conflicting netmask for review.
Accessing IPAM Integrator
This procedure shows how to access IPAM integrator.
-
To enable IPAM Integration feature, perform the following steps:
-
Choose Admin > System Settings > Feature Management.
-
Check the IPAM Integration check box and click Apply.
-
-
On NDFC UI, choose Virtual Management > IPAM Integrator.
-
Click on Authentication Access to provide the required IPAM server authentication details.
-
Provide the required access details in the Access Config window.
You can provide the access details of an Infoblox server or an Infoblox grid manager.
-
IPAM Server IP Address - Specifies the IP address of the IPAM server.
-
IPAM Server Username - Specifies the user name for the IPAM server. The Infoblox user has to be granted API permission for the application to retrieve data from Infoblox server via API.
-
IPAM Server Password - Specifies the password for the IPAM server with respect to the username.
-
Poll Interval (minutes) - Specifies the time in minutes that determines how often you want the data to be retrieved from Cisco NDFC and IPAM server. The default value is 15 minutes.
-
-
Click Authenticate.
-
After you access IPAM, you can modify, remove the access details, or edit the poll interval using the Edit Authentication Access.
Only the NDFC users with the admin role can add, update, and delete the access setting. Also, only Infoblox user who has been granted with API permission and at least IPv4 network read access of IPAM permission is able to view the retrieved Infoblox network records.
Viewing Network IP Scope
Network IP Scope is the landing page after you access the IPAM Integrator.
The following table describes the fields retrieved from the IPAM server.
Field |
Description |
Network View |
Specifies the network view, which is a single routing domain with its own networks and shared networks on the Infoblox server. |
IP Subnet |
Specifies the IP subnet defined in the IPAM server. A subnet, or subnetwork, is a segmented piece of a larger network. More specifically, subnets are a logical partition of an IP network into multiple, smaller network segments. |
DHCP Utilization |
Specifies the utilization percentage of a network in terms of the IP addresses that are leased out.Hover over the percentage value to view the number of allocated IPs and their details.In the Infoblox server, it takes time to calculate the DHCP utilization. The IPAM utilization is calculated approximately every 15 minutes on the Infoblox server, and the latest value will be reflected on the IPAM Integrator after that. |
IP Range |
Specifies the IP range for the network. Hover over a range to view the enabled DHCP range, the reserved DHCP range, and the fixed addresses for a network. |
The following table describes the fields retrieved from NDFC.
Field |
Description |
Fabric Name |
Specifies the name of the fabric. |
Fabric Type |
Specifies the type of the fabric. It can be Multi-Site Domain (MSD), or a standalone easy fabric or an eBGP VXLAN fabric. |
Network Name |
Specifies the name of the network. |
VRF Name |
Specifies the name of the VRF. |
Network ID |
Specifies the network ID. |
VLAN ID |
Specifies the VLAN ID. |
Last Updated (by Infoblox) |
Specifies the date and time when the data was last updated by Infoblox. The date and time of the last poll are displayed under the Network IP Scope title. |
Click Export to export the data in a .csv file.
For each field, you can sort the values by clicking the arrow icons, and search by entering the search criterion in Filter by attributes box.
The polling of data is based on the following criteria:
-
Poll interval value that the user configured initially in the Access Authentication window. It specifies how often you want the data to be retrieved from Cisco NDFC and IPAM.
-
User can click the Refresh icon to receive instantaneous data from NDFC and IPAM server.
-
NDFC Web UI automatically refreshes every 2 minutes and displays data retrieved from NDFC and Infoblox server.
For example, if the poll interval is 15 minutes and user doesn’t refresh (on-demand) the data during this 15-minute duration, the NDFC Web UI displays the same polling data after every 2-minute refresh until 15 minutes. After 15 minutes, new data is polled from NDFC and IPAM, and saved in the database. This new data is fetched by NDFC after a total of 16 minutes.
Viewing Statistics and Summary Data for the Subnet Utilization
To view the summary data for the utilization of the IP Subnet over a time, navigate to the following path.
-
Click on the IP Subnet. A Subnet slide-in pane displays summary data with IP Allocations, Utilization, Allocations, and DHCP Range Details.
To view the statistics for the utilization of the IP Subnet over a time, navigate to the following paths.
-
Click on the IP Subnet. A Subnet slide-in pane displays summary data.
-
Expand the Subnet slide-in pane. A Subnet Details screen appears.
-
Click the Statistics tab.
Click the drop-down list and select the time for which you want to view the statistics. These statistics include utilization of subnet such as DHCP allocations, total allocations, dynamic allocations, and static allocations.
Viewing IP Allocation for Hosts
To view the IP allocation for each host, navigate to the following paths.
-
Click on the IP Subnet. A Subnet slide-in pane displays summary data.
-
Expand the Subnet slide-in pane. A Subnet Details screen appears with IP Allocation details.
The following fields are displayed for each host in the IP Allocation window. The data for these fields is retrieved from the IPAM server.
-
IP Address
-
Host Name
-
State of the host, that is, active or free
-
Range start time and end time
-
Subnet
-
VRF Name
-
Protocol version
-
MAC address
-
DHCP server info such as IP address and server name
-
Switch:Port
-
Fabric Name
-
Last requested by the host
The Switch:Port and Fabric Name are retrieved through NDFC EPL (Endpoint Locator) integration. Their values are empty if EPL feature is not enabled.
For each field, you can sort the values by clicking the arrow icons, and search by entering the search criterion in Filter by attributes box.
By default, information about only active hosts are displayed. Click the All value to view information about all hosts retrieved from the IPAM server. Click Export to export the data in a .csv file.
Hosts that were recently freed show as "FREE" in the All tab. All the originally free hosts won’t be shown as FREE. Only the hosts that were recently freed appear in this tab.
Viewing Conflicting Networks
IPAM Integrator detects conflicting networks defined in IPAM server and NDFC. You can view this info by clicking Conflicting in the Network IP Scope window.
For example, if one network is a subset of another, the conflicting IP addresses of the network are displayed under Conflicting.
The data is displayed similar to how the Matched data is displayed. You can click the IP range value under the IP Range column to view the IP allocation for each host.
Note that this table also lists the NDFC Gateway for the conflicting IP scopes in addition to the subnet information from the IPAM server.
For each field, you can sort the values by clicking the arrow icons, and search by entering the search criterion in Filter by attributes box.
Copyright
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
© 2017-2024 Cisco Systems, Inc. All rights reserved.
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Need help?
- Open a Support Case
- (Requires a Cisco Service Contract)