Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

SA520 Firmware 2.1.71 RIP routing table bug found...

Gang,

Can someone confirm this for me?

I'm updating the routing table on a SA520 from another cisco router, but I've been able to determine that the routes that the SA520 receives will NOT age out of the table.

I have RIP on the 520 setup as "In-only,"  version "RIP-2M."   It receives routes from the other router and adds them to the table.

So I have a route table entry of:

10.0.1.0   192.168.0.1    255.255.255.0 UG    2      0        0 bdg1

I then take that route out of the Sending router, and then I get this in the SA520's table:

10.0.1.0   192.168.0.1    255.255.255.0 UG    2       0        0 bdg1

10.0.1.0   192.168.0.1    255.255.255.0 UG    16     0        0 bdg1

The first entry should age out of the table, but it does not.  I've waited 10 minutes to see if it would.  It doesn't.  The entry with the metric of 16 should tell the router that this particular subnet is no longer reachable, but since the original table entry is not removed, it still thinks that the subnet is good.

Even after I bring up the 10.0.1.0 subnet again on the originating router....  BOTH entries stay in the SA520's table.  I must REBOOT it to clear the old routes.  There's no adjustment of the RIP timers on the SA520 either.  The documentation doesn't mention them at all.

I would downgrade to firmware 2.1.51, but the config files are not compatible. 

Could someone running the same firmware comfirm this bug, and perhaps prod the Cisco folks to get correct it?

Everyone's tags (5)
11 REPLIES
Silver

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

Larry,

i just pull one SA540 and SA520 out into the lab and simulated what you described and did get the same routing information as you did but after 4 minutes my routes disappear from my routing table, of course i had to hit the back button and go back to display my routing table but routes deleted after 4 minutes/240 seconds as said in the administration guide  Both SA500 devices running 2.1.71

Do you have a topology of your network?

Jasbryan

New Member

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

Jas,

The incoming RIP traffic is from a 2901 voice router, and on my unit, it's still displaying routes with both metrics like so:

10.0.1.0       192.168.0.1    255.255.255.0   UG    2      0        0 bdg1

10.0.1.0       192.168.0.1    255.255.255.0   UG    16     0        0 bdg1

192.168.20.0    192.168.0.1    255.255.255.0   UG    2      0        0 bdg1

192.168.20.0    192.168.0.1    255.255.255.0   UG    16     0        0 bdg1

the code on the 2901 is:

router rip

version 2

redistribute eigrp 1001

default-metric 1

no auto-summary

The 2901 is feeding a number of other subnets to the SA520 via EIGRP redistribution.  The EIGRP sends routes of other internal networks via MPLS.  If our MPLS Links go down, the EIGRP updates stop, and I'm trying to setup VPN tunnels.

I tried to change the default-metric to different numbers, and it works, but it keeps adding MORE routes to the SA520's table with different metrics.  If I set the default-metric as 2 I get a table full of routes at metric 3, set at 4, I get another set with metrics of 5.  The SA520 keeps all of the old routes with metrics of 2 and 4.  This table will grow every time I change the metric.  NONE of the entries seem to age out, and I left it overnight with the bad entries there....and they're still there in the morning.  They don't go away.

My gut says that something isn't syncing properly, and I need more time to test with, but that means taking our business network off-line, after hours. 

To make sure that I'm not doing something wrong, I did setup a mock GNS3 setup with a couple of 2961 routers and configuring the RIP setup very similar.  It works, but it's emulating a REAL Cisco Router, not a SA520.

Silver

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

how are the physically connected and ill try to test again. As i don't have a 2911 router ill still have to test from two SA500's

Jasbryan

New Member

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

Jas,

Take a generic 100M switch and plug both into the SWITCH.  My 2901 and SA520 are hanging off the switch.

Our MPLS router is also connected to that switch, but it only talks to the 2901....then the 2901 passes that infomration to the SA520.  The SA520 doesn't know or care about the other (MPLS) router.

I know, it's not the best arrangement, but what I'm doing with it now was not in the original design.

Silver

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

Larry,

So coming off the switch is plugged into WAN ports of each router (SA500 and Cisco 1900)

Jasbryan

New Member

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

Sorry Jas,  I wasn't clear enough.

The SA520 WAN port is connected to our broadband provider.  It is a static address.  No bearing on this issue.

SA520 LAN Port 1 is connected to SW1 Port1

Cisco 2901 G0/0 is also connected to SW1 Port 2

MPLS Router F0/0 is connected to SW1 Port 3.

MPLS feeds EIGRP routes to 2901.

2901 redis the EIGRP routes to the SA520 via RIP.

All outbound Inet traffic passes through SA520 NAT'ed.

If MPLS link goes down, the routes on the far side of the MPLS fall off the EIGRP.  Then it should fall off of the SA520, too.  They don't.

New Member

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

Well, I took some time this evening to do a factory reset and I was VERY disappointed that all THREE of my backup configs would NOT restore....due to a checksum error!!!!!!!  I did not edit nor open the files.

So an hour and a half wasted plugging in data by hand and rebuilding the configuration from scratch.

BEWARE!!!!!!!!!!!!!!!!!!!!   Backups are a WASTE of time with the 2.1.71 firmware.

I would really like to take a BFH to this box, and get an ASA.  It's a shame to have the name "Cisco" on it.   

The RIP bug is still present.  Routes do NOT age, so they stay in the table until a reboot.

Silver

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

Larry,

I haven't had time to set this backup in the lab as community forum is important it's doesn't take precedence over actual cases. So for faster resolution on this issue please give the Cisco Small Business Support Center a call and open a support case with next available engineer (1-866-606-1866) (All Support Numbers)

Jasbrayn 

New Member

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

Jas,

In process of getting this officially reported. 

It was just very frustrating last night, and I've spent too much time on this project.

Do DO appreciate your help and assistance.

New Member

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

The SOLUTION to this issue is:

Reload the 2.1.71 firmware AGAIN!

This unit had FW 1.1.65 and 2.1.71.  I believe that the two versions were corrupting the system.  Now that both firmware banks have the same software, the RIP tables are working as expected.

I do wish I could test this more, but I'm trying to 'test' equipment in a live network.    If someone still has access to the 1.1.x firmwares and a spare box....feel free to try it.

Silver

Re: SA520 Firmware 2.1.71 RIP routing table bug found...

Strange - 1.1.65 was an old firmware release

Jasbryan

1636
Views
0
Helpful
11
Replies
CreatePlease to create content