Wireless Access

last person joined: 11 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Noisy process log after upgrade to 6.4 (dhclient)

This thread has been viewed 0 times

  • 1.  Noisy process log after upgrade to 6.4 (dhclient)

    Posted Mar 14, 2014 06:46 AM

    After an upgrade to 6.4 to solve certain problems we had with fragmented packets we get a ton of these in our process log:

     

    Mar 14 11:41:14	 dhclient: XMT: Solicit on bond0, interval 128410ms.
Mar 14 11:41:14	 dhclient: XMT: Solicit on br0, interval 122010ms.
Mar 14 11:41:15	 dhclient: XMT: Solicit on br0, interval 125650ms.
Mar 14 11:41:17	 dhclient: XMT: Solicit on bond0, interval 123430ms.
Mar 14 11:41:17	 dhclient: XMT: Solicit on br0, interval 112070ms.
Mar 14 11:41:17	 dhclient: XMT: Solicit on br0, interval 108750ms.
Mar 14 11:41:18	 dhclient: XMT: Solicit on br0, interval 116000ms.
Mar 14 11:41:18	 dhclient: XMT: Solicit on bond0, interval 111110ms.
Mar 14 11:41:19	 dhclient: XMT: Solicit on br0, interval 108170ms.
Mar 14 11:41:20	 dhclient: XMT: Solicit on br0, interval 121370ms.
Mar 14 11:41:21	 dhclient: XMT: Solicit on br0, interval 121400ms.

     What are these? Looking at the intervals it looks like it's coming from the access points, but I don't understand why. Tried to google a bit, and dhcp solicit seems to be a DHCPv6 feature..

     

    Are the access points in AOS 6.4 trying to use DHCP on both ipv4 and ipv6? We only use ipv4.



  • 2.  RE: Noisy process log after upgrade to 6.4 (dhclient)

    EMPLOYEE
    Posted Oct 21, 2014 11:08 AM
    It's related to the APs now using ipv6 trying to get an IP address. ----------------------------------- Bug ID – 100208. • These logs are spewed out from dhclient6 of AP. In 6.4 version, we support ipv6 dhcp client, it is a daemon. While it is starting, these logs are spewed out from AP until it is killed. • These messages are errantly appearing in nominal log severities, should only appear when debug level is configured. • Engineering Team confirmed that it is implemented in AOS 6.5 So the messages should only appear if DEBUG logging is enabled, 6.5 will contain the change.