ATM Vision Operator and Administration Guide


ATM Vision
ATM Vision Operator and Administration Guide
ATM Vision Operator and Administration Guide Contents
Introduction .........................................................................................................................................5
Getting started ....................................................................................................................................6
Software installation ........................................................................................................................6
Hardware installation .......................................................................................................................6
TCP/IP configuration .......................................................................................................................6
Connecting to an ATM Vision system ................................................................................................7
Creating/Editing a target system entry .............................................................................................7
Deleting a target system entry .........................................................................................................7
Accounts..........................................................................................................................................8
Logon ..............................................................................................................................................8
ATM Vision System Configuration .....................................................................................................9
The configuration submenu .............................................................................................................9
General configuration ......................................................................................................................9
Firmware download ....................................................................................................................10
Watchdog timer and remote system reset ..................................................................................10
TCP/IP setup..............................................................................................................................11
Modifying the system's routing table...........................................................................................11
Changing the password and access permission..........................................................................14
Line interface configuration............................................................................................................15
Operation mode .........................................................................................................................15
Local ATM Endsystem Address (AESA)* ....................................................................................15
Selecting the signalling protocol* ................................................................................................17
Configuring Classical IP .............................................................................................................18
Video channel configuration...........................................................................................................19
Changing the name of a video channel ......................................................................................19
Changing the interface default settings.......................................................................................19
Saving changes .............................................................................................................................19
Statistics ...........................................................................................................................................20
Alarm statistics ..............................................................................................................................20
Task statistics ................................................................................................................................21
Line interface statistics ..................................................................................................................22
The video connection database.........................................................................................................23
Creating or modifying system entries .............................................................................................26
Creating or modifying a systems channel entries ...........................................................................27
Saving changes to the database ....................................................................................................27
Creating or modifying connection entries .......................................................................................28
Exporting and Printing of the Database Entries..............................................................................29
Importing Database Entries............................................................................................................29
Permanent Virtual Connections (PVCs).............................................................................................30
Switched Virtual Connections (SVCs)................................................................................................30
Point to Multipoint connections ......................................................................................................30
Setting up video connections.............................................................................................................31
Adding a new connection ...............................................................................................................31
Options .............................................................................................................................................32
Notifications...................................................................................................................................32
Connection ....................................................................................................................................32
Logging .............................................................................................................................................33
Appendix...........................................................................................................................................34
Database example.........................................................................................................................34
System configurations ................................................................................................................34
Connections ...............................................................................................................................34
Entries in the system database...................................................................................................34
Entries in the connection database .............................................................................................35
Classical IP (CLIP) setup ...............................................................................................................37
Setting up CLIP..........................................................................................................................38
Setting up IP connections over PVCs .........................................................................................39
Setting up IP connection by the use of SVCs without ATMARP support......................................39
Setting up IP connection by the use of an ATMARP server ........................................................39
Adaptive clock recovery.................................................................................................................40
NSAP versus E.164 addresses ......................................................................................................41
3
ATM Vision registry entries ..........................................................................................................43

The ATM Vision console ................................................................................................................44
The ATM Vision console commands ..........................................................................................44
Changing the ATM Vision system time .......................................................................................45
Changing the watchdog timeout interval.....................................................................................45
Tools for testing the network configuration .................................................................................45
Testing the hardware .....................................................................................................................49
Trouble shooting............................................................................................................................50
ATM Vision technical description .................................................................................................52
General ......................................................................................................................................52
CPU ...........................................................................................................................................52
System Firmware .......................................................................................................................52
Line Interface Modules ...............................................................................................................53
Video channels...........................................................................................................................56
Acronyms..........................................................................................................................................59
References........................................................................................................................................62
Notes ................................................................................................................................................64
4
ATM Vision Operator and Administration Guide Introduction
Introduction
The program ATMVISION.EXE is the user interface for the ATM Vision system running under
Microsoft Windows NT/Windows 95. The application offers four functional setup to the ATM Vision
user:
1. the configuration of the ATM Vision system including TCP/IP and ATM interworking setup,
2. the administration and maintenance of the ATM connection database,
3. the setup of ATM video connections and
4. the tracking of error conditions, system malfunctions or configuration errors.
5
ATM Vision Operator and Administration Guide Getting started
Getting started
Software installation
Copy the file ATMVISION.EXE from the distribution floppy to your harddisk.
No special directory is recommended.
Hardware installation
Connect a free serial port of your PC or Laptop with port 2 of the ATM Vision system. The
appropriate
cable is supplied.
For the communication between the application and the ATM Vision system a serial connection as
well as a TCP/IP connection1 can be used. The TCP/IP networking allows a centralised management
of multiple ATM Vision systems from a single PC.
TCP/IP configuration
In order to integrate the system into an existing TCP/IP network the pre-configured network
parameters of the ATM Vision system must be modified as follows:
1. Start the application.
2. Choose System/Connect from the main menu.
3. Select the Administrator account from the account list.
4. Leave the password field empty.
5. Press the New system... button.
6. Enter a name for the system. This name is only used for the entry in the system list and has no
additional meaning.
7. Select the serial port to which the ATM Vision system is connected from the serial port list.
8. Press OK.
9. Press OK.
After the connection to the ATM Vision system is established the main window shows the current
system configuration.
10. From the main menu select Configuration/General.
11. In the System Configuration window select the Network page.
Enter the appropriate values for the IP address, the netmask and the default gateway.
Ask your local administrator for the correct values.
12. Press OK.
13. Select System/Disconnect from the main menu.
14. Connect your Ethernet to the AUI port of the ATM Vision system by the use of a transceiver.
15. Reset the ATM Vision system.
Note: The changes to the TCP/IP settings will come into effect only after rebooting the ATM Vision
system.
1
This requires a running TCP/IP protocol under Windows NT/ Windows 95. For information on
TCP/IP protocol installation and configuration please refer to the Microsoft Windows documentation or
ask your system administrator.
6
ATM Vision Operator and Administration Guide Connecting to an ATM Vision system
Connecting to an ATM Vision system

Choosing System/Connect from the main menu opens the Logon Information dialogue.
This dialogue allows the user to specify which ATM Vision system he wants to connect to, which
media to be used for the connection and under which account (Operator or Administrator) the user
wants to logon.
Each ATM Vision system is described by a name and the corresponding IP address and/or serial
port. The connection parameters like IP address and/or serial port number are stored in an local
database and can be selected from the system select box.
Creating/Editing a target system entry

You can add a new or modify an existing system entry by pressing the New system.../Edit system...
button at the lower right corner of the Logon Information dialogue. If the system list is empty or no
system entry is selected the button text is New system.... On selecting an entry the button text
changes to Edit system...
In the New Target System/Edit Target System dialogue choose a unique name for the system, which
will be used as the list index and is displayed in the system select box. Renaming an existing entry
creates a new system entry with the new name.
If you want to use TCP/IP enter the IP address of ATM Vision system, otherwise select the serial port
of the PC to which the ATM Vision system is connected. You can also create a system entry, which
contains both an IP address and a serial port. From the Logon Information dialogue you can choose
between the two possibilities by using the „Logon using serial line“check box.
Deleting a target system entry

In Logon Information dialogue select the entry from the system select box you want to delete.
Press the Edit system... button. In the Edit Target System dialogue press the Delete button.
Confirm the delete by pressing the OK button in the confirmation message box.
7
ATM Vision Operator and Administration Guide Connecting to an ATM Vision system
Accounts
Logging on as Operator allows you to maintain the video connection database and to setup video
connections. As Administrator you will be also able to modify all operational parameters which are
required to integrate the system into your LAN and the ATM network. From both accounts all
configuration and status information are accessible.
Logon
1. Select the target system from the system select box.

2. Select the account you want to be logged on as.
3. Enter the password. For both accounts no password is pre-configured.
4. Press OK
The application now connects to the ATM Vision system retrieving the current configuration and
status information of the system. The different hardware components are displayed in the main
window to reflect the current configuration.
The caption of the window gives the system name, the account used and the instance number of the
application.
The footer gives information on the alarm state of the system, the state of transaction, the system
name and the connection parameters.
Note: As long as multiple user access is disabled only one application can be connected to an
ATM Vision system at a time. If the system is already connected to an application all
incoming request are refused until this connection is closed.
8
ATM Vision Operator and Administration Guide ATM Vision System Configuration
ATM Vision System Configuration

Configuration parameter can only be changed by the Administrator.
The configuration submenu
The Configuration sub-menu contains entries for all logical devices attached to the system.
The top most entry always points to the general or system configuration.
The second entry points to the configuration of the first network or line interface, followed by all video
transmitter channels (Video à ATM) and the video receiver channels (ATM à Video) attached to this
line interface.
If the ATM Vision system contains more than one line interface the entries for the interfaces and the
attached video channels are appended to the configuration menu in the same manner. The video
interfaces are listed by synonyms, which can be assigned by the administrator, i.e. describing the
equipment or location attached to this channel.
An example of the resulting sub-menu structure is shown below:
General configuration
The General configuration contains all parameters which apply to the entire system. Most of the
parameters have a pre-configured value which can not be modified. The Firmware and CPU pages
contain vendor and product information, the Network and Security pages configuration parameters for
networking and accounting.
9
Firmware download
The application offers the opportunity to upgrade the firmware of the ATM Vision System. If the
application was started with the command line parameter /D (ATMVISION.EXE /D) the Download
button on the Firmware page becomes visible. In order to upgrade the ATM Vision firmware press the
Download button and select the file containing the firmware from the file selection dialogue.
After the file is loaded the transfer of the firmware to the ATM Vision system starts. The transfer can
be stopped by pressing the Abort button. After the transfer is completed and before the firmware is
stored to the ATM Vision system Flash memory you will be ask to confirm this operation. After
confirmation the application will disconnect. The programming of the Flash memory will take less than
10 seconds.
Watchdog timer and remote system reset
If you are logged on under the administrator account you can enable/disable the system's watchdog
timer. The watchdog timer is an interval timer, which causes a system reset on timer expire. In order
to prevent from timer expire the system firmware reinitialises the timer after half the timeout period.
If the firmware runs into a fatal condition, which will cause the system to hang, the watchdog timer
expires and a system reset will be performed. For information on how to configure the watchdog
timeout period please refer to chapter Changing the watchdog timeout interval, page 45.
The Reset button located on the CPU page allows you to perform a remote system reset.
10
TCP/IP setup
Select the Network page from the System Configuration dialogue.
Modify the IP address and netmask to appropriate values in the dotted address format
(aaa.bbb.ccc.ddd).
Enter the address of the default gateway to be used for connections with targets outside the LAN or
0.0.0.0 for none.
Modifying the system's routing table

Under certain conditions, i.e when using inband Classical IP it will be necessary to modify the
system's routing table by adding static routing entries. Pressing the Routes... button a window will get
opened displaying the contents of the system's routing table.
In this example the IP address of the Ethernet interface is configured to 192.168.2.101, the IP address
of the ATM interface is configured to 192.168.5.4 and the host with the IP address 192.168.2.1 is
selected as the default gateway.
The first entry specifies the local loopback (lo0). This entry is created automatically by the system
firmware. The second entry defines the machine with IP address 192.168.2.1 as the default gateway
accessible by the Ethernet interface (eth0). This entry will be created as far as in the TCP/IP
configuration a default gateway is specified. The third entry is the route to the network 192.168.2.0
accessible via the Ethernet interface. This entry is created automatically by the system firmware if a
IP address is assigned within the TCP/IP configuration. The forth entry is the route to the Classical IP
network 192.168.5.0 accessible by the ATM interface (atm0). The last entry specifies a indirect route
11
to the network 192.168.6.0 accessible via the gateway 192.168.5.5 located on the Classical IP
network.
A route entry can be removed from the system's routing table by selecting the routing entry and
pressing the Delete button.
By pressing the New.. button a dialogue is opened which allows you to add a static route entry to the
system's routing table.
The IP address of the host or the network must be entered into the field Target. The field Gateway
must contain the IP address of a host, which is located on a network directly accessible via one of the
IP interfaces (eth0 or atm0) and acts as the gateway to the specified target.
The entries of the routing table are stored permanently and will be initialised automatically after a
system reboot or power on.
Modifying the system's ATMARP table
For the purpose of mapping a IP address to an ATM Endsystem Address and wise versa in a
Classical IP network a mechanism comparable to ARP (Address Resolution Protocol) called ATMARP
is used.
It requires a ATMARP server running on the network. If the network does not provide this service or a
PVC shall be used for a IP connection a manual configuration of the ATMARP table of the system is
required. Pressing the ATMARP... button a window will get opened displaying the entries of the
system's ATMARP table.
The example shows a manual configured (static) ATMARP entry for the IP address 192.168.5.5 and
the corresponding ATM Endsystem Address. ATMARP entries retrieved via the ATMARP server are
marked as dynamic.
A entry of the ATMARP table can be deleted by selecting the entry and pressing the delete button.
An active ATM connection to the target will be closed at this time.
In order to add an entry to the system's ATMARP table press The New button.
Enter the host's IP address in the IP address field, select the appropriate ATM address format and
enter the ATM address. Pressing the Apply button will add the entry to the ATMARP table. In case of
a PVC connection (address format is PVC) the connection will be activated immediately. In case of a
SVC connection the connection will be established by the first outgoing IP packet for the selected IP
address or by an incoming connection from the host, this address is assigned to.
In case of PVC connections or if the network does not provide an ATMARP server the ATMARP
entries must be configured at both endpoints of the connection.
12
The example above will create a PVC connection on VPI 0, VCI 62 to the host 192.168.5.6.
In order to provide addressing across a public ATM network where only the E.164 address scheme is
supported the ATMARP entry may include a ATM Endsystem Subaddress (AESSA). Address
translation will be performed by the egress switch of the public network. See chapter NSAP versus
E.164 addresses, page 41 for further details.
13
Changing the password and access permission

Select the Security page from the System Configuration dialogue.
As Administrator you can select the account for which you want to change the password from the
account select box. You can also permit logon of multiple users using the Operator account at the
same time. By default this option is disabled. In order to enable the concurrent access of multiple
users check the field Enable multi user logon.
Note: All users connected to a system at the same time will get all the status information. They all
are permitted to establish and release connections, even if this connection is under the
responsibility of someone else.
As Operator you are only allowed to change the password of the Operator account. Press the Change
button. In the Change Password dialogue enter the new password and retype it in the confirmation
box. The Administrator also can permit Press OK.
14
Line interface configuration

Each line interface attached to the system has its own configuration window accessible through the
corresponding entry in the Configuration sub-menu.
Operation mode
Select the General page from the Line Interface Configuration dialogue. The operation modes you
can select from the mode select box depend on the type of the line interface.
The following table shows all modes and the default value for the different interface types.
Interface Type Mode Default

STM-1/STS-3c SONET
SDH x
G.703 E1 ADM x
PLCP
G.703 E3 G.832 ADM x
G.751 ADM
G.751 PCLP
T1 ADM x
PLCP
T3 CBIT ADM x
CBIT PLCP
M23 ADM
M23 PLCP
Local ATM Endsystem Address (AESA)*

Each line interface represents a link to a private or public network. The connection setup between two
end-systems across these networks can be performed via network management (Permanent Virtual
Connection or PVC) or a signalling protocol (Switched Virtual Connection or SVC).
For PVCs a fix VPI/VCI pair is assigned to the ATM cells and the route through the ATM network is
manually configured. Therefore, for this kind of connection setup no additional address information is
required.
Using SVCs (Switch Virtual Connection) a connection is established by passing the ATM address of
the target system and parameters specifying the required bandwidth and quality of service (QoS) to
15
the network. In order to identify the initiator of a connection at the target end-system the local ATM
address is enclosed in the setup message.
In order to ease the network administration for private networks a protocol called ILMI (Interim Local
Management Interface) is defined, which allows the automatic assignment of ATM addresses to end-
systems, also called address registration. To avoid configuration conflicts the ILMI address
registration should be used, if it is supported by the network. Please ask your local ATM administrator
for details.
Select the ATM Address page from the Line Interface Configuration dialogue.
If the ATM Vision system is connected to an ATM network, which does not support signalling, choose
None from the address format select box.
If the system is connected to a private network supporting the ILMI protocol select the automatic
address registration by activating the check box in lower left corner. Otherwise select the appropriate
address format from the select box and enter the local ATM end-system address of the ATM Vision
system.
16
Selecting the signalling protocol*

The ATM Vision system supports the signalling protocols according to UNI 3.01, UNI 3.11, UNI 4.01
and Q.29311. For each line interface a different protocol can be selected.
In order to change the signalling protocol for a line interface select the Signalling page from the Line
Interface Configuration dialogue.
Select the signalling protocol, which you want to use and which is supported by the network.
Enable point to multipoint connections for this link, if required.
Select the CPCS mode to be used. The CPCS (Common Part Convergence Sublayer) is a protocol,
which ensures secure data transfer for the signalling protocol. The CPCS protocol is initiated by the
active side, while the passive side awaits an incoming CPCS connection. The CPCS mode must
match the switch setting to which the system is connected. Configuring both the end-system and the
switch to active or passive CPCS will lead to network malfunction. Under normal conditions the end-
system must be configured as the active side.
The ATM Vision system firmware supports the ILMI 3.0 and ILMI 4.0 protocol for address registration
in private networks.
Select the ILMI protocol version, which is supported by the network.
Note: The ILMI protocol is only enabled, if ILMI is configured to be used for the retrieval of the local
AESA. (See previous chapter).
*
Signalling option only
1
Additional license required
17
Configuring Classical IP
The ATM Vision System provides Classical IP for in-band control and monitoring. Dependent on the
hardware configuration at least four channels for IP connections at a max. speed of 770Mbit/s are
provided.
In order to enable CLIP on an ATM interface an IP address for this interface must be provided. All
members of the CLIP network must have the same network address. The MTU (Max. Transfer Unit)
can be configured in order to adapt to the requirements of the network. All members of a CLIP
network must use the same MTU.
If the network provides an ATMARP server, which allows dynamic address resolution the IP address
of the ATMARP server can be entered in the appropriate field. In order to enable a connection setup
between the ATM Vision System and the ATMARP server an entry for this IP address must be added
to the system's ATMARP table as described in the chapter TCP/IP setup, page 11.
For security reasons a forwarding of TCP/IP packets towards the Ethernet port of the system can be
disabled. If IP packets should be routed over the CLIP network towards the network attached to the
Ethernet port of the ATM Vision system, IP forwarding must be enabled. By default this option is
disabled.
The chapter Classical IP (CLIP) setup, page 37, gives a description on the CLIP configuration needed
to run a sample network.
18
Video channel configuration

Select the ATM Address page from the Line Interface Configuration dialogue.
Changing the name of a video channel

The name of a video channel is only used as entry for the video channel in the Configuration and the
Status sub-menu. You can select any name up to 20 characters to identify a video channel. A good
choice is to use names describing the equipment and/or the location attached to the channel.
Changing the interface default settings

Each video channel requires a set of configuration parameter, which depends either on the hardware
installation or the network characteristics.
Using serial video interfaces the attenuation or the length of the cables, which are used to connect the
video interface to the video codec, can be specified to adjust input and output levels.
Note: The use of a wrong cable length parameter can lead to transmission errors.
In order to restrict the use of AAL1 FEC (Forward Error Correction) for this channel, deselect the FEC
checkbox. Now only video connections without FEC will be accepted. This feature may be required if
third party ATM products are used as peer of the video connection, which doesn't support AAL1 FEC.
The CDV parameter is used as the default value for the Peek-Peek CDV measured in the network
when using switched connection establishment due to the limitations given by the signalling protocols.
Using permanent connections this parameter is replaced by the CDV value passed to the system
during the connection setup. For further information refer to chapter Adaptive clock recovery, page 37.
For receiving channels (ATM à Video) the Frequencies page shows the frequencies of the installed
VCXOs (Voltage Controlled Cristal Oscillator). For video interfaces with a specific frequency, i.e.
G.703 E3, only one VCXO is installed. Otherwise the video frequencies, which can be recovered by a
channel, can be calculated according to:
VCXO
Freq rec = k
, w ith 1 ≤ k ≤ 6 a n d 0 ≤ n ≤ 6
2n
Note: VMB-2.0 boards support a frequency range from 1.5MHz to 132MHz.
Saving changes
By pressing the OK or Apply button the modified configuration is sent to the ATM Vision system and
will be confirmed by an update of the configuration information in the application window.
OK closes the configuration window immediately while Apply leaves the configuration window open,
so you can review the changes you have made. Pressing Cancel discards all changes made.
19
ATM Vision Operator and Administration Guide Statistics
Statistics
For several system components statistic information can be collected.
Alarm statistics
The alarm list contains at maximum the last 512 alarms occurred on the system.
For each alarm the following information is displayed:

