No watchdog on stripped ports?

[WirelessRudy]

I have a WS-6-MINI connected to router-A- on port 3 where administration IP is set to 10.50.51.4 and unit is well reachable on that IP through that port and watchdog is set to watch the router. Router gets power from de mini so if ping fails router is rebooted and since router-A- has backhaul to central we hope to get access back in case of disaster....

On port 5 & 6 we have two other routers (Mikrotik radio's) connected.
Both have a vlan starting in router-A- so their respective vlan's 2 & 3 come in on port 3 ('T' for "tagged") and leave their designated port 6 & 5 respectively untagged ("U") to reach the routers -B- and -C-
All vlan's have a /29 subnet-
For each of the two vlan's with ID "2" and "3" we have set a non-routable IP in the netonix.

For ease we just only take vlan 2 (outgoing 'U' port 6) where unit that has to be watched for is 10.50.51.29
vlan 2 started in Router-A- with 10.50.51.25/29 and ends in this router-5- with IP=10.50.51.29/29.
We first just set the watchdog to watch for 10.50.51.29 but the MINI doesn't see it and thus re-cycles the power of port 6.
Then we found we had to set a non-routable IP (but part of that network) to make watchdog to work. So we set the MINI to 10.50.51.26 with subnet 255.255.255.248 and applied.
Still the MINI can't ping that IP address?

Is this a bug?
Is this because it is stripped traffic leaving the router from a network originally coming 'in' as stipped?

Why can I not ping this address? (It is working fine, it is a fully working AP) or where did I go wrong?

[WirelessRudy]

hmm, I was hoping to have an reply by now.

we have 2 routers behind the switch, on the 'U'nstripped ports that do have an issue at times. I need the watchdog to monitor them so if they fail again it will be power cycled. Now I have a graphical ping running and each time I pass my PC can look at it if it still runs. If not, I have to do the manual port bounce...

The watchdog tool would be perfect for this but it doesn't work (in my scenario?)...

Please some feedback...

[Eric Stern]

For ease we just only take vlan 2 (outgoing 'U' port 6)

According to the screenshots vlan 2 is 'U' on port 5, not on port 6.

A network diagram would be helpful.

[WirelessRudy]

You were right about the vlan2, outgoing through 'U' port 5.
I attached a diagram. It's about vlan3 outgoing port 'U' 6 but the idea is the same.

vlan3 in router has IP 10.50.51.17/29 and runs over the ethernet to enter netonix mini on port 3 where it gets stripped and as 'u'ntagged traffic goes to port 5. Traffic in this network now goes to 10.50.51.19/29 and that all functions fine. Traffic flows and routers can ping eachother and all access from remote location is fine.

In the netonix watchdog is set to 10.50.51.19 with the non-routable address set to 10.50.51.18/255.255.255.248
Watchdog recycles power on port 5 every set time and from 'tools' I cannot ping the .19 address from the mini.....

[Eric Stern]

Again, the screenshot above shows vlan 3 on port 6, not on port 5, but your network diagram indicates vlan 3 on port 5.

Double check your configuration and make sure you haven't got your vlans mixed up.

[WirelessRudy]

Ok, you are right. I double checked and made a new, detailed diagram and indeed found the 'U' ports were switched.
It's corrected and now the ping and watchdog works.

What is weird though is that although the 'U' port for traffic still worked. So packages coming in on port 3 with vlan2 (or 3) header still ended up in their assigned routers. Even though the 'U' port were set wrong? How is that possible?
We could still reach the routers on port 5 and 6 and further away over that vlan-to-port combination.
We did have ping failures at times and one router sometimes giving a crash (still don't know if this was the reason, lets hope so!) but in 99% of the time it worked.......?