Slide 1 - Enter the eLearning
Slide notes
Welcome to the BullSequana Administration training.
Slide 2 - Administration
Slide notes
Each module has a BMC (Baseboard Management Controller) embedded on the motherboard.
The BMC is accessible from the PEB / PEBS administration port (port 0).
The BullSequana S platform administration can be done with Graphic User Interface (GUI) or Command Line Interface (CLI).
The Graphic User Interface (GUI) on the BullSequana S platform is called SHC (Server Hardware Console).
The system administration must be done from the Primary module of the partition.
The documentation “SHC Reference Guide” is available from support web.
Slide 3 - SHC – Server hardware console (GUI)
Slide notes
The SHC is accessible using a web browser.
The SHC is initialized at the installation of the platform using « psetup » software to configure the network and user / password.
The « psetup » tool is available from the ISO of the Technical State.
The default user / password is super / pass.
Slide 4 - SHC – Main page
Slide notes
The main page of the SHC is divided in 4 zones: The SHC Main Menu navigation tabs.
A contextual menu according to the selected tab.
The settings available for the options selected.
An information zone about the partition and the role of the module.
Slide 5 - SHC – console
Slide notes
A virtual console is available from SHC.
The console uses JAVA applet.
It is accessible in the “System Control” menu.
Slide 6 - SHC – console : Configuring Java console
Slide notes
Internet browsers don’t support Java anymore.
So, the SHC must be configured to use an external java.
To do, go to “Configuration Tab” then select “Remote Console Settings” menu.
Check the box to use a Java Web Start.
Slide 7 - SHC – console : Configuring Java console environment
Slide notes
To use the java console, the open source “OpenWebStart” software must be installed on the customer or field engineer laptop.
The complete procedure to configure “OpenWebStart” software is available in the documentation “Hardware Console”.
Take time to read the following resume of the steps to install and configure the “OpenWebStart” tool.
Slide 8 - SHC – console : Configuring Java console environment
Slide notes
After installation of OpenWebStart, a configuration of the software is needed.
The first step is to set OpenWebStart to allow server from JNLP files.
Slide 9 - SHC – console : Configuring Java console environment
Slide notes
Then the internet connection for openwebstart must be configured as needed.
Slide 10 - SHC – console : Configuring Java console environment
Slide notes
When the virtual console is launched, the file “rcgui.jnlp” is created by the BMC to start the virtual console.
This file must be executed by OpenWebStart to open the virtual console.
Windows must be configured to start JNLP files with OpenWebStart as follow.
Slide 11 - SHC – console
Slide notes
Run the “rcgui.jnlp” to start the virtual console.
Slide 12 - SHC – virtual drive - connect an ISO image
Slide notes
From the virtual console, a virtual drive can be mounted.
This allows to mount an ISO image for OS installation for example.
To mount the virtual drive, select “Virtual Media” menu on the virtual console.
Select Image File folder.
Browse and find the ISO image on your computer.
Then connect the ISO image.
Slide 13 - SHC – virtual drive
Slide notes
If a virtual drive is mounted, it can be seen and disconnected from the “Virtual Media” menu in the “System Control” tab.
Slide 14 - SHC – Monitoring
Slide notes
The “monitoring” menu allows to check the sensors status, get the SEL (System Event Logs) and Messages logs.
Only the modules of the partitions are showed in this menu.
The sensor status tab shows a warning if attention is required by the administrator.
In this example, the power sensors show a redundancy loss due to a loss of power on PS1.
Slide 15 - SHC – Monitoring - System Event Log
Slide notes
The monitoring tab.
The SHC can provide hardware logs and administration logs for the BullSequana S.
The SEL (System Event Logs) is the hardware logs of the motherboard.
It records voltage issues, temperature events, fan events, and events from BIOS.
See in this example the SEL show the memory RAS configuration done during the BIOS boot.
Slide 16 - SHC – Monitoring - Messages Log
Slide notes
The Messages log is generated by the BMC.
These are the administration logs of the BullSequana S platform.
These logs are very important for the issue identification.
They never have to be cleared.
Slide 17 - SHC – Configuration
Slide notes
The configuration tab.
This menu allows the settings of the BMC as the date and time, the platform name, the user settings, the partitioning configuration, etc.
The date and time is set for the BMC and not for the operating system.
It is important the date and time of the BMC is correctly set for logs review in case of issue.
For that an NTP server is strongly recommended and can be configured for the BMC in the date and time menu.
Slide 18 - SHC – Partitioning
Slide notes
Partitioning of the system.
The configuration TAB allows the partitioning of the system.
In this example of the partitioning of a BullSequana S400, the system is configured as a single partition with 2 modules.
The platform administrator can change the partitioning configuration and create 2 partitions (one module in each).
To do, first, the actual partition must be powered OFF.
Then the platform administrator can select the number of partitions and create the partitions.
The new partitions will be displayed at the bottom of the page.
Slide 19 - SHC – Partitioning
Slide notes
After the partitions are created, the available modules can be added to the partition with a drag and drop as follow.
The name of the partitions can be changed if needed.
Then apply to enable the new partitioning configuration.
Slide 20 - SHC – firmware version
Slide notes
The maintenance tab.
This tab gives access to the firmware versions, the firmware updates of the BullSequana S platform and the collect of the logs.
The “Firmware Version” menu, display the firmware versions of all components of the BullSequana S platform as the BIOS and the BMC.
All the firmwares interact with each other, so it is mandatory to always keep a supported configuration.
This is assumed by the TS (Technical State) which contains firmwares, and the firmwares release note.
Slide 21 - Thank you
Slide notes
Slide 22 - Instructions
Slide notes