Wireless Access

Reply
Highlighted
MVP

Help with Error: DHCP-OPTION82 relay agent receive, bogus giaddr

Hi,


Could someone help me with the above error message?

 

It is generating from the IP address on the secondary controller on a site for a particular client VLAN however the option DHCP82 is not enabled on the vlan so I'm not sure how to get it to stop generating as it is clogging up syslog entries.

 

Thanks

Highlighted
Super Contributor II

Re: Help with Error: DHCP-OPTION82 relay agent receive, bogus giaddr

Are you sending DHCP to an external server, or is it being served by the controller?

 

 

Dustin Burns
Senior Mobility and Access Engineer @WEI
ACMX #509 | ACCX #1272 | ACSA | ACDA | ACEA | CCNP | CCDP | CCNA Wireless

If my post address your queries, give kudos and accept as solution!
Highlighted
MVP

Re: Help with Error: DHCP-OPTION82 relay agent receive, bogus giaddr

It is being sent to a DHCP Server

Highlighted
Super Contributor II

Re: Help with Error: DHCP-OPTION82 relay agent receive, bogus giaddr

And you have this unchecked? See image: 

Dustin-Burns_0-1596111088514.png

 

 

 

Dustin Burns
Senior Mobility and Access Engineer @WEI
ACMX #509 | ACCX #1272 | ACSA | ACDA | ACEA | CCNP | CCDP | CCNA Wireless

If my post address your queries, give kudos and accept as solution!
Highlighted
MVP

Re: Help with Error: DHCP-OPTION82 relay agent receive, bogus giaddr

Yeah sure do:

 

scottm_0-1596111758059.png

 

Highlighted
Super Contributor II

Re: Help with Error: DHCP-OPTION82 relay agent receive, bogus giaddr

Other than checking to make sure another L3 interface in that VLAN is not also relaying, and checking the ip information / masks for the scope are correct, I would say TAC to the rescue?

 

 

Dustin Burns
Senior Mobility and Access Engineer @WEI
ACMX #509 | ACCX #1272 | ACSA | ACDA | ACEA | CCNP | CCDP | CCNA Wireless

If my post address your queries, give kudos and accept as solution!
Highlighted
MVP

Re: Help with Error: DHCP-OPTION82 relay agent receive, bogus giaddr

I noticed this on the controller:

 

(WLAN-1) [MDC] #show ip dhcp relay counters

Invalid/Missing GIADDR           537

 

Also in the logs there is multiple entries, all of the entries are from the IP addresses of the client VLANs on the secondary controller (WLAN-2):

 

 
 
 
 

Screenshot at Jul 30 13-54-58.png

Highlighted
Super Contributor II

Re: Help with Error: DHCP-OPTION82 relay agent receive, bogus giaddr

Is there any type of L3 GW redundancy deployed on the client VLANs?

 

 

Dustin Burns
Senior Mobility and Access Engineer @WEI
ACMX #509 | ACCX #1272 | ACSA | ACDA | ACEA | CCNP | CCDP | CCNA Wireless

If my post address your queries, give kudos and accept as solution!
Highlighted
Guru Elite

Re: Help with Error: DHCP-OPTION82 relay agent receive, bogus giaddr


@scottm wrote:

I noticed this on the controller:

 

(WLAN-1) [MDC] #show ip dhcp relay counters

Invalid/Missing GIADDR           537

 

Also in the logs there is multiple entries, all of the entries are from the IP addresses of the client VLANs on the secondary controller (WLAN-2):

 

 
 
 
 

Screenshot at Jul 30 13-54-58.png


There is an open bug where DHCP-Option82 is mentioned wrongly in this log.  In ArubaOS 8.7 the "DHCP-Option82" string will be removed and this will be in logged at the debug level, instead.  The log right now is correctly  indicating that the giaddr is invalid or missing, however.  The DHCP-Option82 portion can be ignored.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Video Knowledge Base
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Highlighted
MVP

Re: Help with Error: DHCP-OPTION82 relay agent receive, bogus giaddr

Is there any way to stop it from generating this one log in the meantime?

 

It is uploading a lot of logs to the syslog server which is cloud hosted so adding on cost (not much) but still not required.  The thing is as this is an error log if I change the logging level to below this I will miss any other warning or error messages potentially.

 

Thanks

 

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: