BladeSystem - General
1748112 Members
3454 Online
108758 Solutions
New Discussion

Virtual Connect SystemLog Architecture

 
chuckk281
Trusted Contributor

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?