1.0.2 Manual Conventions
For navigation, we use this format: Main Tab > Sub-tab > ... > ... >Function. This is shorthand, asking
you to click on the rst level menu level and click on successive levels until you nd the appropriate
page.
An explanatory note. Usually not critical for the normal operation of the system.
A settings note. The note requires your attention, but due to the dierence in browsers or
conguration might not apply for the operation or conguration of the system.
A warning note. The note requires your attention and will aect the way you and other
approved users will use your system.
A danger note. The note requires your full attention and may signicantly aect your system's
integrity, cause electrical damage, data corruption or even a health and safety-related injury.
1.0.3 CMS Conventions
The CMS uses a number of user feedback and help tools to assist you in managing your network:
Hover Help ( ) Hovering over these icons provide extra info on that specic option.
Error/Warning Area If an error or warning is generated by a conguration option, the page
you've attempted to save settings on re-appears with a highlighted
message above the main body of the page.
Save when nished The interface uses a mix of dynamic data entry (for example, automatically
updated input when you click a radio button) and non-dynamic data
entry (for example, text eld entry will not be updated until you click a
Save or Add button). Some pages may have Save buttons scrolled o your
screen.
When you enter text in data elds you will not be automatically prompted
to save changes. This means navigating away from a screen without
saving changes will result in no change to your system.
Save buttons are generally in the bottom right of a page, and may also be
called Add [...], Update [...] or some other relevant call-to-action.
1.0.4 Who is this Document For?
This is the eternal question for a manual: What level of detail is comfortable for you? Too little, and this
manual might as well not exist, or you might feel inadequate to the task. Too much, and attention wanes
from important details, or you may feel we're insulting your intelligence.
The line we drew separates Action from Knowledge, or, things we want you to do, and things we
want you to know. The main body of this manual is all about what you should do to operate the CMS
safely and competently. It tells you where to nd operations or settings, and even briey expands
the enormous number of acronyms used in the Network IT industry. But it does NOT give you best
practice advice, in-depth troubleshooting, or many worked examples on how to deploy ideal or specic
congurations for your network.
There are two reasons for this.
1) Providing specic examples is a security risk to your system. Even if we recommend or indicate
ways to do specic operations (how to create a password, what to name your devices, examples of usual
IP address settings, etc.) we would be subconsciously (or even explicitly) imposing patterns on you that
hackers and other unethical types can take advantage of.
However, we do provide some examples that are fairly basic that everyone in the IT Industry knows or
should know.
2) Use the Glossary. A glossary is about as close as we can come to economically explain what many
terms in this manual mean. If background information was placed behind every option available to you
you'd never get through a site conguration.
