ViewCheck on ATCA-9405 Installation and Use (November 2014)

ViewCheck on ATCA-9405 Installation and Use (November 2014)
ViewCheck on ATCA-9405
Installation and Use
P/N: 6806800S51F
November 2014
©
Copyright 2014 Artesyn Embedded Technologies, Inc.
All rights reserved.
Trademarks
Artesyn Embedded Technologies, Artesyn and the Artesyn Embedded Technologies logo are trademarks and service marks of
Artesyn Embedded Technologies, Inc.© 2014 Artesyn Embedded Technologies, Inc. All other product or service names are the
property of their respective owners.
Intel® is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
Java™ and all other Java-based marks are trademarks or registered trademarks of Oracle America, Inc. in the U.S. and other countries.
Microsoft®, Windows® and Windows Me® are registered trademarks of Microsoft Corporation; and Windows XP™ is a trademark of
Microsoft Corporation.
PICMG®, CompactPCI®, AdvancedTCA™ and the PICMG, CompactPCI and AdvancedTCA logos are registered trademarks of the PCI
Industrial Computer Manufacturers Group.
UNIX® is a registered trademark of The Open Group in the United States and other countries.
Notice
While reasonable efforts have been made to assure the accuracy of this document, Artesyn assumes no liability resulting from any
omissions in this document, or from the use of the information obtained therein. Artesyn reserves the right to revise this document
and to make changes from time to time in the content hereof without obligation of Artesyn to notify any person of such revision or
changes.
Electronic versions of this material may be read online, downloaded for personal use, or referenced in another document as a URL to
an Artesyn website. The text itself may not be published commercially in print or electronic form, edited, translated, or otherwise
altered without the permission of Artesyn.
It is possible that this publication may contain reference to or information about Artesyn products (machines and programs),
programming, or services that are not available in your country. Such references or information must not be construed to mean that
Artesyn intends to announce such Artesyn products, programming, or services in your country.
Limited and Restricted Rights Legend
If the documentation contained herein is supplied, directly or indirectly, to the U.S. Government, the following notice shall apply
unless otherwise agreed to in writing by Artesyn.
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (b)(3) of the Rights in
Technical Data clause at DFARS 252.227-7013 (Nov. 1995) and of the Rights in Noncommercial Computer Software and
Documentation clause at DFARS 252.227-7014 (Jun. 1995).
Contact Address
Artesyn Embedded Technologies
Artesyn Embedded Technologies
Marketing Communications
Lilienthalstr. 17-19
2900 S. Diablo Way, Suite 190
85579 Neubiberg/Munich
Tempe, Arizona 85282
Germany
Contents
About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1
1.2
2
Concepts of ViewCheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1
2.2
2.3
2.4
2.5
2.6
3
Test Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Device Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Test ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Device Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Monitor ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Error ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installation of ViewCheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
4
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
ViewCheck Access Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.1 CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.2 XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
ViewCheck RPM Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
BSF Service RPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
ViewCheck Service OS Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Access and Execution of a Test Using CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Access and Execution of a Test Using XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.6.1 Authenticate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.6.2 Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.6.3 GetClassList . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.6.4 DescribeClass. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.6.5 InvokeMethod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
ViewCheck Service LOG Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
ViewCheck TestLog Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Commands Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
3
Contents
Contents
4.2
4.3
4.4
4
Generic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2.1 configure-error-strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2.2 configure-log-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.2.3 device-category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.2.4 diag-service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.2.5 hw-inventory-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.2.6 list-all-tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.2.7 list-device-instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.2.8 purge-all-log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.2.9 purge-log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.2.10 set-log-level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.2.11 show-all-monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.2.12 show-all-test-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.2.13 show-diag-scan-result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.2.14 show-log-content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.2.15 show-log-info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.2.16 show-log-level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.2.17 show-running-mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.2.18 show-systemerror-log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.2.19 start-all-monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.2.20 start-diag-scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.2.21 stop-all-monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.2.22 stop-diag-scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.2.23 switch-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.2.24 version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Test Management and Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.3.1 start-test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.3.2 show-test-help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.3.3 list-tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.3.4 show-test-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.3.5 show-test-result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.3.6 stop-test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Monitoring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.4.1 show-monitor-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.4.2 show-poll-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.4.3 start-monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Contents
4.5
4.6
A
4.4.4 set-poll-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.4.5 set-poll-interval-default. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.4.6 stop-monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.4.7 set-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.4.8 show-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.4.9 show-networkcounter-log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.4.10 show-networkerror-log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.4.11 exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
InService Monitoring Specifics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.5.1 Monitoring Hardware Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.5.2 Monitoring Device Critical Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
OOSD Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.6.1 CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.6.2 HDD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.6.3 Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.6.4 OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.6.5 PCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.6.6 IPMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.6.7 NETWORK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.6.8 FPGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.6.9 I2C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.6.10 USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.6.11 RTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
A.1
Artesyn Embedded Technologies - Embedded Computing Documentation . . . . . . . . . . . . . . . . 85
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
5
Contents
Contents
6
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
List of Tables
Table 3-1
Table 3-2
Table 4-1
Table 4-2
Table 4-3
Table 4-4
Table 4-5
Table 4-6
Table 4-7
Table 4-8
Table 4-9
Table 4-10
Table 4-11
Table 4-12
Table 4-13
Table 4-14
Table 4-15
Table 4-16
Table 4-17
Table 4-18
Table 4-19
Table 4-20
Table 4-21
Table 4-22
Table 4-23
Table 4-24
Table A-1
RPM Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
ViewCheck Service OS Image Files on SP and PP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
configure-error-strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
configure-log-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
diag-service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
purge-log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
set-log-level Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
set-log-level Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
show-log-content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
start-all-monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
start-diag-scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
stop-all-monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
switch-mode Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
start-test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
show-test-help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
show-test-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
show-test-result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
stop-test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
show-poll-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
start-monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
set-poll-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
set-poll-interval-default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
stop-monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
set-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
show-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Artesyn Embedded Technologies - Embedded Computing Publications . . . . . . . . . . . . . . . 85
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
7
List of Tables
8
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
About this Manual
Overview of Contents
This guide provides detailed information about installation, configuration, and how to work
with ViewCheck. This manual is divided into following chapters and appendix.

About this Manual lists all conventions and abbreviations used in this manual and outlines the
revision history.

Introduction provides detailed overview and features of ViewCheck.

Concepts of ViewCheck describes the concepts of ViewCheck.

Installation of ViewCheck provides instructions to install ViewCheck.

Commands Execution describes the various tests that can be executed in ViewCheck.

Related Documentation lists the relevant manuals and provides additional information.
Abbreviations
The following table lists the abbreviations used throughout the document.
Abbreviation
Definition
ATCA
Advanced Telecom Computing Architecture
BBS
Basic Blade Services Software
BSF
Blade Services Framework. A derivative of System Services Framework.
Client
The applications used to Access ViewCheck via various Interfaces (CLI
and XML)
INSM
In Service Monitoring. Functional module in ViewCheck framework
handling the monitoring functionality of various critical parameters in
the blade.
OOSD
Online Out of service Diagnostics. Functional module in ViewCheck
framework that manages Test Management requests related to Out of
Service Diagnostics.
PP
Packet Processor
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
9
About this Manual
About this Manual
Abbreviation
Definition
SDK
Software Development Kit
SP
Service Processor
TFTP
Trivial File Transfer Protocol
XML
Extensible Markup Language
Conventions
The following table describes the conventions used throughout this manual.
Notation
Description
0x00000000
Typical notation for hexadecimal numbers (digits are
0 through F), for example used for addresses and
offsets
0b0000
Same for binary numbers (digits are 0 and 1)
bold
Used to emphasize a word
Screen
Used for on-screen output and code related elements
or commands in body text
Courier + Bold
Used to characterize user input and to separate it
from system output
Reference
Used for references and for table and figure
descriptions
File > Exit
Notation for selecting a submenu
<text>
Notation for variables and keys
[text]
Notation for software buttons to click on the screen
and parameter description
...
Repeated item for example node 1, node 2, ..., node
12
.
Omission of information from example/command
that is not necessary at the time being
.
.
..
10
Ranges, for example: 0..4 means one of the integers
0,1,2,3, and 4 (used in registers)
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
About this Manual
Notation
Description
|
Logical OR
Indicates a hazardous situation which, if not avoided,
could result in death or serious injury
Indicates a hazardous situation which, if not avoided,
may result in minor or moderate injury
Indicates a property damage message
No danger encountered. Pay attention to important
information
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
11
About this Manual
About this Manual
Summary of Changes
Part Number
Date
Description
6806800S51A
October 2013
Initial version.
6806800S51B
March 2014
Updated the sections Overview on page 21,
ViewCheck RPM Image on page 21 and BSF
Service RPM on page 23.
6806800S51C
May 2014
R2.6 Release
Added new commands in Generic
Commands on page 43, a test in Memory on
page 80 and section FPGA on page 83.
Updated ViewCheck Service OS Image on
page 24 and OOSD Tests on page 79.
Re-branded to Artesyn template.
12
6806800S51D
May 2014
Added notice in sections Orion License RPM
Installation, Overview, ViewCheck RPM Image,
and BSF Service RPM.
6806800S51E
Septembe, 2014
Added show-all-test-status on page 52,showlog-level on page 54, switch-mode on page
59, ViewCheck TestLog Information on page
41, and SfpDetectionTest command.
6806800S51F
November 2014
Updated Installation of ViewCheck on page
21.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Chapter 1
Introduction
1.1
Overview
ViewCheck™ is a comprehensive software service used to diagnose, manage, and monitor
Artesyn blades. The diagnostic utilities of ViewCheck help in identifying, detecting, and
locating hardware issues on a blade. ViewCheck also provides mechanism to monitor status of
Storage devices, Ethernet counters and errors.
ViewCheck can be accessed locally using Command Line Interface (CLI) and Extensible Markup
Language (XML) interfaces provided via Blade Services Framework (BSF) service.
ViewCheck provides:

InService Diagnostics
In this mode, the diagnostics service can run even while the blades are instantiated with
customer applications and are providing service.
ViewCheck can monitor key hardware parameters like network counters, and network
errors. It can also be used for watching kernel critical errors logged by various hardware
devices and device drivers.

Out of Service Diagnostics
In this mode, a service OS is provided with various Out of Service Diagnostics tests and
utilities. This Service OS has to be loaded and diagnostics utilities can be executed. To
execute these tests, CLI /XML access is provided.
Both InService and Out of Service are provided as binary images. For more information on
Binary images and installation procedures, refer Installation of ViewCheck on page 21.
In this mode, ViewCheck can execute all Out of Service Diagnostics (OOSD) tests along
with InService Diagnostics activities
For more information on commands supported for InService and OOSD, refer Commands
Execution on page 43.
ViewCheck on ATCA-9405 is supported on P2020 service processor (SP) and two Cavium
OCTEON II packet processors (PP). Procedure to install and accessing ViewCheck on SP and PP
are different and are detailed in Installation of ViewCheck on page 21.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
13
Introduction
1.2
ViewCheck Access Methods
This section explains various methods for accessing ViewCheck services on Artesyn blades. You
can access ViewCheck using the following interfaces:

CLI

XML
Using these interfaces, you can:
1.2.1

Initiate a diagnostic test

Query available diagnostic tests

Query status of a particular diagnostic test

Start and stop monitoring

Stop a diagnostic test

Generate Hardware inventory.
CLI
Using CLI, you can start, stop, and query kind of primitives at this prompt. The ViewCheck CLI
can be accessed via a console using Secure Shell (SSH).
BSF, a proprietary service of Artesyn, is used to provide the CLI access to ViewCheck service.
BSF binaries are provided along with the ViewCheck binaries.
For more information on BSF RPMs and Installation procedures, refer Installation of ViewCheck
on page 21.
1.2.2
XML
XML interface supports methods, classes, and event notification mechanism. Using XML, you
can start, stop, query, and configure the parameters related to tests and monitors. XML
interface can be accessed in the same manner as CLI and is provided by BSF.
14
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Introduction
XML notifications are generated with following details:

State changes about the diagnostic test under execution

Pre-determined monitor exceeding set Threshold value

Occurrence of any pre-determined hardware device error/warning generated by the
device driver or the kernel on the blade.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
15
Introduction
16
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Chapter 2
Concepts of ViewCheck
This section explains terminology and keywords used extensively in ViewCheck services.
2.1
Test Identification
Unique Test identification is based on following triple key:
< Device Category, Test ID, Device Instance >
2.2
Device Category
The Device Category is an enumerated value, reused from similar enumeration already defined
in the HPI-B Standard specification.
It is used to express commonly used devices, such as Storage, Network, Serial, CPU, and
Memory, available on all the blades, irrespective of function and architecture. This category is
used in commands as one of the key fields to identify uniquely a particular test.
Device Category allows for:
2.3

Grouping of test cases per category for display and statistical purposes

Reuse of Test IDs across the device categories
Test ID
Test ID is an integer value that uniquely identifies the actual test that can be invoked or
executed on a hardware device instance, which belongs to a specific device category available
on the blade. Following are the examples of tests that can be executed on the devices.

Ping Flood test

Network connectivity test in case of Network Device Category
Each of these tests would be associated with a unique Test Identifier (Test ID).
These Test IDs start with value ’0’ and increases linearly for various sub-tests in a device
category.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
17
Concepts of ViewCheck
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.
18
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Concepts of ViewCheck
The list of messages that constitute these errors is not standardized by the hardware device
vendor nor the Linux Kernel Community. Error ID attempts to standardize all such messages on
Artesyn blades. These messages would be OS and driver specific. Mostly, the same Error ID
would be associated with the same category of error across blades and OS. For more
information on commands, refer to Commands Execution on page 43.
Note: Monitor ID and Error ID are used in InService Monitoring.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
19
Concepts of ViewCheck
20
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Chapter 3
Installation of ViewCheck
3.1
Overview
This section explains the ViewCheck release modules and installation procedures to install and
run ViewCheck service on the Artesyn ATCA-9405 blade.
ViewCheck service is released as a set of two distinct images.

ViewCheck RPM Image
This RPM contains all ViewCheck services. BSF service RPMs are also distributed along with
the ViewCheck RPMs. BSF service RPMs provide access to CLI and XML.
If user wants to move to a newly available ViewCheck and BSF RPMs, the current set of RPMs
should be uninstalled before installing the new RPMs. For more information, see ViewCheck
RPM Image and BSF Service RPM.

3.2
ViewCheck Service OS image
You can download this image from SWORDS. This contains the ViewCheck OOS image for
PPs.
ViewCheck RPM Image
The ViewCheck RPM Image functionally comprises Diagnostics Framework, specific test cases,
and test suites. The ViewCheck RPM always uses same OS variant and compile time
environment based on the BBS release of the target blade. For ATCA-9405 Service Processor
(SP) blade, the ViewCheck RPM is created for PNE 4.1 environment.
ViewCheck service RPM consists of:

Diagnostics Core - Daemon

Static Test Suite Configuration files for the specific blade

Start/Stop scripts for Diagnostics Core
Using the following command, you can install the ViewCheck RPM Image:
rpm -iv --nodeps diagnostics<RELEASE>_<BUILD>.<DIST>.<OS>.9405sp.rpm
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
21
Installation of ViewCheck
Using the following command, you can remove the ViewCheck RPM Image:
rpm -e diagnostics-<RELEASE>_<BUILD>.<DIST>.<OS>.9405sp.rpm
You need to stop the Diagnostics Core service, before performing un-installation using the
script, /opt/diagnostics/etc/init.d/diagcore stop.
The following table provides details of the files that are created on the blade once the
ViewCheck RPM is installed.
Table 3-1 RPM Files
File Name
Path
Descriptions
diagcored
/opt/diagnostics/bin/
Diagnostics Core - Daemon
diagconfig.xml
/opt/diagnostics/etc/diag/
ViewCheck configuration file and user
configuration file.
diagcore
/opt/diagnostics/etc/init.d/
Script to Start/Stop diagnostics core
libdiagintf.so
on 9405_SP: /lib/
on 9405_PP: /lib/ and /lib64/
Interface library between diagnostics
core daemon and BSF application.
<TestScripts>.sh
/opt/diagnostics/tools/diagt
estscripts/
Test scripts
EmrDiag_Debug.log
/opt/diagnostics/var/log/dia
g/service/
Diagnostics daemon service log
diagLib_log,
diagCore_log,
diagResults_log,
diagTestRaw_log,
/etc/logrotate.d
Configuration files required for log
rotation of service logs
/opt/diagnostics/tools/diagt
estutils/
Utilities and Tools used by ViewCheck
application
diaguserconf.xml
diagShowCmds_log
Testutilities
22
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Installation of ViewCheck
3.3
BSF Service RPM
BSF service is distributed as a package contains 3 RPMs, namely eMIND, BSFCore, and
Diagnostics Transport Layer Service. Following are the list of RPM:
ssf_main_rel-<BLADE>-<DIST>-<RELEASEBUILD>.<ARCH>.rpm
ssf_csim_rel-<BLADE>-<DIST>-<RELEASEBUILD>.<ARCH>.rpm
ssf_diagnosticsTLS_rel-<BLADE>-<DIST>-<RELEASEBUILD>.<ARCH>.rpm
You should install BSF RPMs in the following sequence:
1. ssf_main
2. ssf_csim
3. ssf_diagnosticsTLS
You can install the BSF using the following RPM commands:

rpm -iv --nodeps --force ssf_main_rel-<BLADE>-<DIST><RELEASEBUILD>.<ARCH>.rpm

rpm -iv --nodeps --force ssf_csim_rel-<BLADE>-<DIST><RELEASEBUILD>.<ARCH>.rpm

rpm -iv --nodeps --force ssf_diagnosticsTLS_rel-<BLADE>-<DIST><RELEASEBUILD>.<ARCH>.rpm
After the installation, the BSF binary files are installed at the /opt/ssf location.
The BSF applications can be started, stopped, and restarted using below script.
/opt/ssf/etc/config/S99SsfBsfRun.sh <start/stop/restart>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
23
Installation of ViewCheck
To uninstall the BSF, execute the following RPM commands:

rpm -e ssf_diagnosticsTLS_rel-<BLADE>-<DIST><RELEASEBUILD>.<ARCH>.rpm

rpm -e ssf_csim_rel-<BLADE>-<DIST>-<RELEASEBUILD>.<ARCH>.rpm

rpm -e ssf_main_rel-<BLADE>-<DIST>-<RELEASEBUILD>.<ARCH>.rpm
Before performing uninstallation, stop the BSF services using below script.
/opt/ssf/etc/config/S99SsfBsfRun.sh stop
The order of removal of RPMs is a reverse procedure to that of installation.
3.4
ViewCheck Service OS Image
The ViewCheck Service OS Image enables you to boot into ViewCheck specific OS and execute
the OOSD tests. The ViewCheck service is not completely dependent on the blade BBS
environment. For compatibility purpose, it may use the same OS or the Kernel variant that are
used by the blade BBS service. For ATCA-9405 SP, the ViewCheck service OS is created with PNE
4.1 as the OS. For ATCA-9405 PP the OOSD image is built from cavium Software Development
Kit (SDK). The ATCA-9405 PP OOSD image is packaged along with ATCA-9405 SP OOSD image.
So there is a single ViewCheck OS image for ATCA-9405 blade.
The ViewCheck service OS along with the ViewCheck RPM, test suites, and test procedures are
distributed as an ISO file that contains:
24

ViewCheck OS as Ram Disk image that can be Net bootable.

ViewCheck OS image can be Net bootable and installable on selected Flash partition,
provided User Flash is available on the blade.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Installation of ViewCheck
The following table provides details of the files that are distributed as part of this image once
the ViewCheck service OS is installed.
Table 3-2 ViewCheck Service OS Image Files on SP and PP
File Name
Remarks
diagnostics-RELEASEBUILD.windriver4.1.linux.atca940
5sp.gz
Net bootable Ram Disk image with
ViewCheck RPM and BSF services package.
ViewCheck OOS image for PP with ViewCheck RPM
and BSF service packages.
Installing the ViewCheck Service OS image on SP
Before installing the ViewCheck service OS Image, you should have the knowledge of
configuring Trivial File Transfer Protocol (TFTP) server, configuring ATCA-9405 for Network
Booting and booting the ATCA-9405 using a ramdisk. For more information, refer to the section
2.3 in Blade Services Software on ATCA-9405 Programmer’s Reference Manual.
1. Once the blade is configured to boot with ramdisk image, it will have ViewCheck
and BSF installed.
2. SP should also have the interfaces to PP1 and PP2 configured so that a
communication can be established between SP and PPs.
Installing the ViewCheck Service OS image on PP
The following procedure is to boot the ViewCheck OOS image on PP. For more information,
refer to section 2.6.5 in Blade Services Software on ATCA-9405 Programmer’s Reference Manual.
Before installing ViewCheck Service OS image on PP, make sure that VLANs are configured
appropriately to reach Octeons.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
25
Installation of ViewCheck
1. On SP, go to /opt/diagnostics/etc/diag/ location and execute the
runlinux scripts.

For installing ViewCheck Service OS image on PP1, execute./runlinux 1
command.

For installing ViewCheck Service OS image on PP2, execute ./runlinux 2
command.
Installing ViewCheck Service OS Image on USB
The ViewCheck service OS image can be installed on any external USB drive using flashprep
and flashinstall tools available on the board.
Use the flashrc tool available on the board to install the ViewCheck service OS image on USB
device.
For more information on installation, refer section 2.6.5 in Blade Services Software on ATCA-9405
Programmer’s Reference Manual.
Before installing on USB, the image needs to be converted into tar.bz2 format using
mk_atca_9405_sp_bzip2_format.sh script provided along with this release.
Example
./mk_atca_9405_sp_bzip2_format.sh <ViewCheck service image>
For this, any Linux PC can be used.
3.5
Access and Execution of a Test Using CLI
You can access ViewCheck CLI using the following procedure:
1. Establish the secure shell using SSH or Putty.
2. Start the Telnet connection from an already established secure shell.
telnet localhost 11001
Trying :1...
telnet: connect to address ::1: Connection refused
26
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Installation of ViewCheck
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
Welcome to Emerson's SSF CLI
3. Type your username and password.
Username: Admin
Password:
Access granted
>enable
#configure terminal
BSF(config)#
By default, the administrator user name and password are "Admin".
4. Select Virtual Execution Environment as below:

On SP, use the virExecEnv SP_VEE0 options in the virExecEnv.
BSF(config)#virExecEnv virExecEnv SP_VEE0
BSF(VEE-SP_VEE0)#diagnostic
BSF(diag-SP_VEE0)#

On PP, use the OCTEON1_VEE0/OCTEON1_VEE1 options in the virExecEnv.
BSF(config)#virExecEnv OCTEON1_VEE0
BSF(VEE-OCTEON1_VEE0)#diagnostic
BSF(diag-OCTEON1_VEE0)#
After logging into the ViewCheck CLI, you can list all supported commands by typing '?' on
the CLI console. Following is an example.
BSF(diag-SP_VEE0)#?
configure-error-strings User configurable error strings, notified
by ViewCheck when reported by the device.
configure-log-path
Configures the log path where the resluts
are stored.
device-category
Configure deviceCategory
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
27
Installation of ViewCheck
diag-service
exit
hw-inventory-list
list-all-tests
purge-all-log
purge-log
reload
set-log-level
show-all-monitors
show-diag-scan-result
show-log-content
show-log-info
show-running-mode
show-systemerror-log
start-all-monitors
start-diag-scan
stop-all-monitors
stop-diag-scan
version
Diag operation(start/stop/restart).
Exit from diagnostic
Provides the Inventory of Hardware (Type,
Vendor ID, Major Number, Minor Number and
any associated Details) as detected by the
Diagnostics Application.
Displays all the supported tests on the
Board.
All log files are Zipped and stored away.
Purge specific log file.
User can issue this command when there
are updates to the User XML.
Sets the Log Level of Diagnostic
Application.
Displays all the supported Monitors on
the Board.
Displays the last run result of Diagscan.
Displays the content of log files related
to Rawlogs and ResultsLog of ViewCheck.
List all Log files of Diagnostics
Application.
Displays the current running mode of
ViewCheck.
show system error log.
Starts all the supported Monitors
available on the board or related to a
device category.
Executes the Diagnostics tests supported
on the Board.
Stops all the supported Monitors
available on the board or related to a
device category.
stop the diag scan tests.
Displays versions of BBS,ViewCheck and
BBS installed on the Board.
You can enter into device category mode by giving the command device-category on CLI
and view the list of commands supported only at device category level.
28
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Installation of ViewCheck
BSF(diag-SP_VEE0)#device-category ?
deviceCategory> other, processor, hardDisk, memory, os,
pciBus, pciExpressBus, scsiBus, sataBus,
clock, firmware, cpld, fpga,
networkinterface, digitalsignalprocessor,
networkprocessingunit, interface, systemBus,
flash, serial, i2cBus, spiBus, usbBus, ipmc, all
BSF(diag-SP_VEE0)# device-category networkinterface
BSF(diag-SP_VEE0-networkinterface)#?
exit
Exit from deviceCategory
list-device-instances
List all the possible device
instances in present
deviceCategory.
list-tests
User can use this command to get
information on the available
Diagnostic tests with details like
tests and sub tests associated,
along with Test
IDs.
set-lower-threshold-info
Set the Lower Threshold value for
the Monitor
set-rate
set the rate of change value for
network monitors
set-poll-interval-default Set Poll Interval to default value
set-poll-interval
Set the Poll Interval
set-threshold-default
Set Threshold to default value
set-upper-threshold-info
Set the Upper Threshold value for
the Monitor
show-lower-threshold-info Show Lower Threshold info.
show-monitor-id
List all monitors for the
deviceCategory.
show-networkcounter-log
show network counters log
show-networkerror-log
show network errors log
show-poll-interval
Show Poll Interval
show-rate
show the rate of change value for
network monitors
show-test-help
Brief help on the usage of the
Specific Test referred by Test ID.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
29
Installation of ViewCheck
show-test-result
show-test-status
show-upper-threshold-info
start-monitor
start-test
stop-monitor
stop-test
Show test result
Show test status
Show upper threshold info.
Start a monitor
Start a test
Stop a monitor
Stop a test
After logging into the CLI, you can start, stop, and query a test from the CLI. You can view the
details of the test by executing show-test-help command.
To start a test, you can run start-test command with testId, deviceInstance, and
arguments as input to the command. The arguments can be neglected for tests that does not
take any argument as input.
After test execution, the results can be viewed by show-test-result command, which
displays test result and a raw log generated by that test.
Using CLI, you can list all the InService diagnostics monitors in a device category. By default, all
monitors start when ViewCheck application is initialized. You can start and stop any monitor
using start-monitor and stop-monitor commands.
To exit from the ViewCheck CLI:
BSF(diag-SP_VEE0)#exit
BSF(VEE-vee0)#exit
BSF(config)#exit
#exit
3.6
Access and Execution of a Test Using XML
You can access ViewCheck XML interface similar to ViewCheck CLI.
1. Establish the secure shell using SSH or Putty.
2. Start the Telnet connection from an already established secure shell.
30
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Installation of ViewCheck
telnet localhost 15550
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
3.6.1
Authenticate
After a connection with XML Agent is established, the only command should be executed is
Authenticate. This command is for evaluating user credentials.
The Authenticate command contains user name and password for verification. Successful
authentication is signified by the success response, otherwise an error message is returned.
You need to enter the user credentials to XML Agent using the command Authenticate. The
XML Agent forwards the authentication request to the BSF system, which validates the user
credentials and allows the XML client to access it.
3.6.2

Request:
In the below request, the user credentials “Admin” and "Admin” are created by default in
the BSF. But you need to provide credentials by creating them using the "CreateObject"
command as shown in the section GetClassList.
<Script><Authenticate><User>Admin</User><Password>Admin</Passwo
rd></Authenticate></Script>]]>]]>

Response:
The below response is received if the authentication is successful.
<?xml version="1.0"?><Response><Success/></Response>]]>]]>
The following response is received if authentication fails.
<?xml
version="1.0"?><Response><Error><ErrorCode>1</ErrorCode><Type>O
peration not allowed</Type><Description>Authentication
error</Description><CustomError/></Error></Response>]]>]]>
Configure
This command configures the XML protocol for the indentation and the events to
enable/disable state. There are two configuration options available:
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
31
Installation of ViewCheck
IndentOutput option controls the indentation of the XML response produced by the
MINDAgent. Its default value is ’0’, which means, by default, output indentation is off.

Request:
The following request command sets the indentation to 4:
<Script><Configure><IndentOutput>4</IndentOutput></Configure></
Script>]]>]]>

Response:
<?xml version="1.0"?>
<Response>
<Success/>
</Response>]]>]]>
EnableEvents option enables or disables events that reach XML interface from the BSF
framework. Successful execution is signifies by the success response. Otherwise, an error
message is returned.
The values for the command is true/false. The value, "True" enables the events and the
"false" value disables the events.
32

Request:
<?xmlversion ="1.0"?>
<Script>
<Configure>
<EnableEvents>true</EnableEvents>
</Configure>
</Script>]]>]]>

Response:
<?xml version="1.0"?><Response><Success/></Response>]]>]]>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Installation of ViewCheck
3.6.3
GetClassList
This command is used to retrieve all BSF classes.

Request:
<Script ><GetClassList /></Script >]]>]]>

Response:
The response message received from the XML Agent is shown below. The response
contains all the BSF classes including the BSF framework classes along with the application
defined classes.
<Response>
<Classes>
<Class>session</Class>
<Class>shell</Class>
<Class>mode</Class>
<Class>command</Class>
<Class>user</Class>
<Class>group</Class>
<Class>membership</Class>
<Class>ACManager</Class>
<Class>shutdown</Class>
<Class>usmuser</Class>
<Class>traphost</Class>
<Class>cppscript</Class>
<Class>classlock</Class>
<Class>globallock</Class>
<Class>CommunityMO</Class>
<Class>SystemMO</Class>
<Class>SNMPAgentConfig</Class>
<Class>EventReceiver</Class>
<Class>EventFilter</Class>
<Class>agent</Class>
<Class>logsink</Class>
<Class>logfilter</Class>
<Class>acl</Class>
<Class>aclclass</Class>
<Class>aclmember</Class>
<Class>aclmoid</Class>
<Class>aclclassrange</Class>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
33
Installation of ViewCheck
<Class>aceclass</Class>
<Class>acemember</Class>
<Class>acemoid</Class>
<Class>aceclassrange</Class>
<Class>virExecEnv</Class>
<Class>interface</Class>
<Class>service</Class>
<Class>diagnostic</Class>
<Class>deviceCategory</Class>
</Classes>
</Response>]]>]]>
ViewCheck software uses classes, diagnostics, and device category to start, stop, and query
the status of tests and monitors.
3.6.4
DescribeClass
DescribeClass XML command retrieves the description and properties of a BSF class, such
as class creatability, class deletable, class writability, attributes, attributes description,
attribute types and so on. It returns class description on success or an error on failure.
34

Request:
The below XML request gets the description of class, "shelf" in the BSF system.
<?xmlversion ="1.0"?>
<Script version ="2">
<DescribeClass>
<Class>diagnostic</Class>
</DescribeClass>
</Script>]]>]]>
<?xml version="1.0"?>

Response:
The below XML response shows the different details of the class, "shelf" in the BSF system.
<Response>
<ClassDesc>
<Class>diagnostic</Class>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Installation of ViewCheck
<Id>1201</Id>
<Description>In Diagnostic mode, user can configure and perform
Diagnostic related tests, monitoring &amp;
updating.</Description>
<IsSingleton>false</IsSingleton>
<IsCreatable>true</IsCreatable>
<IsDeletable>true</IsDeletable>
<IsWritable>false</IsWritable>
<MOIDDesc>
<Name>diagnosticMoid</Name>
<Id>1201</Id>
<Description/>
<MOIDItemDesc>
<Ref>
<ClassId>1102</ClassId>
<MOIDId>1102</MOIDId>
</Ref>
</MOIDItemDesc>
</MOIDDesc>
<MethodDesc>
<Name>hwInventoryList</Name>
<Id>10</Id>
<Description>Provides the Inventory of Hardware (Type, Vendor
ID, Major Number, Minor Number and any associated Details) as
detected by the Diagnostics Application. </Description>
<IsStatic>false</IsStatic>
<ArgDesc>
<Name>outputResult</Name>
<Id>0</Id>
<Description/>
<TypeDesc>
<Name/>
<Description/>
</TypeDesc>
<IsInput>false</IsInput>
<IsOutput>true</IsOutput>
<IsOptional>false</IsOptional>
</ArgDesc>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
35
Installation of ViewCheck
</MethodDesc>
<MethodDesc>
<Name>reload</Name>
<Id>20</Id>
<Description>User can issue this command when there are
updates to the User XML .</Description>
<IsStatic>false</IsStatic>
<ArgDesc>
<Name>commandStatus</Name>
<Id>0</Id>
<Description/>
<TypeDesc>
<Name/>
<Description/>
</TypeDesc>
<IsInput>false</IsInput>
<IsOutput>true</IsOutput>
<IsOptional>true</IsOptional>
</ArgDesc>
</MethodDesc>
<MethodDesc>
<Name>setLogLevel</Name>
<Id>30</Id>
<Description>Sets the Log Level of Diagnostic
Application.</Description>
<IsStatic>false</IsStatic>
<ArgDesc>
<Name>logLevelValue</Name>
<Id>0</Id>
<Description>Valid log levels (3-Critical, 2-Normal, 1Info)</Description>
<TypeDesc>
<Name>Integer</Name>
<Description>Integer number in range (-2^32)/2 to (2^32)/2 1</Description>
</TypeDesc>
<IsInput>true</IsInput>
<IsOutput>false</IsOutput>
36
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Installation of ViewCheck
<IsOptional>false</IsOptional>
</ArgDesc>
<ArgDesc>
<Name>commandStatus</Name>
<Id>1</Id>
<Description/>
<TypeDesc>
<Name/>
<Description/>
</TypeDesc>
<IsInput>false</IsInput>
<IsOutput>true</IsOutput>
<IsOptional>true</IsOptional>
</ArgDesc>
</MethodDesc>
<MethodDesc>
<Name>showLogInfo</Name>
<Id>40</Id>
<Description>List all Log files of Diagnostics
Application.</Description>
<IsStatic>false</IsStatic>
<ArgDesc>
<Name>outputResult</Name>
<Id>0</Id>
<Description/>
<TypeDesc>
<Name/>
<Description/>
</TypeDesc>
<IsInput>false</IsInput>
<IsOutput>true</IsOutput>
<IsOptional>false</IsOptional>
</ArgDesc>
</MethodDesc>
<MethodDesc>
<Name>purgeLog</Name>
<Id>50</Id>
<Description>Purge specific log file.</Description>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
37
Installation of ViewCheck
<IsStatic>false</IsStatic>
<ArgDesc>
<Name>logFileName</Name>
<Id>0</Id>
<Description>log file name</Description>
<TypeDesc>
<Name/>
<Description>file name</Description>
</TypeDesc>
<IsInput>true</IsInput>
<IsOutput>false</IsOutput>
<IsOptional>false</IsOptional>
</ArgDesc>
<ArgDesc>
<Name>commandStatus</Name>
<Id>1</Id>
<Description/>
<TypeDesc>
<Name/>
<Description/>
</TypeDesc>
<IsInput>false</IsInput>
<IsOutput>true</IsOutput>
<IsOptional>true</IsOptional>
</ArgDesc>
</MethodDesc>
<MethodDesc>
<Name>purgeAllLog</Name>
<Id>60</Id>
<Description>All log files are Zipped and stored
away.</Description>
<IsStatic>false</IsStatic>
<ArgDesc>
<Name>commandStatus</Name>
<Id>0</Id>
<Description/>
<TypeDesc>
<Name/>
38
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Installation of ViewCheck
<Description/>
</TypeDesc>
<IsInput>false</IsInput>
<IsOutput>true</IsOutput>
<IsOptional>true</IsOptional>
</ArgDesc>
</MethodDesc>
<MethodDesc>
<Name>showSystemErrorLog</Name>
<Id>70</Id>
<Description>show system error log</Description>
<IsStatic>false</IsStatic>
<ArgDesc>
<Name>outputResult</Name>
<Id>0</Id>
<Description/>
<TypeDesc>
<Name/>
<Description/>
</TypeDesc>
<IsInput>false</IsInput>
<IsOutput>true</IsOutput>
<IsOptional>false</IsOptional>
</ArgDesc>
</MethodDesc>
</ClassDesc>
</Response>]]>]]>
3.6.5
InvokeMethod
InvokeMethod XML command calls the method of a BSF Object. BSF methods are defined
with method parameters such as input, output, and input-output.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
39
Installation of ViewCheck
BSF Object method can be invoked with a list of input or input-output arguments. This
command returns a list of output or input-output arguments. The input argument means it is
only an input and will not be displayed in the output. But in the case of input-output
arguments, both input and output will be displayed in the output.
Diagnostics and device category classes have different instances: SP_VEE0,
OCTEON1_VEE0, and OCTEON1_VEE1 for service and packet processors respectively. The
examples given below are with respect to service processor. In case, you want to execute
any commands on PP, use either OCTEON1_VEE0 or OCTEON1_VEE1 as instance.
40

Request:
The below example invokes the method class, "diagnostic" with instance "SP_VEE0". Upon
execution of this method by the class instance, response will be sent in the output/inputoutput arguments.
Request
=======
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>setLogLevel</Method>
<Argument>
<Name>logLevelValue</Name>
<Value>1</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>

Response:
InvokeMethod command returns the below response after executing the above
example command.
<?xml version="1.0"?>
<Response>
<Arguments>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Installation of ViewCheck
<Argument>
<Name>commandStatus</Name>
<Value>Set Log Level Success</Value>
</Argument>
</Arguments>
</Response>]]>]]>
To exit from the ViewCheck XML:
<Script>
<Command name="Exit"/>
<Script>]]>]]>
3.7
ViewCheck Service LOG Information
ViewCheck service logs are generated in EmrDiag_Debug.log file and is located at
/opt/diagnostics/var/log/diag/service/
The Test result logs and raw logs generated by various tests are available at
/opt/diagnostics/var/log/diag/testlog/
3.8
ViewCheck TestLog Information
ViewCheck internally retains data related to tests invoked by the user. If the number of tests
invoked by the user exceed 1000, all this information is saved in the
Emr_TestResultsMib.txt file and the internal storage is erased.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
41
Installation of ViewCheck
42
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Chapter 4
Commands Execution
4.1
Overview
CLI and XML are the primary ways to access ViewCheck capabilities on the blade. These
mechanisms allow you to perform activities such as start, stop, and query on the ViewCheck
software. Using CLI and XML, you can also set the parameters for monitoring.
Commands are classified into:
4.2

Generic commands

Commands for test management and control

Commands for monitoring
Generic Commands
This section describes the generic commands of ViewCheck service.
The command syntaxes for XML interface is given for the diagnostic class with instance
as vee0. This instance varies depending on the blade.
4.2.1
configure-error-strings
configure-error-strings command allows to add user-defined kernel error strings to
the diagnostics database.
Syntax for CLI
configure-error-strings errorStrings <string>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
43
Commands Execution
The following table provides the configure-error-strings command arguments.
Table 4-1 configure-error-strings
Argument
Data Type
Description
String
String
Kernel error string to be added to the diagnostics
database.
Make sure that the string that you enter must be more than one word.
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>configureErrStrings</Method>
<Argument>
<Name>Error String</Name>
<Value>{error String}</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
4.2.2
configure-log-path
configure-log-path command allows to configure the location of diagnostics logs. You
can also specify the maximum limit for log size. Once the log size reaches the user-defined
limit, a trap is sent to the user. Specifying log size is optional and by default, its value is 1GB.
Syntax for CLI
configure-log-path logpath <PATH> logSize <size>
44
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
The following table provides the configure-log-path command arguments.
Table 4-2 configure-log-path
Argument
Data Type
Description
logpath
String
Location of the log files where diagnostics should place.
size
String
Optional parameter. Size of the log. For example,
10M, 2G, 100K, 1048576.
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>configureLogPath</Method>
<Argument>
<Name>logpath</Name>
<Value>{logPath String}</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
4.2.3
device-category
device-category command allows to configure the available device categories.
Syntax
device-category <Dev category>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
45
Commands Execution
Expected Output
The CLI prompt will show the device category that you have selected.
This command is valid only in CLI.
4.2.4
diag-service
diag-service command allows to start, stop, restart, and check status of the diagnostics
service.
Syntax for CLI
diag-service operation <restart/start/stop/status>
The following table provides the diag-service command argument.
Table 4-3 diag-service
Argument
Data Type
Description
operation
String
Requested operation to the diagnostics core.
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>diagService</Method>
<Argument>
<Name>operation</Name>
<Value>{operation String}</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
46
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
4.2.5
hw-inventory-list
hw-inventory-list command provides the detailed information of hardware
components available on the blade. The command displays the Hardware Type, Vendor ID,
Major Number, Minor Number and any other associated details that are identified by the
ViewCheck.
Syntax for CLI
hw-inventory-list
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>hwInventoryList</Method>
</InvokeMethod>
</Script>]]>]]>
4.2.6
list-all-tests
list-all-tests command lists all the tests available on the blade.
Syntax for CLI
list-all-tests
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>showListAllTests</Method>
</InvokeMethod>
</Script>]]>]]>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
47
Commands Execution
4.2.7
list-device-instances
list-device-instances command lists all possible device instances in present device
category.
Syntax for CLI
list-device-instances
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>listInstances</Method>
</InvokeMethod>
</Script>]]>]]>
This command will be deprecated in future.
4.2.8
purge-all-log
purge-all-log command allows to zip all log files and store away.
Syntax for CLI
purge-all-log
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
48
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
</Object>
<Method>purgeAllLog</Method>
</InvokeMethod>
</Script>]]>]]>
4.2.9
purge-log
purge-log command deletes the log files generated by ViewCheck software.
Syntax for CLI
purge-log logFileName <logfile Name>
The following table provides the purge-log command argument.
Table 4-4 purge-log
Argument
Data Type
Description
logfile Name
String
Type the name of the Log file that you want to delete or
clear.
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>purgeLog</Method>
<Argument>
<Name>logFileName</Name>
<Value>{Name of the log file}</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
49
Commands Execution
Example
BSF(diag-SP_VEE0)#purge-log logFileName NETWORK_base1.log
Purge Log Success
You can purge only raw log files. The raw log file naming convention is in the form of *.log.
4.2.10 set-log-level
set-log-level command sets the current log level of ViewCheck to value ’X’. This is an
internal debug command, used mainly for generating detailed debug log information. The
valid log level values are listed in the following table:
Table 4-5 set-log-level Values
Values
Description
1-Info
All logs are logged. Even functions like entry and exit are also logged.
2- Normal
Details of function flows are logged.
3- Critical
High level errors are logged.
Syntax for CLI
set-log-level logLevelValue <x>
The following table lists the set-log-level command argument.
Table 4-6 set-log-level Arguments
50
Argument
Data Type
Description
X
Integer
Possible values are 3, 2, 1 (3-Critical, 2-Normal, 1-Info).
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>setLogLevel</Method>
<Argument>
<Name>logLevelValue</Name>
<Value>1</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
Example
BSF(diag-SP_VEE0)#set-log-level logLevelValue 2
Set Log Level Success
4.2.11 show-all-monitors
show-all-monitors command lists all the monitors available on the blade.
Syntax for CLI
show-all-monitors
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>showAllMonitors</Method>
</InvokeMethod>
</Script>]]>]]>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
51
Commands Execution
4.2.12 show-all-test-status
show-all-test-status command allows you to view the current status of all tests
available on the blade.
Syntax for CLI
show-all-test-status
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>ShowAllTestStatus</Method>
</InvokeMethod>
</Script>]]>]]>
4.2.13 show-diag-scan-result
show-diag-scan-result command shows result of the last diag-scan command.
Syntax for CLI
show-diag-scan-result
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>showDiagScanResult</Method>
</InvokeMethod>
</Script>]]>]]>
52
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
4.2.14 show-log-content
show-log-content command displays the content of the mentioned log file.
Syntax for CLI
show-log-content logfilename <logfile Name>
The following table provides the show-log-content command arguments.
Table 4-7 show-log-content
Argument
Data Type
Description
logfile Name
String
Name of the log file to be displayed.
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>showLogContent</Method>
<Argument>
<Name>logFileName</Name>
<Value>{logfilename String}</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
4.2.15 show-log-info
show-log-info command provides the details of the various log files along with the
diagnostics data.
Syntax for CLI
show-log-info
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
53
Commands Execution
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>showLogInfo</Method>
</InvokeMethod>
</Script>]]>]]>
4.2.16 show-log-level
show-log-level command displays the current logging level of ViewCheck.
Syntax for CLI
show-log-level
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>showLogLevel</Method>
</InvokeMethod>
</Script>]]>]]>]
4.2.17 show-running-mode
show-running-mode command displays the running mode of the ViewCheck (INSM or
OOSD).
Syntax for CLI
show-running-mode
54
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>showRunningMode</Method>
</InvokeMethod>
</Script>]]>]]>
4.2.18 show-systemerror-log
show-systemerror-log command displays the kernel critical and error messages
captured by ViewCheck application.
Syntax for CLI
show-systemerror-log
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>showSystemErrorLog</Method>
</InvokeMethod>
</Script>]]>]]>
4.2.19 start-all-monitors
start-all-monitors command starts all the monitors of the mentioned device category.
Syntax for CLI
start-all-monitors device-category <Dev category>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
55
Commands Execution
The following table provides the start-all-monitors command arguments.
Table 4-8 start-all-monitors
Argument
Data Type
Description
Dev category
String
Name of the device category.
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>startAllMonitors</Method>
<Argument>
<Name>device-category</Name>
<Value>{Dev category String}</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
4.2.20 start-diag-scan
start-diag-scan starts the diag-scan on the specified device categories.
Syntax for CLI
start-diag-scan deviceCategory <Dev category-1>,…,<Dev category-N>
Iterations <Itr-num> haltOnError <halt-string> timeout <timeoutval>
Iterations, haltonError, and timeout are optional arguments.
56
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
The following table provides the start-diag-scan command arguments.
Table 4-9 start-diag-scan
Argument
Data Type
Description
Dev category-N
String
Name of the device category. You can specify multiple
device category using comma ’,’ in between.
Itr-num
Integer
Enter the number of times that diag-scan has to run. By
default, value is "1".
Maximum number of iterations that user can specify is
1000.
halt-string
String
Type "Yes" or "No".
haltOnError specifies whether to continue or stop
with test case execution on the occurrence of any error.
By default, value is "No".
timeout-val
Integer
Enter the maximum time period to be taken by each test
to execute.
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>startDiagScan</Method>
<Argument>
<Name>device-category</Name>
<Value>{Dev category String}</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
4.2.21 stop-all-monitors
stop-all-monitors command stops all the monitors of the mentioned device category.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
57
Commands Execution
Syntax for CLI
stop-all-monitors device-category <Dev category>
The following table provides the stop-all-monitors command arguments.
Table 4-10 stop-all-monitors
Argument
Data Type
Description
Dev category
String
Name of the device category.
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>stopAllMonitors</Method>
<Argument>
<Name>device-category</Name>
<Value>{Dev category String}</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
4.2.22 stop-diag-scan
stop-diag-scan stops the currently running diag-scan command.
Syntax for CLI
stop-diag-scan
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
58
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
</Object>
<Method>stopDiagScan</Method>
</InvokeMethod>
</Script>]]>]]>
4.2.23 switch-mode
switch-mode command allows to switch ViewCheck from OOS mode to InService mode and
vice versa.
Syntax for CLI
switch-mode modeVal <x>
The following table lists the switch-mode command arguments.
Table 4-11 switch-mode Arguments
Argument
Data Type
Description
X
string
Possible values are insm and oosd. Parameter given for
the command is case-insensitive.
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>switchMode</Method>
<Argument>
<Name>modeVal</Name>
<Value>oosd</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
59
Commands Execution
Example
BSF(diag-SP_VEE0)#switch-mode modeVal insm
Mode of ViewCheck is successfully changed to INSM
It is recommended to not to run following test cases in OOS mode:

OctBootTest

OctDDR2MemTest
OctRCStressTest
In order to execute these tests, you have to install ViewCheck OOS image on the blade.

4.2.24 version
version command displays the RPM versions of all the ViewCheck packages installed.
Syntax for CLI
version
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>diagnostic</Class>
<Name>SP_VEE0</Name>
</Object>
<Method>showVersion</Method>
</InvokeMethod>
</Script>]]>]]>
60
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
4.3
Test Management and Control Commands
This section describes the CLI commands used for test management and control of diagnostics
tests.
Execute all test management and control commands only after entering a specific device
category.
4.3.1
start-test
start-test command allows to start and run a particular diagnostics test.
Syntax for CLI
start-test testId <Test ID> deviceInstance <Dev Instance> arguments
-t <timeout-val> -Iterations <Itr-num> -Halt-onerror <halt-string>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>startTest</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>testId</Name>
<Value>Test ID</Value>
</Argument>
<Argument>
<Name>arguments</Name>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
61
Commands Execution
<Value>Param1</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
Iterations, haltonError, and timout are optional arguments.
The following table lists the start-test command arguments.
Table 4-12 start-test
4.3.2
Argument
Data Type
Description
Test ID
Integer
Type the unique ID of a particular test that you want to
start.
Dev Instance
Enum
Use list-device-instances command to get the
equivalent enumerated value of supported device
instance.
timeout-val
Integer
Time out value for the test.
Itr-num
Integer
Number of iterations of the test.
halt-string
String
"Yes" or "No" value. if "Yes", the test halts on error. if "No",
the test does not halts.
show-test-help
show-test-help command provides the brief information on how to use a particular test.
This command provides information such as how to start, stop, and query the specified test ID.
Syntax for CLI
show-test-help testId <Test ID>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{dev Cat}</Name>
</Object>
<Method>showTestHelp</Method>
62
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
<Argument>
<Name>testId</Name>
<Value>Test ID</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
The following table lists the show-test-help command arguments.
Table 4-13 show-test-help
4.3.3
Argument
Data Type
Description
Test ID
Integer
Type the unique ID of a particular test to get the details
of it.
list-tests
list-tests command provides a supported list of diagnostics tests on the blade with
associated test IDs.
Syntax for CLI
list-tests
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{dev Cat}</Name>
</Object>
<Method>showTestList</Method>
</InvokeMethod>
</Script>]]>]]>
4.3.4
show-test-status
show-test-status command allows to view the status of a particular test. The status of a
test can be In Progress, Test Execution Completed, Test Stopped, and Test Timed Out.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
63
Commands Execution
Syntax for CLI
show-test-status testId <Test ID> deviceInstance <Dev Instance>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>showTestStatus</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>testId</Name>
<Value>Test ID</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
The following table lists the show-test-status command arguments.
Table 4-14 show-test-status
4.3.5
Argument
Data Type
Description
Test ID
Integer
Type the unique ID of a particular test that you want to
view the status
Dev Instance
Enum
Use list-device-instances CLI command to get
the equivalent enumerated value of supported Device
Instance
show-test-result
show-test-result command allows to view the latest result of a particular test. This
command displays the start and end time of the test, the test status such as Passed, Failed,
Aborted, and Timed Out, and additional test arguments.
64
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
Syntax for CLI
show-test-result testId <Test ID> deviceInstance <Dev Instance>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>showTestResult</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>testId</Name>
<Value>Test ID</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
Table 4-15 show-test-result
4.3.6
Argument
Data Type
Description
Test ID
Integer
Type the unique ID of a particular test that you want to
view the latest result.
Dev Instance
Enum
Use list-device-instances command to get the
equivalent enumerated value of supported device
instance.
stop-test
stop-test command allows to stop or cancel any running diagnostics test.
Syntax for CLI
stop-test testId <Test ID>
deviceInstance <Dev Instance>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
65
Commands Execution
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>stopTest</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>testId</Name>
<Value>Test ID</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
The following table provides the Stop-test command arguments.
Table 4-16 stop-test
66
Argument
Data Type
Description
Test ID
Integer
Type the unique ID of the Test that you want to stop
Dev Instance
Enum
Use list-device-instances CLI command to get
the equivalent enumerated value of supported Device
Instance
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
4.4
Monitoring Commands
The following list of commands are used for management of the InService Monitoring
functionality of ViewCheck.
Execute all commands related to monitors only after entering the specific device category
mode.
4.4.1
show-monitor-id
show-monitor-id command displays the list of parameters that are monitored using the
InService Diagnostic. This command displays default monitor ID values of the parameters also.
Syntax for CLI
show-monitor-id
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>showMonitorId</Method>
</InvokeMethod>
</Script>]]>]]>
This command displays a list of monitors, if supported, only in that particular device
category.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
67
Commands Execution
4.4.2
show-poll-interval
show-poll-interval command displays list of default Poll intervals that are associated
with the monitors. The Poll interval values are in seconds.
Syntax for CLI
show-poll-interval monitorId <Monitor ID> deviceInstance <Dev
Instance>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>showPollInterval</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>monitorId</Name>
<Value>Monitor ID</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
The following table provides the show-poll-interval command arguments.
Table 4-17 show-poll-interval
68
Argument
Data Type
Description
Monitor ID
Integer
Type the unique ID of the monitor of which you want to
view its default Poll interval values, if any.
Dev Instance
Enum
Use list-device-instances command to get
the equivalent enumerated value of supported device
instance.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
4.4.3
start-monitor
start-monitor command allows you to trigger a specific monitor to start monitoring if it
is not already initiated by default.
Syntax for CLI
start-monitor monitorId <Monitor ID> deviceInstance <Dev Instance>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>startMonitor</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>monitorId</Name>
<Value>Monitor ID</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
The following table provides the Start-monitor command arguments.
Table 4-18 start-monitor
Argument
Data Type
Description
Monitor ID
Integer
Type the unique ID of the monitor that you want to
start.
Dev Instance
Enum
Use list-device-instances command to get the
equivalent enumerated value of supported device
instance.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
69
Commands Execution
4.4.4
set-poll-interval
set-poll-interval command is used to set the Poll interval value for monitors.
Syntax for CLI
set-poll-interval monitorId <Monitor ID> deviceInstance <Dev
Instance> pollInterval <PollIntervaLvalue>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>setPollInterval</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>monitorId</Name>
<Value>Monitor ID</Value>
</Argument>
<Argument>
<Name>pollInterval</Name>
<Value>PollInterval Value</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
The following table provides the set-poll-interval command arguments.
Table 4-19 set-poll-interval
70
Argument
Data Type
Description
Monitor ID
Integer
Type the unique ID of the monitor for which you want to
set the Poll interval value.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
Table 4-19 set-poll-interval
4.4.5
Argument
Data Type
Description
Dev Instance
Enum
Use list-device-instances command to get the
equivalent enumerated value of supported device
instance.
PollInterval Value
Integer
Type the Poll interval value for the specified monitor ID.
set-poll-interval-default
set-poll-interval-default command is used to reset the Poll interval value to default
value of a particular monitor.
Syntax for CLI
set-poll-interval-default monitorId <Monitor ID> deviceInstance
<Dev Instance>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>setPollIntervalDefault</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>monitorId</Name>
<Value>Monitor ID</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
71
Commands Execution
The following table provides the set-poll-interval-default command arguments.
Table 4-20 set-poll-interval-default
4.4.6
Argument
Data Type
Description
Monitor ID
Integer
Type the unique ID of the monitor for which you want to
reset the Poll interval value to default value.
Dev Instance
Enum
Use list-device-instances command to get the
equivalent enumerated value of supported device
instance.
stop-monitor
stop-monitor command allows you to trigger a specific monitor to stop monitoring, which
is already in service.
Syntax for CLI
stop-monitor monitorId <Monitor ID> deviceInstance <Dev Instance>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>stopMonitor</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>monitorId</Name>
<Value>Monitor ID</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
72
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
The following table provides the stop-monitor command arguments.
Table 4-21 stop-monitor
4.4.7
Argument
Data Type
Description
Monitor ID
Integer
Type the unique ID of the monitor that you want to stop
monitoring.
Dev Instance
Enum
Use list-device-instances command to get the
equivalent enumerated value of supported device
instance.
set-rate
set-rate command sets the rate of change value for network monitors.
Syntax for CLI
set-rate monitorId <Monitor Id> deviceInstance <Dev Instance> rate
<Rate>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>setRate</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>monitorId</Name>
<Value>Monitor ID</Value>
</Argument>
<Argument>
<Name>rate</Name>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
73
Commands Execution
<Value>Rate</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
The following table provides the set-rate command arguments.
Table 4-22 set-rate
4.4.8
Argument
Data Type
Description
Monitor ID
Integer
Type the unique ID of the monitor for which rate of
change value is to be set.
Dev Instance
Enum
Use list-device-instances command to get the
equivalent enumerated value of supported device
instance.
Rate
Integer
Rate of change value.
show-rate
show-rate command shows the rate of change value of network monitors.
Syntax for CLI
show-rate monitorId <Monitor Id> deviceInstance <Dev Instance>
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>showRate</Method>
<Argument>
<Name>deviceInstance</Name>
<Value>Dev Instance</Value>
</Argument>
<Argument>
<Name>monitorId</Name>
74
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
<Value>Monitor ID</Value>
</Argument>
</InvokeMethod>
</Script>]]>]]>
The following table provides the show-rate command arguments.
Table 4-23 show-rate
4.4.9
Argument
Data Type
Description
Monitor ID
Integer
Type the unique ID of the monitor of which rate of
change value is to be shown
Dev Instance
Enum
Use list-device-instances CLI command to get
the equivalent enumerated value of supported Device
Instance
show-networkcounter-log
show-networkcounter-log command displays the list of network counters on devices
that have crossed the maximum rate value. For more information on command, rate, refer
show-rate on page 74.
Syntax for CLI
show-networkcounter-log
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev Cat}</Name>
</Object>
<Method>showNetworkCounterLog</Method>
</InvokeMethod>
</Script>]]>]]>
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
75
Commands Execution
4.4.10 show-networkerror-log
show-networkerror-log command displays the list of network errors on devices that
have crossed the maximum rate value. For more information on command, rate, refer showrate on page 74.
Syntax for CLI
show-networkerror-log
Syntax for XML
<Script>
<InvokeMethod>
<Object>
<Class>deviceCategory</Class>
<Name>SP_VEE0-{Dev cat}</Name>
</Object>
<Method>showNetworkErrorLog</Method>
</InvokeMethod>
</Script>]]>]]>
4.4.11 exit
exit command allows you to exit from the ViewCheck CLI.
Syntax for CLI
exit
Syntax for XML
<Script>
<Command name="Exit"/>
<Script>]]>]]>
76
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
4.5
InService Monitoring Specifics
The In Service Monitoring of ViewCheck provides functionality to:

Monitor Hardware Device Status

