R80.20 Management and vpn domain Edge N

[Andrey_Ganichev]

Hello,

We plan to update MGMT (MDS) R77.30 to R80.20. This MGMT manages geteways including Edge N/X. Edge N is referred to as supported by R80.20. But when testing we found out that to Edge N not transmitted vpn domain behind central cluster and traffic inside tunnel does not work. Has anyone faced this issue? While there is a temporary solution to transfer these devices to local management or to the dedicated MGMT R77.30.

Andrey

[PhoneBoy]

Recommend a TAC case so we can investigate.

[Andrey_Ganichev]

TAC with RnD are investigating this issue. We are waiting the result.

Andrey

[RicardoI]

hi, any solution, i have the same issue with a N Edge in R80.30, problem with the traffic in the vpn

[Wolfgang · Accepted solution]

Andrey,

we observed the same.

If you don‘t use VPN with the edges everything will be fine. The tunnel is established but no traffic is going this way.

A workaround is, to not install R80.20 policy to the edge device or the LSM-profile if used. But with this workaround you can‘t change anything at the policy for the edges.

We used these, because we were on the way of replacement of the edges with 14xx appliances. This worked for us for an half year, now we replaced all edges and we can change the policy for the new 14xx.

We never opened a case for this.

Wolfgang

[Andrey_Ganichev]

Wokfgang,

Thanks. I'll keep that in mind. We can't replace all Edge N/X to 14xx quickly too.

Andrey

[G_W_Albrecht]

VPN-1/UTM-1 Edge X is out of support since 31-May-2015, UTM-1 Edge N since May-2018 - but as the R80.20 Release Notes state that it can manage UTM-1 Edge N 8.1 and higher, something is missing here... Only UTM-1 Edge Industrial has support until 26-May-2020.

[miko_it]

Andrey,

We noticed the same, but installing R80.10 did work. Now we'll see to get the latest UTM Edge N replaced by a newer edge but at least it works.