Gents,
I spent several hours last night Googling and studying to try to figure out how to use afp to mount external drives. I am NOT that technical. I didn't succeed, but here's what I did if it gives someone else a clue to carry on the fight, or perhaps I totally went down the wrong path.
I allowed my system to normally mount the external firewire drive (boot up with external dock turned on and drive inserted). I then unmounted the drive using Disk Utility. I then opened Terminal and tried various forms of the 'mount_afp' command. There is probably a way to set the default, I couldn't find any info on that, so the 'mount_afp' was the only other thing I could think of. Now typically, mount_afp or forms of 'afp://xxx/ss' are used to attach clients that have a share defined, so maybe mounting a bare drive that is not part of a share within a system is not possible using this command. For the record, the drive is not being used for TM, just as a general archive disk, so ownership is set to 'Ignore ownership on this drive' when you look at Get Info. don't know if that is significant, but it seems 'mount_afp' requires a username/pw as part of the command, so I just used my admin login
In short, I never got the drive to mount. I believe there were some error codes returned, sometimes the prompt would just come back with no error code returned (at least not in text at the prompt, there may have been a return code), sometimes the command resulted in error code '2'. I know there are ways to setup a shell script to test for the return code, but I'm not savvy enough to write it.
Also, are we to understand then that Apple Enterprise is stating that SMB2 is now used as the default file protocol for ALL interfaces, meaning USB, Tbolt and Firewire? If we are to believe AE's explanation given to Lcrooks, then why do drives sleep fine using USB but not FW, if they are both using SMB2 now? Or is AE claiming that USB connections still use AFP, but FW now uses SMB2 by default? OR is it only the combination of SMB2 and FW? The whole explanation from AE as described doesn't quite fly; there's something missing or that is not being told. If it's an 'intended' outcome of using SMB2 for drives not to sleep, then that should be true regarless of the connection interface (eSata, FW, USB, TB, two dixie cups and a piece of string, etc).
Lastly, the statement that we "lose" performance by using afp versus smb2...if I understand what AE told you, AFP was the DEFAULT protocol for mounting external drives up until 10.9, so staying with AFP means that performance is NO WORSE than what we have been accustomed to for many, many years, presumably all the way back to 10.0. I would venture that the impact of drive specs, spin rate, cache size, seek time and so on, and the connection interface used (USB/FW) are FAR MORE impactful to performance than micro-second differences due to AFP versus SMB2.
What performance improvement is SMB2 doing for me if I have to switch back to using USB 2 instead of FW 800, so that my drives don't burn out and fail from spinning all day? Like many, I've invested thousands in drives and FW....I"m supposed to be appeased because SMB2 is 'faster', meanwhile my MTF (Mean Time to Failure) of my drives is dropping from year/months to weeks. Perhaps Apple Enterprise would like to share some actual benchmarks using same hardware, with the only difference being the file protocol? If Lcrooks can share how he set his system back to using AFP, I"m sure all of us here will run benchmarks and shove it right back into the face of Apple Enterprise.
Lcrooks my apologies, my frustration is with Apple, NOT you, please accept my apologies if my message sounds like a rant on you or a personal attack, it is not meant to be. I appreciate the time you spent working with Apple Enterprise. Could you PLEASE (yes, I am BEGGING) share the secret to reverting to AFP instead of SMB2 to mount drives? I will gladly live with the 'performance hit'.