Guest

Preview Tool

Cisco Bug: CSCvs95140 - vEdge5K Rebooted and Failed to create reboot entry for the reboot time in the vManage UI Reboot Pane

Last Modified

May 18, 2020

Products (1)

  • Cisco vEdge Router

Known Affected Releases

18.4.4

Description (partial)

Symptom:
The Reboot pane does not display the reboot of vEdge5K that occurred as a result of power-cycling a device.

System uptime: reflects the time of the reboot.
"show reboot history" command does not record the reboot time and reason.

COGINPUNICCVE1# show system status

Viptela (tm) vedge Operating System Software
Copyright (c) 2013-2017 by Viptela, Inc.
Controller Compatibility: 
Version: 18.4.302
Build: 56


System logging to host  is disabled
System logging to disk is enabled

System state:            GREEN. All daemons up
System FIPS state:       Enabled

Last reboot:             Unknown. 
CPU-reported reboot:     Unknown
Boot loader version:     5.11  [VIP5000.P01]

System uptime:           0 days 08 hrs 37 min 07 sec
Current time:            Mon Jan 13 00:07:09 +09 2020

Load average:            1 minute: 26.34, 5 minutes: 26.32, 15 minutes: 26.32
Processes:               349 total
CPU allocation:          28 total,   2 control,   26 data
CPU states:              0.53% user,   2.11% system,   97.32% idle
Memory usage:            32659444K total,    9674376K used,   22203384K free
                         86636K buffers,  695048K cache

Disk usage:              Filesystem      Size   Used  Avail   Use %  Mounted on
                         /dev/root       115644M  622M  109105M   1%   /


Personality:             vedge
Model name:              vedge-5000
Services:                None
vManaged:                false
Commit pending:          false
Configuration template:  None

COGINPUNICCVE1# 
COGINPUNICCVE1# 
COGINPUNICCVE1# sh clock
Mon Jan 13 00:07:21 +09 2020
COGINPUNICCVE1# 
COGINPUNICCVE1# 
COGINPUNICCVE1# 
COGINPUNICCVE1# 
COGINPUNICCVE1# show reboot history 

REBOOT DATE TIME           REBOOT REASON                          
------------------------------------------------------------------
2019-07-06T04:57:03+00:00  Initiated by user - activate 18.3.5    
2019-07-16T02:36:34+00:00  Initiated by user - activate 18.3.7    
2019-11-14T05:06:44+00:00  Initiated by user - activate 18.4.302

COGINPUNICCVE1# file show /var/log/tmplog/vdebug | include reboot

local7.debug: Jan 13 00:03:50 COGINPUNICCVE1 SYSMGR[470]: get_reboot_type[2880]: %SYSMGR_DBG_MAIN-1: reboot reason fetch failed!  
local7.debug: Jan 13 00:07:09 COGINPUNICCVE1 SYSMGR[470]: get_reboot_type[2880]: %SYSMGR_DBG_MAIN-1: reboot reason fetch failed!  
local7.debug: Jan 13 00:12:08 COGINPUNICCVE1 SYSMGR[470]: get_reboot_type[2880]: %SYSMGR_DBG_MAIN-1: reboot reason fetch failed!  
local7.debug: Jan 13 00:17:44 COGINPUNICCVE1 SYSMGR[470]: get_reboot_type[2880]: %SYSMGR_DBG_MAIN-1: reboot reason fetch failed!

Conditions:
Power cycle vEdge5K device.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.