Recommendations
Posted: Tue Aug 30, 2016 4:59 pm
As we deploy more Netonix Switches on towers, And other critical locations. A few concerns come to mind. And a few suggested hardware/software configurations.
1. Dual Power option. We like to remove single points of failure. It's great to be able to stack a bunch of stuff on a Wisp Switch on a tower. But we start to put a lot of eggs in the netonix basket. If the netonix fails. Everything connected to it fails. Our current operation is deploying two backhauls that are direct powered, And direct interfaced with our router at the tower. Any additional AP's, Or additional backhauls are connected and powered from the netonix. I'd be more comfterable connecting more gear to the Netonix if it had a secondary power option, Redundant power supplies. Even a backup DC input..Something.
2. Software change, Rapid port shutdown. In the instance that we are using the Netonix as a midspan POE injector. Being able to group two ports together would be fantastic. The way this would work is monitoring the POE powering port, If it loses link, it administratively downs the non-poe powered "To router" port. Honestly, I can't think of a reason this can't go both ways, IE, if I shutdown the port on the router, The linkstate is passed all the way to the radio. In the instance that we have a radio that also supports Rapid Port shutdown, We can quickly re-route a link since OSPF detects a loss of link as an immediate re-route. Vs, Waiting for the hello timer to expire. Granted, We could run tighter hello timers or BFD, But for the moment we'd like to keep them sane, And BFD has never worked for us with Mikrotik. Not reliably at least.
1. Dual Power option. We like to remove single points of failure. It's great to be able to stack a bunch of stuff on a Wisp Switch on a tower. But we start to put a lot of eggs in the netonix basket. If the netonix fails. Everything connected to it fails. Our current operation is deploying two backhauls that are direct powered, And direct interfaced with our router at the tower. Any additional AP's, Or additional backhauls are connected and powered from the netonix. I'd be more comfterable connecting more gear to the Netonix if it had a secondary power option, Redundant power supplies. Even a backup DC input..Something.
2. Software change, Rapid port shutdown. In the instance that we are using the Netonix as a midspan POE injector. Being able to group two ports together would be fantastic. The way this would work is monitoring the POE powering port, If it loses link, it administratively downs the non-poe powered "To router" port. Honestly, I can't think of a reason this can't go both ways, IE, if I shutdown the port on the router, The linkstate is passed all the way to the radio. In the instance that we have a radio that also supports Rapid Port shutdown, We can quickly re-route a link since OSPF detects a loss of link as an immediate re-route. Vs, Waiting for the hello timer to expire. Granted, We could run tighter hello timers or BFD, But for the moment we'd like to keep them sane, And BFD has never worked for us with Mikrotik. Not reliably at least.