- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect SystemLog Architecture
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2012 06:42 AM
10-31-2012 06:42 AM
Virtual Connect SystemLog Architecture
Chris had some quesitons regarding the VC Syslog architecture:
*****************
1) What is the max size of the systemlog?
2) Is the systemlog FIFO type of logging?
3) Can the systemlog be cleared? Doesn’t seem like it.
4) Any other info would be appreciated.
***************
Jim had some info:
***************
1. The approximate maximum size is 256Kb.
2. Events are logged with the most recent event displayed at the end of the list. Use the scroll bar on the right of the screen to scroll through the list if it is longer than the display box. When the log reaches maximum capacity, the oldest logged event is automatically deleted as new events are added.
3. The system log cannot be reset, or cleared.
4. Other info
- The system log is persistent and survives a reboot.
- Events are logged with the most recent event displayed at the end of the list
- The VCM contains persistent and non persistent log files. If a customer has a VC issue, which they solve by power-off/power-on the VC module in interconnect bay 1 and then power-off/power-on the VC module in interconnect bay 2 most of the data in the VC support file is lost. The power cycle wipes the non persistent log files and it’s almost impossible to do a Root cause analysis to determine what went wrong
******************
Other comments or questions?