HP BL680c HP Virtual Connect Enterprise Manager User Guide - Page 15

Setup and configuration summary, Virtual Connect Enterprise Manager operations

Page 15 highlights

Figure 1-2 Virtual Connect Enterprise Manager operations VCEM centralizes Virtual Connect infrastructure management and increases productivity. Setup and configuration summary To set up and configure VCEM into an existing HP BladeSystem environment running Virtual Connect: 1. Verify that existing Virtual Connect module firmware and HP Onboard Administrator firmware meets the minimum requirements. For a complete list of hardware, firmware, and software requirements, see the HP Insight Software Support Matrix. 2. Install the VCEM software on a designated host system running a supported operating system using the HP Insight Software DVD. Insight Software media can be downloaded from http://www.hp.com/go/insightcontrol. 3. Open the VCEM console, and then discover all existing VC Domains. 4. From the list of discovered domains, select which ones you want to manage using VCEM. 5. Apply a single VCEM license to each VC Domain to be managed. A VCEM license enables operations across all bays in an enclosure for the life of the enclosure. 6. From the VCEM console, create one or more VC Domain Groups, and assign available VC Domains to the groups. • The configuration of the first domain in a VC Domain Group defines the characteristics for all subsequent group members. • All domains in a group have the same Virtual Connect uplink connections to LANs and SANs. After you complete these steps, VCEM is ready to centrally manage your Virtual Connect infrastructures. You can now add, change, and move blade servers across the data center in minutes. Setup and configuration summary 15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111

Figure 1-2 Virtual Connect Enterprise Manager operations
VCEM centralizes Virtual Connect infrastructure management and increases productivity.
Setup and configuration summary
To set up and configure VCEM into an existing HP BladeSystem environment running Virtual Connect:
1.
Verify that existing Virtual Connect module firmware and HP Onboard Administrator firmware meets
the minimum requirements. For a complete list of hardware, firmware, and software requirements, see
the
HP Insight Software Support Matrix
.
2.
Install the VCEM software on a designated host system running a supported operating system using the
HP Insight Software DVD.
Insight Software media can be downloaded from
ht
tp://w
w
w
.hp
.com/go/insight
contr
ol
.
3.
Open the VCEM console, and then discover all existing VC Domains.
4.
From the list of discovered domains, select which ones you want to manage using VCEM.
5.
Apply a single VCEM license to each VC Domain to be managed. A VCEM license enables operations
across all bays in an enclosure for the life of the enclosure.
6.
From the VCEM console, create one or more VC Domain Groups, and assign available VC Domains
to the groups.
The configuration of the first domain in a VC Domain Group defines the characteristics for all
subsequent group members.
All domains in a group have the same Virtual Connect uplink connections to LANs and SANs.
After you complete these steps, VCEM is ready to centrally manage your Virtual Connect infrastructures. You
can now add, change, and move blade servers across the data center in minutes.
Setup and configuration summary
15