Ok, some new experiences and comments for you guys:
First the comments.
Yes, in reading I found many have the 'manual' practise still in place as sort of 'thing from the past when things were different so we just keep on using this practise?. Even when several other, very experienced network operators state that nowadays 'auto' is the preferred way since it works in 99,999% of the cases.
But these statements are up to today contested by some others, with the same base of experiences, stating that 'manual' is preferred on carrier and server networks since it eliminates possible problems from 'auto' setting. They defend very hard their working method to still, up to today, 'manual' settings. Off course with the mentioning that it has to be guaranteed both ends use the same setting and Gigabit is the exclusion. Giga should always be set to auto....
The 'auto' camp now actually contested the 'manual' guys in saying that if they have issues on negotiation and therefore using 'manual' its not the ethernet handshaking giving the problem, but more probably a cable issue or router issue.
And so it goes up and down...
Some came up with very recent manuals or white papers for a Cisco router where possible negotiation issues are to be solved by going to 'manual'. The manual (Cisco white paper for that series of devices) states even that 'manual' is to be preferred!
Their was also a website from a very big network operator related to ethernet issues and their conclusion was that in most fast ethernet connections manual is to be preferred.... (with the mentioning that every change of router or port or cable has to be certified and administered so no duplex or speed mismatches can occur. They claim a good operator's network administration should have ruled out any human error in this...
But ok, since I am working in an all MT routerboard environment and even the oldest units are from 2006 or so I suppose the MT drivers and embedded protocols are fully compliant to the latest standards (My network is never more than 4 OS versions behind and firmware is updated each time the OS is.)
This would make me think 'auto' is the preferred setting in my network.
I also distilled that if you have a multiple hop link running over several cable connected AND wireless connected routers, the wireless setting by themselves make no difference? So as long as one or the other medium is not the bottle neck they have no influence on eachothers performance?
This thinking is actually fed since some on the forum said that port flapping some have is probably a result from poor sync between NV2 and Gigabit interfaces on MT stuff... He mentioned that even MT had said to him it was better to have all interfaces the same and not to mix networks in partially gigabit and partially fastethernet when the wireless parts are in NV2. Basically he stated that the whole network should be made gigabit before you really would start using it in parts??
(It sounds a bit weird to me because some devices like rb750UP still have no Gigabit replacement so making a full gigabit network is impossible if you use the different MT devices....)
You guys didn't answer yet my question about what should be the setting on a multiple port router that connect to different type of networks....
Last night I had a rb1100AH that I set one port wrongly in regard to his opponent and almost all other ports stopped working inmediately! The only port still worked was the one connected to my office network (Gigabit connection to a cloud switch) and the port to my internet gateway (CCR router).
I could only bring the other ports backup by disabling the one I must have made the misalignment and reboot the rb1100AH. After that I could via a backdoor route login to the one router (netmetal) creating the issue and set is to 'auto' with all other setting enable. Only after that it worked again..... (for abt 7 hours. The rb1100AH just crashed again.... I'll tell more about this in the next post)
But this proofs imho that a mismatch in one interface will make other interface to go down as well!
Or do you guys disagree on that?
Show your appreciation of this post by giving me Karma! Thanks.
Rudy R. Puister
WISP operator based on MT routerboard & ROS.