1. The type of alarm:
Red: FATAL ERROR
Yellow: WARNING
Blue: INFORMATION
2. The cause for the alarm
3. The code assigned to this alarm (presented also at the alarm relay contacts)
4. The time when the alarm occurred
5. The time when the alarm condition was cleared
Alarms, which are already cleared, can be hide by selecting Active alarms only.
For documentation purpose the alarm history can be stored to a text file by pressing the Save...
button.
Pressing the Clear button will delete the alarm list stored on the system. In order to retrieve the actual
alarm list press the Refresh button.
20
Task statistics
Task statistics are useful to estimate the system performance. They are displayed on the page
Processes in the System Statistics window.
For each task running on the system an entry is displayed consisting of:
1. The task name
2. The task ID
3. The priority at which the task runs
4. The current state of the task
5. The CPU time used by the task
6. The stack size
7. The size of the current unused stack
8. The minimum free stack size
The task statistics can be updated by pressing the Refresh button.
21
Line interface statistics

For each line interface statistics can be collected, which includes the error statistics and the status of
the physical interface i.e STM-1 or E3/DS3 and ATM cell statistics. In order to start the measurement,
press the Start button.
Under the current status a green LED indicates an error free operation, while a red LED indicates that
an error has occurred during the last measurement period (1 second). A yellow LED under history
indicates that during the whole measurement at least one error has occurred.
The LEDs in the transmit and receive section will become green if during the last measurement cells
were sent or received.
In order to clear the statistics during a measurement press the Clear button. The measurement can be
stopped by pressing the Stop button.
22
ATM Vision Operator and Administration Guide The video connection database
Video channel statistics

The ATM Vision system provides powerful statistics gathering for all active video channels. For each
channel the statistics can be switched on or off on demand. In order to switch on the statistics select
the channel from the Statistics menu. The window Clock Recovery Statistics is displayed. Switch on
the statistics gathering by pressing the Start button. The process can be stopped at any time by
pressing the Stop button.
For the active connection the values for the recovered bitrate and the output buffer level are collected
and minimum and maximum values within the measurement period are displayed. These counters
can be cleared at any time. You can switch to a graphical presentation of the measurements by
pressing the Graph button.
The curves for different measurements can be displayed:

Bitrate: the bitrate, which is recovered by the ATM Vision system. Please mention that the
figures for the recovered bitrate is a relative value related to the internal reference
clock of the ATM Vision system. So the absolute value may differ from the one given
by the measurement.
FIFO Level: the output buffer level of the ATM Vision system
Delta: the difference between expected data rate and received amount of data over the ATM
network. This curve directly represents the CDV on the network.
When using AAL1 FEC additional the statistics of the Forward Error Correction are reported. These
counters represent the number of events since the connection started. The counters can be cleared
only by dropping the connection.
23
The video connection database
In order to configure and/or monitor several ATM Vision systems multiple instances of the
application can be started. Changes committed to the system and connection database are
transparent to all applications. Access to the database requires no connection to the ATM Vision
system.
The video connection database is divided into two parts:

1. the system database containing address and channel information of end systems representing the
peer of a video connection and
2. the connection database containing connection parameters combined with references to the
system database.
The figure below shows the structure of the system and the connection database and their
relationship.
Figure 1: The structure of the system and the connection database
The system database can best be compared with a private phone book: each system (exchange) is
described by a unique name, its ATM addresses (phone number) and the video channels (extensions)
attached to the system. Each video channel is described by a name, which is unique for the system it
is attached to, its mode (transmitter or receiver) and a unique number called selector.
Note: If an ATM Vision system is equipped with more than one line interface each line interface
and its attached video channels are treated as a single system and requires its own system entry.
24
25
A video connection requires a set of transfer parameters, i.e. the video bit-rate, specifying the data-
rate of the connection. The connection entries now combine the transfer parameters with a single
channel of a target system. For channels supporting variable bit-rates, like DVB, several connections
can be defined using different transfer parameter.
The chapter „Database example", page 59, explains on the basis of sample configurations how to set
up the video connection database.
Creating or modifying system entries

Select Database/Systems from the main menu.
Select the page Systems from the System Database dialogue.
To create new system entry one of the following methods can be used:
1. In order to create a new system entry, press the Add button.
2. If you want to work from an existing entry select the entry in the system list box and press the
Add button. All information of the selected entry except its name is copied to the new entry.
In order to modify an existing system entry select the entry from the system list box and press the Edit
button.
In the System Address dialogue specify a unique name to be used for system identification.
Select the AESA (ATM Endsystem Address) format from the select box.
In the case that either the system or the network does not support signalling choose None.
Using SVCs address translation may be required, because the ATM Vision system can be either
connected to a public or a private network. This depends on the location of the target system as well
as on the location of the initiator of a connection setup in the network. The following table lists all
possible configurations and the corresponding selections for the address formats.
Initiator connected to Target connected to AESA format AESSA format

private network public network private network public network
unspecified • E.164 NONE
• • NSAP NONE
• • E.164 NSAP
unspecified • E.164 NSAP
If the target system is connected to a private network the address formats depend on the location of
the initiator. If the location of the initiator is unspecified (see last line in the table) the initiator decides
depending on its local address format, which addresses to be used in the setup message. For further
information of the different address formats refer to chapter NSAP versus E.164 addresses on page
59, or ask your local ATM administrator for the valid addresses.
If an address format other than None is selected for the AESA and/or AESSA (ATM Endsystem
Subaddress) enter the address in the corresponding address fields.
Press OK to accept or Cancel to discard the changes you have made.
In order to delete a system entry select the entry from the system list box and press the Delete button.
26
Creating or modifying a systems channel entries
If a system entry is selected the Channels page becomes accessible showing a list of all video
channels attached to the system.
The channel entries are handled in the same manner as described for the system entries.
In the System Channels dialogue enter a name identifying the channel. This name must be unique for
the selected system. Select the channel’s mode. A transmitter converts its video input into ATM cells
and transfers it to a receiver, which converts the received ATM cells back into video data. Select the
video interface type of the system channel.
Enter a selector value, which must be unique for the selected system.
Note: For SVCs the selector is added to the systems ATM address to address the single channel.
Although the selector has no special meaning when using PVCs for compatibility reasons it
must be specified.
Press OK to accept or Cancel to discard the changes you have made.
Saving changes to the database

Pressing OK or Apply stores all changes in the database. Pressing Cancel discards all changes since
the last save.
27
Creating or modifying connection entries

Select Database/Connections from the main menu.
To create a new empty connection entry, press the Add button in the Connection Database dialogue.
If you want to work on an existing connection entry select the connection entry from the connection
list box before pressing the Add button. In order to modify an existing connection entry select the
entry from the connection list box and press the Edit button.
In the New Connection dialogue enter a unique name, which identifies the connection.
Select the destination system and the system’s channel. Dependent on the channel type (transmitter
or receiver) the title of the dialogue changes between Outgoing connection to and Incoming
connection from.
If a channel with a fix frequency video interface, i.e. G.703 E3, is selected the video frequency is
inserted automaticly. For variable frequency interfaces, i.e. DVB SPI the video data rate to be
transmitted or received must be specified. Enter the maximum peak to peak CDV (Cell Delay
Variation) which is to be expected for this connection. Please ask your network administrator for
further details.
Select whether or not AAL1 FEC (Forward Error Correction) should be used at the ATM level. The use
of AAL1 FEC allows the recovery of ATM cells, which have been discarded by the ATM network.
For the DVB SPI interface the European standard CENELEC EN 50083, Part 9 describes three
modes for transmitting or receiving MPEG-2 data as transport packets:
1. a 188 byte packet structure,
2. a 204 byte packet structure with 188 bytes MPEG data and 16 bytes error correction data or
3. a 204 byte packet structure with 188 bytes MPEG data and 16 dummy bytes
The ATM Vision DVB SPI supports all three modes. The packet structure is detected automatically.
For 204 byte packets the information, if the 16 bytes contain error correction data or not, must be
supplied to the receiving side. For connections established at the receiving side select the MPEG TS
FEC switch according to the expected packet format. For incoming connections the default handling
of 204 byte packets must be specified by the channels configuration.
Note: If the MPEG packet structure is unknown switch off the MPEG TS FEC.
In order to set up a PVC activate the Permanent switch and enter the values for the VPI and VCI in
the VC fields. The Permanent switch is automatically activated if the selected system has no ATM
address defined.
Press OK to save or Cancel to discard the changes you have made.
28
Exporting and Printing of the Database Entries

In order to export or print the system and connection database entries select Export or Print from the
Database menu. The dialogue Database Export will be opened.
The tree on the left shows all system entries and their related channels and video connections
contained in the local database. If one entry gets selected the parameters of this entry are shown in
the right box. All entries contained in the tree will be exported or printed. In order to exclude all
connection entries deselect the check box below the tree view. In order to exclude specific entries,
select the entry to exclude and press the Delete button. The selected entry will be removed from the
tree view. When the tree only contains these entries which you want to export or print press the Done
button. You will be prompted for a file name or the printer to be used.
Importing Database Entries

In order to import database entries from a ATM Vision database file select Import from the Database
menu. After you have been prompted for the filename the Database Import dialogue will be opened.
The tree on the left shows all entries found in the database file. You can exclude connection entries
from being imported to the local database by disabling the check box below the tree view. Existing
entries of the local database will only be modified if the check box Modify existing Entries is selected.
Otherwise duplicate entries are skipped.
29
A protocol of all actions which will be performed during the import are written to the Database Import
Log. The changes are only made to the local database if you press Apply. Pressing Undo will discard
all changes.
Permanent Virtual Connections (PVCs)

The use of PVCs always requires two entries in the connection database, one for the transmitting and
one for the receiving side of the connection.
For the transmitting side select the destination system and channel to which the video data should be
sent. The VPI and VCI values specify the VC to be used at the transmitting side. On the receiving
side select the source system and channel from which the video data should be received. The VPI
and VCI values specify the VC on which the video data will be received at the receiving side.
Across a network the VPI and/or VCI values may change because of the switches internal routing
tables, so different values for the VPI and/or VCI may be required for the two entries. If the transmitter
is directly connected to a receiver the VPI and VCI values must be the same at both sides.
Switched Virtual Connections (SVCs)

Using SVCs only one entry in the connection database is required. Video connections can be
established in both directions, so the initiator can establish a connection to send a video stream to as
well as to receive a video stream from a remote system. Bi-directional connections can be established
by defining two entries in the connection database, one for each direction. These connection can be
switched independent from each other.
Point to Multipoint connections

The ATM Vision system also supports point to multipoint connections. In order to transmit the same
video stream to different locations or channels add entries to the connection database, which only
differ in the selected system and/or channel, but use the same transfer parameters. These
connections can be established or closed independent of each other.
30
ATM Vision Operator and Administration Guide Setting up video connections
Setting up video connections

Logon to the ATM Vision system as described in chapter Connecting to an ATM Vision system,
page 7.
Select the local channel for which you want to establish a connection by clicking on the corresponding
video port in the bitmap or select it from the status menu.
The connection list box in channels status window contains information on all connections, which are
currently established for this channel. Only for a transmitter, which supports point to multipoint
connections and also initiates the connection setup, multiple connection with the same transfer
parameters but different targets can be established at a time. Connections initiated by a remote
system are listed as well as connections initiated by the local channel.
The transfer parameters are shown in the status bar below the connection list box. The status LED in
left lower corner reflects the state of the video input/output:
LED colour Transmitter Receiver

GRAY Channel is idle, no connection is established
RED No video input detected. No ATM cells are received on the selected VC.
YELLOW Video input frequency too high. ATM cells are received. Video output available.
GREEN Video input detected. ATM cells are transmitted. Clock recovery has locked.
Adding a new connection

New connections can only be established under one of the following conditions:
• The channel is not in use yet, there are no active connections for this channel, or
• the channel is a transmitter supporting point to multipoint connections and the active connections
are initiated by this channel.
In order to establish a new connection press the Add button.
The list box of the Add Connection dialogue contains all connection entries of the connection
database which match the local channel’s configuration, i.e. for a transmitter only those connections,
which refer to a receiving channel of the same video interface type, are displayed.
Note: The use of variable frequency video interfaces, i.e. DVB, at the transmitter side permits any
video data rate to be transmitted. At the receiving side only discrete frequencies dependent
on the hardware configuration can be recovered. It is in the responsibility of the user to select at
the transmitter side only those connections with a video data rate supported by the receiver.
In order to release an established connection select it form the list box and press the Release button.
31
ATM Vision Operator and Administration Guide Options
Options
There are a few options, which allow you to modify the behaviour of the application.
From the main menu selectOptions/Properties.
Notifications
From the notification box you can select, whether or not a warning should be displayed, if connections
are active for longer than a user specified period. The connection itself is not affected by this
mechanism.
By the use of the second and third option the application can be forced to open the channel status
window, when a change to the channel status takes place, or a connection is established by a remote
side.
Connection
Normally a connection failure between the application and the ATM Vision system can only be
detected if messages are sent to the ATM Vision system, i.e. caused by a connection setup or
configuration changes. In order to detect a break down of the connection between the application and
the ATM Vision system the application can be forced to transmit keep alive messages to the ATM
Vision system. Using keep alive message, a connection failure will be detected in between the next
minute.
Note: Using keep alive messages in combination withdial-in networking the dial-in connection will
become permanent established.
By default all options are disabled.Pressing the Apply button will store the options permanently.
The settings are loaded each time the application is started.
32
ATM Vision Operator and Administration Guide Logging
Logging
For easier detection of a malfunction or a configuration errorthe application can collect debug
messages from the ATM Vision system.
In order to switch on the logging selectOptions/Logging from the main menu.
Press the Options button and select from the Logging Options window the mo
dules, for which the
logging should be enabled and how verbose the logging should be
.
Selecting a high verbositylevel all messages of the lower levels are included.
Note: The logging can affect the system performance. Choosing a high verbosity in combination
with multiple modules selected at a time can lead to system malfunction.
The log messages are subject to change. For further information on the different logging
options please refer to the sample log filein the appendix or contact the ATecoM support line.
In order to inspect the logthe capture process can be paused by pressing the Pause button. All further
messages are captured in the background and will become accessible when pressing thePause
button again. In order to discard all messages received yetpress the Clear Log button.
The captured messages can also be stored to a file by pressing theSave to... button.
The Close button only closes the logging window while the capture processkeeps active as long as
message buffer are available on the local PC.
Note: The logging can only be switched off by setting the verbosity in the option window to off or by
disconnecting from the ATM Vision system.
33
ATM Vision Operator and Administration Guide Database example
Appendix
Database example
This chapter describes the video connection database setup on the basis of sample scenario.
Three systems will be configured to transfer video data via PVCs and SVCs.
System configurations
System #1 (Location A):
Line interface: STM-1 Monomode 155 Mbit
Local party no.: E.164, 4924079586
No. of video channels: 2
Video channel #1:
Selector: 1
Video interface: DVB
Oscillators: 20 MHz, 24 MHz
Video channel #2:
Selector: 2
Video interface: E3
Oscillators: 34.368 MHz
System #2 (Location B):
Line interface: STM-1 Monomode 155 Mbit
Local party no.: E.164, 49615187231
Video channel #1:
Selector: 1
Video interface: DVB
Oscillators: 20 MHz, 24 MHz
System #3 (Location C)
Line interface: PDH E3 34.368 Mbit
Local party no.: E.164, 4910089318
Video channel #1:
Selector: 1
Video interface: E3
Oscillators: 34.368 MHz
Connections
Entries in the system database

We start by adding a complete description of all systems and their video channels to the system database. The database afterwards
contains the following entries:
System #1:
Name: System-1, AESA: E.164, 4924079586 AESSA: None
Channels:
Name: MPEG-Encoder, Type: Transmitter, Selector: 1
Name: MPEG-Decoder, Type: Receiver, Selector: 1
Name: ETSI-Encoder, Type: Transmitter, Selector: 2
Name: ETSI-Decoder, Type: Receiver, Selector: 2
System #2:
Channels:
Name: MPEG-Encoder, Type: Transmitter, Selector: 1
Name: MPEG-Decoder, Type: Receiver, Selector: 1
System #3:
Channels:
Name: ETSI-Encoder, Type: Transmitter, Selector: 1
Name: ETSI-Decoder, Type: Receiver, Selector: 1
The system database can be use as a common database for all the three systems.
34
Entries in the connection database

We start adding the connection entries required by system #1 to the connection database:
1. Connection: SVC from System #1, TRM #1 to System #2, RCV #1 with 20Mbit video rate.
Connection #1:
Name: System-1 à System-2 DVB
System: System-2
Channel: MPEG-Decoder
Video Frequency: 20 MHz
FEC: Yes
Permanent: No
2. Connection: SVC from System #1, TRM #2 to System #3, RCV #1 with 34.368 Mbit video rate.
Connection #2:
Name: System-1 à System-3 ETSI
System: System-3
Channel: ETSI-Decoder
Video Frequency: 34.368 MHz
FEC: Yes
Permanent: No
3. Connection: PVC fromSystem #2, TRM #1 to System #1, RCV #2 with 10 Mbit video rate.
Connection #3:
Name: System-1 ß System-2 DVB PVC
System: System-2
Channel: MPEG-Encoder
FEC: Yes
Permanent: Yes VC 1, 10
The connection database should look like shown below:
The entries in the connection database always contain the transfer parameters and the peer of the connection.
The initiator of the connection, one of the local channels, is defined during connection setup by selecting a channel
and assigning a
connection entry it.
35
Now we add the connection entries required by system #2 follow:
3. Connection: PVC from System #2, TRM #1 to System #1, RCV #1 with 10 Mbit video rate.
Connection #4:
Name: System-2 à System-1 DVB PVC
System: System-1
Channel: MPEG-Decoder
FEC: Yes
Permanent: Yes VC 1, 10
Finally the connection entries required by system #3:
4. Connection: SVC from System #3, TRM #1 to System #1, RCV #2 with 34.368 Mbit video rate.
Connection #5:
Name: System-3 à System-1 ETSI
System: System-1
Channel: ETSI-Decoder
Video Frequency: 34.368 MHz
FEC: Yes
Permanent: No
The connections can be stored in one database common to all systems or in individual databases one for
each system. Then the
database for system #2 contains only the entry connection #4 and the database for system #3 the entry connection #5.
36
ATM Vision Operator and Administration Guide Classical IP (CLIP) setup
Classical IP (CLIP) setup

The following examples will refer to the sample network configuration shown below.
Three ATM Vision systems at different customer sides are connected to an ATM network building up
a CLIP network. The CLIP network address is assumed to be 192.168.5.0 with a netmask of
255.255.255.0 (Class C) allowing up to 254 hosts to be connected to this ne
twork.
The LAN (Local Area Network) of customer 1 has a network address of 192.168.2.0 with a netmask of
255.255.255.0.The network address of the LAN of customer 2 is 192.168.6.0 with a netmask of
255.255.255.0.
The third ATM Vision system has no connection to a customer network via it's Ethernet interface.
Common to all configurations are the routing entries required by the workstations attached to the
different customer LANs.
Routes to be configured atCustomer LAN 1, Gateway 1:

192.168.5.0 192.168.2.101 255.255.255.0 eth0
192.168.6.0 192.168.2.101 255.255.255.0 eth0
Note: Workstation 1 does not need any additional routing information in case that Gateway
1 is it's default gateway.
Routes to be configured atCustomer LAN 2, Workstation 1:

192.168.5.0 192.168.6.1 255.255.255.0 eth0 or
37
0.0.0.0 192.168.6.1 0.0.0.0 eth0
Setting up CLIP
Configuration of ATM Vision 1:
Configuration/LineInterface/Clip:
IP address: 192.168.5.4
Netmask: 255.255.255.0
MTU: 9180
ATMARP: 0.0.0.0 (192.168.5.1 if the ATMARP service is providedby the network)
IP forwarding: Yes
Configuration/General/Network:
IP address: 192.168.2.101
Netmask: 255.255.255.0
Default Gateway: 192.168.2.1
Routes: Target Gateway Mask Interface Type

127.0.0.1 127.0.0.1 255.0.0.0 lo0 dynamic
0.0.0.0 192.168.2.1 0.0.0.0 eth0 dynamic
192.168.2.0 192.168.2.101 255.255.255.0 eth0 dynamic
192.168.5.0 192.168.5.4 255.255.255.0 atm0 dynamic
192.168.6.0 192.168.5.5 255.255.255.0 atm0 static

IP address: 192.168.5.5
Netmask: 255.255.255.0
MTU: 9180
ATMARP: 0.0.0.0 (192.168.5.1 if the ATMARP service is provided by the network
)
IP forwarding: Yes
IP address: 192.168.6.1
Netmask: 255.255.255.0

127.0.0.1 127.0.0.1 255.0.0.0 lo0 dynamic
0.0.0.0 192.168.5.4 0.0.0.0 atm0 dynamic
192.168.5.0 192.168.5.5 255.255.255.0 atm0 dynamic
192.168.6.0 192.168.6.1 255.255.255.0 eth0 dynamic

IP address: 192.168.5.6
Netmask: 255.255.255.0
MTU: 9180
ATMARP: 0.0.0.0 (192.168.5.1 if the ATMARP service is provided by the network)
IP forwarding: No
IP address: 0.0.0.0
Netmask: 255.255.255.0

127.0.0.1 127.0.0.1 255.0.0.0 lo0 dynamic
0.0.0.0 192.168.5.4 0.0.0.0 atm0 dynamic
192.168.5.0 192.168.5.6 255.255.255.0 atm0 dynamic
192.168.6.0 192.168.5.5 255.255.255.0 atm0 static
Note: All routing entries of type static must be added manually to the system's routing table.
Additional tools for verifying and testingthe network setup of the ATM Vision system are available via
the console. Please refer to chapterTools for testing the network configuration on page 45 for
additional information.
38
Setting up IP connections over PVCs

The ATM Vision System supports in-band IP connections evenif the ATM network does not support
signalling. For each IP connectiona bi-directional PVC must be configured by the network
management. At both endpoints of the connectiona corresponding ATMARP entries must be
provided:
ATMARP table of ATM Vision 1:

192.168.5.5 PVC VPI 0, VCI 62 static


Setting up IP connection by the use of SVCs without ATMARP support

The following exampleassumes that the network prefix for all the three ATM Vision systems is
0x45.004924195864214F.0000.0000, which implies thatthey are all connected to the same switch.
The ESIs of the three ATM Vision systems are assigned in the following manner:
ESI of ATM Vision 1: 0000000001

192.168.5.5 SVC 0x45.004924195864214F.0000.0000.000000000002.00 static
192.168.5.6 SVC 0x45.004924195864214F.0000.0000.000000000003.00 static

192.168.5.4 SVC 0x45.004924195864214F.0000.0000.000000000001.00 static
192.168.5.6 SVC 0x45.004924195864214F.0000.0000.000000000003.00 static

192.168.5.4 SVC 0x45.004924195864214F.0000.0000.000000000001.00 static
192.168.5.5 SVC 0x45.004924195864214F.0000.0000.000000000002.00 static
Setting up IP connection by the use of an ATMARP server

If an ATMARP server is provided by theATM network, no static ATMARP entries must be configured
at all.
Please refer to the chapterThe ATM Vision console, page 44 ff for additional tools for testing the
network configuration of theATM Vision system.
39
ATM Vision Operator and Administration Guide Adaptive clock recovery
Adaptive clock recovery

The ATM Vision system is designed for the transport of high quality video data over an ATM network.
At the transmitting end the video stream (analogue or digital) is packed into AAL1 ATM cells and sent
over a dedicated VC (virtualchannel) towards the receiving end. At the receiving end the frequency
or bit-rate of the video stream is recovered by an adaptive clock recovery. In contrast to the SRTS
method (Synchronous Residual Time Stamp) no common network clock is required.
In comparison to circuit emulation, which offers a leased line to the service user, the quality of the
recovered clock, must fulfil the much stricter requirements of the PAL and MPEG specifications.
Parameter PAL MPEG Circuit emulation G703 E3

Frequency accuracy ≈0.2ppm +/- 20ppm
Rate of change ≈0.02ppm unspecified
On analogue video signals a rate of change greater than 0.02ppm will lead to distortions in the
horizontal and vertical synchronisation.
The major problem introduced by the use of network ser vices for high quality video data transfer is
the network jitter, which overlays the original video signal. In ATM networks this jitter results from
differences in the inter-arrival time between consecutive cells caused by several synchronisation
stages. The parameter, which qualifies this value is the variation of the in ideal constant cell delay
over the network, called CDV (Cell Delay Variation).
For the algorithm of the adaptive clock recovery the difference between the maximum/minimum and
the mean delay measured in us (Peak-Peak CDV), is more important. In general the time required to
guaranty the required accuracy of 0.2ppm at a given CDV can be calculated as:
trec[s]= 5 * CDVPEAKPEAK [us]
In order to minimise the delay between the receipt of the first ATM cell and moment the video output
is switched on, the ATM Vison system provides the video output in less than five seconds. The output
signal then will probably not fulfil the requirements of PAL specification, but no loss of data will occur
furthermore. In order to keep the mean delay as short as possible the buffer size of the ATM Vision
system is adapted to the video data rate and the peak -peak CDV.
The choice of the peak-peak CDV parameter has a great impact on the performance of the clock
recovery. Specifying a too great value (greater than the CDV observed in the network) will increase
the mean delay and the time required by the recovery, but prevents from loss of data. Choosing a too
small value increase the potential of loss of data.
Using PVCs the connection is established at the local system. The connection parameter passed to
the system includes the CDV value stored in the connection entry. Using SVCs , the connection can
be initiated by the transmitting side. Because there is no possibili
ty to pass the CDV parameter along
with the connection setup message, the pre-configured CDV parameter of the video channels is taken
instead.
40
ATM Vision Operator and Administration Guide NSAP versus E.164 addresses
NSAP versus E.164 addresses

The ATM Forum has defined an AESA (ATM Endsystem Address) for the use in private AT M
networks based on the OSI NSAP address format. These 20-octet AESAs consist of two parts: an
Initial Domain Part (IDP), consisting of an Address Format Identifier (AFI) and an Initial Domain
Identifier (IDI), and a Domain Specific Part (DSP) encoding bot h the High Order DSP (HO-DSP) and
a low-order part consisting of an End System Identifier (ESI) and a Selector (SEL) where required.
The AFI defines the overall format of the NSAP, and may contain an identifier as to theternational
in
organisation responsible for the address space. The AFI is one octet in length. The next field is the
IDI, with a length and content dependent upon the AFI. The DSP is also based on the AFI, and may
contain decimal or binary values. DCC (Data C ountry Code) addresses use an IDI corresponding to a
particular country as identified in ISO 3166. ICD (International Code Designator) addresses are
allocated by the British Standards Institute and identify international organisations. For both DCC and
ICD formats the Domain Format Identifier (DFI) identifies the address format used by the body
responsible for the assigning of the Address Authority (AA) field. In most cases the AA field contains
an organisational identifier. These AAs may structure the rema inder of the 10-octet HO-DSP. The ESI
identifies an actual end-system and must be unique within a particular IDP and HO -DSP. In almost all
cases this ESI will be based upon a globally unique -6octet IEEE MAC address. Though the final field,
SEL, is not used for routing, it may be used by ATM end -systems for multiplexing to identify sub-
interfaces.
In contrast to the multiple NSAP formats, only one E.164 address structure exists, based on the global
ISDN numbering plan. When connecting a private ATM domainto a public network, only the UNIs
connected directly to the public network will be assigned E.164 addresses. The first 1 to three digits
identify the country code. The remainder of the E.164 address is nationally assigned, containing in
most cases a city or area code, an exchange code and an end -system identifier. Referring to the
NSAP form at addresses, one option encapsulates E.164 address into the NSAP structure.
In interworking between public and private ATM domains, each based on different address ructures,
st
four scenarios have been defined:
• private host to private host without intervening public networks
• private host to private host with intervening public networks
• public host to public host and
• private host to public host and reverse direction
In the first and second case the target host can be addressed by the use of its NSAP address. In the
case of an intervening public network, the connection request from one host to another will transit one
or more public networks. In this case, a routing decis
ion must be made at this time as to which egress
point from the public network must be used. This egress will be in the form of an E.164 address.
41
ATM Vision Operator and Administration Guide NSAP versus E.164 addresses
Under this scenario the NSAP address of the ultimate destination will be mapped into an E.164
address at the ingress to the public network.
In the third scenario all signalling requests use native E.164 addresses. The fourth scenario requires
address resolution in both directions. The public host must resolve the NSAP address of the private
host, and with it the E.164 address of the best egress point of the public network. In the opposite
direction the private host converts the E.164 address of the public host to NSAP making use of the
E.164 private ATM address format with RD, AREA and ESI set to zero.
42
ATM Vision Operator and Administration Guide ATM Vision registry entries
ATM Vision registry entries

The application stores several information to the local registry under the HKEY_LOCAL_MACHINE
root entry. The registry entries can be reviewed with standard registry tools, but should only be
modified by the use of the ATM Vision application.
The entry HKEY_LOCAL_MACHINE\SOFTWARE\ATecoM\ATM_Vision\Devices contains the entries

of the device database.
The entry HKEY_LOCAL_MACHINE\SOFTWARE\ATecoM\ATM_Vision\Targets contains the
information on the connections between ATM Vision systems and the local PC.
The entry HKEY_LOCAL_MACHINE\SOFTWARE\ATecoM\ATM_Vision\VideoConnections contains
the entries of the connection database.
Note: When running the application only the registry of your local system willebchanged.
To remove the ATM Vision application from your local system , just delete the program and
the ATecoM entry from your registry.
43
ATM Vision Operator and Administration Guide The ATM Vision console
The ATM Vision console

Some parameterand additional static information of theATM Vision system firmware can be
accessed by the ATM Vision console.
The ATM Vision console runs on the serial port 1 of the ATM Vision systemand can be accessed with
a standard terminal program running 19200 Baud, no parity, 8 data bits, 1 stop bit and hardware
handshake.
Connect your PC to the serial port 1 of the ATM Vision system. After pressing RETURN you will see a
login prompt.
Login:
Login as ADMINISTRATOR with the same password as used within ATMVISION.EXE.

Login: administrator
Password:
ATM Vision:/>
The ATM Vision console commands

You can obtain a list of the commands by typing ?
ATM Vision:/> ?
help - Display this screen
? - Display this screen
cd - Select device path
configure - System configuration menu
show - Show system/device inf ormation
status - Display system/device status
set - Set system variables
passwd - Change maintenance password
reconfigure - Reconfigure the system (Clears CMOS)
reset - Reset the system
exit - Logout
The commands SHOW, STATUS and CONFIGURE can be supplied on the different devices of the
ATM Vision firmware. The device tree is shown below, whereby # represents the number of the
device.
/system
/system/1/watchdog
/interfaces/#
/interfaces/#/video_trm/#
/interfaces/#/video _rcv/#
/interfaces/#/aal5
/interfaces/#/sig
/interfaces/#/ilmi
In order to retrieve statistics of thefirst line interface of the system type:
ATM Vision:/> stat /interfaces/1
SDH interface 1
Transmitted cells: 1024657586
Received cells: 1023485001
Idle cells: 0
Errored cells: 15
Corrected cells: 1
Errors:
Section
LOS - 0
LOC - 0
LOF - 0
OOF - 0
BIP8 - 329
Line
AIS - 0
RDI - 0
FEBE - 76
BIP24 - 55
Path
RDI - 0
AIS - 0
BIP8 - 329
FEBE - 43
LOP - 0
44
You can walk through the device tree by the use of the
CD command. The CD command accepts
absolute and relative pathnames:
ATM Vision:/> cd /interfaces/1/aal5
ATM Vision:/interfaces/1/aal5/>
or
ATM Vision:/> cd /interfaces/1
ATM Vision:/interfaces/1/> cd aal5
ATM Vision:/interfaces/1/aal5/>
In order to step back type

ATM Vision:/interfaces/1/aal5/> cd ..
ATM Vision:/interfaces/1/>
Changing the ATM Vision system time

The SET command allows you to adjust the ATM Vision system time.
ATM Vision:/> set date
Enter system time 05/15/1998 14:37:41: 05/15/1998 14:40:00
ATM Vision:/>
Note: The date/time must be entered in the international format MM/DD/Y

YYY HH:MM:SS whereby
the year includes the century.
Changing the watchdog timeout interval

ATM Vision:/> conf /system/1/watchdog
Watchdog timeout [ms] [ 5000]: 10000
ATM Vision:/>
Tools for testing the network configuration

The atmarp command
Usage: atmarp <ip-address> Displays the ATMARP entry for the given IP address
atmarp -a Displays all entries stored inthe ATMARP table
atmarp -d <ip-address> Deletes the ATMARP entry of the given IP address
atmarp -s <ip-address> <aesa> [ae ssa] Creates a SVC ATMARP entry
atmarp -p <ip-address> <vpi> <vci> Creates a PVC ATMARP entry
Examples:
• Display all entries in the ATMARP table:
ATM Vision:/> atmarp -a

IP address AESA
192.168.5.5 0x45.000492407958642F.0000.0000.00000000 0002.00
• Add a SVC entry for IP address 192.168.5.6:
ATM Vision:/> atmarp -s 192.168.5.6 0x45.000492407958642F.0000.0000.000000000002.0000.0000000003
• Display entries for IP address 192.168.5.6:
ATM Vision:/> atmarp 192.168.5.6

IP address AESA
192.168.5.6 0x45.000492407958642F.0000.0000.000000000003.00
• Add a PVC entry for 192.168.5.7
ATM Vision:/> atmarp -p 192.168.5.7 0 62
• Display all entries in the ATMARP table:
ATM Vision:/> atmarp -a

IP address AESA
192.168.5.7 VPCI 0.62
192.168.5.6 0x45.000492407958642F.0000.0000.000000000003.00
192.168.5.5 0x45.000004202670080F.0000.0000.000000000001.00
• Delete entry for IP address 192.168.5.7:
ATM Vision:/> atmarp -d 192.168.5.7
45
46
The ifconfig command

Usage: ifconfig <interface> | -a
[ <address> [ <dest_addr> ] ] [ up | down ]
[ netmask <mask> ] [ broadcast <broad_addr> ]
[ mtu <n> ] [ arp | -arp | arpserver <ip -address> ]
[ speed <n> [kbps] ] [ forward | noforward ]
Examples
• Display configuration of all interfaces:
ATM Vision:/> ifconfig -a

eth0: 192.168.2.101 mask FFFFFF00 broadcast 192.168.2.255
[ UP BROADCAST ARP ] mtu 1500 speed 10.0Mbps
atm0: 192.168.5.4 mask FFFFFF00 arpserver 0.0.0.0

[ UP FORWARDING ] mtu 9180 speed 2.0Mbps
lo0: 127.0.0.1 mask FF000000

[ UP LOOPBACK ] mtu 1536 speed 10kbps
• Set ATMARP server for interface atm0:
ATM Vision:/> ifconfig atm0 arpserver 192.168.5.1
• Display configuration of interface atm0:
ATM Vision:/> ifconfig atm0

atm0: 192.168.5.4 mask FFFFFF00 arpserver 192.168.5.1
[ UP FORWARDING ] mtu 9180 speed 2.0Mbps
• Change MTU and speed of interface atm0:
ATM Vision:/> ifconfig atm0 mtu 1500 speed 64

atm0: 192.168.5.4 mask FFFFFF00 arpserver 192 .168.5.1
[ UP FORWARDING ] mtu 1500 speed 64kbps
• Disable IP forwarding on interface atm0:
ATM Vision:/> ifconfig atm0 noforward

atm0: 192.168.5.4 mask FFFFFF00
[ UP ] mtu 1500 speed 64kbps
• Shutdown interface atm0:
ATM Vision:/> ifconfig atm0 down

atm0: 192.168.5.4 mask FFFFFF00
[ ] mtu 1500 speed 64kbps
The ping command

Usage: ping [-t timeout] [-s size] [-c count] <ip-address>
Parameters:
-t Timeout between twoICMP echo request in seconds [ Default = 10s ]
-s Packet size used by the ICMP echo request[ Default = 64 Bytes]
-c Total number of ICMP echo requests [ Default = 1 ]
ip-address IP address of host to send the ICMP echo requests to
Example:
ATM Vision:/> ping 192.168.5.5
Pinging 192.168.5.5 with 64 bytes, Seq = 1
Timed out
47
The route command

Usage: route add | delete [ host | net ] <destination> <gateway>
route show
Examples:
• Display routing table:
ATM Vision:/> route show

Destination Mas k Gateway Device Type Proto
--------------- --------------- --------------- ------ -------- -------
127.0.0.1 255.0.0.0 127.0.0.1 lo0 direct static
192.168.2.0 255.255.255.0 192.168.2.101 eth0 direct static
192.168.5.0 255.255.255.0 192.168.5.4 atm0 direct static
• Adding a new routing entryfor network 192.168.6.0
ATM Vision:/> route add net 192.168.6.0 192.168.5.5

Destination Mask Gateway Device Type Proto
--------------- --------------- --------------- ------ -------- -------
127.0.0.1 255.0.0.0 127.0.0.1 lo0 direct static
192.168.6.0 255.255.255.0 192.168.5.5 atm0 indirect static
• Delete routing entry for network 192.168.6.0
ATM Vision:/> route delete net 192.168.6.0 192.168.5.5

Destination Mask Gateway Device Type Proto
--------------- --------------- --------------- ------ -------- -------
127.0.0.1 255.0.0.0 127.0.0.1 lo0 direct static
48
Testing the hardware

The following chapter describes a test procedure for testing the hardware of a standalone ATM
Vision system.
1. Disconnect the ATM Vision system from your ATM network.

2. Connect a video source to a video input connector.
3. Create two database entries for a PVC loop -back video connection using the same values for
VPI/VCI, video rate, and FEC.
4. Establish the connection for the transmitter (video input). The LED in the channel's status window
now should switch from IDLE (Grey) to ACTIVE (Green) or WRONG_INPUT Y ( ellow). If the video
clock is missing (LED gets Red) check the output signal of your video equipment and the video
cables by applying it directly to a decoder. If the LED gets yellow, indicating a higher input rate
than configured, check the configured bitrate and the measured bitrate against the configure
output bitrate of the encoder.
5. Run statistics on the line interface. Check thetransmitted number of cells and the cell rate.
6. The intensity of the green TX LED of the line terminatormodule reflects the outgoing ATM cell
rate.
7. Connect the receiver and transmitter of the line terminator by the use of a loop -back cable or
fibre. The intensity of the green RX LED now reflects the incoming ATM cell rate.
8. Run statistics on the line interface. Check the received number of cells and the cell rate.
9. Establish the connection for the receiver (video output).The LED in the channel's status window
now should switch from IDLE (Grey) to INITIALIZED (Red),ACTIVE (Yellow) and after some time
to LOCKED (Green).
10. Compare the recovered bitrate with the encoder's output bitrate.
49
ATM Vision Operator and Administration Guide Trouble shooting
Trouble shooting
ion system the following errors
During the connection establishment from the local PC to an ATM Vis
can occur:
Error message possible Reason Actions

Unable to open device The serial port you have selected is already in •Check if another application, i.e. Hyperterm is
use by another application. using this serial port. Disconnect or terminate
the application. Try again to connect to the ATM
Vision system.
•Try to find out, if the port you have selected is
available. Use the control Panel to get further
information.
Invalid target address The specified IP address is invalid. •Check if the IP address is not a reserved
address, i.e. a broadcast address. Ask your
network administrator for a valid IP address.
No route to destination The network is unable to route the IP packets •Check the hosts IP address.
to the specified host. •Check if a gateway for the hosts network is
defined in the network configuration.
•Use the program TRACERT to find the point of
failure.
•Use the program PING to test the IP connection
to the ATM Vision system.
Connection timed out The ATM Vision system does not respond on •Check if the ATM Vision system is powered on.
the connection establishment via serial •Check if the cables are connected.
line or TCP/IP. •Check the interfaces of your PC.
•Use the program PING to test the IP connection
to the ATM Vision system.
The system is already in use by The ATM Vision system is already connected •Check if another instance of the application is
another application to another application. already running and is connected with the
system.
•Check if another user is connected with the
system. Try again later.
•Connect to the system via a serial line. If the
same error message appears than another
application is connected with the system via
TCP/IP. If the connection is excepted than the
last connection to the system via seria l line was
terminated without a log off.
Access denied The specified password is invalid. •Retype the password.
•Check if the right account is selected.
•Ask your system administrator for the valid
password.
Invalid message received The application receiveda invalid or •When using a serial connection check if the
corrupted message. serial port #2 of the ATM Vision system is used.
•Check the cabling between your PC and the
ATM Vision system.
50
ATM Vision Operator and Administration Guide Trouble shooting
Errors while setting up a video connection.
Error message possible Reason Actions

