1. TL1 Cartridge Guide
  2. Preface

Preface

This guide explains the functionality and design of the Oracle Communications Network Integrity TL1 cartridge and the design of the Cisco ONS 15454 SONET TL1 reference cartridge.

Audience

This guide is intended for Network Integrity administrators, developers, and integrators.

This guide assumes that you are familiar with the following documents:

  • Network Integrity Developer's Guide: For an understanding of cartridge deployment, cartridge development, working with cartridges, working with actions, and the extensibility SDK.

  • Network Integrity Concepts: For an understanding of the Network Integrity architecture and using Oracle Communications Design Studio for Network Integrity.

This guide assumes that you are familiar with the following concepts:

  • Oracle Communications Design Studio and its terminology

  • Oracle Communications Information Model

  • Transaction Language 1 (TL1) standards and terminology

  • Cisco ONS 15454 SONET TL1 commands

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Oracle is fully committed to diversity and inclusion. Oracle respects and values having a diverse workforce that increases thought leadership and innovation. As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation. We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.