TMA management for Telindus access products - Route 66 ...

TMA management for Telindus access products1 IntroductionNetwork management becomes more than ever a competitive issue in networks, not only in thebackbone but also in the access network. Network management may help you saving costs in yourown organisation and delivering better services to your customers. Telindus as a modemmanufacturer has always given much attention to this. Therefore all Telindus access devices aremanageable. In management terminology these are called network elements. The type of networkmanagement Telindus provides is mainly Element Management. Telindus offers a variety of solutionsboth for the field engineer (maintenance) and for the operators and administrators on a centralNetwork Management System (NMS) under the global name TMA management. This refers to thespecific Telindus User Interface. However other tools such as SNMP, telnet and ping are also part ofthis solution.Telindus has additionally modules for inventory management and path management.What can you manage with the Telindus management solutions?The following is a non-exhaustive list of what you can achieve with the different Telindus managementsolutions:• Configuration of individual network elements and the complete access network.• Monitoring of individual network elements and the complete access network. In addition to typicalmonitoring, the network elements keep performance parameters for the last 2 hours and 24 hours.Recent device types keep also some performance parameters for the last 7 days. This preventivemonitoring greatly simplifies the task of diagnosing problems in the network.• Alarm collection and visualisation of the complete access network and detailed alarm visualisationof individual network elements.• Secured access of individual network elements and the complete access network.• Firmware upgrade of individual network elements and the complete access network.• Automatically keeping a network element’s configuration and/or firmware after hardwareswapping.• Integration with higher order network management platforms (network and service platforms).• Inventory ManagementThe operator or administrator on a central NMS station can achieve for the complete networkeverything the field engineer can achieve locally near the equipment for an individual network elementand much more.This document gives an overview of the different possibilities to manage Telindus access products.The next chapter explains the possible management network topologies in access networks. Thesucceeding chapter highlights features available for the different maintenance applications. The next 3chapters explain all the available management applications, including integration with othermanagement platforms. The last chapter lists the supported products and availability.Telindus Version 4.3 - 1 July 2004 6

TMA management for Telindus access productsvery efficiently the available bandwidth, a feature not provided by IP protocols. Network elements areconstantly being polled to see if alarm conditions are present. Alarm conditions are immediatelyforwarded to the network management system.A increasing number of Telindus devices do not need the Orchid management concentrator as amediation device. They have a direct IP interface and offer the same management protocols directly.These are typically the devices with an Ethernet interface. Examples of such equipment are theTelindus 1421 SHDSL Router and the Telindus 1030 Router Series. In the succeeding text, suchdevices are called true IP devices.Telindus Version 4.3 - 1 July 2004 8

TMA management for Telindus access products2.2 The Orchid management concentratorVersionsThe Telindus 1035 Orchid exists both in a desktop and a CN4 card version. The card version is theevident choice in concentration sites with card nests. The desktop version is the alternative in siteswith some dispersed desktop devices. The differences between these versions are further explainedbelow.Figure 2: Telindus 1035 TTFigure 3: Telindus 1035 CVI/O portsThe Telindus 1035 Orchid has the following I/O ports for connection to the management station andthe network elements:Port type Electrical interface Maximumspeed (kbit/s)Number of portsCTRL port DB9 DTE (asynchronous) V.24 9.6 1AUX port DB9 DCE (asynchronous) V.24 9.6 1E1 port RJ45 DTE G.703 2048 2RS530 port DB25 DTE V.10/V.11 10000 1TPI Ethernet port RJ45 IEEE 802.3 & 802.3u 100000 1HS high speed synchronous port RJ45 proprietary 800 1The purpose of the different ports is as follows:PortPurposeCTRL port • Connect TMA or VT100 terminal serially• Connect Desktop network elementsAUX port • Connect Desktop network elementsE1 and RS530 ports • Connect to an IP network with Frame Relay, PPP or ATM encapsulationHS port • Connect the Orchid to a card nestEthernet port • Connect to an IP LAN networkA desktop Telindus 1035 Orchid has 2 asynchronous ports for direct connection to desktop devices.To increase the number of connected desktop devices, an Orchid DM can be inserted. Alternatively anOrchid 1003 LAN TT can be used, which has 14 asynchronous ports.Telindus Version 4.3 - 1 July 2004 9

TMA management for Telindus access productsThe number of network elements the Orchid can concentrate depends on the chosen protocol and theaccess network topology. As a general rule however one Orchid can concentrate at least 250 networkelements. There is no limitation on the number of Orchids in the network.MemoryThe Telindus 1035 Orchid has 64MByte of RAM. It has 16MByte of Flash memory. This memory isorganised as a large memory bank, which includes one or two firmware images, the Orchid’sconfiguration file and optionally model files, configuration files and firmware files of connected networkelements.FTP, TFTP or the proprietary TML software can be used to download files into this file system.The Telindus 1035 Orchid management concentrator supports different types of IP encapsulation:MAC encapsulation over Ethernet and PPP, Frame Relay and ATM encapsulation over WANinterfaces. In this way, the Orchid management concentrator can be integrated in almost any networkarchitecture without having to build a separate overlay network for network management.Telindus Version 4.3 - 1 July 2004 10

TMA management for Telindus access products2.3 Concentrator - Network element connectionTwo types of connections exist between the Orchid management concentrator and the central networkelements:• low-speed asynchronous connections (e.g. 9.6 kbit/s) between the Orchid managementconcentrator and the desktop network elements• high-speed synchronous connections between the Orchid management concentrator and the cardversion network elementsIt is important to note that not only the immediately connected network elements are managed, butalso the ‘remote’ ones (e.g. central and remote modem of a link). In order to offer this functionality, anembedded low speed management channel is transported over the communication link, withoutaffecting the user data. The Orchid management concentrator uses this management channel tocommunicate with the ‘remote’ network element.2.3.1 Connecting desktops to the concentratorThe interconnection between the Orchid management concentrator and the network element isestablished through a low-speed asynchronous connection (e.g. 9.6 kbit/s). Up to 2 desktop networkelements can be directly connected to the Telindus 1035 Orchid (TT and CV). If you need to connectmore units, you can extend the number of ports with an Orchid DM (Digital Multipoint) as shown in thefigure. The Orchid 1003 LAN TT can directly connect to 14 desktop network units.Figure 4 - The Telindus 1035 Orchid TT can be combined with the Orchid DM to concentrate lowspeedmanagement connections2.3.2 Connecting cards to the concentratorThe communication between a card nest and the Orchid management concentrator is over a highspeedsynchronous connection up to 800 kbit/s. Up to 7 card nests can be managed with one TelindusOrchid 1035 CV.Figure 5 - The connection between a card nest and the Orchid management concentratorTelindus Version 4.3 - 1 July 2004 11

TMA management for Telindus access products2.3.3 Management extensionsOn sites with a limited number of network elements, the additional cost of a card nest and an Orchidmanagement concentrator and its connection to the central management system are high, comparedto the cost of the network elements. To reduce this cost extended links and digital multi-points onmanagement level are possible. For extensions on SDH and PDH networks, management can be sentover the Sa bits in time slot 0 of an E1 interface.Extended links and digital multi-pointsFigure 6 gives an example of such a network. Remote network elements may connect their CTRLconnector via a cross-cable to the CTRL connector of another network element. Alternatively remotenetwork elements may connect their CTRL connector to a Digital Multi-point’s main port. The other DMports are connected to the CTRL ports of other network elements on that site. Multiple extensions mayexist. The number of managed network elements behind one central network element (= networkelement directly or via the High Speed bus connected to the Orchid management concentrator) is onlylimited by the speed of the network element’s auxiliary channel. The more remote networks elementsconnected this way to a single network element at the concentrator site, the slower the response forthese network elements.The digital multi-point device from Telindus is called Orchid DM.This solution implies that Orchids 1003 LAN are only required on sites with card nests, because of theHS bus communication between the card nest and the concentrator.SDH/PDH extensionsFigure 6 - Management topology for extended linksFigure 7 - Management topology over a SDH / PDH networkFigure 7 shows a network topology with extensions on a SDH or PDH network. To offer services ondistant locations, without investing heavily in SDH or PDH nodes, a simple E1 add and dropmultiplexer or E1 Nx64K cross-connect with modem extensions may be a cheap alternative. If thenumber of devices is small on such site, their management is possible without a local Orchidmanagement concentrator.Telindus Version 4.3 - 1 July 2004 12

TMA management for Telindus access productsBy interconnecting the CTRL interfaces on the different devices (possibly through the use of an OrchidDM), 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 theSa bits in time slot 0 of their E1 interfaces. On the central side, the management information can beretrieved again from the Sa bits on a cross-connect or add and drop mux card and further transferredto the Orchid management concentrator card.The available bandwidth on the Sa bits is typically 1kbit/s. Therefore the number of devices connectedremotely in this way should be limited (typically up to 10). Interconnecting devices for management viathe CTRL port is in general possible on desktop units and not on card units. For the availability on cardunits, please contact Telindus.Sending management information over the Sa bits on a G703 interface requires the use of absoluteNMS addresses (see below) for all devices, managed in this way.2.3.4 Addressing modesThe Orchid management concentrator identifies each network element by its exit port and NMSaddress.The exit port includes whether the network element can be reached over the HS bus (the central unitis a card version) or an asynchronous port (the central unit is a desktop). In case of card versioncentral units, it includes also the card nest address, the card position and possibly the unit number onthe card.The NMS address is also used to identify the network element with the maintenance software TMAwhen it is connected to the NMS connector of a network element.The NMS address may be either relative or absolute. In relative addressing mode, the central networkelement gets relative address 0, the remote network element gets relative address 1. If extended linksexist, the next network element gets relative address 2 and so on. The figure below shows hownetwork elements are addressed from within TMA when TMA is connected to the NMS connector ofone of the network elements.Figure 8: Relative address exampleThe relative addressing mode requires no specific configuration per network element. The networkelement’s address depends on its relative position towards the network management application. Inmost access network topologies, relative addressing is applicable.In absolute addressing mode, each network element gets a unique NMS address in the range 0 to65535. Absolute addressing mode allows the use of Digital Multi-points as described above. Howeverthe network elements must be configured individually.Absolute and relative addressing modes can be mixed in a single network as shown below.Figure 9: Mixed relative and absolute address exampleTelindus Version 4.3 - 1 July 2004 13

TMA management for Telindus access products2.4 Concentrator - Network Management System connectionThe Orchid management concentrator supports a variety of protocols towards the NMS system. Itconverts the Telindus proprietary protocol CMS2 into the following protocols:ProtocolCMS2SNMPtelnetHTTPICMP request / replyCorresponding applicationsTMA, TMA CLI, TMA Element Management, TMA for HPOpenView, TMA Inventory Management, TMA Path Managementany SNMP browsertelnetweb interfacePingOther Telindus true IP devices such as Telindus 1030 Router Series, Telindus 14XX SHDSL Router…support the same management features directly over IP. Such devices do not require an Orchidmanagement concentrator. See the last chapter for a detailed overview of the Telindus accessdevices. All the above protocols can be transported over an IP network.For the standard IP protocols SNMP, telnet, HTTP and ping, the Orchid management concentrator isalso called a IP proxy device, because it responds to these protocols instead of the connected networkelements.Each Orchid management concentrator has got at least one IP address. Each other network elementmay also have an IP address, which is defined in the Orchid management concentrator.Advantages of assigning one IP address per network element are:• One can ping each network element• One can send SNMP requests to each network element and receive SNMP traps.Telnet sessions and web sessions do not require an IP address for each network element. In thiscase, one builds a session to the Orchid’s IP address and can make the appropriate selection to thedesired network element from within that session.Advantages of assigning only IP addresses to the Orchid management concentrator and devices withdirect IP access are mainly for large networks using the TMA for HP OpenView application:• The number of IP addresses is drastically reduced• More efficient bandwidth usage between Orchid management concentrator and the managementstation• Cost reduction in HP OpenView license if one uses TMA for HP OpenView managementTrue IP devices and the Orchid management concentrator send their management information usingthe protocols mentioned above over the IP network to the central management station. Depending onthe capabilities and available interfaces, the IP traffic is further encapsulated in Ethernet or a WANprotocol.EncapsulationMore infoEthernet MACFrame RelayRFC 1490 compliant. Compliance with LMI revision 1, ANSI T1.617 D and ITU-T.Dynamic mapping between IP addresses and DLCIs is based on Inverse ARP.Multiple DLCIs over a single interface.Telindus Version 4.3 - 1 July 2004 14

TMA management for Telindus access productsPPP RFC 1661, 1662 compliant. Synchronous PPP. Asynchronous PPP on V.24interfaces. CHAP and PAP authentication. Multi-link PPP and PPP fragmentation.ATMITU-T I.361 compliant. UNI 3.1/4.0. ILMI 3.1/4.0. UBR service class.On the Orchid management concentrator, one may define an internal IP address with its subnet mask.The latter serves as IP address pool for the connected network elements in case each one is assignedits proper IP address.Finally the Orchid management concentrator is also a full IP router. Routing features depend ondevice and firmware level.Telindus Version 4.3 - 1 July 2004 15

TMA management for Telindus access products3 General features3.1 Model conceptsFor management purposes Telindus access products are described in a standardised format. This iscalled the model of the product. Each Telindus access product has its own model file.The TMA management applications are generic. Also the telnet and HTTP servers in the Orchidmanagement concentrator are generic. This means that they all use the model files to translate theUser Interface into protocol language. When a new product becomes available, it is sufficient to installonly its model file to make it manageable.The SNMP private MIB parameters match also completely the TMA model files.The access product description in a model file uses the terms objects, attributes, groups andcontainment tree, which are all explained below.3.1.1 ObjectsThe management model consists of a number of items which we call objects. Objects can be seen asfunctional building blocks. Examples of such objects are crocusHDSLTT, nMS, nx64 ...The top object for the Crocus HDSL TT is called crocusHDSLTT. Each object may have child objects,i.e. objects below this level. Object nMS is a child object of object crocusHDSLTT. ObjectcrocusHDSLTT is the parent object of object nMS. Objects may occur several times. In that case theyget an index.3.1.2 AttributesEach object has attributes. An attribute is a unit of information regarding its object. It can be read.Configuration attributes can be modified as well. Action attributes are variables that can be used toinitiate a certain action. An example is the Activate Configuration attribute, which will make thenetwork element use new configuration data.Attributes can be primitive or complex. Primitive attributes are single variables such as integers,character strings and enumerated lists. Complex attributes are all variables that consist of multipleparameters. Tables are also complex attributes.3.1.3 GroupsEach attribute belongs to a group. The available groups are Configuration, Status, Performance andAlarms. Some examples:• All configuration parameters belong to the group Configuration• An interface being up or down, the software revision are Status attributes• Error counters are Performance attributes• The current alarms belong to the Alarms group3.1.4 Containment treeAn object may contain one or several child objects. Each of them may contain other objects and so on.The containment tree of a product shows the object relationships.In the reference chapters of the product specific manuals, you may find the containment tree with allobjects, attributes and attribute parameters listed per group. The same object, attribute and attributeTelindus Version 4.3 - 1 July 2004 16

TMA management for Telindus access productsparameter names appear in all the different User Interfaces, except for SNMP due to the nature of thisprotocol. For SNMP a name conversion list is available.3.1.5 Data files availabilityPer product the following data files are available:• A binary model file with extension .mod. These files include all the information regarding objectsand attributes that may be present in the device type. One ASCII file models.nms contains the listof all supported products. All TMA applications use these files, as well as the Orchid managementconcentrator for SNMP, HTTP and telnet management.• Bitmap files with extension .bmp and .def. These files are used for the TMA subsystem picture.• Private MIB files in ASN.1 format with extension .mib. SNMP browsers use these files.All these files are present on the TMA CD ROM, which is delivered with each Telindus access productthat supports TMA local management. The latest version of these files is at all times available on theTelindus web server http://www.telindusproducts.com.3.1.6 Model revision compatibilityWith new firmware revisions for a Telindus access product, new features may become availablerequiring changes to the model information. Different situations may occur:• Additional objects, attributes or management options become available. This implies a modifiedmodel that is fully compliant with the previous version. Most changes to the model informationbelong to this category.• Objects or attributes are changed or removed. This implies a new version of the model that is notfully compliant with the previous version.The binary model files contain the information for all the different versions of a Telindus accessproduct. When a TMA session is established, the version is exchanged prior to the device’scontainment tree. Therefore with the latest version of the TMA data files loaded on the networkmanagement station, the different firmware versions are compliant for all TMA applications. With thelatest version of the TMA data files loaded on the Orchid’s file system, telnet and HTTP sessionsremain supported when some connected units have a different firmware involving changes in themodel.Only scripts based on TMA CLI or SNMP may need to be adapted for new firmware versions of theproducts if objects or attributes involved in the scripts are changed or removed. TMA CLI scripts cancheck on the firmware version before proceeding with different code for the versions.Since SNMP does not support version control and only one MIB version can be loaded, a SNMPmanaged network using the private MIBs should only have firmware compatible products.Telindus Version 4.3 - 1 July 2004 17

TMA management for Telindus access products3.2 Communication protocolThe communication protocol between the Orchid concentrator and the network elements is aproprietary Telindus protocol, called CMS2. This same protocol is in use between the NMS station andtrue IP devices (including the Orchid concentrator). TMA also uses this protocol. It is optimised forusing minimal bandwidth. This allows good response times over slow auxiliary channels between amodem pair. The generic nature of this protocol is reflected in separate model files per networkelement type. They accompany the TMA software and the Orchid concentrator conversions.The CMS2 protocol has a built-in error correction, including retransmissions and timeouts for aguaranteed error-free communication. Once a CMS2 session has been opened, all data is encryptedin a proprietary way for enhanced security.The Orchid concentrator communicates with some older equipment in a former proprietary Telindusprotocol, called CMS. For these network elements the Orchid concentrator converts the former CMSprotocol into the CMS2 protocol.Network elements supporting the CMS and CMS2 protocol may be mixed on a single Orchidconcentrator. The only limitation is that all network elements that are attached to a singleasynchronous port or to a single card, use the same protocol.3.3 SecurityIn order to protect a network element against manipulations by unauthorised people, a list ofpasswords with associated access levels can be defined in the network element. All applications usethese 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 belowshows these access levels:AccessReadAccessWriteAccessSecurityAccessTestAccessFileAccessDescriptionA password that includes this access level allows reading all parameters, exceptsecurity items.A password that includes this access level allows changing all (configuration)parameters, except security items.A password that includes this access level allows reading and changing securityattributes. Typical security attributes are the password table and authenticationprotocol parameters.A password that includes this access level allows performing loop and other tests.This level is only present on recent device types.A password that includes this access level allows uploading and downloading files tothe file system of this device. This is only applicable on devices with a file system.In a large network, one can define different passwords. Below is an example.• 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.Telindus Version 4.3 - 1 July 2004 18

TMA management for Telindus access products3.4 Network element definitionThe Orchid management concentrator keeps a list of all connected network elements. This list iscalled the objectTable. Each network element is defined with the following parameters:ParameterNameExit port and NMS addressIP addressDescriptionTMA Element Management, TMA for HP OpenView and TMA InventoryManagement use this name.This defines the exact position of the network element towards the Orchidmanagement concentrator. It includes also whether a relative or absoluteNMS address is in use.This optional parameter makes the network element SNMP manageable.Additionally it may be pinged.The Orchid may auto-discover all card nest devices and their remote devices (in case of modems).Other network topologies are not automatically discovered (e.g. absolute addressed units, extendedlinks). Those devices should be configured in the list of connected network elements.On true IP devices one can access the device using any of its IP addresses.3.4.1 IP address assignment for proxied IP devicesThe Orchid management concentrator can optionally assign an IP address for each proxied networkelement. IP address assignment is mandatory if you want to SNMP manage or ping the networkelement.If no IP address has been assigned for a network element, it still is manageable over an IP networkwith the TMA applications, telnet and HTTP when accessible via the Orchid managementconcentrator. The TMA applications address then the network element with the IP address of theOrchid management concentrator combined with the Orchid’s exit port and NMS address values. Atelnet or HTTP connection is built first to the Orchid management concentrator. Within the telnet orHTTP session one can select each of the network devices defined in the Orchid.The IP addresses for the network elements either may belong to one of the subnets on one of itsinterfaces (e.g. Ethernet or port A interface) or to a virtual subnet. Virtual subnets can be definedinside the Orchid management concentrator. As an IP router the Orchid management concentratorroutes packets destined for an IP address on one of its virtual subnets to its own protocol stack. Thepacket is interpreted as a packet for the network element with the corresponding IP address.Telindus Version 4.3 - 1 July 2004 19

TMA management for Telindus access products3.5 Alarm tuning and filteringEach network element has an extended range of possible alarms. Since the user is not alwaysinterested in all these alarms, each alarm can individually be masked. If an alarm has been masked, itwill 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 thealarm. 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 number of severity levels in use on the management station, onecan 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 differentalarms per network element at 5 different levels.The following alarms exist on Telindus access products:Alarm name Description DefaultvalueDefaultlevelNotRespondingAlarmSyncLossConfigChangedAccessColdBootWarmBootThe alarm is active whenever the network element is notresponding to a poll from the Orchid management concentrator (forproxied devices) or a poll from the element managementapplication (for true IP devices), i.e. whenever it cannot beaccessed by the management system.This alarm indicates that the Orchid management concentrator (forproxied devices) or the element management application (for trueIP devices) and the network element are no longer synchronisedon alarm level (their alarm counters do not match any more). Thismay be due to lost contact or communication errors.The network element sends this alarm when the configuration hasbeen changed.This alarm is active when a telnet, a HTTP or a TMA session isactive.This alarm will not arise when connecting via the CentralManagement System or via one of the ports of the Orchidmanagement concentrator.Each time the network element reboots completely, this alarm isgenerated. Rebooting may occur due to power drop or the actionCold Boot.Each time the network element reboots for another reason, thisalarm is generated. This may occur after configuration changes orwhen an internal error has been detected.enabled 4enabled 4disabled 1disabled 1disabled 1disabled 1LinkDown This interface related alarm is active if the interface is not up. enabled 3On some central office devices, the alarms can also be forwarded to tension-less alarm contacts, if nocentral management is in use. Two alarm contacts are available: a high alarm contact and a low alarmcontact. These alarm contacts may be connected to a visible or audible alarm circuit, e.g. a bell or aTelindus Version 4.3 - 1 July 2004 20

TMA management for Telindus access productslamp. All alarms can - independently from the NMS alarm masks – be filtered before sending them toone of the alarm contacts.When using the TMA Element Management or TMA for HP OpenView application, the alarms canfurther be filtered in this application for different purposes. See TMA Element Management sectionAlarm management.To avoid alarm overload on the management station, the Orchid management concentrator delays itscommunication with the TMA Element Management application at boot time for a configurable timeinterval. This allows the Orchid management concentrator to synchronise communication first with itsconnected devices before sending alarms. The advantage of this is that all ‘loss of contact’ alarms donot occur. Afterwards only real alarm state differences for the connected devices are passed to theTMA management application. The Orchid management concentrator sends of course an alarm forbeing available again.Telindus Version 4.3 - 1 July 2004 21

TMA management for Telindus access products3.6 Preventive monitoringIn addition to the monitoring of the actual status and absolute performance parameters of a networkelement, the network elements keep also performance parameters for the last 2 and 24 hours. Recentdevice types also include performance parameters for the last 7 days. This preventive monitoringgreatly simplifies the task of diagnosing problems in the network. Such performance values are incompliance with relevant ITU-T recommendations.One may consider 3 types of absolute performance parameters:TypetimecounterstatusDescriptionA value expressed in time units since last boot.This counts the number of times an event has occurred since last boot.The current value or status of a parameter.For each of these types corresponding values exist for the last 2 hours, 24 hours and 7 days.Over the last 2 hours 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.Over the last 7 days 7 values represent the parameter values for each 24 hours period.Depending on the parameter type, the following values are available for the last 2 hours, 24 hours and7 days period:TypetimeDescriptionA value expressed in time units during the 15 minutes, 2 hours or 1 day period. E.g.the time an interface is up.counter A counter indicating the number of times an event has occurred during the 15minutes, 2 hours or 1 day period. E.g. how many times an interface did go down.statusThree values are kept per time interval: minimum, maximum and average values.E.g. Signal/Noise ratio.If on the management station detects that a modem line has dropped, one can look at the different lineparameters on the central modem during the last 2 hours, 24 hours or 7 days. Probably an accuratediagnosis of the problem can be found within minutes by looking at these historical performancevalues.Telindus Version 4.3 - 1 July 2004 22

TMA management for Telindus access products3.7 Configuration and Firmware management on the Orchidmanagement concentrator3.7.1 The Orchid’s file systemThe Orchid management concentrator comes with a file system. This memory is used for differentpurposes:• To store its firmware code• To store its configuration in binary format.• To store configuration and firmware image files for the connected devices.You can list the files on the file system. Individual files can be deleted or renamed. You can store fileson the file system using TFTP or FTP (Telindus 1035) over an IP network or using the TML DOSpackage. Both packages are also integrated in the TMA user interface.3.7.2 Configuration distributionIn networks with many network elements, experienced network administrators may want to slightlychange configurations (e.g. changed alarm masks or levels) for large numbers of network elements foroptimal network management behaviour. In a modem network typically only a limited number ofdifferent configurations exist. Instead of sending new configurations individually from the networkmanagement station to each network element, one can send each configuration once to each Orchidmanagement concentrator and tell them to distribute the configurations to individual network elements.The latter is more efficient in terms of bandwidth and time consumption.Figure 10: Configuration distributionOnce the configurations are stored on the Orchid’s file system, you can tell the Orchid managementconcentrator also e.g. to send configurations to network elements that are being installed.If the Orchid management concentrator fails to send a configuration to a network element, it tries up to3 times. Per network element one can check whether the configuration download succeeded or not.3.7.3 Firmware distributionMost Telindus access devices store their code in Flash memory. This offers the possibility to upgradethe code without opening the box. In many cases it is even possible to upgrade code from the centralmanagement station.Telindus Version 4.3 - 1 July 2004 23

TMA management for Telindus access productsIf a firmware upgrade is desired, many network elements may be involved in the network.Downloading code to each network element individually from the central management station may bea very time-consuming task, since firmware code size is much bigger than configurations are.Similarly to configuration distribution, one can send a new firmware code once to each Orchidmanagement concentrator and tell them to distribute it to the individual network elements. This freesthe network management station mostly from the time-consuming task to upgrade firmware.If the Orchid management concentrator fails to send a firmware code to a network element, it tries upto 3 times. Per network element one can check whether the firmware download succeeded or not.There are some limitations to firmware distribution:Figure 11: Firmware distribution• On some modems it is not possible to send new firmware to the remote modem due to limitedbandwidth in the auxiliary channel.• Firmware distribution is not possible to links with desktop network elements on the central side(connected directly to the Orchid management concentrator).• Firmware distribution is not possible on extended links, due to too large delays.Telindus Version 4.3 - 1 July 2004 24

TMA management for Telindus access products3.7.4 Configuration consistencyDuring the installation of network elements, it is desirable that configurations can be prepared centrallybefore the network elements have been installed and that these configurations are downloaded intothe network elements whenever they get connected. Similarly, whenever a unit is replaced, it isdesirable that the service engineer does neither need to completely reconfigure the unit locally nor thatthe central management operator needs to take specific actions at the time of installation.Figure 12: Configuration consistencyIn most central network management solutions, configuration management is one of the tasks to easeinstallations and replacement. In networks with Telindus access devices, the Orchid managementconcentrator does most of this task. The result is a more efficient control since each Orchidmanagement concentrator needs only to watch a smaller number of network elements than the centralmanagement station.Similar to the distribution, the configuration file is stored on the Orchid’s file system. After a loss ofcontact and after each configuration change, the Orchid management concentrator compares theconfiguration file on its file system with the configuration of each network element under consistency. Ifconfigurations do not match, the Orchid management concentrator starts downloading theconfiguration to the network element. If downloading fails, it tries up to 3 times to download again. If itstill fails, the Orchid management concentrator proceeds to the next network element. Theconsistency status is continuously available per Orchid management concentrator on the managementstation.On network elements under consistency, it is not possibly to change the configuration in any other waythan by changing the configuration file on the Orchid’s file system.Telindus Version 4.3 - 1 July 2004 25

TMA management for Telindus access products3.7.5 Firmware consistencyFigure 13: Firmware consistencyTo have a completely consistent behaviour of all network elements in a managed network, networkoperators sometimes require that all network elements have exactly the same firmware code. On theOrchid management concentrator concentrator, one can configure which firmware version eachnetwork element should have. The Orchid checks on a regular time interval whether the firmwareversion on each network element under firmware consistency matches the firmware version on its filesystem. If firmware versions do not match, the firmware version on the Orchid is downloaded to thenetwork element.Similar restrictions apply as for the firmware distribution. Also a minimum firmware version may berequired on the network elements for firmware consistency.Telindus Version 4.3 - 1 July 2004 26

TMA management for Telindus access products3.8 Management by multiple stationsThe Orchid management concentrator is designed to allow maintenance and management by multiplestations:• A total of 30 simultaneous TMA, telnet, HTTP, CLI, ATWIN and TMA CLI sessions are possible todevices connected to a single Orchid management concentrator. This includes also TMA sessionsinitiated on a TMA Element Management application.• A total of 30 simultaneous TMA, telnet, HTTP, CLI, ATWIN and TMA CLI sessions are possible onan Orchid management concentrator. This includes also TMA sessions initiated on a TMAElement Management application.• The Orchid management concentrator can send SNMP traps to a large number of SNMP stations.This is only limited by the RAM memory.• Different stations can send SNMP and ping requests simultaneously. The Orchid managementconcentrator handles them serially. The number of simultaneous SNMP and ping requests is onlylimited by the processing power and RAM memory.True IP devices are designed to allow maintenance and management by multiple stations:• At least 5 simultaneous TMA, telnet, HTTP, CLI, ATWIN and TMA CLI sessions are possible totrue IP devices. This includes also TMA sessions initiated on a TMA Element Managementapplication.• True IP devices can send SNMP traps to a large number of SNMP stations. This is only limited bythe RAM memory.• Different SNMP stations can send SNMP and ping requests simultaneously. True IP deviceshandle them serially. The number of simultaneous SNMP and ping requests is only limited by theprocessing power and RAM memory.Telindus Version 4.3 - 1 July 2004 27

TMA management for Telindus access products4 Element maintenance applicationsIn this chapter the basic applications to maintain and manage Telindus network elements aredescribed. The table lists all supported element maintenance and management applications:ApplicationRemarksTMAHand terminalCLI and ATWINtelnetWeb (HTTP)SNMPFTP, TFTP and TMLFTP and TFTP is only used for the Orchid management concentrator and thetrue IP devices.PingTMA CLITMAManagementElementTMA Element Management offers a complete stand-alone elementmanagement solution for Telindus network elements. It is described in the nextchapter.TMA for HP OpenViewTMA for HP OpenView offers a complete element management solution forTelindus network elements, integrated in the HP OpenView NNM managementsuite. It is described in the next chapter.Telindus Version 4.3 - 1 July 2004 28

TMA management for Telindus access products4.1 TMATMA (Telindus Maintenance Application) is a free Windows ® software for the complete control oflocally and remotely installed Telindus access equipment. The system offers not only the configurationof the equipment, but it includes also the creation of configuration profiles stored on the hard-disk, acompletely interactive picture of the connected device, real-time monitoring, interrogation and exportof status and performance parameters, test-loop, etcetera.4.1.1 Feature overviewTMA features the following:Figure 14 TMA application• Establishment and termination of the connection with an equipment (either local or remote)• Password protected access and permanent session identification• Reading and changing configuration of the equipmentTelindus Version 4.3 - 1 July 2004 29

