IP-Transceiver IP Reverting to DHCP
Occasionally, during an upgrade, the AoIP Audio IP address (the “second” IP address) of the IP-Transceiver may revert to a DHCP connection. To remedy:
In EHX, navigate to Hardware > Transceivers and select the settings cog for the unit in question.
Set the AoIP Audio IP for a static IP, and enter the appropriate IP, Subnet Mask, and Gateway.
Apply using the blue check box.
Let the unit reboot, then verify the connection.
or:
2. Using the AoIP Admin (the “first” IP address) of the unit, navigate the CCM and log in.
Navigate to Device > Network
Set the AoIP Audio Address to static, and enter the appropriate IP, Subnet Mask, and Gateway.
Save Changes.
Let the unit reboot, then verify the connection.
If the unit RANDOMLY reverts to DHCP:
Navigate the the CCM and login.
Navigate to Device > Maintenance > Support Info.
Let the logs compile, then save/export.
Unzip the logs, and navigate to /var/log/messages
Search for the following entries:
2022-05-12T01:49:56.872473+00:00 CC-TCVR-46Y50058 avahi-autoipd[605]: Received conflicting normal ARP packet.2022-05-12T01:49:56.873360+00:00 CC-TCVR-46Y50058 avahi-autoipd[605]: Trying address 169.254.120.160
2022-05-12T01:50:02.310859+00:00 CC-TCVR-46Y50058 avahi-autoipd[605]: Callout BIND, address 169.254.120.160 on interface eth0
2022-05-12T01:50:02.334014+00:00 CC-TCVR-46Y50058 avahi-daemon[754]: Registering new address record for 169.254.120.160 on eth0.IPv4.
2022-05-12T01:50:06.309707+00:00 CC-TCVR-46Y50058 avahi-autoipd[605]: Successfully claimed IP address 169.254.120.160
*If the above entries are seen, this is internal service/mechanism the IP-Transceiver uses to detect duplicate IPs, and it may be that the unit detected a conflict and tried to change it’s own IP to allow it to re-connect. If a DHCP server is not present, this can land the AoIP Audio IP on a different subnet from the AoIP Audio connection, thus leaving it unusable as there is a protection in place to eliminate it. Additionally, there are some IPs reserved within the units that are not allowed, so if the DHCP lease comes from something within that range, it will also trip into a protection.
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.
We are looking for your help! Please consider sharing your stories, update an old solution or help us with a new one. Follow this link to share!