Configuration tips and tricks: Difference between revisions
No edit summary |
No edit summary |
||
| Line 41: | Line 41: | ||
=== Policies === | === Policies === | ||
In most cases, people from different teams will assist with the configuration and updating of nGeniusONE | In most cases, people from different teams will assist with the configuration and updating of nGeniusONE. | ||
In such cases, it is very important to create a series of rules or guidelines on how to create applications, services etc. so evrybody understands what someone else has done. | |||
It will also prevent the creation of duplicates, which only take resources from nGeniusONE without adding more visibility. | It will also prevent the creation of duplicates, which only take resources from nGeniusONE without adding more visibility. | ||
| | ||
Revision as of 11:52, 9 December 2018
Introduction
When you are new to nGeniusONE configuration, all those acronyms, variable names and definitions may be overwhelming.
These guidelines will assist you 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.
In such cases, it is very important to create a series of rules or guidelines on how to create applications, services etc. so evrybody understands what someone else has done.
It will also prevent the creation of duplicates, which only take resources from nGeniusONE without adding more visibility.