5 device instance, 6 monitor id, 5 device instance 2.6 monitor id – Artesyn ViewCheck on ATCA-9405 Installation and Use (May 2014) User Manual
Page 18
Concepts of ViewCheck
ViewCheck on ATCA-9405 Installation and Use (6806800S51D)
18
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, or eth2 are used to identify unique devices in
networking devices 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.
2.6
Monitor ID
ViewCheck Service monitors pre-identified parameters for hardware devices. These
parameters are Network Device counters, Network Device errors etc. 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. This value shall be used by the ViewCheck, to control monitoring and also
while reporting events via XML on these monitors.