maestro port type can't change to uplink

[LaurentFr]

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

[Timothy_Hall]

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.

[LaurentFr]

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.

[Alon_Cohen · Accepted solution]

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