Skip Navigation Links | |
Exit Print View | |
Sun Datacenter InfiniBand Switch 36 HTML Document Collection for Firmware Version 2.0 |
Network Management Connector and Pins
USB Management Connector and Pins
Preparing to Install the Switch
Suggested Tools for Installation
Antistatic Precautions for Installation
Verify Shipping Carton Contents
Install the Switch in the Rack
Verifying the InfiniBand Fabric
Understanding Routing Through the Switch
Understanding Administrative Commands
Administering the I4 Switch Chip
Controlling the I4 Switch Chip
Administering the Subnet Manager
Controlling the Subnet Manager
Administering the InfiniBand Fabric
Monitoring the InfiniBand Fabric
Controlling the InfiniBand Fabric
Configuring the Fabric Director Node List
Partitioning the InfiniBand Fabric
Understanding Oracle ILOM on the Switch
Understanding Oracle ILOM Targets
Installing the Oracle ILOM Firmware
Acquire the Oracle ILOM Firmware Version 1.1.3
Install the Oracle ILOM Firmware Version 1.1.3
Administering Oracle ILOM (CLI)
Accessing Oracle ILOM From the CLI
Switching Between the Oracle ILOM Shell and the Linux Shell
Monitoring Oracle ILOM Targets (CLI)
Controlling Oracle ILOM Targets (CLI)
Upgrading the Switch Firmware Through Oracle ILOM (CLI)
Administering Oracle ILOM (Web)
Access Oracle ILOM From the Web Interface
Monitoring Oracle ILOM Targets (Web)
Controlling Oracle ILOM Targets (Web)
Upgrade the Switch Firmware (Web)
Accessing the Rear Panel Diagram
Accessing Status Pane Information
Monitoring Parameters and Status
Administering Oracle ILOM (SNMP)
Monitoring Oracle ILOM Targets (SNMP)
Controlling Oracle ILOM Targets (SNMP)
Display the Sensor States (IPMI)
Display the Sensor Information (IPMI)
Display the System Event Log (IPMI)
Display FRU ID Information (IPMI)
Display Switch Status LED States (IPMI)
Disable the Locator LED (IPMI)
Understanding Oracle ILOM Commands
Understanding Service Procedures
Antistatic Precautions for Service
Remove the Switch From the Rack
Understanding Hardware Commands
Linux Shells for Hardware Commands
Understanding InfiniBand Commands
Linux Shells for InfiniBand Commands
Understanding the SUN-DCS-IB-MIB MIB OIDs
Understanding the SUN-FABRIC-MIB MIB OIDs
Understanding the SUN-HW-TRAP-MIB MIB OIDs
Understanding the SUN-ILOM-CONTROL-MIB MIB OIDs
Understanding the SUN-PLATFORM-MIB MIB OIDs
Checks firmware integrity.
fwverify
This hardware command checks if the firmware installed is corrupted or has been tampered with. The command first makes a comparison of the installed RPM packages to a predefined list of what RPM packages should be installed for the given firmware version. This list was generated at the time of the firmware image build. The fwverify command then performs a verification for each installed package using the rpm --verify command.
Should the command find a missing, corrupt, or additional package or file, the command will display the package or file name, and its location in the filesystem. The conditions of the error are displayed as an 8-character string of flags, SM5DLUGT, where:
S – File size differs.
M – Mode (including permissions and file type) differs.
5 – MD5 sum differs.
D – Device major/minor number mis-match.
L – readlink(2) path mis-match.
U – User ownership differs.
G – Group ownership differs.
T – mtime differs.
. – Flag was not set (no error).
Note - The fwverify command might indicate that files in the /config/fwutils directory have changed. The error can safely be ignored.
The fwverify command is available from the /SYS/Switch_Diag and /SYS/Fabric_Mgmt Linux shell targets of the Oracle ILOM CLI interface.
This example shows how to verify the firmware integrity with the fwverify command.
# fwverify Checking all present packages: ........................................................................... OK Checking if any packages are missing: ........................................................................... OK Verifying installed files: ....................................................................... FAILED * Package nm2-phs-2.0.5-1.i386: S.5....T /etc/init.d/dcs #
In this example, within the nm2-phs-2.0.5-1.i386 RPM package, the /etc/init.d/dcs file size differs, the MD5 sum differs, and the time differs
This example shows a successful verification.
# fwverify Checking all present packages: ........................................................................... OK Checking if any packages are missing: ........................................................................... OK Verifying installed files: ........................................................................... OK #