HP Virtual Connect Manager Version 1.21 Release Notes and Compatibility Matrix

Important notes and recommendations 10
• Virtual Connect Manager assigns or migrates MAC addresses or WWNs for server Ethernet and FC
ports connected to HP Virtual Connect modules. Virtual Connect Manager also assigns MAC
addresses and WWNs to server Ethernet and WWNs to FC ports that are not connected to an I/O
module because Virtual Connect modules can be added later. Server Ethernet and FC ports
connected to non-Virtual Connect modules retain the server factory default MACs addresses and
WWNs.
• Verify that all iLOs and Virtual Connect modules have valid and unique IP addresses on the same
subnet as the OA. Without IP addresses on all modules, Virtual Connect does not work properly.
• Back up the Virtual Connect domain configuration each time changes are made. While saved in
non-volatile memory and check-pointed to the neighboring module, HP recommends saving the
configuration external to the enclosure.
• Removing a VC-Enet module and plugging it into another enclosure causes the configuration
information on that module to be cleared. This action prevents a configured spare from overwriting
configuration data in another enclosure.
• The CX4 interface on the HP 1/10 Gb VC-Enet modules uses the same physical connector as
Infiniband, but Infiniband cables are tuned differently and do not perform as well in CX4
applications. HP recommends purchasing CX4 cable assemblies that meet the IEEE CX4
specifications and support 10-Gigabit communication at distances from 3 m to 15 m (9.84 ft to
49.20 ft). These cables can be used as uplinks to external switches.
HP 1/10Gb VC-Enet modules also support 10GBASE-CX4 stacking cables 0.5 m to 7 m (1.64 ft to
23.00 ft). When multiple cables of the same speed are connected to two VC-Enet modules, they are
aggregated to provide enhanced throughput for the stacking link.
• The Onboard Administrator must have an IP address on the same subnet as the Virtual Connect
module before the administrator sets the Enclosure Bay IP Addressing (EBIPA) mode. Changing the
EBIPA address for a module causes the module to be reset by the OA (resulting in an outage) when
the change is applied. If multiple modules have their EBIPA address changed, all modules
experience the outage at approximately the same time.
• The port monitoring network analyzer port should only be connected directly to an analyzer.
Improper connection of the port or improper configuration of the port monitoring could result in
network loops and cause a network outage.
• Port monitoring is disabled in a mixed firmware environment. If any module in the domain is running
a version of firmware prior to v1.20a, port monitoring is automatically disabled.
• When the management network is fully saturated, access to the VC Manager and response times
might be slower due to network congestion.
For additional information, see the Virtual Connect user guide on the HP website
(http://www.hp.com/go/bladesystem/documentation
).