Applies to CN1610 Cluster switch CN1610 is migrated from one management subnet to a different one management interface does not automatically receive a DHCP IP address Switch log shows <13> Apr 15 23:...Applies to CN1610 Cluster switch CN1610 is migrated from one management subnet to a different one management interface does not automatically receive a DHCP IP address Switch log shows <13> Apr 15 23:30:17 switch-1 DHCP_CLI[osapiTimer]: dhcp_prot.c(784) 51998 %% Failed to acquire an IP address on Network Port; DHCP Server did not respond. <13> Apr 15 23:25:14 switch-1 DHCP_CLI[osapiTimer]: dhcp_prot.c(784) 51996 %% Failed to acquire an IP address on Network Port; DHCP Server did not respond.
<13> Oct 21 01:51:16 172.16.0.100-1 DHCPCLIEN[300012345]: dhcp_prot.c(745) 82300 %% Failed to acquire an IP address on Network Port; DHCP Server did not respond. <13> Oct 21 01:56:19 172.16.0.100-1 DH...<13> Oct 21 01:51:16 172.16.0.100-1 DHCPCLIEN[300012345]: dhcp_prot.c(745) 82300 %% Failed to acquire an IP address on Network Port; DHCP Server did not respond. <13> Oct 21 01:56:19 172.16.0.100-1 DHCPCLIEN[300012345]: dhcp_prot.c(745) 82301 %% Failed to acquire an IP address on Network Port; DHCP Server did not respond. <13> Oct 21 02:01:22 172.16.0.100-1 DHCPCLIEN[300012345]: dhcp_prot.c(745) 82302 %% Failed to acquire an IP address on Network Port; DHCP Server did not respond.
Applies to FAS and AFF Systems ONTAP 9.2 and later Issue While setting a static IP address for netboot or boot_recovery operations on port e0M that IP gets set and is reachable, but later in the proce...Applies to FAS and AFF Systems ONTAP 9.2 and later Issue While setting a static IP address for netboot or boot_recovery operations on port e0M that IP gets set and is reachable, but later in the process it is lost and an attempt to get a DHCP address for that port is made. If DHCP is not available then the netboot or boot_recovery process fails. During the boot sequence the following is seen: Starting DHCP client on e0M