6.5R3 - WSAM supported applications/Allowed Server naming issue

[dcvers_]

I've just upgraded our test box to 6.5R3 and noticed that in the list of WSAM supported applications/Allowed Server the name of every other application/server is prefixed with '1-'. Not sure if this will cause any issues but it looks a bit ugly

[muttbarker_]

Interesting - where exactly are you seeing that? I just did an upgrade this morning and have not noticed that behavior.

[SonicBoom_]

ive been running 6.5R3 for about a week now and havent noticed that either

[irtizas_]

Where did you get 6.5R3 from, I cant see it on the downloads page!

---

@SonicBoom wrote:

ive been running 6.5R3 for about a week now and havent noticed that either

---

[dcvers_]

Its on the WSAM Support Applications adn Allowed server lists. See attached as an example

[MattR_]

I've seen this happen before after a config import. When the imported entries create duplicates of existing apps/destinations it adds the 1- to the begining. In this case I don't know if there are dup's but that's generally what it means.

[zanyterp_]

What version did you upgrade from?

Do you have any other roles with the same bookmark configured?

It has been known to happen in some instances; but it is not expected and does not affect the functionality of your device.

It is a cosmetic admin UI-only item

Do you use NSM, push config, XML import/export for any configuration items?

[dcvers_]

The upgrade was from 6.1R7 (build 13915). I've just tried rolling back and upgrading to 6.5R3.1 with the same results.

For every WSAM role with multiple Applications or allowed servers every other item in the list is prefixed with '1-'.

We have not used NSM, push config or XML import on any of the config items.

Putting my programmers hat on as the error is so regular I would say it sounds like a variable's not getting reset properly during the import. Maybe because of the large version difference there are multiple passes to upgrade the config (I did double checked and 6.1R7 is a supported source release).

If I get time I'm going to try upgrading to an interemediate release first to see if this helps.

[dcvers_]

OK, I've tried doing some upgrades to ealier release and get the same issue. I tried all of the following with the same result:
6.1R7 to 6.2R7.0
6.1R7 to 6.3R7
6.1R7 to 6.4R5.1

I guess we'll just have to live with it but I'll submit a trouble ticket