HTTPS Issue has ben solved on L3 Switch and MX -firmware issu on 17 x Ver or higher

Kave
Getting noticed

HTTPS Issue has ben solved on L3 Switch and MX -firmware issu on 17 x Ver or higher

We are using MX105 and MS 250.

 

had issue with firmware upgrade when upgrade from 16 x to 17 x or higher ver.

 

problem was HTTPS traffic got slow even with good bandwidth .

 

Please use Unique Client Identifier instead MAC address as shown on screen shot.

 

you can find it in Security & SD-WAN --> Addressing&VLANs

 

We are using MX105 and MS 250.

 

had issue with firmware upgrade when upgrade from 16 x to 17 x or higher ver.

 

problem was HTTPS traffic got slow even with good bandwidth .

 

Please use Unique Client Identifier instead MAC addres as shown on screen shot.

 

you can find it in Security & SD-WAN --> Addressing&VLANs

kav noroozi
3 Replies 3
alemabrahao
Kind of a big deal
Kind of a big deal

Does not make sense.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
ww
Kind of a big deal
Kind of a big deal

Its also what support tells you now.

Unique Client Identifier or Ip address

 

However its just strange that this is suddenly  a issue... And you cant use it when you have a combined network without a switch...

Kave
Getting noticed

HI,

 

Meraki Tec suggestion was  using Unique Identifier

kav noroozi
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels