Configuration tips and tricks: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
=== Captitals === | === Captitals === | ||
Type ALL CAPS when configuring nGeniusONE and replace | Type ALL CAPS when configuring nGeniusONE and replace <space> by "_" (underscore). Dynamically assigned names like resolved hostnames and the majority of standard application names are in small letters so you can easily spot the difference. Not using spaces in names is just plain scientific. | ||
| | ||
| Line 16: | Line 16: | ||
=== Prefixes === | === Prefixes === | ||
Prefixes will allow you see where | Prefixes will allow you to clearly see where these variables are used in various real-time and printed reports. | ||
==== Module Service Configuration ==== | ==== Module Service Configuration ==== | ||
Revision as of 06:27, 21 September 2017
Introduction
When you are new to nGeniusONE configuration, all those acronyms variable names and definitions may be overwhelming. It may be usefull to have a few guidelines in order to help you better understand the power of nGeniusONE and discover its full potential.
Solution
Captitals
Type ALL CAPS when configuring nGeniusONE and replace <space> by "_" (underscore). Dynamically assigned names like resolved hostnames and the majority of standard application names are in small letters so you can easily spot the difference. Not using spaces in names is just plain scientific.
Prefixes
Prefixes will allow you to clearly see where these variables are used in various real-time and printed reports.
Module Service Configuration
- as_ = Application Service
- ns_ = Network Service
- sh_ = Service Hierarchy
Module Global Settings
- ls_ = Location Key / Site
- lv_ = Location Key / VLAN
- cc_ = Client Community
- sc_ = Server Community
- vp_ = VIP
- ap_ = Application