Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 27 subscribers
  • Views 1298 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

dhcp stops serving addresses

Ed Rubin

I've got an XG 230 that was just updated to SFOS 17.5.0 GA last night and has two RED 50s serving branch offices. This morningone of the branches had no dhcp service on the Aruba WAP connected to the RED. The XG acts as DHCP server for the RED networks and on the office network for this site all the clients on the WAP had 169.254.xxx.xxx APIPA addresses until I stopped and started the dhcp scope. 

Any ideas on why this was happening? The other three dhcp scopes have not had any issues.



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to LuCar Toni

    Thanks for the insight, I checked and neither of our REDs has tunnel compression enabled. Also we have a second site with an identical RED 50 setup (other than IP subnets) and it hasn't reported any issues. I'm beginning to think there is something wrong with the RED itself.