V6 to V8.0.6180 Upgrade: Sync Channel Issues
Posted: Sun Jan 05, 2014 1:29 pm
Greetings - I noticed when I upgraded from 6.0.5569 to 8.0.6180 that my Sync Channels did not convert correctly.
In my environment I utilize 2x 10GB interfaces for sync channels and 1x 1GB for control:
192.168.32.xxx - Sync
192.168.33.xxx - Sync
192.168.10.xxx - Control
Issues observed
1. After the upgrade all HA devices (28) had interface 192.168.33.xxx listed twice in the *.swdsk files
2. Link ids did not sequence correctly
3. Utilizing the GUI to modify/remove one of the two dupe interfaces would actually remove both from the *.swdsk file. And re-adding the correct interfaces would NOT update the file with the new data.
4. Restarting the service after modifying the interfaces from the GUI (with the failure to actually update the *.swdsk file) would cause a failure when the service tried to mount the HA device.
5. Manually modifying he *swdsk files (IP and ids) corrected the interface issue
In my environment I utilize 2x 10GB interfaces for sync channels and 1x 1GB for control:
192.168.32.xxx - Sync
192.168.33.xxx - Sync
192.168.10.xxx - Control
Issues observed
1. After the upgrade all HA devices (28) had interface 192.168.33.xxx listed twice in the *.swdsk files
2. Link ids did not sequence correctly
3. Utilizing the GUI to modify/remove one of the two dupe interfaces would actually remove both from the *.swdsk file. And re-adding the correct interfaces would NOT update the file with the new data.
4. Restarting the service after modifying the interfaces from the GUI (with the failure to actually update the *.swdsk file) would cause a failure when the service tried to mount the HA device.
5. Manually modifying he *swdsk files (IP and ids) corrected the interface issue
Code: Select all
<transport type="iSCSI" id="1">
<links>
<link id="1" type="data" priority="1" connections="4">
<peer ip="192.168.33.35" port="3260"/>
</link>
<link id="2" type="data" priority="1" connections="4">
<peer ip="192.168.33.35" port="3260"/>
</link>
<link id="2" type="control" priority="1" connections="1">
<peer ip="192.168.10.35" port="3260"/>
</link>
</links>
</transport>