Hi,
We are an ISP company and I have several VPLS tunnels configured for my Fiber customers. I am facing a strange issue with my VPLS tunnels and that is whenever a customer’s router is rebooted for any reason then sometimes the VPLS comes up and sometimes it doesn’t come up and after disabling and re-enabling the VPLS interface it starts working again. Can anyone from the experts help me resolve this issue please ?
Regards,
It sounds like a timing issue when rebooting.
The fact that it happens only some times (and possibly only on some routers) makes it difficult to avoid completely.
Probably the workaround would be a script set to run (say) after 3 minutes after boot that disables and re-enables the VPLS interface.
I have corrected the date and time on the customer router now, will monitor it whether it faces the similar issue the next time it reboots or not. Also, your script idea is great, can you please guide me about the script thing as I am new to the mikrotik.
You will need to use one of these methods:
http://forum.mikrotik.com/t/run-script-after-re-boot/157645/1
http://forum.mikrotik.com/t/run-script-after-re-boot/157645/1
The script in itself (or the command added to the scheduler script) should amount to:
delay 10s
/interface vpls disable [find]
delay 5s
/interface vpls enable [find]
to disable and enable all vpls interfaces or use something like:
/interface vpls disable [find where <property>="<value>"]
where could be name, comment, mac-address, peer, etc.:
https://help.mikrotik.com/docs/display/ROS/VPLS
to select a specific one.
You will need to experiment with the amount of delays that are needed, both the initial and the one after disable before enable.
Also you could complicate it by adding a check whether the connection is actually working and only disable and re-enable it if is stuck, but this depends on how the running state of the interface is reported correctly or on what other parameter one could check.
EDIT:corrected a couple of typos
Thank you. I will try to implement this now.