Configuration tips and tricks: Difference between revisions
No edit summary |
No edit summary |
||
| Line 40: | Line 40: | ||
=== Policy === | === Policy === | ||
Most likely, colleagues from different departments will be involved during the configuration and updating nGeniusONE. | |||
Even | Even for smaller and multidicipline teams, it is very important to create a set of rules, guidelines and policies on how to create applications, services etc. | ||
It will also prevent duplicate configurations that only take resources from nGeniusONE without adding more visibility. | It will also prevent duplicate configurations that only take resources from nGeniusONE without adding more visibility. | ||
| | ||
Latest revision as of 07:36, 9 May 2019
Introduction
We've all been here: all those acronyms, variable names and definitions may be overwhelming.
These guidelines help users to discover the power of nGeniusONE and explore its full potential.
Solution
Name
Use meaingfull names for naming appliactions,communities, services ... . Use as much as possible UPPER CASE. Don't use space; replace with underscore '_" or hyphen "-".
Prefix
The use of prefix will clarify which varable is used on reports. It allows for easy filtering and alphabetic ordening of longer lists.
Module Service Configuration
- as_ = Application Service
- ns_ = Network Service
Module Global Settings
- ls_ = Location Key of type Site
- lv_ = Location Key of type VLAN
- lr_ = Location Key of type VRF
- cc_ = Client Community
- sc_ = Server Community
- tc_ = Telephony Community
- ap_ = Application
- ag_ = Application Group
Policy
Most likely, colleagues from different departments will be involved during the configuration and updating nGeniusONE.
Even for smaller and multidicipline teams, it is very important to create a set of rules, guidelines and policies on how to create applications, services etc.
It will also prevent duplicate configurations that only take resources from nGeniusONE without adding more visibility.