 |
| Flowers of Cassia fistula was blooming together in southern Taiwan starting from mid-May. This photo was taken around this location in Baihe District of Tainan City, Taiwan. |
An interesting question might be asked. Does Cisco hardware keep track of system uptime even upon supervisor/CPU failover events? And how to display the system uptime, in addition to individual supervisor/CPU uptime?
I spent some time and I summarize my findings in this post.
[Cisco NX-OS on Nexus 7000 and MDS 9500]
Basically the command “show system uptime” is for NX-OS to display system uptime for both Nexus 7000 and MDS 9500
For Cisco MDS 9500, the official web site gives me an explaining example.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/4_1/configuration/guides/cli_4_1/clibook/ha.html#pgfId-1120592
switch# show system uptimeSystem start time: Fri Aug 27 09:00:02 2004
System uptime: 1546 days, 2 hours, 59 minutes, 9 seconds
Kernel uptime: 117 days, 1 hours, 22 minutes, 40 seconds
Active supervisor uptime: 117 days, 0 hours, 30 minutes, 32 seconds
For Nexus 7000, the following link tell us “show system uptime” is a legal command for Nexus 7000.
http://docwiki.cisco.com/wiki/Cisco_Nexus_7000_Series_NX-OS_Troubleshooting_Guide_--_Troubleshooting_Installs,_Upgrades,_and_Reboots
However, the screen capture is not helpful for me to clarify system uptime and supervisor uptime.
I found another more meaningful example here.
http://ccie5851.blogspot.tw/2011/01/joys-of-issu-on-nexus-7000.html
cmhlab-dc2-sw2-otv1# show system uptimeSystem start time: Tue Oct 26 19:46:38 2010System uptime: 89 days, 6 hours, 56 minutes, 26 secondsKernel uptime: 0 days, 0 hours, 29 minutes, 16 secondsActive supervisor uptime: 0 days, 0 hours, 19 minutes, 56 secondscmhlab-dc2-sw2-otv1#
[Cisco IOS on Catalyst 6500 and Catalyst 4500]
The command for Cisco IOS platforms, such as Catalyst 6500 and 4500, is “show redundancy”.
http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/71585-cat6k-red-supeng-swimg-upg.html
Router#show redundancy Redundant System Information : ------------------------------ Available system uptime = 34 minutes Switchovers system experienced = 1 Standby failures = 0 Last switchover reason = unsupported Hardware Mode = Duplex Configured Redundancy Mode = Stateful SwitchOver - SSO Operating Redundancy Mode = Stateful SwitchOver - SSO !--- This verifies that software has set the redundancy mode !--- back to SSO after the software upgrade. Maintenance Mode = Disabled Communications = Up Current Processor Information : ------------------------------- Active Location = slot 6 Current Software state = ACTIVE Uptime in current state = 4 minutes Image Version = Cisco Internetwork Operating System Software IOS (tm) MSFC2A Software (C6MSFC2A-IPBASE_WAN-M), Version 12.2(18)SXF6, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2006 by cisco Systems, Inc. Compiled Mon 18-Sep-06 17:17 by tinhuang BOOT = bootflash:c6msfc2a-ipbase_wan-mz.122-18.SXF6.bin,1; CONFIG_FILE = BOOTLDR = Configuration register = 0x2102 Peer Processor Information : ---------------------------- Standby Location = slot 5 Current Software state = STANDBY HOT Uptime in current state = 3 minutes Image Version = Cisco Internetwork Operating System Software IOS (tm) MSFC2A Software (C6MSFC2A-IPBASE_WAN-M), Version 12.2(18)SXF6, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2006 by cisco Systems, Inc. Compiled Mon 18-Sep-06 17:17 by tinhuang BOOT = bootflash:c6msfc2a-ipbase_wan-mz.122-18.SXF6.bin,1; CONFIG_FILE = BOOTLDR = Configuration register = 0x2102
This is for Catalyst 4500. However, the screen capture is not good.
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/12-2/25ew/configuration/guide/conf/RPR.html
[Cisco IOS XR, ASR 9000]
The command for ASR 9000 is again “show redundancy”.
http://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k_r4-2/rommon/configuration/guide/b_rommon_cg_42asr9k/b_rommon_cg_42asr9k_chapter_0101.html#ID2119
RP/0/RSP1/CPU0:router# show redundancy Redundancy information for node 0/RSP1/CPU0: ========================================== Node 0/RSP1/CPU0 is in ACTIVE role Partner node (0/RSP0/CPU0) is in STANDBY role Standby node in 0/RSP0/CPU0 is ready Standby node in 0/RSP0/CPU0 is NSR-ready Reload and boot info ---------------------- A9K-RSP-4G-HDD reloaded Thu Dec 11 14:50:47 2008: 2 hours, 41 minutes ago Active node booted Thu Dec 11 17:15:15 2008: 16 minutes ago Last switch-over Thu Dec 11 17:19:29 2008: 12 minutes ago Standby node boot Thu Dec 11 17:28:56 2008: 3 minutes ago Standby node last went not ready Thu Dec 11 17:30:02 2008: 2 minutes ago Standby node last went ready Thu Dec 11 17:31:02 2008: 1 minute ago There has been 1 switch-over since reload RP/0/RSP1/CPU0:router#
One more thing…
I also found one example for Cisco ASA.
[Cisco ASA Cluster]
For Cisco ASA, the hardware itself does not provide system-wide redundancy. It only provides cluster-wide (pair-wide) redundancy. Here is the “show version” command output example of Cisco ASA, which explains Cisco ASA also keeps track of cluster-wide uptime in addition to single hardware box uptime.
https://supportforums.cisco.com/discussion/11291816/failover-cluster-uptime
asa-firewall> sh ver
Cisco Adaptive Security Appliance Software Version 8.2(1)
Compiled on Tue 05-May-09 22:45 by builders
System image file is "disk0:/asa821-k8.bin"
Config file at boot was "startup-config"
asa-firewall up 2 days 22 hoursfailover cluster up 1 year 79 daysHardware: ASA5550, 4096 MB RAM, CPU Pentium 4 3000 MHz
Why do I have to write down this post? If I can capture the system-wide uptime (or cluster-wide uptime) in addition to single hardware uptime, I have something much more persuading to buying decision makers because the traffic is not stopped at all right here at this system (or cluster) for such a long time.
By the way, what is the “longest” system or cluster uptime you have ever seen before? Please share your experiences with me here at the comments area!
Thank you so much!
No comments:
Post a Comment
Tip: you can also anonymously comment here.