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.
•Do not create or modify a network name with a hyphen
•If a
•Server blade boot can be delayed when more than one server blade HBA is aggregated through a
•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 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 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.
•Virtual Connect Manager might not display an error in the Domain Status screen when a
•Some messages listed in the Domain Status screen might not appear in the Domain Status Summary 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.
•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.
•The current IP address of the
The following issues that existed in
•A Brocade (or HP
Resolved issues 12