Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics), iSCSI accelerator and RAM disk
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
-
makerbiles6
- Posts: 1
- Joined: Tue Jun 02, 2020 9:11 am
Tue Jun 02, 2020 9:42 am
I picked starport up about a month ago and have become thoroughly hooked. One odd behavior I've noticed is that if I have X fleets in a system with X starports and I upgrade them all at the same time, they all queue up at one of the starports and leave the other ones empty and not doing anything. I feel like this should be something the fleet AI does automatically, but I guess not. Is there a way to assign what starport in a system with multiple starports a fleet will upgrade at?
-
anton (staff)
- Site Admin
- Posts: 4021
- Joined: Fri Jun 18, 2004 12:03 am
- Location: British Virgin Islands
-
Contact:
Tue Jun 09, 2020 2:34 pm
It's unsupported to have multiple different StarPort drivers installed on the same system. You should have one single binary running which does multiple things: NVMe-oF connectivity, FCoE, iSCSI etc.
Regards,
Anton Kolomyeytsev
Chief Technology Officer & Chief Architect, StarWind Software
