1. Version 4.5 11 February 2004 Paul Pyck
TMA management
Version February Paul Pyck

2. Contents Management topologies General features TMA management tools
TMA Element Management applications
Network management applications and integration with other platforms
Supported products

3. Management Topologies
Overview
Non-IP and IP devices
Management topologies in the access network
Orchid hardware
Orchid connections to Telindus devices
Orchid connections to management stations

4. Overview Backbone network: IP protocol Access network: CMS2 protocol
Protocol conversions in Orchid management concentrator:
Telnet
SNMP
HTTP
ping
IP device
TMA
IP network
management station:
TCP/IP management
HP OpenView
Other
TMA
TMA
Concentrator device:
Orchid 1003 LAN or
Telindus 1035
Three types of equipment can be distinguished:
The managed equipment (Network element): This is the actual equipment the operator wants to manage: e.g. a Crocus base band Modem or an Aster 4 voice band modem.
The Network management system: This is the equipment with its proper software that is actually used by the operator for running the management application. It is constituted of:
A hardware platform with its Operating System, e.g. a PC with Windows 95/98, Windows NT or any UNIX workstation.
A management platform application: Any application, which supports SNMP, can be used. Alternatively Telindus offers its proper application TMA for HP OpenView that runs on the popular HP OpenView network management suite.
The mediation or concentration device: This device is put between the managed equipment and the Network management system: the Orchid 1003 LAN. It collects management information from the managed equipment (modems) that it is responsible for and translates it into a number of IP protocols: SNMP, telnet or ping. This is called TCP/IP proxy functionality. It encapsulates as well the Telindus proprietary modem protocol into IP packets. TMA, TMA CLI and TMA for HP OpenView communicate in this way with the Orchid 1003 LAN.
Backbone network: IP protocol
Access network: CMS2 protocol

5. Non-IP and IP devices IP devices Non-IP devices
Examples: transparent modems, multiplexers and converters
Require Orchid concentrator (mediation device) for central management
Orchid concentrates alarms, is CMS2 relay agent, TCP/IP proxy and handles consistency
IP devices
Examples: Telindus 1421 SHDSL Router, Telindus 1030 Router
Do not require Orchid concentrator for central management
Definitions:
IP device: includes IP protocol stack and interfaces to communicate using the IP protocol.
Non-IP device: such device is not IP aware
To manage non-IP devices using IP related protocols, one needs the Orchid 1003 LAN:
TMA over IP, TMA CLI, TMA for HP OpenView: Orchid encapsulates CMS2 protocol in IP and is a CMS2 relay agent.
Telnet, SNMP, HTTP: Orchid 1003 LAN is a TCP/IP proxy
Ping: Orchid 1003 LAN replies on ping requests if it is in contact with device.
To manage non-IP devices with SNMP or ping, each device needs its own IP address (configured in the Orchid)
Non-IP devices can be managed via the Orchid without their own IP address with TMA, TMA CLI, TMA for HP OpenView, telnet and HTTP.

6. Management topologies in the access network(1)
Modem links have an auxiliary channel for management
Default relative addressing scheme 1 1 2 3
Extended links by interconnecting CTRL ports
More complex extensions with absolute addressing scheme
Each device has a CTRL port for local maintenance.
Relative addressing:
device address determined by network position
no NMS address configuration required
Absolute addressing:
allows to cross digital multipoints
requires NMS address configuration 1
223
222
139
140
Orchid DM

7. Management topologies in the access network (2)
Crocus DXC / ADM 2P
Orchid DM E1 E1
SDH / PDH
Crocus DXC / ADM 2P
Small extensions on a PDH or SDH network. These include typically Crocus DXC or Crocus ADM 2P devices.
Management information forwarded over the Sa bits of time slot 0 of E1 interface over the SDH / PDH network.
On the central side, similarly a Crocus DXC or Crocus ADM 2P can retrieve the management information from the E1 interface and send it to the Orchid 1003 LAN.
To offer services on distant locations, without investing heavily in SDH or PDH nodes, a simple E1 add and drop multiplexer or E1 Nx64K cross-connect with modem extensions may be a cheap alternative. If the number of devices is small on such site, their management is possible without a local Orchid 1003 LAN concentrator.
By interconnecting the CTRL interfaces on the different devices (possibly through the use of an Orchid DM), all management information is concentrated in either the Crocus DXC or Crocus ADM 2P card. These cards provide the possibility to transfer this information over the SDH or PDH network using the Sa bits in time slot 0 of their E1 interfaces. On the central side, the management information can be retrieved again from the Sa bits on a cross-connect or add and drop mux card and further transferred to the Orchid 1003 LAN card.
The available bandwidth on the Sa bits is typically 1kbit/s. Therefore the number of devices connected remotely in this way should be limited (typically up to 10). Interconnecting devices for management via the CTRL port is in general possible on desktop units and not on card units. For the availability on card units, please contact Telindus.
Sending management information over the Sa bits on a G703 interface requires the use of absolute NMS addresses (see below) for all devices, managed in this way.

8. Orchid hardware Telindus 1035 Orchid CV Telindus 1035 Orchid TT
Best suited for topology with CN4 central units
Telindus 1035 Orchid TT
Has 2 low-speed asynchronous ports for desktop units
Other 1030 Router Series include also Orchid features with different interfaces, but without HS-bus
Orchid 1003 LAN TT
Best suited for direct connection of desktop devices in heterogeneous topologies.
Has 14 low-speed asynchronous port
Available until end-of-stock
Orchid DM is a simple digital multipoint device
The Orchid 1003 LAN includes standard 8MByte Flash memory. The Flash memory is organised as follows:
2MByte for Orchid 1003 LAN firmware bank 1
2MByte for Orchid 1003 LAN firmware bank 2
The rest is available as a file system with a single directory. It contains typically the following files: Orchid configuration file, modem model files, modem configuration files, modem firmware files.
Available interfaces on Orchid 1003 LAN:
Port type Max speed (bps) #ports TT #ports CV
Asynchronous V24 port (RJ45)
Asynchronous V24 port (DB9)
Sync/async V24 port (A / B) (RJ45)
High speed RJ45 sync port
V24 control port (RJ45)
TPI Ethernet port
AUI Ethernet port

9. Orchid connections to Telindus devices
Telindus 1035 Orchid / Orchid 1003 LAN
High Speed bus
similar to LAN bus
Up to 4 / 7 card nests
100 … 800 kbit/s
on CV: 2 ports to divide load
Asynchronous ports
connect directly to Table Top modem
speed up to 9600 bit/s
The purpose of the different ports is as follows:
Port Purpose
Asynchronous V24 ports Connect Table Top network elements
Connect TMA serially
Sync/async V24 ports (A/B): Connect to an IP network with Frame Relay, X.25 or PPP encapsulation
Connect to another Orchid 1003 LAN over PPP
High speed port Connect the Orchid 1003 LAN to a card nest (up to 7)
V24 control port Local management of the Orchid 1003 LAN using VT100 terminal or TMA
Ethernet port s Connect to an IP LAN network

10. Orchid connections to management stations
Orchid = IP router
Always IP protocol towards the management station
Each device has its own IP address. Alternatively it is addressed through Orchid’s IP address + exit port & NMS address
Each modem has also a name
Direct WAN encapsulations possible
PPP
Frame Relay
X25 (Orchid 1003 LAN only)
ATM (Telindus 1035 Orchid only)
The Orchid 1003 LAN keeps a list of all connected network elements. This list is called the objectTable. Each network element is defined with the following parameters:
Parameter Description
Name This name is used by TMA for HP OpenView.
Exit port & NMS address This defines the exact position of the network element towards the Orchid 1003 LAN. It includes also whether relative or absolute addressing is used.
IP address This optional parameter makes the network element SNMP manageable. Additionally it may be pinged. If no IP address has been assigned for a network element, it still is manageable over an IP network with TMA, TMA CLI, TMA for HP OpenView and telnet. The TMA applications address then the network element with the IP address of the Orchid 1003 LAN combined with the Orchid exit port and NMS address value. A telnet connection is built first to the Orchid 1003 LAN. Within the telnet session each of the network devices connected to the Orchid can be selected.
Network elements are not auto-discovered by the Orchid due to the wide variety of network topologies and dual addressing mode (relative and absolute). However the Orchid 1003 LAN keeps track of all used slots in connected card nests and indicates the undefined network elements in those slots.
The IP addresses for the network elements either may belong to one of the subnets on one of its interfaces (e.g. Ethernet or port A interface) or to a virtual subnet. Virtual subnets can be defined inside the Orchid 1003 LAN. As an IP router the Orchid 1003 LAN routes packets destined for an IP address on one of its virtual subnets to its own protocol stack. The packet is interpreted as a packet for the network element with the corresponding IP address.

11. General features CMS2 protocol Alarm reporting Preventive monitoring
Security
Orchid as CMS2 relay agent for non-IP devices
Orchid as TCP/IP proxy for non-IP devices
Configuration and firmware distribution and consistency

12. CMS2 protocol Proprietary network management protocol
Uses principles of CMIP and CORBA
Generic protocol -> per device type:
model file
bitmap file for sub-system picture in TMA
private MIB file for SNMP
All management applications like TMA, TMA for HP OpenView, TMA CLI, console CLI & ATWIN, telnet, SNMP, HTTP, EasyConnect all use the model file
Complete set is called TMA management features
The CMS2 protocol:
The CMS2 protocol is a proprietary Telindus protocol used between the Orchid and the modems. TMA uses it as well. The reason for a proprietary protocol is to use very efficiently the available bandwidth and to have a guaranteed response, two features not provided by TCP/IP protocols.
Telindus access products are for management purposes described in a standardised format. This is called the model of the product. Each Telindus access product family has its own model files.
The TMA management applications and telnet user interface are generic. This means that they all use the model files to translate the User Interface into protocol language. When a new product becomes available, it is sufficient to install only its model files to make it manageable.
The SNMP private MIB parameters match also completely the TMA model files.
Per product family the following data files are available:
Binary model file with extension .mod. One ASCII file models.nms contains the list of all supported products. TMA, TMA CLI and TMA use these files for HP OpenView, as well by the Orchid 1003 LAN for SNMP, HTTP and telnet management.
Bitmap files with extension .bmp. These files are used for the TMA subsystem picture. They are referenced in the binary model files.
Private MIB files in ASN.1 format with extension .mib. SNMP browsers use these files.

