fos v6.4.3 demands different portnames?

We have upgraded an silkworm 4100 switch to fos v6.4.3 following the upgrade path.

The old fos we used supported duplicate portnames, also the new ones ( 6510, fos v7.1.0a ) allow duplicate port names.

So we used it to label an unused port with "---Unused---"

Fos v6.4.3 however doesnt allow it, or is there some setting i have missed to change the portname policy. The Strange thing however is actually there are duplicate port names (configured prior to the fos update) but once i change them i cant change the name to the old (duplicate) name.

Re: fos v6.4.3 demands different portnames?

After downgrading 6.4.3e -> 6.3.2d-> 6.2.2f Iam now able to use duplicate portnames again.

Interestingly I couldnt find anything in any fos releaselog between 6.2.2f --> mentioning a policy change.

The command however in fos 6.3.2 and 6.4.3e changed the syntax slightly and added the feature to rename multiple portsnames by using indexes but this feature is more or less useless if it doesnt allow duplicates.

However maybe its just device specific and doesnt occur on other models by opening the "portcmd" in a bin editor I can find the encoded error String "Invalid port name, Duplicate" in those two fos versions.

Im still not sure if this is a feature or a bug, Is there some more detailed release or changelog containing all fos changes ?