I have to follow up on this comment you made. I work for an ISP in
Indianapolis called IHETS. We have 7 cisco 7500 series routers on our
backbone. Wre just spent a chunck of money to upgrade the RAM on them to
64Meg. If yoiu are saying that regular SIMMS work in Cicso routers, then I'll
shoot myself in the foot. I'd like to know if you have used this method and
how well it works out in the field. Does latency increase with *unqualified*
Cisco memory, or is the *unqualified* *qualified* Cisco ram stuff just a big
ruse? Thanks for your input.
I have to follow up on this comment you made. I work for an ISP in
Indianapolis called IHETS. We have 7 cisco 7500 series routers on our
backbone. Wre just spent a chunck of money to upgrade the RAM on them to
64Meg. If yoiu are saying that regular SIMMS work in Cicso routers, then I'll
shoot myself in the foot. I'd like to know if you have used this method and
Ok, get some bullets.
how well it works out in the field. Does latency increase with *unqualified*
Cisco memory, or is the *unqualified* *qualified* Cisco ram stuff just a big
ruse? Thanks for your input.
Na, ram is ram. It is just like FDDI cables. I spent $250 on FDDI cables,
and then found out that I can get the exact same cable for $50 each.
Nathan Stratton CEO, NetRail, Inc. Tracking the future today!
==>> how well it works out in the field. Does latency increase with
==>*unqualified* > Cisco memory, or is the *unqualified* *qualified* Cisco
==>ram stuff just a big > ruse? Thanks for your input.
==>
==>Na, ram is ram. It is just like FDDI cables. I spent $250 on FDDI cables,
==>and then found out that I can get the exact same cable for $50 each.
There is a list of third-party RAM that Cisco approves, and this list is
available on CCO *somewhere*. I don't remember where, though; Paul
Ferguson is really good at remembering where this stuff is, though.
The reason you should at least follow Cisco's recommendation for RAM is to
keep your router at least running sanely. I have seen WAY TOO MANY
machines (including routers) do really weird stuff because the operator(s)
used cheap re-labeled RAM from Fry's or similar. Usually, it's in the
form of weird segfaults in UNIX, or software-forced-reloads in the case of
routers.