"Cannot have duplicate Priority"

[Nick-ZetaBroadband]

WS-12-250-DC

We cannot make any changes to the device due to this error message.

Error Message

We were thinking it was STP as the priority was listed as the same there, but we received the message even when trying to disable STP.

STP

LAG is disabled. The only other priority we can see is power, which is different.

Power

It is currently running 1.4.4.

Status

We have rebooted the device via Utilities. The error message persists and even shows up when no changes are made when we hit Save/Apply.
We have powered the device off via unplugging the DC power. When it comes back on it gave an error message "Invalid Fields" each time a change was attempted. It went back to the Duplicate Priority error once it was rebooted via Utilities again.

Any ideas?

[Eric Stern]

That message refers to the priorities on the Power tab. But the priorities on the Power tab look correct. So it must be something else.

Can you send me a backup of the config? Email to eric@netonix.com would be easiest.

[Nick-ZetaBroadband]

Backup config sent.

[Eric Stern]

The config actually has Priority values for ports 13 and 14 even though they are not shown in the UI. Somehow those values got set to 9 and 10, which are duplicates of the values for port 9 and 10, hence the error.

I'll send you a fixed config.

I'll also change the code so it ignores the values for ports 13 and 14 in the future.

[Nick-ZetaBroadband]

Thank you!

[Nick-ZetaBroadband]

We just got a tech onsite today to be there in case something went wrong with the restore.
The backup config provided did not resolve the issue. Cannot have Duplicate Priority is still preventing changes to the device after the device was restored from the config file.

[sirhc]

We just got a tech onsite today to be there in case something went wrong with the restore.
The backup config provided did not resolve the issue. Cannot have Duplicate Priority is still preventing changes to the device after the device was restored from the config file.

Sadly Eric has gone home for the day and can not be reached.

Options:
1) Wait until tomorrow then allow Eric to Team View to your computer and allow him to manually modify the switch config file.

2) Default the switch and set back up manually.

[Banana Jack]

I got this issue too after restoring a config from a WS-8-250-DC to a WS-12-250-DC running 1.4.5rc2 on both. I will configure from scratch manually.

[sirhc]

I got this issue too after restoring a config from a WS-8-250-DC to a WS-12-250-DC running 1.4.5rc2 on both. I will configure from scratch manually.

Well considering your running v1.4.5rc2 and Eric did not fix this issue until v1.4.5rc6 I would assume you would have the issue?

Mon Sep 26, 2016 4:35 pm

The config actually has Priority values for ports 13 and 14 even though they are not shown in the UI. Somehow those values got set to 9 and 10, which are duplicates of the values for port 9 and 10, hence the error.

I'll send you a fixed config.

I'll also change the code so it ignores the values for ports 13 and 14 in the future.

However your description is being you restored a config from a WS-8 to a WS-12 config is backwards of what occurred before I will ask Eric to verify that direction of restoring a config works.

[Banana Jack]

Well considering your running v1.4.5rc2 and Eric did not fix this issue until v1.4.5rc6 I would assume you would have the issue?

Yes I agree. I'll get round to upgrading the network soon, but today it was just easier for me to do the manual config.

However your description is being you restored a config from a WS-8 to a WS-12 config is backwards of what occurred before I will ask Eric to verify that direction of restoring a config works.

Well spotted; I hadn't noticed that. Yes, making config files interchangeable both ways would be great.

Thanks as ever
Glenn