12-09-2002 10:13 PM - edited 03-02-2019 03:29 AM
We have two Cat6509 switches in a fairly simple HSRP arrangement. They have identical configuarations. This worked well until about a week ago when I
started to get memory allocation errors for OSPF and virtual exec processes
on one of the MSFC's. We upgraded the DRAM to 128MB and MSFC is running ok EXCEPT the OSPF process is holding roughly 20MB memory. Every other 6500 on our network, (including its HSRP partner), in the same OSPF area are holding bewteen 2-4 MB for the OSPF process. Has anyone seen this type of behaviour before?
sh mod
Mod Slot Ports Module-Type Model Sub Status
--- ---- ----- ------------------------- ------------------- --- --------
1 1 2 1000BaseX Supervisor WS-X6K-SUP1A-2GE yes ok
15 1 1 Multilayer Switch Feature WS-F6K-MSFC no ok
2 2 8 1000BaseX Ethernet WS-X6408-GBIC no ok
3 3 8 1000BaseX Ethernet WS-X6408-GBIC no ok
4 4 8 1000BaseX Ethernet WS-X6408-GBIC no ok
5 5 8 1000BaseX Ethernet WS-X6408-GBIC no ok
sh ver
Cisco Internetwork Operating System Software
IOS (tm) MSFC Software (C6MSFC-JSV-M), Version 12.1(2)E, EARLY DEPLOYMENT
RELEAS
E SOFTWARE (fc1)
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Mon 19-Jun-00 19:15 by linda
Image text-base: 0x60008900, data-base: 0x614D0000
ROM: System Bootstrap, Version 12.0(3)XE, RELEASE SOFTWARE
BOOTFLASH: MSFC Software (C6MSFC-IS-M), Version 12.0(3)XE2, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
C2-C1-SW2-RT1 uptime is 1 week, 6 days, 4 hours, 58 minutes
System returned to ROM by power-on
Running default software
cisco Cat6k-MSFC (R5000) processor with 114688K/16384K bytes of memory.
Processor board ID SAD03413144
R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache
Last reset from power-on
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
33 Virtual Ethernet/IEEE 802.3 interface(s)
123K bytes of non-volatile configuration memory.
4096K bytes of packet SRAM memory.
16384K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x102
12-13-2002 09:40 PM
There might be a possibilty that when you checked the memory consumed the OSPF calculations might have been taking place and hence the memory utilization could have gone high. Is this consistent? However, Version 12.1(2) E has a bug with OSPF memory fragmentation.CSCdr70471. Check the Bug Toolkit for details. Not sure if this could be the reason for memory consumption. Try upgrading your IOS. Might resolve the issue. Let me know if this works!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide