The Top 15 TL1 Resources

#1 - TL1 Tutorial White Paper.
TL1 is a frequent command line interface choice for gear manufacturers. TL1 messages are also embedded with the database information required to interpret the meaning of an alarm. How Understanding TL1 Will Help You TL1 is a multi-vendor and multi-technology protocol with comprehensive management support. There's a very good chance that TL1 protocol plays a significant role in your network. A solid foundation of TL1 knowledge allows you to do your job more effectively. With this white paper, you're just a few pages away from the core knowing you need. Is TL1 Easy to Understand? TL1 is a set of ASCII-based instructions, or "messages". Because TL1 is text-based, you won't be intimidated by a jumble of code or hexadecimal protocols. This makes the learning curve for basic TL1 much shorter than with other protocols. This doesn't mean, however, that you won't need a basic introduction to TL1 basics. You must learn the basics before you can read, know, and write TL1 commands. Fortunately, TL1 message formats are very well defined and documented, and you can learn about the most frequently used commands in this guide. High-Capacity Discrete Alarm Collection Reported to Your TL1 or SNMP Master The NetGuardian 480 provides 80 discrete alarm inputs and reports to your TL1 or SNMP master. This dense alarm coverage gives you the convenience of a single-box solution, saves you the cost of buying a lot of low-capacity remotes, and offers you the lowest possible cost per point. With sophisticated TL1 and SNMP implementations, the NetGuardian 480 is the right combo of power, visibility, and simplicity - all in one box. To learn more about the NetGuardian 480, visit http://www.dpstelecom.com/rtus 3 Benefits Shared by TL1 and SNMP TL1 is a spiritual precursor to SNMP. Both were intended to be open standards and comprehensive languages.
TL1 and SNMP protocols share the following three benefits:
1) Widespread implementation.
2) Open standard makes it easier to connect networked devices with monitoring software.
3) Verbose command responses.

The Most Common TL1 Message Types

Although there is a wide range of standard TL1 messages, four types comprise the majority of TL1 communication:
1) Autonomous messages. Asynchronous messages (usually events or alarms) that are typically sent by network elements.
2) Input/Command messages. Commands sent by the user or OSS to a network object.
3) Output/Response messages. Replies sent by the network object in response to an input/command message.
4) Acknowledgment messages. Acknowledgments of the receipt of a TL1 input message, usually associated with a delayed report or action.
Connect 8 Streams of TL1 Messages to a Single Physical Port The DPS TL1 MUX-8 combines eight incoming TL1 streams into a single stream of data, allowing you to connect 8 physical ports to a single port on your TL1 master. This prevents simultaneous TL1 messages from "colliding" and becoming unreadable. The TL1 MUX-8 watches for the semicolon terminator at the end of each TL1 message. If the single stream is currently available, the message is forwarded to your TL1 master instantly. If the single stream is busy sending messages from another port, any other simultaneous messages are stored in the 256K buffer. Stored messages are sent to your master, in the order received by the MUX-8, at the next available opportunity...Download White Paper...

