A anomaly routeing rule in config for EOL VPN300

PeterUK · February 20

So might not be a problem I'm not sure its causing a issue and likely when I reboot this rule is not understood by the VPN300 and skips it but through I show anyway.

This is what I see in config file when I save from VPN300 for the end of routing rules

!

policy 129

 interface vlan777

 source IP192168130

 dscp any

 next-hop interface ge4

 snat outgoing-interface

 auto-disable

 conn-check activate

 conn-check 1.1.1.1 method icmp period 5 timeout 1 fail-tolerance 2

!

policy 130

 interface vlan777

 source IP192168130

 dscp any

 next-hop interface ge2

 snat outgoing-interface

!

policy6 1

 interface vlan1000

 dscp any

 next-hop interface ge4

LeoEthan · March 8

This looks like a small syntax anomaly in the config. The line policy6 1 doesn’t follow the same format as the other policies (129, 130), so it may simply be a parsing or formatting issue in the exported configuration. Since the VPN300 is already EOL, the device might just ignore that entry when loading the config. If everything is working normally, it’s probably harmless, but it might still be worth cleaning it up to keep the configuration consistent.

A anomaly routeing rule in config for EOL VPN300

All Replies

Categories

Security Help Center