Hello I would need to create a script to delete the interfaces is known when disconnecting from it indeed after a certain time there are a lot of unknowns in interface and I would like to develop a daily script to delete this value useless I have tried several approaches but I can’t manage to simply delete an element inside
/ip route vrf set number=0 do{remove interfaces=“FTTH_PPPoE”}
I attached a screenshot to show what it looks like. Thank you very much for your help I’ve been looking for a while I can’t find a solution to this problem
I want to clarify that unknown that appears in the VRF listing are created when a link drops with the script up down in a VRF profile to include a link in a VRF when it goes up. I’m just looking for a script that could daily purge its errors attempts to create a script that realizes are unsuccessful. I need a little helping hand.
Thanks in advance for this answer but the problem is that I cannot for the moment pass on version 7 and I would simply like to try to find a script for network temporarily this concern…
I would simply have liked to find a script which deletes the entries which do not correspond to anything and which goes up as unknown in ip route VRF and this cyclically every day at midnight this would have made it possible to solve the problem temporarily
Is there anything I could fix in my code to avoid this problem if not?
Here is the script i use in up and down :
up
:local localAddr $“local-address”
:local remoteAddr $“remote-address”
:local callerId $“caller-id”
:local calledId $“called-id”
:local routes $“routes”
:local routes $“routes”
:local interfaceName [/interface get $interface name]
:local calledRealm PI-VRF-4G
:local vrfId [/ip route vrf find where routing-mark=$calledRealm]
/ip route vrf print terse file=($calledRealm.“Members”) where routing-mark=$calledRealm
:local actualVrfIfs [/file get ($calledRealm.“Members”) contents] ;
:local actualExistentIfs [:pick $actualVrfIfs ([:find $actualVrfIfs “interfaces=” ]+11) ([:find $actualVrfIfs “route-distinguisher=” ]-1)]
/ip route vrf set $vrfId interfaces=“$actualExistentIfs,$interfaceName”
:log info “$user (srcIp=$callerId, dstIp=$calledId) connected: was given $remoteAddr IP (GW $localAddr) and routes $routes and assigned to $interfaceName interface in VRF $calledRealm”
/file set ($calledRealm.“Members”) contents=“”
/ip route vrf print terse file=($calledRealm.“Members”) where routing-mark=$calledRealm
Changing config in the VRF will flap the VRF. Instead I would suggest to add static entries for each l2tp user in /interface l2tp_server and use that for VRF config, instead of adding dynamic entries and then trying to deal with the consequences via scripts.
so you are advised not to use the script that I mentioned a little earlier in the subject and to use another function to automatically integrate the links when it goes up in the right VRF?
I do not understand the script that is inserted in script down in the profile will have to remove the ppp interface in /ip route vrf. I made a description of what the script should do but I think there is something in it that is not working properly because the remaining error should no longer be present when the script applies. I put you the script in question if you have an idea I’m interested.
This script is used by dozens of operators in France with whom I am a partner and whose solution we are looking for.
Script down in profil :
:local localAddr $"local-address"
:local remoteAddr $"remote-address"
:local callerId $"caller-id"
:local calledId $"called-id"
:local interfaceName [/interface get $interface name]
:local calledRealm PI-VRF-4G:local vrfId [/ip route vrf find where routing-mark=$calledRealm]
:delay 2
/ip route vrf print terse file=($calledRealm."CleanUpMembersSec") where routing-mark=$calledRealm
:local cleanUpVrfIfsSec [/file get ($calledRealm."CleanUpMembersSec") contents] ;
:local cleanUpExistentIfsSec ([:pick $cleanUpVrfIfsSec ([:find $cleanUpVrfIfsSec "interfaces=" ]+11) ([:find $cleanUpVrfIfsSec F00 ] -2)]. \
[:pick $cleanUpVrfIfsSec ([:find $cleanUpVrfIfsSec F00 ] + 6) ([:find $cleanUpVrfIfsSec "route-distinguisher=" ]-1)])
:put $cleanUpExistentIfsSec
/ip route vrf set $vrfId interfaces="$cleanUpExistentIfsSec"
/file set ($calledRealm."CleanUpMembersSec") contents=""
/file set ($calledRealm."Members") contents=""
/ip route vrf print terse file=($calledRealm."Members") where routing-mark=$calledRealm
This Mikrotik script runs on a Mikrotik router and performs the following actions:
Defining variables: The script defines several local variables to store information such as local address, remote address, caller ID, callee ID, interface name, name of the called reality and the identifier of the VRF (Virtual Routing and Forwarding).
Retrieving information about VRF interfaces: The script uses the “/ip route vrf print terse” command to retrieve information about the current interfaces in the called VRF. The results are saved in a file called “CleanUpMembersSec”.
Modification of VRF interfaces: The script uses the “/ip route vrf set” command to define the interfaces associated with the called VRF. The script extracts information about VRF interfaces from the “CleanUpMembersSec” file.
File update: The script uses the “/file set” command to dump the files that contain the VRF interface information.
Basically, this script changes the interfaces associated with the called VRF by removing all information about previous VRF interfaces.
uses “F00” to search for a string in the cleanUpVrfIfsSec variable, but “F00” is likely not a valid value in the string. This can cause an error in the script and prevent the correct removal of VRF interface information.
It would be advisable to change “F00” to a valid value or find another method to extract the necessary information from the VRF interfaces.
Otherwise I’m thinking of removing the “unknown” interface from the VRF route list, using the following code but I’m not sure:
:local vrfId [/ip route vrf find where routing-mark=PI-VRF-4G];
/ip route vrf print terse where routing-mark=PI-VRF-4G
:local vrfRoutes [/ip route vrf print where routing-mark=PI-VRF-4G];
:local vrfRouteCount [:len $vrfRoutes];
:local removedRoute 0;
:for i from=0 to=($vrfRouteCount - 1) do={
:local route [:pick $vrfRoutes $i];
:if ([:find $route "unknown"] >= 0) do={
/ip route vrf remove $route;
:set removedRoute 1;
}
}
:if ($removedRoute = 0) do={
:log info "No unknown routes found in VRF PI-VRF-4G";
} else={
:log info "Removed unknown routes from VRF PI-VRF-4G";
}
This code first finds the VRF ID named “PI-VRF-4G”, then prints the full list of VRF routes. It then loops through each route and uses the “/ip route vrf remove” command to remove any routes that contain the word “unknown”. Finally, the code sends an informational message to logging to indicate whether or not a route has been deleted.
Ok so if I understood correctly no longer need to use the up script and the down script in profile to automatically add or remove a PPP session from a VRF with V7
Ok for that but I allow myself to insist because we cannot yet switch to V7 and we are stuck on V6 the script that I wrote a little above can it clean the errors that appear in VRF where is the on down profile script needs to be patched to properly remove its entries? I speak on behalf of several integrators who have the same problem and who are stuck like me…
if u use dynamic interface in VRF on v6.
Obviously u need to make them statically , but also in ppp → profiler - make sure that u got selected only-one=yes.
In case if the session established will be assigned as static, and will work perfectly.
so according to your technique I have to put the same name that I use of a secret PPP in a new L2TP server binding interface and then add this L2TP server binding interface in the VRF?
If I understood correctly using this technique no longer need to use the up and down script in the profile?
