Artesyn ViewCheck on ATCA-7470/7475 Installation and Use (May 2014) - Manual (Page 18)

Concepts of ViewCheck
ViewCheck on ATCA-7470/7475 Installation and Use (6806800S49C) 18
 Bad Blocks test in case of Storage Device category
 Temperature tests in case of CPU categories
Each of these tests would be associated with a unique Test Identifier (Test ID).
These Test IDs start with value of (0) and would increase linearly for various sub-tests in a device
category.
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 shall provide
capability to control, execute, and manage the test on a Device Instance in a Device category.
With this mechanism, same test can be simultaneously started or triggered on multiple Device
Instances under that device category, thus providing parallel execution of tests.
2.5 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
described above. 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, eth2 or Base 0, Base 1, Base 2 are used to identify
unique devices in networking devices category. Similarly, hda1, hda2, and so on can identify
unique instances of devices in the storage category. Device instances use the standard
nomenclature already defined by the OS (for instance Linux) on the blade.
A diagnostic test identified by triple < Device Category, Test ID, device Instance> would be
invoked (or) executed on the unique device instance.
The Enumerations mentioned below are used extensively in the context of InService
Monitoring.