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
Controlling the Subnet Manager
Configuring Secure Fabric Management
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
Manages the secret M_Key.
smsubnetprotection subcommand [-h]
This hardware command has subcommands that determine its functionality. This table describes the subcommands and provides their syntax.
|
where:
m_key is the management key (16 hexadecimal digits).
password is encryption string for M_Key replication (8 alphanumeric characters).
This hardware command manages the secret M_Key and its implementation. The secret M_Key is a passphrase used by trusted Subnet Managers to securely perform activities (enabling ports, setting parameters, and so on) on the I4 switch chips of the InfiniBand fabric. The secret M_Key is an encrypted M_Key that is implemented at a lower level in fabric management than the readable M_Key. Use the smsubnetprotection command and its subcommands to create and manage the list of secret M_Keys.
When configuring a list of secret M_Keys, you initiate the configuration session on the master Subnet Manager with the smsubnetprotection start command. During the session, you add or delete secret M_Keys to the configuration, set the current secret M_Key, and list the M_Keys configured.
Note - There is a maximum of 10 secret M_Keys for the configuration.
To end the session, you must use the smsubnetprotection commit command to make the configuration active. Once committed, the configuration is automatically distributed to all Subnet Managers in the InfiniBand fabric.
Note - You cannot both add and delete secret M_Keys within a single configuration session. You must perform these actions in separate configuration sessions.
Should a local secret M_Key be created for an I4 switch chip without a corresponding Subnet Manager, that secret M_Key is only recognized by that I4 switch chip, and is unrecognized by the other I4 switch chips in the InfiniBand fabric.
Because of the complexity of the secret M_Key functionality, this table describes the impact of certain scenarios and actions you can take.
|
This table describes each of the columns of the output of the smsubnetprotection command.
|
The smsubnetprotection command is available from the /SYS/Fabric_Mgmt Linux shell target of the Oracle ILOM CLI interface.
This table describes the options to the smsubnetprotection command and their purposes.
|
This example shows how to display the active secret M_Keys with the smsubnetprotection command.
FabMan@switch_name->smsubnetprotection list active # File_format_version_number 1 # Sun DCS IB mkey config file # This file is generated, do not edit # secretmkey=enabled # nodeid=mnm # time=15 Dec 03:54:46 # checksum=378d9b09744e1d8b8ba6ae868c99d0c9 #! commit_number : 3 Mkey Untrusted Mkey Smkey Attribute ------------------ ------------------ ------------------ --------- 0x00abcdefabcdef01 0x1aa45124fee612ae 0x15fc26aea300f831 0x00abcdefabcdef02 0x4ccd8230de6cd348 0x3fc7e6ad701a8a2a 0x00abcdefabcdef03 0x9baa1debcc74de5e 0x1b253003600d137b C FabMan@switch_name->
Switch Administration, configuring secure fabric management