User guide

How this Document is Organized Document Sections
Telesyn Service Guide (What this Guide Provides)
1-2
This document will focus on the technologies that are used to provide these Services
1.2.2 Document Sections
For each section, there is an explanation of how to engineer, provision, and implement each service. For each
service one or more of the following subsections may be included.
Note: For some services, all of these subsections may not be included since they may not be
relevant for the service; however the first three subsections (Overview, Technology, and
Features) are always included.
• Overview - This provides physical/functional figures of the configuration, allowing the user to see the main
components involved.
• Technology - This lists any relevant standards that are followed and how Telesyn meets those standards.
• Features - This lists the features of the Telesyn that the configuration supports
Note: In some cases the explanation of how a service interacts with the features provide enough
information to allow the user to optimally provision the service.
• Network Engineering - These are the tasks that are done before the components are provisioned (or even
installed), and include traffic modeling as well as formulas that help the provider calculate the maximum or
minimum numbers of components for various configurations. Ideally, the information would help the cus-
tomer optimize a configuration for the following scenarios:
• Telesyn products are providing most if not all of the functionality needed
• Telesyn products are being included in a larger configuration that involves products from many sources
• Hardware Provisioning - This can be divided into two areas:
• Physical - These are the guidelines for cards and cabling.
• Functional - These are the critical parameters that must be data filled with certain values if the models
described in the Network Engineering subsection are to be implemented.
• Software Engineering - This includes the software tools and parameters that allow providers to monitor
what has been provisioned. This would include statistics (performance measurements), audits, statistic
thresholds, test levels, QoS counts, etc.
• Monitor/Maintenance - This would include the logs/messages when components have errors and an expla-
nation of how certain faults or patterns of faults can determine if Hardware Engineering/Provision and Soft-
ware Engineering need to be changed because of these reports.
Note: The CLI will be the primary interface used in these provisioning scenarios. These tasks can
also be done with the Telesyn NMS, and they can be found in the Telesyn NMS User Guide
and Administration Guide.