HP Virtual Connect Firmware Virtual Connect and Insight Control Server Deployment

9	Start with FCoE-capable	Port	Connected to	Bay 1	Bay 2	Port	Connected to
	modules in Bays 1 and 2,	1	Bay 1	—	—	1	Bay 1
	then create a profile and	2	Bay 2	—	—	2	Bay 2
	add connections.			—	—	3	Bay 1
						4	Bay 2
						5	Bay 1
						6	Bay 2
						7	Bay 1
						8	Bay 2
						Add connection, 6 times*
10	Start with 8 FCoE-capable	Port	Connected to	Bay 1	Bay 2	Port	Connected to
	modules, then create a	1	Bay 1	Bay 3	Bay 4	1	Bay 1
	profile and add connections.	2	Bay 2	Bay 5	Bay 6	2	Bay 2
		3	Bay 3	Bay 7	Bay 8	3	Bay 3
		4	Bay 4			4	Bay 4
		5	Bay 5			5	Bay 5
		6	Bay 6			6	Bay 6
		7	Bay 7			7	Bay 7
		8	Bay 8			8	Bay 8
						9	Bay 1
						10	Bay 2
						11	Bay 3
						12	Bay 4
						13	Bay 5
						14	Bay 6
						15	Bay 7
						16	Bay 8
						17	Bay 1
						18	Bay 2
						19	Bay 3**
						20	Bay 4**
						21	Bay 5**
						22	Bay 6**
						23	Bay 7**
						24	Bay 8**
						25	Bay 1
						26	Bay 2
						Add connection, 18 times

*Using the BL890c i4 server blade, an additional eight connections can still be added. Each pair is connect to bays 1 and 2. The first four pairs of entries are mapped to LOM 1 and LOM 2 on each blade, and the last four pairs of entries are mapped to LOM 3 and LOM 4 on each blade.

**Not mapped

Virtual Connect and Insight Control Server Deployment

If you plan on using VC-assigned MAC addresses and WWNs and are also working with server software that will be licensed by MAC addresses or WWNs, assign server profiles before deploying an image through HP Insight Control Server Deployment or attaching the license.

Always apply relevant licenses that are dependent on MAC addresses after the server profiles are assigned so that the licenses are not lost due to a change in MAC address.

Virtual Connect server profiles 227