SNMP UPTIME
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2008 03:00 AM - edited 03-05-2019 10:38 PM
Hi,
I've a Cisco 6500 with this system image:
c6sup22-jsv-mz.121-19.E1
The uptime for this switch is 1 year, 23 weeks, 13 hours, 32 minutes,but the sysUpTime is 29 Days.
"Cisco Internetwork Operating System Software
IOS (tm) c6sup2_rp Software (c6sup2_rp-JSV-M), Version 12.1(19)E1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc2)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Sun 29-Jun-03 17:06 by nmasa
Image text-base: 0x40008C00, data-base: 0x41B0C000
ROM: System Bootstrap, Version 12.2(17r)S1, RELEASE SOFTWARE (fc1)
BOOTLDR: c6sup2_rp Software (c6sup2_rp-JSV-M), Version 12.1(19)E1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc2)
OPIM1SWA250 uptime is 1 year, 23 weeks, 13 hours, 32 minutes
Time since OPIM1SWA250 switched to active is 1 year, 23 weeks, 13 hours, 34 minutes
System returned to ROM by power-on (SP by power-on)
System restarted at 19:43:55 UTC Wed Nov 8 2006
System image file is "sup-bootflash:c6sup22-jsv-mz.121-19.E1"
]# snmpwalk -Os -c rcdatasocr -v 2c 172.19.40.250 1.3.6.1.2.1.1
sysDescr.0 = STRING: Cisco Internetwork Operating System Software
IOS (tm) c6sup2_rp Software (c6sup2_rp-JSV-M), Version 12.1(19)E1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc2)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Sun
sysObjectID.0 = OID: enterprises.9.1.283
sysUpTime.0 = Timeticks: (254716234) 29 days, 11:32:42.34
sysContact.0 = STRING:
sysName.0 = STRING: OPIM1SWA250
sysLocation.0 = STRING:
sysServices.0 = INTEGER: 78
sysORLastChange.0 = Timeticks: (0) 0:00:00.00
May be a limitation of Timeticks and the counters reset to 0 or a IOS BUG(CSCeb60961)..
Thanks
- Labels:
-
Other Switching