Support Central: KB #2901: NIOS Release Updates

[#1]

Are you looking for the latest information on NIOS releases?  If you have Support access, you can view all the past and present details here: https://support.infoblox.com/app/answers/detail/a_id/2901/kw/2901

Introduction:

Infoblox NIOS 7.3.x software, coupled with Infoblox appliance platforms, enables customers to deploy large, robust, manageable and cost-effective Infoblox Grids. This next-generation solution enables distributed delivery of core network services-including DNS, DHCP, IPAM, TFTP, and FTP-with the nonstop availability and real-time service management required for today's 24x7 advanced IP networks and applications.

Please note the following:

NIOS 7.3.x is not supported on the following appliances: IB-250, IB-250-A, IB-500, IB-550, IB-550-A, IB-1000, IB-1050, IB-1050-A, IB-1550, IB-1550-A, IB-1552, IB-1552-A, IB-1852-A, IB-2000, IB-2000-A, IB-VM-250, IB-VM-550, IB-VM-1050, IB-VM-1550, IB-VM-1850, IB-VM-2000, and Trinzic Reporting TR-2000 and TR-2000-A series appliances. You cannot upgrade to NIOS 7.3.x on these appliances. See Upgrade Guidelines on page 25 for additional upgrade information.

Infoblox Reporting and Analytics: There are some significant changes in the functionality and user interface for the Infoblox Reporting solution. Infoblox recommends that you take some time to explore and navigate through the new user interface to get familiar with the new features and terminologies. If you are upgrading to NIOS 7.3.x from a previous NIOS release, your custom reports will be affected and you may need to take some actions to re-create them. For more information about these changes, see Changes to Default Behavior on page 19.

RESOLVED ISSUES

The following issues were reported in previous NIOS releases and resolved in this release. The resolved issues are listed by severity. For descriptions of the severity levels, refer to Severity Levels on page 46.

Fixed in 7.3.6

ID	Severity	Summary
NIOS-60260	Major	When upgrading from NIOS 7.3.4 to NIOS 7.3.5, certain reporting data were affected because the reporting application was misconfigured.

Fixed in 7.3.5

ID	Severity	Summary
NIOS-59793	Critical	NTP daemon did not listen to anycast addresses.
NIOS-59337	Critical	When upgrading from 7.3.3 to 7.3.4, audit logs were filling up with "Login_Denied" messages at logins for the SPLUNK-REPORTING-ADMIN group.
NIOS-58962	Critical	The 7.2 appliance experienced a DDNS issue with incorrect inheritance of properties from the network container that changed the behavior for certain networks. This resulted in network devices getting registered in a wrong DNS domain.
NIOS-58580	Critical	CSV import of host records failed if more than one host was returned for the imported host address.

ID	Severity	Summary
NIOS-59946	Major	Unable to upgrade to NOS 7.3.4 due to a lack of upgrade path.
NIOS-59915	Major	The DNS service on the primary server restarted on its own and started serving automatically.
NIOS-59905	Major	PXE clients were unable to renew the lease when the client UID changed even when the "Ignore Client UID" option was enabled.
NIOS-59860	Major	DNS TTL zero value was not handled as expected when answering multiple client queries for the same name, which negatively impacted client performances.
NIOS-59842	Major	A TE1410 appliance rebooted as a result of high swap usage.
NIOS-59799	Major	DNS integrity check was performed on any member in the Grid if the members' database had zones with the DNS integrity check enabled even if the member was not assigned as integrity check member.
NIOS-59798	Major	Active Directory authentication denied login if the user belonged to a group which name contained multiple backslashes.
NIOS-59797	Major	Remotely authenticated admin users (RADIUS) assigned to a local group were unable to log in using SSH.
NIOS-59635	Major	Member DNS properties dialog box required that the named.conf file listened on the query source address, which caused unintended behavior.
NIOS-59544	Major	When a new VIP address was configured for BIND and used for OSPF Anycast, the OSPF daemon restarted before BIND, which caused DNS queries not being answered.
NIOS-59521	Major	CSV import caused Grid Master to restart due to a database error.
NIOS-59489	Major	Network Insight was unable to discover devices if the SNMP polling options were disabled at the Grid level but enabled at the Network level.
NIOS-59436	Major	Grid Manager displayed a blank screen for the Internet Explorer Compatibility View mode.
NIOS-59434	Major	Synchronization with a Microsoft server did not work due to a database error.
NIOS-59409	Major	It was impossible to increase the cache size on recursion servers beyond 512 MB after a DNS outage.
NIOS-59404	Major	A new PT-1400 appliance got into a reboot recovery loop on first startup.
NIOS-59377	Major	A Grid Master showed CPU and SWAP issues for API usage due to suboptimal HTTP daemon settings.
NIOS-59359	Major	DNS service restart time was excessive on an IB/VM 1400 appliance, which caused a DNS outage.
NIOS-59355	Major	Network Insight: Cisco ASR VRF-aware router did not discover interface information.
NIOS-59322	Major	An IB-4030 appliance hanged and rebooted after a DNS cache acceleration went above threshold.
NIOS-59318	Major	OSPF was advertised through a VIP VLAN interface while another VIP VLAN was configured as the OSPF advertizing interface.
NIOS-59315	Major	Multiple DNS records were regularly disappearing from their Microsoft-managed DNS zones after an upgrade.
NIOS-59301	Major	A Grid member lost connectivity to Grid Manager and rebooted from time to time.
NIOS-59173	Major	The DNS server were unable to recurse out to the Internet on an IPv6-only Grid.
NIOS-59054	Major	The restart process of the DNS and DHCP services was blocked while a Grid member was generating a big amount of certain objects under high load.
NIOS-59041	Major	HA Grid Master used the LAN-1 interface to contact the HSM device rather than the VIP interface as documented in Infoblox documentation, and the communication with the HSM appliances worked only partially.
NIOS-59038	Major	Synchronization with a Microsoft server failed due to a NIOS zone not updating with Microsoft server properly.
NIOS-59031	Major	Grid Manager was inaccessible via GUI and API after booting a vNIOS instance in an Openstack/KVM environment.
NIOS-58966	Major	The Grid Master passive node looped into a synchronization state and produced duplicate object logs.
NIOS-58400	Major	BGP session terminated, causing routing flaps and a DNS service outage.
NIOS-58328	Major	DNS updates were denied after a TSIG key was configured under NAMEDACL.
NIOS-58293	Major	Writing DNS objects to the database took an excessive amount of time due to incorrect Python script behavior, causing the operation to fail.
NIOS-60066	Minor	Grid Manager did not have an option to restrict users to do DNS scavenging for underscore zones.
NIOS-60040	Minor	Network Insight did not associate IP addresses with the proper switch/port.
NIOS-59959	Minor	The named_dump.db cache file in the support bundle was truncated.
NIOS-59682	Minor	The traffic.cap file was missing in the root of the tcpdumplog.tar.gz file when extracted and was found in \storage\tmp.
NIOS-58590	Minor	Some users were getting an intermittent error "DBError: Error occurred during restart banner cleanup" after clicking the Restart Service button in the Grid Manager system messages banner.
NIOS-59332	Enhance	vDiscovery for OpenStack did not discover all possible tenants declared in OpenStack. Now it discovers all tenants if the OpenStack user has the admin role in at least one tenant.