Chapter 2. InfiniBand products for BladeCenter 21
– Unconnected
Six external autosensing 10/100/1000 Mbps RJ-45 Ethernet (copper) ports
802.3ad link aggregation
Support for jumbo frames
Support of IEEE 802.1q VLAN tagging
Support for up to 1150 Virtual NIC ports per module
Automatic port and module failover
TCP/UDP and IP header checksum offload and host checking
802.1p Priority Queuing/Scheduling
Switched internal I2C Interface to the management modules
Two internal 100 Mbps full-duplex Ethernet links to the management modules
Power-on diagnostics and status reporting
Support of simple network management protocol (SNMP) management information bases
(MIBs) and traps through the Ethernet management ports
Ethernet Bridge Module supports the following management methods:
CLI through telnet or SSH
Web-based access with QLogic’s Chassis Viewer
SNMP/MIB
For more information, refer to the following documentation:
QLogic InfiniBand Ethernet Bridge Module and Fibre Channel Bridge Module Installation
Guide - IBM BladeCenter H (Type 8852)
http://www.ibm.com/support/docview.wss?uid=psg1MIGR-5070108
InfiniBand Fibre Channel Bridge Module for IBM BladeCenter & InfiniBand Ethernet
Bridge Module for IBM BladeCenter - Support
http://support.qlogic.com/support/oem_detail_all.asp?oemid=377
2.5 QLogic InfiniBand Fibre Channel Bridge Module
The QLogic InfiniBand to Fibre Channel Bridge module, part number 39Y9211, can provide
Fibre Channel connectivity to InfiniBand clients within the BladeCenter H. It uses a concept of
Virtual HBAs to virtualize InfiniBand fabric to provide blade server’s access to the resources
resided in traditional SANs. Like the Ethernet Bridge Module, it can be installed currently in
switch bays 3 and 5 (use two for redundancy) and its use requires the installation of a Cisco
InfiniBand 4X switch module in bays 7 and 9 (use two for redundancy and 4X InfiniBand HCA
on each blade server that wants to make use of the bridge module.
The Fibre Channel Bridge Module offers six 1/2/4 Gbps external FC SFP ports to connect to
an upstream Fibre Channel network, and two 4x internal InfiniBand ports to connect to the 4x
switch modules in slot 7 and 9. See Figure 2-5. Management is through either a
browser-based GUI interface or a CLI-based interface, with management connectivity coming
Note: If the bridge module is installed in bay 4 or 6 there will not be an internal InfiniBand
connection because the 4X InfiniBand HCA does not have a third and fourth port routed to
bays 8 and 10. See 1.4, “High-speed I/O paths in BladeCenter H” on page 13.
Comments to this Manuals