RB450G with VLAN stops responding

4 weeks ago I added 4 VLANs to a RB450G that’s running 5.26 and since then it has stopped responding a dozen times. It doesn’t respond to anything. After the first 3 times I replaced the board and the power supply but the problem continues. I added a watchdog to it last week because it’s a 20 minute drive to power cycle it. It’s since rebooted another 4 times.

Could my VLAN config be causing it to stop responding ?

Any advice greatly appreciated…

/interface bridge
add name=loopback
add l2mtu=1516 name=Access-VLAN1000 protocol-mode=rstp
add l2mtu=1516 name=Access-VLAN1001 protocol-mode=rstp
add l2mtu=1520 name=Trunk protocol-mode=rstp
add l2mtu=1516 name=Access-VLAN41 protocol-mode=rstp
add l2mtu=1516 name=Bridge-VLAN42 protocol-mode=rstp

/interface ethernet
set 0 comment=“10.3.1.251/26 To KEN” name=ether1
set 1 comment=“10.3.1.20/26 To FTZ” name=ether2
set 2 comment=“Trunk From RB750GL” name=ether3
set 3 comment=NoVLAN name=ether4
set 4 comment=“10.3.1.120/26 To BRS” name=ether5

/interface vlan
add interface=Trunk l2mtu=1516 name=vlan41 vlan-id=41
add interface=Trunk l2mtu=1516 name=vlan1000 vlan-id=1000
add interface=Trunk l2mtu=1516 name=vlan1001 vlan-id=1001
add interface=Trunk l2mtu=1516 name=vlan42 vlan-id=42
/interface ethernet switch
set 0 switch-all-ports=no

/routing ospf instance
set [ find default=yes ] redistribute-connected=as-type-1 router-id=
10.255.255.20

/interface bridge port
add bridge=Access-VLAN1001 interface=vlan1001
add bridge=Trunk interface=ether1
add bridge=Access-VLAN41 interface=vlan41
add bridge=Access-VLAN1000 interface=vlan1000
add bridge=Bridge-VLAN42 interface=vlan42
add bridge=Trunk interface=ether3

/interface bridge settings
set use-ip-firewall-for-vlan=yes

/interface pptp-server server
set enabled=yes

/ip address
add address=10.3.1.129/26 comment=“VLAN1000” interface=Access-VLAN1000
add address=10.3.1.20/26 comment=“To FTZ” interface=ether2
add address=10.255.255.20/32 comment=Loopback interface=loopback network=
10.255.255.20
add address=10.3.1.120/26 comment=“To BRS” interface=ether5
add address=10.3.1.251/26 interface=Access-VLAN1001
add address=10.241.2.1/16 interface=Access-VLAN41
add address=172.16.132.1/25 interface=Bridge-VLAN42

/ip dns
set allow-remote-requests=yes max-udp-packet-size=512 servers=
8.8.8.8,8.8.4.4

/ip firewall connection tracking
set enabled=no

/ip route
add distance=110 dst-address=172.16.104.0/22 gateway=10.3.1.97
add distance=1 dst-address=172.16.130.0/24 gateway=10.3.1.22
add distance=1 dst-address=172.16.131.0/24 gateway=10.3.1.22

/ip service
set api disabled=no
/queue interface
set ether1 queue=ethernet-default
set ether2 queue=ethernet-default
set ether3 queue=ethernet-default
set ether4 queue=ethernet-default
set ether5 queue=ethernet-default
/radius
add address=172.16..secret=***** service=dhcp src-address=
10.255.255.20 timeout=1s500ms
/radius incoming
set accept=yes
/routing ospf interface
add authentication=simple authentication-key=****** interface=Access-VLAN1001
network-type=ptmp
add authentication=simple authentication-key=****** interface=Access-VLAN1000
network-type=ptmp
add authentication=simple authentication-key=****** cost=11 interface=ether5
network-type=ptmp

/routing ospf network
add area=backbone network=10.3.1.192/26
add area=backbone network=10.3.1.128/26
add area=backbone network=10.3.1.64/26

/snmp
/system clock
/system ntp client
set enabled=yes mode=unicast primary-ntp=10.3.1.254 secondary-ntp=10.3.1.121

/system watchdog
set watch-address=10.3.1.130

Has anyone else seen this problem ? Or any comments on how the VLAN config could be causing it ?

I can’t get a supout.rif file from either of the 450G’s that’s I’ve used because when they do this because they are totally non responsive to ALL ports/input.

Watchdog reboots the device but without writing or sending the supout file which I DO have enabled in the watchdog settings.

Thx

If no one can verify the VLAN config any comment on why the watchdog is NOT writing autosupout ? Has anyone seen that before ?

/system watchdog
set auto-send-supout=no automatic-supout=yes no-ping-delay=5m watch-address=
10.241.2.11 watchdog-timer=yes

[admin@RtR] > file pr

NAME TYPE SIZE CREATION-TIME

0 console-dump... .txt file 38 737 jun/29/2013 14:44:06
1 skins directory dec/06/2011 05:09:22
2 xxx-RtR-1502... backup 105 004 feb/15/2014 09:50:43
3 xxx-RtR-1502... backup 105 004 feb/15/2014 09:58:52
4 pub directory may/13/2012 02:00:04

[admin@RtR] > log pr
jan/01/1970 19:00:08 system,error,critical System rebooted because of ping watchdo
g timeout
jan/01/1970 19:00:08 system,info router rebooted
jan/01/1970 19:00:17 interface,info ether5 link up (speed 100M, full duplex)
jan/01/1970 19:00:17 interface,info ether2 link up (speed 100M, full duplex)
jan/01/1970 19:00:18 interface,info ether3 link up (speed 1000M, full duplex)
jan/01/1970 19:00:18 interface,info ether1 link up (speed 1000M, full duplex)

Finally got a supout.rif file from this Routerboard. Sent it in and support’s suggestion was to upgrade to 6.11… umm, no thanks…

Instead we downgraded this box to 5.24, 10 days ago and no issues since… which is at least 3 days better than the best we had with 5.26

It looks like there’s something wrong with VLANs in 5.26.

Munsi