13. Alarm reporting for non-IP devices
Concentrator device:
Orchid
ORCHID 1003
LAN
Present?
Yes
Modems spontaneously send alarms to Orchid
Orchid polls modems for presence
Each network element has an extended range of possible alarms. Since the user is not always interested in all these alarms, each alarm can individually be masked. If an alarm has been masked, it will not be sent to a management station any more.
One can also assign a severity level to each alarm. The alarm severity is the level of importance of the alarm. It is sent along with the alarm to the management station. Severity levels can range from level 0 (no alarm) to 255. Depending on the used number of severity levels on the management station, one can choose the number of levels in use. Typically 4 or 5 alarm levels are in use, e.g. normal (level 0), warning (level 1), error (level 2), severe (level 3) and critical (level 4).
Default values for the alarm masks and levels have been assigned to obtain typically 5 to 10 different alarms per network element on 5 different levels.
All alarms can be masked and given a severity level per device

14. Alarm reporting for IP devices
Any SNMP station
Arszerfzdrfqsfzr fe^pt”-gµdùmg
qesrasdsqdfsqdsfqsdqsdqdqdqsdqsdqdq
“)’ré$e-)t -àr é)-r )r zmsldf “!I ,ik
67) àsoe às-e)z ér pd ùmlk& µ $^zp^r
fsqdfqzerfze qsdqsd qfghjgfhjlmkfmk
µdg
dfghfgµù dµù µùµùsdm ùdm$(r^ùf ^$r
easedasdzerfzq qqsd qsd sdflmkzàoert
zfp p^pl ^^pl ^pl ^p l^p ^p ^^
SNMP traps
ORCHID 1003
LAN
TMA Element Management station IP
Arszerfzdrfqsfzr fe^pt”-gµdùmg
qesrasdsqdfsqdsfqsdqsdqdqdqsdqsdqdq
“)’ré$e-)t -àr é)-r )r zmsldf “!I ,ik
67) àsoe às-e)z ér pd ùmlk& µ $^zp^r
fsqdfqzerfze qsdqsd qfghjgfhjlmkfmk
µdg
dfghfgµù dµù µùµùsdm ùdm$(r^ùf ^$r
easedasdzerfzq qqsd qsd sdflmkzàoert
zfp p^pl ^^pl ^pl ^p l^p ^p ^^
CMS2 alarms
(1) Orchid or IP device forwards alarms as SNMP traps
Trap destinations to be configured
(2) TMA Element Management application receives alarms in proprietary protocol:
alarms are acknowledged
much more processing efficient (important for large networks)
Two measures are taken to avoid alarm overflow on TMA for HP OpenView:
If an alarm state toggles more than a configurable number of times within a configurable time interval, the alarm will only be logged once for all succeeding state toggles with the additional indication ‘streaming’.
The alarm exchange between TMA for HP OpenView and the network elements is connection-oriented: each alarm message is acknowledged, the protocol uses a window size and corresponding flow control. This means that if one or several devices start sending an alarms burst, TMA for HP OpenView cannot get flooded with alarms.

15. Preventive monitoring
Statistics over last period
last 2 hours and last 24 hours
last 7 days on recent device types
Simplifies network problem diagnosis
3 kinds of parameters
time
counter
status
In addition to monitoring of the current status and statistics parameters of a network unit, the network units keep also performance parameters for the last 2 and 24 hours. This preventive monitoring greatly simplifies the task of diagnosing problems in the network.
One may consider 3 types of absolute performance parameters: time, counter, status. For each of these types corresponding values exist for the last 2 and 24 hours.
Over the last 2 hours typically 8 values represent the parameter values for each 15 minutes period.
Over the last 24 hours 12 values represent the parameter values for each 2 hours period.
Depending on the parameter type, the following values are available for the last 2 and 24 hours period:
time: A value expressed in time units during the 15 minutes or 2 hours period. E.g. the time an interface is up.
Counter: A counter indicating the number of times an event has occurred during the 15 minutes or 2 hours period. E.g. how many times an interface did go down.
Status: Three values are kept per time interval: minimum, maximum and average values. E.g. Signal/Noise ratio.
If on the NMS station one detects a modem line has dropped, he can look at the different line parameters on the central modem during the last 2 or 24 hours. Probably an accurate diagnosis of the problem can be found within minutes by looking at these history performance values.

16. Security One device may have different passwords
Passwords can assigned with different access levels: read, write, security, test, file access
If no passwords defined, no password required for access
All applications use these passwords
The following applications can be inhibited on IP devices:
SNMP
Telnet and HTTP (web)
TFTP and FTP
In order to protect a network element against manipulations by unauthorised people, a list of passwords with associated access levels can be defined in the network element. All applications use these passwords. When no password has been programmed, each user has total access to all parameters.
With each password a combination of up to 5 different access levels can be assigned. The table below shows these access levels:
ReadAccess: A password that includes this access level allows reading all parameters, except security items.
WriteAccess: A password that includes this access level allows changing all (configuration) parameters, except security items.
SecurityAccess: A password that includes this access level allows reading and changing security attributes. Typical security attributes are the password table and authentication protocol parameters.
TestAccess: A password that includes this access level allows performing loop and other tests. This level is only present on recent device types.
FileAccess: A password that includes this access level allows uploading and downloading files to the file system of this device. This is only applicable on devices with a file system.
In a large network, one can e.g. define different passwords for
·A field engineer who installs the network elements might have e.g. ReadAccess and TestAccess.
·A central management operator might have e.g. ReadAccess, WriteAccess and TestAccess
A central management administrator might have all access levels.

17. Orchid as CMS2 relay agent for non-IP devices
TMA, TMA CLI
IP network
Orchid concentrator
TMA Element Management application
TMA
TMA over IP, TMA CLI, TMA for HP OpenView: Orchid encapsulates CMS2 protocol in IP
Orchid is a CMS2 relay agent

18. Orchid as TCP/IP proxy for non-IP devices
Telnet, SNMP, HTTP: Orchid is a TCP/IP proxy: translates IP protocol into CMS2, gets info from device and translates this into IP protocol
Ping: Orchid replies on ping requests if it is in contact with device
To manage non-IP devices with SNMP or ping, each device needs its own IP address (configured in the Orchid)
Non-IP devices can be managed via the Orchid without their own IP address with TMA, TMA CLI, TMA Element Management , TMA for HP OpenView, telnet and HTTP
In order to use telnet or HTTP without an IP address assigned to the device, one must connect to the Orchid and then select the device behind the Orchid.

19. Configuration & firmware distribution
Management station IP
ORCHID
Orchid File System
Modem Configuration profile
Modem firmware
Available for non-IP devices
Firmware distribution has some limitations:
on some type of equipment, not possible on remote
not possible on central Table Top modems
not possible on modem extensions
Configuration distribution
In networks with many modems, experienced network administrators may want to change slightly configurations (e.g. changed alarm masks or levels) for large numbers of network units for optimal network management behaviour. In a modem network typically only a limited number of different configurations exist. Instead of sending new configurations individually from the network management station to each network unit separately, one can send each configuration once to each Orchid LAN and tell them to distribute the configurations to individual network units. The latter is more efficient in terms of bandwidth and time consumption.
Once the configurations are stored on the Orchid’s file system, you can tell the Orchid 1003 LAN also e.g. to send configurations to network units that are being installed. If the Orchid 1003 LAN fails to send a configuration to a network unit, it tries up to 3 times. Per network unit one can check whether the configuration download succeeded or not.
Software distribution
Most Telindus access devices store their code in Flash memory. This offers the possibility to upgrade the code without opening the box. In many cases it is even possible to upgrade code from the central management station.
Similarly to configuration distribution, one can send a new firmware code once to each Orchid 1003 LAN and tell them to distribute it to the individual network units. This frees the network management station mostly from the time consuming firmware upgrade task.
If the Orchid 1003 LAN fails to send a firmware code to a network unit, it tries up to 3 times. Per network unit one can check whether the firmware download succeeded or not.

20. Configuration & firmware consistency
Management station IP
ORCHID
Modem Configuration profile
Orchid File System
Modem firmware
Available for non-IP devices
Permanent check on same configuration/firmware on file system and in device
If not same, download from Orchid
During the installation of modems in a network, it is desirable that configurations can be prepared centrally before the modems have been installed and that these configurations are downloaded into the modems whenever they get connected. Similarly, whenever a unit is replaced, it is desirable that the service engineer does neither need to completely reconfigure the unit locally nor that the central management operator needs to take specific actions at the time of installation.
Similar to the distribution, the configuration file is stored on the Orchid’s file system. After a loss of contact and after each configuration change, the Orchid 1003 LAN compares the configuration file on its file system with the configuration of each network unit under consistency. If configurations do not match, the Orchid LAN starts downloading the configuration to the network unit. If downloading fails, it tries up to 3 times to download again. If it still fails, the Orchid 1003 LAN proceeds to the next network unit. The consistency status is continuously available per Orchid LAN on the management station.
On network units under consistency, it is not possibly to change the configuration in any other way than by changing the configuration file on the Orchid’s file system. The Orchid 1003 LAN inhibits configuration changes in this way.
To have completely consistent behaviour of all network elements in a managed network, network operators sometimes require that all network elements have exactly the same firmware code. On the Orchid 1003 LAN concentrator, one can configure which firmware version each network element should have. The Orchid checks on a regular time interval whether the firmware version on each network element under firmware consistency matches the firmware version on its file system. If firmware versions do not match, the firmware version on the Orchid is downloaded to the network element.
Similar restrictions apply as for the firmware distribution. Also a minimum firmware version may be required on the network elements for firmware consistency.

21. TMA management tools TMA EasyConnect hand terminal
VT100 local connection and telnet
Web interface
SNMP
Ping
TFTP, FTP & TML
TMA CLI

22. TMA: Features Connects to CTRL port and over IP
Windows 95/98/NT/2000/XP platforms
Configuration, Status & Performance management
Local, Remote & Network connectivity
Interactive subsystem picture (ISSP)
Export & import data to/from PC
Flash software download
Session authentication and frame encryption
Filtering and sorting of tables
TMA can be called with command line parameters
Free software
Feature overview
Establishment and termination of the connection with an equipment
Password protected access
Continuous session identification
Frame encryption
Reading and changing configuration of the equipment
Retrieving status information (current operation) of the equipment, including the current alarm status
Retrieving statistical information on the modem (e.g. covering a period of 24 hours)
Diagnostic tests
Configuration storage and retrieval on hard-disk
Status and statistics storage on hard-disk
Software download to equipment with flash-memory (software upgrades)
Subsystem pictures reflecting the status of indicators and push-buttons

23. TMA: User Interface Menu bar Containment tree window Toolbar
Subsystem picture button
Attribute window
Action window
Ease of Use
In the development of the software package, user-friendliness and ease of operation were set as primary design goals. This resulted in features like a menu navigation window, selection between basic and advanced views, MRU (Most Recent Used) list of connected equipment for a fast selection of the desired equipment to connect to, interactive picture etc …
Structured value window
Status bar

24. TMA: interactive subsystem picture
The interactive subsystem picture can be tuned to the customer’s needs:
Creating help text near LEDs, buttons and interfaces
Defining buttons to retrieve information in a separate window
Defining buttons to execute an action (e.g. test loop)

25. TMA ISSP can be customised to customer’s needs
Based on .usr file
Includes scripting + CLI commands

26. EasyConnect hand terminal
Connects to the CTRL connector for all equipment that supports TMA locally (both TT and CV units)
Gives LCD/keyboard interface based on model info on 2 lines of 24 characters
Full management information available!
Has processor and memory on-board
Has rechargeable battery for portable use
Typically used if installation engineers have no PC, for devices without much configuration
The hand terminal is a hand-set equipment for basic local management of Telindus access devices. It is targetted for customers that do not have or do not want to invest in PCs for local TMA management of Telindus access devices. It can be connected to the CTRL interfaces on any Telindus access device (desktop and card versions) that supports locally TMA. The user interface is the same as on the LCD display built into Aster 5. One can manage the same as with the other management tools (TMA, telnet, HTTP…), except the more complex items like tables. The hand terminal has Flash memory for storing data files and firmware code. The hand terminal is powered from a rechargeable battery.

27. VT100 local connection and telnet
VT100 terminal or terminal emulation connects to CTRL port
Starts up in Command Line Interface (CLI)
Suitable for experienced users
Type ‘ATWIN’ to switch to interactive user interface (ATWIN)
Suitable for novice users
Telnet connection
Same user interfaces CLI and ATWIN
IP device
Non-IP device IP
VT100 terminal
Orchid

28. CLI user interface Example: /crocus ShdslTt/line: “Edit Configuration”
>GET
retrain = {
errorPersistenceTime = “10 seconds”
errorThreshold = “30 %” }
channel = remote
region = annexB
timingMode = plesiochronous …
/ crocus ShdslTt : “Edit Configuration”
>GET / crocus ShdslTt /line/startupMargin
/ crocus ShdslTt /line/startupMargin = 2dB
>
Telnet is a standard TCP/IP protocol to connect a terminal to a computer. You can use telnet to connect any terminal or terminal emulation program to every network element via the Orchid 1003 LAN. If the network elements have their own IP address, one can make a straight telnet session to the network elements. If they do not have an IP address, you can make first a telnet session with the Orchid LAN. Within this session you can select the desired network element using its name.
The telnet session leaves the choice for one of the following user interfaces:
ATWIN: this is a VT100 application, which looks like a simplified TMA user interface. This is best suited for novice users.
CLI: this is a Command Line Interface. Knowing the syntax, you can more quickly access the network elements than with TMA or the ATWIN interface. This is best suited for experienced users.
These user interfaces allow to interactively maintain the network elements. All the configuration, status, statistics and alarm information available in TMA is also available using a standard telnet session, yet using a comprehensible user interface.
One can tune the number of lines and columns on the screen to its needs. Telnet access can be inhibited by configuration in the Orchid 1003 LAN. The Orchid LAN needs the TMA model file per device type on its file system to support telnet.
The Command Line Interface uses the same parameter names and object – attributes relationship as TMA does. A generic syntax allows to read and change parameters, change between groups etcetera.

29. ATWIN user interface
The ATWIN user interface guides the user to all network element parameters using a VT100 screen. The parameter names and the object – attributes relationship is exactly the same way as with TMA.

30. Web interface IP IP device Non-IP device Orchid Web browser
Attribute values
Actions window
Attributes
Objects
Group window
Buttons
Using the HTTP protocol, one can use any JAVA enabled web browser to connect to every network element. If the network elements have their own IP address (true IP devices or IP address assigned on Orchid 1003 LAN), one can browse straight to the network elements. If they do not have an IP address, you can browse first to the Orchid 1003 LAN. Within this session you can select the desired network element using its name.
The web interface allows maintaining interactively the network elements. All configuration, status, statistics and alarm information available in TMA is also available using a simple web browser.

31. SNMP MIB2 + standard traps system and interface groups supported
IP device
Non-IP device IP
SNMP station
Orchid
MIB2 + standard traps
system and interface groups supported
Private MIB + enterprise specific traps
maps completely to maintenance possibilities in TMA
each device has own private MIB
Each network element must have an IP address
SNMP MIB2
The Telindus network elements support MIB2 (RFC 1213) as far as the parameters are relevant. Most parameters are read-only. The following groups are supported: system, interface, ip
All 5 generic MIB2 traps (RFC 1215) are supported. These are coldStart, warmStart, linkDown, linkUp and authenticationFailure.
SNMP Private MIB
Each network element has its own private MIB. This private MIB maps completely with the device model information used by TMA. This includes also actions like making a test loop.
In addition to the 5 generic SNMP MIB2 alarms enterprise specific traps are defined that match exactly the TMA alarms. Each enterprise specific trap contains in its variable bindings amongst others a textual description of the alarm, the alarm severity level (the global alarm level of the network element) and the trap severity level (the alarm level for this specific alarm).
Some enterprise specific traps overlap with the generic MIB2 traps. The Orchid LAN does not send both traps. A configuration parameter selects for the overlapping traps whether MIB2 or Private MIB traps are sent.
A list of all stations to send traps to can be configured in the Orchid 1003 LAN.
SNMP security
SNMP uses the passwords defined in the network element as community strings. SNMP access can be inhibited by configuration in the Orchid 1003 LAN.

32. Ping Ping reply Ping request
IP device
Non-IP device IP
Ping station
Orchid
Ping reply
For non-IP devices: Orchid replies if it is in contact with the device
Each network element must have an IP address
Ping request
Available on IP devices
Ping packets are a simple way to see if an IP device can be reached. Ping requests sent to a network element’s IP address are replied by the Orchid 1003 LAN if the modem is reachable by the Orchid 1003 LAN. This means that ping requests are treated as if the modem itself responds.
True IP devices reply to ping requests if the interface having the destination IP address of the ping is up. True IP devices can launch themselves a ping request as well.
Like SNMP packets, ping packets can only be sent to network elements with an IP address.

33. TFTP, FTP and TML For configuration & firmware download TFTP/FTP
For use over IP network to Orchid concentrator or IP device
TML
Telindus Memory Loader
DOS program for local firmware download
TFTP and TML are both integrated in TMA
New configuration files and firmware images can be downloaded on true IP devices using TFTP over an IP network. TFTP is the Trivial File Transfer Protocol, a simple, yet solid file-transfer protocol.
The Orchid 1003 LAN has a file system. It contains the Orchid 1003 LAN configuration and model files for the connected network elements. Additionally configuration files and firmware images for connected network elements may also reside on the file system (see sections on configuration and firmware distribution/download). All these files may be downloaded and/or uploaded to the Orchid 1003 LAN over an IP network with TFTP.
TFTP for configuration and firmware download is not supported to the network elements without TCP/IP protocol stack directly. Instead configuration and firmware distribution to the network elements can be activated in the Orchid 1003 LAN by putting once the configuration or firmware file on the Orchid’s file system.
To download firmware via a serial interface straight to the AUX/CTRL connector of a network element (including the Orchid 1003 LAN), a proprietary file transfer protocol TML (Telindus Memory Loader) can be used. TML is a DOS program.
On network elements with Flash memory, TML is supported by the BOOT code, i.e. even if the Flash or loader code would become corrupted, it is still possible to locally download new firmware into the Flash memory with TML.
TFTP and TML are both integrated in TMA. They are used by the Download … option.
TFTP can be inhibited in the Orchid 1003 LAN and true IP devices.

34. TMA CLI What is it? Executable Command Line Interface
Serves to write scripts to automate management functions
CLI user interface syntax
Typically used in large networks
On Windows & Sun Solaris platforms
Comes with license key and maintenance contract
TMA CLI (Telindus Management Application Command Line Interface) is a Telindus product suited to write customised scripts with all the possibilities from the interactive TMA application. TMA CLI can be called from any scripting language as an executable. When running these scripts in background mode, some management activities may become fully automated or integrated with other management systems.
As an example, imagine one wants to keep the logging of the Bit Error Rate of all modems in the network on a daily base. With the Command Line Interface, a script can be written to gather the BER values of all the modems in the network once every 24 hours. These values can be appended to a file on disk. The results can finally be treated to give overall statistical information. This may be graphically presented using standard tools.
TMA CLI uses the same syntax as the CLI User Interface. This means it offers an easy to understand syntax with straight-forward rules. In addition it offers logging and file download. Finally writing scripts and running batch files is easier with TMA CLI than when a telnet session should be integrated.
TMA CLI is typically used in large networks to ease certain repetitive operations for the operators. An example is a line test by running a Remote Digital Loop (RDL) and Error Test (ET) and then reading the number of errors on the line. If this test is done interactively (e.g. using TMA or a telnet session), different actions must be taken and the operator should watch the test time. If this test is replaced by a TMA CLI script, the operator calls the script. If the script is finished, the resulting number of errors appears immediately on the screen.
TMA CLI comes with a licence key.

35. TMA Element Management applications
TMA Element Management (EM) applications
TMA EM common features
TMA Element Management
TMA for HP OpenView
TMA EM versions and support
TMA EM platforms
TMA EM system requirements

36. TMA Element Management (EM) applications
Two EM applications available
TMA Element management: stand-alone Element Management application, exist of
Element Manager
Element View
TMA for HP OpenView: Element Management application integrated on HP-OV NNM platform

37. TMA EM common features (1)
TMA Elm Mgt appl.
TMA application
Proprietary alarms IP
Alarms
Proprietary protocol (CMS2) for 100% reliability and optimal performance
Notification with user-selectable severity level
Alarm filtering towards event log
Alarm acknowledgement
Alarm synchronisation after connection fail
Alarm status view per device
TMA for HP OpenView is integrated with HP OpenView Node Manager. The modems are represented in the OpenView map as icons.
Alarms are reported into the Event log of the Node Manager and can change the colour of the icons on the HP OpenView maps.
Apart from the HP OpenView event log, alarms can also be stored in separate log file.
Before the alarms are forwarded, they can be filtered: TMA for HP OpenView forwards only alarms above a configured severity level. There are separate thresholds for forwarding to HP OpenView and the separate event log.

38. TMA EM common features (2)
Individual network element configuration & maintenance (TMA)
Security: each user login may correspond with a different password
TMA EM application automatically managing all devices defined in an Orchid concentrator
Name address resolution for TMA and TMA CLI
e.g. “TMA Haasrode” instead of “TMA ”
Using the right mouse key on the icon, the user can access the management functions of the selected modem in exactly the same way as with the stand-alone TMA application.
Each user login on the management station corresponds with a password. This password is used during TMA sessions to all the network elements in the network. This avoids that the user should enter his password for each TMA session. Different users may have different passwords with different rights.
Once HP OpenView has detected (through auto-discovery or by manual configuration) an Orchid 1003 LAN concentrator in the network, TMA for HP OpenView retrieves all the information on network elements, connected to the Orchid 1003 LAN and passes this information to HP OpenView. In this way all the Telindus network elements are very rapidly auto-discovered in HP OpenView.
Up to the 3 last configurations of each Orchid 1003 LAN are automatically backed up on the management station.

39. TMA Element Management: GUI Element View
Current alarms for selected device(s)
Device explorer window
Colour of device icon indicates alarm status
Alarm history for selected device(s)

40. TMA Element Management: additional features
Multiple Element Views (GUI) on different stations
Element View
represent the devices graphically in a hierarchical icon view
device icons indicate the alarm status of the device
has a window showing the current alarms and alarm history
can acknowledge and unacknowledge alarms
Is not a snmp tool
IP Element Discovery by entering IP address range*
Filtering and sorting of alarms in Element View*

41. TMA Element Management
Acknowledge
Acknowledged by

42. TMA for HP OpenView: GUI
HP OpenView sub-map
Right-click on icon for TMA and alarm status view

43. TMA for HP OpenView: additional features
Multiple console stations or use of X-terminal sessions
IP auto-discovery using SNMP and ping
Many other EM applications from other vendors run on the HP-OV platform
Using the right mouse key on the icon, the user can access the management functions of the selected modem in exactly the same way as with the stand-alone TMA application.
Each user login on the management station corresponds with a password. This password is used during TMA sessions to all the network elements in the network. This avoids that the user should enter his password for each TMA session. Different users may have different passwords with different rights.
Once HP OpenView has detected (through auto-discovery or by manual configuration) an Orchid 1003 LAN concentrator in the network, TMA for HP OpenView retrieves all the information on network elements, connected to the Orchid 1003 LAN and passes this information to HP OpenView. In this way all the Telindus network elements are very rapidly auto-discovered in HP OpenView.
Up to the 3 last configurations of each Orchid 1003 LAN are automatically backed up on the management station.

44. TMA EM versions and support
Demo (up to 8 devices): free
Entry level (up to 250 devices): licensed
Unlimited (>250 devices): licensed
Maintenance contract required
Free upgrades
Assistance via web-based interface

45. TMA Element Management Network Management Platform
TMA EM platforms
Application Software
TMA for HP OpenView
TMA Element Management
HP OpenView NNM
Network Management Platform
–6.X
6.1-6.X
6.4
7, 8
2000 / XP
2000 XP
Hardware / O.S. Platform
Sun Solaris
Windows
Sun Solaris
Windows
HP gives figures concerning the station hardware requirements in function of the number of network elements. The system requirements found there should be interpreted with care, because many parameters like the number of alarms and whether the network elements are IP devices strongly determine the processing needs. The additional processing and memory required for the TMA for HP OpenView application is limited.
Telindus has made tests and simulations for a modem network to determine the maximum modem network size for a single HP OpenView station. The HP OpenView station collects all information and presents it graphically on its console. No other Graphical User Interfaces (GUIs) are connected. Up to modems can be managedwith a single HP OpenView station.
One can propose the following hardware platforms for networks up to modems:
Windows NT platform Sun Solaris platform
Intel Pentium II or III 500MHz processor Sun Ultra 5 or 10
Windows NT 4.0 or Solaris 2.6, 7 or 8
Ram: 256MB Ram: 256MB
Free disk space: 600MByte Free disk space: 1GByte
If all the network elements have their proper IP address for SNMP management, the guaranteed number of network elements per HP OpenView station drops to 2500.
These figures are rather conservative compared to figures from HP. However above figures have been tested and deliver a good performing system. 69

46. TMA EM system requirements
Single management station with TMA EM application can manage over Telindus access devices
TMA EM applications can manage up to Telindus true IP devices on 1 station

47. Network management applications and integration with other platforms
TMA Inventory Management
TMA Path Management TDM
TMA integration with higher-layer platforms
NewBridge integration
TeMIP integration

48. TMA Inventory Management
Inventory management = central database keeps information regarding the network elements
TMA inventory management = add-on application to TMA Element Management applications
Goal: Outside network management platform extracts information
Communication protocol = CMS2
Any change generates an event to the outside application -> automatic trigger
The supported platforms are the same as for TMA Element Management
TMA Inventory Management automatically builds a database with a number of inventory parameters from each Telindus access device in the network. It retrieves the information automatically from the devices and the Orchid concentrators. All devices under TMA for HP OpenView are concerned. The database includes device information such as the name, the contact person, the location, the description, the unique identification code, the software version(s) and the available interfaces. Additionally the most recent configurations of all devices are stored as well.
The database information is accessible from an outside application, using the Telindus proprietary CMS2 protocol. This protocol uses the principles of CMIP and CORBA, thus making the integration with other network management platforms easier. TMA Inventory Management includes a complete protocol documentation. Once a session with an outside management platform is established, the outside application is automatically triggered of any database changes.
The database information is also available on the TMA user interface on the HP OpenView platform. Any changes can be logged in a file*.
The supported platforms are the same as for TMA for HP OpenView.
Subscription of a maintenance contract for TMA inventory management is required.

49. TMA Path Management TDM (1)
Active section
Passive section
Active section
ADM
SDH
Leased line
Mux devices in portfolio -> complete backbone extensions possible with only Telindus access devices
A single view on a complete TDM path
Both access and backbone equipment may be involved
Add-on application to TMA inventory management and TMA Element Management applications
For service and business management, an operator is interested in the quality and the use of a complete service. Examples of such services are a leased line service, a frame relay or ATM PVC. The operator wants also a simple and automated procedure to provision a service to a new customer into the network. This involves that all equipment involved in the path for this service is correctly configured.
With the advent of devices with TDM multiplexing features like Crocus SDSL Quad, Crocus DXC, Crocus ADM 2P and Crocus E3 mux, customers can build complete backbone extensions and even points of presence (POPs) with only Telindus access products. Along with this there is an increasing demand to manage not only all devices as separate entities (element management), but to manage as well the logical TDM connections within such network.
TMA Path Management is the answer to it. It is a software product for end-to-end management (network management) between different Telindus access devices. TMA Path Management is an add-on product to TMA for HP OpenView (element management) and TMA Inventory Management.

50. TMA Path Management TDM (2)
Features
Look-up of TDM paths over Telindus access devices
Provisioning of TDM paths between Telindus access devices*
Status view of the complete link
Performance view of the complete link
Alarm status of the complete link
Breakdown from the link view to detailed element view
Path alarm forwarding with SNMP or CMS2
User interfaces
TMA for administration
Web for operation & maintenance
Supported platforms: same as for TMA Element Management
Paths are defined by reference to their end points. For an existing path, TMA Path Management tries to find out the complete path given only the end points. It continuously monitors the path status and keeps related performance information for the last day, the last month and the last year. Changes in the path status are logged and may be forwarded as alarms to other platforms.
Path definitions may go beyond Telindus equipment. For this purpose, a path may consist of several sections. Each section may be active (i.e. across Telindus devices) or passive (i.e. across other devices). The figure gives an example of a leased line with 3 sections: 1 passive section in the backbone network and 2 active sections in the access network.
TMA Path Management provides also the possibility to completely provision a path. Provisioning results in the correct configuration of all the equipment along the path.*
TMA Path Management has 2 different user interfaces. For administration purposes (definition of the paths, configuration) the TMA user interface is available. For operation and maintenance purposes a web interface is available with click-through possibilities to the individual devices.
The supported platforms are the same as for TMA for HP OpenView.
Subscription of a maintenance contract for TMA path management is required.

51. TMA Path Management TDM (3)
TMA User Interface

52. TMA Path Management TDM (4)
Web Interface

53. TMA Path Management TDM (5)
Path View

54. TMA Path Management TDM (6)
Alarm View

55. Integration with higher layer platforms
Requirements and platforms vary greatly from one network to another
In almost every case, this requires specific developments
Options
TMA CLI: useful to gather specific attributes from the network elements or executing actions like making loops
Forward filtered alarms from HP OpenView NNM as SNMP traps
Alarm integration using Telindus protocol CMS2 over TCP/IP
CMS2 Uses the principles of ITU-T TMN
Less complex than a Q3 or a CORBA interface
Information from the add-on applications TMA inventory management and TMA path management can also be exchanged in this way
Build a Q3 or CORBA interface
Read TMA alarm log file at regular intervals

56. Integration with NewBridge 46020 (1)
NewBridge is a platform for path management of NewBridge equipment (NewBridge = Alcatel 5620)
This integration allows the element management of all Telindus equipment from the platform
Requires installation of openSNMP module + HP OpenView on platform
Two ways to see Telindus devices:
launch HP-OV map with Telindus devices from map
all HP-OV and TMA for HP-OV features are available on this map
with a command, the operator can copy the Telindus devices from HP-OV to the map
operator can make logical connections to NewBridge equipment
launching TMA from map is possible!
One can combine both ways

57. Integration with NewBridge 46020 (2)
NewBridge map
Logical link
Telindus device
TMA window launched
from icon

58. Integration with TeMIP
Telindus AM IP
TMA for HP OpenView
Alarm integration with TeMIP
Off-the shelf available as separate sales item from Compaq or Telindus partner
The HP OpenView TeMIP Access Module (AM) for Telindus TMA provides an interface between TeMIP and TMA. This access module supports basic fault management capabilities with a basic information model. It is a bi-directional module, which receives and processes unsolicited messages, as well as sends management commands (keep-alive messages, synchronisation commands) and receives associated responses.
TMA is directly interfaces to TeMIP by means of a combination of Management Modules and applications. It features the following capabilities:
·         Unsolicited messages support
·         Synchronisation commands
·         Automatic detection and reporting of communication failure (heartbeat)
·         Keep-alive message generation at configurable interval
·         Automatic alarm state resynchronisation after communication failure
This product is off-the shelf available from Compaq or from one of our partners.

59. These products are supported by TMA management applications:
Supported products
These products are supported by TMA management applications:

60. Conclusions Complete set of maintenance and management applications
All device types support the different applications
All applications support the complete attribute set of the devices
Manageable topologies very flexible
Extensive management information in the devices

61. Your network management solution