TMA management for Telindus access products• Retrieving status information (current operation) of the equipment, including the current alarmstatus• Retrieving statistical information on the network element (e.g. covering a period of 24 hours)• Diagnostic tests• Configuration storage and retrieval on hard-disk in binary and ASCII format• Status and statistics storage on hard-disk• Software download to equipment with flash-memory (software upgrades)• Interactive subsystem picture reflecting the equipment and the status of indicators and pushbuttons• Subsystem picture can be customized to user’s needs• TMA can be called from a command line with parameters• Tables can be sorted by clicking on column headers• Structured types can be expanded by clicking on the right arrow in the column header• Rows in tables can be filtered. Wildcards can be used when filtering character strings• Customised value editing: string parameters can be customized to enumerated values list4.1.2 Making a TMA connectionA PC running TMA software can be connected in several ways with the network element. The tablegives an overview of the most common topologies:1 One possibility to make a maintenanceconnection to a device is a straight serial cablebetween the network element and the PC. It willprovide the TMA access to the local and remotenetwork element (including also possibleextensions of the link)(modem example).2 Another topology connects the PC via a straightserial cable with an Orchid managementconcentrator. Each network element connectedto the Orchid management concentrator canthen be reached with TMA. This extends themaintenance access to a large number ofnetwork elements from one central location.3 The previous topology can be extended over aPSTN or ISDN network. The telephone numberselection is integrated in the TMA connectwindow. This extends the maintenance accessfrom one central location to a complete network.4 Over an IP network TMA can access all thenetwork elements with an IP address. If thenetwork elements have no individual IP addressstill it is possible to contact them using theOrchid’s IP address combined with the path tothe network element.Telindus Version 4.3 - 1 July 2004 30

TMA management for Telindus access products4.1.3 Ease of UseIn the development of the software package, user-friendliness and ease of operation were set asprimary design goals. This resulted in features like a menu navigation window, selection betweenbasic and advanced views, MRU (Most Recent Used) list of connected equipment for a fast selectionof the desired equipment to connect to, interactive picture, table sorting, table expansion, tablefiltering, customized value editing etcetera.The pictures below show some details:Figure 15: Interactive pictureFigure 16: Table sortingFigure 17: Equipment statisticsFigure 18: Customised value editingIn larger networks, TMA can be used simultaneously with a central management system. It allows anoptimal interaction between network operator and field-engineer, since the user interface is the same.TMA is the ideal support tool for the field-engineer, optimising the speed and efficiency of theinstallation. The software is delivered with the equipment, and at all times, the latest version can bedownloaded from the Telindus web-site.4.1.4 Customised Interactive Sub-System Picture (TMA ISSP)One can customise the Interactive Subsystem Picture within TMA with extra information to focus theattention of field technicians and operators to the parameters, essential for their application. By doingso, one doesn’t need any more the generic TMA user interface with its complete set of allconfiguration, status, performance and alarm parameters.Telindus Version 4.3 - 1 July 2004 31

TMA management for Telindus access productsFigure 19: Customised Interactive Sub-System Picture Figure 20: Customised'Configuration' windowWhen starting TMA, one immediately selects the ISSP button and gets the interactive subsystempicture. When clicking on LEDs or interfaces, one may get related information. This relatedinformation is defined in a .usr file in the TMA directories. That file is an ASCII file with commands,described in the TMA manual. It can be edited and completely customised. Figure 19 shows anexample of an TMA ISSP for the Telindus 1421 SHDSL Router with 2 extra buttons compared to thestandard TMA ISSP. When selecting the ‘Configuration’ button, a new window is opened where onecan define some specific parameters of the device (see Figure 20). The text can be completelyadapted to the user’s needs (e.g. different languages). The ‘Ping’ button allows sending pings andseeing the results.A typical deployment scenario for operators using the customised TMA ISSP is the following:1. The operator pre-configures the devices with all its parameters common to the service. This canbe accomplished with a simple configuration file download to all devices.2. The pre-configured devices are kept in the operator’s stock.3. The operator creates a customised .usr file and copies it on the PCs of the technicians.Alternatively the operator delivers the .usr file with the equipment to customer and givesinstructions for the installation (self-installation).4. At installation, the technicians or the customers only need to fill in the parameters that are differentfrom one installation to another.4.1.5 Minimum system requirementsThe minimum system requirements for TMA are:• Operating System MS Windows95 ®, Windows 98 ®, Windows NT 4.0 ® , Windows 2000 or WindowsXP• 100 MByte free hard-disk space• 16 MByte RAM on Windows 95/98, 32 MByte RAM on Windows NT 4.0, Windows 2000 orWindows XP• CD ROM drive (unless it is downloaded from the Telindus web server)• One serial communication port and/or Ethernet port• MouseTelindus Version 4.3 - 1 July 2004 32

TMA management for Telindus access products4.2 EasyConnect hand terminalCustomers without laptop for eachtechnician find a good alternative in theEasyConnect hand terminal for localmaintenance of Telindus accessproducts. This product has a LCDdisplay with 2 lines and each 24characters and 6 navigation buttons. Itconnects using a serial cable to theCTRL connector on Telindus accessdevices (both card and desktop units).All the information available with theTMA and ATWIN user interfaces isavailable as well on this hand terminal!Additionally, on some new equipment,shortcuts are available to basic statusinformation and loop tests.The EasyConnect hand terminal has a file system. One can store and remove files on this file systemusing TMA or TML. For that purpose the PC’s COM port is connected to the hand terminal via theserial interface. One needs the model file of the device types under maintenance on this file system.However on new devices, while connecting, the EasyConnect hand terminal retrieves itself the modelfile from the device if it is not yet available or an older model file version is present on its file system.Additionally one can store configuration files and firmware images on the file system first anddownload them afterwards to a connected device.*The EasyConnect hand terminal has a rechargeable battery with included power adapter and anON/OFF button. When there is no activity during a certain period, the unit goes into power-save mode.The EasyConnect hand terminal is supported on the products as mentioned in the last chapter.Telindus Version 4.3 - 1 July 2004 33

TMA management for Telindus access products4.3 CLI and ATWINCustomers without TMA or a windows based laptop have, besides the use of a dedicated handterminal, still another way to configure and maintain locally a Telindus access device. One canconnect a simple VT100 terminal (using its serial port) or a PC with VT100 terminal emulation (usingits COM port) to the CTRL port of a Telindus device using the same cable as used for TMA.Once connected, one has 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 bestsuited for novice users.• CLI: this is a Command Line Interface. Knowing the syntax, you can more quickly access thenetwork elements than with the ATWIN interface. This is best suited for experienced users.These user interfaces allow the interactive maintenance of network elements. All configuration, status,statistics and alarm information available in TMA is also available using a CLI or ATWIN session. Onecan tune the number of lines and columns on the screen to its needs.In the last chapter you may find which products support the CLI and ATWIN user interfaces on theirCTRL port.In the succeeding sections, the ATWIN and CLI user interfaces are explained in further detail.4.3.1 ATWIN interfaceFigure 21: ATWIN User Interface exampleThe 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.4.3.2 CLI interfaceThe Command Line Interface uses the same parameter names and object – attributes relationship asTMA does. A generic syntax allows to read and change parameters, change between groups etcetera.The example below shows how the complete configuration of a Crocus HDSL TT modem can be readin CLI format (only those parts are shown that appear also in the ATWIN and TMA examples):/crocusHDSLTT:”Edit Configuration”>get –rGET{Telindus Version 4.3 - 1 July 2004 34

TMA management for Telindus access productsLIST{sysName =sysContact =sysLocation =security ={}forwardTMAToNMSPort = enabledforwardTMAToLine = enabledbootFromFlash = AutoalarmLevel ={NotResponding = 4…}…}SELECT modem{LIST{retimingBuffer = short…}SELECT line[1]…SELECT line[2]…SELECT nMS…SELECT router…SELECT nx64…SELECT g703OnBoard…}OK/crocusHDSLTT:”Edit Configuration”Figure 22: CLI User Interface exampleTelindus Version 4.3 - 1 July 2004 35

TMA management for Telindus access products4.4 TelnetTelnet is a standard IP protocol to connect a terminal to a computer. You can use telnet to connectany terminal or terminal emulation program to every network element via the Orchid managementconcentrator. If the network elements have their own IP address, one can make a direct telnet sessionto the network elements. If they do not have an IP address, you can make first a telnet session withthe Orchid management concentrator. Within this session you can select the desired network elementusing its name. Telnet is also available on all true IP devices.Once connected, the telnet session leaves the choice for the ATWIN and CLI user interfaces. Itbehaves exactly the same as with the local CLI and ATWIN user interfaces.Telnet access can be inhibited by configuration in the Orchid management concentrator and the trueIP devices. The Orchid management concentrator needs the TMA model file per device type on its filesystem to support telnet for the connected devices.Telindus Version 4.3 - 1 July 2004 36

TMA management for Telindus access products4.5 Web interfaceUsing the HTTP protocol, one can use any JAVA enabled web browser to connect to every networkelement. If the network elements have their own IP address (true IP devices or IP address assignedon Orchid management concentrator), one can browse directly to the network elements. If they do nothave an IP address, one can browse first to the Orchid management concentrator. Within this sessionone 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 web browser.Figure 23: Web interfaceWhen using Internet Explorer version 5.0 or higher, one gets the best graphical results. Any JAVAenabled browser however gives a good result. Information is retrieved from the device per object. Thisgives the fastest results for browsing within an object.Web access can be inhibited by configuration in the Orchid management concentrator or on the trueIP devices. The Orchid management concentrator needs the TMA model file per device type on its filesystem to support HTTP.Telindus Version 4.3 - 1 July 2004 37

TMA management for Telindus access products4.6 SNMPThe Simple Network Management Protocol is a de facto standard protocol for network management.Since SNMP requires a lot of bandwidth, SNMP is not present in the Telindus network elementswithout LAN interface. Instead the Orchid management concentrator serves as a SNMP proxy server:it translates the SNMP messages into the Telindus proprietary protocol and vice versa. To do so, itneeds the TMA model file per device type on its file system. Using SNMP each network elementneeds its own IP address. The IP addresses are configured in the Orchid management concentrator.True IP devices support SNMP directly.The SNMP protocol uses Management Information Bases (MIBs) describing the product. This can becompared with the model files used by TMA. The Internet Community standardised one generic MIB(MIB2) for general use in all equipment. Telindus network elements support both MIB2 and a privateMIB.4.6.1 MIB2The Telindus network elements support MIB2 (RFC 1213) as far as the parameters are relevant. Allparameters are read-only. The following groups are supported:GroupsysteminterfaceipDescriptionThis group contains general information regarding the network element like the system name.This group contains information regarding the different equipment interfaces. Single portmodems e.g. have 2 interfaces: the line interface and the digital interface (V.24, V.35,X.21…). Here one can read e.g. whether the interface is up or down.This group contains the IP related information: the ipAddrTable, ipRouteTable and theipNetToMediaTable are supported. This group is of course only present on true IP devices.The generic MIB2 traps (RFC 1215) coldStart, warmStart, linkDown and linkUp are supported.4.6.2 Private MIBEach network element has its own private MIB. This private MIB maps completely with the devicemodel information used by TMA. This includes also actions like making a test loop. The private MIBsare delivered as part of the TMA model files package.In addition to the generic SNMP MIB2 alarms enterprise specific traps are defined that match exactlythe TMA alarms. Each enterprise specific trap contains in its variable bindings amongst others atextual 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).4.6.3 TrapsSome enterprise specific traps overlap with the generic MIB2 traps. The Orchid managementconcentrator / true IP devices do not send both traps. A configuration parameter selects for theoverlapping traps whether MIB2 or Private MIB traps are sent. A list of all stations to send traps to canbe configured.4.6.4 SNMP community stringsSNMP uses the passwords defined in the network element as community strings. SNMP access canbe inhibited.Telindus Version 4.3 - 1 July 2004 38

