Configuration tips and tricks: Difference between revisions

From wiki.comcert.com
Jump to navigation Jump to search
VisualWikitext
(Created page with " == Introduction == When you are new to nGeniusONE configuration, all acromyms and definitions may be overwhelming.  it may be usefull to follow a few guidelines to help...")
 
No edit summary
 
(28 intermediate revisions by the same user not shown)
Line 2: Line 2:
== Introduction ==
== Introduction ==


When you are new to nGeniusONE configuration, all acromyms and definitions may be overwhelming.  it may be usefull to follow a few guidelines to help you better understand the power of nGeniusONE and discovr its full potential.
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 ==
== Solution ==


=== Prefixes ===
=== 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 "-". 
 
 


==== In module Service Configuration: ====
=== Prefix ===


*
The use of prefix will clarify which varable is used on reports.  It allows for easy filtering and alphabetic ordening of longer lists.
==== AS_ = Application Service ====


*
==== Module Service Configuration ====
==== NS_ = Network Service ====


*
*as_ = Application Service
==== SH_ = Service Hierarchy ====
*ns_ = Network Service  


==== Module Global Settings ====


==== In module Global Settins: ====
*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


*
 
==== LS_ = Location / Site ====


*
=== Policy ===
==== LV_ = Location / VLAN ====


*
Most likely, colleagues from different departments will be involved during the configuration and updating nGeniusONE.
==== CC_ = Client Community ====


*
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.
==== SC_ = Server Community ====


*
It will also prevent duplicate configurations that only take resources from nGeniusONE without adding more visibility.
==== VP_ = VIP ====


*
 
==== AP_ = Application ====

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.

 

Retrieved from "https://wiki.comcert.com/index.php?title=Configuration_tips_and_tricks&oldid=4375"