Cisco Blogs

Beat this uptime

July 24, 2008 - 17 Comments

We had an interesting thread unfold on an internal list, which I thought I would open up to our readership. Someone was foraging around the network and came across some impressive server uptime (all server names changed to keep infosec happy):

server-x% uptime7:13pm up 500 day(s), 3:17, 53 users, load average: 0.08, 0.11, 0.11

to which someone else countered with

server-y$ uptime23:45:15 up 700 days, 8:31, 3 users, load average: 0.00, 0.00, 0.00

The irony behind this server is that it has outlasted the business unit it apparently supported.
However, the winner so far is:

WS-C5000 Software, Version McpSW: 3.1(2) NmpSW: 3.1(2a)Copyright (c) 1995-1998 by Cisco SystemsNMP S/W compiled on Feb 20 1998, 18:56:57MCP S/W compiled on Feb 20 1998, 19:05:51System Bootstrap Version: 2.4(1)Hardware Version: 2.1 Model: WS-C5000 Serial #: 007584271…Uptime is 2618 days, 9 hours, 11 minutes

7+ years–guess there is something to that investment protection thing after all.
So what is the best system uptime in your data center? The response with the best uptime gets a Cisco fleece.

In an effort to keep conversations fresh, Cisco Blogs closes comments after 60 days. Please visit the Cisco Blogs hub page for the latest content.


  1. Not sure if I saw anything that could beat this uptime. The other five “Cisco LS1010” we own have spontaneously booted on their on. Not sure how much longer this one will hang on and we are in the process of moving the last production off this segment. My local Cisco SE can verify this is authentic. ATM3#sh ver Cisco Internetwork Operating System Software IOS (tm) LS1010 WA4-5 Software (LS1010-WP-M), Version 12.0(8), RELEASE SOFTWARE (fc1) Copyright (c) 1986-1999 by cisco Systems, Inc. Compiled Tue 30-Nov-99 13:57 by kpma Image text-base: 0x60010930, data-base: 0x6068E000 ROM: System Bootstrap, Version 11.2(1.4.WA3.0) [integ 1.4.WA3.0], RELEASE SOFTWARE ATM3 uptime is 10 years, 33 weeks, 1 day, 19 hours, 26 minutes System restarted by power-on at 16:15:37 CST Wed Feb 23 2000 Running default software cisco LS1010 (R4600) processor with 65536K bytes of memory. R4700 processor, Implementation 33, Revision 1.0 Last reset from power-on 1 Ethernet/IEEE 802.3 interface(s) 23 ATM network interface(s) 123K bytes of non-volatile configuration memory. 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x2102

  2. An old thread, but thought I would post something I just found on a 2900 switch in our data center...Cisco Internetwork Operating System Software IOS (tm) C2900XL Software (C2900XL-H2-M), Version 12.0(5.1)XP, MAINTENANCE INTERIM SOFTWARECopyright (c) 1986-1999 by cisco Systems, Inc.Compiled Fri 10-Dec-99 11:00 by cchangImage text-base: 0x00003000, data-base: 0x00282880ROM: Bootstrap program is C2900XL boot loaderXXX-XX-XXX uptime is 9 years, 46 weeks, 2 days, 20 hours, 11 minutesSystem returned to ROM by power-onSystem image file is flash:c2900XL-h2-mz-120.5.1-XP.bin"""^0^1^^^0^0 22624^6888^Peter Morford^^^^2010-04-23 22:11:29^2010-04-23 22:11:29^I had a company in the Philippines and decided to have a reward system for an ideas to improve production. Each idea was only small but each step made a better product overall. Funily enough we were making replica models of americas cup ships.^0^1^^^0^0 22625^7506^USA Headline News^^^^2010-03-26 22:33:23^2010-03-26 22:33:23^WE LOVE CISCO.Thanks for useful and meaningful article. yes, i agree...., DKIM advance is absolutely staggering and there will be a bang in the road.Goerge & Family, from New York & Jakarta.^0^1^^^0^0 28214^8885^James Vahl^^^^2010-05-07 20:50:42^2010-05-07 20:50:42^Watched the video on the TelePresence. Great job Cisco! You showed in the video of the classroom teaching environment. Think of the potential on foreign language teaching. Very Cool!^0^1^^^0^0 27977^8850^joydeep^^^^2010-05-07 21:05:06^2010-05-07 21:05:06^vow..that's really superior technology..I am looking forward to it as its very beneficial for companies on the whole.^0^1^^^0^0 22627^8612^ausbildungpilot^^^^2010-03-08 15:32:09^2010-03-08 15:32:09^This was kind a great video regarding to the speaker Dave.^0^1^^^0^0 22628^7305^Free Bets Online^^^^2010-03-08 18:48:04^2010-03-08 18:48:04^Superbe article, vraiment simple et utile. Bravo pour sa mise en ligne. C’est ce genre d’information que le public (et moi en particulier) recherche.^0^1^^^0^0 22745^8628^Rafal Los^^^^2010-03-10 04:19:30^2010-03-10 04:19:30^"The mass increase in performance and throughput is impressive - but the problem in my opinion is not at the core"". I continue to see bottlenecks from the distribution edge to the end-users...I'm still waiting for faster broadband-type access to the home, or on the go (via WiMax), and I don't know that this solves the whole problem."

  3. I can't beat 7+ years, or the 10+ years above, but I did just recently retire two Catalyst 3550-48 switches that showed the following on their last show ver"" output:TICNTC013550S02 uptime is 6 years, 3 weeks, 6 days, 22 minutesTICNTC013550S01 uptime is 6 years, 3 weeks, 5 days, 23 hours, 51 minutesThese were in a UPS-backed wiring closet installed in December 2003 in support of a VoIP deployment. I checked my trouble ticket logs and found that no tickets were ever logged re: these switches, either. As far as I can tell they're fully functional (no bad ports, etc)."

  4. Lotta love 11.2, token-tastic. 10 years and counting....Cisco Internetwork Operating System Software IOS (tm) 4500 Software (C4500-IS-M), Version 11.2(17), RELEASE SOFTWARE (fc1)Copyright (c) 1986-1999 by cisco Systems, Inc.Compiled Mon 04-Jan-99 18:18 by ashahImage text-base: 0x600088A0, data-base: 0x60604000 ROM: System Bootstrap, Version 5.2(7) [rchiao 7], RELEASE SOFTWARE (fc1)BOOTFLASH: 4500 Bootstrap Software (C4500-XBOOT), Version 10.2(7), RELEASE SOFTWARE (fc1) XXXXXXXX uptime is 10 years, 6 weeks, 7 hours, 33 minutesSystem restarted by reload at 02:44:34 AEST Fri Aug 6 1999System image file is flash:c4500-is-mz.112-17"", booted via flash cisco 4700 (R4K) processor (revision B) with 32768K/16384K bytes of memory.Processor board ID 02169217R4600 processor, Implementation 32, Revision 2.0 (Level 2 Cache)G.703/E1 software, Version 1.0.Bridging software.X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.2 Token Ring/IEEE 802.5 interface(s)128K bytes of non-volatile configuration memory.8192K bytes of processor board System flash (Read/Write)4096K bytes of processor board Boot flash (Read/Write) Configuration register is 0x2102"

  5. kgraham:While this thread was never meant to be an exhaustive study of operational best practices, that being said, I only asked folks for a snippet of information, so I am not sure its all that fair to extrapolate that into an overall discussion of operational rigor. That being said, you do bring up a good point. There is an interesting dichotomy at work. While we demand systems to never go down, we also expect them to be dynamic and adapt to changing needs, so a system (server, switch, whatever) can no longer be snapshot of the day it was last booted.As Timothy pointed out earlier, this is one of the reasons IBM (or DEC in their day) were successful--bulletproof hardware with an OS that supports this dichotomy. As I mentioned in the initial post, the N7K follows a similar path.I have to admit, the security angle is not one I had paid much attention to, but you bring up good points. I guess the current hubbub over DNS vulnerabilities is an example of that.

  6. >So what is the best system >uptime in your data center? Our old internet border gateway:IOS (tm) 7200 Software (C7200-IS-M), Version 12.2(15)T7, RELEASE SOFTWARE (fc2)TAC Support: (c) 1986-2003 by cisco Systems, Inc.ROM: System Bootstrap, Version 12.2(8r)B, RELEASE SOFTWARE (fc1)BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.2(4)BW, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) uptime is 4 years, 13 weeks, 5 hours, 29 minutesSystem returned to ROM by reload at 10:40:08 MET-DST Sun Jul 4 2004System restarted at 10:42:16 MET-DST Sun Jul 4 2004

  7. >So what is the best system >uptime in your data center? Our old Internet border gateway verIOS (tm) 7200 Software (C7200-IS-M), Version 12.2(15)T7, RELEASE SOFTWARE (fc2)TAC Support: (c) 1986-2003 by cisco Systems, Inc.ROM: System Bootstrap, Version 12.2(8r)B, RELEASE SOFTWARE (fc1)BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.2(4)BW, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) uptime is 4 years, 13 weeks, 5 hours, 18 minutesSystem returned to ROM by reload at 10:40:08 MET-DST Sun Jul 4 2004System restarted at 10:42:16 MET-DST Sun Jul 4 2004

  8. I don't think anyone can beat HP's OpenVMS - 10 years of uptime!

  9. kgraham:You make some great points--I do agree with your last point that these metrics will lose relevance as we start to measure different things with the evolution of infrastructure.In general, we find the hardest part of data center transformation is changing behavior--the same seems to be true in this area. What do you think would help change behavior and people's thinking?

  10. Omar -- yep, its just a reminder that in most of the common cases I'm familiar with, long uptime is indicative of sloppy, not adept, operational practices. There's the geeky how long can I keep this cool thing going"" and the conservative management ""don't touch it if its working"", both of which are widely accepted but harmful to long-term reliable operation. (I'll take a wild guess and say that the case of those two unix boxes and Cat5k cited originally hadn't seen a kernel patch or confirmed a clean startup process in a very long time.)As the IT industry starts to rediscover clustering and partitioning (I think I've heard the word ""virtualization"" mentioned a lot this time around), the definition of the ""uptime"" counter is again thoroughly misleading. Some of the earlier posts mentioned it as well, but if there's a slippery slope just past anything more than ""time since the running kernel initialized itself"". 12.2SX phrases it well, referring to ""continuous operation of this forwarding plane"" while not obfuscating what ""we all know"" is the uptime:test6504 uptime is 2 years, 5 weeks, 4 days, 19 hours, 37 minutesUptime for this control processor is 19 weeks, 6 days, 20 hours, 2 minutes...though replace this with a VSS or 3750 stack, or dive in further, especially with distributed components and virtualized layers, it really becomes impossible to express in a number (which really _is_ cool)."

  11. ...can be said about our Nexus 7000 — I would venture that they were both designed with similar principles in mind. Does 497 days sound familiar? That being said, the Law of Entropy is alive and well in the data center, so anytime you see numbers like these, the people that keep these systems up and running deserve a nod....Hardly. They deserve a serious questioning as to how they are properly managing their systems. This is usually the result of gross neglect, not solid administration policies. Huge uptimes are always a neat novelty, but novelties don't have a place in production. * Is the system configuration and functionality similar to currently available hardware? Can existing functionality be duplicated quickly and efficiently without compromising availability? * How will resources be allocated to repair the inevitable failure of this component? Have budgets been pre-allocated for a rapid replacement? * What methodology is used to identify ongoing security risks and vulnerabilities to the code being run? * Are current networking best practices applicable to this device? If you've made an exception, where else do you let standardization slip? * Are current security best practices even applicable? (I'm guessing you're not running ssh or snmpv3; what additional compensating infrastructure have you had to introduce to continue to facilitate this device? * With no current shipping product running this operating system, how much additional time has been allocated to ensure that staff are able to adequately manage it and ensure consistency with the rest of the environment? * Did you explicitly call out this device in your most recent security audits? If you omitted it because it was a nifty toy how many other nifty toys are you excluding?

  12. switch (enable) sho verWS-C5000 Software, Version McpSW: 3.2(2) NmpSW: 3.2(2)Copyright (c) 1995-1998 by Cisco SystemsNMP S/W compiled on Aug 7 1998, 11:43:53MCP S/W compiled on Aug 07 1998, 11:47:44System Bootstrap Version: 2.1Hardware Version: 2.0 Model: WS-C5000 Serial #: 004993573Module Ports Model Serial # Hw Fw Fw1 Sw------ ----- ---------- --------- ------ ------- ------- --------------------1 2 WS-X5009 004993573 2.0 2.1 2.1(4) 3.2(2)2 12 WS-X5213 001900817 1.2 1.4 3.2(2)3 12 WS-X5213 001900731 1.2 1.4 3.2(2)4 12 WS-X5213 001900917 1.2 1.4 3.2(2) DRAM FLASH NVRAMModule Total Used Free Total Used Free Total Used Free------ ------- ------- ------- ------- ------- ------- ----- ----- -----1 20480K 8316K 12164K 4096K 3584K 512K 256K 117K 139KUptime is 3450 days, 19 hours, 45 minutes

  13. Wow--Andrew is in the lead. His server had better uptime than my first marriage. But James is no slouch at almost six years.When I started this, I used the generic term system""--do you think its fair to put servers and networking gear in the same category? Is 5 years uptime for a server equally as impressive as 5 years for a switch?Omar"

  14. Timothy:I do not disagree with anything you said--heck, my first real job included managing DEC VAXes and FEPs. In fact, much of what you say about “a certain renowned type of business server” ( :) ) can be said about our Nexus 7000 -- I would venture that they were both designed with similar principles in mind.I agree that service uptime is the correct measure and that is dependent on system architecture and operations. Components will always fail--the goodness of the architecture and operations dictate how gracefully the system handles that.That being said, the Law of Entropy is alive and well in the data center, so anytime you see numbers like these, the people that keep these systems up and running deserve a nod....and perhaps some free clothing.

  15. It should be noted that the results of an uptime"" command represent an IT-centric view of the world, and a binary one that doesn't capture any performance slowdowns, for example. It's fun, but it's not a business-centric view, and we IT people are kidding ourselves if we think so.With that background, we have some customers running ""a certain renowned type of business server"" that:- upgrade hardware models and features- upgrade software (including operating systems and middleware, even whole database versions)- upgrade applications- reconfigure network connections- add storage- relocate and reconfigure data centersand otherwise change any server component you care to imagine, yet still deliver verified continuous business service that fully complies with all business performance requirements.And they've been doing that continously for over a decade.The poster upthread is correct. It's not a particular engineering challenge to install a gadget, leave it be, let it run at a low pulse, and get some years from an ""uptime"" command at the console. My refrigerator does that, and it's more sophisticated. :-) The real trick is to keep business activities humming continuously while everything possible changes. And it can be done with a combination of careful planning, exceptional technology, and competent people."

  16. % uptime 1:11pm up 3307 day(s), 23:42, 1 user, load average: 0.24, 0.17, 0.16%Over nine years, how about that? Last rebooted for y2k patching.

  17. >So what is the best system>uptime in your data center?I can't beat 7+ years. IOS (tm) RSP Software (RSP-DSV-M), Version 11.2(15)PRouter uptime is 5 years, 39 weeks, 5 days, 1 hour, 3 minutes