4 device instance, 5 monitor id, 6 error id – Artesyn ViewCheck on ATCA-9405 Installation and Use (November 2014) User Manual

Page 18: 4 device instance 2.5 monitor id 2.6 error id

Advertising
background image

Concepts of ViewCheck

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

18

Some tests may be applicable to all device instances in a particular device category. The
combination of <Device category, Test ID, Device Instance> would be unique
and provides capability to control, execute, and manage the test on a device instance in a
device category. With this mechanism, same test can be simultaneously initiated or triggered
on multiple device instances under that device category, thus providing parallel execution of
tests.

2.4

Device Instance

Hardware devices uniquely identified and recognized by the drivers and OS on the blade are
treated as device instances. A device instance can belong to a particular device category. Tests
can be invoked and executed on this device instance. OS and driver support to access the
device is assumed to be readily available.

For example, device instances eth0, eth1, or eth2 are used to identify unique devices in
networking device category. Device instances use the standard nomenclature already defined
by the OS (for instance Linux) on the blade.

A diagnostics test identified with "< Device Category, Test ID, device
Instance>"

is executed on the specified device instance.

2.5

Monitor ID

ViewCheck service monitors pre-identified parameters for hardware devices. These
parameters are network device counters, and errors. To periodically poll and check these
parameters, the ViewCheck service uses CLI and XML configuration. For each parameter of
interest, a Monitor ID is an enumerated constant that uniquely represents the monitoring
entity. ViewCheck uses this value to control monitoring and while reporting events via XML on
these monitors.

2.6

Error ID

Error ID is to provide identification for pre-determined errors/warnings of hardware devices
generated by the device driver or the kernel on the blade. These critical and error messages are
indications of abnormal behavior on part of the kernel or the hardware device on the blade.
ViewCheck functionality attempts to detect all such errors and provides suitable information
to external high-level software intelligence to act upon.

Advertising