The connection database The video database contains no entry which •Check if the connection database contains an
contains no entry with the matches the requirements of the selected entry which can be used for the selected
required parameters. video channel or when using PVCs the PVCs channel. If necessary create a new entry.
of all possible connection entries is already in •Check the channel configurations in the system
use by another channel. database.
•Check the FEC and video frequency settings in
the connection entries.
•When using SVCs check if a signaling protocol
is selected for the line interface the channel is
connected to.
Resource unavailable The as target selected video channel is •If you have access to the remote sys tem check
already in use. if the video channel is connected to another
system.
Recovery on timer expire The protocol for assured data transfer •Check the state of the signaling protocol for the
underlying the signaling protocol SSCOP has line interface.
terminated. •Ask your network provider to check the state of
the ATM switch.
Destination out of order A temporary failure in the ATM Vision system •Retry to connect.
or the ATM switch has occurred. •Check the state of the signaling protocol for the
line interface.
•Ask your network provider to check the state of
the ATM switch.
Temporary failure The signaling protocol between the ATM •Check the state of the signaling protocol for the
Vision system and the ATM switch was line interface.
terminated. All active video connections are •Ask your network provider to check the state of
closed. the ATM switch.
Unassigned number specified The specified end system address is •Check the number.
unknown to the network. •Ask your network provider to check the
configuration of the network switches.
No route to destination The specified number can not be reached by •Check the number.
the ATM network. •Check if the target system is registered to the
network.
•Ask your network provider to check the
configuration of the network switches.
Destination not responding The target system is not responding on the •Check if the target system is powered on.
connect request.
Call rejected The connect request was rejected by the •Check if the correct signaling protocol is
network. selected for the line interface.
•Ask your network provider to check the
configuration of the network switches
Invalid address format or The specified end system address is invalid •Check the number.
address incomplete or incomplete.
Quality of service unavailable The by the ATM Vision system requested •Ask your network provider to check the
quality of service is not available in the configuration of the network switches
network. •Ask your network provider to check the network
load.
User cell rate unavailable The requested bandwidth is not available in •Ask your network provider to check the
the network. configuration of the network switches
•Ask your network provider to check the network
load.
Identified channel does not exist A channel for the specified selector does not •Check the number and the selector.
exist.
Incompatible destination The network or the target system is running a •Ask your network provider to check the
different protocol version. configuration of the network switches
•Check if the right signaling protocol is
configured on both ATM Vision systems.
51
ATM Vision Operator and Administration Guide ATM Vision technical description
ATM Vision technical description
General
• Dimensions:
• Weight:
• Power supply:
• Cooling:
•
CPU
• Motorola M68030, 25MHz
• RAM 4MB min. 32MB max.
• 32kB SRAM, onboard battery backup or backup via +5V-Stdby
• Flash memory 4MB min 8MB max.
• Ethernet to IEEE 802.3 Rev.0,AUI with 15-pin SUB-D connector
• 3 RS-232 serial ports with standard 9-pin SUB-D connectors
Connectors
Transceivers
Model Supplier 10Base2 10BaseT

MX10S CentreCOM •
210TS CentreCOM •
LTX-2A-11 Transtec •
LTX-TA-11 Transtec •
LEDs
Name Indicates Normal operation Error indication
RUN CPU activity GREEN OFF or RED
BM BUS access flickering permanently on
System Firmware
• ATM Vision application interface over RS
-232 or TCP/IP
• Terminal (VT100) based configuration console
• Signalling according to ATM Forum UNI 3.0, UNI 3.1, UNI 4.0, and ITU-T Q.2931
• ATM Forum ILMI 3.0 and ILMI 4.0
• Mixed PVC and SVC setup
• Point to Multipointsupport
• Automatic setup of pre-configured PVCs at power up
• SNMP V1 support
• SYSLOG support
• Firmware update via downloadover RS-232 or TCP/IP
52
Line Interface Modules

PDH E3
• Physical/electrical characteristics to ITU-T G.703 (75Ω coaxial)
• E3 (34.368 Mbit/s ±20ppm)
• ITU-TS G.703 physical layer
• HDB3 encoder/decoder
• Framing (ADM) to ITU-TS G.804/G.832 (ETS-300.337)
• Framing (PLCP) cell mapping to ETS-300.214
• ATM cell generation and delineation including HEC processing, error correction and
scrambling to ITU-T I.432
• Connectors 2 x BNC or 1 x RJ48C for line
53
DS3
• Physical /electrical characteristics to ITU-TS G.703 (75Ω coaxial)
• B3ZS encoder/decoder
• Framing (ADM) to ITU-TS G.804/G.832
• Framing (PLCP) to ATM Forum UNI & ANSI TA-TSY-00773
• C-bit parity default, M23 option
• ATM cell generation and delineation including HEC processing, error correction and
scrambling to ITU-TS I.432
• Connectors BNC or DIN 47295 {1,6/5,6 mS (75Ω )}
SDH electrical
• 155.520 Mbit/s ±20ppm
• G.703 electrical (twin 75Ω coaxial cables)
• CMI line coding
• SDH (SONET) section, line and path overhead processing
• Cell generation and delineation including HEC processing error correction and scrambling to
ITU-T I.432
• Connectors - DIN 47295 {1,6/5,6 mS (75Ω )}
Cable characteristics:
Cable description Supplier Diameter Loss Max. Range
[mm] [dB/100m] at 100MHz [m]
V45466-D2-B25 Siemens 6.00 15 85
CT100 RS 6.65 6.4 200
CT125 RS 7.80 4.9 260
CT167 RS 10.10 3.7 340
RG-11 Conrad 10.30 7.5 170
1-GA-75 Conrad 7.00 9 140
Note that the larger diameter cables may not fit directly into the required DIN 47295
connectors. Try and avoid complex cables
with too many connections. Each connection will present a discontinuity in the characteristic impe
dance of the link and will
reduce the useful distance.
This cable information is offered as a rough guide only, please check with the manufacturers for precise information.
54
SDH multimode
• Centre wavelength 1260nm min. 1380 nm max.
• 155 Mbit/s NRZ line coding
• Output power -21 dBm min, -13.0 dBm max.
• Input sensitivity -31 dBm min.
• Saturation level-14 dBm min.
ITU-T I.432
• SC connector
• Optical fibre 62.5/125 µm or 50/125 µm
SDH monomode
• 155.520 Mbit/s ±20ppm
• Physical /optical characteristics of digital interfaces to IT
U-T G.957-S1.1, inter-office / short
haul using 1310 nm fibre.
• Optical interface for 9/125um monomode fibre (Receiver module has 50/125um pigtail, thus
ensuring compatibility to mono and multimodesystems.)
• NRZ line coding
• Centre wavelength 1260 nm min. 1360nm max.
• rms spectral width 7.7 nm max.
• Laser output power -15 dBm min. -8.0 dBm max.
• Input sensitivity -28 dBm min.
• Optical path penalty 1dBm max.
• Input saturation level-8 dBm min.
ITU-T I.432
• SC connector
55
Video channels
Transmitter
• AAL type 1 to ITU-T I.363.1
• Byte interleaving 128 x 47to ITU-T I.363.1
• FEC using RS encoding (124,128) to ITU-T I.363.1
• Bypass of byte interleaving and FEC generation
• Cascade SAI input
• 1 universal purpose low bit rate AALchannel
• Full VPI/VCI range support
• Test pattern generator (VMB 2.0 only)
Receiver
• Adaptive clock recovery
• Lock in time (1 ppm) typical < 10s @ 8.448 MHz video rate
• Frequency accuracy < ±0.2ppm
• Max. rate of change in locked state <±0.02ppm
• Byte de-interleaving 128 x 47 to ITU-T I.363.1
• FEC using RS decoding (124,128) to ITU-T I.363.1
• F4/F5 OAM channel
• universal purpose low bit rateAAL channels
• Bypass of FEC check and byte de-interleaving
• Full VPI/VCI range support
Video interface modules

G.703 E1 HDB3
• 2.048 Mbit/s ±50ppm 75Ω coaxial to ITU-T G.703
• HDB3 coding
• Output impedance 75Ω
• Pulse width 244 ns ±25 ns
• Output signal amplitude2.37V ±0.237V max., 0 ±0.237V min.
• Input impedance 75Ω
• Return loss > 18dB at 2048 kHz
• Connectors 2*BNC
G.703 E2 HDB3
• HDB3 coding
• Pulse width 59 ns ±10 ns
• Output signal amplitude 2.37V±0.237V max., 0 ±0.237V min.
• Connector 2*BNC
56
G.703 E3 HDB3
• HDB3 coding
• Pulse width 14.55 ns ±2.45 ns
• Output signal amplitude 1V±0.1V max., 0 ±0.1V min.
• Connector 2*BNC
DS3
• 44.736 Mbit/s ±20ppm 75Ω coaxial
• B3ZS coding
• Connector 2*BNC
Synchronous 8-bit parallel DVB LVDS

• 1..130 Mbit/s ±20ppm
• NRZ coding
• Common mode voltage 1.125V to 1.375V
• Signal amplitude 250mV to 450mV
• Input impedance 90Ω to 132Ω
• Input signal 2.0V pp max., 100mV pp min.
• Transmission formats 188 Byte and 204 Byte packets to ITU
-T J.82 and
Cenelec prEN 50083-9
• Connector SUB-D to ISO 2110
Synchronous 8-bit parallel DVB ECL (ITU-R BT.656-3)

• 1..130 Mbit/s ±20ppm
• NRZ coding
• Common mode voltage-1.29V ±15%
• Signal amplitude 0.8Vpp to 2.0V pp
• Input impedance 110Ω ± 10Ω
• Input signal 2.0V pp max., 185mV pp min.
-T J.82 and
Cenelec prEN 50083-9
• Connector SUB-D to ISO 2110
Asynchronous Serial Interface DVB ASI (Electrical)2

• 1..130 Mbit/s ±20ppm @ 270 MHz carrier
-T J.82 and
Cenelec prEN 50083-9 in burst and packet mode
• Connector 2*BNC
Asynchronous Serial Interface DVB ASI (Optical)3

• 1..130 Mbit/s ±20ppm
-T J.82 and
Cenelec prEN 50083-9 in burst and packet mode
• Connector SC
2
Requires VMB-2.0 board
57
8-bit parallel DVB interface specification
58
Acronyms
AAL ATM Adaptation Layer

ADM ATM Direct Mapping
AESA ATM Endsystem Address
AESSA ATM Endsystem Subaddress
AIS Alarm Indication Signal
ANSI American National Standards Institute
API Application Program Interface
ARP Address Resolution Protocol
ASCII American Standard Code for Information Interchange
ATM Asynchron Tranfer Mode
ATMARP ATM Address Resolution Protocol
AUI Attachment User Interface
BCOB Broadband Connection Oriented Bearer
BCOB-A Bearer Class A
BCOB-C Bearer Class C
BCOB-X Bearer Class X
BER Bit Error Rate
BES Bursty Errored Seconds
B-ICI B-ISDN Inter-Carrier Interface
BIP Bit Interleaved Parity
B-ISDN Broadband Integrated Services Digital Network
B-ISUP Broadband ISDN User’s Part
BNC Bayonet-Neill-Concelman
bps Bits per Second
B-TE Broadband Terminal Equipment
BUS Broadcast and Unknown Server
CBR Constant Bit Rate
CCITT International Telephone and Telegraph Consultative Commitee
CDV Cell Delay Variation
CDVT Cell Delay Variation Tolerance
CE Connection Endpoint
CEI Connection Endpoint Identifier
CLIP Classical IP
CLP Cell Loss Priority
CLR Cell Loss Ratio
CMR Cell Misinsertion Rate
CRC Cyclic Redundancy Check
CS Convergence Sublayer
CTD Cell Transfer Delay
CTS Clear To Send
DCC Data Country Code
DCE Data Communication Equipment
DDI Direct Dial In
DNS Domain Name Service
DSR Data Set Ready
DTE Data Terminal Equipment
DTR Data Terminal Ready
DVB Digital Video Broadcasting
EBU European Broadcasting Union
EEPROM Electrical Erasable Programmable Read Only Memory
EMI Electromagnetic Interference
EPROM Erasable Programmable Read Only Memory
ESI End System Identifier
FEBE Far End Block Error
FEC Forward Error Correction
59
FERF Far End Receive Failure

FIFO First-In, First-Out
FTP File Transfer Protocol
GFC Generic Flow Control
HDB3 High Density Bipolar
HEC Header Error Control
ICD International Code Designator
ICMP Internet Control Message Protocol
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
ILMI Interim Local Management Interface
IP Internet Protocol
ISO International Standards Organization
ITU International Telecommunication Union
ITU-R ITU Radiocommunication
ITU-T ITU Telecommunication
Kbps Kilobits per Second
LAIS Line Alarm Indication Signal
LAN Local Area Network
LANE LAN Emulation
LCV Line Coding Violations
LEC LAN Emulation Client
LECS LAN Emulation Configuration Server
LES LAN Emulation Server
LOF Loss Of Frame
LOP Loss Of Pointer
LOS Loss of Signal
LSB Least Significant Bit
MAC Media Access Control
MAN Metropolitan Area Network
MBS Maximum Burst Size
MCDV Maximum Cell Delay Variation
MCLR Maximum Cell Loss Ratio
MCR Minimum Cell Rate
MCTD Maximum Cell Transfer Delay
MIB Management Information Base
MIC Media Interface Connector
MMF Multimode Fibre Optic Cable
MPEG Motion Picture Expert Group
MPOA Multi Protocol over ATM
MPLS Multi Protocol Layer Switching
MSB Most Significant Bit
MTU Maximum Tansmission Unit
NM Network Management Entity
NML Network ManagementLayer
NMS Network Management Station
NNI Network to Network Interface
NSAP Network Service Access Point
NTSC National TV Standards Committee
OAM Operation and Maintenance
OC-n Optical Carrier level-n
OID Object Identifier
OOF Out Of Frame
OSI Open Systems Interconnection
PAIS Path Alarm Indication Signal
PAL Phase Alternate Line
PCR Peak Cell Rate
PDH Plesiochronous Digital Network
PDU Protocol Data Unit
60
ping Packet Internet Groper

PPP Point to Point Protocol
PROM Programmable Read Only Memory
PVC Permanent Virtual Channel
PVCC Permanent Virtual Channel Connection
PVPC Permanent Virtual Path Connection
QoS Quality of Service
RD Routing Domain
RDI Remote Defect Indication
RFCs Request For Comment
RFI Radio Frequency Interference
RSD Reed Solomon Decoding
RSE Reed Solomon Encoding
RTS Request To Send
SAI Standard ATM Interface
SAP Service Access Point
SAR Segmentation And Reassembly
SCR Sustainable Cell Rate
SDH Synchronous Digital Hierarchy
SDU Service Data Unit
SECAM Systeme En Coleur Avec Memoire
SEL Selector
SES Severely Errored Seconds
SLIP Serial Line IP
SMF Single Mode Fibre
SMPTE Society of Motion Picture & Television Engineers
SNMP Simple Network Management Protocol
SONET Synchronous Optical Network
STM Synchronous transfer Mode
STS Synchronous Transport Signal
SVC Switched Virtual Channel
SVCC Switched Virtual Channel Connection
SVPC Switched Virtual Path Connection
TCP Transmission Control Protocol
TCP/IP Transmission Control Protocol/Internet Protocol
TE Terminal Equipment
TFTP Trivial File Transfer Protocol
UAS Unavailable Second
UDP User Datagram Protocol
UNI User to Network Interface
UTOPIA Universal Test & Operation Interface for ATM
UTP Unshielded Twisted Pair
VC Virtual Channel
VCC Virtual Channel Connection
VCI Virtual Channel Identifier
VP Virtual Path
VPC Virtual Path Connection
VPI Virtual Path Identifier
WAN Wide Area Network
61
References
[ATMF UNI3.0] ATM User-Network Interface Version 3.0 (UNI 3.0) Specification
[ATMF ILMI4.0] Integrated Local Management Interface (ILMI) Specification Version 4.0
[DVB-CAS-60] DVB Interfaces to PDH Networks
[ETS 300 814] DVB Interfaces to SDH Networks, Final Draft, December 1996
[ITU-T E.164] Numbering plan for the ISDNera
[ITU-T G.702] Digital hierarchy bit rates
[ITU-T G.703] Physical/electrical characteristics of hierachical digital interfaces
[ITU-T G.707] Synchronous digital hierarchy bit rates
[ITU-T G.804] ATM cell mapping into plesiochronous digital hierarchy (PDH)
[ITU-T G.823] The control of Jitter & Wander within Digital Networks which are basedon the
2048Kbit/s Hierarchy
[ITU-T G.957] Optical interfaces for equipmentand systems related to the synchronous digital
hierarchy
[ITU-T I.361] B-ISDN ATM layer specification
[ITU-T I.363-1] B-ISDN ATM adaptation layer (AAL) specification
[ITU-T I.432] B-ISDN User-Network Interface - Physical layer specification
[ITU-T I.732] Functional characteristics of ATM equipment
[ITU-T J.82] Transport of MPEG-2 constant bit rate television signals in B -ISDN
[ITU-T Q.2110] B-ISDN ATM adaptation layer- Service specific connection oriented protocol
(SSCOP)
[ITU-T Q.2130] B-ISDN ATM adaptation layer- Service specific coordination function (SSCF)
[ITU-T Q.2931] B-ISDN DSS2 user-network interface layer 3 protocol
[ITU-T Q.2951] Stage 3 description for number identification supplementary services using
B-ISDN digital subscriber Signalling System No. 2 (DSS2)
[ITU-T Q.2957] Stage 3 description for additional information transfer supplementary services
using B-ISDN digital subscriber Signalling System No. 2 (DSS2)
[ITU-T Q.2971] DSS2 - User-network interface layer 3 specification for point-to-multipoint
call/connection control
[ISO 2110] 25 pole DTE/DCE interface connector and contact number assign ment
[EN 50083-9] Interfaces for CATV/SMATV headends and similar professional equipment
62
ATM Vision Operator and Administration Guide Notes
63
Notes
Seller will have no obligation or liability in respect of defects or damage caused by unauthorised use, mis -use, accident, external
cause, installation error, or normal wear and tear. There are no war ranties, representations or guarantees of any kind, either express
or implied by law or custom, regarding the product or its performance, including those regarding quality , merchantability, fineness for
purpose, condition, design, title, infringement of third-party rights, or conformance with sample. Seller shall not be responsible for any
loss or damage of whatever nature resulting from the use of, or reliance upon, the information contained in this document. In no event
will Seller be liable to Buyer or to any other party for loss
of profits, loss of savings, or punitive, exemplary, incidental, consequential or
special damages, even if Seller has knowledge of the possibility of such potential loss or damage and even if caused by Seller ’s
negligence.
 1997 ATecoM GmbH
64

ATM Vision Operator and Administration Guide

Uploaded by

Copyright:

Available Formats

ATM Vision Operator and Administration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ATM Vision Operator and Administration Guide

Uploaded by

Copyright:

Available Formats



ATM Vision registry entries ..........................................................................................................43

Connecting to an ATM Vision system

Creating/Editing a target system entry

Deleting a target system entry

1. Select the target system from the system select box.

ATM Vision System Configuration

The configuration submenu

An example of the resulting sub-menu structure is shown below:

Watchdog timer and remote system reset

Modifying the system's routing table

Changing the password and access permission

Line interface configuration

Interface Type Mode Default

Local ATM Endsystem Address (AESA)*

Selecting the signalling protocol*

Video channel configuration

Changing the name of a video channel

Changing the interface default settings

For each alarm the following information is displayed:

The task statistics can be updated by pressing the Refresh button.

Line interface statistics

Video channel statistics

The curves for different measurements can be displayed:

The video connection database

The video connection database is divided into two parts:

Figure 1: The structure of the system and the connection database

Creating or modifying system entries

Initiator connected to Target connected to AESA format AESSA format

Creating or modifying a systems channel entries

Press OK to accept or Cancel to discard the changes you have made.

Saving changes to the database

Creating or modifying connection entries

Exporting and Printing of the Database Entries

Importing Database Entries

Permanent Virtual Connections (PVCs)

Switched Virtual Connections (SVCs)

Point to Multipoint connections

Setting up video connections

LED colour Transmitter Receiver

Adding a new connection

Entries in the system database

Entries in the connection database

The connection database should look like shown below:

Now we add the connection entries required by system #2 follow:

Finally the connection entries required by system #3:

Classical IP (CLIP) setup

Routes to be configured atCustomer LAN 1, Gateway 1:

Routes to be configured atCustomer LAN 2, Workstation 1:

0.0.0.0 192.168.6.1 0.0.0.0 eth0

Routes: Target Gateway Mask Interface Type

Configuration of ATM Vision 2:

Routes: Target Gateway Mask Interface Type

Configuration of ATM Vision 3:

Routes: Target Gateway Mask Interface Type

Setting up IP connections over PVCs

ATMARP table of ATM Vision 1:

ATMARP table of ATM Vision 2:

ATMARP table of ATM Vision 3: