2 monitoring device critical errors, 6 oosd tests, 1 cpu – Artesyn ViewCheck on ATCA-9405 Installation and Use (May 2014) User Manual

Page 87: Oosd tests

Advertising
background image

Commands Execution

ViewCheck on ATCA-9405 Installation and Use (6806800S51D)

87

5.5.2

Monitoring Device Critical Errors

Under Linux OS, the Device Drivers LOG abnormal behavior and potential errors occurring in
the Hardware device with KERN_ERR or KERN_CRIT category. These notifications are
considered as potential errors as they could manifest into latent faults in the live system.

As part of monitoring the Device Critical errors, all such Kernel CRITICAL and Kernel ERROR
notifications have been extracted from the PNE Kernel (4.1) driver sources and represented in
the form of a database.

The In Service Monitoring Module of ViewCheck would watch out for the occurrence of these
notifications and on detection would send a notification to XML.

The Device Errors are captured and are identified uniquely by ERROR ID. For definition of ERROR
ID, refer

Error ID

on page 19

.

5.6

OOSD Tests

OOSD Tests are used to monitor and manage the performance of the hardware components of
blades. You can execute these tests only when blades are offline, that is blades are not
providing any service. Details of the test is supported on SP or PP or both is mentioned with the
test name.

5.6.1

CPU

CpuBurnTest (SP): CPUBurnTest constantly cycles FPU intensive functions.The resultant
calculations are constantly checked for data integrity. If the test detects erroneous data,
the test fails.

OctBootTest (SP): This test boots the PPs into U-Boot. If the correct U-Boot prompt is
detected, the test is passed.

Before starting any PP related OOSD diagnostics test, make sure that VLAN interface
(example, eth1.21) reaching octeon is properly configured with an IP.

Advertising