Hive and SSID names must be different?

  • 1
  • Question
  • Updated 4 years ago
  • Answered
This might be well know, but I just stumbled upon this "limitation", which is "handy to know":

It appears that we cannot create an SSID profile with the SSID value itself being the same as the Hive name used.

Example:
- I created a new VHM "Hotel"
- Therefore, the Hive name created automatically is "Hotel"
- I tried to create a new Network Policy and inside a new SSID profile called "Hotel-Guests" (name doesn't matter), with SSID name "Hotel"

The last step is failing with the message that an object with the same name is already in use.

When changing the SSID name to something else, there is no problem. In this case I changed the Hive name to "HotelHive", and now I can create a SSID object with "Hotel" as SSID name...

I thought it's a bit weird, as a value inside an object causes the conflict, and not the object name itself. The profile name can be "Hotel", no problem...

Maybe someone from Aerohive can confirm that this is known / a bug / by design?

carsten
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes

Posted 4 years ago

  • 1
Photo of Brian Ambler

Brian Ambler

  • 245 Posts
  • 126 Reply Likes
Hi Carsten,

While I'm not sure off the top of my head whether this is as designed behavior, based on the language of the error message when I tested your workflow on 6.1r3, 6.1r5 and 6.1r6 I would imagine that that is the case.


If you require a more definitive answer I can attempt to get one for you, but since the error message contains the phrase "hive profile" I highly suspect that this is as designed behavior. 

Hope this helps
(Edited)
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
Thanks Brian!

I basically wanted to have this somehow confirmed and mentioned inside this platform, so that others stumble upon this when they encounter the same issue and search for it :-)

carsten
Photo of Brian Ambler

Brian Ambler

  • 245 Posts
  • 126 Reply Likes
Hi Carsten,

Not a problem, I was curious myself so I poked into it on a couple of different releases. When I saw no change I figured I would reply back with my findings. Hopefully our discussion helps someone out if they search for this question in the future :)

Cheers,
Brian
Photo of Rusty Wyatt

Rusty Wyatt, Technical Support Engineer

  • 14 Posts
  • 15 Reply Likes
Carsten,

Just to follow up with what Brian mentioned - it is true, you cannot have a SSID with the same name as the Hive name.  The reason is that the hidden mesh SSID utilizes the Hive name as its SSID name.  

As the Hive name is only used internally by the AP's roaming updates and for the AP's building mesh connections - there is never any user interaction with the SSID based on the Hive name.  If it is still wish to have a SSID that is a particular name, it would be easiest to change the Hive name to something different, delete the original Hive configuration object and then setup your SSID as desired.

-Rusty

Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
Ok, that makes sense - thanks for the explanation Rusty!
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Rusty, would it not make more sense to use a GUID for / append a GUID to the hidden mesh SSID?
(Edited)