Справочник Пользователя для HP (Hewlett-Packard) 1.15b
Resolved issues 12
Resolved issues
The following issues that existed in Virtual Connect 1.10 have been resolved in Virtual Connect 1.15:
•
To move a server profile from a device bay containing a storage blade to another bay, the storage
blade must first be removed.
blade must first be removed.
•
Do not create or modify a network name with a hyphen ("-") in the name. Only use characters that
are alpha-numeric (a-z, A-Z, 0-9) and the underscore ("_"). Virtual Connect Manager does not reject
are alpha-numeric (a-z, A-Z, 0-9) and the underscore ("_"). Virtual Connect Manager does not reject
names with a hyphen, but subsequent updates to the network fail without giving any error indication.
•
If a VC-FC module is connected to a Fibre Channel switch that does not support NPIV, the Virtual
Connect user interface performance will degrade significantly. If this occurs, disconnect the FC
Connect user interface performance will degrade significantly. If this occurs, disconnect the FC
switch, reconfigure the FC switch for NPIV support, and reconnect.
•
Server blade boot can be delayed when more than one server blade HBA is aggregated through a
VC-FC uplink port attached to a fabric switch. This situation occurs when the VC-FC uplink port
WWN is placed in the same zone as the server HBA WWNs. To avoid this problem, do not place
WWN is placed in the same zone as the server HBA WWNs. To avoid this problem, do not place
VC-FC uplink ports in the same zone with server HBAs on the fabric switch.
•
When the server profile wizard attempts to assign a profile to a server that is powered on, a
"creation failed" message is displayed. The profile is created, but not assigned to a device bay. The
"creation failed" message is displayed. The profile is created, but not assigned to a device bay. The
profile can be assigned to the device bay later when the server is powered off.
•
When creating a shared uplink set with a large number of networks, the error "object name already
in use" might be displayed or some networks might not be created. Verify that all the intended
in use" might be displayed or some networks might not be created. Verify that all the intended
networks were actually added to the shared uplink set by choosing to view all networks. If any
networks were not created, edit the shared uplink set and add the uncreated networks.
networks were not created, edit the shared uplink set and add the uncreated networks.
•
Virtual Connect Manager might not display an error in the Domain Status screen when a VC-FC
module is removed from the enclosure or powered down.
module is removed from the enclosure or powered down.
•
Some messages listed in the Domain Status screen might not appear in the Domain Status Summary
window.
window.
•
If the Domain Setup Wizard is cancelled prior to completion, it might not start automatically in future
logins. The wizard can be initiated again from the Tools menu.
logins. The wizard can be initiated again from the Tools menu.
•
If a server is rebooted several times while its server profile is being edited, an error displaying an
XSL transformation failure may be displayed. Do not edit a server profile while repeatedly rebooting
a server.
a server.
•
The current IP address of the VC-Enet modules is not displayed in the Onboard Administrator 1.30
Enclosure Bay IP Addressing (EBIPA) screen. This omission does not affect the ability of EBIPA to
Enclosure Bay IP Addressing (EBIPA) screen. This omission does not affect the ability of EBIPA to
assign IP addresses to VC-Enet modules.
The following issues that existed in VC-FC v1.01 have been resolved in VC-FC v1.02, which is packaged
in Virtual Connect 1.15b and 1.16:
•
A Brocade (or HP B-Series) Fibre Channel Switch running Fabric OS v5.2.x will reject NPIV login
requests when more than seven c-Class server blades are attempting to log in simultaneously through
a VC-FC module.
a VC-FC module.