IDEA: Port state follows port state
Posted: Sun Sep 06, 2015 3:38 pm
Say what? What is crazy Matt up to now.
So the airFiber radios will track RF to Ethernet port state, meaning if the RF drops (rain fade, link failure, etc) the Ethernet port will drop so that the network converges to a backup link very quickly. NICE!
I just had a thought, if I'm using a Netonix as a mid-span injector for my backhaul, which then goes to a router, I have no way to take advantage of this as the airFiber will drop the port, but the switch port connected to my router is still up, so OSPF/BGP will converge slower.
I would like to see the ability to have a port on the Netonix track the state of a different port.
EXAMPLE:
airFiber24 plugged into port 12, router plugged into port 11.
airFiber24 loses RF link, so it shuts down Ethernet to port 12. Port 12 now shows no link.
Netonix then shuts down port 11, which instantly causes the router to activate the backup link rather than waiting for an OSPF timeout.
Thoughts?
So the airFiber radios will track RF to Ethernet port state, meaning if the RF drops (rain fade, link failure, etc) the Ethernet port will drop so that the network converges to a backup link very quickly. NICE!
I just had a thought, if I'm using a Netonix as a mid-span injector for my backhaul, which then goes to a router, I have no way to take advantage of this as the airFiber will drop the port, but the switch port connected to my router is still up, so OSPF/BGP will converge slower.
I would like to see the ability to have a port on the Netonix track the state of a different port.
EXAMPLE:
airFiber24 plugged into port 12, router plugged into port 11.
airFiber24 loses RF link, so it shuts down Ethernet to port 12. Port 12 now shows no link.
Netonix then shuts down port 11, which instantly causes the router to activate the backup link rather than waiting for an OSPF timeout.
Thoughts?