#2 - TL1 FAQ's.
What is TL1? Transaction Language 1 (TL1) is a set of ASCII-based instructions, or "messages". These messages allow a human user or an Operations Support System (OSS) to manage a network object (NE) and its resources. TL1 is a widely used management protocol in telecommunications. It is a cross-vendor, cross-technology man-machine language, and is widely used to manage optical (SONET) and broadband access infrastructure in North America What is the origin of TL1 protocol? In the early 70's, network actions began to increase and many companies started using Man-Machine Language (MML), a protocol readable by both humans and machines, to control gear elements both locally and remotely. In 1984, Bellcore, an gear manufacturer and research institute for the Regional Bell Operating Companies (RBOCs), specified Transaction Language 1 (TL1) as the standard protocol. Bellcore changed its specification in 1988 to Common Management Interface Protocol (CMIP). However, perhaps because of its perceived complexity, CMIP was never widely implemented and TL1 continues to be the dominant network management protocol. After divestiture, many new companies began using a variety of protocols within their networks, but TL1 remains arguably the most widely used protocol in North America today. What kind of messages does TL1 consist of? The TL1 language consists of a set of messages. There are 4 kinds of messages: Input message - This is the command sent by the user or the OSS. Output/Response message - This is reply sent by the NE in response to an input message. Acknowledgment message - This is an acknowledgment of the receipt of a TL1 input message and is sent if the response message will be delayed by more than 2 seconds. Autonomous message - These are asynchronous messages (usually events or alarms) sent by the NE. What are some of the advantages of TL1 as a management protocol? Standard Command-line Interface: TL1 provides an industry standard command line interface CLI for managing network elements. It is also flexible enough to allow for vendor extensions where appropriate. Human-to-machine Language: TL1 messages are in plain ASCII text, so staff and developers alike can always read them. As messages are easily readable, TL1 does not require sophisticated debuggers or protocol analyzers - what you see is what you get. Services: Unlike protocols such as SNMP, TL1 has a well-defined set of management services for performance, fault, security and other areas of management. For instance, an operator has standard ways to set up performance schedules and receive performance reports from any vendor's TL1-manageable NE. Tracking of Alarms/Events: TL1 easily tracks and handles events with a built-in identifier, or "alarm correlation tag" called an ATAG. This unique identifier TL1 is inserted in each autonomous alarm or event message sent from an NE. If an alarm message is "lost," the manager knows about it, as the ATAG of the next event is not in sequence.Read Full Article...

#3 - Featured TL1 RTU: The NetMediator.
If you've got TBOS gear in the field, and an SNMP or TL1 manager in the NOC, getting all your boxes to talk to each other can be a challenge. The simplest way is to bring contact closure alarms out of your field gear - but do you really want to monitor vital gear with just major-minor summary alarms? What you really need is a way to take all the detailed information contained in your TBOS alarms and convert it into a protocol message that your SNMP or TL1 manager can know. And for that, the best tool is the NetMediator. The NetMediator: Mediate 8 TBOS devices to SNMP or TL1, plus terminal server functionality, 32 discrete alarms, 8 analog alarms, and 8 controls. TBOS alarm mediation and alarm collection The NetMediator is like an RTU on steroids - it does everything the NetGuardian 832A does, and then some. It's a full-featured alarm collector and protocol mediation device in one. You can mediate and monitor, saving you the expense of buying extra RTUs. The NetMediator mediates eight displays of TBOS alarm data either to SNMP traps (with the NetMediator T2S model) or to TL1 autonomous messages (with the NetMediator TNT model). The NetMediator fully captures TBOS data and converts it into detailed, highly informative SNMP or TL1 alarms. You'll be able to diagnose gear problems exactly - so you can send the right technician with the right tools on the very first truck roll, reducing maintenance costs and windshield time. Or create a custom NetMediator for your single needs You're not limited to mediating TBOS, SNMP and TL1, either. The NetMediator platform is a general-purpose mediation device, and its capabilities allow DPS Telecom to create a custom solution for your single needs. Here are just a few possible NetMediator applications: Converting battery pack voltages to a PC screen gauge for continuous visibility. Activating a camera for a continuous photographic record of facility access. Designing an SNMP interface to a legacy plant control panel. Monitoring your system current draw with a periodic email, reporting amount of amps drawn. Collecting legacy TBOS or TABS alarms using network bandwidth instead of expensive dedicated copper. Accessing the craft or TL1 ports of facility gear using the Telnet client of...View Full Product Details...

#4 - Featured TL1 Mediation Device: T/Mon.
Summary of Features Permits T/MonXM and IAM's to respond TL1. Ideal for sending locally collected alarms to a main monitoring center. Commands based on TR-NWT-000833 Issue 4. Supports REPT-ALM and REPT-EVENT autonomous messages. Supports alarm retrieval commands such as RTRV-ALM. Permits TL1 controls to be issued to many of T/MonXM interrogator modules (ie: E2A, DCPF, TBOS, TRIP, DATALOK, DCM) Multiple SID's per port. TL1/X.25 & TL1/RS232 support available. Overview The TL1 responder software module gives either the T/MonXM WorkStation or IAM the ability to report alarms via TL1 (Transaction Language 1). Report Alarms via TL1: TLQ Responder Module Permits T/MonXm and IAM's the Ability to Report Alarms via TL1. TL1 is an ASCII based alarm protocol that can be used by either a person or a computer. Its popularity is growing as is evident by the number of network elements that support it. Consequently, new TL1 alarm masters are also popping up. Unfortunately, most of this new generation of TL1 masters only support TL1. This means that the "Legacy" gear can not be directly monitored by these masters. This leaves you with several choices. You can split your network into old / new sections, which complicates administration. You can replace your old gear, which is usually expensive and not always possible, or you can use a TL1 Mediation device. The T/MonXM software with a TL1 responder module is such a device. This module was specifically designed for those users who want to use their existing TL1 master to monitor alarms from non TL1 elements. ANY data collection protocol on the T/MonXM platform can be easily converted to TL1. TL1 responding comes in three flavors: Single port, which means that any one, previously unused hardware port, can be assigned TL1 functionality. Multiple port, same as one except that you can have a lot of TL1 responders on your available ports. If you plan on needing more than one responding port, this is the way to go. TL1/X.25, in this scenario you can send your TL1 alarms out directly over X.25. This module will support either a single SVC or a single PVC. X.25 parameters such as data rate, frame/packet window sizes plus many more are definable. TL1 sample autonomous output & command / response examples...View Full Product Details...

#5 - Case Study: TL1 Alarm Management.
Although the DACS and switching gear output alarms via human-readable ASCII text messages (including TL1 protocol), simply assigning staff to "watch for important alarms" was not a good option. For ASCII text streams with any significant traffic, human staff easily become overloaded, leading to missed alarms and unresolved threats. Even if your staff are perfect, it's still a waste of manpower to have your technicians hovering over long text streams all day. Startec also wanted to monitor environmentals - like temperature and humidity - at several sites. This was not an embedded feature in their existing gear, so they needed a stand-alone box to perform environmental monitoring. Startec's T/Mon manages alarms sent via ASCII text and TL1 protocol (also ASCII-text-based). It also collects DCP alarms from Startec's NetGuardian RTUs (NetGuardians can alternatively report via SNMP to any SNMP manager). "Any time circuits go down, we'll see those alarms. Whether they are GSP alarms, Soft switch alarms DACS or Fiber mux alarms." Startec Did Their Homework and Chose a Solution After researching their options, Startec selected a T/Mon master station to collect alarms from their Sonus softswitch, GSP switch, DACS, and TDAX gear. To cover environmentals, they also deployed several NetGuardian 216T and NetGuardian 832A remotes. These NetGuardians report back to the T/Mon master. Walid KarimNOC ManagerStartec Global Communications How Startec's NOC Manager Monitors the Network Walid Karim is the NOC manager at Startec Global Communications. "I take care of day-to-day actions in the NOC, including the employees and network," Karim said. "I make sure that our network is optimal at all times. We're quite busy." "We have a softswitch, a GSP switch, and DACSes and fiber muxes," he said. "We're mostly running VoIP & TDM for the domestic and international calls that we're terminating, including both wholesale and retail traffic." Startec uses T/Mon as their top-level master. "We use T/Mon as a monitoring tool to monitor our Sonus softswitch and our GSP switch," Karim said. "It also monitors DACSes and fiber muxes in Miami, New York, LA, Vancouver & Toronto sites." Startec Global uses the ASCII processor in their T/Mon master station to convert TL1 text alarms into computer-readable alarms. After conversion...Read Full Case Study...

#6 - Application Diagram: RTU dealing with TL1, TBOS, E2A, and SNMP procotols.
Find the right RTU for monitoring with SNMP, TL1, E2A, TABS, TBOS and other protocols ... plus protocol mediation solutions ... SNMP RTU: Select an SNMP remote telemetry unit like the NetGuardian 832A (32 discrete alarms - expandable to 176 discrete inputs - 32 ping alarms, 8 analog alarms, 8 controls, 8 serial terminal server ports). TL1 RTU: Select TL1 remote telemetry unit like the Remote Alarm Block (176 discrete alarms, 4 controls, standard wire-wrap terminations, also available for TBOS or SNMP). E2A / TBOS RTU: Select an E2A / TBOS remote telemetry unit like the KDA 864 (64 discrete alarms - expandable to 256 discrete inputs - 8 controls, plus options for 8-16 analog alarms and 3 ASCII craft ports, also available for SNMP). Select an option below to find the right remote telemetry unit for SNMP, TL1, E2A, or TBOS... RTUs for any protocol and capacity, plus extra features to meet any remote network alarm monitoring need ... Multiprotocol support: SNMP, TL1, E2A, TBOS, plus remote site protocol mediation options...View Application Diagram...

#7 - Application Diagram: Monitor Turin SONET Equipment over TL1....
This solution will provide you with a large improvement to your network alarm management system. As you will see in this application drawing, this solution addresses your important concerns, including getting rid of obsolete monitoring gear, increasing monitoring reliability, and consolidation of subsystem alarms. This solution provides you with a way to gradually, and in a controlled fashion, migrate away from your existing legacy gear using the T/Mon NOC and the NetGuardian G4's. The T/Mon NOC preloaded with the Badger Interrogator Software Module will receive alarms over your existing RS232 transport so it will require very little effort or expense on your part to make changes to your existing infrastructure. In addition this proposal features NetGuardian G4's that will eventually replace the older Badger units and provide alarm visibility at sites where you currently have no alarm collection whatsoever. We've also design the needed software for monitoring the TL1 alarms from your Turin SONET gear and your SNMP based routers and servers.This solution will allow you to monitor your existing Badger gear, NetGuardian G4's, TL1 alarms from your Turin SONET gear as well as SNMP v1 or v2 traps from your routers and servers. The NetGuardian G4 will report alarms to the T/Mon NOC over LAN but will also report alarms over a POTS line in the event of a LAN failure.In order to directly poll your existing Badger gear, we've created the Badger 481 software interrogation module. We've populated the T/Mon NOC with 4 RS232 interfaces, one of which will be used for polling the Badger remotes the others will be available for other applications. We've also included a database conversion utility that will allow your existing Badger 481 database to be substantially transferred to the T/Mon NOC saving considerable time & errors.The Badger to T/Mon NOC Database Conversion utility will be used prior to the delivery and turn up of the T/Mon NOC. It's designed to convert the database from your Badger 2000 manager to a format that the T/Mon NOC can use. It does this by performing the "Bulk" of the transfer. This utility will transfer: Address, Points, Provisioning information (Points/Controls) and create site controls. This converter drastically reduces the View Application Diagram...

#8 - TL1 over TCP/IP.
TL1 is one of the most widely used protocols in network gear today. While other protocols, such as SNMP, do have advantages over TL1, it is still present in most SONET (Synchronous Optical NETwork) and legacy gear. DPS provides an entire product line that can collect, mediate and send TL1 messages over a TCP/IP network. Using DPS gear to send TL1 messages over TCP/IP will reduce costs and guarantee message delivery. There are several benefits to sending your TL1 alarm data over a TCP/IP network. The first benefit is communication speed. TCP/IP is simply a faster network than a dedicated land-line (circuit-switched network) due to the a lot of paths that data can take in a packet-switched network. The second benefit is reliability. TCP/IP features automatic recovery from any dropped or lost data. It can guarantee that the data is transferred without the need for any intervention by the user. The third benefit is the mediation of legacy gear to different computer systems. TCP/IP is compatible with any computer system, eliminating the need for proprietary systems for telemetry monitoring. Finally, using TCP/IP to transport TL1 will save you money. The price for a dedicated copper line for each TL1 device can be eliminated by the ability to report alarms over existing LAN/WAN infrastructure. DPS has several products that have the ability to collect, mediate and/or send TL1 messages over a TCP/IP Network: the KDA, the NetGuardian and the T/Mon NOC. Data transport: LAN transport of TL1 and SNMP alarm data The KDA-TL1 is an alarm and control remote with 64 discrete alarm points and 8 control points. It reports alarms via pagers and to an OSS in TL1 over TCP/IP when equipped with a Network Interface Adapter (NIA) card. The NetGuardian is an alarm and control remote with 32 discrete alarm points, 8 controls and 8 analogs. It reports alarms to pagers, e-mail, DCP masters, a lot of SNMP managers and a lot of TCP ports. It features a web browser interface for user-friendly monitoring and provisioning. It also acts as a terminal server for 8 serial ports, providing reach through access via TCP/IP to a proxy port for each device. Using the proxy ports of the NetGuardian, legacy gear reporting TL1 can be mediated to your existing LAN/WAN. Using the proxy ports of the NetGuardian, legacy gear reporting TL1 can be mediated to your existing LAN/WAN. The IAM and the T/MonXM are the most powerful and flexible tools that DPS offers for telemetry monitoring. Different types of messages sent through a variety of protocols over differing transports can all be utilized while presenting them in a graphical format that is the same regardless of the input protocol. In the case of TL1, this eliminates the need for laborious interpretation of TL1 messages. The instant a TL1 alarm is generated, the user is...Read Full Article...

#9 - TL1 Message Samples.
Command Messages TL1 commands request an action to be executed by the recipient of the message Sample Command #1 (Login to Network Element with "Activate" Command): In this example, the UID is a username, and the PID is a password. They will be compared against the receiving element's administrator list to determine the success of this login attempt. It's also important to remember that some NEs will send you no response at all until you have logged in successfully. This is a security measure to prevent malicious users from discovering that the NE is present at all. NOTE: Some TL1 NE's do not support any security, do not require a login, and do not support the "ACT-USER" command. NOTE: The CANC-USER command is used to log off of a TL1 network object. Remember that some NE's will automatically log you off after a certain period of inactivity. Response Messages The response message (or "output message") is a reply sent by the NE in response to an input message. The response comes upon the completion of the task requested by the TL1 input message, and it states whether or not the requested task was completed successfully. Sample Response (Response to User Login Attempt): Acknowledgment Messages. An acknowledgment message is a special reply sent by the NE in connection with a delayed command. This special response is issued after the receipt of the command and indicates the status of the request. An acknowledgment message begins with one of the following two-letter response codes: IP - "In Progress" - Sent if the NE cannot execute a request within 2 seconds. PF - "Printout Follows" - Command execution is in progress and a response will be sent upon completion. OK - "Current status is OK" - Command has been executed successfully. NA - "No Acknowledgment" - Execution status is unknown (an error). NG - "No Good" - Valid command, but cannot be executed due to a...Read Full Article...

#10 - TL1 Alarm Monitoring Applications Guide.
TL1-based monitoring integrated into a total network alarm management solution TL1 is used throughout the telecommunications industry, in SONET and access infrastructure, network management elements, and operational support systems (OSSs). Wherever TL1 fits into your network, DPS Telecom offers a TL1-based monitoring solution, with products for collecting alarms from TL1 devices, reporting discrete and analog alarms as TL1, and mediating other protocols, like SNMP, to TL1. All of our TL1 solutions fit into a total single-platform network alarm management system, giving you one uniform platform for viewing, acknowledging, and managing alarms. TL1 over TCP/IP improves communications speed and reliability and reduce costs Our line of TL1 products provides support for collecting, mediating, and forwarding TL1 messages over dedicated circuits or TCP/IP. TCP/IP transport offers several benefits over traditional dedicated lines: increased speed, automatic recovery for dropped or lost data, and compatibility with any computer system, eliminating the need for proprietary telemetry monitoring systems. Another great advantage of TCP/IP transport is its low cost. The price for a dedicated copper line for each TL1 device can be eliminated by the ability to report alarms over existing LAN/WAN infrastructure. TL1 alarm collection solutions The KDA-TL1 is an alarm and control remote with 64 discrete alarm points and 8 control points. It reports alarms via pagers and to an OSS in TL1 over TCP/IP when equipped with a Network Interface Adapter (NIA) card. The NetGuardian is an alarm and control remote with 32 discrete alarm points, 8 controls and 8 analogs. It reports alarms to pagers, e-mail, DCP masters, a lot of SNMP managers and a lot of TCP ports. It features a web browser interface for user-friendly monitoring and provisioning. It also acts as a terminal server for 8 serial ports, providing reach through access via TCP/IP to a proxy port for each device. Using the proxy ports of the NetGuardian, legacy gear reporting TL1 can be mediated to...Read Full Article...

#11 - Monitor Discrete and Environmental Alarms with Your TL1 Master.
If TL1 is your preferred protocol for monitoring your network, you may find that you still need other protocols to get complete visibility of your remote sites. Network outages can occur because of failures of non-IP gear or environmental factors. But your TL1 master is deeply embedded in your network, and you don't want to install a specialized network monitoring system to manage site alarms. The answer is a remote that collects alarms from discrete contact closures and analog sensors and sends the alarm data in TL1 to your master. This solution is practical, cost-effective, and provides the many advantages of an integrated, multiprotocol network monitoring solution. The Cost Savings of a Multiprotocol Master. When you are integrating a wide variety of remote telemetry devices, including a lot of protocols, the ideal solution is to integrate all your monitoring into a single multiprotocol monitoring platform, for several reasons. Using a single interface for all your monitoring applications will: Create substantial savings in initial expenditure, operational, and maintenance costs. Save your investment in legacy protocol devices. Give you a smooth transition to advanced telemetry capabilities. Allow you to spread network gear upgrade costs over several budget cycles, since both old and new gear types are supported by the multiprotocol master. Free, No-Risk Engineering Development to Integrate Legacy Devices and Protocols While DPS Telecom supports over 15 protocols, you may need to use a protocol that we don't currently support. That's no problem - we can add support for the protocol you need, at no expense, risk, or obligation to you. If you need a custom-engineered solution, your choice of vendor is vital. Many gear vendors charge up-front non-recurring engineering fees (NREs) for custom engineering and give no guarantee that...Read Full Article...

#12 - 10 Key TL1 Master Features.
10 T/Mon NOC TL1 Master Features that Other Masters Can't Match TL1 Interrogator collects alarms from your TL1 devices. T/Mon can extract vital alarm data from autonomous TL1 messages and convert them to a standard format, bring all of your alarms from over 25 protocols onto one screen. TL1 Responder mediates alarms to your TL1 master. T/Mon can report alarms collected from over 25 protocols as TL1 messages to your existing TL1 master. You'll be able to see all of your alarms on your familiar TL1 master interface. Detailed alarm alerts in plain English that your staff will immediately know and take action on. Every alert includes full information about the alarm, including its severity, location, date/time stamp, and a user-defined description. Immediate alert of changes of state (COSs), including new alarms and alarms that have cleared. You don't have to hunt to find out what's changed in your network- T/Mon lists it for you. A continuously updated list of all current standing alarms. Even if the system operator acknowledges the alarm, it remains in the Standing Alarms screen until it is cleared. Text message windows displaying single instructions for the appropriate action for an alarm. System staff, even without extra training, will know precisely what to do and who to call in case of an alarm. Nuisance alarm filtering. Unimportant alarms that generate meaningless status notices or oscillate between alarm and clear conditions train your staff to ignore the alarm monitoring system. T/Mon filters out nuisance alarms, allowing your staff to focus its attention on serious threats. Pager and e-mail alerts. Send alarm alerts Read Full Article...

#13 - What is TL1?.
Transaction Language 1 (TL1) is a set of ASCII-based instructions, or "messages". These messages allow a human user or an Operations Support System (OSS) to manage a network object (NE) and its resources. A Standardized Protocol Bellcore developed TL1 in 1984 as a standard (MML) man-machine language to manage network elements. Before the development of TL1, most vendors designed gear around their own proprietary protocols. These incompatible protocols caused headaches for staff, programmers, and support technicians. Having a lot of protocols means more training, more support issues, and more screens to monitor. With the creation of TL1, Bellcore hoped to introduce a single, open protocol for managing network elements. It was intended to replace the diverse protocols used by different vendors. A Man-Machine Language. In addition to being open, TL1 is powerful because it bridges the gap between human users and network gear. It is structured enough to be parsed by machines, but also verbose enough to be read by human staff. Since special decoders or debuggers are not needed, TL1 is a frequent command line interface choice for gear manufacturers. TL1 messages are also embedded with the database information required to interpret the meaning of an alarm. How Understanding TL1 Will Help You TL1 is a multi-vendor and multi-technology protocol with comprehensive management support. There's a very good chance that TL1 protocol plays a...Read Full Article...

#14 - Let T/Mon Mediate Alarms From Your TL1 and SNMP Devices... .
T/Mon NOC Alarm Master Fujitsu TL1 devices SNMP Devices, such as CalixCisco, DHCPatriot and Kasenna. The T/Mon NOC will perform many vital functions such as collecting, filtering, categorizing & present your alarms, maintaining log, alphanumeric paging and e-email alert. One of the most powerful features of the T/Mon NOC is its ability to mediate alarms to other protocols. The T/Mon NOC is a rack mounted, -48V dual feed, Pentium computer. The T/Mon NOC will use the slide rack which can be placed into Vantage Point Solutions's 19" or 23" racks. This solution provides the highest level of local alarm visibility. Alarm viewing will take several forms including our embedded web browser support facility. This interface is incredibly easy to use and will provide network visibility to your staff provided they are given the access rights by your system administrator. Other remote access will be provided using our T/Windows software. This software can be loaded on a lot of PC's and is ideal for technicians and other members of your staff to view alarms from remote locations over LAN, direct connect or dial up. In the event you lose your main hard drive, the T/Mon NOC will automatically fall back to the backup hard drive. In addition, the T/Mon NOC supports a modular interface design. This design allows us to semi-customize each T/Mon NOC for deployments in diverse network architectures. The SNMP Trap Processor Software Module will give your T/Mon NOC the ability to receive SNMP traps from network elements and convert them to standardized T/Mon alarms so you will be able to view them. This will result in a very powerful SNMP manager because not only will your T/Mon be able to accept DCPx from DPS remotes, you will be able to monitor your other SNMP devices as well...Read Full Article...

#15 - Additional TL1 Message Samples... .
TL1 Message Samples Autonomous Messages Autonomous messages, the most frequently used TL1 response type, are output messages sent by the NEs to report alarms, performance data, configuration changes, or condition changes. This means that alarms are sent immediately, instead of waiting until someone requests a status update. In this way, autonomous messages are the TL1 equivalent of the SNMP trap. In addition to receiving autonomous alert of alarms, TL1 staff can schedule messages that periodically report performance data values. Sample Autonomous Message #1 (Critical Alarm): These codes are used to indicate an alarm severity or a response message. Sample Autonomous Message #2 (Alarm Clear): As you can see, this message is almost identical to the original Autonomous Alarm Message, but with a slight difference: The code for Critical Alarm ("CR") has replaced by the code for Clear ("CL"). This indicates that the alarm condition described in the previous message has been cleared. Command Messages TL1 commands request an action to be executed by the recipient of the message Sample Command #1 (Login to Network Element with "Activate" Command): In this example, the UID is a...Read Full Article...

#15 - How to Monitor AFC gear via TL1 with T/Mon....
How This Application Works: Equipment Used: T/Mon NOC or T/Mon SLIM AFC Equipment. There are two master options for this solution. We have provided a technical overview as well as an application drawing for each Master Station. Option 1 features the T/Mon SLIM. The T/Mon SLIM is the smaller of the two Master Stations, however it is capable of collecting alarms from up to 64 devices and 10,000 alarm points. Fitting into a one rack unit size, it's perfect for the networks that have little spare space. Option 2 features the T/Mon NOC. The T/Mon NOC has the ability to monitor upwards of a million alarm points (we have not had a client reach this far yet)! It can have up to 17 simultaneous users, compared to the 5 that are alloted with the T/Mon SLIM, using 6 rack units of physical space. In addition, we included the DTMF/Voice Interface for the T/Mon master that lets you acknowledge or silence alarms from the field, using any touch-tone/cell phone. As easy and familiar as a voice-mail system, the DTMF/Voice Interface uses stored voice prompts to guide you through a menu of options, and you just select your choice by pressing a phone button. The T/Mon keeps track of who acknowledges the alarms over the phone. The T/Mon SLIM is 1 RU unit that fits into any...Read Full Article...