| Skip Navigation Links | |
| Exit Print View | |
|
Sun Datacenter InfiniBand Switch 36 HTML Document Collection for Firmware Version 2.1 |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Sun Datacenter InfiniBand Switch 36 HTML Document Collection for Firmware Version 2.1 |
USB Management Connector and Pins
InfiniBand QSFP Connector and Pins
Understanding InfiniBand Cabling
Preparing to Install the Switch
Suggested Tools for Installation
Antistatic Precautions for Installation
Verify Shipping Carton Contents
Assemble the Optical Fiber InfiniBand Cables
Install the Switch in the Rack
Verifying the InfiniBand Fabric
Network Management Troubleshooting Guidelines
Understanding Routing Through the Switch
Understanding Administrative Commands
Administering the I4 Switch Chip
Controlling the I4 Switch Chip
Administering the Subnet Manager
Display Subnet Manager Location History
Display the Secret M_Key Configuration
Verify the Subnet Manager Configuration Integrity
Display the Subnet Manager Log
Controlling the Subnet Manager
Set the Subnet Manager Priority
Enable Subnet Manager Controlled Handover
Set the Subnet Manager Readable Management Key
Clear the Subnet Manager Readable Management Key
Set the Subnet Manager Routing Algorithm
Configuring Secure Fabric Management
Prepare for Secret M_Key Functionality
Create the Secret M_Key Configuration
Add Secret M_Keys to the Configuration
Delete Secret M_Keys From the Configuration
Configure a Local Secret M_Key
Enable or Disable Secret M_Key Persistence
Enable or Disable Secret M_Key Functionality
Considering Situations In Regard to Secret M_Key
Add a New Subnet Manager to the Secret M_Key Fabric
Merge Subnets Into One Secret M_Key Fabric
Secret M_Key and Firmware Upgrade and Downgrade Guidelines
Administering the InfiniBand Fabric
Monitoring the InfiniBand Fabric
Controlling the InfiniBand Fabric
Understanding Oracle ILOM on the Switch
Understanding Oracle ILOM Targets
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
Identify Faults in the Oracle ILOM Event Log
Determining the Alarm State of a Component or System
Understanding Service Procedures
Antistatic Precautions for Service
Determine If a Power Supply Is Faulty
Inspecting the InfiniBand Cables
Determine If the Battery Is Faulty
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
The secret M-Key feature of the version 2.1 firmware adds an extra layer of security to the InfiniBand fabric through use of a hidden passphrase, or secret M_Key.
The secret M_Key enforces a policy that only a Subnet Manager authorized to manage the InfiniBand fabric is able to do so, and that write requests from unauthorized sources are rejected. Conveniently, information can be read from the InfiniBand devices without restriction, except for the secret M_Key itself.
In the process of initiating the secret M_Key functionality, you create the secret M_Key on the master Subnet Manager using the smsubnetprotection command and its subcommands in a configuration session. During the session, one or more secret M_Keys are added to a configuration list. There is a maximum of 10 secret M_Keys. Upon committing to the configuration, the list and active secret M_Key is automatically propagated to the standby Subnet Managers in the InfiniBand fabric. This action authorizes and enables the standby Subnet Managers to control the fabric in the event of a failover or handover. The master Subnet Manager also sets the value of the secret M_Key to the InfiniBand nodes of the subnet.
If a switch or gateway having a different secret M_Key is brought into the fabric, the fabrics current secret M_Key must be assigned manually.
Once implemented, the secret M_Key functionality is transparent to the user. Attempts to hijack the fabric by a rogue Subnet Manager are refused because the secret M_Key is missing, or there is a secret M_Key mismatch. This condition prevents the intruder from configuring the InfiniBand fabric.
There are prerequisites to implementing the secret M_Key functionality. You must:
Correctly define and distribute the smnodes list to all smnodes.
For redundancy and up-time, configure and enable IPoIB across the fabric.
Verify and propagate the fabric element configuration.
Configuring secret M_Key for the first time requires:
Setting the replication (and encryption) password
Enabling M_Key persistence
Enabling secret M_Key functionality
These requirements are implemented before configuring secret M_Key functionality so that the security of the fabric is maintained during the configuration.
|