cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
539
Views
0
Helpful
4
Replies

7206 VXR Loses routes

mtnuga
Level 1
Level 1

Hi

I am experiecing a problem with my 7206 VXR, Below is the error message i get..

Oct 27 02:14:28.257 gmt: RIB: failed to allocate memory. Could lead to missing route updates in applications.

Also attached is a sh ver

isco Internetwork Operating System Software

IOS (tm) 7200 Software (C7200-IS-M), Version 12.1(14)E3, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

TAC Support: http://www.cisco.com/tac

Copyright (c) 1986-2003 by cisco Systems, Inc.

Compiled Wed 26-Mar-03 22:37 by hqluong

Image text-base: 0x60008C08, data-base: 0x612B0000

ROM: System Bootstrap, Version 12.2(4r)B2, RELEASE SOFTWARE (fc2)

BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.1(8a)E, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

MTN_Customer_Access2 uptime is 16 weeks, 16 hours, 17 minutes

System returned to ROM by reload at 07:36:16 UTC Sun Jul 6 2003

System image file is "disk0:c7200-is-mz.121-14.E3.bin"

cisco 7206VXR (NPE400) processor (revision A) with 114688K/16384K bytes of memory.

Processor board ID 29741534

R7000 CPU at 350Mhz, Implementation 39, Rev 3.3, 256KB L2, 4096KB L3 Cache

6 slot VXR midplane, Version 2.7

Last reset from power-on

Bridging software.

X.25 software, Version 3.0.0.

2 FastEthernet/IEEE 802.3 interface(s)

32 Serial network interface(s)

125K bytes of non-volatile configuration memory.

46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).

8192K bytes of Flash internal SIMM (Sector size 256K).

Configuration register is 0x2102

any help will be appreciated

MK

4 Replies 4

t.baranski
Level 4
Level 4

I would assume you're either out of memory or that the remaining memory is so fragmented that it's essentially unusable. Is this router receiving one or more full BGP tables from peers?

Hi

Yes, you are right that my memory is fragmented and yes i am receiving full BGP routes from peers. Can you advise how should change this?

Thank you

MK

A reboot may fix the fragmentation temporarily, but the better solutions are a) getting more memory, or b) reducing the number of BGP routes that you receive from peers.

Hello,

I am not sure if more memory helps. I would rather try to find out the source for the fragmented memory. If you execute the show proc mem command, check for processes with a high number of allocs. If you execute the show mem all and the show mem sum command, check if these processes actually have a lot of fragmented memory blocks assigned in various locations. Are you actually running something like policy-based routing ?

Regards,

Georg

Review Cisco Networking for a $25 gift card