topic Re: maestro port type can't change to uplink in Hyperscale Firewall (Maestro)

maestro port type can't change to uplink

LaurentFr — Wed, 17 May 2023 13:45:10 GMT

Hi,

We have two MHO-175 in R81.10 Take94 and i can't change port type to uplink.

If for example i want to change the type of the port 1/17/1 to uplink :

set maestro port 1/17/1 type uplink no-confirmation
NMSSG0013 Port 1/17/1 can't be set to uplink type.
set maestro port 1/17/1 type uplink
------------------------^^^^^^^^^^^

If i want to change the type of the port 1/17/1 to downlink, site_sync;... no problem :

> set maestro port 1/17/1 type site_sync no-confirmation
You are about to perform "set maestro port 1/17/1 type site_sync no-confirmation"
Action might impact the connectivity between the Orchestrators.

"set maestro port 1/17/1 type site_sync no-confirmation" requires auditing
Enter your full name: Auto Admin
Enter reason for "set maestro port 1/17/1 type site_sync no-confirmation" [Maintenance]: Maintenance
WARNING: "set maestro port 1/17/1 type site_sync no-confirmation", User: Auto Admin, Reason: Maintenance

Successfully set port 1/17/1 type to site_sync

Do you have an idee of the problem ?

Best regard

Re: maestro port type can't change to uplink

Timothy_Hall — Thu, 18 May 2023 13:35:22 GMT

Is port 1/17/1 currently provisioned in any of your Security Groups for any purpose? If it is I don't think it will allow you to change the port type. I believe the only ports on the 175 that have restrictions as far as type setting are ports 1 and 32.

Re: maestro port type can't change to uplink

LaurentFr — Mon, 22 May 2023 08:56:53 GMT

Hi,

I had a discussion with a PS checkpoint, with MHO-175 we can't use port 17-32 for uplink port. I confirm that i can change port beetwen 3-16 to uplink port and i can't change port beetwen 17-32 to uplink. This morning I test on a mho-170 and I don't have this limit.

Re: maestro port type can't change to uplink

Alon_Cohen — Tue, 30 May 2023 17:37:24 GMT

Hi @LaurentFr ,

I'm sure this was answered by TAC by now, but I'm making this post to have it logged.

As of now, up to 64 interfaces are supported as uplinks

As each port can be split into 4 interfaces, the 17th port is out of the allowed range. (64/4 = 16)

while supporting more than 64 is on the roadmap, I suggest submitting an RFE.

Thanks

Re: maestro port type can't change to uplink

koendsp — Thu, 12 Sep 2024 14:00:57 GMT

Thanks for the feedback. We are in the same situation a year later.
I asked TAC if they can provide more information concerning future improvements.

Re: maestro port type can't change to uplink

ShemHunter — Tue, 12 Nov 2024 11:40:02 GMT

Hello @koendsp, team

Perhaps you or one of your colleagues can help us too

We have two GW 16600HS connected to port 1/17/1 and it is defined as N/A

Replacing the DAC cable does not help, the port is constantly falling off

Now we have such a situation, the port has been rebooted, the take 89 has been set

Re: maestro port type can't change to uplink

koendsp — Tue, 12 Nov 2024 11:44:58 GMT

1/17/1 is always available as downlink.

You can't just change it from downlink to uplink. For this I have feedback from Checkpoint. It's not possible to change this. They'll go back to R&D to see if they can implement this is the new release of R82.

So for now we are stuck, we can't add new interfaces or virtual firewalls.

Re: maestro port type can't change to uplink

ShemHunter — Tue, 12 Nov 2024 12:23:36 GMT

Thank you for your reply, it helped me a lot.

And could you accidentally provide their comment, you can in private messages, you can here, I would be very grateful to you!