BladeCenter networking

Hunter, S. W.; Strole, N. C.; Cosby, D.; Green, D. M.

doi:10.1147/rd.496.0905

Cited by 15 publications

(13 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The BladeCenter AMMs are connected to the SE via a redundant switched Ethernet network [9]. The SE runs a Dynamic Host Configuration Protocol daemon to provide IP addresses to the AMMs.…”

Section: Bladecenter Discoverymentioning

confidence: 99%

IBM zBX hardware management and operational controls

et al. 2012

View full text Add to dashboard Cite

The IBM zEnterprise A Unified Resource Manager support for the IBM zEnterprise BladeCenter A Extension (zBX) hardware management and operational controls was established as an extension of the z196 system. System z hardware control design principles of concurrency, security, and automatic configuration were mainstays for the extended and new support for the zBX hardware and controls. This paper describes the hardware integration approach and different aspects of management: change, problem, serviceability, configuration, operations, performance, and business. In addition, included in this paper are details of the zBX firmware, components within the zBX blades, and the automation interfaces used between the hardware management console, Support Element, and the zBX components.

show abstract

“…The BladeCenter AMMs are connected to the SE via a redundant switched Ethernet network [9]. The SE runs a Dynamic Host Configuration Protocol daemon to provide IP addresses to the AMMs.…”

Section: Bladecenter Discoverymentioning

confidence: 99%

IBM zBX hardware management and operational controls

et al. 2012

View full text Add to dashboard Cite

show abstract

“…It adds virtual LAN tags to each Ethernet segment and enables separation of multiple networks. An example for high-performance Infiniband VLANs is given in [11]. In wide-area networks, VLAN tags are often not preserved.…”

Section: Related Workmentioning

confidence: 99%

Towards automated provisioning of secure virtualized networks

Cabuk

Dalton

Ramasamy

et al. 2007

Proceedings of the 14th ACM Conference on Computer and Communications Security

View full text Add to dashboard Cite

We describe a secure network virtualization framework that helps realize the abstraction of Trusted Virtual Domains (TVDs), a security-enhanced variant of virtualized network zones. The framework allows groups of related virtual machines running on separate physical machines to be connected together as though there were on their own separate network fabric and, at the same time, helps enforce crossgroup security requirements such as isolation, confidentiality, security, and information flow control. The framework uses existing network virtualization technologies, such as Ethernet encapsulation, VLAN tagging, and VPNs, and combines and orchestrates them appropriately to implement TVDs. Our framework aims at automating the instantiation and deployment of the appropriate security mechanism and network virtualization technologies based on an input security model that specifies the required level of isolation and permitted network flows. We have implemented a prototype of the framework based on the Xen hypervisor. Experimental evaluation of the prototype shows that the performance of our virtual networking extensions is comparable to that of the standard Xen configuration.

show abstract

“…These cards provide redundant ports from each processor blade to switch module positions 3 and 4. Once a specific I/O expansion adapter is installed in one processor blade, all other processor blades in a given chassis must also use this card or no card at all [10].…”

Section: Figurementioning

confidence: 99%

BladeCenter packaging, power, and cooling

Crippen¹,

Alo²,

Champion³

et al. 2005

IBM J. Res. & Dev.

View full text Add to dashboard Cite

This paper addresses the packaging, power, and cooling of the IBM eServere BladeCentert compact server infrastructure consisting of 14 servers in a 7U (1U ¼ 44.45 mm) vertical space for installation in an industry-standard rack. A typical rack is 42U tall. Therefore, six BladeCenter systems will fit in a rack, for a total of 84 servers. The density of a BladeCenter system (servers/ U) is double that of previous 1U rack-optimized servers. To build such a dense server system required overcoming a multitude of challenges in packaging, power, and cooling design. Our approach to these challenges is described, but in the broader context of not only increasing the density, but setting a new server standard for a highly available redundant infrastructure with integrated systems management and network switching that uses less power and is simple to maintain on site or remotely, even by nonspecialized personnel. Server processors, memory, storage, and input/output devices were combined in a single compact server unit called a processor blade, while the support infrastructure, such as systems management, network connectivity, optical media, power, and cooling, was consolidated in a single structure and shared among many servers. The result is a package architecture that lends itself well to standardization. Custom server blades and input/output devices may be designed in accordance with BladeCenter base specifications and be effectively integrated into the blade server system.

show abstract

BladeCenter networking

Cited by 15 publications

References 25 publications

IBM zBX hardware management and operational controls

IBM zBX hardware management and operational controls

Towards automated provisioning of secure virtualized networks

BladeCenter packaging, power, and cooling

Contact Info

Product

Resources

About