TMA management for Telindus access products4.7 TFTP, FTP and TMLTrue IP devices have a file system. New configuration files and firmware images can be downloadedon the file system using FTP or TFTP over an IP network. TFTP is the Trivial File Transfer Protocol, asimple, yet solid file-transfer protocol. Recent true IP devices have also a FTP server running. FTP isthe standard TCP/IP File Transfer Protocol.The Orchid management concentrator has also a file system. Similarly configuration files, firmwareimages and model files for the Orchid and its connected devices can be stored on the file system withFTP or TFTP.TFTP and FTP are not supported to the network elements without an own IP protocol stack. Insteadconfiguration and firmware distribution to the network elements can be activated in the Orchidmanagement concentrator by putting once the configuration or firmware file on the Orchid’s filesystem.To download firmware via a serial interface to the AUX/CTRL connector of a network element(including the Orchid management concentrator), a proprietary file transfer protocol TML (TelindusMemory Loader) can be used. TML is a DOS program.On network elements with Flash memory, the BOOT code supports TML, i.e. even if the Flash orloader code would become corrupted, it is still possible to locally download new firmware into theFlash memory with TML.The configuration files on the file system are in binary format. FTP, TFTP and TML only can downloadbinary configuration files on the file system. TMA allows downloading (and uploading) configurationfiles in ASCII format: TMA converts the ASCII file format into binary format and vice versa.TFTP and TML are both integrated in TMA. They are used by the Download … option.TFTP and FTP can be inhibited in the Orchid management concentrator and true IP devices.Telindus Version 4.3 - 1 July 2004 39

TMA management for Telindus access products4.8 PingPing packets are a simple way to see if an IP device can be reached. The Orchid managementconcentrator replies on ping requests sent to a network element’s IP address if the network element isreachable by the Orchid management concentrator. This means that ping requests are treated as ifthe network element responds itself.True IP devices reply to ping requests if the interface having the destination IP address of the ping isup. 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.Telindus Version 4.3 - 1 July 2004 40

TMA management for Telindus access products4.9 TMA CLITMA CLI (Telindus Management Application Command Line Interface) is a Telindus product suited towrite customised scripts with all the possibilities from the interactive TMA application. TMA CLI can becalled 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 managementsystems.As an example, imagine one wants to keep the logging of the Bit Error Rate of all modems in thenetwork on a daily base. With the Command Line Interface, a script can be written to gather the BERvalues of all the modems in the network once every 24 hours. These values can be appended to a fileon disk. The results can finally be treated to give overall historical information. This may be graphicallypresented using standard tools.TMA CLI uses the same syntax as the CLI User Interface. This means it offers an easy to understandsyntax with straightforward rules. In addition it offers logging and file download. Finally writing scriptsand running batch files is easier with TMA CLI than if a telnet session should be integrated.TMA CLI is typically used in large networks to ease certain repetitive operations for the operators. Anexample is a line test by running a Remote Digital Loop (RDL) and Error Test (ET) and then readingthe 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 a TMA CLI scriptreplaces this test, the operator calls the script. If the script is finished, the resulting number of errors isimmediately available.TMA CLI is available on the following platforms:Hardware platform Revision(s) Recommended for new installationsSun Solaris 2.6, 7 and 8 7 and 8HP-UX 10.20 and 11.X NoneWindows 95, 98, NT4.0, 2000 and XP 2000, XPTMA CLI comes with a licence key.Telindus strongly recommends the subscription of a maintenance contract for TMA CLI. Themaintenance contract includes telephone advice and assistance concerning the operation of TMA CLI.The service is provided during office hours Central European Time. Additionally one gets automaticallynew releases for TMA CLI.The maintenance contract is initially for 3 years with a yearly fee.Telindus Version 4.3 - 1 July 2004 41

TMA management for Telindus access products5 TMA Element Management applications5.1 IntroductionTelindus has 2 element management applications:• TMA Element Management is the stand-alone element management application• TMA for HP OpenView is the management application running on the widely spread networkmanagement platform HP OpenView Network Node Manager (NNM).Both applications share the common software for communication with the network elements and themanagement of alarms. Key common features include:• Guaranteed reception of alarms from the network elements• Optimised alarm processing• Alarm history• Alarm acknowledgement• Alarm synchronisation after connection loss• TMA and TMA ISSP initiation with a click on the device iconThe applications differ in the graphical network presentation to the user.TMA Element Management represents the network elements and maps in a way similar to how foldersand files can be represented in Microsoft’s Windows Explorer on a PC. The icons have the colour ofthe actual alarm status of each device. Map icons have the colour of the overall alarm status of alldevices on the map. When selecting an icon, the actual alarms and alarm history of the selected mapor device are shown.HP OpenView represents the network elements in the OpenView map as icons. Several icons exist fordifferent Telindus products. The icons have the colour of the actual alarm status of each device.Alarms are reported into the Event log of the Node Manager and can change the colour of the iconson the HP OpenView maps. In addition HP OpenView has a number of additional features like autodiscoveryand SNMP polling, which are not present on the stand-alone version.This chapter first describes the common features of both element management products. Then somespecific issues for both products are highlighted. Finally versions, platforms, system requirements andsupport conditions are discussed.Telindus Version 4.3 - 1 July 2004 42

TMA management for Telindus access products5.2 Common element management features5.2.1 Alarm managementAlarm handlingWhen an alarm is reported, the colour of the related icon on the Element Management maps changesaccordingly. One can see the list of all active alarms per Telindus network element. The alarm historyis also logged and can be stored in an ASCII log file. The log file uses TAB separated fields. Per alarmthe time stamp, the alarm level, the device’s name and alarm description are given, as well as theduration of the previous alarm status.Telindus devices send their alarms to the Element Management application in a proprietary format(possibly through the Orchid management concentrator). This has the following advantages overSNMP traps:1. A guaranteed alarm delivery2. Because the alarm handling is optimised, many more network elements can be managed on asingle management station, there are lower delays to make alarms visible on the network mapsand the start-up time is drastically reduced.3. A number of additional features like alarm acknowledgement and alarm synchronisation areavailable (see below).Alarm filteringEach network element has a wide range of possible alarms. Each alarm can be masked and assigneda severity level on the network element. All unmasked alarms are sent to the Element Managementapplication with their severity level.The Element Management application can forward the alarms. Before they are forwarded, the alarmscan be filtered based on their severity level. Only alarms above a configured severity level areforwarded. There are separate thresholds for forwarding to• HP OpenView (only on TMA for HP OpenView)• The event log file• Other management stations*Two measures are taken to avoid alarm overflow on the Element Management application:• If an alarm state toggles more than a configurable number of times within a configurable timeinterval, for all succeeding state toggles the alarm will only be logged once with the additionalindication ‘streaming’.• The alarm exchange between the Element Management application and the network elements isconnection-oriented: each alarm message is acknowledged, the protocol uses a window size andcorresponding flow control. This means that if one or several devices start sending an alarm burst,the Element Management application cannot get flooded with alarms.Alarm acknowledgementOne can acknowledge each alarm within the Element Management application. The impact on theicon colour can be configured. Two options are available:1. Acknowledged alarms remain visible in the icon colour.2. Acknowledged alarms are no more visible in the icon colour.Telindus Version 4.3 - 1 July 2004 43

TMA management for Telindus access productsThis selection can be combined with specific map settings within TMA Element Management and TMAfor HP OpenView. For details see the specific sections. Acknowledging an alarm is also logged in theASCII log file.Alarm synchronisationThe polling between the Element Management application and the true IP devices or the Orchidmanagement concentrators and between the Orchid management concentrators and the proxiedTelindus access devices are session oriented. This means that each management component knowswhen it looses connection with the other one.Alarm synchronisation means that each of the above management components is in permanentcontact with the other one. When the contact is established again after a loss, all the relevantinformation is exchanged again to have a correct view of what happened on the management station.• For a loss of contact between an access device and the Orchid management concentrator, thismeans that the Orchid management concentrator sends the alarms notResponding andalarmSyncLoss for those devices.• After a reboot of true IP devices or the Orchid management concentrator, the ElementManagement application waits until the device’s sysUpTime (= time after boot) has reached aconfigurable value (default 2 minutes). At this moment the alarm status of all connected devices iscompared with their status before the reboot. The Element Management application generatesalarms for alarms that have changed state.• True IP devices and the Orchid management concentrator keep their alarm history. The Orchidadditionally keeps the alarm history of the connected devices (log size 1000 alarms). When themanagement station has failed during a certain time, the true IP devices and the Orchidconcentrator send their alarm history afterwards to the management station in order to minimisethe loss of information.5.2.2 Complete network element access with TMAFigure 24 TMA application integration in HP OpenViewTMA access to the network elements is integrated in the Element Management application. AllTelindus device icons have a TMA selection in the right button menu. All features from the stand-aloneTelindus Version 4.3 - 1 July 2004 44

TMA management for Telindus access productsTMA version to configure, monitor and test an individual network element are thus integrated inElement Management application. Above is an example of this integration in HP OpenView.Similarly Telindus device icons have a TMA ISSP selection in the right button menu. TMA ISSP canthus be started directly or through the TMA application.The Element Management applications themselves can be configured also with a TMA session to thestations running them.5.2.3 Network element auto-discovery for proxied network elementsIf the Element Management application knows the Orchid management concentrators, it learns all theconnected network elements from the Orchid’s objectTable. This is a table where all network elementsconnected to the Orchid are defined with their NMS address.The Element Management application adds all discovered network elements in its database and bydefault creates icons in the network map with the related Orchid management concentrator. After eachsubsequent change in the Orchid’s objectTable the databases and maps are automatically adapted.In this way the Element Management application auto-discovers very quickly all the Telindus networkelements without own IP protocol stack.By configuration in the Orchid management concentrator it is possible to define different maps for allnetwork elements per card nest or even in any network element combination. The ElementManagement application automatically creates the maps according to this configuration.5.2.4 Name resolution server for proxied devicesThe Element Management application contains a name resolution server. It translates a networkelement’s name as defined in the Orchid management concentrator into its IP address or theconnected Orchid’s IP address, its exit port and NMS address. This name server is different from aDNS server, since the address may consist of more than an IP address.If this name resolution server is present, TMA CLI can be called with the network element’s nameinstead of its full address. TMA CLI will then request the Element Management application for thecorresponding address.5.2.5 Access securityOn the Element Management station, each user login corresponds with one password for use by theElement Management application. This password is used whenever a TMA or TMA ISSP session isopened to a managed device without prompting the user for it. This avoids that the user should enterhis password for each TMA or TMA ISSP session. Different users may have different passwords withdifferent rights.Telindus Version 4.3 - 1 July 2004 45

