13.2 Manage InfiniBand Network Using Subnet Manager
This section contains the following topics:
• Overview of Subnet Manager
• Subnet Manager Operation in Different Rack Configurations
• Monitor the Subnet Manager
• Control the Subnet Manager
13.2.1 Overview of Subnet Manager
The subnet manager (SM) manages all operational characteristics of the InfiniBand
network, such as the following:
• Discovering the network topology
• Assigning a local identifier (LID) to all ports connected to the network
• Calculating and programming switch forwarding tables
• Programming Partition Key (PKEY) tables at HCAs and switches
• Programming QoS tables (Service Level to Virtual Lane mapping tables, and
Virtual Lane arbitration tables)
• Monitoring changes in the fabric
The InfiniBand network typically has more than one SM, but only one SM is active at a
time. The active SM is Master SM, others are Standby SMs. If the master SM shuts
down or fails, a standby SM will automatically become the master SM.
Note:
In the Exalogic machine, the InfiniBand switches (both leaf and spine) are
automatically configured to separate the IP over InfiniBand (IPoIB) traffic and
the Ethernet over InfiniBand (EoIB) traffic.
13.2.2 Subnet Manager Operation in Different Rack Configurations
Table 13-1 provides information about the switches on which the subnet manager
should run in different rack configurations.
Table 13-1 Running the Subnet Manager in Different Rack Configurations
Rack Configuration SM Should Run
On...
SM Priority
Single Exalogic machine All leaf switches
All leaf switches: 5
Two half- or full-rack Exalogic machines Spine switches
Spine switch: 8
Two quarter-rack Exalogic machines All leaf switches
All leaf switches: 5
Manage InfiniBand Network Using Subnet Manager
13-2 Oracle Exalogic Elastic Cloud Machine Owner's Guide
To Next Page
Loading...
Need help?
General
