3: BladeManager Web Access
3-6
AlterPath BladeManager Manual
Alarm Logs
The BladeManager not only stores each alarm in a database, but also
maintains a log for each alarm. There are two ways in which you can view
alarm logs:
•
From the Alarms List form
•
From the Logs form (
Logs
>
Data Buffer
)
Responding to an alarm
Since no two issues are exactly the same, you have several ways to respond to
an alarm depending on its nature and severity. A “typical” procedure for
responding to an alarm is as follows:
•
Accept the ticket or assignment.
•
Reassign the ticket or assignment to another user, and optionally add
notes about the ticket.
Once assigned, the user working on the ticket can perform any of the
following procedures to resolve the alarm or complete the ticket:
•
View Blade Log and other related logs.
•
Edit information ticket by changing the status and adding notes.
•
Connect to the blade.
•
Run a console session.
•
If problem is fixed, change the alarm status and close the ticket.
•
Re-assign the ticket to another user.
Alarm List Form
When you first log in to the BladeManager as a regular user or select Alarms
from the menu, the Alarm List form is the first form that you will see. Use this
form to view the list of alarms, to connect to a blade, and to view blade logs.
Summary of Contents for AlterPath BladeManager
Page 10: ...Table of Contents VIII AlterPath BladeManager Manual...
Page 16: ...Before You Begin vi AlterPath BladeManager Manual...
Page 24: ...1 Introduction 1 8 AlterPath BladeManager Manual...
Page 54: ...2 BladeManager Installation 2 30 AlterPath BladeManager Manual...
Page 162: ...4 BladeManager Web Administration 4 80 AlterPath BladeManager Manual...
Page 186: ...5 Advanced Configuration 5 24 Alterpath BladeManager Manual...
Page 202: ...A BladeManager Hardware Specifications A 4 AlterPath BladeManager Manual...