- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- How to determine uptime intervals from gateway log...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How to determine uptime intervals from gateway logs?
Does anyone know if there is a way to extract the history of boot and shutdown dates and times from R80.10 vSEC instances?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here's what I see in my vSEC instances in AWS.
These gateways are set up in an autoscaling group and are created/destroyed using an Ansible playbook.
Your mileage may vary.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks,
Unfortunately, this will not work for me: I have number of vSECs non-AG that are periodically powered-up or down, but the management server itself suffered failure and was restored from the snapshot.
Hence this headache. Do you know if there are any events pertaining to power-up/down logged on the gateways themselves?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Every Unix-like system will have tell-tale signs of a reboot in /var/log/messages.
I believe by default we keep 5 days worth of messages.
And there's obviously the "uptime" command on each gateway which will tell you when it was last rebooted.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think what you are after might be in $FWDIR/log/fwd.elg, though...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
native will not work, as I am looking for about a month and a half of halt/powerup events.
Same issue is with "uptime", as it only shows the current value.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
fwd.elg does not contain the timestamps.
bummer...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unfortunatly the default values may not work to well. I recommend to:
- Increase the number of backup files and the size of each Messages file. sk36798
- If you get bogus input like missing RAID disks. Find the cause and make sure it is no longer send to the messages file when it is not needed.
And I strongly recommend to send your syslog to a central log server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you.
This is a one-off situation. I've build a bunch of AWS scenarios intended to be a proof of concept, but am now in a position to bill the client for the time spend on it.
Under normal circumstances, (i.e. in production), I'll be using an AWS Cloud Trail to have this info readily available. But since it was not configured from the get-go, I was trying to determine if there are CP specific logs with this data.
Alas, I'll have to estimate time spent on the project without supporting documentation, which I really dislike doing.
