English Community

Datacenter SystemsBladeCenter / Flex Systems
All Forum Topics
Options

15 Posts

07-11-2017

US

44 Signins

423 Page Views

  • Posts: 15
  • Registered: ‎07-11-2017
  • Location: US
  • Views: 423
  • Message 1 of 3

AMM kept losing connectivity: "DHCP application failed to obtain DHCP IP address.FAIL".

2018-02-23, 18:34 PM

The AMM lost connectivity after an undetermined amount of idle time. It was pingable but couldn't be accessed either through the web interface or SSH remote login. The workaround was to reseat the AMM and then it was able to be accessed again. We did the paper clip pinhole reset but the connectivity problem kept coming back. 

 

We then looked through the AMM's event logs and found this message: "DHCP application failed to obtain DHCP IP address.FAIL". Has anyone seen this message before? We never seen this message before on our other working AMMs with the same configuration and firmware.

 

We are currently using firmware level BPET66N, which has been working fine on our other systems but will be trying to update the firmware to BPET68C to see if the lost connectivity problem will be fixed.

 

Thanks!

Reply
Options

83 Posts

08-13-2015

CN

135 Signins

1249 Page Views

  • Posts: 83
  • Registered: ‎08-13-2015
  • Location: CN
  • Views: 1249
  • Message 2 of 3

Re: AMM kept losing connectivity: "DHCP application failed to obtain DHCP IP address.FAIL"

2018-02-27, 6:54 AM

we suggest set fixed address on AMM ,IMM etc, so that the management ip didn't change to others duo to some reason.

Reply
Options

30 Posts

08-06-2015

CN

19 Signins

210 Page Views

  • Posts: 30
  • Registered: ‎08-06-2015
  • Location: CN
  • Views: 210
  • Message 3 of 3

Re: AMM kept losing connectivity: "DHCP application failed to obtain DHCP IP address.FAIL"

2018-02-28, 6:32 AM

Here is a probably cause: When a DHCP client is moved from one subnet to another, it may fail to obtain a valid IP address on the new subnet.

 

When a DHCP client that has previously had a DHCP-assigned address is started again, The client will attempt to verify that it can still use the same address by sending a DHCPRequest packet with the previously assigned IP address.

 

Then DHCP server begin to check if it came from the local segment. If it originated from the local segment, the DHCP server compares the requested address to the IP address and subnet mask belonging to the local interface that received the request. If the address appears to be on the same subnet, the DHCP server will remain silent even if the address is not in the range of its pool of addresses. The DHCP server assumes that the address was assigned by another DHCP server on the same segment if it is not from its own pool. So the client will fail to obtain a valid IP address for the new subnet.

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms