Managing the Server

Configuring the Server Boot Order


Note

Do not change the boot order while the host is performing BIOS power-on self test (POST).

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope bios

Enters BIOS command mode.

Step 2

Server /bios # set boot-order device1, device2, device3....

Specifies the boot device options and order.

Note

 

The options are not case sensitive.

You can select one or more of the following:

  • uefimap

  • uefios

  • uefipxeTE0/TE1/TE3/TE4

  • uefipxeGE2

Step 3

Server /bios # commit

Commits the transaction to the system configuration.

Step 4

(Optional) Server /bios # show detail

Displays the server boot order.

The next BIOS boot uses the new boot order.

Example

This example sets the boot order and commits the transaction:

server /bios # set boot-order uefimap,uefios
To manage boot-order:
- Reboot server to have your boot-order settings take place
- Do not disable boot options via BIOS screens
- If a specified device type is not seen by the BIOS, it will be removed
from the boot order configured on the BMC
- Your boot order sequence will be applied subject to the previous rule.
The configured list will be appended by the additional device types
seen by the BIOS
- Legacy Boot Order configuration will disable all the active Boot Devices which will
hide them from BIOS

server /bios *# commit
Changes to BIOS set-up parameters will require a reboot.
Do you want to reboot the system?[y|N]y
A system reboot has been initiated.

server /bios # show detail
BIOS:
BIOS Version: UCSEDM6_1.08
BIOS Flash: 1
Backup BIOS Version: UCSEDM6_1.08
Backup BIOS Flash: 0
BIOS Post Complete: 0
Boot Order: UEFIMAP,UEFIOS
FW Update Status: Done, OK
Password: ******
server /bios #

Resetting the Server

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # power hard-reset

After a prompt to confirm, resets the server.

Note

 

Power cycling the server is the same as powering off and then powering on the x86 server.

Note

 

Powerhard-reset is the same as pressing the physical reset button on the server.

Example

This example resets the server: 

Server# scope chassis
Server /chassis # power hard-reset
This operation will change the server's power state. 
Continue?[y|N]y

Shutting Down the Server

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # power shutdown

After the prompt to confirm, shuts down the server.

Example

This example shuts down the server: 

Server# scope chassis
Server /chassis # power shutdown

This operation will change the server's power state. 
Do you want to continue?[y|N]y

Locking Cisco IOS CLI Configuration Changes

Use this procedure to prevent configuration changes from being made using the Cisco IOS CLI.

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # show detail

(Optional) Displays server properties, which allows you to determine the current status of the IOS lockout (whether it is locked or unlocked).

Step 3

Server /chassis # set ios-lockout locked

Prevents configuration changes from being made using the Cisco IOS CLI.

Step 4

Server /chassis* # commit

Commits the changes.

Step 5

Server /chassis # show detail

(Optional) Displays server properties, which allows you to determine the current status of the IOS lockout (whether it is locked or unlocked).

Example

This example prevents configuration changes from being made using the Cisco IOS CLI:

Server /chassis # show detail
Chassis:
Power: off
    IOS Lockout: unlocked
    Power Button: unlocked
    Reset Button: unlocked
    Serial Number: FOC26285Q4B
    Product Name: UCS E1100D M6
    PID: UCS-E1100D-M6
    UUID: 1CD1E026-089C-0000-E822-D9826168E8F8
    Description:
    Asset Tag: Unknown
    FPGA Version: 3.4.2
    Uptime: 22 hours, 54 minutes
    SBFPGA Version: 1.0.2
    MCU Version: 240.10
    AIKIDO Version: 2711-270
    Last Reboot Reason: Flash Reset
Server /chassis # set ios-lockout locked
Server /chassis *# commit
Server /chassis # show detail
Chassis:
    Power: off
    IOS Lockout: locked
    Power Button: unlocked
    Reset Button: unlocked
    Serial Number: FOC26285Q4B
    Product Name: UCS E1100D M6
    PID : UCS-E1100D-M6
    UUID: 1CD1E026-089C-0000-E822-D9826168E8F8
    Description:
    Asset Tag: Unknown
    FPGA Version: 3.4.2
    Uptime: 22 hours, 54 minutes
    SBFPGA Version: 1.0.2
    MCU Version: 240.10
    AIKIDO Version: 2711-270
    Last Reboot Reason: Flash Reset

Unlocking Cisco IOS CLI Configuration Changes

Use this procedure to allow configuration changes to be made using the Cisco IOS CLI.

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # show detail

(Optional) Displays server properties, which allows you to determine the current status of the IOS lockout (whether it is locked or unlocked).

Step 3

Server /chassis # set ios-lockout unlocked

Allows configuration changes to be made using the Cisco IOS CLI.

Step 4

Server /chassis* # commit

Commits the changes.

Step 5

Server /chassis # show detail

(Optional) Displays server properties, which allows you to determine the current status of the IOS lockout (whether it is locked or unlocked).

Example

This example allows configuration changes to be made using the Cisco IOS CLI:

Server /chassis # show detail
Chassis:
    Power: off
    IOS Lockout: locked
    Power Button: unlocked
    Reset Button: unlocked
    Serial Number: FOC26285Q4B
    Product Name: UCS E1100D M6
    PID : UCS-E1100D-M6
    UUID: 1CD1E026-089C-0000-E822-D9826168E8F8
    Description:
    Asset Tag: Unknown
    FPGA Version: 3.4.2
    Uptime: 22 hours, 54 minutes
    SBFPGA Version: 1.0.2
    MCU Version: 240.10
    AIKIDO Version: 2711-270
    Last Reboot Reason: Flash Reset 
Server /chassis # set ios-lockout unlocked
Server /chassis *# commit
Server /chassis # show detail
Chassis:
    Power: off
    IOS Lockout: unlocked
    Power Button: unlocked
    Reset Button: unlocked
    Serial Number: FOC26285Q4B
    Product Name: UCS E1100D M6
    PID : UCS-E1100D-M6
    UUID: 1CD1E026-089C-0000-E822-D9826168E8F8
    Description:
    Asset Tag: Unknown
    FPGA Version: 3.4.2
    Uptime: 22 hours, 54 minutes
    SBFPGA Version: 1.0.2
    MCU Version: 240.10
    AIKIDO Version: 2711-270
    Last Reboot Reason: Flash Reset 
Server /chassis #

Managing Server Power

Powering On the Server


Note

If the server was powered off other than through the CIMC, the server will not become active immediately when powered on. In this case, the server will enter standby mode until the CIMC completes initialization.

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # power on

After the prompt to confirm, turns on the server power.

Example

This example turns on the server:

Server /chassis # power on
This operation will change the server's power state.
Do you want to continue?[y|N]y
Server /chassis # show
Power   Serial Number    Product Name      PID 		 UUID
----- --------------- ----------------- -----------------  ---------------------------
on      FOC26071VZY      UCS E1100D M6     UCS-E1100D-M6    1CD1E026-0311-0000- 0F12-FC9ABB95AA0A

Server /chassis #

Powering Off the Server

Before you begin

You must log in with user or admin privileges to perform this task

Procedure

  Command or Action Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # power off

Turns off the server.

Example

This example turns off the server: 

Server# scope chassis
Server /chassis # power off
This operation will change the server's power state.
Do you want to continue?[y|N]y
Server /chassis # show
Power  Serial Number  Product Name    PID 		UUID
----- ------------- ---------------- ------------- --------------------------
off   FOC26071VZY     UCS E1100D M6   UCS-E1100D-M6  1CD1E026-0311-0000-0F12-FC9ABB95AA0A

Server /chassis #

Power Cycling the Server

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # power cycle

After the prompt to confirm, power cycles the server.

Note

 

  • Power cycling the server is the same as powering off and then powering on the x86 server.

  • Power hard-reset is the same as pressing the physical reset button on the server.

Example

This example power cycles the server: 

Server# scope chassis
Server /chassis # power cycle

This operation will change the server's power state. 
Continue?[y|N]y

Configuring the Power Restore Policy

The power restore policy determines how power is restored to the server after a chassis power loss.

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope cimc

Enters CIMC command mode.

Step 2

Server /cimc #scope power-restore-policy

Enters the power restore policy command mode.

Step 3

Server /cimc/power-restore-policy # set policy {power-off | power-on | restore-last-state}

Specifies the action to be taken when chassis power is restored. Select one of the following:

  • power-off —Server power will remain off until manually turned on.

  • power-on —Server power will be turned on when chassis power is restored.

  • restore-last-state —Restores the server to the same power state (off or on) that it was in when the power was lost. This is the default action.

Step 4

Server /cimc/power-restore-policy# commit

Commits the transaction to the system configuration.

Example

This example sets the power restore policy to power-on and commits the transaction: 

Server# scope CIMC
Server /CIMC # scope power-restore-policy
Server /CIMC/power-restore-policy # set policy power-on
Server /CIMC/power-restore-policy *# commit
Server /CIMC/power-restore-policy #  show detail
Power Restore Policy:
    Power Restore Policy: power-on
   
Server /CIMC/power-restore-policy #

Locking the Server's Front Panel Power Button

Use this procedure to disable the physical power button, which is located on the front panel of the physical server. Once the power button is disabled, you cannot use the front panel power button to turn the server power on or off.

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # show detail

(Optional) Displays server properties, which allows you to determine the current status of the power button (whether it is locked or unlocked).

Step 3

Server /chassis # set power-button locked

Disables the power button. You cannot use the front panel power button to turn the server power on or off.

Step 4

Server /chassis* # commit

Commits the changes.

Step 5

Server /chassis # show detail

(Optional) Displays server properties, which allows you to determine the current status of the power button (whether it is locked or unlocked).

Example

This example disables the server's physical power button, which is located on the front panel of the physical server: 

Server# scope chassis
Server /chassis # show detail
Chassis:
    Power: off
    IOS Lockout: unlocked
    Power Button: unlocked
    Reset Button: unlocked
    Serial Number: FOC26285PBW
    Product Name: UCS E1100D M6
    PID : UCS-E1100D-M6
    UUID: 1CD1E026-05DC-0000-88E4-3E11AF0AA302
    Description:
    Asset Tag: Unknown
    FPGA Version: 3.4.2
    Uptime: 4 hours, 22 minutes
    SBFPGA Version: 1.0.2
    MCU Version: 240.9
    AIKIDO Version: 271e-270
    Last Reboot Reason: Flash Reset
Server /chassis # set power-button locked
Server /chassis *# commit
Server /chassis # show detail
Chassis:
    Power: off
    IOS Lockout: unlocked
    Power Button: locked
    Reset Button: unlocked
    Serial Number: FOC26285PBW
    Product Name: UCS E1100D M6
    PID : UCS-E1100D-M6
    UUID: 1CD1E026-05DC-0000-88E4-3E11AF0AA302
    Description:
    Asset Tag: Unknown
    FPGA Version: 3.4.2
    Uptime: 4 hours, 22 minutes
    SBFPGA Version: 1.0.2
    MCU Version: 240.9
    AIKIDO Version: 271e-270
    Last Reboot Reason: Flash Reset
Server /chassis #

Unlocking the Server's Front Panel Power Button

Use this procedure to enable the physical power button, which is located on the front panel of the physical server. Once the power button is enabled, you can use the front panel power button to turn the server power on or off.

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope chassis

Enters chassis command mode.

Step 2

Server /chassis # show detail

(Optional) Displays server properties, which allows you to determine the current status of the power button (whether it is locked or unlocked).

Step 3

Server /chassis # set power-button unlocked

Enables the power button. You can use the front panel power button to turn the server power on or off.

Step 4

Server /chassis* # commit

Commits the changes.

Step 5

Server /chassis # show detail

(Optional) Displays server properties, which allows you to determine the current status of the power button (whether it is locked or unlocked).

Example

This example enable the server's physical power button, which is located on the front panel of the physical server: 

server /chassis # set power-button unlocked
server /chassis *# commit
server /chassis # show detail
Chassis:
    Power: off
    IOS Lockout: unlocked
    Power Button: unlocked
    Reset Button: unlocked
    Serial Number: FOC26285PBW
    Product Name: UCS E1100D M6
    PID : UCS-E1100D-M6
    UUID: 1CD1E026-05DC-0000-88E4-3E11AF0AA302
    Description:
    Asset Tag: Unknown
    FPGA Version: 3.4.2
    Uptime: 4 hours, 22 minutes
    SBFPGA Version: 1.0.2
    MCU Version: 240.9
    AIKIDO Version: 271e-270
    Last Reboot Reason: Flash Reset
server /chassis #

Configure the Boot Order

Configure the Server Boot Order Using UEFI Map and UEFIOS


Note

Do not change the boot order while the host is performing BIOS power-on self-test (POST).

Before you begin

You must log in with user or admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server# scope bios

Enters BIOS command mode.

Step 2

Server /bios # set boot-order {uefimap, uefios, uefipxeTE0, uefipxeTE1, uefipxeTE3, uefipxeTE4, uefipxeGE2}

Server/bios # set boot-order uefimap,uefios

Specifies the boot device options and order.

Note

 

The options are not case sensitive.
You can select one or more of the following:

  • uefimap—UEFI virtual-map boot option

  • uefios—UEFI Operating System

  • uefipxe—PXE boot

    • TE0

    • TE1

    • TE3

    • TE4

    • GE2

Step 3

Server /bios # commit

Commits the transaction to the system configuration.

Step 4

(Optional) Server /bios # show detail

Displays the server boot order.

The new boot order is used on the next BIOS boot.

Example

This example sets the boot order and commits the transaction:

server /bios # set boot-order uefimap,uefios
To manage boot-order:
- Reboot server to have your boot-order settings take place
- Do not disable boot options via BIOS screens
- If a specified device type is not seen by the BIOS, it will be removed
from the boot order configured on the BMC
- Your boot order sequence will be applied subject to the previous rule.
The configured list will be appended by the additional device types
seen by the BIOS
- Legacy Boot Order configuration will disable all the active Boot Devices which will
hide them from BIOS

server /bios *# commit
Changes to BIOS set-up parameters will require a reboot.
Do you want to reboot the system?[y|N]y
A system reboot has been initiated.

server /bios # show detail
BIOS:
BIOS Version: UCSEDM6_1.08
BIOS Flash: 1
Backup BIOS Version: UCSEDM6_1.08
Backup BIOS Flash: 0
BIOS Post Complete: 0
Boot Order: UEFIMAP,UEFIOS
FW Update Status: Done, OK
Password: ******
server /bios #

Note

When you enable UEFI secure boot, only the UEFI options—uefimap, and uefios are available. Additionally,configure the UEFI secure boot, this reduces their average boot time by approximately 45-50 seconds.

Configuring BIOS Settings

Viewing BIOS Status

Procedure

  Command or Action Purpose

Step 1

Server # scope bios

Enters BIOS command mode.

Step 2

Server /bios # show detail

Displays details of the BIOS status.

The BIOS status information contains the following fields:

Name Description
BIOS Version The version string of the running BIOS.
Boot Order The order of bootable target types that the server will attempt to use.
FW Update/Recovery Status The status of any pending firmware update or recovery action.
FW Update/Recovery Progress The percentage of completion of the most recent firmware update or recovery action.

Example

This example displays the BIOS status: 

SERVER /bios # show detail
BIOS:
    BIOS Version: UCSEDM6_1.08
    BIOS Flash: 1
    Backup BIOS Version: UCSEDM6_1.08
    Backup BIOS Flash: 0
    BIOS Post Complete: 0
    Boot Order: (none)
    FW Update Status: Done, OK
    Password: ******

Configuring Server Management BIOS Settings

Before you begin

You must log in with admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server # scope bios

Enters BIOS command mode.

Step 2

Server /bios # scope server-management

Enters the server management BIOS settings command mode.

Step 3

Configure the BIOS settings.

For the CLI commands, descriptions and information about the options for each BIOS setting, see section Server Management BIOS Settings.

Step 4

Server /bios/server-management # commit

Commits the transaction to the system configuration.

Changes are applied on the next server reboot. If server power is on, you are prompted to choose whether to reboot now.

Example

This example shows how to set the BAUD rate to 9.6k :

SERVER /bios #
SERVER /bios # scope server-management
SERVER /bios/server-management # set BaudRate
<VALUE> 115.2k* | 19.2k | 38.4k | 57.6k | 9.6k
SERVER /bios/server-management # set BaudRate 9.6k
SERVER /bios/server-management *# commit
Your changes will be reflected in BIOS on next boot.
SERVER /bios/server-management #

Clearing the BIOS CMOS

On rare occasions, troubleshooting a server may require you to clear the server's BIOS CMOS memory. This procedure is not part of the normal maintenance of a server.

Procedure

  Command or Action Purpose

Step 1

Server# scope bios

Enters BIOS command mode.

Step 2

Server /bios # clear-cmos

After a prompt to confirm, clears the CMOS memory.

Example

This example clears the BIOS CMOS memory: 

Server# scope bios
Server /bios # clear-cmos

This operation will clear the BIOS CMOS.
Note: Server should be in powered off state to clear CMOS. 
Continue?[y|N] y

Setting the BIOS Password

Procedure

Command or Action Purpose

Server/bios# set password

Sets the BIOS password.

Example

This example sets the BIOS password:

Server/bios# set password
Warning:

Strong Password Policy is enabled!


For CIMC protection your password must meet the following requirements:
The password must have a minimum of 8 and a maximum of 20 characters. The password must not contain the User's Name.
The password must contain characters from three of the following four categories.
English uppercase characters (A through Z) English lowercase characters (a through z) Base 10 digits (0 through 9)
Non-alphabetic characters (!, @, #, $, %, ^, &, *, -, _, +, =)

Clearing the BIOS Password

Procedure

  Command or Action Purpose

Step 1

Server# scope bios

Enters BIOS command mode.

Step 2

Server /bios # clear-bios-password

Clears the BIOS password. You must reboot the server for the clear password operation to take effect. You are prompted to create a new password when the server reboots.

Example

This example clears the BIOS password:

Server# scope bios
Server /bios # clear-bios-password

This operation will clear the BIOS Password.
Note: Server should be rebooted to clear BIOS password. 
Continue?[y|N]y

Restoring BIOS Defaults

Before you begin

You must log in as a user with admin privileges to perform this task.

Procedure

  Command or Action Purpose

Step 1

Server # scope bios

Enters BIOS command mode.

Step 2

Server /bios # bios-setup-default

Restores BIOS default settings. This command initiates a reboot.

Example

This example restores BIOS default settings: 

Server# scope bios
Server /bios # bios-setup-default

This operation will reset the BIOS set-up tokens to factory defaults. All your configuration will be lost.
Changes to BIOS set-up parameters will initiate a reboot. 
Continue?[y|N]y

Server BIOS Settings

The tables in the following sections list the server BIOS settings that you can view and configure.


Note

We recommend that you verify the support for BIOS settings in your server. Depending on your installed hardware, some settings may not be supported.

Advanced: Processor BIOS Settings

Name

Description

Package C State Limit

The amount of power available to the server components when they are idle. This can be one of the following:

  • The server provides all server components with full power at all times. This option maintains the highest level of performance and requires the greatest amount of power.

  • System level coordination is in progress resulting in high power consumption. There might be performance issues until the coordination is complete.

  • When the CPU is idle, the system reduces the power consumption further than with the C3 option. This option saves more power than C0 or C2, but there might be performance issues until the server returns to full power.

  • When the CPU is idle, the server makes a minimal amount of power available to the components. This option saves the maximum amount of power but it also requires the longest time for the server to return to high performance mode.

  • The server may enter any available C state.

    Note

     

    This option is used only if CPU C State is enabled.

Advanced: USB BIOS Settings

Name

Description

USB Port 0

Status of the USB port 0 (KVM connector). This can be one of the following:

  • Disabled—USB port 0 is disabled.

  • Enabled—USB port 0 is enabled.

USB Port 1

Status of the USB port 1 (physical port). This can be one of the following:

  • Disabled—USB port 1 is disabled.

  • Enabled—USB port 1 is enabled.

Server Management BIOS Settings

Name

Description

FRB2 Enable

Whether the FRB2 timer is used by CIMC to recover the system if it hangs during POST. This can be one of the following:

  • Disabled—The FRB2 timer is not used.

  • Enabled—The FRB2 timer is started during POST and used to recover the system if necessary.

Console Redirection

Allows a serial port to be used for console redirection during POST and BIOS booting. After the BIOS has booted and the operating system is responsible for the server, console redirection is irrelevant and has no effect. This can be one of the following:

  • Disabled—No console redirection occurs during POST.

  • Enabled —Enables serial port A for console redirection during POST. Note that Serial Port A option also requires that you enabled Serial Port A in the Advanced menu.

    Note

     

    If you enable this option, you also disable the display of the Quiet Boot logo screen during POST.

Flow Control

Whether a handshake protocol is used for flow control. Request to Send/Clear to Send (RTS/CTS) helps to reduce frame collisions that can be introduced by a hidden terminal problem. This can be one of the following:

  • None—No flow control is used.

  • RTS-CTS—RTS/CTS is used for flow control.

Note

 

This setting must match the setting on the remote terminal application.

Baud Rate

What BAUD rate is used for the serial port transmission speed. If you disable Console Redirection, this option is not available. This can be one of the following:

  • 9.6k—A 9600 BAUD rate is used.

  • 19.2k—A 19200 BAUD rate is used.

  • 38.4k—A 38400 BAUD rate is used.

  • 57.6k—A 57600 BAUD rate is used.

  • 115.2k—A 115200 BAUD rate is used.

Note

 

This setting must match the setting on the remote terminal application.

Terminal Type

What type of character formatting is used for console redirection. This can be one of the following:

  • PC-ANSI—The PC-ANSI terminal font is used.

  • VT100—A supported VT100 video terminal and its character set are used.

  • VT100-PLUS—A supported VT100-plus video terminal and its character set are used.

  • VT-UTF8—A video terminal with the UTF-8 character set is used.

Note

 

This setting must match the setting on the remote terminal application.

OS Boot Watchdog Timer

Whether the BIOS programs the watchdog timer with a specified timeout value. If the operating system does not complete booting before the timer expires, the CIMC resets the system and an error is logged. This can be one of the following:

  • Disabled—The watchdog timer is not used to track how long the server takes to boot.

  • Enabled—The watchdog timer tracks how long the server takes to boot. If the server does not boot within the length of time specified

OS Boot Watchdog Timer Policy

The action the system takes when the watchdog timer expires. This can be one of the following:

  • Do Nothing—The state of the server power does not change when the watchdog timer expires during OS boot.

  • Power Down—The server is powered off if the watchdog timer expires during OS boot.

  • Reset—The server is reset if the watchdog timer expires during OS boot.

Note

 

This option is only applicable if you enable the OS Boot Watchdog Timer.

The following example shows the BIOS server management settings:

server /bios/server-management # set

BaudRate 				Baud rate
BootOrderRules 			 Boot Order Rules
cli 				     CLI options
ConsoleRedir 			   Console redirection
FlowCtrl 				Flow Control
FRB-2 				   FRB 2 Timer
OSBootWatchdogTimer 		   OS Watchdog Timer
OSBootWatchdogTimerPolicy 	    OS Watchdog Timer Policy
OSBootWatchdogTimerTimeout 	   OS Watchdog Timer Timeout
TerminalType 			   Terminal type

server /bios/server-management # show detail

Set-up parameters:
Baud rate: 115.2k
Boot Order Rules: CIMC-config
Console redirection: Disabled
FRB 2 Timer: Enabled
Flow Control: None
OS Watchdog Timer: Disabled
OS Watchdog Timer Policy: Reset
OS Watchdog Timer Timeout: 10 minutes
Terminal type: PC-ANSI