86A143FL10 Remote Hardware Management CLI Reference Guide

bullion
bullion S
Remote
Hardware
Management
CLI
Reference
Guide
86 A1 43FL 10 - December 2016 -1
The following copyright notice protects this book under Copyright laws which prohibit such actions
as, but not limited to, copying, distributing, modifying, and making derivative works.
Copyright ©Bull SAS 2016

Printed in France
Trademarks and Acknowledgements
We acknowledge the right of proprietors of trademarks mentioned in this manual.

All brand names and software and hardware product names are subject to trademark and/or
patent protection.
Quoting of brand and product names is for information purposes only and does not represent
trademark and/or patent misuse.
Hardware
December 2016
Bull Cedoc
357 avenue Patton
BP 20845
49008 Angers Cedex 01
FRANCE
The information in this document is subject to change without notice. Bull will not be liable for errors contained
herein, or for incidental or consequential damages in connection with the use of this material.
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . p‐1
Intended Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . p‐1
Chapter 1. Introducing the Hardware Management CLIs . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1. Connections and Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.1.1. Remote Hardware Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.1.2. Local Hardware Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2. Installing the Hardware Management CLI for Linux . . . . . . . . . . . . . . . . . . . . . 1-4
1.3. Installing the Hardware Management CLI for Windows . . . . . . . . . . . . . . . . . . 1-5
1.4. Editing the BSMCLI Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Chapter 2. Commands for bullion S server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1. bsmAddHardwareExclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.1.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.1.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.1.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2. bsmBios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.2.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.2.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.2.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.3. bsmBiosLog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
2.3.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
2.3.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
2.3.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.4. bsmBiosSettings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.4.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.4.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.4.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2.5. bsmBMCcfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
2.5.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
2.5.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
2.5.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
2.6. bsmBootDevice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
2.6.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
2.6.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
2.6.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
2.7. bsmevent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
2.7.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
2.7.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
2.7.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
2.8. bsmfru ................................................................ 2-20
2.8.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
2.8.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
2.8.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Contents i
2.9. bsmFwGlobalUpg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
2.9.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
2.9.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
2.9.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
2.10. bsmGetConfParam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
2.10.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
2.10.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
2.10.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
2.11. bsmGetFunctionalProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
2.11.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
2.11.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
2.11.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
2.12. bsmGetHardwareExclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
2.12.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
2.12.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
2.12.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
2.13. bsmGetModuleLevelInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
2.13.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
2.13.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
2.13.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
2.14. bsmGetPartitionLevelInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
2.14.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
2.14.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
2.14.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
2.15. bsmGetPlatformLevelInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
2.15.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
2.15.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
2.15.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
2.16. bsmGUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
2.16.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
2.16.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
2.16.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
2.17. bsmidentify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
2.17.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
2.17.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
2.18. bsminfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
2.18.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
2.18.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
2.18.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
2.19. bsmlog ................................................................ 2-57
2.19.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
2.19.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
2.19.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
2.20. bsmOSpm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
2.20.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
2.20.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
2.20.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
2.21. bsmpower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
2.21.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
2.21.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
2.21.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
ii Reference Guide
2.22. bsmRegDump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
2.22.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
2.22.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
2.22.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
2.23. bsmRemoveHardwareExclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72
2.23.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72
2.23.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72
2.23.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73
2.24. bsmreset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74
2.24.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74
2.24.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74
2.24.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75
2.25. bsmResetAllEMMPartition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
2.25.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
2.25.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
2.25.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
2.26. bsmsdr ................................................................ 2-77
2.26.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77
2.26.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78
2.26.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78
2.27. bsmseld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-84
2.27.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-84
2.27.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-84
2.27.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-85
2.28. bsmsensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86
2.28.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86
2.28.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-87
2.28.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-87
2.29. bsmSetConfParam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-89
2.29.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-89
2.29.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-90
2.29.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-90
2.30. bsmSetPartitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-93
2.30.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-93
2.30.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-94
2.30.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-94
2.31. bsmSetPlatformLevelParam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-95
2.31.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-95
2.31.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-95
2.31.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-96
2.32. bsmsnapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97
2.32.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97
2.32.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97
2.32.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97
2.33. bsmsol ................................................................ 2-99
2.33.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-99
2.33.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100
2.33.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100
Contents iii
2.34. bsmUCMcmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-101
2.34.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-101
2.34.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-101
2.34.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-101
Chapter 3. Field Hardware Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1. bsmMAINTBMCcfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.1.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.1.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.1.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2. bsmMAINTDisplayModuleConfigur ation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.2.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.2.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.2.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.3. bsmFWupg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.3.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.3.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.3.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.4. bsmPSUcmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.4.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.4.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.4.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Appendix A. Server ON / OFF Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Appendix B. User/Password Internal Authentication File . . . . . . . . . . . . . . . . . . . . . . . B-1

B.1. User/Password Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
B.2. bsmcfg_auth_cmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
B.2.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
B.2.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
B.2.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Appendix C. Optional Equipment Management CLIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

C.1. bsmPDUpower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
C.1.1. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
C.1.2. General Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
C.1.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
iv Reference Guide
Preface
This guide describes the Hardware Management CLIs (Command Line Interface)
for bullion S server.
Note You are advised to consult the Bull Support Web site for the most
uptodate product information, documentation, firmware updates,
software fixes and service offers:
http://support.bull.com
Important ATTENTION: Please read carefully the safety instructions

before you perform the procedures described in this
manual.
ATTENTION : Merci de lire attentivement les consignes de
sécurité avant d'effectuer les procédures décrites dans ce
manuel.
ACHTUNG : Bitte lesen Sie sorgfältig die angegebenen
Sicherheitshinweise, bevor Sie die Verfahren in diesem
Handbuch beschrieben durchführen.
Multilingual Safety Notices Guide, 86 X1 12FL
Intended Readers
This guide is intended for System Administrators and Operators in charge of
managing systems locally and remotely and of writing server management batch
scripts.
Preface p‐1
Chapter 1. Introducing the Hardware Management
CLIs
This chapter provides general information about the BSM Hardware Command
Line Interface (CLI) scriptable management commands for hardware
management and configuration. It includes the following topics:
• Connections and Prerequisites, on page 1-2
• Installing the Hardware Management CLI for Linux, on page 1-4
• Installing the Hardware Management CLI for Windows, on page 1-5
• Editing the BSMCLI Configuration File, on page 1-8

manual.
manuel.
Chapter 1. Introducing the Hardware Management CLIs 1-1

1.1. Connections and Prerequisites
The Hardware Management CLIs package provides an easy Command Line
Interface (CLI) for local or remote hardware management and automation
scripts. The following architectures and Operating Systems are supported:
• IA32
• IA64
• x64
• Linux
• Windows using a Cygwin context
1.1.1. Remote Hardware Management

Different Out-Of-Band network protocols are used to connect remotely to the
equipment management controllers. These protocols vary according to
equipment type:
• IPMIoverLAN
• SNMP
• SSH
• …
The model, host, user and password arguments MUST be used for
Out-Of-Band connections.
Most commands allow the use of an internal authentication file for easy
authentication. This file is created with the bsmcfg_auth_cmd.sh command,
detailed in Appendix B. Alternatively, the -p password argument can be used.
Note IPMI connection is established with the lanplus interface using cipher
suite IDs for authentication, integrity, and encryption algorithms. The
default cipher suite ID is 3 and specifies the RAKP‐HMAC‐SHA1
authentication, HMAC‐SHA1‐96 integrity, and AES‐CBC‐128 encryption
algorithms.
For Windows using a Cygwin context, all the packages required for internal
authentication are pre-installed.
For Linux, the following packages are required for internal authentication and
must be installed in the the bin sub-directory of the BSMHW_NG package
install directory (Default: /opt/BSMHW_NG/bin):
• perl‐XML‐LibXML
• perl‐XML‐LibXML‐Common
• perl‐XML‐SAX
• perl‐XML‐NamespaceSupport
1-2 Reference Guide

1.1.2. Local Hardware Management
The ipmidrv driver is used to connect locally to the equipment management
controllers.
The model argument is mandatory for In-Band connections. The host,
username and password arguments MUST NOT be used for In-Band
connections.
For Windows using a Cygwin context, all drivers and libraries required for IPMI
management of a local system are pre-installed.
For Linux, IPMI management of a local system requires the installation and
configuration of the Linux OpenIPMI driver and the installation of the OpenIPMI
library.

1.2. Installing the Hardware Management CLI for Linux
Install the BSM Hardware CLI RPM package provided on the Resource and
Documentation DVD:
1. Insert the DVD in the drive and browse to the directory containing the RPM
package:
Resources > Software > Linux > BSMHW_NG<release>.<arch>.rpm
2. Copy the RPM package and install by launching:
rpm -i BSMHW_NG<release>.<arch>.rpm
where the values for <arch>.rpm are:

i386.rpm for IA32
ia64.rpm for IA64
x86_64.rpm for x64
3. Launch the Hardware Management CLI.
1-4 Reference Guide

1.3. Installing the Hardware Management CLI for Windows
Install the BSM Hardware CLI BSMHW_NG<version>.exe executable file
provided on the Resource and Documentation DVD. This will install both the
Cygwin environment and the Hardware Management CLI.
1. Double click the executable file. The Welcome to BSM HW CLI Setup
dialog opens.
Figure 1-1. BSM HW CLI Installation Setup

2. Click Next to continue. The Choose Destination Location dialog opens.
Figure 1-2. BSM HW CLI Installation Destination

3. Click Next to install in the default destination folder or click Browse to
select the destination folder of your choice and then click Next to continue.
The Setup Complete dialog opens.
Figure 1-3. BSM HW CLI Installation Setup Complete

4. Click Finish to complete installation.
5. Perform post installation tasks:
a. Open a command window.
Figure 1-4. BSM HW CLI Post installation

b. Select the install directory:
C:
cd Program Files/bull/BSM HW CLI/engine/bin
c. Launch the Cygwin bash environment:

bash login i
1-6 Reference Guide

d. Go to the /bin directory to list the files:
cd /bin
Figure 1-5. Launching BSM HW CLI on Windows

6. Launch the Hardware Management CLI.
For details, refer to the BSM HW Management CLI Commands documentation.

1.4. Editing the BSMCLI Configuration File
To suit your needs, you may change the following parameters in the
bsmcli.cfg.custom.sh.tmpl file:
CYPHER_SUITE_ID: this parameter specifies the authentication, integrity
and confidentiality algorithms used when connecting
via the lanplus interface. The default value is 3.
ME_CHANNEL: this parameter specifies the destination channel for
IPMI requests. The default value is 0x06.
ME_ADDRESS: this parameter specifies the IPMB address for IPMI
requests. The default value is 0x2c.
1. Rename the file, as shown, so that it can be called by the BSM CLI scripts.
$ cd /opt/BSMHW_NG/bin
$ mv bsmcli.cfg.custom.sh.tmpl bsmcli.cfg.custom.sh
2. Edit the bsmcli.cfg.custom.sh file as required.

3. Save the file.
1-8 Reference Guide

Chapter 2. Commands for bullion S server
This chapter describes the Hardware Management CLIs available for bullion S
server:
• bsmAddHardwareExclusion , on page 2-3
• bsmBios, on page 2-6
• bsmBiosLog, on page 2-8
• bsmBiosSettings , on page 2-11
• bsmBMCcfg, on page 2-14
• bsmBootDevice, on page 2-16
• bsmevent, on page 2-18
• bsmfru, on page 2-20
• bsmFwGlobalUpg, on page 2-24
• bsmGetConfParam, on page 2-34
• bsmGetFunctionalProfile , on page 2-37
• bsmGetHardwareExclusion , on page 2-38
• bsmGetModuleLevelInfo , on page 2-39
• bsmGetPartitionLevelInfo , on page 2-41
• bsmGetPlatformLevelInfo , on page 2-43
• bsmGUID, on page 2-46
• bsmidentify, on page 2-48
• bsminfo, on page 2-49
• bsmlog, on page 2-57
• bsmOSpm, on page 2-62
• bsmpower, on page 2-66
• bsmRegDump, on page 2-69
• bsmRemoveHardwareExclusion , on page 2-72
• bsmreset, on page 2-74
• bsmResetAllEMMPartition, on page 2-76
• bsmsdr, on page 2-77
• bsmseld, on page 2-84
• bsmsensor, on page 2-86
• bsmSetConfParam, on page 2-89
• bsmSetPartitions, on page 2-93
• bsmSetPlatformLevelParam, on page 2-95
• bsmsnapshot, on page 2-97
• bsmsol, on page 2-99
Chapter 2. Commands for bullion S server 2-1

manual.
manuel.
2-2 Reference Guide

2.1. bsmAddHardwareExclusion
The bsmAddHardwareExclusion command is used to exclude hardware
components defined with -C option.
When the command is accepted, the return code is 0. If the command fails, the
return code is -1.
2.1.1. Options
-h Displays command usage
l level Specifies the message severity to be logged in syslog
0: no message is logged (default)
1: only the FAILED completion of the command is
logged
3: FAILED and successful completion of the command
are logged
m interface Target server interface: lanplus
H host Module IP address or DNS name
u user MC user
p password MC user password
C componentlist List of hardware components for exclusion
Components must be listed in quotes and separated
by a blank
-Y cipher Cipher suite ID to be used by lanplus interface: from 0
to 14 according to the security level
Default is 3: Authentication (RAKP-HMAC-SHA1),
Integrity (HMAC-SHA1-96), Confidentiality
(AES-CBC-128)
-o outfile Output file name to which stdout and stderr outputs
are redirected

2.1.2. General Syntax
bsmAddHardwareExclusion.sh [-h] [-l level]m interface -H host -C
componentList [-u user] [-p password] [-Y cipher] [-o outfile]
C componentlist List of hardware components for exclusion.
by a blank
Possible values:
MMRx_CHy_DIMMz: RDIMMs exclusion
x from 0 to 7
y from 0 to 1
z from 0 to 2
XQPIx: XQPI port exclusion
x from 0 to 6
moduleX: module exclusion
X from 0 to 7
ultracapa: ultracapacitor exclusion
2.1.3. Examples
This section includes examples for the component list option.
2.1.3.1. Exclude a XQPI Port

Command
$ bsmAddHardwareExclusion.sh -m lanplus –H X.X.X.X –u super -p <password> -C XQPI0
Output
---------------------------------------------------------------------------
XQPI0 excluded
A port of module 1 is also excluded
---------------------------------------------------------------------------
2.1.3.2. Exclude some RDIMMs

Command
$ bsmAddHardwareExclusion.sh -m lanplus –H X.X.X.X –u super -p <password> -C 'MMR0_CH1_DIMM1
MMR1_CH1_DIMM1 MMR4_CH0_DIMM2 MMR5_CH0_DIMM1'
Output
---------------------------------------------------------------------------
MMR0_CH1_DIMM1 (D4) excluded
---------------------------------------------------------------------------
2-4 Reference Guide

2.1.3.3. Exclude a Module
Command
$ bsmAddHardwareExclusion.sh -m lanplus –H X.X.X.X –u super -p <password> -C module0
Output
---------------------------------------------------------------------------
module0 excluded
---------------------------------------------------------------------------
2.1.3.4. Exclude Ultracapacity

Command
$ bsmAddHardwareExclusion.sh -m lanplus –H X.X.X.X –u super -p <password> -C ultracapa
Output
---------------------------------------------------------------------------
ultracapa excluded
---------------------------------------------------------------------------

2.2. bsmBios
The bsmBios command is used to manage the module BIOS.
return code is -1.
2.2.1. Options
h Displays command usage
l level Specifies the severity of the messages to be logged
into syslog
logged
are logged
-a action Possible values:
getBiosInfo: returns BIOS image information
getMemorySize: gets the BIOS memory size saved in
the BMC
enterBiosSetup: sets a BIOS boot option to interrupt
the BIOS setup process at the next reboot. This
interruption can be used to enter, check and/or modify
BIOS setup parameters
u user MC user
(AES-CBC-128)
o outfile Output file name to which stdout and stderr outputs
are redirected

bsmBios.sh [h] [l level] [m interface] H host -a action [-F File] [u
user] [p password] [Y cipher] [o outfile]
2-6 Reference Guide

2.2.3. Examples
This section includes examples for the action option.
2.2.3.1. Get BIOS Image Details

Command
$ bsmBios.sh -H X.X.X.X -u super -p <password> -a getBiosInfo
Output
---------------------------------------------------------------------------
firmware version of BIOS : LCX05.013.06.135
---------------------------------------------------------------------------
2.2.3.2. Get BIOS Memory Size Details

Command
$ bsmBios.sh -H X.X.X.X -u super -p <password> -a getMemorySize
Output
---------------------------------------------------------------------------
BIOS Memory Size is 5701632 Mbytes.
---------------------------------------------------------------------------

2.3. bsmBiosLog
The bsmBiosLog command is used to list, get, remove and get the size of BIOS
log message files present on the SD card.
return code is -1.
2.3.1. Options
l level Specifies the message severity to be logged in syslog.
m interface Target server interface: ipmilan, lanplus (default is
lanplus)
H host Chassis IP address or DNS name
u user MC user
to 14 according to the security level.
(AES-CBC-128).
a action Possible values:
list: returns the names of the BIOS log files on the SD
card
get: copies the specified BIOS log file, or all BIOS log
files, into the specified directory (default /tmp
directory)
size: returns the size of the specified BIOS log file
rm: removes the specified BIOS log file, or all BIOS
log files, from the SD card
d directory Directory path for destination (default /tmp)
f filename BIOS log file name on SD card
are
redirected

bsmBiosLog.sh [h] [l level] [m interface] H host [u user] [p password]
[Y cipher] [f filename] [d directory] [o outfile] a action arglist
2-8 Reference Guide

2.3.3. Examples
2.3.3.1. List the BIOS Log Files

Syntax
bsmBiosLog.sh [h] [l level] [m interface] H host [u user p password]
[Y cipher] a list [o outfile]
Command
$ bsmBiosLog.sh H X.X.X.X u super p <password> a list
Output
---------------------------------------------------------------------------
rwxrxrx 1 root root 1258119 Aug 4 10:19 BIOS_LOG_19700101_00_00_52.log
rwxrxrx 1 root root 614553 Aug 4 12:38 BIOS_LOG_19700101_00_00_54.log
---------------------------------------------------------------------------
2.3.3.2. Copy BIOS Log Files

Syntax
[Y cipher] a get [-n number] [f filename] [d directory] [o outfile]
Options
-a get gets all the BIOS log files
-a get -n number gets the required number of most recent BIOS log
files
-a get -f filename gets the required BIOS log file
Command
In the following example, all the BIOS log files will be copied in the /tmp/BIOS
directory:
$ bsmBiosLog.sh H X.X.X.X u super p <password> a get -d /tmp/BIOS
This command returns no output.

Command
In the following example, the specified BIOS log file will be copied in the default
/tmp directory, as no path is specified for destination:
$ bsmBiosLog.sh H X.X.X.X u super p <password> a get f BIOS_LOG_19700101_00_00_52.log
2.3.3.3. Get BIOS Log File Size

Syntax
[Y cipher] a size f filename [o outfile]
Command
$ bsmBiosLog.sh H X.X.X.X u super p <password> a size f BIOS_LOG_19700101_00_00_52.log
Output
---------------------------------------------------------------------------
Size of file BIOS_LOG_19700101_00_00_52.log = 1258119(bytes)
---------------------------------------------------------------------------

2.3.3.4. Remove BIOS Log Files from SD Card
Syntax
[Y cipher] a rm f <filename | all> | -M month | -n number[o outfile]
Options
-a rm -f all removes all the BIOS log files
-a rm -f filename removes the required log file
-a rm -M month removes the BIOS log files dated the required month.
The month is specified with the three first letters of
the month (Jan,Feb…)
-a rm -n number removes the required number of oldest BIOS log files
Command
In the following example, all the BIOS log files will be removed from SD card:
$ bsmBiosLog.sh H X.X.X.X u super p <password> a rm -f all

Command
In the following example, the specified BIOS log file will be removed from SD
card:
$ bsmBiosLog.sh H X.X.X.X u super p <password> a rm f BIOS_LOG_19700101_01_01_18.log
2-10 Reference Guide

2.4. bsmBiosSettings
The bsmBiosSettings command is used to manage the BIOS settings.
return code is -1.
Note Refer to the file BIOSXnn_SetupOptions.xlsx provided on the Resource

and Documentation DVD for the list of BIOS settings.
2.4.1. Options
into syslog
logged
are logged
list: returns the BIOS settings
get: gets the required BIOS settings values
set: sets the required settings
reset: sets the BIOS settings to the default values
u user MC user
(AES-CBC-128)
are redirected

bsmBiosSettings.sh [h] [l level] [m interface] H host [u user] [p
password] [Y cipher] [o outfile] -a action arglist

2.4.3. Examples
2.4.3.1. Get all the BIOS Settings Values

Syntax
password] [Y cipher] [o outfile] -a list
Command
$ bsmBiosSettings.sh -H X.X.X.X -u super -p <password> -a list
Output
---------------------------------------------------------------------------
ACPIHP_1 :0
ACPIHP_10 :0
ACPIHP_11 :0
ACPIHP_12 :0
ACPIHP_13 :0
ACPIHP_14 :0
ACPIHP_15 :0
…
vmseRmPatternLength :0
vunitClkGating :0
wrVrefCenter :0
zqCalEn :1
---------------------------------------------------------------------------
2.4.3.2. Get the Required BIOS Settings Values

Syntax
password] [Y cipher] [o outfile] -a get -n settingName | -f filename
Options
n settingname list of required BIOS settings. Several BIOS setting
can be put in quotes and separated with space
-f filename file with the required BIOS settings. Several BIOS
settings can be put in the file, one per line
Command
$ bsmBiosSettings.sh -H X.X.X.X -u super -p <password> -a get 'serialDebugTrace nbErrTh'
Output
---------------------------------------------------------------------------
SerialDebugTrace :0
EnErrTh :255.
---------------------------------------------------------------------------
Command
$ bsmBiosSettings.sh -H X.X.X.X -u super -p <password> -a get -f myfile
Input file format example:

SerialDebugTrace
EnErrTh

2.4.3.3. Set BIOS Settings Values
Syntax
password] [Y cipher] [o outfile] -a set -n values | -a set -f filename
Options
-n settingvalues list of pairs consisting of the BIOS setting and its
value, put in quotes separated with space. Several pair
can be put in quotes and separated with space
-f filename file with the list of BIOS settings and their value.
Several BIOS settings can be put in the file, one per
line. The format is the same as the list action result
Command
$ bsmBiosSettings.sh -H X.X.X.X -u super -p <password> -a set -n 'serialDebugTrace 1'
Output
---------------------------------------------------------------------------
Setting serialDebugTrace is OK
---------------------------------------------------------------------------
Command
$ bsmBiosSettings.sh -H X.X.X.X -u super -p <password> -a set -n 'serialDebugTrace 1 nbErrTh 0'
Output
---------------------------------------------------------------------------
Setting serialDebugTrace is OK
Setting nbErrth is OK
---------------------------------------------------------------------------
Command
$ bsmBiosSettings.sh -H X.X.X.X -u super -p <password> -a set -f myfile
Input file format example:

SerialDebugTrace :0
EnErrTh :15
2.4.3.4. Reset BIOS Settings Values

Syntax
password] [Y cipher] [o outfile] -a reset [-q]
Options
-q Quiet mode. No acknowledgement for reset action

2.5. bsmBMCcfg
The bsmBMCcfg command is used to backup the BMC configuration parameters
of all modules included in a partition or to restore the BMC configuration
parameters for a module.
A backup copies three data types into three different files: configuration
parameters (config file), alert filters (pef file) and system parameters (system
file). You must specify the data type when restoring data.
return code is -1.
Note The full path for the backup files is generated as follow:
/var/BSMHW/<partition name>/<module serial
number>/<date>_<time>/
2.5.1. Options
logged
are logged
u user MC user
backup: backups the BMC configuration parameters of
all partition modules
restore: restores the BMC configuration parameters for
a module
-D backupDir Full directory path for backup files (used with restore
action)
-F file Type of file to be restored. Possible values are config,
pef, system (used with restore action)
-M module Module identifier (used with restore action)
(AES-CBC-128)
are redirected

bsmBMCcfg.sh [-h] [-l level][m interface] -H host -a action [-F file -D
backupDir -M module] [-u user] [-p password] [-Y cipher] [-o outfile]
2.5.3. Examples
2.5.3.1. Backup all BMC Configuration Parameters

Command
$ bsmBMCcfg.sh -m lanplus –H X.X.X.X –u super -p <password> -a backup
Output
---------------------------------------------------------------------------
backup into /var/BSMHW_NG/XXX.XXX.XXX.XXX/SP1426043/141203_100015/config
successful.
backup into /var/BSMHW_NG/XXX.XXX.XXX.XXX/SP1426043/141203_100015/perf
successful.
backup into /var/BSMHW_NG/XXX.XXX.XXX.XXX/SP1426043/141203_100015/system
successful.
---------------------------------------------------------------------------
2.5.3.2. Restore BMC Configuration Parameters for a Module

Command
$ bsmBMCcfg.sh -m lanplus –H X.X.X.X –u super -p <password> -a restore -F pef -D
'/var/BSMHW_NG/XXX.XXX.XXX.XXX/SP1426043/141203_100015'
Output
---------------------------------------------------------------------------
Command complete. Please, do not lauch a command immediately. The BMC is
restarting.
---------------------------------------------------------------------------

2.6. bsmBootDevice
The bsmBootDevice command is used to get and set the BIOS boot device
configuration.
return code is -1.
Note If the system is running, the setting command will only apply to the
next power on. You are advised to power off the system, launch the
command and power on the system.
2.6.1. Options
-d device Boot device. Possible values:
bios: BIOS displays the front page and waits for user's
input
pxe: BIOS tries to boot on the first network card in
the boot manager boot list
disk: BIOS tries to boot on the first hard drive in the
boot manager boot list
diag: BIOS EFI shell
none: BIOS uses its own boot device
-i instanceNumber Instance number of boot devices disk and pxe.
-O option[=value] Specifies an option and its value. Several options can
be separated with comma(s). Possible options:
persistent or persistent=yes: permanently
persistent=no: temporary, for next boot only
efiboot or efiboot=yes: EFI boot
efiboot=no: no EFI boot
u user MC user
(AES-CBC-128)
are redirected
Note Instance selection only works for device disk or pxe.

Instance 0 refers to the first instance. So if you want to boot pxe 0 by
default, the right value for -i parameter will be -i 0.

bsmBootDevice.sh [h] [l level] [m interface] H host [-d device] [-i
instanceNumber] [-O options] [u user] [p password] [Y cipher] [o outfile]
2.6.3. Examples
2.6.3.1. Get the Boot Device Configuration

Command
$ bsmBootDevice.sh -H X.X.X.X -u super -p <password>
Output
---------------------------------------------------------------------------
Boot_Device PXE
BIOS_Boot_Type EFI
Boot_Flags_Persistent Yes
Device_Instance_Selector External0
CMOS_Clear No
---------------------------------------------------------------------------
2.6.3.2. Set the Boot Device Configuration

Command
$ bsmBootDevice.sh -H X.X.X.X -u super -p <password> -d pxe -O persistent=no

Command
$ bsmBootDevice.sh -H X.X.X.X -u super -p <password> -d pxe -i 0 -O efiboot,persistent

2.7. bsmevent
The bsmevent command is used to add sensor events to the SEL repository.
return code is -1.
2.7.1. Options
l level Specifies the severity of the messages to be logged in
syslog
logged
are logged
setEvent: inserts events attached to a sensor in the
SEL repository
testEvent: tests trap events sent without writing
messages in the SEL repository
-u user MC user
-s sensorID Sensor identifier (put between doublequotes)
-d landest Alert destination number
This can be obtained by running: bsminfo a
get_lan_alert_dest
-b state State for the sensor identifier (default is list). Possible
states: list, lnr, lcr, lnc, unc, ucr, unr, present
-e eventDir Direction taken by the state (default is assert)
-i i2csaAdr Address of the device generating the event (default is
the BMC address)
(AES-CBC-128)
are redirected

bsmevent.sh [h] [l level] a action m interface H host [u user]
[p password] s sensorID [b state] [e eventDir] [i i2csaAdr]
[-d landest] [Y cipher] [o outfile]

2.7.3. Examples
2.7.3.1. Insert Events Attached to a Sensor into the SEL Repository

Command
$bsmevent.sh m lanplus H X.X.X.X u super p bull a setEvent b list s "CPU_0 DTS Temp."
Output
---------------------------------------------------------------------------
Finding sensor CPU_0 DTS Temp.... ok
Sensor States:
lnr : Lower NonRecoverable
lcr : Lower Critical
lnc : Lower NonCritical
unc : Upper NonCritical
ucr : Upper Critical
unr : Upper NonRecoverable
---------------------------------------------------------------------------
Command
$./bsmevent.sh m lanplus H X.X.X.X u super p <password> a setEvent b unc s "CPU_0 DTS Temp."
Output
---------------------------------------------------------------------------
Finding sensor CPU_0 DTS Temp.... ok
0x0000 | PreInit Timestamp | | Temperature #0200#2d | Upper
Noncritical going high #57fcfb | Asserted
---------------------------------------------------------------------------
2.7.3.2. Test Trap Event

The landest option corresponds to an alert destination configured with an alert
IP address.
Command
$ bsmevent.sh m lanplus H X.X.X.X u MWA p guest
a testEvent –d 2

2.8. bsmfru
The bsmfru command displays the FRU contents using the standard output.
return code is -1.
The FRU is displayed in stdout, as follows:
<fru tag>: <fru content>
Note Servers are identified by their DNS name or IP address (-H parameter).
2.8.1. Options
syslog
logged
are logged
m interface Target server interface: lanplus, ipmidrv
u user MC user
(AES-CBC-128)
are redirected

bsmfru.sh [h] m interface H host u user [p password]
[o outfile] [l level] [Y cipher]

2.8.3. Examples
This section includes examples for remote and hardware management.
2.8.3.1. Remote Hardware Management

Syntax
bsmfru.sh [h] m lanplus H host u user [p password]
[o outfile] [l level] [Y cipher]
Command
$ bsmfru.sh -m lanplus -H X.X.X.X -u super -p <password> -Y 0
Output
---------------------------------------------------------------------------
FRU Inventory Device: System (ID 00 on MC 0x20)
FRU Product Manufacturer Name: BULL
FRU Product Name: bullion S
FRU Product Part/Model Number: bullion S16
FRU Product Version: 002
FRU Product Serial Number: XAN-S18-00005
FRU Inventory Device: Module (ID 01 on MC 0x80)

FRU Chassis Type: Rack Mount Chassis
FRU Chassis Part Number: not used
FRU Chassis Serial Number: XAN-LX7-00005
FRU Inventory Device: CIX (ID 02 on MC 0x80)

FRU Board Manufacturing Date/Time: 07/04/14 - 14:04:00
FRU Board Manufacturer: PLEXUS
FRU Board Product Name: CIX
FRU Board Serial Number: PP14230LB
FRU Board Part Number: 11074283-004
FRU Board Custom Info: 11074283-004
FRU Board Custom Info: PP14230LB
FRU Board Custom Info: 14254
FRU Board Custom Info: SFOK
FRU Board Custom Info: Reop Caterr
FRU Board Custom Info: BULL
FRU Device Description : PIROM CPU_0 (ID 03 on MC 0x80)

Processor S-spec/QDF Number : QFKJ
Processor Sample/Production : Sample
Number of Cores : 15
Number of Threads per Core : 2
System BUS Speed : 100 MHz
Core Processor Family : 6
Core Processor Model : 14
Core Processor Stepping : 7
Maximum P1 Core Frequency : 2800 MHz
Maximum Core Voltage ID : 1.250 V
Minimum Core Voltage ID : 0.600 V
Core Voltage Tolerance High : 15 mV
Core Voltage Tolerance Low : 15 mV
Max Intel QPI Link Transfer Rate: 8000 MT/s
Min Intel QPI Link Transfer Rate: 8000 MT/s
Intel QPI Version Number : 1.1
Memory Support flags : LT-SX : Not Supported
Max Intel SMI Transfer Rate : 2666 MT/s
Min Intel SMI Transfer Rate : 1600 MT/s
Uncore Voltage ID : 1.200 V
Uncore Voltage Tolerance High : 0 mV
Uncore Voltage Tolerance Low : 0 mV
L2 Cache Size : 256 Kb
Package Revision : 1.0

Substrate Revision Software ID : 0
Processor Family Number : CM80636
Processor SKU Number : 01375300
Maximum Case Temperature : 77 øC
Maximum Thermal Design Power : 155 Watts
Processor Core Feature Flags : 0xfffbebbf
Multiprocessor Support : 2 processors socket
Number of Devices in TAP Chain : 1
Serial Number : 0x746bd27bfe3ce900
FRU Device Description : PIROM CPU_1 (ID 04 on MC 0x80)

Processor S-spec/QDF Number : QFKJ
Processor Sample/Production : Sample
Number of Cores : 15
Number of Threads per Core : 2
System BUS Speed : 100 MHz
Core Processor Family : 6
Core Processor Model : 14
Core Processor Stepping : 7
Maximum Core Voltage ID : 1.250 V
Minimum Core Voltage ID : 0.600 V
Core Voltage Tolerance High : 15 mV
Core Voltage Tolerance Low : 15 mV
Max Intel QPI Link Transfer Rate: 8000 MT/s
Min Intel QPI Link Transfer Rate: 8000 MT/s
Intel QPI Version Number : 1.1
Memory Support flags : LT-SX : Not Supported
Max Intel SMI Transfer Rate : 2666 MT/s
Min Intel SMI Transfer Rate : 1600 MT/s
Uncore Voltage ID : 1.200 V
Uncore Voltage Tolerance High : 0 mV
Uncore Voltage Tolerance Low : 0 mV
Package Revision : 1.0
Substrate Revision Software ID : 0
Processor Family Number : CM80636
Processor SKU Number : 01375300
Maximum Case Temperature : 77 øC
Maximum Thermal Design Power : 155 Watts
Processor Core Feature Flags : 0xfffbebbf
Multiprocessor Support : 2 processors socket
Number of Devices in TAP Chain : 1
Serial Number : 0x9e7a85e35ca81700
FRU Inventory Device: LCP (ID 05 on MC 0x80)

FRU Board Manufacturer: SANMINA-SCI
FRU Board Product Name: LCP2
FRU Board Serial Number: K014112I
FRU Board Part Number: 12000417
FRU Board Custom Info: K014112I
FRU Inventory Device: PS_0 (ID 06 on MC 0x80)
FRU Inventory Device: PS_1 (ID 07 on MC 0x80)
FRU Inventory Device: UCM (ID 08 on MC 0x80)
FRU Inventory Device: MMR_0 (ID 09 on MC 0x80)

FRU Board Product Name: RM3D3
FRU Board Serial Number: PP1421036

FRU Board Custom Info: PP1421036
FRU Board Custom Info: none
FRU Inventory Device: MMR_7 (ID 16 on MC 0x80)

FRU Board Product Name: RM3D3
FRU Board Serial Number: PP142107F
FRU Board Custom Info: PP142107F
FRU Board Custom Info: none
FRU Inventory Device: WEO (ID 17 on MC 0x80)

FRU Board Info Area Error: FRU information inconsistent
FRU Inventory Device: Module (ID 01 on MC 0x82)

FRU Chassis Type: Rack Mount Chassis
FRU Chassis Part Number: not used
FRU Chassis Serial Number: XAN-LX7-00012
FRU Inventory Device: CIX (ID 02 on MC 0x82)

…
---------------------------------------------------------------------------
2.8.3.2. Local Hardware Management

Syntax
bsmfru.sh [h] m ipmidrv [o outfile] [l level]

2.9. bsmFwGlobalUpg
The bsmFwGlobalUpg command is used to check the installed firmware versions
and, if necessary, to upgrade them with the versions on the Resource and
Documentation DVD.
W018 WARNING
W018:
It is mandatory to consult the documentation delivered with the
firmware files before proceeding to update firmware.
The update process may take some time and MUST NOT be interrupted.
No other actions may be performed during the process.
Only qualified personnel are authorized to update firmware.
return code is -1.
Prerequisite
Insert the Resource and Documentation DVD in the drive
2.9.1. Options
-V Displays BSM version
list: lists the component firmware provided on the
Resource and Documentation DVD
check: checks the installation prerequisites for all the
components that need upgrading
diff: compares the firmware versions installed with the
versions on the Resource and Documentation DVD for
all components
upg: upgrades all the components that can be
upgraded with the versions available on the
-D directory DVD mount point (full path)
-f Forces the upgrade of the prerequisites
-T action_to Timeout for the upgrade of the prerequisites in
minutes (default is 3)
-L later y(yes): checks and upgrades earlier and later versions
(default)
n(no): checks and upgrades earlier versions
-M module_id For multi-module servers only.
If present, the action will be executed on the module
with this id.
If not, the action will be executed on all the modules.
-H host Module IP address or DNS name
u user MC user

are redirected
-d Debug mode

bsmFwGlobalUpg.sh [h | -V] -a action -D dir [H host u user p password]
[-M module_id] [-f [-T action_to]] [-L y|n] [-r] [o outfile] [-d]
2.9.3. Examples
2.9.3.1. List Component Firmware Details

Syntax
bsmFwGlobalUpg.sh -a list -D dir [H host u user p password] [o outfile]
Note If the -H, -u and -p options are present, only the firmware for the
same machine type (same PRODUCT_ID) rather than the remote host
specified is displayed.
Command
$ bsmFwGlobalUpg.sh -a list -D /STV/PRODUCTS/Customer/ -H X.X.X.X -u super -p <password>
Output
---------------------------------------------------------------------------
TECHNICAL STATE FIRMWARE INFORMATION
INPUT TS : Mesca2 005.02
DATE : 9/10/2014
FIRMWARE LIST FOR PRODUCT_ID : bullion_S
FW NAME : BCM53101_WEO
FW VERSION : 001
FW DIFF : NO
FW UPGRADE : NO
COMPONENT_ID LIST : WEO MC
FW NAME : BIOSX05
FW VERSION : 05.013.05.133
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : BIOS
FW NAME : BIOSX05VM
FW VERSION : 05.013.05.033
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : BIOS
FW NAME : LCP
FW VERSION : 20
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : LCP
FW NAME : POWERVILLE_CIX
FW VERSION : 1.63
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : ETHERNET
FW NAME : FPGA_WEO
FW VERSION : 0.2.3
FW DIFF : NO
FW UPGRADE : NO
COMPONENT_ID LIST : FPGA WEO
FW NAME : FPGA_CIX
FW VERSION : 0.2.9
FW DIFF : YES

FW UPGRADE : YES
COMPONENT_ID LIST : Main FPGA
FW NAME : CPLD_M_CIX
FW VERSION : 0.0.9
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : MCPLD
FW NAME : CPLD_P_CIX
FW VERSION : 0.2.3
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : PCPLD
FW NAME : CPLD_PM1_CIX
FW VERSION : 0.6
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : PM1CPLD
FW NAME : CPLD_PM2_CIX
FW VERSION : 0.6
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : PM2CPLD
FW NAME : DS750PED_PSU
FW VERSION : 01.03.01
FW DIFF : NO
FW UPGRADE : NO
COMPONENT_ID LIST : PSU1 PSU2
FW NAME : DS1600PED_PSU
FW VERSION :
FW DIFF : NO
FW UPGRADE : NO
COMPONENT_ID LIST : PSU1 PSU2
FW NAME : CPLD_MUCM
FW VERSION : 1.2
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : UCMCPLD
FW NAME : PM_MUCM
FW VERSION : 0.3
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : UCMPM
FW NAME : PM_RMxD3
FW VERSION : 0.3
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : MEMR 0 PM MEMR 1 PM MEMR 2 PM MEMR 3 PM MEMR 4 PM
MEMR 5 PM MEMR 6 PM MEMR 7 PM
FW NAME : EMM30_BMC
FW VERSION : 30.10.0
FW DIFF : YES
FW UPGRADE : YES
COMPONENT_ID LIST : MC
action duration : 0.178973
---------------------------------------------------------------------------

2.9.3.2. Compare Firmware Versions
Syntax
bsmFwGlobalUpg.sh -a diff -D dir H host u user p password [-M module_id]
[o outfile]
Command
$ bsmFwGlobalUpg.sh -a diff -D /STV/PRODUCTS/Customer/ -H X.X.X.X -u super -p <password>
Output
---------------------------------------------------------------------------
FIRMWARE DIFF FOR
HOST ADDRESS : X.X.X.X
HOST PRODUCT ID : bullion_S
CURRENT HOST TS : unknown
MODULE ID : 0
FW NAME TS FW VERSION HOST COMPONENT HOST VERSION RESULT

BIOSX05VM 05.013.05.033 BIOS 05.013.04.032 EARLIER
LCP 20 LCP 20 OK
FPGA_CIX 0.2.9 Main FPGA 0.2.6 EARLIER
CPLD_M_CIX 0.0.9 MCPLD 0.0.9 OK
CPLD_P_CIX 0.2.3 PCPLD 0.2.0 EARLIER
CPLD_PM1_CIX 0.6 PM1CPLD 5.6 LATER
CPLD_MUCM 1.2 UCMCPLD 0.0 EARLIER
PM_MUCM 0.3 UCMPM 0.0 EARLIER
EMM30_BMC 30.10.0 MC 30.9.0 EARLIER
FIRMWARE TO UPGRADE : 6
FIRMWARE DIFF FOR
HOST ADDRESS : X.X.X.X
MODULE ID : 1
FW NAME TS FW VERSION HOST COMPONENT HOST VERSION RESULT

LCP 20 LCP 20 OK
FIRMWARE TO UPGRADE : 6
---------------------------------------------------------------------------
Result Values
Result Description
unknown The installed firmware version is not known
EARLIER The installed firmware version is earlier than the one on
the Resource and Documentation DVD
LATER The installed firmware version is later than the one on the
OK The installed firmware version and the one on the
Resource and Documentation DVD are the same

2.9.3.3. Check Installation Prerequisites
Note You can choose to check either the earlier versions or the earlier and
the later versions against the versions on the Resource and
Documentation DVD, using the -L option.
Syntax
bsmFwGlobalUpg.sh -a check -D dir H host u user p password [-M module_id]
[-L y|n] [o outfile]
Command
$ bsmFwGlobalUpg.sh -a check -D /STV/PRODUCTS/Customer/ -H X.X.X.X -u super -p <password> -L yes
Output
---------------------------------------------------------------------------
FIRMWARE CHECK FOR
HOST ADDRESS : 172.31.50.60
MODULE ID : 0
FW NAME TS FW VERSION HOST COMPONENT HOST VERSION DIFF
UPGRADABLE PREREQ STATUS

YES KO KO : pre_check POWER_STATUS_OFF failed
LCP 20 LCP 20 OK
YES N/A OK
YES N/A OK
YES N/A OK
YES N/A OK
FIRMWARE OK TO UPGRADE: 0
FIRMWARE CHECK FOR
HOST ADDRESS : 172.31.50.61
MODULE ID : 1
FW NAME TS FW VERSION HOST COMPONENT HOST VERSION DIFF
UPGRADABLE PREREQ STATUS

LCP 20 LCP 20 OK
YES N/A OK
YES N/A OK

YES N/A OK
YES N/A OK
FIRMWARE OK TO UPGRADE: 0
---------------------------------------------------------------------------
Result Values
Status Description
unknown The installed firmware version is not known
OK No need to upgrade
OK to upg Upgrade needed and possible
Other tool to upg Upgrade needed but not possible with this command. It
must be performed with a different tool
KO Upgrade needed but impossible
KO : pre_check Upgrade needed but the prerequisites must be upgraded
XXX failed first: use the -f option to force the upgrade of the
prerequisites
2.9.3.4. Upgrade Firmware
Notes • You can choose to upgrade either the earlier versions or the earlier
and the later versions to match the versions on the Resource and
Documentation DVD, using the -L option.
• You can choose to force the upgrade of the prerequistes using the -f
option. The default timeout for the upgrade of the prerequisites is 3
minutes. This can be changed using the -T option.
Syntax
bsmFwGlobalUpg.sh -a upg -D dir H host u user p password [-M moduleIndex]
[-f [-T action_to]] [-L y|n] [-r] [o outfile]
Command
$ bsmFwGlobalUpg.sh -a upg -D /CD_bullion_060.02 -M all -H X.X.X.X -u super -p <password> -f
Output in the case of BIOS and BMC upgrading

---------------------------------------------------------------------------
FIRMWARE UPGRADE FOR
HOST ADDRESS : 172.31.130.10
CURRENT HOST TS : Mesca2 007.01
MODULE ID : 0
starting upgrade of BIOS 05.019.02.110 with BIOSX05 05.021.00.107 , output

file is /var/log/BSMHW/172.31.130.10_2015-03-
04_11-01-10_BIOSX05_05.021.00.107_BIOS
end upgrade of BIOS 05.019.02.110 with BIOSX05 05.021.00.107 : result is

successful , output file is /var/log/BSMHW/172.
31.130.10_2015-03-04_11-01-10_BIOSX05_05.021.00.107_BIOS
END OF FIRMWARE UPGRADE FOR


HOST ADDRESS : 172.31.130.10
MODULE ID : 0
SUCCESSFUL FW UPGRADE : 1
FAILED FW UPGRADE : 0
PRE_CHECK FAILED : 0

HOST ADDRESS : 172.31.130.11
MODULE ID : 1

04_11-06-43_BIOSX05_05.021.00.107_BIOS

31.130.11_2015-03-04_11-06-43_BIOSX05_05.021.00.107_BIOS
starting upgrade of MC 30.14.0 with EMM30_BMC 30.15.0 , output file is

/var/log/BSMHW/172.31.130.11_2015-03-04_11-11-42_
EMM30_BMC_30.15.0_MC
end upgrade of MC 30.14.0 with EMM30_BMC 30.15.0 : result is successful ,

output file is /var/log/BSMHW/172.31.130.11_20
15-03-04_11-11-42_EMM30_BMC_30.15.0_MC

HOST ADDRESS : 172.31.130.11
MODULE ID : 1

HOST ADDRESS : 172.31.130.12
MODULE ID : 2

04_11-14-27_BIOSX05_05.021.00.107_BIOS

31.130.12_2015-03-04_11-14-27_BIOSX05_05.021.00.107_BIOS

HOST ADDRESS : 172.31.130.12
MODULE ID : 2

HOST ADDRESS : 172.31.130.13
MODULE ID : 3


04_11-19-41_BIOSX05_05.021.00.107_BIOS

31.130.13_2015-03-04_11-19-41_BIOSX05_05.021.00.107_BIOS

/var/log/BSMHW/172.31.130.13_2015-03-04_11-24-41_

15-03-04_11-24-41_EMM30_BMC_30.15.0_MC
HOST ADDRESS : 172.31.130.13
MODULE ID : 3

HOST ADDRESS : 172.31.130.14
MODULE ID : 4

04_11-27-31_BIOSX05_05.021.00.107_BIOS

31.130.14_2015-03-04_11-27-31_BIOSX05_05.021.00.107_BIOS

/var/log/BSMHW/172.31.130.14_2015-03-04_11-32-51_

15-03-04_11-32-51_EMM30_BMC_30.15.0_MC

HOST ADDRESS : 172.31.130.14
MODULE ID : 4

HOST ADDRESS : 172.31.130.15
MODULE ID : 5

04_11-35-31_BIOSX05_05.021.00.107_BIOS

31.130.15_2015-03-04_11-35-31_BIOSX05_05.021.00.107_BIOS

/var/log/BSMHW/172.31.130.15_2015-03-04_11-40-53_


15-03-04_11-40-53_EMM30_BMC_30.15.0_MC

HOST ADDRESS : 172.31.130.15
MODULE ID : 5

HOST ADDRESS : 172.31.130.16
MODULE ID : 6

04_11-43-42_BIOSX05_05.021.00.107_BIOS

31.130.16_2015-03-04_11-43-42_BIOSX05_05.021.00.107_BIOS

/var/log/BSMHW/172.31.130.16_2015-03-04_11-48-46_

15-03-04_11-48-46_EMM30_BMC_30.15.0_MC

HOST ADDRESS : 172.31.130.16
MODULE ID : 6

HOST ADDRESS : 172.31.130.17
MODULE ID : 7

04_11-51-25_BIOSX05_05.021.00.107_BIOS

31.130.17_2015-03-04_11-51-25_BIOSX05_05.021.00.107_BIOS

/var/log/BSMHW/172.31.130.17_2015-03-04_11-56-25_

15-03-04_11-56-25_EMM30_BMC_30.15.0_MC

HOST ADDRESS : 172.31.130.17
MODULE ID : 7
Launching BMC reset on master module(s). It may take several minutes

---------------------------------------------------------------------------

2.10. bsmGetConfParam
The bsmGetConfParam command is used to get various configuration parameter
values.
return code is -1.
Notes • The configuration parameter value can be obtained even with the
action option or with the keyname option.
• The options -a and -k are exclusive.
2.10.1. Options
l level Specifies the severity of the messages to be logged by
syslog
logged
are logged
getPowerRestorePolicy: gets the power restore policy
(On, Off or Restore) applied after an AC power loss
getPrimaryNTP: gets the address for the primary NTP
server that gives the date and time
getSecondaryNTP: gets the address for the secondary
NTP server that gives the date and time
getDisableBCS: gets the BCS status
getBiosNoMemoryHole: gets the feature setting. It
removes all gaps in the memory allocation for the
modules. For VMware only.
getBiosVMwareMaxMemPerModule: gets this feature
setting. It pre-allocates DRAM slice per module. For
VMware only.
getBiosBootTimeout: gets the BIOS boot timeout.
getTSnumber: gets the Technical State number
-k keyname BMC key put between quote. Keyname format:
'bmc.xxxxx'
-u user MC user

(AES-CBC-128)
are redirected

bsmGetConfParam.sh [h] [l level] a action m interface H host [u user]
[p password] [Y cipher] [o outfile]
2.10.3. Examples
2.10.3.1. Get the Power Restore Policy

Command
$ bsmGetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password>
-a getPowerRestorePolicy
Output
-----------------------------------------------------------------------
Power Restore Policy is: on
-----------------------------------------------------------------------
2.10.3.2. Get the Primary NTP Server IP Address

Command
bsmGetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a getPrimaryNTP
Output
-------------------------------------------------------------------
Primary NTP server is: Y.Y.Y.Y
-----------------------------------------------------------------------
2.10.3.3. Get the Secondary NTP Server IP Address

Command
bsmGetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a getSecondaryNTP
Output
-------------------------------------------------------------------
Secondary NTP server is: Z.Z.Z.Z
-----------------------------------------------------------------------

2.10.3.4. Get the BCS Status
Syntax
bsmGetConfParam.sh [h] a getDisableBCS m interface H host
[u user] [p password] [Y cipher] [o outfile] [l level]
Command
bsmGetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a getDisableBCS
Output
---------------------------------------------------------------------------
BCS disabling is : yes
---------------------------------------------------------------------------
2.10.3.5. Get the BIOS Boot Timeout

Command
bsmGetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a getBiosBootTimeout
Output
---------------------------------------------------------------------------
Bios boot timeout is : 15 minutes
Multiply the value per 3 to have the timeout used by the BMC of a
multi-modules server.
---------------------------------------------------------------------------
2.10.3.6. Get DRAM Compaction Feature for VMware System
Note This feature is available for VMware systems only. It removes all gaps
in the memory allocation for the modules. This feature is only available
for the 8 sockets BIOS images for VMware systems.
Command
bsmGetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a getBiosNoMemoryHole
2.10.3.7. Get the Pre-allocation of DRAM per Module
Note This feature is available for VMware system only and allows you to
pre-allocate DRAM slice per module, according to the DRAM amount per
module and the physical memory address limits supported by the OS.
Command
bsmGetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a getBiosVMwareMaxMemPerModule
2.10.3.8. Get the Technical State Number

Command
bsmGetConfParam.sh -H X.X.X.X -u super -p <password> -a getTSnumber
Output
---------------------------------------------------------------------------
Technical state number is Mesca2 009.01
---------------------------------------------------------------------------

2.11. bsmGetFunctionalProfile
The bsmGetFunctionalProfile command is used to get functional profile
information for a partition. It displays the state of the functional profile
identifier (active or not) and the state of its Power Restore Policy (on or off).
return code is -1.
2.11.1. Options
syslog
logged
are logged
u user MC user
-n functionalProfileId Functional Profile identifier (0 or 1)
(AES-CBC-128)
are redirected

bsmGetFunctionalProfile.sh [h] [l level] m interface H host [u user]
[p password] n functionalProfileID [Y cipher] [o outfile]
2.11.3. Example
Command
$ bsmGetFunctionalProfile.sh -m lanplus -H X.X.X.X -u super -p <password> –n 0
Output
---------------------------------------------------------------------------
Functional profile 0 is active
Power Restore Policy is: off
---------------------------------------------------------------------------

2.12. bsmGetHardwareExclusion
The bsmGetHardwareExclusion command is used to get the hardware
component exclusion list for a server.
return code is -1.
2.12.1. Options
‐m interface Target server interface: lanplus
‐H host Module IP address or DNS name
-u user MC user
‐p password MC user password
(AES-CBC-128)
are redirected

bsmGetHardwareExclusion.sh [-h] [-l level]‐m interface -H host [-u user] [-p
password] [-Y cipher] [-o outfile]
2.12.3. Examples
Command
$ bsmGetHardwareExclusion.sh -m lanplus –H X.X.X.X –u super -p <password>
Output
---------------------------------------------------------------------------
No hardware exclusion
---------------------------------------------------------------------------
Command
Output
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Command
Output
---------------------------------------------------------------------------
XQPI0 excluded
XQPI2 excluded
---------------------------------------------------------------------------

2.13. bsmGetModuleLevelInfo
The bsmGetModuleLevelInfo command is used to get information about a
partition module.
return code is -1.
2.13.1. Options
logged
are logged
m interface Target server interface: lanplus.
u user MC user
-k keyname Lists information required. Several values can be put
in double quotes (“) and separated with space. If this
option is not set, information about the module_id is
displayed. Possible values:
module_id: module identifier
model_type: model type
model_name: marketing name
(AES-CBC-128)
are redirected

bsmGetModuleLevelInfo.sh [h] [l level] m interface H host [u user]
[p password] [k keyname] [Y cipher] [o outfile]

2.13.3. Examples
This section includes examples for the keyname option.
2.13.3.1. Display Default Information

Command
$ bsmGetModuleLevelInfo.sh -m lanplus -H X.X.X.X -u super -p <password>
Output
---------------------------------------------------------------------------
Module identifier is 0
---------------------------------------------------------------------------
2.13.3.2. Display Module Details

Command
$ bsmGetModuleLevelInfo.sh -m lanplus -H X.X.X.X -u super -p <password> -k module_id
Output
---------------------------------------------------------------------------
Module identifier is 1
---------------------------------------------------------------------------

2.14. bsmGetPartitionLevelInfo
The bsmGetPartitionLevelInfo command is used to get information about the
partition composition for a platform.
return code is -1.
2.14.1. Options
-l level Specifies the message severity to be logged into
syslog
logged
are logged
-m interface Target server interface: lanplus
-H host Module IP address or DNS name
-u user MC user
-p password MC user password
between double quotes (“) and separated with spaces.
If this option is not set, information about
partition_composition and master_id are displayed.
Possible values:
partition_composition: lists the modules included in
the partition
master_id: current master module identifier
next_master_id: master module identifier which will
be set after the next power on
ip_emm_list: lists the module IP addresses for the
platform
partition_name: name of the partition
(AES-CBC-128)
are redirected

bsmGetPartitionLevelInfo.sh [h] [l level] m interface H host [u user]

2.14.3. Examples

Command
$ bsmGetPartitionLevelInfo.sh -m lanplus -H X.X.X.X -u super -p <password>
Output
---------------------------------------------------------------------------
Module 0 is in the partition
No current master ID. - Partition is Off
---------------------------------------------------------------------------
2.14.3.2. Display Partition Modules with Master Module IDs, Module Addresses and
Partition Name
Command
$ bsmGetPartitionLevelInfo.sh -m lanplus -H X.X.X.X -u super -p <password>
-k “partition_composition master_id next_master_id ip_emm_list partition_name”
Output
---------------------------------------------------------------------------
Modules 0 and 1 are in the partition
No current master ID. Partition is Off
Master ID for the next power on is 0
IP address for module 0 is X.X.X.X.
IP address for module 1 is X.X.X.X.
Partition name is bimodules
---------------------------------------------------------------------------

2.15. bsmGetPlatformLevelInfo
The bsmGetPlatformLevelInfo command is used to get platform information.
return code is -1.
2.15.1. Options
l level Specifies the messages severity to be logged in syslog
logged
are logged
u user MC user
between double quotes (“) and separated with spaces.
If this option is not set, information about platform_id,
platform_name and module_count are displayed.
Possible values:
platform_id: platform identifier
platform_name: platform label
module_count: number of modules in the platform
prefix_ip: internal network IP address prefix
ip_emm_list: lists platform module's IP addresses
is_flexible: possibility to change the partition
composition
get_reset: gets the value set for automatic reset
get_uc_presence: gets the value set to power the
ultracapacity
(AES-CBC-128)
are redirected

bsmGetPlatformLevelInfo.sh [h] [l level] m interface H host [u user]

2.15.3. Examples

Command
$ bsmGetPlatformLevelInfo.sh -m lanplus -H X.X.X.X -u super -p <password>
Output
---------------------------------------------------------------------------
Platform identifier is 152
Platform name is PVT-NL-4838
Module count is 01
---------------------------------------------------------------------------
2.15.3.2. Display Number of Modules with IP Prefix, Platform Name and ID

Command
$ bsmGetPlatformLevelInfo.sh -m lanplus -H X.X.X.X -u super -p <password>
-k “module_count prefix_ip platform_name platform_id”
Output
---------------------------------------------------------------------------
Module count is 02
IP prefix is 10.24
Platform name is PVT-NL-4837
Platform identifier is 154
---------------------------------------------------------------------------
2.15.3.3. Display Partition Flexibility with Module IP Addresses

Command
$ bsmGetPlatformLevelInfo.sh -m lanplus -H X.X.X.X -u super -p <password> -k “is_flexible ip_emm_list”"
Output
--------------------------------------------------------------------------
Partitions can be changed
IP address for module 0 is X.X.X.X
---------------------------------------------------------------------------
2.15.3.4. Display Values for Automatic Reset

Command
$ bsmGetPlatformLevelInfo.sh -m lanplus -H X.X.X.X -u super -p <password> -k 'get_reset'
Output
--------------------------------------------------------------------------
-module 0 - automatic reset set to no
---------------------------------------------------------------------------

2.15.3.5. Display Ultracapacity
Command
$ bsmGetPlatformLevelInfo.sh -m lanplus -H X.X.X.X -u super -p <password> -k 'get_uc_presence'
Output
--------------------------------------------------------------------------
-module 0 - ultracapacity presence is set to yes
---------------------------------------------------------------------------

2.16. bsmGUID
The bsmGUID command is used to set the Globally Unic IDentifier (GUID)
2.16.1. Options
syslog
logged
are logged
H host Module IP address
u user MC user
get: returns the system GUID for each partition of the
platform
set:sets the system GUID for each partition of the
platform
(AES-CBC-128)
are redirected

bsmGUID.sh [h] m lanplus H host [u user p password] [l level] a action
[o outfile] [Y cipher]

2.16.3. Examples
2.16.3.1. Set GUID for a bi-module partition

Command
$ bsmGUID.sh -H X.X.X.X -u super -p <password> -a set
Output
---------------------------------------------------------------------------
GUID for modules 0 1 set.
---------------------------------------------------------------------------
2.16.3.2. Returns GUID for a bi-module partition

Command
$ bsmGUID.sh -H X.X.X.X -u super -p <password> -a get
Output
---------------------------------------------------------------------------
GUID for modules 0 1 is 90A1D2BC256948B3A610B449FDDD9A14
---------------------------------------------------------------------------
2.16.3.3. Set GUID for two mono-module partitions

Command
$ bsmGUID.sh -H X.X.X.X -u super -p <password> -a set
Output
---------------------------------------------------------------------------
GUID for module(s) 0 set
GUID for module(s) 1 set
---------------------------------------------------------------------------
2.16.3.4. Returns GUID for two mono-module partitions

Command
$ bsmGUID.sh -H X.X.X.X -u super -p <password> -a get
Output
---------------------------------------------------------------------------
GUID for module(s) 0 is BB338B914D6B4C478061B361F7F69AE0
GUID for module(s) 1 is 192E56C3D7DA4AF39299CF2B3A4BEC15
---------------------------------------------------------------------------

2.17. bsmidentify
The bsmidentify command is used to identify a remote host physically via
uservisible lights or beeps for a defined period of time.
2.17.1. Options
syslog
logged
are logged
C value Specifies the identification time period (in seconds):
this value may be set from 0 to 250
u user MC user
(AES-CBC-128)
are redirected

bsmidentify.sh [h] m interface H host u user [p password] [l level] C
value [o outfile] [Y cipher]

2.18. bsminfo
The bsminfo command is used to get IPMI details such as BMC parameters, LAN
configuration parameters, users list, and Alert parameters.
return code is -1.
2.18.1. Options
syslog
logged
are logged
bmc_info: gets IPMI details,e.g., BMC Firmware
revision, Manufacturer, BMC Device support
lan_print: gets the configuration parameters of the
LAN channel used to access the BMC with an
OutOfBand connection
user_list: gets details about the users configured for
the LAN channel used to access the BMC with an
OutOfBand connection
get_lan_alert_dest: gets LAN alert destination details
configured for the LAN channel used to access the
BMC with an OutOfBand connection
get_pef_list: gets details about the Alert Policy Table
used by the BMC for Alert processing
get_pef_policy: gets details about the Platform Event
Filter Table used by the BMC for Alert processing
-u user MC user
(AES-CBC-128)
are redirected

bsminfo.sh [h] m lanplus H host –a action [u user] [p password]
[o outfile] [l level]

2.18.3. Examples
2.18.3.1. Get IPMI Information for a Server Using Lanplus

Command
$ bsminfo.sh -a bmc_info -m lanplus –H X.X.X.X –u super -p <password>
Output
---------------------------------------------------------------------------
Device ID : 80
Device Revision : 1
Device SDRs : unsupported
Firmware Revision : 30.18
Device Available : yes (normal operation)
IPMI Version : 2.0
Sensor Device : supported
SDR Repository Device : supported
SEL Device : supported
FRU Inventory Device : supported
IPMB Event Receiver : unsupported
IPMB Event Generator : unsupported
Bridge : unsupported
Chassis Device : supported
Manufacturer ID : Bull Company (107)
Product ID : 17
Auxiliary Firmware Revision Information : 28130000h
Device GUID : 0f0e0d0c-0b0a-0908-b0ea-3cfeff38000a
System GUID : 1f8f9df0-cbdc-b4bc-f046-9a97d19f422a
System Firmware Version :
System Name : Capri5
Primary Operating System Name : Capri5-Linux00
Operating System Name :
Channel Information
Channel Number : 0
Medium Type : IPMB (I2C)
Protocol Type : IPMB-1.0
Active Session Count : 0
Session Support : session-less
Vendor ID : Intelligent Platform Management Interface forum (7154)
Channel Number : 1
Medium Type : 802.3 LAN
Session Support : multi-session
Channel Number : 5
Medium Type : Asynch. Serial/Modem (RS-232)
Session Support : single-session
---------------------------------------------------------------------------

2.18.3.2. Get Configuration Parameters for the LAN Channel
Command
$ bsminfo.sh -a lan_print -m lanplus –H X.X.X.X –u guest -p <password>
Output
---------------------------------------------------------------------------
Section Lan_Conf_Auth
User_Enable_Auth_Type_MD5 Yes
Operator_Enable_Auth_Type_MD5 Yes
Admin_Enable_Auth_Type_MD5 Yes
OEM_Enable_Auth_Type_MD5 Yes
EndSection
Section Lan_Conf
IP_Address_Source Use_DHCP
IP_Address 172.31.130.10
MAC_Address 08:00:38:3C:EA:B0
Subnet_Mask 255.255.255.0
Default_Gateway_IP_Address 172.31.130.1
Default_Gateway_MAC_Address 00:00:00:00:00:00
Backup_Gateway_IP_Address 0.0.0.0
Backup_Gateway_MAC_Address 00:00:00:00:00:00
EndSection
Section Rmcpplus_Conf_Privilege
Maximum_Privilege_Cipher_Suite_Id_1 User
Maximum_Privilege_Cipher_Suite_Id_3 OEM_Proprietary
EndSection
---------------------------------------------------------------------------

2.18.3.3. Get Information about Users Configured for the LAN Channel
Command
$ bsminfo.sh -a user_list -m lanplus –H X.X.X.X –u super -p <password>
Output
---------------------------------------------------------------------------
Section User1
Enable_User No
Lan_Enable_IPMI_Msgs No
Lan_Enable_Link_Auth No
Lan_Enable_Restricted_to_Callback No
Lan_Privilege_Limit No_Access
SOL_Payload_Access No
EndSection
Section User2
Username super
Enable_User Yes
Lan_Enable_IPMI_Msgs Yes
Lan_Privilege_Limit OEM_Proprietary
SOL_Payload_Access Yes
EndSection
Section User3
Username
Enable_User No
EndSection
.....
Section User62
Username
Enable_User No
EndSection
Section User63
Username
Enable_User No
EndSection
---------------------------------------------------------------------------

2.18.3.4. Get Information about LAN Alert Destinations for the LAN Channel
Command
$ bsminfo.sh -a get_lan_alert_dest -m lanplus –H X.X.X.X –u MWA -p guest
Output
---------------------------------------------------------------------------
Section Lan_Alert_Destination_1
Alert_Destination_Type PET_Trap
Alert_Acknowledge Yes
Alert_Acknowledge_Timeout 12
Alert_Retries 3
Alert_Gateway Default
Alert_IP_Address 172.31.50.73
Alert_MAC_Address 00:00:00:00:00:00
EndSection
Alert_Retries 3
EndSection
Alert_Retries 3
EndSection
Alert_Retries 3
EndSection
Alert_Acknowledge No
Alert_Retries 0
EndSection
...
---------------------------------------------------------------------------

2.18.3.5. Get Information about the Alert Policy Table
Command
$ bsminfo.sh -a get_pef_policy -m lanplus –H X.X.X.X –u MWA -p guest
Output
---------------------------------------------------------------------------
Section Alert_Policy_1
Policy_Type
Always_Send_To_This_Destination
Policy_Enabled Yes
Policy_Number 0
Destination_Selector 1
Channel_Number 1
Alert_String_Set_Selector 0
Event_Specific_Alert_String No
EndSection
Policy_Type
Policy_Enabled Yes
Policy_Number 0
Channel_Number 1
EndSection
Policy_Type
Policy_Enabled Yes
Policy_Number 0
Channel_Number 1
EndSection
Policy_Type
Policy_Enabled Yes
Policy_Number 0
Channel_Number 1
EndSection
Policy_Type
Policy_Enabled No
Policy_Number 0
Channel_Number 0
EndSection
.....
---------------------------------------------------------------------------

2.18.3.6. Get Information about the Platform Event Filter Table
Command
$ bsminfo.sh -a get_pef_list -m lanplus –H X.X.X.X –u MWA -p guest
Output
---------------------------------------------------------------------------
Section Event_Filter_1
Filter_Type
Manufacturer_Pre_Configured
Enable_Filter Yes
Event_Filter_Action_Alert Yes
Event_Filter_Action_Power_Off No
Event_Filter_Action_Reset No
Event_Filter_Action_Power_Cycle No
Event_Filter_Action_Oem No
Event_Filter_Action_Diagnostic_Interrupt No
Event_Filter_Action_Group_Control_Operation No
Alert_Policy_Number 0
Group_Control_Selector 0
Event_Severity Information
Generator_Id_Byte_1 0xFF
Sensor_Type System_ACPI_Power_State
Sensor_Number 0x0F
Event_Trigger 0x6F
Event_Data1_Offset_Mask 0xFFFF
Event_Data1_AND_Mask 0x00
Event_Data1_Compare1 0xFF
Event_Data1_Compare2 0x00
EndSection
Filter_Type
Enable_Filter Yes
Sensor_Type Button_Switch
Sensor_Number 0xFF
Event_Trigger 0xFF
Event_Data1_Offset_Mask 0xFFFF
EndSection

Filter_Type
Enable_Filter Yes
Sensor_Type Power_Supply
Sensor_Number 0xFF
Event_Trigger 0x6F
Event_Data1_Offset_Mask 0x01
EndSection
---------------------------------------------------------------------------

2.19. bsmlog
The bsmlog command is used to direct system log contents (SEL) to standard
output or write messages and internal traces to the BMC into a filename or to
clear them.
return code is -1.
If the –v option is not specified, the output format is:
<rank> | <record id> | <local date> | <local time> | <event target> |
<severity> <event description>
If the -v option is specified, one record is displayed by field (over several rows
according to the format):
<label>: <value>
Notes • Servers are identified by their DNS name or IP address (-H

parameter).
• −n range is ignored if the −a clear_logs is specified.
• By default, the n range parameter is set to n 10.

2.19.1. Options
syslog
logged
are logged
v Displays record details. See below
n range Specifies range of records to be displayed
May be specified as a number or as an interval:
n n: displays the n most recent records.
n r1r2: displays records from r1 to r2
Events are displayed in chronological order beginning
with the most recent ones
m interface Target server interface: lanplus, ipmidrv.
get_sel (default): directs system log contents (SEL) to
standard output
clear_sel: clears the system logs contents (SEL)
get_logs: writes BMC messages and internal traces to
the BMC (eric traces) into a filename
clear_logs: clears the BMC messages and internal
traces to the BMC (eric traces)
-D backupDir Full directory path for log file (default is /tmp)
-s suffix Log filename suffix
-M module Module identifier
u user MC user
(AES-CBC-128)
o outfile Output file to which stdout and stderr outputs are
redirected

bsmlog.sh [h] m interface H host u user [p password] [n range]
a action [D backupdir] [s suffix] [M module]][o outfile] [l level]
[Y cipher] [v]
2.19.3. Examples
This section includes examples for remote and local hardware management.

Syntax
bsmlog.sh [h] m lanplus H host u user [p password] [n range]
a action [D backupdir] [s suffix] [M module]][o outfile] [l level]
[Y cipher] [v]
Clear SELs
Command
$ bsmlog.sh -m lanplus -H X.X.X.X -a clear_sel -u super -p <password>

Display SELs
Command
$ bsmlog.sh -m lanplus -H X.X.X.X -u super -p <password> -a get_sel -n 130-150
Output
---------------------------------------------------------------------------
ID | Date | Time | Owner ID | Name | Type
| Event
150| Apr-01-2015 | 10:59:59 | 0x20 | ACPI Pwr State | System ACPI Power
State | S4/S5 soft-off
State | S0/G0
148| Apr-01-2015 | 10:59:43 | 0x20 | System Boot Init| System Boot Initiated
| System Restart ; OEM Event Data2 code = 01h ; OEM Event Data3
code = 0Dh
147| Apr-01-2015 | 10:49:17 | 0x80 | FAN_5 Redund. | Cooling Device
| Fully Redundant
| Fully Redundant
| Fully Redundant
| Fully Redundant
| Fully Redundant
| Fully Redundant
141| Apr-01-2015 | 10:49:15 | 0x80 | Mod 1 LAN Cnct | Cable/Interconnect
| Cable/Interconnect is connected
140| Apr-01-2015 | 10:49:12 | 0x80 | Pwr Redundancy | Power Unit
| Fully Redundant
State | S4/S5 soft-off
138| Apr-01-2015 | 10:49:03 | 0x80 | PS_1 Status | Power Supply
| Presence detected
137| Apr-01-2015 | 10:49:03 | 0x80 | PCI_6 | Entity Presence
| Entity Absent
136| Apr-01-2015 | 10:49:03 | 0x80 | PCI_6 RISER | Entity Presence
| Entity Absent
| Entity Absent
| Entity Absent
| Entity Absent
| Entity Absent
| Entity Absent
| Entity Absent
---------------------------------------------------------------------------

Get Logs
Command
$ bsmlog.sh -m lanplus -H X.X.X.X -u admin -p admin -a get_logs
Output
---------------------------------------------------------------------------
backup file of module 0 into /tmp/boardmsg1 successful.
backup file of module 0 into /tmp/boardmsg2 successful.
backup file of module 0 into /tmp/erictrace1 successful.
backup file of module 0 into /tmp/erictrace2 successful.
command complete.
---------------------------------------------------------------------------
Command
$ bsmlog.sh -m lanplus -H X.X.X.X -u admin -p admin -a get_logs -D /tmp/log -s '.txt'
Output
---------------------------------------------------------------------------
backup file of module 0 into /tmp/log/boardmsg1.txt successful.
backup file of module 0 into /tmp/log/boardmsg2.txt successful.
backup file of module 0 into /tmp/log/erictrace1.txt successful.
backup file of module 0 into /tmp/log/erictrace2.txt successful.
command complete.
---------------------------------------------------------------------------
Clear logs
Command
$ bsmlog.sh -m lanplus -H X.X.X.X -a clear_logs -u super -p <password>

Syntax
bsmlog.sh [h] [v] m ipmidrv [n range] [o outfile] [l level]
Command to clear SELS
$ bsmlog.sh -m impidrv -a clear_sel
Output
---------------------------------------------------------------------------
Clearing SEL. Please allow a few seconds to erase.
---------------------------------------------------------------------------
Command to display SELs
$ bsmlog.sh -n 245-240 -m ipmidrv
Output
---------------------------------------------------------------------------
245 | 0x00bd | 10/13/2014 | 18:14:05 | 0x1 | OEM (0xc7) (Memory
RAS)#01f0#d4 | Patrol Scrub activated in all processors #800100 | Asserted
244 | 0x00bc | 10/13/2014 | 18:08:41 | 0x2c | Microcontroller/Coprocessor
(ME Power State)#2c00#16 | Transition to Running #000000 | Asserted
243 | 0x00bb | 10/13/2014 | 18:08:32 | 0x20 | System ACPI Power State (ACPI
Pwr State)#2000#00 | S0/G0: working #000000 | Asserted
242 | 0x00ba | 10/13/2014 | 18:08:29 | 0x20 | System Boot Initiated (System
Boot Init)#2000#d5 | System Restart #a70a00 | Asserted
241 | 0x00b9 | 10/13/2014 | 18:08:18 | 0x20 | System ACPI Power State (ACPI
Pwr State)#2000#00 | S4/S5: softoff #060000 | Asserted
240 | 0x00b8 | 10/13/2014 | 18:08:13 | 0x80 | Processor (CPU_1
Status)#8000#02 | IERR #000000 | Deasserted
--------------------------------------------------------------------------

2.20. bsmOSpm
The bsmOSpm command is used to control the CPU frequency and policy of a
platform via cpufrequtils package.
return code is -1.
2.20.1. Options
getPolicy: gets the governor and frequency range for
one or all CPUs
setPolicy: sets the CPU governor and to set the
frequency range for all CPUs for the usespace
governor
getCurrentFreq: gets the current frequency of one or
all CPUs
setCurrentFreq: sets the current frequency for one or
all CPUs
GetHWlimits: gets the minimum and maximum CPU
frequency allowed
m interface Remote host OS: linux
syslog
logged
are logged
u user Username for remote connection via ssh
C configfile Config file used for remote connection (default is “”)
I idfile Identity file used for remote connection (default is
id_dsa)
d cfgdir Full path directory containing config file and_identity
file
D pathdir Full path directory containing script bsmOSpm_local
on remote host
o outfile Output file name where stdout and stderr outputs are
redirected
arglist Lists arguments specific to the action

bsmOSpm.sh [h] [l level] m interface –H host [–u user] [o outfile]
[I idfile] [d cfgdir] [C configfile] [D pathdir] –a action arglist

2.20.3. Examples
2.20.3.1. Get the Governor and the Frequency Range of One or All CPUs
Syntax
[I idfile] [d cfgdir] [C configfile] [D pathdir] –a getPolicy [c CPU]
Options
c cpu CPU for the action (number, all, synth (default value))
Get a Synthesis
Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a getPolicy –c synth
Get Results for All CPUs

Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a getPolicy –c all
Get Results for a Single CPU

Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a getPolicy –c 5
2.20.3.2. Set the CPU Governor and the Frequency Range
Syntax
[I idfile] [d cfgdir] [C configfile] [D pathdir] –a setPolicy
–g governor [y freq_min –x freq_max]
Options
g governor cpufreq governor. Values available are userspace,
ondemand, performance.
-y freq_min Minimum CPU frequency the governor may select
(only if userspace governor is specified). The
frequency may be specified in kHz or as a percentage
of the maximum frequency possible (hardware limit).
-x freq_max Maximum CPU frequency the governor may select
(only if userspace governor is specified). The
frequency may be specified in kHz or as a percentage
of the maximum frequency possible (hardware limit).
Set the CPU Frequency Governor to ondemand

Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a setPolicy –g ondemand
Set the CPU Frequency Governor to userspace, with Frequency Range in Percent
Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a setPolicy –g userspace –y 77% -x 87%

Set the CPU Frequency Governor to userspace, with Frequency Range in kHertz
Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a setPolicy –g userspace –y 2000000 -x 2560000
2.20.3.3. Get the Current Frequency of One or All CPUs

Syntax
[I idfile] [d cfgdir] [C configfile] [D pathdir] –a getCurrentFreq [c
CPU]
Options
c cpu CPU for the action (number, all, synth (default value)).
Get a Synthesis
Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a getCurrentFreq –c synth
Get Frequency of CPU 6

Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a getCurrentFreq –c 6
2.20.3.4. Set the Current Frequency for One or All CPUs

Syntax
[I idfile] [d cfgdir] [C configfile] [D pathdir] –a setCurrentFreq
[c CPU]
Options
f freq CPU frequency to be set. The userspace governor
must have been set and loaded. The frequency may
be specified in kHz or as a percent of the maximum
frequency possible (hardware limit).
Set the Frequency for all CPUs

Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a setCurrentFreq –f 2394000 –c all
Set the Frequency of CPU 6

Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a setCurrentFreq –f 2394000 –c 6

2.20.3.5. Get the Minimum and Maximum CPU Frequency Allowed
Syntax
[I idfile] [d cfgdir] [C configfile] [D pathdir] –a getHWlimits
[c CPU]
Options
Get the Frequency Allowed for each CPU

Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a getHWlimits –c all
Get the Frequency Allowed for CPU 3

Command
$ bsmOSpm.sh -m linux –H X.X.X.X –u root –a getHWlimits –c 3

2.21. bsmpower
The bsmpower command is used to perform system POWER ON/OFF and FORCE
POWER OFF operations and to check the power status:
This command is asynchronous and returns the prompt before the command
has completed.
return code is -1.
A power ON command on an already powered ON system and/or a power OFF
command on an already powered OFF system may return 0 (command
accepted).
An acknowledgement message is displayed in stdout (except if the -q option is
specified).
Notes • For the Power Off command to be taken into account on a remote
host running Windows 2000 / 2003 Server, the Shutdown: Allow
system to be shut down without having to log on security
option must be enabled on the remote host. To configure this
security option:
- Click Start > Run.
- In the Open box, type gpedit.msc and click OK.
- In the Group Policy window, expand Computer
Configuration\Windows\ Settings\Security
Settings\Local\Policies\Security Options\.
- Set the Shutdown Security option to enabled.
• In order to power on/off a chassis, the system executing bsmpower
must be declared on the target server as a member of a SNMPv1
read-write community. The default read-write community name used
by bsmpower is private.
2.21.1. Options
-h Displays command usage.
-q Quiet option: stops all output (stdout, sdterr, or outfile
if the -o option is specified).
on: power on
off: power off
off_force: force power off
status: display power status
diag: send diagnostic interrupt
-H host Module IP address or DNS name.
-m interface Target system interface: lanplus, ipmidrv.
-u user MC user

(AES-CBC-128).
-p password MC user password or authentication key
-o outfile Output file name to which the stdout and stderr
outputs are redirected.

bsmpower.sh [-h] [-q] -a action -m interface -H host [-u user] [-p password]
[-o outfile] [-Y cipher]
Note The bsmpower.sh -a status command displays the system power

ON/OFF status. The system power ON/OFF status represents the
electrical status and not the functional status of the system. For
example, a system may be powered ON but not RUNNING, due to a
BIOS initialization error.
2.21.3. Examples
Syntax
bsmpower.sh [-h] [-q] -a action -m lanplus -H host [-u user] [-p password]
[-o outfile] [-Y cipher]
Power on Command
$ bsmpower.sh -a on -m lanplus -H X.X.X.X -u super -p <password>
Power off Command

$ bsmpower.sh -a off -m lanplus -H X.X.X.X -u super -p <password>
Power Off_force Command

$ bsmpower.sh -a off_force -m lanplus -H X.X.X.X -u super -p <password>
Display Power Status Command
Note The bsmpower.sh -a status command displays the system power

ON/OFF status. The system power ON/OFF status represents the
electrical status and not the functional status of the system. For
example, a system may be powered ON but not RUNNING, due to a
BIOS initialization error.
$ bsmpower.sh -a status -m lanplus -H X.X.X.X –u super –p <password>
Output
---------------------------------------------------------------------------
X.X.X.X: off
---------------------------------------------------------------------------
Return Codes
0 System powered ON
1 System powered OFF
-1 Command failed
Send Diagnostic Interrupt Command

This command sends a diagnostic interrupt to the processor(s) and forces the
Operating System to perform a diagnostic dump for troubleshooting purposes.
Note A diagnostic launched on a powered off server cannot be executed.
$ bsmpower.sh -a diag -m lanplus -H X.X.X.X -u super -p <password>
Return Codes
0 Command accepted
-1 Command failed

2.22. bsmRegDump
The bsmRegDump command is used to manage registry dumps from the SD
card.
return code is -1.
2.22.1. Options
config: copies the registry configuration file to the SD
card
dump: launches a dump of the registries
list: lists all the registry dump files present on the SD
card
get: gets the registry dump file(s)
size: gets the size of the specified registry dump file
rm: removes the registry dump file(s)
-d directory Directory path for destination (default /tmp)
-f filename file name
u user MC user
(AES-CBC-128)
are redirected

bsmRegDump.sh [h] [m interface] H host [u user] [p password] [Y cipher]
[o outfile] -a action arglist
2.22.3. Examples
2.22.3.1. List all the Registry Dump Files

Syntax
[o outfile] -a list
Command
$ bsmRegDump.sh -H X.X.X.X -u super -p <password> -a list

Output
---------------------------------------------------------------------------
+++++++++++++++++++++++++++++++++++
Getting dump list information ...
+++++++++++++++++++++++++++++++++++
Copying... 100%
1407 bytes copied.
+++++++++++++++++++++++++++++++++++
Dump file details:
+++++++++++++++++++++++++++++++++++
drwxr-xr-x 2 root root 32768 May 11 09:26 .
drwxr-xr-x 4 root root 32768 May 13 16:45 ..
-rwxr-xr-x 1 root root 187 May 4 14:00 Dump_Bcs_Mod0_04052015_00004
-rwxr-xr-x 1 root root 73 May 4 14:00 Dump_Cpu0_Mod0_04052015_00004
-rwxr-xr-x 1 root root 42 May 4 14:00 Dump_Fpga_Mod0_04052015_00004
-rwxr-xr-x 1 root root 280 May 4 14:00 Dump_SystemInfo_04052015_00004
---------------------------------------------------------------------------
2.22.3.2. Get and Concatenate Registry Dump Files

Syntax
[o outfile] -a get [-n id] [-f filename]
Options
-a get Get all the registry dump files and concatenate by id
-a get n id Get and concatenate the registry dump files with the
specified id number
-a get -f filename Get the specified registry dump file
Command
$ bsmRegDump.sh -H X.X.X.X -u super -p <password> -a get -n 6 -d /tmp/DUMP6
Output
---------------------------------------------------------------------------
Copying Dump_Bcs_Mod0_11052015_00006 into /tmp/DUMP6
Copying... 100%
187 bytes copied.
Copying Dump_Cpu0_Mod0_11052015_00006 into /tmp/DUMP6
Copying... 100%
73 bytes copied.
Copying Dump_Cpu1_Mod0_11052015_00006 into /tmp/DUMP6
Copying... 100%
73 bytes copied.
Copying Dump_Fpga_Mod0_11052015_00006 into /tmp/DUMP6
Copying... 100%
42 bytes copied.
Copying Dump_SystemInfo_11052015_00006 into /tmp/DUMP6
Copying... 100%
280 bytes copied.
/tmp/DUMP6/DVT-VALID3_Dump_11052015_00006.json created
---------------------------------------------------------------------------

2.22.3.3. Get the Size of the Specified Dump File
Syntax
[o outfile] -a size [-f filename]
Options
-a size -f filename Get the size of the specified registry dump file
2.22.3.4. Remove the Dump Files

Syntax
[o outfile] -a rm [-f filename| -f all] [-M month] [-n id]
Options
-a rm -f all Removes all registry dump files
-a rm -f filename Removes the specified registry dump file
-a rm -M month Removes the registry dump file of the month specified
(3 letters Jan, Feb…Dec in English)
-a rm -n id Removes the registry dump files with the specified id
number
2.22.3.5. Copy a Registry Configuration File to the SD card

Syntax
[o outfile] -a copy [-f filename]
Options
-a copy -f filename copies the configuration file specified to the SD card
2.22.3.6. Launch a Dump of the Registries

Syntax
[o outfile] -a copy [-f filename]
Options
-a dump launches a dump of the registries

2.23. bsmRemoveHardwareExclusion
The bsmRemoveHardwareExclusion command is used to remove the hardware component
exclusion. Hardware components are defined with -C option.
When the command is accepted, the return code is 0. If the command fails, the return code is
-1.
2.23.1. Options
u user MC user
C componentList Lists hardware components to be removed from the
exclusion list. Components must be put between
quotes and separated by a blank
(AES-CBC-128)
are redirected

bsmRemoveHardwareExclusion.sh [-h] m interface -H host -C componentList [-u
user] [-p password] [-Y cipher] [-o outfile]
C componentList List of hardware components for exclusion.
by a blank
Possible values:
MMRx_CHy_DIMMz: RDIMMs exclusion
x from 0 to 7
y from 0 to 1
z from 0 to 2
XQPIx: XQPI port exclusion
x from 0 to 6
moduleX: module exclusion
X from 0 to 7
ultracapa: ultracapacitor exclusion

2.23.3. Examples
This section includes examples for the component list option.
2.23.3.1. Remove Exclusion for XQPI Ports

Command
$ bsmRemoveHardwareExclusion.sh -m lanplus –H X.X.X.X –u super -p <password> -C 'XQPI0 XQPI2'
Output
---------------------------------------------------------------------------
XQPI0 removed from exclusion list
XQPI2 removed from exclusion list
---------------------------------------------------------------------------
2.23.3.2. Remove Exclusion for RDIMMs

Command
$ bsmRemoveHardwareExclusion.sh -m lanplus –H X.X.X.X –u super -p <password> -C 'MMR0_CH1_DIMM1
MMR1_CH1_DIMM1 MMR4_CH0_DIMM2 MMR5_CH0_DIMM1'
Output
---------------------------------------------------------------------------
MMR0_CH1_DIMM1 (D4) removed from exclusion list.
---------------------------------------------------------------------------
2.23.3.3. Remove Exclusion for Modules

Command
$ bsmRemoveHardwareExclusion.sh -m lanplus –H X.X.X.X –u super -p <password> -C module0
Output
---------------------------------------------------------------------------
Module0 removed from exclusion list
---------------------------------------------------------------------------
2.23.3.4. Remove Exclusion for Ultracapacity

Command
$ bsmRemoveHardwareExclusion.sh -m lanplus –H X.X.X.X –u super -p <password> -C ultracapa
Output
---------------------------------------------------------------------------
Ultracapa removed from exclusion list.
---------------------------------------------------------------------------

2.24. bsmreset
The bsmreset command is used to forcibly power reset a server, to reset the
BMC.
return code is -1.
If the server is not in the right state to perform the reset command, an error is
displayed.
Note Servers are identified by their DNS name or IP address (-H parameter).
2.24.1. Options
syslog
logged
are logged
q Quiet option: no output
-action Possible values:
BMCreset: BMC cold reset
HARDreset: Hardware reset with OS reboot
FPGAreset: MSM FPGA reset
BCM1reset: MSM BMC1 switch reset
BMC2reset: MSM BMC2 switch reset
UNITreset: other component reset (CMM, ESM…)
u user MC user
are redirected

bsmreset.sh [h] [q] m lanplus H host u user [p password] -a action [o
outfile]

2.24.3. Example
2.24.3.1. Reset the BMC

Syntax
bsmreset.sh [h] [q] [-h level] m lanplus H host u user [p password] -a
BMCreset [o outfile]
2.24.3.2. Hardware Reset with OS Reboot

Syntax
HARDreset [o outfile]
2.24.3.3. Unit Reset

Syntax
UNITreset [o outfile]
2.24.3.4. MSM FPGA Reset

Syntax
FPGAreset [o outfile]
2.24.3.5. MSM BCM1 Switch Reset

The BCM1 switch is connected to modules 0, 1 ,2 , 3. Use this command when
there is no connection between the master module and the slave modules.
Syntax
BCM1reset [o outfile]
2.24.3.6. MSM BCM2 Switch Reset

The BCM2 switch is connected to modules 4, 5, 6, 7. Use this command when
there is no connection between the master module and the slave modules.
Syntax
BCM2reset [o outfile]

2.25. bsmResetAllEMMPartition
The bsmResetAllEMMPartition command is a specific multi-module configuration
tool. It is used to reset the firmware for all partition modules.
return code is -1.
2.25.1. Options
into syslog
logged
are logged
u user MC user
(AES-CBC-128)
are redirected

bsmResetAllEmmPartition.sh [h] [l level] m interface H host [u user]
[p password] [Y cipher] [o outfile]
2.25.3. Example
Command
$ bsmResetAllEMMPartition.sh -m lanplus -H X.X.X.X -u super -p <password>
Output on a bi-modules
---------------------------------------------------------------------------
Sent cold reset command to MC
Sent cold reset command to MC
---------------------------------------------------------------------------

2.26. bsmsdr
The bsmsdr command is used to obtain data from the Sensor Data Repository for all sensors.
-1.
2.26.1. Options
l level Defines the message level to be logged
m interface Target server interface: ipmilan, lanplus(default is
lanplus)
u user MC user
Y cipher Cipher suite ID to be used by the lanplus interface
(default is 3)
list: lists sensor data including type, ID and status
info: displays SDR details
dump: dumps SDR data into a text file
cclear: clears the SDR cache
get: gets specific sensor data either by type, ID,
address or entity
s sensor_ids Specifies sensor names separated by commas
(between double quotes)
i i2csa_addr Specifies the address of the device generating a event
(default is the BMC address)
t sensor_type Specifies sensor type by string or code (0x..) or list
e entity_type Specifies entity type by string or decimal
(entity_id[.entity_instance]) or list
F filename Name of the SDR dump file
X Optional parameter for the list action:
display extended list
x value Optional values for the list action:
all: all sensors
full: Full Sensor Record
compact: Compact Sensor Record
event: Event-Only Record
mcloc: Management Controller Device Locator Record
fru: Fru Device Locator Record
generic: generic
o outfile Output file name

bsmsdr.sh [h] [l level] [m interface] H host [u user p password]
[Y cipher] a action [s sensor_ids] [i i2csa_addr] [t sensor_type]
[e entity_type] [F filename] [X] [x value] [o outfile]
2.26.3. Examples
2.26.3.1. List Sensor Data

Syntax
bsmsdr.sh [h] [l level] [m interface] H host [u user p password]
[Y cipher] a list [X] [x value] [o outfile]
Command
$ bsmsdr.sh H <IP_address> u super p <password> a list X
Output
-----------------------------------------------------------------------
Record ID | ID string | Owner ID | Number | Entity IDs
0x0013 | ACPI Pwr State | 0x20 | 15 | 14.0
0x0014 | Power button | 0x20 | 1 | 23.96
0x101e | Pwr Redundancy | 0x80 | 0 | 19.96
0x101f | CPU_0 Status | 0x80 | 1 | 3.96
0x1020 | CPU_1 Status | 0x80 | 2 | 3.97
0x1021 | PS_0 Status | 0x80 | 3 | 10.96
0x1022 | PS_1 Status | 0x80 | 4 | 10.97
0x1023 | MMR_0 | 0x80 | 5 | 8.96
0x1024 | MMR_1 | 0x80 | 6 | 8.97
0x1025 | MMR_2 | 0x80 | 7 | 8.98
0x1026 | MMR_3 | 0x80 | 8 | 8.99
0x1027 | MMR_4 | 0x80 | 9 | 8.100
0x1028 | MMR_5 | 0x80 | 10 | 8.101
0x1029 | MMR_6 | 0x80 | 11 | 8.102
0x102a | MMR_7 | 0x80 | 12 | 8.103
0x102b | PCI_0 RISER | 0x80 | 13 | 25.96
0x102c | PCI_1 RISER | 0x80 | 14 | 25.97
0x102d | PCI_2 RISER | 0x80 | 15 | 25.98
0x102e | PCI_3 RISER | 0x80 | 16 | 25.99
0x102f | PCI_4 RISER | 0x80 | 17 | 25.100
0x1030 | PCI_5 RISER | 0x80 | 18 | 25.101
0x1031 | PCI_6 RISER | 0x80 | 19 | 25.102
0x1032 | PCI_0 | 0x80 | 20 | 25.96
0x1033 | PCI_1 | 0x80 | 21 | 25.97
0x1034 | PCI_2 | 0x80 | 22 | 25.98
0x1035 | PCI_3 | 0x80 | 23 | 25.99
0x1036 | PCI_4 | 0x80 | 24 | 25.100
0x1037 | PCI_5 | 0x80 | 25 | 25.101
0x1038 | PCI_6 | 0x80 | 26 | 25.102
0x1039 | FAN_0 | 0x80 | 27 | 29.96
0x103a | FAN_1 | 0x80 | 28 | 29.97
0x103b | FAN_2 | 0x80 | 29 | 29.98
0x103c | FAN_3 | 0x80 | 30 | 29.99
0x103d | FAN_4 | 0x80 | 31 | 29.100
0x103e | FAN_5 | 0x80 | 32 | 29.101
0x103f | FAN CABLE 0 | 0x80 | 33 | 30.96
0x1040 | FAN CABLE 1 | 0x80 | 34 | 30.97
0x1041 | PWR CABLE 0 | 0x80 | 35 | 19.96
0x1042 | PWR CABLE 1 | 0x80 | 36 | 19.96
0x1043 | PDB CABLE | 0x80 | 37 | 19.96
0x1044 | UCM CABLE | 0x80 | 38 | 21.96
0x1045 | RL CABLE | 0x80 | 39 | 7.96
0x1046 | UCM | 0x80 | 40 | 21.96
0x1047 | HDD BACKPLANE | 0x80 | 41 | 7.96
0x1048 | CPU_0 DTS Temp. | 0x80 | 45 | 3.96

0x1049 | CPU_1 DTS Temp. | 0x80 | 46 | 3.97
0x104a | BCS Int. Temp. | 0x80 | 47 | 1.96
0x104b | BCS Diode Temp | 0x80 | 48 | 1.96
0x104c | CIX Temperature | 0x80 | 49 | 7.96
0x104d | CIX Inlet1 Temp | 0x80 | 50 | 7.96
0x104e | CIX Inlet2 Temp | 0x80 | 51 | 7.96
0x104f | CIX Near BCS2 | 0x80 | 52 | 7.96
0x1050 | CIX Near BMC | 0x80 | 53 | 7.96
0x1051 | UCM Temperature | 0x80 | 54 | 21.96
0x1052 | UCM MOSFET Temp | 0x80 | 55 | 21.96
0x1053 | LCP Temperature | 0x80 | 56 | 12.96
0x1054 | FAN_0F speed | 0x80 | 57 | 29.96
0x1055 | FAN_1F speed | 0x80 | 58 | 29.97
0x1056 | FAN_2F speed | 0x80 | 59 | 29.98
0x1057 | FAN_3F speed | 0x80 | 60 | 29.99
0x1058 | FAN_4F speed | 0x80 | 61 | 29.100
.....
-----------------------------------------------------------------------
2.26.3.2. Display SDR Details

Syntax
bsmsdr.sh [h] [l level] [m interface] H host [u user p password] [Y
cipher] a info [o outfile]
Command
$ bsmsdr.sh H <IP_address> u super p <password> a info
Output
-----------------------------------------------------------------------
SDR version : 1.5
SDR record count : 453
Free space remaining : 65534 bytes
Most recent addition timestamp : Post-Init 0 s
Most recent erase timestamp : Post-Init 0 s
Get SDR Repository Allocation Information Command : unsupported
Reserve SDR Repository Command : supported
Partial Add SDR Command : supported
Delete SDR Command : supported
Modal/non-modal SDR Repository Update operation : modal supported
SDR could not be written due to lack of space : No
-----------------------------------------------------------------------
2.26.3.3. Dump SDR Data into a Text File

Syntax
cipher] a dump F filename [o outfile]
Command
$ bsmsdr.sh H <IP_address> u super p <password> a dump F /tmp/dump203.txt
Output
-----------------------------------------------------------------------
Dumping Sensor Data Repository to '/tmp/dump203.txt'
-----------------------------------------------------------------------
2.26.3.4. Clear SDR Cache

Syntax
cipher] a cclear [o outfile]
Command
$ bsmsdr.sh H <IP_address> u super p <password> a cclear

2.26.3.5. Get Data for Specific Sensors
Note The -s sensorids, –t sensor_type and -e entity_type options are

exclusive.
Get Data by Sensor Type

Use the -t option with the get action to get data by sensor type.
Syntax
cipher] a get t sensor_type [o outfile]
Note The list of sensor types can be obtained by using the -t list option.
Command
$ bsmsdr.sh H <IP_address> u super p <password> a get t list
Output
-----------------------------------------------------------------------
Sensor Types:
Battery
Button/Switch
Cable/Interconnect
Chassis
Chip Set
Cooling Device
Current
Entity Presence
Event Logging Disabled
Fan
Microcontroller/Coprocessor
OEM Reserved
OS Critical Stop
Other Units Based Sensor
Platform Security Violation Attempt
Power Supply
Power Unit
Processor
System ACPI Power State
System Boot Initiated
System Event
Temperature
Version Change
Voltage
Watchdog 2
-----------------------------------------------------------------------
Command
$ bsmsdr.sh H <IP_address> u super p <password> a get t Fan
Output
-----------------------------------------------------------------------
Record ID | ID string |Owner ID| Number| Event | Entity | Sensor
Reading
0x1054 | FAN_0F speed | 0x80 | 57 | N/A | 29.96 | N/A
0x105a | FAN_0R speed | 0x80 | 63 | N/A | 29.96 | N/A
0x105b | FAN_1R speed | 0x80 | 64 | N/A | 29.97 | N/A
0x105c | FAN_2R speed | 0x80 | 65 | N/A | 29.98 | N/A
0x105d | FAN_3R speed | 0x80 | 66 | N/A | 29.99 | N/A

0x105e | FAN_4R speed | 0x80 | 67 | N/A | 29.100 | N/A
0x105f | FAN_5R speed | 0x80 | 68 | N/A | 29.101 | N/A
0x1060 | FAN_0 HP Fault| 0x80 | 69 | N/A | 29.96 |
0x1061 | FAN_1 HP Fault| 0x80 | 70 | N/A | 29.97 |
0x1062 | FAN_2 HP Fault| 0x80 | 71 | N/A | 29.98 |
0x1063 | FAN_3 HP Fault| 0x80 | 72 | N/A | 29.99 |
0x1064 | FAN_4 HP Fault| 0x80 | 73 | N/A | 29.100 |
0x1065 | FAN_5 HP Fault| 0x80 | 74 | N/A | 29.101 |
0x205a | FAN_0R speed | 0x82 | 63 | N/A | 29.96 | N/A
0x205b | FAN_1R speed | 0x82 | 64 | N/A | 29.97 | N/A
0x205c | FAN_2R speed | 0x82 | 65 | N/A | 29.98 | N/A
0x205d | FAN_3R speed | 0x82 | 66 | N/A | 29.99 | N/A
0x205e | FAN_4R speed | 0x82 | 67 | N/A | 29.100 | N/A
0x205f | FAN_5R speed | 0x82 | 68 | N/A | 29.101 | N/A
0x2060 | FAN_0 HP Fault| 0x82 | 69 | N/A | 29.96 |
0x2061 | FAN_1 HP Fault| 0x82 | 70 | N/A | 29.97 |
0x2062 | FAN_2 HP Fault| 0x82 | 71 | N/A | 29.98 |
0x2063 | FAN_3 HP Fault| 0x82 | 72 | N/A | 29.99 |
0x2064 | FAN_4 HP Fault| 0x82 | 73 | N/A | 29.100 |
0x2065 | FAN_5 HP Fault| 0x82 | 74 | N/A | 29.101 |
-----------------------------------------------------------------------
Get Data by Sensor ID

Use the -s option with the get action to get data for a sensor specified by its
ID.
Syntax
cipher] a get s sensor_ids [i i2csa_addr] [o outfile]
Command
$ bsmsdr.sh H <IP_address> u super p <password> a get s 'FAN_1R speed'
Output
-----------------------------------------------------------------------
Record ID: 4187
Record Type: Full Sensor Record (1h)
ID String FAN_1R speed
Sensor Type: Fan (4h)
Sensor Number: 64
IPMB Slave Address: 40h
Sensor Owner ID 80
Sensor Owner LUN: 0h
Channel Number: 0h
Entity ID: fan/cooling device (29)
Entity Instance: 97
Entity Instance Type: Physical Entity
Event/Reading Type Code: 1h
B: 0
M: 100
R Exponent: 0
B Exponent: 0
Linearization: linear (0h)
Analog Data Format: unsigned (0h)
Tolerance: 100.000000 RPM
Resolution: 100.000000 RPM
Lower Critical Threshold: 3500.000000 RPM
Upper Critical Threshold: N/A
Lower Non-Critical Threshold: N/A
Upper Non-Critical Threshold: N/A
Lower Non-Recoverable Threshold: N/A

Upper Non-Recoverable Threshold: N/A
Sensor Min. Reading: 100.000000 RPM
Sensor Max. Reading: 25400.000000 RPM
Normal Min.: 0.000000 RPM
Normal Max.: 0.000000 RPM
Nominal Reading: 0.000000 RPM
Accuracy: 0.000000
Sensor Direction: Unspecified
Sensor Reading: N/A
Sensor Event: N/A
-----------------------------------------------------------------------
Get Data by Entity

Use the -e option with the get action to get data by entity type.
Syntax
cipher] a get e entity_type [o outfile]
Note The list of entity types can be obtained by using the -e list option.
Command
$ bsmsdr.sh H <IP_address> u super p <password> a get e list
Output
-----------------------------------------------------------------------
Entity IDs:
1 other
3 processor
6 system management module
7 system board
8 memory module
10 power supply
12 front panel board
14 power system board
19 power unit/power domain
21 power management/power distribution board
23 system chassis
25 Other chassis board
29 fan/cooling device
30 cooling unit/cooling domain
31 cable/interconnect
34 System Firmware
46 Management Controller Firmware
212 OEM System Integrator
-----------------------------------------------------------------------
Command
$ bsmsdr.sh H <IP_address> u super p <password> a get e 3
Output
-----------------------------------------------------------------------
Record ID | ID string |Owner ID| Number| Entity | Record Type
0x100f | CPU_0 | | | 3.96 | LOG FRU @03h
0x1010 | CPU_1 | | | 3.97 | LOG FRU @04h
0x101f | CPU_0 Status | 0x80 | 01 | 3.96 | Compact Sensor Record
0x1020 | CPU_1 Status | 0x80 | 02 | 3.97 | Compact Sensor Record
0x1048 | CPU_0 DTS Temp.| 0x80 | 45 | 3.96 | Full Sensor Record
0x10a6 | CPU_0 fault | 0x80 | 141 | 3.96 | Compact Sensor Record
0x200f | CPU_0 | | | 3.96 | LOG FRU @03h
0x2010 | CPU_1 | | | 3.97 | LOG FRU @04h

-----------------------------------------------------------------------
Command
$ bsmsdr.sh H <IP_address> u super p <password> a get e processor
Output
-----------------------------------------------------------------------
Record ID | ID string | Owner ID | Number | Entity | Record Type
0x100f | CPU_0 | | | 3.96 | LOG FRU @03h
0x1010 | CPU_1 | | | 3.97 | LOG FRU @04h
0x200f | CPU_0 | | | 3.96 | LOG FRU @03h
0x2010 | CPU_1 | | | 3.97 | LOG FRU @04h
0x2049 | CPU_1 DTS Temp | 0x82 | 46 | 3.97 | Full Sensor Record
-----------------------------------------------------------------------

2.27. bsmseld
The bsmseld command logs new SEL messages in the syslog file.
Note This command is for remote OS Linux only.
2.27.1. Options
H host Module IP address
u user MC user
start: starts the SEL syslog logging daemon
stop: stops the SEL syslog logging daemon
-M module Module identifier (if not set, action is done on all the
modules)

bsmseld.sh [h] m lanplus H host [u user p password] a action [M
module]

2.27.3. Examples
2.27.3.1. Start the SEL logging daemons for all the modules
Command
$ bsmseld.sh -H X.X.X.X -u super -p <password> -a start
Check the daemons are launched

---------------------------------------------------------------------------
$ ps -ef | grep seld
---------------------------------------------------------------------------
Output
---------------------------------------------------------------------------
root 18828 1 0 11:00 ? 00:00:00 /opt/BSMHW_NG/bin/../sbin/ipmiseld -D
lanplus -h 172.31.130.10 -u -p -I 3 --target-slave-address=0x80
--interpret-oem-data --poll-interval=60 --ignore-sdr -v
lanplus -h 172.31.130.10 -u -p -I 3 --target-slave-address=0x8a
lanplus -h 172.31.130.10 -u -p -I 3 --target-slave-address=0x8c
lanplus -h 172.31.130.10 -u -p -I 3 --target-slave-address=0x8e
---------------------------------------------------------------------------
2.27.3.2. Start the SEL logging daemon for a module

Command
$ bsmseld.sh -H X.X.X.X -u super -p <password> -a start -M 1
Check the daemon is launched

---------------------------------------------------------------------------
$ ps -ef | grep seld
---------------------------------------------------------------------------
Output
---------------------------------------------------------------------------
---------------------------------------------------------------------------
2.27.3.3. Stop SEL logging daemons

Command
$ bsmseld.sh -H X.X.X.X -u super -p <password> -a stop

2.28. bsmsensor
The bsmsensor command is used to direct sensor values to standard output.
return code is -1.
The sensor values are displayed in stdout, as follows:
<sensor addr> | <sensor id> | <sensor value> | <sensor unit> | <status> |
<lower non recoverable> | <lower critical> | <lower non critical> | <upper non
critical> | <upper critical> | <supper non recoverable>
If the -v option is specified, one sensor is displayed per field, over several rows
depending on the format.
<label>: <value>
The fields and labels display may change according to servers and to sensors.
Notes • Servers are identified by their DNS name or IP address (-H

parameter).
• Sensor type (see definition in IPMI specification) may be specified
either with the sensor type code in hexadecimal (i.e. t 0x01 for
temperature) or with the sensor type string (i.e. t Power Unit).
• -s sensorid and –t type parameters are exclusive.
2.28.1. Options
syslog
logged
are logged
v Displays details of each sensor. See output section
below
u user MC user
(AES-CBC-128)
c Used in conjunction -v to get sensor information in a
more compact form on IPMI servers
are redirected

s sensorid Specifies a list of sensor(s), specified between quotes
and separated by comma(s), to be read
t type Processes sensors of the specified type only (as
defined in IPMI specification)
a Processes only analog sensors of the type specified
with t type
Specific Multi-module Option

-i module Specifies a module number or module address
or partition to display the sensors of all the modules
constituting the partition
or platform to display the sensors of all the modules
constituting the platform

bsmsensor.sh [h] [v] m lanplus H host u user [p password] [c] [o
outfile] [l level] [s sensorid_list] [t type [a]] [Y cipher]
2.28.3. Examples
This section includes examples for remote and local hardware management.

Command to display a single sensor
$ bsmsensor.sh -m lanplus -H X.X.X.X -u super -p <password> -s 'CPU_0 Status'
Output
---------------------------------------------------------------------------
Record ID: 4127
ID String: CPU_0 Status
Sensor Type: Processor (7h)
Sensor Number: 1
Sensor Owner ID: 80h
Channel Number: 0h
Entity ID: processor (3)
Entity Instance: 96
Event/Reading Type Code: 6Fh
Sensor Event: N/A
Record ID: 8223
ID String: CPU_0 Status
Sensor Type: Processor (7h)
Sensor Number: 1
Sensor Owner ID: 82h
Channel Number: 0h
Entity ID: processor (3)
Entity Instance: 96
Event/Reading Type Code: 6Fh
Sensor Event: N/A
---------------------------------------------------------------------------
Command to display all the sensors with the same type
$ bsmsensor.sh -m lanplus -H X.X.X.X -u super -p <password> -t Power_Supply

Output
---------------------------------------------------------------------------
ADDR | Name | Owner ID | Reading | Units | State | Lower NR
| Lower C | Lower NC| Upper NC| Upper C | Upper NR| Event
0x00800003 | PS_0 Status | 0x80 | N/A | N/A | 0x0100 | N/A

| N/A | N/A | N/A | N/A | N/A | 'Presence detected'



| N/A | N/A | N/A | N/A | N/A |'Presence detected'
---------------------------------------------------------------------------

Syntax
bsmsensor.sh [h] [v] m ipmidrv [o outfile] [l level] [s sensorid_list]
[t type [a]] [c]
Command to display power supply sensor
$ bsmsensor.sh -m ipmidrv -t "Power Supply"
Output
Command to display power supply sensor
$ bsmsensor.sh -m ipmidrv -t "CPU_0 Status"
Output
---------------------------------------------------------------------------
Locating sensor record…
Sensor Addr : 0x00800001
Sensor ID : CPU_0 Status (0x1)
Owner ID : 0x80
Entity ID : 3.96 (Processor)
Sensor Type (Discrete): Processor
States Asserted : Processor
[Presence detected]
---------------------------------------------------------------------------

2.29. bsmSetConfParam
The bsmSetConfParam command is used to set the values of various
configuration parameters.
return code is -1.
Notes • The configuration parameter value can be set even with the action
option or with the keyname option.
• The options -a and -k are exclusive.
2.29.1. Options
syslog
0: no messages are logged (default)
logged
are logged
setPowerRestorePolicy: sets the power restore policy
(On, Off or Restore) that follows an AC power loss
setPrimaryNTP: sets the address for the primary NTP
server for the date and the time
setSecondaryNTP: sets the address for the secondary
NTP server for the date and the time
setDisableBCS: disables the BCS
setBiosNoMemoryHole: removes all gaps in the
memory allocation for the modules. For VMware only.
setBiosVMwareMaxMemPerModule: pre-allocates DRAM
slice per module. For VMware only.
SetBiosBootTimeout: sets the BIOS boot timeout.
setTSnumber: sets the Technical State number
-k keyname BMC key put between quote. Keyname format:
'bmc.xxxxx'
-u user MC user
(AES-CBC-128)
o outfile Output file name to which the stdout and stderr
outputs are redirected

bsmSetConfParam.sh [h] [l level] a action m interface H host -x value |
-k keyname [u user] [p password] [Y cipher] [o outfile]
2.29.3. Examples
2.29.3.1. Set the Power Restore Policy

Syntax
bsmSetConfParam.sh [h] a setPowerRestorePolicy m interface H host
x value [u user] [p password] [Y cipher] [o outfile] [l level]
Options
x value on: chassis always powers on after AC mains
electricity is switched on or returns following an
interruption.
off: chassis always stays powered off after AC mains
electricity is switched on, power button is pushed or
command required to power on system is run.
restore: after AC main electricity is switched on or
returns, power is restored to the state that was in
effect when AC mains electricity was switched off or
lost.
Command
$ bsmSetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a setPowerRestorePolicy –x on
2.29.3.2. Set the Primary NTP Server IP Address

Syntax
bsmSetConfParam.sh [h] a setPrimaryNTP m interface H host -x value
Option
-x value Sets NTP server IP address
Command
bsmSetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a setPrimaryNTP -x X.X.X.X
Output
-------------------------------------------------------------------
NTP server set successfully
-----------------------------------------------------------------------

2.29.3.3. Set the Secondary NTP Server IP Address
Syntax
bsmSetConfParam.sh [h] a setSecondaryNTP m interface H host -x value
Command
bsmSetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a setSecondaryNTP -x X.X.X.X
Output
-------------------------------------------------------------------
NTP server set successfully
-----------------------------------------------------------------------
2.29.3.4. Disable the BCS

Syntax
bsmSetConfParam.sh [h] a setDisableBCS m interface H host -x value
Option
-x value Possible values: yes, no
Command
bsmSetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a setDisableBCS -x yes
Output
---------------------------------------------------------------------------
BCS disabling set successfully.
---------------------------------------------------------------------------
2.29.3.5. Set the BIOS Boot Timeout

Command
bsmSetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a setBiosBootTimeout -x 10
Output
---------------------------------------------------------------------------
Bios boot timeout set successfully.
---------------------------------------------------------------------------
2.29.3.6. Set DRAM Compaction Feature for VMware System
Note This feature is available for VMware systems only. It removes all gaps
in the memory allocation for the modules. This feature is only available
for the 8 sockets BIOS images for VMware systems.
Syntax
bsmSetConfParam.sh [h] a setBiosNoMemoryHole m interface H host -x value
Option
-x value Possible values: yes, no
Command
bsmSetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a setBiosNoMemoryHole -x yes

2.29.3.7. Pre-allocation of DRAM per Module
Note This feature is available for VMware system only and allows you to
pre-allocate DRAM slice per module, according to the DRAM amount per
module and the physical memory address limits supported by the OS.
Syntax
bsmSetConfParam.sh [h] a setBiosVMwareMaxMemPerModule m interface H host
-x value [u user] [p password] [Y cipher] [o outfile] [l level]
Option
-x value Possible values:
0 (8TB)
1 (4TB)
2 (2TB)
3 (1TB)
4 (512GB)
Command
bsmSetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a setBiosVMwareMaxMemPerModule -x
3
2.29.3.8. Set the Technical State Number

Syntax
bsmSetConfParam.sh [h] a setTSnumber m interface H host -x value
Option
-x value Technical State number put between quote
bsmSetConfParam.sh -m lanplus -H X.X.X.X -u super -p <password> -a setTSnumber -x 'Mesca2 009.01'
Output
---------------------------------------------------------------------------
Successfully set key mc.technical_state to Mesca2 009.01.
---------------------------------------------------------------------------

2.30. bsmSetPartitions
The bsmSetPartitions command is a specific multi-module configuration tool. It
is used to set global partitioning. All partitions are defined in one particular
way. Master identifier(s) is(are) set to the default value (the lower module
number of the partition).
Master identifier and partition name can be redefined after using the
bsmSetPartitions command by using the bsmSetPartition command.
return code is -1.
Note Modules of the new partition must have been powered OFF first.
2.30.1. Options
into syslog
logged
are logged
u user MC user
-P partition_name Partition name
C composition Partition composition:
for a mono-module: possible value is 0. It means
one partition composed with module 0
for a bi-module: possible values are 01 or 0_1

01 means on partition composed with modules 0 and
1
0_1 means two partitions : one composed with
module 0 and one composed with module 1
for a tri-module: possible values are 012, 0_12,

1_02, 2_01 or 0_1_2
012 means one partition composed with module 0, 1
and 2.
module 0 and one composed with modules 1 and 2.
0_1_2 means three partitions : one composed with
module 0, one composed with module 1 and one
composed with module 2
for a quadri-module: possible values are 0123,
0_123, 1_023, 2_013, 3_012, 01_23, 02_13, 03_12,
0_1_23, 0_2_13, 0_3_12, 1_2_03, 1_3_02, 2_3_01
or 0_1_2_3.
0123 means one partition composed with module 0,

1, 2 and 3
module 0 and one composed with modules 1, 2 and 3
0_1_23 means three partitions : one composed with
module 0, one composed with modules 1 and 2 and
one composed with module 3
0_1_2_3 means four partitions : one composed with
module 0, one composed with module 1, one
composed with module 2 and one composed with
module 3
r reset If present, bmc reset will not be executed (not
recommended)
(AES-CBC-128)
are redirected

bsmSetPartitions.sh [h] [l level] [m interface] H host –C composition [-r
reset] [u user] [p password] [Y cipher] [o outfile]
2.30.3. Example
The example below creates 2 partitions that are composed of 2 modules each.
Command
$ bsmSetPartitions.sh -m lanplus -H X.X.X.X -u super -p <password> -C03_12
Output
---------------------------------------------------------------------------
New partition composition set on module0.
Module 0's BMC is resetting.
Module 1's BMC is resetting.
---------------------------------------------------------------------------

2.31. bsmSetPlatformLevelParam
The bsmSetPlatformLevelParam command is used to set a platform IP address
prefix. If neither the platform name nor the IP prefix is set, nothing is done.
The setting is applied to all modules included in the platform.
return code is -1.
Note • -I prefix_ip is a specific for multi-module parameter.
2.31.1. Options
into syslog
logged
are logged
u user MC user
N name Platform label (14 characters maximum)
I prefix_ip Platform IP address prefix
-F is_flexible Partitions can be changed (possible values 'yes' or
'not')
-M module Module identifier
(AES-CBC-128)
are redirected

bsmSetPlatformLevelParam.sh [h] [l level] m interface H host [u user]
[p password] [[N name][I prefix_ip]] [[-a action][-M module][-x value]]
[Y cipher] [o outfile]

2.31.3. Examples
This section includes examples for the IP prefix.
Command
$ bsmSetPlatformLevelParam.sh -m lanplus -H X.X.X.X -u super -p <password> -I 172.32
Output
---------------------------------------------------------------------------
Address IP prefix set for module0.
Address IP prefix set for module1.
---------------------------------------------------------------------------

2.32. bsmsnapshot
The bsmsnapshot command is used to collect sensor data, SELs, messages,
FRU, BMC configuration files, BIOS logs and firmware versions in an archive
file. The tar.gz file is created in the directory indicated or in the default one.
return code is -1.
2.32.1. Options
into syslog
logged
are logged
-d directory Directory path for tar.gz file (default: /var)
u user MC user
(AES-CBC-128)
are redirected

bsmsnapshot.sh [h] [l level] [m interface] [H host] [-d directory] [u
user] [p password] [Y cipher] [o outfile]
2.32.3. Examples
This section includes archive creation examples.
2.32.3.1. Create an Archive in the Default Directory

Command
$ bsmsnapshot.sh -m lanplus -H X.X.X.X -u super -p <password>
Output
---------------------------------------------------------------------------
$File /var/BSMHW_NG/chassis4_22-03-13_09-57-59.gz was created
---------------------------------------------------------------------------

2.32.3.2. Create an Archive in the Directory Specified
Command
$ bsmsnapshot.sh -m lanplus -H X.X.X.X -u super -p <password> -d '/tmp'
Output
---------------------------------------------------------------------------
$File /tmp/Capri1bi_141014_154148.gz was created
---------------------------------------------------------------------------

2.33. bsmsol
The bsmsol command is used to establish a SerialOverLan session and to
obtain or to set Serial-Over-Lan parameters.
Notes • Enter ”~.” to close the session.

• Only one SerialOverLan session can be opened on a given target
server.
2.33.1. Options
syslog
logged
are logged
H host Module IP address or DNS name.
set: sets Serial-Over-Lan parameters
info: obtains Serial-Over-Lan parameters
activate: activates SerialOverLan session
deactivate: closes SerialOverLan session
-k keyname Keyname for set action. Keyname must be put
between quotes
-x value Value for set action. Value must be put between
quotes
Keyname Values
Enable_SOL Yes, No
Force_SOL_Payload_Encryption Yes, No
Force_SOL_Payload_Authentication Yes, No
SOL_Privilege_Level User, Operator, Administrator,
OEM_Proprietary
Character_Accumulate_Interv al time in 5ms increments
Character_Send_Threshold N: a number
SOL_Retry_Count N: a number
SOL_Retry_Interval time in 10ms increments
Non_Volatile_Bit_Rate Serial, 9600, 19200, 38400, 57600,
115200
Volatile_Bit_Rate Serial, 9600, 19200, 38400, 57600,
115200
Table 2-1. Keyname and value for set action

-u user MC user
(AES-CBC-128)
-L priv Remote session privilege level (default: Administrator)
-o outpufile Output file name to which stdout and stderr outputs
are redirected

bsmsol.sh [h] m lanplus -a action [-k keyname] [-x value] H host u user
[p password] [l level] [Y cipher]
2.33.3. Examples
2.33.3.1. Activate Serial-Over-LAN Session

Command
$ bsmsol.sh -m lanplus -H X.X.X.X -u root -p root -a activate
Output
---------------------------------------------------------------------------
[SOL Established]
&? - this menu
&. - exit
&B - generate break
&D - send DEL character
&& - & character
&
[closing the connection]
---------------------------------------------------------------------------
2.33.3.2. Obtain Serial-Over-LAN Parameters

Command
$ bsmsol.sh -m lanplus -H X.X.X.X -u root -p root -a info
Output
---------------------------------------------------------------------------
Enable_SOL Yes
SOL_Privilege_Level User
Force_SOL_Payload_Authentication Yes
Force_SOL_Payload_Encryption Yes
Character_Accumulate_Interval (unit is 5ms) 10
Character_Send_Threshold 80
SOL_Retry_Count 7
SOL_Retry_Interval (Unit is 10ms)10
Non_Volatile_Bit_Rate 115200
Volatile_Bit_Rate 115200
SOL_Payload_Port_Number 623
---------------------------------------------------------------------------

2.34. bsmUCMcmd
bsmUCMcmd.sh is used to perform UCM management.
-1.
2.34.1. Options
syslog
0: no messages are logged (default)
logged
are logged
charge: charges the UCM
discharge: discharges the UCM
H host BMC IP address
-M module Module identifier from 0 to 7 (if not set, action is done
an all modules of the partition)
u user CMC user
p password User password
(AES-CBC-128).
o outfile Output file name to which the stdout and stderr
outputs are redirected.

Syntax
bsmUCMcmd.sh [h] [l level] a action H host [u user] [p password] [m
interface] -M module [Y cipher] [o outfile]
2.34.3. Examples
2.34.3.1. Charge UCM

Command
$ bsmUCMcmd.sh -H X.X.X.X -u super -p <password> -a charge -M 0
Output
---------------------------------------------------------------------------
Ultracapacitor charging
---------------------------------------------------------------------------

2.34.3.2. Discharge UCM
Command
$ bsmUCMcmd.sh -H X.X.X.X -u super -p <password> -a discharge -M 0
Output
---------------------------------------------------------------------------
Ultracapacitor discharging
---------------------------------------------------------------------------

Chapter 3. Field Hardware Management Commands
The maintenance Hardware Management CLIs comprises the following
commands:
• bsmMAINTBMCcfg, on page 3-2
• bsmMAINTDisplayModuleConfigur ation, on page 3-3
• bsmFWupg, on page 3-5
• bsmPSUcmd, on page 3-8

manual.
manuel.
W059 WARNING
W059:
Only qualified support personnel are authorized to use Maintenance
Hardware Management CLIs.
Chapter 3. Field Hardware Management Commands 3-1

3.1. bsmMAINTBMCcfg
The bsmMAINTBMCcfg command is used to restore some specific default factory
keys in the configuration file.
return code is -1.
3.1.1. Options
restoreFactory: restores the default factory keys
u user MC user

bsmMAINTBMCcfg.sh [-h] [m interface] -H host [-u user] [-p password] -a
action
3.1.3. Example
This section includes examples for the action list option.
3.1.3.1. Restore the Factory Keys

Command
$ bsmMAINTBMCcfg.sh –H X.X.X.X -u super -p <password> -a restoreFactory
Output
---------------------------------------------------------------------------
Factory keys restored.
---------------------------------------------------------------------------
3-2 Reference Guide

3.2. bsmMAINTDisplayModuleConfiguration
The bsmMAINTDisplayModuleConfiguration command is a specific multi-module
configuration tool. It is used to get all configuration details for a module.
-1.
3.2.1. Options
1: only the FAILED completion of the command is logged
3: FAILED and successful completion of the command are
logged
u user MC user
-Y cipher Cipher suite ID to be used by lanplus interface: from 0 to 14
according to the security level
Default is 3: Authentication (RAKP-HMAC-SHA1), Integrity
(HMAC-SHA1-96), Confidentiality (AES-CBC-128)

bsmMAINTDisplayModuleConfiguration.sh [-h] [-l level][m interface] -H host
[-u user] [-p password] [-Y cipher]

3.2.3. Example
Command
$ bsmMAINTDisplayModuleConfiguration.sh –H X.X.X.X
Output
---------------------------------------------------------------------------
Module X.X.X.X configuration
Configuration keys:
mc.module_id: 1
mc.partition_composition: 15
mc.module_count: 4
mc.platform_id: 153
mc.force_multi_legacyIOH: no
mc.CF9_reset_disabled: no
mc.OS_shutdown_disabled: no
mc.BCS_snoop_mode_in_mono_module: no
mc.LOM_directories_disabled: no
mc.REM_directories_disabled: no
mc.BCS_timeouts_disabled: yes
mc.BIOS_timeout_sec: 60
mc.flexible: yes
bmc.power.linkspeeds.cpu_cpu_link: 6_4
bmc.power.linkspeeds.cpu_ioh_link: 6_4
bmc.power.linkspeeds.cpu_bcs_link: 6_4
bmc.power.linkspeeds.bcs_ioh_link: 6_4
bmc.power.linkspeeds.bcs_bcs_link: 4
network.inhibit_phy_reset_of_shared_eth_ctrl: yes
EMM states:
Power state: off
CPU full exclusion: none
CPU partial exclusion: none
Error mode: Normal
Functional profile 0:
Mono threading mode
00 enabled cores per socket (0=all)
1024GB max memory per module
BCS non degraded mode
---------------------------------------------------------------------------
3-4 Reference Guide

3.3. bsmFWupg
The bsmFWupg command is used to upgrade the firmware of Remote
Management Modules.
This command is available only for ipmilan servers with Raritan Remote
Management Modules that can be manipulated with the KiraTool command line
tool, and on Bull servers which use the bulloem command extension for
ipmitool.
Note For a multimodule platform, if the module number (M) is not

indicated, all the modules contained in the partition will be impacted.
For example, for a partition containing modules 0 and 1, upgrading the
BMC with the IP address of the module 0 without using M option
implies the upgrade of the BMC of the module 1 too.
return code is -1.
3.3.1. Options
F fw_binfile Name of the firmware binary file used during the
upgrade
d fw_bindir Directory where the firmware binary file is (full path)
Default value is /tmp
a action Possible values for a component (identified by
component_id) on the module (specified by
module_id):
ver Displays the firmware version
of the component
upg Upgrades the firmware of the
component
listhw Displays the list of
components which can be upgraded
E component_id Component name (all for all components)
M module_id Module ID, from 0 to 3
m interface Target server interface: lanplus, ipmidrv. If not
present, kcs driver will be used
u user MC user
are redirected

bsmFWupg.sh [h] H host –F [fw_binfile] [u user]
[p password] a action [E component] [M module] [m interface]
[d fw_bindir] [o outfile]

3.3.3. Examples
This section includes examples for the actions that can be performed.
3.3.3.1. Display the List of the Components that can be Upgraded

Command
$ bsmFWupg.sh -a listhw –H X.X.X.X -u super -p <password>
Output
---------------------------------------------------------------------------
Module 0 :
LCP
BIOS
ETHERNET
Main FPGA
PCPLD
MCPLD
UCMPM
UCMCPLD
PM1CPLD
PM2CPLD
MEMR0 PM
MEMR1 PM
MEMR2 PM
MEMR3 PM
MEMR4 PM
MEMR5 PM
MEMR6 PM
MEMR7 PM
PSU1
PSU2
MC (*)
(*) stands for Management controllers , i.e. BMC , CMC ...
Module 1 :
LCP
BIOS
ETHERNET
Main FPGA
PCPLD
MCPLD
UCMPM
UCMCPLD
PM1CPLD
PM2CPLD
MEMR0 PM
MEMR1 PM
MEMR2 PM
MEMR3 PM
MEMR4 PM
MEMR5 PM
MEMR6 PM
MEMR7 PM
PSU1
PSU2
MC (*)
(*) stands for Management controllers , i.e. BMC , CMC ...
---------------------------------------------------------------------------
3.3.3.2. Display the Firmware Version

Command
$ bsmFWupg.sh –a ver –H X.X.X.X –u super -p <password> –m lanplus –E LCP –M 1
3-6 Reference Guide

3.3.3.3. Upgrade the BMC Firmware
Command
$ bsmFWupg.sh –a upg –H X.XX.X –u super
-p <password> –F “fw-wub-kira_bulldc_150100_1047.bin” –E BMC
Command specifying the directory where the firmware binary file is:
$ bsmFWupg.sh a upg H X.X.X.X u super p <password> d /Tools/Upgrade
F fwwubwpcm450_bulldc_MESCA_111100_1202.bin E BMC
3.3.3.4. Display all Firmware Versions

Command
$ bsmFWupg.sh –a ver –H X.X.X.X –u super -p <password> –E all -M 0

3.4. bsmPSUcmd
The bsmPSUcmd command is used to manage PSU redundancy. This command
is used only for maintenance operations.
return code is -1.
W059 WARNING
W059:
Only qualified support personnel are authorized to use Maintenance
Hardware Management CLIs.
3.4.1. Options
syslog
logged
are logged
H host Module IP addresses or DNS names
getTime: returns the time set for the PSU cold
redundancy test
setTime: sets the time (hh:mm) for the PSU cold
redundancy test
get_psu_redundancy: gets the power supply
redundancy policy
set_psu_redundancy: sets the power supply
redundancy policy
test_psu_redundancy: launches the PSU cold
redundancy test immediately
-x time Time with format hh:mm.
u user MC user
(AES-CBC-128)
are redirected
3-8 Reference Guide

bsmPSUcmd.sh [-h] [-l level] [m interface] -H host -a action [-x time] [-u
user] [-p password] [-Y cipher] [-o outfile]
3.4.3. Examples
This section includes for the cold redundancy test.
3.4.3.1. Get Time for PSU Cold Redundancy Test

Command
$ bsmPSUcmd.sh –H W.W.W.W -u super -p <password> -a getTime
Output
---------------------------------------------------------------------------
Cold redundancy for PSU set to 10h 25mn
---------------------------------------------------------------------------
3.4.3.2. Set Time for PSU Cold Redundancy Test

Options
x value Time (hh:mm)
Command
$ bsmPSUcmd.sh –H W.W.W.W -u super -p <password> -a setTime -x 10:50
Output
---------------------------------------------------------------------------
Cold redundancy for PSU set to 10h 50mn
---------------------------------------------------------------------------
3.4.3.3. Enable Power Supply Redundancy

Options
x value Possible values:
yes
no
Command
$ bsmPSUcmd.sh -m lanplus -H X.X.X.X -u super -p <password> -a set_psu_redundancy -x yes
Output
---------------------------------------------------------------------------
Module 0 - power supply redundancy successfully set to yes.
---------------------------------------------------------------------------
3.4.3.4. Display PSU Redundancy

Command
$ bsmPSUcmd.sh -m lanplus -H X.X.X.X -u super -p <password> -k 'get_psu_redundancy'
Output
--------------------------------------------------------------------------
-module 0 - power supply redundancy is set to yes
--------------------------------------------------------------------------

3.4.3.5. Test PSU Cold Redundancy Immediately
Command
$ bsmPSUcmd.sh -H X.X.X.X -u super -p <password> -a test_psu_redundancy
Output
---------------------------------------------------------------------------
Command completed normally
---------------------------------------------------------------------------

Appendix A. Server ON / OFF Status Codes
This appendix lists the interconnection between the ON / RUNNING /
TRANSIENT / OFF states returned by the bsmpower.sh a status command
and the server states.
OFF corresponds to server states:
INACTIVABLE
INACTIVE
TRANSIENT corresponds to server states:
POWERING ON
POWERING ON FAILED
TIMEOUT DURING POWER ON
POWERING ON SUSPENDED
POWERING DOWN
POWER DOWN FAILED
TIMEOUT DURING POWER DOWN
ON corresponds to server states:
DOMAIN HALTED
POWERED ON LOADING BIOS
BIOS READY STARTING EFI
BIOS LOADING TIMEOUT
RECOVERING BIOS
TIMEOUT DURING START EFI
RUNNING corresponds to server states:
EFI STARTED BOOTING OS
RUNNING
Appendix A. Server ON / OFF Status Codes A-1

Appendix B. User/Password Internal Authentication
File
This appendix contains all useful information about authentication.
B.1. User/Password Authentication

Most of the Hardware Management Commands need a user/password
authentication in order to access a target identified by the platform manager
(specified by ‐H host).
The password information used by the Hardware Management Commands may
be either specified in the command, or extracted from an authentication
internal file if no password is specified in the command.
This internal authentication file contains the list of targets. The targets are
identified by their role and DNS name, e.g. HWMGR_mgr1:
- platform manager (role : manager, identified by its DNS name),
This file can be accessed by dedicated users/passwords.
It is created and managed using the bsmcfg_auth_cmd command.
The bsmcfg_auth_cmd command is used to:
• Add an entry defined by: user + password + target
• Delete an entry defined by: user + target
• Get the encoded password for an entry defined by: user + target
• Get the decoded password for an entry defined by: user + target
• List the entries
The password information is stored in the authentication internal file as a
base64 encoded string.
Appendix B. User/Password Internal Authentication File B-1

B.2. bsmcfg_auth_cmd
The bsmcfg_auth_cmd command manages the internal authentication file:
return code is -1.
Note For servers using the ipmilan model, it is possible to use the same
user/password authentication for all the servers available. This can be
done by setting “*" as the manager parameter.
B.2.1. Options
‐h Displays command usage
‐a action Possible values:
add: adds a target to the list of targets in the internal
authentication file that can be accessed with a
dedicated user/password
del: deletes a target from the list of targets that can
be accessed by a user from the internal authentication
file
getE: extracts the encoded password needed to access
a target with a dedicated user from the internal
authentication file
getD: extracts the password needed to access a target
for a user from the internal authentication file
list: displays the contents of the internal
authentication file, this means the list of targets that
can be accessed with their user/password details
‐H host Platform Manager IP address or DNS name
‐u user MC user
‐p password MC user password
B.2.2. General Syntax

bsmcfg_auth_cmd.sh [‐h] [‐a action] [‐u user] [‐p password] ‐H host
B-2 Reference Guide

B.2.3. Examples
B.2.3.1. Add a Target

Syntax
bsmcfg_auth_cmd.sh ‐a add ‐u user ‐p password ‐H host
Command to add a platform Manager
$ bsmcfg_auth_cmd.sh -a add -u MWA -p mwapwd -H X.X.X.X
Output
---------------------------------------------------------------------------
Key entry successfully added
---------------------------------------------------------------------------
Command
$ bsmcfg_auth_cmd.sh -a add -u MWA2 -p mwa2pwd -H “*"
B.2.3.2. Extract the Encoded Password
Syntax
bsmcfg_auth_cmd.sh ‐a getE ‐u user ‐H host
Command to get the encoded password to access a platform Manager
$ bsmcfg_auth_cmd.sh -a getE -u MWA -H X.X.X.X
Output
---------------------------------------------------------------------------
cGFzcw==
---------------------------------------------------------------------------
Command
$ bsmcfg_auth_cmd.sh -a getE -u MWA2 -H “*"
Output
---------------------------------------------------------------------------
RfGFerv==
---------------------------------------------------------------------------
B.2.3.3. Extract the Password Needed to Access a Target

Syntax
bsmcfg_auth_cmd.sh ‐a getD ‐u user ‐H host
Command to get the password to access a platform Manager
$ bsmcfg_auth_cmd.sh -a getD -u MWA -H X.X.X.X
Output
---------------------------------------------------------------------------
mwapwd
---------------------------------------------------------------------------
Command
$ bsmcfg_auth_cmd.sh -a getD -u MWA2 -H “*"
Output
---------------------------------------------------------------------------
mwa2pwd
---------------------------------------------------------------------------
Appendix B. User/Password Internal Authentication File B-3

B.2.3.4. Delete a Target
Syntax
bsmcfg_auth_cmd.sh ‐a del ‐u user ‐H host
Command to delete a platform Manager
$ bsmcfg_auth_cmd.sh -a del -u MWA -H X.X.X.X
Output
---------------------------------------------------------------------------
Key entry successfully deleted
---------------------------------------------------------------------------
Command to delete a generic device
$ bsmcfg_auth_cmd.sh -a del -u MWA2 -H “*"
Output
---------------------------------------------------------------------------
Key entry successfully deleted
---------------------------------------------------------------------------
B.2.3.5. Display the Contents of the Internal Authentication File

Syntax
bsmcfg_auth_cmd.sh ‐a list
Command
$ bsmcfg_auth_cmd.sh -a list
Output
---------------------------------------------------------------------------
<?xml version="1.0"?>
<auth_entries>
<auth_entry keyname="HWMGR_mgr1" password="cHdkMQ%3D%3D" user="usr1" />
<auth_entry keyname="HWMGR_mgr2" password="d3h5" user="usr2" />
<auth_entry keyname="FTPSRV_srv1" password="cHdkMQ%3D%3D" user="usr1" />
<auth_entry keyname="DEV_ipaddr1" password="ZGV2cHdk" user="devuser" />
<auth_entry keyname="HWMGR_*" password="d3h6" user="MWA2" />
</auth_entries>
---------------------------------------------------------------------------
B-4 Reference Guide

Appendix C. Optional Equipment Management CLIs
C.1. bsmPDUpower
The bsmPDUpower command is used for monitoring and the administration of
remote controlled PDUs (Power Distribution Units). This includes obtaining the
total power consumption for all the outlets of the PDU (and also the warning
and critical consumption thresholds), poweron/poweroff and status of the PDU
outlets.
The command uses SNMP to get and set requests to the SNMP agent of the
PDU:
return code is -1.
Notes • Only PDUs from APC are supported. For APC metered rack PDUs, only
the getPowerConsumption action is available.
• Firmware version of APC PDUs must be equal to or later than v3.
C.1.1. Options
on/off: sets on or off one or all PDU outlets
status: obtains the status for one or all PDU outlets
getPowerConsumption: gets power consumption (in
Watts) for all PDU outlets
m model PDU model: apc
H host PDU IP address or DNS name
syslog
logged
are logged
are redirected
arglist Lists arguments specific to the action
Appendix C. Optional Equipment Management CLIs C-1

C.1.2. General Syntax
bsmPDUpower.sh [h] [l level] m model –H host [o outfile] –a action
arglist
C.1.3. Examples
C.1.3.1. Set On or Off One or All Outlets of a PDU
Syntax
bsmPDUpower.sh [h] [l level] m model –H host [o outfile] –a on/off
[p SNMP port] [S SNMPv] [[C community]|[u user –L seclevel
–A authPass –P authPro –X privPass –x privPro]] [c outlet] [T timeout]
Options
p port SNMP port (default value: 161)
S SNMPv SNMP version: 1 (default value), 2c, 3
C community SNMPv1 community (default value private for on and
off actions)
L seclevel SNMPv3 SecurityLevel (noAuthNoPriv | authNoPriv |
authPriv)
u user SNMPv3 user
A authPass SNMPv3 authentication passphrase (15 to 32 ASCII
characters)
P authPro SNMPv3 authentication protocol (default value MD5 )
X privPass SNMPv3 privacy passphrase (15 to 32 ASCII
characters, different than –authPass)
x privPro SNMPv3 privacy protocol (default value DES )
c outlet Number or name of one outlet for a PDU (default value
all: all outlets are switched on or off)
T timeout SNMP timeout (default value: 30 seconds)
Command to set all outlets off
$ bsmPDUpower.sh –H X.X.X.X –a off –m apc –S 3 –L authPriv –u $user –A $authpass –P md5 –X $privpass
–x des –c all
Output
---------------------------------------------------------------------------
Outlet1 power: Off(2)
---------------------------------------------------------------------------
Command to set outlet 5 on
$ bsmPDUpower.sh –H X.X.X.X –a on –m apc –S 3 –L authPriv –u $user –A $authpass –P md5 –X $privpass
–x des –c 5
C-2 Reference Guide

Output
---------------------------------------------------------------------------
Outlet5 power: On(1)
---------------------------------------------------------------------------
C.1.3.2. Get the Status for One or All Outlets of a PDU
Syntax
bsmPDUpower.sh [h] [l level] m model –H host [o outfile] –a status
[p SNMP port] [S SNMPv] [[C community]|[u user –L seclevel
–A authPass –P authPro –X privPass –x privPro]] [c outlet] [T timeout]
Options
C community SNMPv1 community (default value 'public' for status
action
authPriv)
u user SNMPv3 user
characters)
P authPro SNMPv3 authentication protocol (default value 'MD5' )
x privPro SNMPv3 privacy protocol (default value 'DES' )
c outlet Number or name of one outlet of PDU (default value
'all': all outlets are switched on or off)
Command to obtain the status for all outlets
$ bsmPDUpower.sh –H X.X.X.X –a status –m apc –S 3 –L authPriv –u $user –A $authpass –P md5 –X
$privpass –x des –c all
Output
---------------------------------------------------------------------------
Power Distribution Unit: X.X.X.X, MODEL: “AP7922”, Serial Nb: “ZA0904000484”,
Firm Rev: “v3.5.7”
Outlet5 power: On(1)
---------------------------------------------------------------------------
Command to obtain the status for outlet 4
$ bsmPDUpower.sh –H X.X.X.X –a status –m apc –S 1 –C public –c 4
Output
---------------------------------------------------------------------------
Power Distribution Unit: X.X.X.X, MODEL: “AP7922”, Serial Nb: “ZA0904000484”,
Firm Rev: “v3.5.7”
---------------------------------------------------------------------------
Appendix C. Optional Equipment Management CLIs C-3

C.1.3.3. Get the Power Consumption
Syntax
bsmPDUpower.sh [h] [l level] m model –H host [o outfile]
–a getPowerConsumption [p SNMP port] [S SNMPv] [[C community]|
[u user –L seclevel –A authPass –P authPro –X privPass –x privPro]]
[T timeout]
Options
C community SNMPv1 community (default value 'public' for
getPowerConsumption action
authPriv)
u user SNMPv3 user
characters)
P authPro SNMPv3 authentication protocol (default value 'MD5' )
x privPro SNMPv3 privacy protocol (default value 'DES' )
Command
$ bsmPDUpower.sh –H X.X.X.X –a getPowerConsumption –m apc
Output
---------------------------------------------------------------------------
Power OK: Reading 5 Watts|power=5;5520;7360;0
---------------------------------------------------------------------------
Or should be:
---------------------------------------------------------------------------
power=10;5000;7000;0
power consumption:10
high power level: 5000
critical power level: 7000
minimal consumption: 0
---------------------------------------------------------------------------
Output OK:
---------------------------------------------------------------------------
Power OK: 10|power=10;5000;7000;0
---------------------------------------------------------------------------
Output WARNING:
---------------------------------------------------------------------------
Power WARNING: High power level detected: 5500|power=5500;5000;7000;0
---------------------------------------------------------------------------
Output CRITICAL:
---------------------------------------------------------------------------
Power CRITICAL: Critical power level detected: 7500|power=7500;5000;7000;0
---------------------------------------------------------------------------
C-4 Reference Guide

Bull Cedoc
357 avenue Patton
BP 20845
49008 Angers Cedex 01
FRANCE

86A143FL10 Remote Hardware Management CLI Reference Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

86A143FL10 Remote Hardware Management CLI Reference Guide

Uploaded by

Copyright:

Available Formats

bullion

Copyright ©Bull SAS 2016

Trademarks and Acknowledgements

We acknowledge the right of proprietors of trademarks mentioned in this manual.

Chapter 1. Introducing the Hardware Management CLIs . . . . . . . . . . . . . . . . . . . . . . 1-1

Chapter 2. Commands for bullion S server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Chapter 3. Field Hardware Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Appendix A. Server ON / OFF Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Appendix B. User/Password Internal Authentication File . . . . . . . . . . . . . . . . . . . . . . . B-1

Appendix C. Optional Equipment Management CLIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Important ATTENTION: Please read carefully the safety instructions

Multilingual Safety Notices Guide, 86 X1 12FL

Important ATTENTION: Please read carefully the safety instructions

Multilingual Safety Notices Guide, 86 X1 12FL

Chapter 1. Introducing the Hardware Management CLIs 1-1

1.1.1. Remote Hardware Management

1-2 Reference Guide

Chapter 1. Introducing the Hardware Management CLIs 1-3

where the values for <arch>.rpm are:

1-4 Reference Guide

Figure 1-1. BSM HW CLI Installation Setup

Figure 1-2. BSM HW CLI Installation Destination

Chapter 1. Introducing the Hardware Management CLIs 1-5

Figure 1-3. BSM HW CLI Installation Setup Complete

Figure 1-4. BSM HW CLI Post installation

c. Launch the Cygwin bash environment:

1-6 Reference Guide

Figure 1-5. Launching BSM HW CLI on Windows

Chapter 1. Introducing the Hardware Management CLIs 1-7

2. Edit the bsmcli.cfg.custom.sh file as required.

1-8 Reference Guide

Chapter 2. Commands for bullion S server 2-1

Multilingual Safety Notices Guide, 86 X1 12FL

2-2 Reference Guide

Chapter 2. Commands for bullion S server 2-3

2.1.3.1. Exclude a XQPI Port

2.1.3.2. Exclude some RDIMMs

2-4 Reference Guide

2.1.3.4. Exclude Ultracapacity

Chapter 2. Commands for bullion S server 2-5

2.2.2. General Syntax

2-6 Reference Guide

2.2.3.1. Get BIOS Image Details

2.2.3.2. Get BIOS Memory Size Details

Chapter 2. Commands for bullion S server 2-7

2.3.2. General Syntax

2-8 Reference Guide

2.3.3.1. List the BIOS Log Files

2.3.3.2. Copy BIOS Log Files

This command returns no output.

This command returns no output.

2.3.3.3. Get BIOS Log File Size

Chapter 2. Commands for bullion S server 2-9

This command returns no output.

This command returns no output.

2-10 Reference Guide

Note Refer to the file BIOSXnn_SetupOptions.xlsx provided on the Resource

2.4.2. General Syntax

Chapter 2. Commands for bullion S server 2-11

2.4.3.1. Get all the BIOS Settings Values

2.4.3.2. Get the Required BIOS Settings Values

Input file format example:

2-12 Reference Guide

Input file format example: