Adding Port When Updating a Farm Does Not Switch Devices (4989531)

Initially, a device with only a single connection was requested and allocated. Later a second connection to the device was requested, but the request could not be granted because the allocated device only has one connection. No new device is allocated to fulfill this request.

Workaround 1: Always connect both physical interfaces to subnets even if you do not need the two interfaces. Connecting both interfaces guarantees that a device with two connected interfaces is allocated to the farm. The secondary interface can then be reconfigured at a later time once a purpose has been identified.

Workaround 2: When a farm update fails due to the lack of resources after connecting a secondary interface of a server, bring the farm into active state by changing the farm design back to its previous design and resubmitting a farm update request. When the farm is in active state, snapshot the device to which you would like to add a second interface. Once the snapshot is completed, update the farm by removing the original server to which you would like to add a second interface and replace the deleted server with a new server and initialize its disk from the snapshot image. Connect both physical interfaces of the new device to a subnet and submit the farm update request. A new server will be allocated to the farm with two connected interfaces.

Workaround 3: Add a second switch to the chassis that hosts the device requiring the second connection. Update the device using the shelfsync command. Then resubmit the farm update request.

Workaround 4: Instead of using the secondary interface of the server, update the farm using a virtual interface on the primary interface. This workaround will force the bandwidth of the primary interface to be shared across the eth0 and virtual interfaces.