Configuration tips and tricks: Difference between revisions
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
We've been here: all those acronyms, variable names and definitions may be overwhelming. Colleagues that are not involved in the configuration, may have difficulties userstanding what some else has done. | We've been here: all those acronyms, variable names and definitions may be overwhelming. Colleagues that are not involved in the configuration, may have difficulties userstanding what some else has done. | ||
These guidelines | These guidelines allow all users to dscover the power of nGeniusONE and explore its full potential. | ||
| |
Revision as of 11:58, 9 December 2018
Introduction
We've been here: all those acronyms, variable names and definitions may be overwhelming. Colleagues that are not involved in the configuration, may have difficulties userstanding what some else has done.
These guidelines allow all users to dscover the power of nGeniusONE and explore its full potential.
Solution
Captitals
Type ALL CAPS when configuring nGeniusONE and replace spaces by underscores or hyphens.
Prefixes
Using prefixes allow you to clearly see where a variablesis being used in real-time screens and reports.
Service Configuration
- as_ = Application Service
- ns_ = Network Service
- sh_ = Service Hierarchy
Global Settings
- ls_ = Location Key / Site
- lv_ = Location Key / VLAN
- cc_ = Client Community
- sc_ = Server Community
- tc_ = Telephony Community
- vp_ = VIP
- ap_ = Application
- ag_ = Application Group
Policies
In most cases, people from different teams will assist with the configuration and updating of nGeniusONE.
Even in small teams, it is very important to create a set of rules or guidelines on how to create applications, services etc. so that everybody understands what someone else has done.
It will also prevent duplicates, which only take resources from nGeniusONE without adding more visibility.