up vote 0 down vote favorite
share [g+] share [fb]

I have a Summit extreme router and I've recently been receiving the following error:

<WARN:ESRP> edp.c 2892: PREMASTER-->Master : VLAN=Buyers1 [HIGHER Priority]
<WARN:ESRP> edp.c 2780: MASTER-->slave : VLAN=Buyers1 [Master PDU in master state]
<WARN:RIP > ripDeleteRt: SIOCDELRT (S_objLib_OBJ_TIMEOUT)

It's giving the first two errors on every vlan I have.

My entire network usually starts to lose connectivity. The only thing that has changed lately is someone put a NAT policy on our firewall to point to a 192.168.225.x IP address. Would this cause this error? Also, what does the error mean?

link|improve this question
89% accept rate
OK, I undid the NAT policy and still received the error message this morning. When I got here I shtudown the port for the new device that was added to the network. I'm going to wait all day to make sure I don't get the error message anymore, before I blame it on the device! Do you think assigning the device a legacy IP address caused these issues? – Jacob Sep 4 '09 at 16:50
feedback

2 Answers

up vote 0 down vote

According to: http://www.extremenetworks.com/libraries/services/ErrorMessageDecoderRev5.pdf

Failed to Delete RIP Route
ripExpireRt: SIOCDELRT (S_errno_EWOULDBLOCK)
Software Version
ExtremeWare 6.0 and later
Hardware Version
All
Explanation
The system failed to delete RIP route from the IP routing table. The RIP route to be deleted is not found
in the Kernel routing table.
Action
Verify whether the expired RIP route entry is present in the IP routing table.
If any invalid route entry is present, reboot the switch.
link|improve this answer
I read that last night. I undid the recent changes that were made to the network, and if this doesn't work I'm going to restart the router. Thanks. – Jacob Sep 4 '09 at 13:18
feedback
up vote 0 down vote accepted

These messages are because the master was failing over to the slave switch. The slave switch was sending out tons of TX errors. I'm thinking the slave was sending out bad ESRP request too, making the master look like it was failing. The slave was sending out so many TX errors and that's the reason my network was losing connectivity.

I unhooked the slave and disabled ESRP. I've recently replaced both of the switches and stress level/power usage is down.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.