TMA management for Telindus access products5.3 TMA Element Management5.3.1 TMA ElementViewFigure 25: TMA ElementViewFigure 25 shows the ElementView. This is the graphical representation of the network within TMAElement Management. Each network element has an icon in the left window. The colour of the icongives the alarm status of the network element. Icons can be grouped in ‘maps’ with the consolidatedalarm status of all network elements within the map. Maps can be structured to one’s needs, e.g. theycan be geographically or functionally structured. The map view can be opened and closed in the sameway as Microsoft’s Windows explorer. The complete map and network element view is called the maptopology. The map topology is unique per ElementView.The other windows show respectively the current alarm status and the alarm history of the selectednetwork element or map.5.3.2 Distributed managementTMA Element Management can run on one management station, while the ElementView can run onanother management station. Multiple ElementViews can run simultaneously. In such case only onelicense key is required.5.3.3 Element discoveryTMA Element Management has a list of managed IP devices. One can add IP addresses of Orchidconcentrators (for proxied devices) and true IP devices to this list. For proxied devices, once theTelindus Version 4.3 - 1 July 2004 46

TMA management for Telindus access productsOrchid concentrator is known, all devices, proxied by this Orchid will automatically be added undermanagement (see section 5.2.3). The list of managed IP devices is common for all views.5.3.4 Alarm managementThe icon of each network element reflects its alarm status in its colour. The impact of alarmacknowledgement on the icon colour in the TMA Element Management can be configured (seegeneral alarm section). As TMA ElementView may run on different stations, one can configure alsoper view one of three options:1. Acknowledged alarms remain visible in the icon colour on this view.2. Acknowledged alarms are no more visible in the icon colour on this view.3. The icon colour in this view behaves as defined generally in the TMA Element Management.Telindus Version 4.3 - 1 July 2004 47

TMA management for Telindus access products5.4 TMA for HP OpenView5.4.1 Real time visualisation of the network statusFigure 26: HP OpenView sub-mapHP OpenView NNM provides the network operator with a hierarchical view on the network. Views canbe geographically structured (different sites, different rooms…), functionally structured (voice bandmodems, base band modems, multiplexers, broadband devices ...) etcetera. Changes in the networkstatus are instantaneously visualised. The figure above shows an example of a HP OpenView submapwith some Telindus devices. With a right mouse click while pointing to a Telindus device, TMA orTMA ISSP can be initiated and the alarm status of the device can be shown.Figure 27: HP OpenView NNM Event LogTelindus Version 4.3 - 1 July 2004 48

TMA management for Telindus access productsAside of the alarm log possibility within TMA for HP OpenView, HP OpenView NNM has also an eventlog window, listing the alarm history of all network elements. The figure above shows a window withthis event log.5.4.2 Distributed managementIn large networks the management tasks can be divided between regional collector stations doing theday-to-day network node management and one or several central management stations. The collectorstations filter alarms and forward them as SNMP traps to a central management station. This centralstation may be again a HP OpenView station or another SNMP based station offering network and/orservice management (at the higher OSI layers). The central HP OpenView management station canalso backup the regional collector stations. Telindus does not support this set-up with TMA for HPOpenView.However Telindus supports a central HP OpenView station running TMA for HP OpenView combinedwith regional stations running TMA Element Management. TMA Element Management has a properalarm forwarding solution that is more performing than the standard HP OpenView forwarding viaSNMP traps. Both collector and management stations require a TMA licence key*.A different approach is to have several console stations running HP OpenView and one HP OpenViewmanagement station. In this topology, the graphical tasks are running on the console stations, while allthe management tasks are running on the HP OpenView management station. Only the managementstation requires a TMA for HP OpenView licence.X-terminal sessions to a HP OpenView station allow monitoring a single network simultaneously withdifferent people at different locations. Using a X-terminal session each user has the same possibilitiesas on the HP OpenView station’s console.As an alternative to the use of X-terminals one can install a web server on the HP OpenView station.HP OpenView NNM includes a web interface. This allows seeing the HP OpenView network mapsusing any standard web browser. This solution is limited to retrieving information from the network. Nochanges can be made. HTTP sessions to the Telindus network elements are not integrated with thisweb interface.HP OpenView is a complete management suite. HP OpenView NNM is only part of it. HP OpenViewallows also the development of an interface to TMN based systems.5.4.3 Auto-discoveryHP OpenView features auto-discovery of IP devices. Auto-discovery uses ping and SNMP messages.It can be used to discover the Orchid management concentrator concentrators and all true IP devices.If the other network elements have also received an IP address, they can be auto-discovered as wellby HP OpenView. However, this way of auto-discovery requires sufficient bandwidth, it may take acertain time to complete and it requires quite a bit of processing on the management station.Therefore for large networks Telindus proposes not to give a separate IP address to each networkelements without IP protocol stack. In such case TMA for HP OpenView auto-discovers these networkelements.5.4.4 Alarm managementTMA for HP OpenView reports alarms into the Event log of the Node Manager. Each alarm containsthe HP OpenView time stamp, the alarm level, the device’s name, the alarm description and theduration of the previous state for this alarm.Telindus Version 4.3 - 1 July 2004 49

TMA management for Telindus access productsWithin HP OpenView one can acknowledge alarms, but this does not impact on the colour of the iconson the network maps. It only impacts the way it is represented in the event log. Alarmacknowledgement within TMA for HP OpenView however has an impact on the icon colour on the HPOpenView maps (see general alarm section). Alarms that are acknowledged within TMA for HPOpenView result also in an acknowledged state in the HP OpenView event log. Alarmacknowledgement requires minimum HP OpenView NNM version 6.0.5.4.5 Interworking with other equipmentTMA for HP OpenView can be used with any other vendor’s application for HP OpenView NNM 6.X onone of the above mentioned hardware platforms. Imagine an SDH network with nodes from onevendor and Telindus access devices. The HP OpenView network map contains icons for the nodesand icons for the Telindus access devices. One can configure within HP OpenView per device typewhich alarms should change the icon’s colour. Double clicking on the SDH node icon starts theapplication for this device, whereas double clicking on the Telindus access device icon start the TMAapplication.Telindus Version 4.3 - 1 July 2004 50

TMA management for Telindus access products5.5 Versions and platforms5.5.1 VersionsTMA Element Management and TMA for HP OpenView are available in a demo version (up to 8network elements), an entry-level version (up to 250 network elements) and an unlimited version.They come with a licence key.5.5.2 TMA Element Management platformsThe following table indicates the operating systems supported by TMA Element Management.OSSolaris 7Solaris 8Windows 2000Windows XP5.5.3 TMA for HP OpenView platformsThe following table indicates the interoperability between operating systems and HP OpenViewNetwork Node Manager (NNM) versions and whether it is possible to run TMA for HP OpenView.OS NNM 6.1 NNM 6.2 &6.3Possible to runNNM 6.4 NNM 7.01Possible to run TMAfor HP-OV?Solaris 7 yes yes no no yesSolaris 8 yes yes yes yes yesSolaris 9 no no yes yes yesWindows 2000 yes yes yes yes yesWindows XP no no yes yes yesTMA for HP OpenView will not support the HP-UX platform any more in future releases.Telindus Version 4.3 - 1 July 2004 51

TMA management for Telindus access products5.6 System requirementsThe system requirements for an element management platform depend on the element managementapplication, the number of true IP network elements in the network, the overall number of networkelements in the network and the performance (bandwidth, delay…) of the DCN 1 network.In the below sections, the system requirements for Windows and Solaris platforms are listed fordifferent situations:1. Minimum system requirement. These are requirements for up to 1000 devices or 250 IP devices.2. System requirements for 7500 IP devices.3. System requirements for 12000 devices of which up to 250 true IP devices.The TMA Element Management applications keep a session open with each true IP device to retrievethe alarms. Proxied network elements are managed through the Orchid concentrator and thereforeneed no separate session towards the network management platform. The load on a networkmanagement platform depends much on the number of open sessions. Therefore the systemrequirements for the Element Management platform depend much on whether the managed devicesare true IP devices or proxied devices.In addition HP OpenView sends ping requests to each IP device and sends SNMP queries. One canlower the interval between ping and SNMP requests or even stop this polling. This has no direct effecton the management of Telindus IP devices, since the alarm status is completely handled by TMA forHP OpenView.Telindus has tested TMA for HP OpenView on a network with over 40000 devices. For true IP devices,we recommend a maximum of 16000 network elements per management station.5.6.1 TMA Element Management requirementsThe following table gives the minimum system requirements for running TMA Element Management.min. system requirements Windows Sun SolarisProcessor specification Pentium IV or more Sun Blade 1500 or moreOperating system version Windows 2000 / XP Solaris 7 / 8Available disk space 500 Mb 500 MbRecommended RAM 512 Mb or more 512 Mb or moreAdditional hardwareNetworkingCD-ROM drivemouseIP networking installed andconfiguredCD-ROM drivemouseIP networking installed andconfigured1 The term DCN ("Data Collection Network", or sometimes "Data Communications Network") refers to a networkused by telecommunications carriers and service providers to carry internal network management and billing data.Telindus Version 4.3 - 1 July 2004 52

TMA management for Telindus access productsBelow one can find the system requirements for 7500 true IP devices or 12000 devices of which up to250 true IP devices. It is advised to use a Solaris operating system when managing 2500 true IP or5000 non-IP devices and above. Therefore only a Sun configuration is shown.7500 true IP devices or 12000devicesProcessor specificationSun SolarisSun Fire V210 Server with 2 UltraSparc-III processors or aboveOperating system version Solaris 7 / 8Available disk spaceRAM memory1 Gb1 Gb5.6.2 TMA for HP OpenView system requirementsThe system requirements are mainly dependent on the HP OpenView configuration. The additionalprocessing and memory required for the TMA for HP OpenView application is limited.HP gives figures concerning the station hardware requirements in function of the number of networkelements. For more information on the HP OpenView configuration refer to the Performance andConfiguration Guide for Network Node Manager 6.x. – Second Edition. The system requirementsfound there should be interpreted with care, because many parameters like the number of alarms andwhether the network elements are IP devices influence the processing needs.The following table gives the minimum system requirements for running TMA for HP OpenView:min. system requirements Windows Sun SolarisProcessor specification Pentium IV or more Sun Blade 1500 or moreOperating system version Windows 2000 / XP Solaris 7 / 8HP OpenView versionHP OpenView NNM 6.01 orhigherHP OpenView NNM 6.01 orhigherAvailable disk space 500 Mb 500 MbRecommended RAM 512 Mb or more 512 Mb or moreAdditional hardwareNetworkingCD-ROM drivemouseIP networking installed andconfiguredCD-ROM drivemouseIP networking installed andconfiguredThe guaranteed maximum number of devices managed by a single HP OpenView station is 25000.Higher values are possible, but this depends mainly on the resources required by HP OpenView. It isadvised to use a Solaris operating system when managing 2500 true IP and 5000 non-IP devices andabove.Below one can find the system requirements for 7500 true IP devices. The HP OpenView stationcollects all information and presents it graphically on its console. No other Graphical User Interfaces(GUIs) are connected.7500 true IP devices Sun SolarisProcessor specificationSun Fire V210 Server with 2 UltraSparc-IIIi processors or aboveTelindus Version 4.3 - 1 July 2004 53

TMA management for Telindus access productsOperating system version Solaris 7 / 8Available disk spaceRAM memory1 Gb2 GbBelow one can find the system requirements for 12000 devices of which up to 250 true IP devices.The HP OpenView station collects all information and presents it graphically on its console. No otherGraphical User Interfaces (GUIs) are connected.12000 devices Sun SolarisProcessor specificationSun Fire V210 Server with 2 UltraSparc-IIIi processors or aboveOperating system version Solaris 7 / 8Available disk spaceRAM memory1 Gb1 Gb5.7 Support conditionsTelindus strongly recommends the subscription of a maintenance contract for TMA ElementManagement and TMA for HP OpenView. The maintenance contract includes advice and assistanceconcerning the operation and the application of TMA Element Management or TMA for HP OpenViewand the Orchid management concentrator Firmware. The service is provided during office hoursCentral European Time. Additionally one gets automatically new releases for the TMA ElementManagement applications.The maintenance contract is initially for 3 years with a yearly fee.Telindus Version 4.3 - 1 July 2004 54

TMA management for Telindus access products6 Network management applications and integration withother platforms6.1 TMA inventory managementIn large networks, there is a need for an inventory of the equipment in the network. A central databasekeeps information regarding the network elements. TMA inventory management is an add-onapplication to TMA Element Management and TMA for HP OpenView. It gathers all the inventoryinformation of the Telindus access products in a central database. It provides also a communicationinterface to that database.TMA Inventory Management builds a database with a number of inventory parameters from eachTelindus access device in the network. It retrieves the information automatically from the devices andthe Orchid concentrators. All devices under TMA Element Management or TMA for HP OpenView areconcerned. The database includes device information such as the name, the contact person, thelocation, the description, the unique identification code, the software version(s) and the availableinterfaces. The most recent configurations of all devices are stored as well.The database information is accessible from an outside application, using the Telindus proprietaryCMS2 protocol. This protocol uses the principles of CMIP and CORBA, thus making the integrationwith other network management platforms easier. TMA Inventory Management includes the completeprotocol documentation. Once a session with an outside management platform is established, theoutside application is automatically triggered of any database changes.The database information is also available on the TMA user interface on the Element Managementplatform. Any changes can be logged in a file.The database includes the following information per network element:• The most recent configurations are stored as a file. The database references the file.• Device selection name. This is an unambiguously unique name for each device, based on the IPaddress and possibly the name or the position.• Device type, including hardware type and firmware version• Device unique identification code. On recent device types, each network element has a uniqueidentification code, which is readable for the management system. When a device in the networkis replaced, the new identification code is immediately available on the inventory database.• Device name, location and contact person• Table with software codes used in the device• Per interface parameters like the name, the description, the administrative status, the type and thespeed per interfaceThe supported platforms are the same as for the TMA Element Management applications. The systemrequirements mentioned for the Element Management applications include the extra memoryrequirements for TMA Inventory Management.Subscription of a maintenance contract for TMA inventory management is mandatory. Themaintenance contract includes telephone advice and assistance concerning the operation and theapplication. The service is provided during office hours Central European Time. Additionally one getsautomatically new releases of TMA inventory management.Telindus Version 4.3 - 1 July 2004 55

TMA management for Telindus access products6.2 TMA path managementFor service and business management, an operator is interested in the quality and the use of acomplete service. Examples of such services are a leased line service, a frame relay or ATM PVCservice. The operator wants also a simple and automated procedure to provide a service to a newcustomer into the network. This involves that all equipment involved in the path for this service iscorrectly 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 evenpoints of presence (POPs) with only Telindus access products. Along with this there is an increasingdemand to manage not only all devices as separate entities (element management), but to manage aswell the logical TDM connections within such network.TMA Path Management TDM 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 TDM is anadd-on product to the TMA Element Management applications and TMA Inventory Management.Paths are defined by reference to their end points. For an existing path, TMA Path Management TDMtries to find out the complete path given only the end points. It continuously monitors the path statusand keeps related performance information for the last day, the last month and the last year. Changesin 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 severalsections. Each section may be active (i.e. acrossTelindus devices) or passive (i.e. across otherdevices). The figure gives an example of a leasedline with 3 sections: 1 passive section in thebackbone network and 2 active sections in the access network.TMA Path Management TDM can also completely provide a path. Provisioning results in the correctconfiguration of all the equipment along the path.*TMA Path Management TDM has 2 different user interfaces. For administration purposes (definition ofthe paths, configuration) the TMA user interface is available. For operation and maintenance purposesa web interface is available with click-through possibilities to the individual devices. The figure belowshows this web interface.Telindus Version 4.3 - 1 July 2004 56

TMA management for Telindus access productsFigure 28: TMA Path Management TDM: web interfaceThe supported platforms are the same as for TMA Element Management. The system requirementsmentioned for the Element Management applications include the extra memory requirements for TMAPath Management TDM.Subscription of a maintenance contract for TMA Path Management TDM is mandatory. Themaintenance contract includes telephone advice and assistance concerning the operation and theapplication. The service is provided during office hours Central European Time. Additionally one getsautomatically new releases for TMA path management TDM.Telindus Version 4.3 - 1 July 2004 57

TMA management for Telindus access products6.3 TMA integration with other management platforms6.3.1 Integration at network element levelAlthough HP OpenView Network Node Manager (NNM) is the most widespread element managementplatform, there are sometimes requests for integration of TMA with other element managementplatforms. The necessary APIs are available for such integration. The integration consists of 2 parts:1. Integration of the TMA stand-alone application on the platform. This means that one can start aTMA session to a Telindus device by pointing to the network element icon on the platform’snetwork map.2. Integration of the alarm handling on the platform. This means that the Telindus application usingproprietary alarms processes all alarms from Telindus devices. It forwards these alarms then tothe alarm handling processes on the element management platform. The TMA alarm handlingprocess has been implemented for the TEMIP hardware platform.As an alternative the alarms can be received on the element management platform as SNMP traps.However this solution requires much more processing power and is therefore only suitable for smallernetworks.6.3.2 Example: integration with NewBridge 46020NewBridge 46020 is a proprietary network management platform from NewBridge for end-to-endmanagement of its equipment. Since Alcatel has become owner of NewBridge, this platform is nowcalled Alcatel 5620.A number of Telindus customers use Telindus modems on a NewBridge backbone for e.g. frame relayor leased line services. Telindus worked out a light integration with the NewBridge 46020 platform forthese customers.Once NewBridge’s openSNMP software has been installed on the platform, one can also install HPOpenView and TMA for HP OpenView on the same 46020 platform. Now one can have elementmanagement of all Telindus devices on the same platform as the NewBridge devices. Two optionsexist, which can be used simultaneously:1. From a 46020 map, one can launch a HP OpenView map with Telindus devices. Using this option,one has all the HP OpenView and TMA for HP OpenView features available on this map. Sincethe Telindus devices are on another map as the NewBridge devices, no logical connections fromthe Telindus devices to the NewBridge devices are possible.2. With a command, the operator can copy the Telindus devices from the HP OpenView database tothe 46020 database. The Telindus devices become then available on the maps with theNewBridge devices. This makes it possible for the operator to make logical connections (lines)between connected Telindus and NewBridge devices. When running an additional TMAinstallation on the NewBridge platform, one can also launch TMA from each Telindus device iconon the 46020 map. However alarm information on the Telindus devices is not visible on thesemaps. To use this option, each Telindus device requires an IP address.Telindus Version 4.3 - 1 July 2004 58

TMA management for Telindus access productsFigure 29: Integration with NewBridge 46020Both options can be combined. The table below summarises advantages and disadvantages for bothoptions.Option 1+ all HP OpenView and TMA for HP OpenView features are available on this map.- no logical connections with NewBridge equipment.Option 2 (seeFigure 29)+ operator can make logical connections to NewBridge equipment.+ one can also launch TMA from each Telindus device icon on the 46020 map- no alarm information available on 46020 map for Telindus devices.- All Telindus devices require an IP address.Telindus Version 4.3 - 1 July 2004 59

TMA management for Telindus access products6.3.3 Integration with higher levelsIntegration of element management platforms with higher layer management platforms for network,service and business management becomes an important issue for large networks. The requirementsand platforms may vary greatly from one network to another. In almost every case, this requiresspecific developments.For this purpose, Telindus offers several options.1. One can use the scripting tool TMA CLI (see section 4.9). This allow gathering specific attributesfrom the network elements or executing actions like loop tests. This is particularly suitable forperformance and status monitoring.2. If alarm integration is involved, one can forward filtered alarm information from HP OpenViewNNM to the other management platform as SNMP traps. This is a standard option. However thismay require a lot of processing on the other management platform and there is no alarm statussynchronisation at start-up.3. Alarm integration between the TMA Element Management application and the other managementplatform can also be achieved using the fully documented proprietary Telindus protocol CMS2over IP. This protocol uses the principles of ITU-T TMN (Telecommunications ManagementNetwork), but it is less complex than a Q3 or a CORBA interface. Also information from the add-onapplications TMA inventory management and TMA path management can be exchanged in thisway.4. Based on the above interface with the proprietary CMS2 protocol it is possible to build as well aQ3 or CORBA interface to other network management platforms.5. If real-time alarm integration is not required, the higher-layer management platform can read atregular intervals the alarm log file of the TMA Element Management application.6.3.4 Example: TeMIP integrationTeMIP is a popular network management platform for large operators. It comes originally from DigitalEquipment Corporation (DEC), later Compaq and now HP. Although HP will integrate TeMIP into itsHP OpenView platform, it still may take a long time before operators make such a switch.The HP OpenView TeMIP Access Module (AM) for Telindus TMA provides an interface betweenTeMIP and TMA. This access module supports basic fault management capabilities with a basicinformation model. It is a bi-directional module, which receives and processes unsolicited messages,as well as sends management commands (keep-alive messages, synchronisation commands) andreceives associated responses.TMA directly interfaces to TeMIP by means of a combination of Management Modules andapplications. 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 failureThis product is available from Compaq/HP or from one of our partners. It includes all TMAmanageable products.Telindus Version 4.3 - 1 July 2004 60

