Passport 8610 error messages

[jcny21]

Hi All,

Last night we had a wierd error message happen and it constantly wrapped for 2 hours and it rebooted the 8610. After the reboot it started again and 2 hours later it rebooted again. The switch is running code 5.0.5.0 and it is IST'ed to another switch. I have multiple server attached via SMLT which wasnt to bad as most servers were ok but stuff that wasnt split had the hit. The error I kept receiving is below, any help from anybody would be greatly appreciated. We contacted Avaya and they have no clue:

CPU5 [03/25/11 16:36:33] IP ERROR DHCP server is configured to offer Re
lay Agent IP address 0.0.0.0 to DHCP client
CPU5 [03/25/11 16:36:34] IP ERROR DHCP server is configured to offer Re
lay Agent IP address 0.0.0.0 to DHCP client
CPU5 [03/25/11 16:36:34] IP ERROR DHCP server is configured to offer Re
lay Agent IP address 0.0.0.0 to DHCP client

[Michael McNamara]

Have you check your configuration? Specifically your DHCP configuration?

Good Luck!

[jcny21]

Yes, all servers are correctly configured and we do not have any dhcp relay on the boxes.

[kstanton]

I am getting the same Issue runing code 5.1.1.1, only the box does not reboot it seems to stop routing then I need to reboot.

[Michael McNamara]

I am getting the same Issue runing code 5.1.1.1, only the box does not reboot it seems to stop routing then I need to reboot.

Hi kstanton and welcome to the forums!

When did this start?

Unfortunately there was no follow-up from @jcny21 so I'm not sure what his outcome was.

What are you running as your DHCP server?

Good Luck!

[kstanton]

Hi Michael

I got the following from jcny21

"Yes we did.. We upgraded to code 5.1.5.1 as recommended by Avaya but we still had a problem. We found a Smart projector plugged into the LAN not configured sending DHCP requests so our Old code would reboot the box. We were previously on code 5.0.5.0"

DHCP server is on windows 2003.

[Michael McNamara]

So when did this problem start?

It sounds from @jcny21's reply that there's probably something on the network that is making some odd DHCP discover requests. You might start by trying to see if there are any mis-configured devices out there or any devices that are constantly querying the DHCP server.