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

Concepts of ViewCheck
ViewCheck on ATCA-7470/7475 Installation and Use (6806800S49E) 18
Some tests may be applicable to all device instances in a particular device category. The
combination of 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, eth2 or Base 0, Base 1, Base 2 are used to identify
unique devices in networking device 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 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 CPU core temperature, 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.