HP ProLiant DL288 ISS Technology Focus, Volume 10, Number 2

HP ProLiant DL288 Manual

HP ProLiant DL288 manual content summary:

  • HP ProLiant DL288 | ISS Technology Focus, Volume 10, Number 2 - Page 1
    by HP with contributions and support from a consortium of companies that include IBM, Broadcom, QLogic, Emulex, and others. You can find detailed specifications for EVB at http://www.ieee802.org/1/pages/802.1bg.html. The following sections explain the need to standardize the operation and management
  • HP ProLiant DL288 | ISS Technology Focus, Volume 10, Number 2 - Page 2
    to standardize the management of these virtual server administrators or network administrators should control these virtual network systems What Port Aggregator (VEPA) Virtual Station Interface (VSI) Discovery Support for multiple channels on one physical link Virtual Ethernet Port Aggregator HP
  • HP ProLiant DL288 | ISS Technology Focus, Volume 10, Number 2 - Page 3
    support the feature. One example is the HP A5820X switch series services. Offloading network services reduces the burden on CPUs and improves system performance. Virtual Station Interface discovery VSI is an internal point-to-point Ethernet LAN that connects a bridge port within the server. The IEEE
  • HP ProLiant DL288 | ISS Technology Focus, Volume 10, Number 2 - Page 4
    using SSDs with a Smart Array controller, always use a cache module, which is called an array accelerator in the HP Array Configuration Utility (ACU). Current generation Smart Array controllers support 256 MiB, 512 MiB, and 1 GiB array accelerators. Use the 512 MiB or 1 GiB array accelerator because
  • HP ProLiant DL288 | ISS Technology Focus, Volume 10, Number 2 - Page 5
    data acquisition system OEM and HP include the first ProLiant DL360 server and the BladeSystem c-Class infrastructure architecture. Gene Freeman, Kevin's manager problem is slain." Name: Kevin Leigh Title: Distinguished Technologist, ISS, Blade Server and Infrastructure Architect Lead Years at HP
  • HP ProLiant DL288 | ISS Technology Focus, Volume 10, Number 2 - Page 6
    Microsoft® Windows® Small Business Server 2011 on HP ProLiant servers HP Virtual Connect technology for the HP BladeSystem c-Class AMD Opteron™ and Intel® Xeon® x86 processors in industry-standard servers URL http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00 231623/c00231623.pdf
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6

ISS Technology Focus, Volume 10, Number 2
Facts about the IEEE 802.1Qbg proposal
...............................................................................................
1
Optimizing SSD performance with HP Smart Array controllers
...................................................................
4
Meet the Expert
Kevin Leigh
................................................................................................................
5
Recently published Industry-Standard Server technology papers
.................................................................
6
Contact us
...........................................................................................................................................
6
Facts about the IEEE 802.1Qbg proposal
The Edge Virtual Bridging (EVB) standard is at the heart of industry efforts to standardize virtualization at the server-network
edge where the server domain ends and the external network domain begins. The proposed EVB standard, identified by the
IEEE802.1 Work Group as IEEE802.1Qbg, is an initiative led by HP with contributions and support from a consortium of
companies that include IBM, Broadcom, QLogic, Emulex, and others. You can find detailed specifications for EVB at
. The following sections explain the need to standardize the operation
and management of virtual networks and describe the components of EVB.
Virtual networks, the server-network edge, and EVB
The proliferation of virtual machines (VMs) has brought about a dramatic increase in the number of network connections
passing between the VM/hypervisor environment and the physical end station, usually a physical NIC or CNA device, in
each host server. Complex networks and network services have traditionally existed upstream
of the server’s physical NIC at
the server-network edge. These networks are now virtual, existing within the physical server and beyond the control of
network administrators using traditional network tools.
Currently, most hypervisors use some form of Virtual Ethernet Bridge (VEB), or virtual Ethernet switch, to connect VMs to the
external network. A VEB can also support internal connections between local VMs within a single physical server. This VM-
to-VM traffic is invisible to standard network policy enforcement. We must enhance VEBs to provide access for network
controls comparable to those found in physical networks.