HP 234664-002 - ProLiant - ML330T02 Техническая белая книга - Страница 8

Просмотреть онлайн или скачать pdf Техническая белая книга для Настольный компьютер HP 234664-002 - ProLiant - ML330T02. HP 234664-002 - ProLiant - ML330T02 12 страниц. Visualization and acceleration in hp proliant servers
Также для HP 234664-002 - ProLiant - ML330T02: Часто задаваемые вопросы (4 страниц), Руководство по внедрению (35 страниц), Обновление прошивки (9 страниц), Обзор (20 страниц), Руководство по внедрению (26 страниц), Вводное пособие (22 страниц), Руководство по устранению неполадок (18 страниц), Руководство по внедрению (11 страниц), Руководство по установке (2 страниц), Руководство по конфигурации (2 страниц), Вводное пособие (19 страниц), Руководство по обновлению (9 страниц), Руководство по обновлению (16 страниц), Вводное пособие (10 страниц), Руководство по установке (15 страниц), Краткое описание технологии (9 страниц)

Печатать страницу
HP 234664-002 - ProLiant - ML330T02 Техническая белая книга
Collecting and
Updating Insight
Diagnostics Online
Edition Information
Accessing and
Viewing
Information
Insight Diagnostics Online Edition provides flexibility in the way that the information is
captured. It provides maximum assurance that the information available reflects the
current state of the server and that the audit trail clearly reflects the stages of changes
that have occurred. Just as several options are available for viewing and generating a
report, multiple methods are used for collecting information.
• Upon Server Reboot—When set for periodic capture, Insight Diagnostics Online
Edition automatically captures a snapshot of information each time the server is
rebooted. After Insight Diagnostics Online Edition is loaded on the server, this capture
process happens without administrator intervention. Since most significant
configuration changes require a server reboot to be recognized, these capture points
help provide maximum coverage for detecting changes. If a significant change is
recognized, it will be check pointed and stored. Any configuration differences will
also be recorded.
• Scheduled Intervals—When set for periodic capture, Insight Diagnostics Online
Edition also provides a mechanism to automatically capture a configuration snapshot
at a regularly scheduled time. While the default setting for this feature is once per
week, the interval is configurable from the browser-based user interface or by using
command line parameters. The interval can be adjusted to occur as often as once a
day. This scheduled interval feature allows the configuration audit trail to capture
views of the system not only upon reboot, but also capture and identify differences (as
well as significant configuration changes) during regular operation of the server. The
scheduled interval feature is important in capturing system difference information,
such as software changes made without a required reboot.
• User Initiated—Insight Diagnostics Online Edition allows the administrator to
initiate a new snapshot on-demand. While this feature can be used when the Insight
Diagnostics Online Edition is configured for periodic capture, it is particularly useful
for one-time collection.
All of the update options help to ensure that the latest information and change history is
always recorded and available when needed.
The information the utility gathers can be accessed in the following three ways.
•
Locally at the host server console
•
Remotely or locally from a browser
•
Remotely or locally using the RILOE
The available options allow the information to be parsed in several ways to provide
different types and levels of information. The system administrator can request viewing of
the active sessions and, because multiple configuration snapshots are stored, a report
that automatically compares any two snapshots. In completing the comparison, the
Insight Diagnostics Online Edition automatically matches the snapshots and highlights
any differences that exist between them. This is a useful feature for enabling clear audit
trail tracking. It allows the system administrator or service provider to identify the history
of events and the order and point at which specific changes were made which provides
significant assistance in identifying the source of server problems.