We have 2 6500/SUP2 running old 12.1(26)E9 and having almost 1MB of
uncompressed config and 14500 lines:
6500#sh start
Using 178291 out of 391160 bytes, uncompressed size = 976219 bytes
"sh run" takes about 10 sec and "sh start" only 1 sec.
On the other hand "wr mem" takes about 80 sec (compression adds time too).
I don't know if the following make any difference in our case:
6500#sh vlan sum
Number of existing VLANs : 40
Number of existing VTP VLANs : 40
Number of existing extended VLANs : 0
6500#sh idb | i IDBs
Maximum number of IDBs 5000
440 SW IDBs allocated (2656 bytes each)
501 HW IDBs allocated (6744 bytes each)
--
Tassos
Phil Mayers wrote on 30/9/2008 12:53 μμ:
Jason Koh wrote:
Hi there.
1. The time taken for show run is about 7-10 minutes long
2. #sh start
Using 67275 out of 391160 bytes
Can't really tell how much lines are there. It's a lot.
For comparison, we've got:
Using 220185 out of 1964024 bytes
...and ~8300 lines in the config and an nvgen (sh run/wr mem/copy run
start) takes ~70 seconds.
However, we're on a sup720
3. ROM: System Bootstrap, Version 12.1(11r)E1, RELEASE SOFTWARE (fc1)
BOOTLDR: c6sup2_rp Software (c6sup2_rp-PS-M), Version 12.2(18)SXD4,
RELEASE
SOFTWARE (fc1)
System image file is "sup-bootflash:c6k222-ps-mz.122-18.SXD4.bin"
You should probably consider upgrading that, but I have no idea if it'll
correct the problem.
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