Monitor Device Critical Errors
Note: Currently monitors are supported only on Service Processor.
4.5.1
Monitoring Hardware Device Status
InService Monitoring also periodically polls for various devices status on the blade. They are

Storage Device HDD Health Status

Network Devices Counter Statistics

Network Devices Error Statistics
Each of the above is identified by a unique Monitor ID. For more information about Monitor ID,
refer Monitor ID on page 18.
The default Poll Interval for monitoring each of the Monitor ID is set to 10 seconds. Commands
are provided to edit the default settings.
For more information on the commands provided for InService Monitoring, refer Monitoring
Commands on page 67.
The following table provides list of monitor IDs and device instances for each of the monitors
being monitored on ATCA-9405.
Table 4-24 Monitors
Monitor Description
Monitor
ID
Valid Device Instances
Remarks
HDD Health Status
1010
sda1 and sda2
Monitors the health status of the
sda1 to sda2 partitions on the
HDD and reports.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
77
Commands Execution
Table 4-24 Monitors (continued)
4.5.2
Monitor Description
Monitor
ID
Network Errors
Network Counters
Valid Device Instances
Remarks
1020
eth0(62),eth1(63),eth2(
64)
Monitors the various error
counters for each of the Network
Device Instances and provides an
error counter exceeds the rate of
change.
1021
eth0(62),eth1(63),eth2(
64)
Monitors the various counters for
each of the Network Device
Instances
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 InService Monitoring Module of ViewCheck looks for the occurrence of these notifications
and on detection sends a notification to XML.
The device errors are captured and are identified uniquely with their ERROR IDs. For definition
of ERROR ID, refer Error ID on page 18.
78
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
4.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.
Before starting any PP related OOSD diagnostics test, make sure that VLAN interface
(example, eth1.21) reaching octeon is properly configured with an IP.
4.6.1
CPU

CpuBurnTest (SP): This test 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.

OctDDR2MemTest (SP): This test executes the hw-ddr2 memory test on Octeons with
ECC check. This includes below set of memory tests:
–
Marching Rows
–
Random Data Test
–
Random XOR Test
–
Self Address Test
–
March C-Solid Bits Test
–
March C-Checkerboard Test
–
Walking Ones Left Test
–
Walking Ones Right Test
–
Walking Zeroes Left Test
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
79
Commands Execution
–
Walking Zeroes Right Test
–
Random XOR Test
The OctDDR2Test (SP) tests memory up to 7692 Megabytes.
It does not check the memory range where boot loader and the test program itself resides.
4.6.2
4.6.3
80

OctRCStressTest (SP): This test executes the hw-rc stress test on Octeon cores for 2
minutes. This test tries to simultaneously run as much of it internal machinery as possible
by performing BIST status check of all cores.

CpuBenchMark: Tests different arithmetic operations and gives the results.
HDD

DiskBadBlksTest (SP): Searches for bad blocks on a device (usually a disk partition).

DiskCntlrTest (SP & PP): Verifies the random data written on disks remains unchanged. It
verifies only IDE and SCSI controllers that are associated with mounted file systems. Disk
controllers associated with read-only mounted file systems are not verified.
Memory

MemCntlrTest (SP & PP): Randomly writes to areas of memory, then reads the memory
back to ensure the written values remain unchanged.

RandomMemoryTest (SP & PP): Performs stress testing on the memory subsystem. This
test is effective in finding intermittent and non-deterministic faults. The problems in other
hardware areas such as overheating CPU, out-of-specification power supply, and so on can
cause memory faults.

MemBandwidth: Measures the ability to copy, read, and write data over a varying set of
sizes.

MemLatency: Measures the time taken by the memory to respond with the data for readrequest.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
4.6.4
4.6.5
OS

MemSepTest (SP & PP): Ensures that user space programs cannot read and write to areas
of memory utilized by items such as Video RAM and kernel code.

SupervisorInstrTest (SP): Ensures that the enforcement of the property that privileged
instructions should only be in supervisor mode is still in effect. The set of privileged
instructions tested to confirm this is architecture dependent.

DmesgCheckTest (SP & PP): Checks for user-given keywords in the kernel dmesg logs.
PCI

4.6.6
4.6.7
PCIScanTest (SP): Enumerates all active PCI devices in the blade and ensures board default
configuration is active. This test need to be executed under supervisory mode.
IPMC

IPMITest (SP): Executes basic IPMI commands and ensures the basic IPMI controller, IPMI
bus functionalities are working properly by reading the response back.

IPMCSENSOREVENTTest (SP): Verifies IPMC Event generation.
NETWORK

EthLinkTest (SP & PP): Verifies Ethernet device (for example: eth0, eth1, eth2, etc...) link
status (active/inactive) and also captures various statistics of Ethernet device.

FloodPingTest (SP & PP): Uses the ICMP protocol’s mandatory ECHO_REQUEST
datagram to elicit an ICMP_ECHO_RESPONSE from a host or gateway.

EthStatsTest (SP): Tests basic network packet consistency, that is, checks network Rx, Tx
errors, generates a warning if errors are less than or equal to 100 and marks the test as fail
if number of errors are more than 100.

NetworkCntlrTest (SP): Verifies random data transmitted and also the data received for
each configured network device. It verifies only Ethernet and token ring devices that are
configured and active. The asynchronous devices are not verified.

SfpDetectionTest(SP): Enumerates all SFP modules connected to SFP ports of blade and
their operational speeds.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
81
Commands Execution

SwitchTempTest (SP): Gets the temperature (in degrees Celsius and can be negative) of
the Ethernet switch. Obtained temperature value will be compared with the minimum and
maximum values of the chipset given in the specification.

NwMemAcessTest (SP): Accesses various memory areas (listed below), accessible by the
device and performs Pattern read/write operations (incremental values, random values
and 0xAA, 0x55) on the memory area. This test ensures the device is able to access those
memories for read and write operations. Frequent failures of this test can be treated as
malfunctioning hardware.
Applicable memory types:
–
Buffer DRAM
–
MAC table memory
–
VLAN table memory

NwCntlrRegAcessTest (SP): Tests the ability to read and write into device registers that
are accessible by writing various patterns ( 0xAA_0x55, Random value, Bit Toggle,
incremental) in to them. This test ensures the accessibility of registers by Switch. Frequent
failures of this test can be treated as malfunctioning hardware.

TcamSelfTest (SP): Invokes the built-in self test of the Ternary Content Addressable
Memory (TCAM) on both policy control lists and router sections. This test does not restore
data relevant TCAM area. This test ensures TCAM accessible to the switch. Frequent
failures of this test can be treated malfunctioning hardware.
The TcamSelfTest is destructive test and cannot be run during presence of network traffic.
Board reboot is required after every run of this test.
82

NetworkThroughputServ: Starts the server for network throughput testing.

NetworkThroughput: Tests the network throughput.

NetworkTxBenchMark (SP): Checks the transmission rate of interface.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Commands Execution
4.6.8
4.6.9
FPGA

CPLDTest (SP): Checks the accessibility of the CPLD device by performing write and read
operations on scratch registers of CPLD device.

FPGATest (SP): Checks the accessibility of the FPGA device, by performing write and read
operation on scratch registers of FPGA device.
I2C

I2CProbeTest (SP): Mod-probes an I2C module and checks for default I2C devices on
board.
4.6.10 USB

USBTest (SP): Accesses the USB partition repeatedly and writes, reads, and verifies the
data.
4.6.11 RTC

RTCTest (SP): Checks for proper functioning of real time clock.
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
83
Commands Execution
84
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Appendix A
A
Related Documentation
A.1
Artesyn Embedded Technologies - Embedded
Computing Documentation
The publications listed below are referenced in this manual. You can obtain electronic copies of
Artesyn Embedded Technologies - Embedded Computing publications by contacting your
local Artesyn sales office. For released products, you can also visit our Web site for the latest
copies of our product documentation.
1. Go to www.artesyn.com/computing/support/product/technical-documentation.php.
2. Under FILTER OPTIONS, click the Document types drop-down list box to select the type of
document you are looking for.
3. In the Search text box, type the product name and click GO.
Table A-1 Artesyn Embedded Technologies - Embedded Computing Publications
Document Title
Publication Number
ATCA-9405 BBS Programmer’s Reference
6806800R18
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
85
Related Documentation
86
ViewCheck on ATCA-9405 Installation and Use (6806800S51F)
Artesyn Embedded Technologies, Artesyn and the Artesyn Embedded Technologies logo are trademarks and service marks of Artesyn Embedded Technologies, Inc.
All other product or service names are the property of their respective owners.
©
2014 Artesyn Embedded Technologies, Inc.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement