Hi all,
I am observing very strange behavior of Omnitik devices. From some reason I have a netwatch that checks the accessibility of some device in the network and in case of non response it disables one ethernet port, waits for 5 seconds and enables it again. It works fine.
What is weird is that when the port is enabled, it shuts down and up also other at the moment active ports:
May/05/2014 23:26:50 interface,info eth1-cbc link down
May/05/2014 23:26:50 interface,info eth2-bub link down
May/05/2014 23:26:50 interface,info eth3-lan link down
May/05/2014 23:26:51 interface,info eth2-bub link up (speed 100M, full duplex)
May/05/2014 23:26:51 interface,info eth3-lan link up (speed 100M, full duplex)
May/05/2014 23:26:52 interface,info eth1-cbc link up (speed 100M, full duplex)
How to ensure that enabling the interface will not affect other ethernets?
Not bridged, not switched, just routed. Ether1 is WAN, Ether2 is another WAN and Ehter3 is LAN behind NAT. So logically are all ports fully separated.
And this happens to two different devices with different ROS versions as written above.
I also do not see anything wrong. Therefore I sent it to public… Of course there is no master port as the ether1 is standalone wan port. The same happens to all active ethernets when ether3 is disabled/enabled by netwatch. Ether3 is part of bridge1.
This also occurs with Rb751 but only when ether1 is cycled. If ether1 is disabled and then renewables all the other ports (ether2 through ether5) reinitialize. It’s normally not noticed but if you have a dynamic routing protocol like ospf running on e2, for example, the ospf session is reset as a result. In such a case it’s very noticeable and disruptive. This doesn’t happen if hue port cycled is not e1 if I remember correctly.