TMA management for Telindus access products7 Supported products and availability7.1 Supported productsTelindus has a continuously growing access product range. TMA management as described in thisdocument is available on all new products. Many access devices are not IP-aware. These devicesneed the Orchid management concentrator as mediation device. Other products have their own IPprotocol stack. Those devices do not need the Orchid management concentrator. The table belowindicates for each product whether TMA access is possible via the CTRL port, via the Orchidmanagement concentrator and over IP without Orchid management concentrator. Devices marked inthe last column are true IP devices.TMA management supports currently the following Telindus access products.Product Direct TMAaccess viaCTRL portTMA accessvia OrchidmanagementconcentratorTMA accessover IPwithout OrchidmanagementconcentratorAster 4 starting from• s/n 9423000 (requires firmware upgrade)• s/n 9507000Aster 4 Flash with• s/n < 9822223 for TWIN models• s/n < 9833000 for all other modelsAster 4 Flash starting from• s/n 9822223 for TWIN models• s/n 9833000 for all other modelsAster 5 √+T √Crocus ADM 2P √+T √Crocus CNV (except Crocus 2M CNV TT) √+T √Crocus DXC √+T √Crocus E3 MUX √+T √ √Crocus FO (10M / 45M) √+T √√√√√Crocus HDSL√Crocus HDSL F √ √Crocus HS√Crocus Inverse Multiplexer √ √Crocus Router Interfaces (2M / 10M / 34M) √ √ √Crocus Router 2M √+T √Telindus Version 4.3 - 1 July 2004 61

TMA management for Telindus access productsCrocus SDSL (including QUAD version) √ √ √Crocus SDSL Router √ √Crocus SHDSL (different versions) √+T √Orchid 1003 LAN √+T √Telindus 1030 Router Series √+T √Telindus 1320 SDSL Router √+T √Telindus 1420 / 1421 SHDSL √+T √ √Telindus 1431 SHDSL √+T √Telindus 2300 Series √+T √Telindus 2400 Series √+T √Regarding the other maintenance and management tools, the following rules apply:If the device has …Direct TMA access via CTRL portThen the following applications are available:TML and EasyConnect hand terminal are available.CLI and ATWIN user interface via serial port isavailable on the devices in the above table, whenindicated with ‘+T’.TMA access via Orchid managementconcentratorTMA access over IP without Orchidmanagement concentratorTMA access via Orchid managementconcentrator or TMA access over IP withoutOrchid management concentratorTelnet and HTTP are available through the Orchidproxy. SNMP and ping reply are available through theOrchid proxy if the device has an IP address.Telnet, HTTP, SNMP, ping.TMA Element Management, TMA for HP OpenView,TMA CLI, TMA Inventory Management. For TMA PathManagement, see the specific TMA Path Managementsection.7.2 Support for some older Telindus devicesThe devices where TMA access is only possible via the Orchid management concentrator (see tableabove) do not support the Telindus proprietary CMS2 protocol. Those devices use instead the formerCMS protocol. The Orchid management concentrator converts it into CMS2.The following remarks apply to TMA management of these devices:1. These devices do not have a user table with passwords for access authentication. Insteadauthentication to these network elements is done using the Orchid’s passwords.2. These devices do not have their own alarm masks. Instead one can configure in the Orchidmanagement concentrator per modem type which alarms will be masked per device type.3. Due to the protocol conversion and the different behaviour of the CMS protocol, response timesfor these devices may be larger. Especially when performance information is retrieved, longresponse times may occur.Telindus Version 4.3 - 1 July 2004 62

TMA management for Telindus access products4. TMA management of Crocus HS modems does not allow a direct configuration. Instead oneshould use the configuration consistency of the Orchid management concentrator.7.3 AvailabilityBased on the long experience Telindus has in network node management, TMA management iscontinuously evolving. All components mentioned in this document are available, except those markedwith an asterisk (*).7.4 Sales CodesThis is the list of sales codes for the Orchid management hardware and the TMA softwareapplications.Code Description Remark150465 O1003LAN NMS Concentrator (19 inch 1U & desk-top) 230/115Vac.151208 O1003LAN 48VDC NMS Concentrator (19 inch 1U & desk-top) 48Vdc.177468 TELINDUS 1035 ORCHID 230VAC NMS Concentrator TMA\SNMP proxy software. IP router-bridgewith 1x 10/100Mbit/s Ethernet interface, 1x RS530 interface, 2x2Mbit/s G703 interfaces, a high speed bus for connection toTelindus card nests CN4, additional memory and Orchidfunctionality. Includes European 230VAC power adapter177469 TELINDUS 1035 ORCHID NPWR NMS Concentrator TMA\SNMP proxy software. IP router-bridgewith 1x 10/100Mbit/s Ethernet interface, 1x RS530 interface, 2x2Mbit/s G703 interfaces, a high speed bus for connection toTelindus card nests CN4, additional memory and Orchidfunctionality. Delivered without power adapter180330 TELINDUS 1035 ORCHID CV-CN4 NMS Concentrator TMA\SNMP proxy software. IP router-bridgewith 1x 10/100Mbit/s Ethernet interface, 1x RS530 interface, 2x2Mbit/s G703 interfaces, 2 high speed interfaces for connection toTelindus card nests CN4, additional memory and Orchidfunctionality. CN4 card version.171295 ORCHID DM NPWR Digital Mixing Module for extensions (1->6) of the asynchronousserial network management path. RJ45 connectors. NO PWRModule = separate item. No cables = separate items171302 PWR-PLUG 230VAC->7,5VDC Wall plug power module for Desktop units delivered withoutexternal PWR plug.171303 PWR-PLUG 115VAC->7,5VDC Wall plug power module for Desktop units delivered withoutexternal PWR plug.171304 PWR-PLUG VDC->7,5VDC Wall plug power module for Desktop units delivered withoutexternal PWR plug.156986 TMA MANAGEMENT SUITE DEMOVERSION187387 TMA_ELMGT SUN SOLARIS ENTRYLEVEL VER.Demo version for TMA_HP-OV, TMA ELMGT, TMA Inventory MgtAND TMA Path Mgt TDM. Max 8 Telindus Devices supported.Telindus Entry Level Standalone Element Manager for SUNSolaris. Up to 250 Telindus Devices supported. 3-yearsMaintenance contract mandatory.Telindus Version 4.3 - 1 July 2004 63

TMA management for Telindus access products187388 TMA_ELMGT SUN SOLARISUNLIMITED VER.187385 TMA_ELMGT WINDOWS ENTRYLEVEL VER.187386 TMA_ELMGT WINDOWS UNLIMITEDVER.187456 TMA_ELMGT ENTRY LEVEL TOUNLIMITED UPGR.187389 TMA_ELMGT ENTRY LEVEL MAINT.CONTRACT + 1ST YR FEE187390 TMA_ELMGT UNLIMITED MAINT.CONTRACT + 1ST YR FEE156685 TMA_HP/OV SUN SOLARIS ENTRYLEVEL VER.156686 TMA_HP/OV SUN SOLARISUNLIMITED VER.156689 TMA_HP/OV WINDOWS ENTRYLEVEL VER.156690 TMA_HP/OV WINDOWS UNLIMITEDVER.171269 TMA_HP/OV ENTRY LEVEL TOUNLIMITED UPGR.158673 TMA_HP/OV ENTRY LEVEL MAINT.CONTRACT + 1ST YR FEE158674 TMA_HP/OV UNLIMITEDMAINT.CONTRACT + 1ST YR FEE171267 TMA_CLI WINDOWS AND SUNSOLARIS163135 TMA_CLI MAINT.CONTRACT + 1STYR FEETelindus Unlimited Standalone Element Manager for SUN Solaris.No limit on Telindus Devices supported. 3-years Maintenancecontract mandatory.Telindus Entry Level Standalone Element Manager for Windows.Up to 250 Telindus Devices supported. 3-years Maintenancecontract mandatory.Telindus Unlimited Standalone Element Manager for Windows. Nolimit on Telindus Devices supported. 3-years Maintenance contractmandatory.Upgrade path from TMA_ELMGT entry level towards Unlimitedversion for the same platform.Maintenance contract for TMA_ELMGT Entry Level. Price includesfirst year’s fee. Once ordered, yearly a new invoice is sent. Theminimum contract period is 3 years.Maintenance contract for TMA_ELMGT Unlimited. Price includesfirst year’s fee. Once ordered, yearly a new invoice is sent. Theminimum contract period is 3 years.Telindus Management Application for HP Openview on SUNSolaris. Up to 250 Telindus Devices supported. 3-yearsMaintenance contract for TMA_HP/OV mandatory.Telindus Management Application for HP Openview on SUNSolaris. No limit on Telindus Devices supported. 3-yearsMaintenance contract for TMA_HP/OV mandatory.Telindus Management Application for HP Openview on Windows.Up to 250 Telindus Devices supported. 3-years Maintenancecontract for TMA_HP/OV mandatory.Telindus Management Application for HP Openview on Windows.No limit on Telindus Devices supported. 3-years Maintenancecontract for TMA_HP/OV mandatory.Upgrade path from TMA_HP/OV entry level towards Unlimitedversion for the same platform.Maintenance contract for TMA_HP/OV Entry Level. Price includesfirst year’s fee. Once ordered, yearly a new invoice is sent. Theminimum contract period is 3 years.Maintenance contract for TMA_HP/OV Unlimited. Price includesfirst year’s fee. Once ordered, yearly a new invoice is sent. Theminimum contract period is 3 years.Command Line Interface application for WINDOWS and SUNSOLARIS. 3-years Maintenance contract mandatory.Maintenance contract for TMA_CLI. Price includes first year’s fee.Once ordered, yearly a new invoice is sent. The minimum contractperiod is 3 years.177948 TMA INVENTORY MANAGEMENT Inventory Management application. Runs on Windows and SUNSolaris. Must be sold with a maintenance contract.Telindus Version 4.3 - 1 July 2004 64

TMA management for Telindus access products177949 TMA INVENTORY MANAGEMENTMAINT. CONTRACT + 1ST YR FEEMaintenance contract for TMA Inventory Management. Priceincludes first year’s fee. Once ordered, yearly a new invoice issent. The minimum contract period is 3 years.177952 TMA PATH MANAGEMENT TDM Path Management application for TDM paths on Windows and SunSolaris platforms. Must be sold with a maintenance contract177953 TMA PATH MANAGEMENT TDMMAINT. CONTRACT + 1ST YR FEEMaintenance contract for TMA Path Management TDM. Priceincludes first year’s fee. Once ordered, yearly a new invoice issent. The minimum contract period is 3 years.Telindus Version 4.3 - 1 July 2004 65