/
HelixNet: HKB-2X and HRM-4X units take time to reboot if DHCP mode is selected
HelixNet: HKB-2X and HRM-4X units take time to reboot if DHCP mode is selected
Question: I have a question about Ethernet connectivity of the HKB’s and HRM’s. We’ve had some instances where it’s taken a very long time for some of these units to boot up into their respective roles. They will sometimes sit in an “Unassigned” state for some time before finally connecting. To be clear, this is not the norm and happens periodically on different units. I went into the network diagnostics menu on one of the last times this happened and realized the unit had a self-assigned IP address. After a bit the unit refreshed and finally got an address from the DHCP server and booted up into the proper role. Any idea why this may be happening?
Answer: If the DHCP server does not answer within 10 seconds, the unit picks a link-local address (169.254.x.x). It retries DHCP every minute from then on.
Using a Static IP would result in quicker and more consistent boot up.
Answer: If the DHCP server does not answer within 10 seconds, the unit picks a link-local address (169.254.x.x). It retries DHCP every minute from then on.
Using a Static IP would result in quicker and more consistent boot up.
Looking for labels? They can now be found in the details panel on the floating action bar.
CAN'T FIND YOUR ANSWER? CLICK HERE TO CONTACT SUPPORT
This solution was provided by Clear-Com via a question submitted to us by customers like you. If you wish to share with us a new solution or update an old one, please follow this link..
The information on this page is owned by Clear-Com and constitutes Clear-Com’s confidential and proprietary information, may be used solely for purposes related to the furtherance of Clear-Com’ business and shall not be disclosed, distributed, copied or disseminated without Clear-Com’s prior written consent. Click Here for Clear-Com's privacy statement.