Reset Search
 

 

Article

EOS-based switches report DHCP Relay messages"Request could not be relayed to Server"

« Go Back

Information

 
TitleEOS-based switches report DHCP Relay messages"Request could not be relayed to Server"
Symptoms
EOS based switches report this type of message when logging application "router" and "logging default severity" is set to 8
0.0.0.0 DHCPRELAY[284995296]: relay_main.c(315) 207319 This is from manager 1 %% Request could not be relayed to Server

 
Environment
  • EOS
  • DHCP Relay
  • iP helper-address
  • Routing
  • set logging local console enable file enable
  • set logging default Severity 8
  • set logging application Router level 8
  • show logging buffer
Cause
The logging of the message was caused by DHCP discover packets traversing the other vlans.  These packets could not be serviced by the relay agent because there is no ip helper-address configured on some of interface vlans so the DHCP request was never processed..
Resolution
  • To address the issue using a sniffer, capture traffic on the interfaces that do not have a ip helper-address applied, to only capture the DHCP packets, use the filter in wireshark: bootp
  • Then Add the proper ip helper-address to the interfaces 
Additional notes
    To temporally hide the messages:
    Change the logging application level for Router back to the default setting of 6

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255