You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would make sense to alter the rack naming constraint to include the rack groups instead of just the site.
Take for instance a Site thats a single building, but within it it has multiple floors with multiple IDF's per floor. Each IDF is its own rack group, but within each IDF the racks can easily be named quite identically, the idf (rack group) is the unique identifier.
With the current constraints the rack names basically have to include the rack group identifier, kinda making it redundant.
The text was updated successfully, but these errors were encountered:
I think it would make sense to alter the rack naming constraint to include the rack groups instead of just the site.
Take for instance a Site thats a single building, but within it it has multiple floors with multiple IDF's per floor. Each IDF is its own rack group, but within each IDF the racks can easily be named quite identically, the idf (rack group) is the unique identifier.
With the current constraints the rack names basically have to include the rack group identifier, kinda making it redundant.
The text was updated successfully, but these errors were encountered: