Specifications

CHAPTER

2-1

Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide, R3.3

May 2002

TL1 Gateway

This chapter describes the TL1 Gateway and provides procedures and examples for implementing

TL1 Gateway on the ONS 15454.

Note TL1 Gateway is supported for the Cisco ONS 15454 only.

2.1 Gateway Network Element Topology

You can issue TL1 commands to multiple nodes via a single connection through the TL1 Gateway. Any

node can serve as a Gateway Network Element (GNE), End-Point Network Element (ENE), or

Intermediate Network Element (INE). A node becomes a GNE when a TL1 user connects to it and enters

a command destined for another node. An ENE is an end node because it processes a TL1 command that

is passed to it from another node. An INE is an intermediate node because of topology; it has no special

hardware, software, or provisioning.

To implement the TL1 Gateway, use the desired ENE’s TID in the ACT-USER command at any node.

You do not need to establish a TL1 session on the GNE. From the GNE, you can access several remote

nodes which become the ENEs. The ENEs are the message destinations or origins. The INE handles the

DCC TCP/IP packet exchange.

The GNE Session is the connection that multiplexes TL1 messages between the OSS/craftsperson and

the GNE. The GNE demulitplexes incoming operations support system (OSS) TL1 commands and

forwards them to the remote ENE. The GNE also multiplexes incoming responses and autonomous

messages to the GNE Session. The ENE Session is the connection that exchanges messages between the

GNE and the remote ENE. Figure 2-1 shows the GNE topology.